Android development issues encountered using Totalcontrol debugging (note)

Background: Android development, using Totalcontrol to control the phone for debugging.

Process: Eclipse debugging has been normal, one afternoon suddenly prompted: Unable to start the ADB.exe, please confirm whether the corresponding path.

Suspect is the program written by the problem, so the previous debugging through the program to turn out, just as unable to run.

At that time depressed, all kinds of Baidu, can not solve the problem.

The basic solution is to close the Totalcontrol ADB.exe, process, and manually launch the ADB under the SDK.

Result: The ADB under the SDK cannot be started. Shutdown Totalcontrol cannot connect to the phone and cannot be debugged.

Unable to determine the cause, directly enlarge the Recruit, uninstall the SDK reinstall. Solve.

Reflection: The morning debugging all smooth, in the middle there is a class can not be used normally, prompted to find the source, so upgrade the SDK, the problem occurs.

Now it should be the result of the upgrade, which causes the file to change or corrupt, the ADB will not function properly.

After the upgrade, the ADB should be able to run normally, my approach is not the best way, have encountered the problem and resolved the welcome message.

Android development issues encountered using Totalcontrol debugging (note)