Adb debugging android Program

I. Android adb is not an internal or external command Solution

 There are two possible reasons for this problem:    

    1. the environment variable is not configured. You only need to add the android installation: C: \ Program File \ android-sdk-windows \ tools to the system variable Path, note that there will be other paths configured in the Path. You need to add them before the android Path. Then paste the above Path and it will be OK.

  2. if the environment variable is configured and adb is entered in cmd, the problem "adb is not an internal or external command" still occurs. Then let's look down: when I first learned about android, I found many ways to configure the android environment variables on the Internet. I also configured the android environment variables according to their statements, and then input adb to display a lot of information. information, but I made a mistake, but I did what I said on the Internet, and most of them were the same. I found a mistake and I couldn't find it for a long time, I can't find it. Isn't it just configuring an environment variable? What are the configuration items? Now let's look at the folder and find that there is adb.exe under \ platform-tools, but not under the tools Folder. It turns out to be like this. Android2.2 is different from android 2.3. android2.3 adb.exe is placed under the android-sdk-windows \ platform-tools directory, while android 2.2 is placed under the tools directory, so the path of my path is under platform-tools, and then enter adb. Success !!!

  I hope you will note that the folder path will change after the android version is changed, but as long as you make the corresponding changes, I believe there is no big problem. O_o