Android Reconnect Debugger
Solution 1:
In eclipse, open the 'DDMS Perspective'
You will notice an upside down triangle on the far right of the 'Devices' tab.
In this menu, you can select 'Reset ADB'. This will reset the ADB server, and reconnect your emulator.
You will likely see an error message telling you the process didn't restart properly - you can ignore this message.
Solution 2:
I've never tried this with intentionally suspending the emulated network, but the android emulator is actually an ADB-over-TCP target with a special name. For some "random" losses of connection, you can recover by creating a new explicit adb-over-tcp session to the emulator.
If you had emulator-5554, you would connect to it with
adb tcp 127.0.0.1:5555
which is to say, the loopback address of the development machine, and one port higher than the control port.
Again, I don't know that this will work for your particular cause of adb failure, but it does work for some.
Also (just answered this elsewhere today) if you have multiple connected adb targets and so need to explicitly specify this reconnected emulator with the -s option to adb, you would need both the address and port, for example
adb -s 127.0.0.1:5555 some_adb_command
Another thing you might try is killing the adb server, then trying to use adb again (which will launch a new adb server) in the hope that it picks up the running emulator instance.
Solution 3:
What about
adb kill-server
adb start-server
in console(terminal)?
Post a Comment for "Android Reconnect Debugger"