After accessing Android, I have encountered the following errors more than once:
The following errors are repeatedly displayed on the ddms console of myeclipse:
[13:16:15-devicemonitor] ADB connection error: the remote host forces an existing connection to be closed.
[13:16:15-devicemonitor] ADB refused request:
[13:16:15-devicemonitor] ADB refused request:
Sometimes, this type of error occurs inexplicably.
I searched the internet for half a day and found that the most effective method is to restart myeclipse.
A netizen said he could kill adb.exe and restart the Service (completed in cmd)
But I couldn't do it during the test.
[2010-01-03 23:09:51 - DeviceMonitor]Adb connection Error:EOF[2010-01-03 23:09:51 - DeviceMonitor]Connection attempts: 1
[2010-01-03 23:09:51 - DeviceMonitor]Connection attempts: 2。。。。
So now I am using the method of restarting myeclipse.
If you have a better method, please leave a message.
————————————————————————————————————————————————————
Now let's explain the cause of the problem.
Ddms uses a long-lived connection toadb
Server Running locally to get info about connected devices/emulators etc. The error message you posted generally just means that the connectionadb
Has been lost.
Because you ran the reset command, you essential just killed and restartedadb
Process, so eclipse showed that harmless warning for a moment.
You can see this yourself by killingadb
Process manually. eclipse will showConnection attempts: n
For about 10 attempts before giving up.
Ddms keeps sending connections like ADB server for a long time to obtain information about simulators or connected devices. This error indicates that the connection has been lost.