Under Windows, the Android phone is very simple to connect to a PC, but when I switch to Ubuntu, I see a line in the target list. N/a unknown "similar to the content of such a line, the PC can not correctly identify the phone, by looking for relevant information, the relevant settings, found that can connect the PC, so this record down, for later use.
1, find the phone USB information (ID)
Method: First unplug the phone to connect to the PC's USB cable, then view the USB device information, plug in the USB cable again, check the USB device information again, by comparison, find the USB information of their phone.
Use command: LSUSB
?
123456789101112131415 |
ubuntu :~$ lsusb
Bus 002 Device 003: ID 062a:3633 Creative Labs
Bus 002 Device 002: ID 8087:0024
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 04d9:a06b Holtek Semiconductor, Inc.
Bus 001 Device 002: ID 8087:0024
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ubuntu :~$ lsusb
Bus 002 Device 003: ID 062a:3633 Creative Labs
Bus 002 Device 002: ID 8087:0024
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 18d1:9025
Bus 001 Device 003: ID 04d9:a06b Holtek Semiconductor, Inc.
Bus 001 Device 002: ID 8087:0024
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
|
The information for finding my phone's USB device is:
?
1 |
Bus 001 Device 005: ID 18d1:9025 |
2. Adding Udev rule information
Udev is a dynamic hardware management service
?
1 |
ubuntu : /etc/udev/rules .d$ sudo /etc/udev/rules .d /70-android-usb .rules |
In the 70-android-usb.rules file, add the following:
?
1 |
SUBSYSTEM== "usb" ,ATTRS{idVendor}== "18d1" ,ATTRS{idProduct}== "9025" ,MODE= "0666" |
18D1 represents a read mode for device Id,mode, and 0666 means that anyone can access it. In another article (link at the end of the article), add the following to the file (not personally tested):
?
1 |
SUBSYSTEM== "usb" , SYSFS( "My Phone (USB Debug)" )== "18d1" ,MODE= "0666" |
Set 70-android-usb.rules file permissions and restart the Udev service.
?
12 |
ubuntu : /etc/udev/rules .d$ sudo chmod a+rx /etc/udev/rules .d /70-android-usb .rules ubuntu : /etc/udev/rules .d$ sudo /etc/init .d /udev restart |
3. Set up adb
Unplug the USB and PC cable, then plug it in again, enter the ANDROID-SDK root directory \platform-tools\, and run the command sudo./adb kill-server and sudo./ADB devices.
?
12345 |
ubuntu: ~ /android-sdk-linux/platform-tools $ sudo /adb kill -server ubuntu: ~ /android-sdk-linux/platform-tools $ sudo /adb devices * Daemon not running. Starting it's on port 5037 * * Daemon started successfully * list of devices attached |
At this point, you'll find that your mobile device eclipse is already recognized.
RELATED links:
Http://www.cnblogs.com/successyiquan/archive/2012/02/08/2342669.html
http://blog.csdn.net/wuzuokun/article/details/7168521
--------------------------------------------------------------------------
Here's the second way to collect online
Update the MTP Library
---------------------------------------------------------------------------
sudo add-apt-repository ppa:langdalepl/gvfs-mtp
sudo apt-get update
sudo apt-get install Gvfs
Install GVFS by the above command, after installation, restart Linux, the system can recognize and transfer files to android4.0+ device after booting.
Ubuntu Connect Android Phone