Fedora 14, Android Development, and udev Rules Part 2

I finally got around to adding the Asus Transformer to 51-android.rules (under /etc/udev/rules.d). Here's the complete list of the devices I've set up in Fedora 14. I'm now trying to experiment with Android 3 (Honeycomb) specific features as well as get comfortable with tablets as apposed to my smartphone.

# HTC myTouch 4G
SUBSYSTEM=="usb",ATTRS{idVendor}=="0bb4",SYMLINK+="android_adb",MODE="0666"
# Motorola Xoom
SUBSYSTEM=="usb",ATTRS{idVendor}=="22b8",SYMLINK+="android_adb",MODE="0666"
# ASUS Transformer
SUBSYSTEM=="usb",ATTRS{idVendor}=="0b05",SYMLINK+="android_adb",MODE="0666"

As a reminder, to determine what to add to a udev rule, plug in your Android device and run 'lsusb' in a terminal. Look for your device in the list. Once you've identified it you use the major USB ID number (in this case 0b05 on the ASUSTek Computer line) in the ATTRS section of the udev rule. Failure to set up a working udev rule will result in a permissions error message on the device when you run Android's ddms.


Bus 007 Device 003: ID 0b97:7772 O2 Micro, Inc. OZ776 CCID Smartcard Reader
Bus 007 Device 002: ID 0b97:7761 O2 Micro, Inc. Oz776 1.1 Hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 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 002 Device 003: ID 0b05:4e1f ASUSTek Computer, Inc.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Comments

Popular posts from this blog

A Decade Long Religious Con Job

Ten Reasons to Ignore Ten Reasons to Dump Windows and Use Linux

Former Eclipse user re-evaluates Eclipse 3.3M5