Solution for Mac OSX that eclipse ADB does not recognize (debug) a real machine

Recently, I had a problem developing Android on my Mac. With Vivo x3t as a development machine, connected to the computer after the discovery eclipse in DDMS without my real machine, after some Google and Baidu, finally found a solution, here to share to you.

If you encounter a situation that the ADB command prompts you to find, you can read my other article, set the Android ADB environment variable in MAC

1. First, make sure that you have installed the Android SDK or integrated development environment ADT. After you connect your phone to your computer, enter it in the terminal

[Plain]View Plaincopy

1. ADB devices

If you see a device after the carriage return indicates that it has been configured successfully, then continue with the following steps.

2. manually modify the USB Vendor ID. 0X9BB5 is the vendor ID of my x3t.

Enter in the terminal

[Plain]View Plaincopy

2. mkdir ~/.android
4. echo "0x9bb5" > ~/.android/adb_usb.ini
6. ADB kill-server

3. Turn on "USB debugging" under the Debug menu.

4. Finally restart Eclipse or idea, then perform a real-machine debugging. If that doesn't work, you can try disconnecting your phone.

Reprint please indicate the source. Thank you.

Personal blog: http://blog.csdn.net/lylzwsy

Solution for Mac OSX that eclipse ADB does not recognize (debug) a real machine