Original address:
ADB can't open Solutions-vaecer-Blog channel-csdn.net
http://blog.csdn.net/vaecer/article/details/45894643
Encountered a problem description:
Run the Android console output
[2015-05-18 16:18:26-] The connection to ADB are down, and a severe error has occured.
[2015-05-18 16:18:26-] You must restart ADB and Eclipse.
[2015-05-18 16:18:26-] Please ensure this adb is correctly located at ' D:\java\sdk\platform-tools\adb.exe ' and can be executed.
Solve the problem:
Baidu Google said that the task manager kill the ADB or restart the ADB server, but I do not have the Task Manager adb, that is, a program occupies the ADB port.
5037 view this port for the ADB default port as follows:
Netstat-aon|findstr "5037"
TCP 127.0.0.1:5037 0.0.0.0:0 LISTENING 6540
Discovery 6540 takes up 5037 ports, continues to view 6540 of the task, and discovers that it is Wandoujia. as shown below
Tasklist|findstr "6540"
Wandoujia_daemon.exe 6540 Console 1 4,276 K
The next problem is solved, in the task Manager kill Wandoujia_daemon.exe, run the Android program, OK.
1. Turn off the pea pod process
2.ADB Kill-server
3.ADB Start-server
4. Restart Eclipse
Ok
Configure the ADB server port yourself, using an uncommon value.
As simple as defining the value of Android_adb_server_port in the system environment variable.
It is best to choose a 5-digit port number (10000 ~ 65535), which is not easy to repeat.
As long as you add a android_adb_server_port to the environment variable, the value fills in your own defined port.
Linux as long as export $ANDROID _adb_server_port = Custom port, you can.
At this point, open a command line, enter the ADB devices, to see if it is started on the new port ah?
ADB Can't open solutions