ADB Connection Error: The remote host forced the shutdown of an existing connection

The Eclipse console always has this problem when it comes to Android development, and sometimes it happens when you start eclipse, sometimes when you run the Android program, restarting the AVD and restarting Eclipse. The solution was found on the Internet.

Let's say why, this is the DDMS call to ADB.  After a search, it was discovered that this is a limitation of the ADB in the Windows environment, which can also be said to be a bug. When the number of simultaneous processes running on the phone is greater than 64 o'clock, the ADB is thrown. The deeper reason is that the maximum number of handles supported by the Windows API WaitForMultipleObjects is maximum_wait_objects, or 64.

Find someone else's adb.exe on the internet and replace the Adb.exe file under the Platform-tools of the Android SDK installation directory. This problem will not be wrong, the principle is to change the maximum number of support to 256.

Files: http://code.google.com/p/android/issues/detail?id=12141

If it doesn't work, use the second method.

In Eclipse view mode Select Ddms(also common Java and debug views), Display the Devices window, if none can be displayed by selecting Window->show view->devices, and then Select Reset adb in the drop-down arrow.

At this point, Eclipse will retry automatically, and entering connection attempts:1 means success.

The third method of

When developing an Android system, sometimes the DDMS console will pop up the following message:

[2012-02-18 17:17:11-devicemonitor] Sending Tracking request failed!
[2012-02-18 17:17:11-devicemonitor] ADB Connection Error: The remote host forced the shutdown of an existing connection.
[2012-02-18 17:17:12-devicemonitor] Sending Tracking request failed!
[2012-02-18 17:17:12-devicemonitor] ADB Connection Error: The remote host forced the shutdown of an existing connection.

Generally under the Linux platform is not to report this error,

It's simple enough to solve.

First step: Open Task Manager, list all user processes, and force all adb.exe processes to be terminated.

Step Two: Enter the phone management interface. The Debug interface has a debug option, close once and open, and connect the data cable to the computer from a new time

Step three: Under the computer terminal to enter their own (if not configured environment variable) SDK path under the tools or TOOLS7 directory, enter ADB kill-server and then enter the ADB start-server configuration environment variables, directly enter these two commands just fine

So the big announcement became.

The reason, some people installed the Pea pod to install the mobile phone driver. The pea clip will start a adb.exe process. Conflicts with existing ADB processes:

Close or unload pea pods when not in use.

Some people do not support the eclipse does not support pad, or high-grade mobile phones. Support for 2.2 or lower mobile phones is good. In this case, check the update in Eclipse, or the Direct SDK directory has an update, click Update adb to the latest version, and the ADB generally does not seem to need to install a mobile phone driver can be connected to the phone.

A workaround:

1. After turning off the pea pods

2. Start-> Run->cmd, go to the Android directory Android-sdk-windows\platform-tools,

Run the following command:

ADB devices

ADB Connection Error: The remote host forced the shutdown of an existing connection