Ubuntu下android开发之配置USB设备

这篇文章讲如何让普通用户访问USB设备

第一步，得到USB设备的ID，使用lsusb命令，得到结果如下:

Bus 002 Device 002: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0

Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 

Bus 001 Device 025: ID 18d1:4e12 

Bus 001 Device 007: ID 1a40:0101 TERMINUS TECHNOLOGY INC. 

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

如果不能从名字里看出来，可以通过插入USB设备之前和之后的lsusb结果来比较出所要访问的设备的ID。

idVendor:idProduct 

***************************************************************
我的edv信息：
lsusb命令后：
Bus 001 Device 006: ID 04e8:689e Samsung Electronics Co., Ltd
***************************************************************

第二步，把USB设备的ID加入到UDEV规则中 

sudo gedit /etc/udev/rules.d/99-android.rules 

如果没有这个文件，请生成一个

并编辑内容如下, 里面的idVendor和idProduct从第一步中得到:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", ATTRS{idProduct}=="4e12", MODE="0666", OWNER="your_name"

下面是一个NexusOne手机的例子
SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", ATTRS{idProduct}=="4e12", MODE="0666", OWNER="your_name" SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0fff", MODE="0666", OWNER="your_name" #Fastboot

注:yourname 就是本机的用户

第三步，重启UDEV和

adb sudo restart udev 

adb kill-server 

拔掉USB设备，并重新插上

***************************************************
另一种实现方式：

在终端运行 lsusb  
会发现结果有会有如下类似记录:  
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub   
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub   
Bus 004 Device 005: ID 1219:0102               ＃这行就是 手机  
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub   
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub   
这时键入  
sudo gedit  /etc/udev/rules.d/51-android.rules  
在打开的文件中增加以下文本：  
SUBSYSTEM=="usb", SYSFS{idVendor}=="1219", MODE="0666"   
SUBSYSTEM=="usb", ATTR{idVendor}=="1219", ATTR{idProduct}=="0102", SYMLINK+="android_adb"  
2) 运行以下命令：  
sudo chmod a+rx /etc/udev/rules.d/51-android.rules  
sudo /etc/init.d/udev restart  
3) 在 android sdk 的 platform-tools 目录下运行 （这一步很重要，必须要sudo，否则没效果）  
sudo ./adb kill-server  
sudo ./adb devices  
然后，就可以直接用 adb  shell来进行操作了

针对小米手机，如果还不行，在拨号处输入 *#*#717717#*#*
**************************************************
官方文档：

Configuring USB Access

Under GNU/linux systems (and specifically under Ubuntu systems), regular users can't directly access USB devices by default. The system needs to be configured to allow such access.

The recommended approach is to create a file /etc/udev/rules.d/51-android.rules (as the root user) and to copy the following lines in it. <username> must be replaced by the actual username of the user who is authorized to access the phones over USB.

# adb protocol on passion (Nexus One)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e12", MODE="0600", OWNER="<username>"
# fastboot protocol on passion (Nexus One)
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0fff", MODE="0600", OWNER="<username>"
# adb protocol on crespo/crespo4g (Nexus S)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e22", MODE="0600", OWNER="<username>"
# fastboot protocol on crespo/crespo4g (Nexus S)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e20", MODE="0600", OWNER="<username>"
# adb protocol on stingray/wingray (Xoom)
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}=="70a9", MODE="0600", OWNER="<username>"
# fastboot protocol on stingray/wingray (Xoom)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="708c", MODE="0600", OWNER="<username>"
# adb protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0600", OWNER="<username>"
# fastboot protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e30", MODE="0600", OWNER="<username>"
# adb protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d101", MODE="0600", OWNER="<username>"
# fastboot protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d022", MODE="0600", OWNER="<username>"
# usbboot protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d00f", MODE="0600", OWNER="<username>"
# usbboot protocol on panda (PandaBoard ES)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d010", MODE="0600", OWNER="<username>"
# adb protocol on grouper/tilapia (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0600", OWNER="<username>"
# fastboot protocol on grouper/tilapia (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0600", OWNER="<username>"
# adb protocol on manta (Nexus 10)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee2", MODE="0600", OWNER="<username>"
# fastboot protocol on manta (Nexus 10)
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="689e", MODE="0600", OWNER="<username>"

Those new rules take effect the next time a device is plugged in. It might therefore be necessary to unplug the device and plug it back into the computer.

This is known to work on both Ubuntu Hardy Heron (8.04.x LTS) and Lucid Lynx (10.04.x LTS). Other versions of Ubuntu or other variants of GNU/linux might require different configurations.