The connection to adb is down in android, Problem and Solution

1. Error:
BUILD FAILED
D: \ workspace \ ganji \ build. xml: 144: The following error occurred while executing this line:
D: \ workspace \ ganji \ build. xml: 271: Unable to delete file D: \ workspace \ ganji \ tmp \ proguard \ tmp. jar
Solution:
A simulator has been enabled and cannot be re-compiled. You must disable one. For ant

2. Error:
The connection to adb is down, and a severe error has occured.
Who can solve this problem?
Solution:
Cmd jump to the sdk tools file path
Adb kill-server
Then adb start-server

3. Error:
The connection to adb is down, and a severe error has occured.
[09:36:56-HelloOPone] You must restart adb and Eclipse.
[09:36:56-HelloOPone] Please ensure that adb is correctly located at 'd: \ OPhoneSDK_1.5
\ Platform-tools \ adb.exe 'and can be executed.
Solution:
Method 1. adb kill-server in cmd, and then adb-startserver
2.18.1then, kill adb.exe in the task manager, and then restart Eclipse.
Method 3. If methods 1 and 2 do not work, check that adb.exe exists in the last error message in platform-tools( my error is that there is no platform-tools Folder under the relevant path ).
So I chose to create a new folder and copy all the files in tools to platform-tools)
4. the previous method was summarized by others. One of the situations I encountered was that software of the "pea pod" or "Mobile assistant" occupied adb, stop pods and adb in Task Manager and restart adb or eclipse.
5. If the previous method still fails, we recommend that you reinstall a new system. You 'd better change the system. Some Daniel also said: MS has some minor problems [size = large] [/size]

1. Have you tried all the methods on the network? If not, check whether 360 security guard is installed;
2nd, if you have installed and with an adb.exepath, The adb.exe of eclipsecannot be started, resulting in the adb connection failure during debugging. First shut down the 360 security guard. After the first running, start adb.exe, and then start the security guard, there will be no problem.

My solution: eclipse and the simulator are all closed, restart eclipse, Run Configuration-> Target at the beginning of Manual by default, the selection is not gray, select automation and then select Manual, Manual becomes gray run, select a simulator. The simulator is normal.

Author: superjunjin