Ext.: http://blog.csdn.net/wangdong20/article/details/20839533
Do Android debugging often encounter, the program is written, ready to connect to the phone debugging, can appear in a few moments
I believe that the students who have done Android debugging have encountered this problem, online said kill off with the ADB-related process, restart eclipse
But I didn't see the obvious ADB process on the Task Manager, how do we find them?
First, open cmd, check with adb command, preferably put the path of the ADB command in the system's PATH environment variable,
It would be easier to use the ADB command.
Start the ADB service by cmd-typing: adb start-server. This time will prompt the startup to fail.
There are many reasons why a service fails to start, but it is generally a port binding failure. Let's take a look at the port binding information. , there is really a problem with the port binding.
It seems that we need to bind the port is 5037, it is occupied by other services, we have to see what services occupy 5037 ports
Then open Task Manager, view PID is 4276 process, sometimes the task Manager PID does not display
I see you can click on the view click to select the column in the PID bar tick
Finally check the process PID4276 to find the ultimate culprit
Yes, that's it. The Sjk_daemon.exe process takes up 5037 ports, looking carefully at the old Jinshan mobile phone assistant inside the residue
Writing here, the problem really began, when I tried to close the Sjk_daemon.exe process, unexpectedly show
I clearly turned off the Golden Hill Guards, or not ( Jinshan mobile phone assistants are more and more rogue)
Finally I turned off the Golden Hill poison PA,Sjk_daemon.exe This process to shut down, finally successfully connected to the ADB
Yes, Sjk_daemon.exe this process at the outset, I thought it was Jinshan defender opened, originally this stubborn process is with the Golden Hill poison PA Open together
Everyone encountered this situation can temporarily turn off the Golden Hill poison PA, and so on after the connection to open the Golden Hill poison PA
Warning today, I have to sigh that the experience of Android developers is getting more tragic.
Before there are various market encircle, after the major power-on software to compete for the ADB port, we really are in the cracks in the existence of wood there ah
(go) When Android debugging encounters adb server didn ' t ack as well as the stubborn Sjk_daemon process.