After modifying the Android engineering code, the DDMS error occurred during the commissioning phase: The connection to ADB was down, and a severe error had occured.
Since this problem has been encountered before, the workaround is to enter ADT's tool directory under DOS commands and execute instructions.
D:\TOOLS\ADT-BUNDLE-WINDOWS-X86\SDK\PLATFORM-TOOLS>ADB Kill-server D:\Tools\adt-bundle-windows-x86\sdk\ PLATFORM-TOOLS>ADB Start-server
Then restart Eclipse. You can complete the re-debug.
However, this time obviously not.
and began to look for problems.
The first step is to find the port number of the ADB communication in ADT.
D:\TOOLS\ADT-BUNDLE-WINDOWS-X86\SDK\PLATFORM-TOOLS>ADB Nodaemon servercannot bind ' tcp:5037 '
The second step is to find out if 5037 ports have other uses.
C:\Documents and Settings\zhoule>netstat-ano | Findstr "5037" TCP 127.0.0.1:5037 0.0.0.0:0 LISTENING 4112
The third step is to isolate the PID.
C:\Documents and Settings\zhoule>tasklist | Findstr "4112" Sjk_daemon.exe 4112 Console 0 1,744 K
All right, this is the shipment. sjk_daemon.exe!!!
After the process is killed, repeat the ADB kill-server and ADB start-server instructions to restart the eclipse!!!
Good one Jinshan Assistant's process!!!
Kingsoft Assistant Rogue Software-by process Sjk_daemon.exe Pit dead