FYI there is a "better" way to do this than setting the OWNER attribute, by using pam authentication to give the console user r/w perms when the device is plugged in. If anyone is still having probs, try this solution:
https://bugzilla.redhat.com/show_bug.cgi?id=468532 There is more info there that I have been able to glean too about how the whole system works. I filed this as a bug in Fedora's bugzilla so hopefully the G1 will work out-of-the-box with Fedora in the near future. On Oct 25, 4:28 am, ______ <[EMAIL PROTECTED]> wrote: > Same problem on Fedora, with a partial solution: > > Try "ls -l /dev/bus/usb/*" before and after plugging in the device, > and compare that to "ls -l /proc/bus/usb/*" before and after plugging > in. > > Looking through the source code, I noticed adb only scans /dev/bus/ > usb, not /proc/bus/usb. On my Fedora system, the device entry was > being added to /proc/bus/usb/001, but not to /dev/bus/usb/001. This > means hotplug was finding it but udev wasn't, even though with the > NAME=="android" rule the /dev/android device was being created by the > udev rule. There seemed to be several other problems too, such as > having to use ATTRS rather than SYSFS on Fedora, and the fact that the > MODE keyword doesn't even work, meaning that even when I got udev to > create the /dev/bus/usb node correctly, it was owned by root and not > writeable by my user account. As a result I have to manually set > ownership of the device. The final working ruleset I ended up with > is: > > SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0c02", > OWNER="myusername" > > (I'm not sure if the /dev/android symlink is even needed; the adb > source code checks for it in a couple of places but I think it might > be created by thedebuggerwhen a debugging session is initiated?) > > Now my problem is I can see the device using "adb devices", I can take > screenshots and I can initiate debugging sessions in Eclipse -- > although debugging only gets as far as transferring the apk to the > device, and then it says "Waitingfordebuggerto connect". At this > point it sits there indefinitely. Any other ideas? > > On Oct 22, 11:20 pm, Wanted unique nickname <[EMAIL PROTECTED]> > wrote: > > > I was able to write the following udev rule, but running "adb devices" > > does not show any device. What does adb look for when its scanning > > for devices? > > > Here is my rule in /etc/udev/rules.d/11-android.rules > > > SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c02", > > MODE="0666", NAME="android" > > > When I connect the device the /dev/android link is created. So my > > rule works with the device, but I still don't get why adb devices > > returns nothing... little help here? > > > -Marc --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
