I usually close down eclipse, kill the adb process and the emulator (make sure eclipse isn't still hanging, kill it if it is).
I would suggest using sysinternals process explorer to find and kill your processes. I use it ALOT while developing in android :). On Apr 6, 8:18 am, sasperilla <[EMAIL PROTECTED]> wrote: > I keep getting this error in my console when I try to startup the > emulator. I've restarted Eclipse, but it keeps croaking with this > error. Also the emulator easily takes 5 minutes to startup before > finally getting a application not responding on googleapps. Any ideas > on what I should do? I'm on Mac OS X 10.4 > > [2008-04-06 10:07:49 - PocketCast] ------------------------------ > [2008-04-06 10:07:49 - PocketCast] Android Launch! > [2008-04-06 10:07:49 - PocketCast] The connection to adb is down, and > a severe error has occured. > [2008-04-06 10:07:49 - PocketCast] You must restart adb and Eclipse. > [2008-04-06 10:07:49 - PocketCast] Please ensure that adb is correctly > located at '/Users/charlie/lib/android-sdk_m5-rc15_mac-x86/tools/adb' > and can be executed. > > Charlie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
