Android Enthusiasts Stack Exchange is a question and answer site for enthusiasts and power users of the Android operating system. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

My main problem with developing in Android is that the emulator seems to continually get disconnected from eclipse. This always happens the 2-3 time I try to upload my .apk from eclipse without rebooting the emulator. Eclipse indicates this with an empty DDMS ->Device section and logcat stays blank - sometimes I'm not sure if the new code made it on the device.

The only fix I have for this is to shut down eclipse, and restart it. With the restarting of Eclipse, on top of the emulator boot time, I can't get any momentum going in my development.

Is there a way to reconnect the emulator to eclipse without having to restart Eclipse or even the Emulator?

share|improve this question
up vote 1 down vote accepted

you can use "emulator" from console. That way it will stay on regardless of eclipse state.
starting emulator

also, try using adb devices to find out is your emulator really running

share|improve this answer

You can reconnect your emulator using the Android Debug Bridge (ADB).

There are 2 primary methods to do this:

  1. In Eclipse, open the "Devices" view. The last button on the right (upside down triangle) will open a menu of additional options. The very bottom selection is "Reset adb"

  2. From a command prompt you can type the following 2 commands to stop and restart ADB. adb kill-server
    adb start-server

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.