Programmer algorithm practice must read, common Java API skills to share>>>
Phenomenon 1: when the mobile phone is connected to USB for monkey test, start a CMD window to input again, and error closed appears after the ADB shell returns. In some cases, some mobile phones will appear this phenomenon
Phenomenon 2: when the mobile phone is connected to USB for eclipse debugging or app installation, Eclispe console prompts: failed to install * *. APK on device ‘019417a3’: unable to open sync connection
I think the reasons for the two phenomena are the same
The solution is as follows:
First: restart the computer, then check the mobile phone to the computer and start eclipse
Second: mobile phone – Settings – Application – Development – USB debugging, open and close again
Third: restart the phone, USB debugging on and off again
Fourth: try “ADB kill server” and then “ADB start server” under CMD
In my opinion, the second and third methods are more practical
Similar Posts:
- The ADB command installs APK, and the installation problem is solved by daemon not running. Starting it now on port 5037
- How to connect Android mobile phone with ADB & reasons and solutions of unable to connect to 192.168.1.100:5555
- Android studio can’t find the emulator and can’t connect to the mobile phone. Prompt adb.exe start server ‘failed — run manually if necessary
- adb server version (31) doesn’t match this client (41); killing…
- Android ADB server didn’t ACK * failed to start d
- Connect unity profiler to Android real machine for debugging
- [Solved] Android ADB server didn’t ACK * failed to start daemon *
- Obnoxious permission denied: how does ADB handle permission denied when accessing mobile directory
- IOS10 debugging problems – Development cannot be enabled while your device is locked.
- How to Solve Android wireless debug Error