Today downloaded a master brush, the results of the Android port to occupy. Depressed for a long time

When the phone is connected to the computer port to run the ADB program debugging, there is a situation like the following:

Analysis: The reason for the error is that the ADB port is occupied by other programs ' processes, so what to do is to find and kill the process.

Tools/Materials

• Cmd.exe, Task Manager

1. Execute ADB nodaemon server in cmd, see what the ADB's port number is, and generally 5037 (why? The port number used by the software should be fixed), as

1. Re-execute Netstat-ano | Findstr "5037", you will see a similar scenario as follows:

3. A little explanation here is that the left-to-right meaning is the connection type (TCP), the local address and port, the external address and port, the connection status, and the PID number of the process. Here are two processes occupy 5037 ports, one occupies the local 5037 port, the other occupies the external 5037 port, to kill the local PID is the port of 240!

4. Ctrl+alt+del to serve as the manager of the service. Click Process, now looking for a PID of 240 process. Sometimes you may find that the Task Manager does not have the process PID information display, this time just click on the task Manager's view---select column, such as, and then the PID check. At this point, check the PID of the current process again and kill the PID 240 process. Then run the ADB command and it will be smooth!

Today downloaded a master brush, the results of the Android port to occupy. Depressed for a long time