[Solved] The application starts only once: (

Common bugs/problems with the Android SDK the Emulator and the ADT-Plugin.

[Solved] The application starts only once: (

Postby jaison » Sat Jan 12, 2008 7:04 pm

I have a problem, the application starts only once.

After I change something in the code, save and compile command, it does not come more in the application, it is only in that original theme of the Android (default).

To solve the problem I have q restart the computer. : (

Anyone has any doubt?

Console the application running:
Code: Select all
[2008-01-12 14:47:44 - TesteCel] ------------------------------
[2008-01-12 14:47:44 - TesteCel] Android Launch!
[2008-01-12 14:47:44 - TesteCel] Launching: com.identificadorunico.android.TesteIMEI
[2008-01-12 14:47:44 - TesteCel] Launching the emulator.
[2008-01-12 14:48:04 - TesteCel] Emulator is up! Waiting for HOME to be launched.
[2008-01-12 14:48:13 - TesteCel] HOME is up!
[2008-01-12 14:48:13 - TesteCel] Pushing TesteCel.apk to /data/app on the device
[2008-01-12 14:48:13 - TesteCel] Starting activity on device: com.identificadorunico.android.TesteIMEI
[2008-01-12 14:48:18 - TesteCel] ActivityManager: Starting: Intent { comp={com.identificadorunico.android/com.identificadorunico.android.TesteIMEI} }


Console the application not working:
Code: Select all
[2008-01-12 14:47:44 - TesteCel] ------------------------------
[2008-01-12 14:47:44 - TesteCel] Android Launch!
[2008-01-12 14:47:44 - TesteCel] Launching: com.identificadorunico.android.TesteIMEI
[2008-01-12 14:47:44 - TesteCel] Launching the emulator.


Note that not enough to load the following bit of code:
Code: Select all
[2008-01-12 14:48:04 - TesteCel] Emulator is up! Waiting for HOME to be launched.
[2008-01-12 14:48:13 - TesteCel] HOME is up!
[2008-01-12 14:48:13 - TesteCel] Pushing TesteCel.apk to /data/app on the device
[2008-01-12 14:48:13 - TesteCel] Starting activity on device: com.identificadorunico.android.TesteIMEI
[2008-01-12 14:48:18 - TesteCel] ActivityManager: Starting: Intent { comp={com.identificadorunico.android/com.identificadorunico.android.TesteIMEI} }
jaison
Freshman
Freshman
 
Posts: 2
Joined: Tue Jan 01, 2008 12:54 pm

Top

Postby plusminus » Sat Jan 12, 2008 7:35 pm

Hello jaison,

I also have the same problem from time to time. I solve it by killing the adb.exe from the taskmanager (not closing the emulator). Eclipse will(or at least should) recognize that there is still an emulator up and will start a new adb.exe to connect to the existing emulator instance to reuse it.

Perhaps it helps (emulator got various bugs :( )

Regards,
plusminus
Image
Image | Android Development Community / Tutorials
User avatar
plusminus
Site Admin
Site Admin
 
Posts: 2688
Joined: Wed Nov 14, 2007 8:37 pm
Location: Schriesheim, Germany

Postby jaison » Sat Jan 12, 2008 8:07 pm

plusminus wrote:Hello jaison,

I also have the same problem from time to time. I solve it by killing the adb.exe from the taskmanager (not closing the emulator). Eclipse will(or at least should) recognize that there is still an emulator up and will start a new adb.exe to connect to the existing emulator instance to reuse it.

Perhaps it helps (emulator got various bugs :( )

Regards,
plusminus


thank's Regards...
jaison
Freshman
Freshman
 
Posts: 2
Joined: Tue Jan 01, 2008 12:54 pm

Top

Return to SDK/ADT/Emulator Problems

Who is online

Users browsing this forum: Yahoo [Bot] and 6 guests