An android-developers thread at http://groups.google.com/group/android-developers/browse_thread/thread/af53210a9c41ec37/a0abc58971a44ac0?pli=1 suggests:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
which is the same as the one in comment #10 but seems too broad, both in the devices matched and in the permissions granted.
Based on the examples I see in the default rules, I think what is probably needed is:
1. A set of rules which match the appropriate USB devices and identify them as Android devices, e.g.:
ATTRS{idVendor}=="0bb4" , ATTRS{idProduct}=="0c02" , ENV{ID_...}="..."
2. A rule which then sets permissions based on the ID_... value, perhaps in 70-acl.rules, e.g.:
ENV{ID_...}=="...", ENV{ACL_MANAGE}="1"
I'm not intimately familiar with this, though, and would appreciate guidance on whether this is the Right Way to Do It now.
An android-developers thread at http:// groups. google. com/group/ android- developers/ browse_ thread/ thread/ af53210a9c41ec3 7/a0abc58971a44 ac0?pli= 1 suggests:
SUBSYSTEM=="usb", SYSFS{idVendor} =="0bb4" , MODE="0666"
which is the same as the one in comment #10 but seems too broad, both in the devices matched and in the permissions granted.
Based on the examples I see in the default rules, I think what is probably needed is:
1. A set of rules which match the appropriate USB devices and identify them as Android devices, e.g.:
ATTRS{idVendor} =="0bb4" , ATTRS{idProduct }=="0c02" , ENV{ID_...}="..."
2. A rule which then sets permissions based on the ID_... value, perhaps in 70-acl.rules, e.g.:
ENV{ID_...}=="...", ENV{ACL_MANAGE}="1"
I'm not intimately familiar with this, though, and would appreciate guidance on whether this is the Right Way to Do It now.