CD/etc/udev/rules. d/
Sudo
Gedit 52-android.rules
Subsystem = "USB ",
Env {devtype} = "usb_device", mode = "0666", General
Sudo chmod A + R/etc/udev/rules. d/52-android.rules
Modify permissions
Sudo/etc/init. d/udev restart restarts the connection to the USB device.
Then go to the android SDK decompression path and go to platform-Tools
Www.linuxidc.com @ linuxidc:/etc/udev/rules. d $ CD/home/Ritter/Android-sdk-linux_86/platform-tools/
Www.linuxidc.com @ linuxidc :~ /Android-sdk-linux_86/platform-tools $
Enter "sudo./ADB kill-server"
Www.linuxidc.com @ linuxidc :~ /Android-sdk-linux_86/platform-tools $ sudo./ADB kill-Server
Enter "sudo./ADB start-server"
Www.linuxidc.com @ linuxidc :~ /Android-sdk-linux_86/platform-tools $ sudo./ADB start-Server
* Daemon not running. Starting it now on port 5037 *
* Daemon started successfully *
Enter "./ADB devices"
Www.linuxidc.com @ linuxidc :~ /Android-sdk-linux_86/platform-tools $./ADB Devices
List of devices attached
Sh0b5rt08771 Device
At this time, my mobile phone number is correctly displayed. It indicates that the real machine connection is successful. In eclipse, you only need to configure the target in run deployments as a mobile device to install the program to the real machine for debugging.
PS:
For the next connection, if the device is displayed as "???", Remember to go to platforms-tools under Android SDK
Run
Sudo./ADB kill-Server
Sudo./ADB Devices
You can see the device that is correctly identified.