The 19% hangup happens to me when I start Eclipse and try to run an APK on the emulator prior to the load finishes. When I let it finish loading, things are almost always smooth.
Note that when you are cleaning up stuff by killing Eclipse and javaw apps, consider also killing adb.exe by the task master or "adb kill- server" from terminal. Sometimes after much debugging session, my Eclipse gets disconnected from the emulator and I have to restart things. On Apr 24, 8:13 pm, kingkung <[EMAIL PROTECTED]> wrote: > Hi, > > I'm working in Eclipse, version m5, and I find that many times, when I > launch my app through Android, the Eclipse progress bar gets stuck at > 50%, and Eclipse hangs. The last thing that shows in the Android > console is > > "Launching: com.google.android.yourAppName" > > Whenever this happens, I have to close eclipse, go to the Windows task > manager and close the eclipse.exe and javaw.exe tasks, and start > eclipse up again for the emulator to work. > > This happens very commonly after the emulator encounters some kind of > error from the previous app, and is forced to quit. > > Is this a common problem for others? This sounds very similar to the > 19% problem, but i'm getting it at 50%. > > Is there anything I can do to not run into this error? It's happening > frequently and it's pretty annoying. > > Thanks, > > James --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Beginners" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~----------~----~----~----~------~----~------~--~---
