There does not appear to be another udev rules file starting with 50 in Ubuntu Jaunty.
I did find a workaround that works: Remove (or comment-out) the udev rule, and set permissions on adb to run as root. Rebooted, and now "adb devices" results in... * daemon not running. starting it now * * daemon started successfully * List of devices attached HT91RLZ01056 device ...I just got this result moments ago, so I have not checked that everything depending on this functions correctly, but it's progress relative to where I was. On Apr 15, 4:03 pm, David Turner <[email protected]> wrote: > I believe there is a conflict in latest versions of Ubuntu, try to rename > your 50-android-something > rule file to 51-android-something, because Ubuntu recently added another > 50-something file that > appears to be resetting/overriding the definitions here. > > Let us know if this works. > > On Wed, Apr 15, 2009 at 9:56 PM, Zigurd <[email protected]> wrote: > > > Trying to get an Ubuntu Jaunty system to talk to a dev phone. I have > > the 1.5 sdk and the new master branch of the sources. > > > If I change the udev rules to: > > > SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666" > > > ...I'm able to mount the memory card and read and write to it. But the > > command: > > > adb devices > > > ...shows only the emulator (so adb appears to work with the new sdk), > > but not the handset. > > > Any ideas? > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
