Up to now, Android Cottage phone manufacturers have so many, can modify and customize the Android OS has been a lot of people, some cows to modify the Android system will only affect the modified point, will not affect the others, and then there is not much to say, In short, the changes will cause a lot of problems affecting other aspects of functionality. For Android app developers, the most common is the ADB (Android Debug Bridge) connection problem, HTC did not say, and Google co-operation, the first few generations of Android system version came out, Google is the first from HTC out of the corresponding new Android version of the product, so the new product of many Android features represent the original intention of Google. So there are fewer problems with HTC's phone. Said a little nonsense, the following to get to the point: Mac OS x and Windows (XP, 7) under the ADB connected to Android phones, there is a difference is the Mac OX X is not the so-called Android USB adb driver, only need to download the official Google SDK development package, Specifies that the android-sdk-macosx/platform-tools/path passes to the current user's environment variable in the system.
[Java]View PlainCopy
- -macbook-pro:~ user$ Vim/users/user/.profile
- Export path= $PATH:/android-sdk/android-sdk-macosx/platform-tools
- Export path= $PATH:/android-sdk/android-sdk-macosx/tools
Tools such as the pre-ADB are placed under the Tools directory, and later unified into the Platform-tools directory. Thereafter, open the terminal, under any current path can directly execute the ADB command, via USB cable will be Android phone and Mac pc connected, ADB devices, no corresponding device list. Here are the workarounds: 1. Open terminal, enter: System_profiler spusbdatatype, check all USB device information of Mac system, find the corresponding vendor Vender ID. Check the corresponding USB hub with Android phone device, find the corresponding manufacturer Vender ID, for example, my test machine K-touch T619 Day language phone can not connect adb, find the corresponding information fragment as follows:
[Java]View PlainCopy
- -----------------
- Spreadtrum Phone:
- Product ID: 0x5d04
- Vendor ID: 0x1782
- ...
- Serial number:t619
- ...
- -----------------
2. The terminal enters/users/user/.android, there should be a Adb_usb.ini file, if not created, then add the above vender ID "0x1782" a separate line to the file, and then exit.
[Java]View PlainCopy
- # ANDROID 3RD Party USB VENDOR ID LIST--does not EDIT.
- # Use the ' Android update adb ' to GENERATE.
- # 1 USB VENDOR ID PER line.
- 0x1782
3. Restart the ADB server process. The terminal executes the following command in turn:
[Java]View PlainCopy
- ADB kill-server
- ADB start-server
The ADB devices command can then be used to view devices with the name serial number of the corresponding device. Such as:
[Java]View PlainCopy
- -macbook-pro:.android user$ ADB devices
- List of devices attached
- emulator-5554 Device
- T619 Device
Ps:1. Sometimes the ADB devices can not display the connection device, need to unplug the data cable, plug in several times, and exit the terminal, and then re-open, then enter the command to find the connected device, and then can not connect please restart the computer, waiting for the system to initialize the environment settings. It is important to note that not all Android machines can be solved, such as some mobile phone has a supplier ID, missing Product ID, still cannot recognize, this kind of wonderful can only find other methods. 2. Windows (XP, 7) can also be resolved in the same way below. However, the premise is that the ADB environment variable has been specified and installed the corresponding Android phone device of the ADB USB driver, determine if there is not installed by the phone and Windows connection, Device Manager did not find that there is a question mark on the device is loaded, there is no installation of instructions. Then in the C:\Users\username\.android directory there is also a Adb_usb.ini file, as in the previous line to add the corresponding device vender ID, restart the ADB server process.
Go Some Android phones under Mac OS X can't connect to the ADB problem solution
