Executing Andorid test preject in eclipse prompts the connection to ADB are down, and a severe error have occured. Workaround

When you start the Android emulator. Sometimes the connection to ADB was dropped, and a severe error has occured. In the user said on the task manager to shut down all the Adb.exe. Restart Eclipse. But try It doesn't work. So find a way to do it on a foreign site:

1. Turn eclipse off first.

2. In the manager to go to your Android SDK under Platform-tools,:


3. Type adb kill-server if ADB is closed and will prompt for server not running *

4. Re-enter ADB start-server if unsuccessful, prompt daemon not running. Starting it now on port * * *

If it succeeds, it does not prompt for any statements. Then re-open Eclipse to run the emulator normally.

There is a situation, the real machine debugging, you opened the wrist bean clip, causing the port conflict, the front has not been aware of the problem, the solution: After installing the driver of the phone, close the wrist bean clip, restart Eclipse, should be able to. The wrist bean clip does not open at the same time as Eclipse!

Executing Andorid test preject in eclipse prompts the connection to ADB are down, and a severe error have occured. Workaround