正如你所说的，这个问题是不是蚀失去联系的仿真器，但亚行 - 中的Android调试桥 - 失去与它接触。由于Eclipse使用亚行与模拟器进行通信时，亚行坏了Eclipse可以什么都不做。

As you said, the problem is not Eclipse losing contact with the Emulator, but ADB - the Android Debug Bridge - losing contact with it. As Eclipse uses ADB to communicate with the emulator when ADB is broken Eclipse can do nothing.

要解决这个问题运行停止ADB服务器以下命令：

To fix this stop the ADB server by running the following command:

adb kill-server

然后Eclipse会通常会尝试重​​新启动亚行，或者您也可以通过运行ADB命令重新启动它自己，如：

Eclipse will then usually try to restart ADB, or you can restart it yourself by running an ADB command, such as:

adb devices

如果你这样做，你会看到这样的输出：

If you do, you'll see output like this:

* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
emulator-5554   device

您还可以通过鼠标做到这一点，使用重置亚行在设备视图在Eclipse中选择。

You can also do this via the mouse, using the Reset adb option in the Devices view in Eclipse.

另外值得一提的控制台查看有两种模式， DDMS 和安卓 。您可以在控制台是平时模式，但它的 DDMS 模式下，它会显示亚行的状态信息。通过点击按钮，用监控器图标，或者使用旁边的箭头，它选择的模式：

It's also worth noting the Console view has two modes, DDMS and Android. You're usually in Console mode but it's DDMS mode which will show ADB status messages. Select modes by clicking the button with the Monitor icon, or using the arrow next to it:

如果一切都失败，请尝试从OS杀亚行的过程。在Windows XP中使用：

If all else fails, try killing the adb processes from the OS. On Windows XP I use:

TASKKILL /F /IM adb.exe