Debugging the new T-Mobile G1 Android phone over a USB transport
doesn't work out of the box on Linux, because udev does not
automatically create a device node for the phone in
/dev/bus/usb/###/### when the phone is plugged in. Interestingly, the
correct entry is created in /proc/bus/usb by hotplug, and the phone
works fine as a mass storage device, but as adb (the Android debugger)
scans through /dev/bus/usb for Android devices, it does not detect the
phone by default.
Adding the following rule causes the device node to be created:
SUBSYSTEM=="usb",ATTR{idVendor}=="0bb4",ATTR{idProduct}=="0c02"
Why would this rule need to be added for the device node to be
created? Shouldn't udev just create the device node even if it
doesn't recognize the device?
The above rule doesn't give the console user the needed r/w perms on
the device, this will still need to be handled by ConsoleKit or
similar.
Somehow generically fixing this upstream would be very helpful as
(based on various G1 dev forums) the exact udev rule needed to get
this working seems to vary across distributions.
Thanks!
Luke Hutchison
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
