You must restart ADB and Eclipse related solutions

There is a problem today, the problem is as follows

I tried n kind of Google to the method, all failed, now put my solution to tell you, hope to help everyone.

First of all, I first listed the method I searched, we can also try.

1, close Eclipse and kill adb.exe in the process, then reboot.

2, if there is a real machine connection, unplug the real machine, repeat the 1 steps,

3, turn off Eclipse, and then run the following command at the command line

ADB kill-server

ADB start-server

Then restart Eclipse

There are other similar ways to not say more here,

My problem is basically Port 5037 is occupied, run netstat-a on the command line, will appear a bunch of things, find out if there is something about 5073 port, after I verify that I have something, so my port is used, But I have killed Adb.exe, so it is something else occupies this port, recalled the next, what the recent operation and the previous difference, that is, with the pea pod connected to the real machine, it may be the pea pod occupied, I first shut eclipse, I killed the pea pod in the process, and then restart Eclipse, then the command line to execute ADB Reboot; The following conditions occur

Can see the port back, daemon open successfully, and before the error in the console daemon is open failure, now the problem basically solved, here is an error, do not worry, just did not detect the device, may not run the simulator or not even the real machine caused, Now you can run the project test, I think the problem should be solved. According to my situation, the next day after the restart of the project to run the same problem, the process of more pea pods, but I did not open the Pea pod, it is recommended not to set the Pea pod boot. The problem will be solved.

If there is a developer like me with a pea pod installed APK developers encounter such a problem can try this method, and finally I recommend that you install the APK or the best command-line push or instal, in fact, I advocate the use of such third-party software, sometimes the most primitive method is the most convenient.

This post incredibly fire, OK, can not bear to update a version, to help you solve the problem faster;

If you try ADB start-server

1. C:\Users\xxxx>adb start-server
2. ADB server is an out of date. Killing ...
3. ADB server didn ' t ACK
4. * Failed to start daemon *

If the problem arises, then the basic question is that the 5037 port is occupied,

Now everyone can come and verify to see if this is my guess, using the command line ADB Nodaemon server

If prompted to say

1. Cannot bind ' tcp:5037 '

Then it means that port 5037 is occupied.

We also do not have to struggle with what Occupy, this gives an intuitive and convenient way, let everyone immediately find the damn thing.

That's using the command line: netstat-a | Findstr "5037" to view processes that occupy 5037 ports

For example, the results are as follows:

Then you can know that the PID 4236 process occupies the port, in the process management to find the PID 4236 process, kill him, just fine oh

PS: How to view the method of PID, in the window above click View---Select the column, and then check the PID is good, hehe.

You must restart ADB and Eclipse related solutions