When your running emulator isn't showing up in the Android Device Chooser

This has been documented elsewhere for similar cases and is more of a note to self than anything else.

Occasionally I have found, while debugging, Eclipse will lose track of the running Android emulator instance. So the emulator is happily chugging away, but will refuse to appear in the 'Android Device Chooser' running device list. Because the emulator takes so long to start, I am loath to kill and restart it, which usually fixes the problem.

With a little bit of Googling I stumbled across someone with a similar issue, who was advised to try the following commands to resolve the problem:

adb kill-server adb start-server

The Android Debug Bridge documentation talks about the occasional necessity to restart the server when it is 'unresponsive', so this is clearly one of those cases:

In some cases, you might need to terminate the adb server process and then restart it. For example, if adb does not respond to a command, you can terminate the server and restart it and that may resolve the problem.

Permalink - Tags: Development,Android,Google