this is probably a permission problem. I don't have the specifics, but I assume that it should be possible to allow a given user/group to access the device by changing the udev rules (which must be done as root though)
On Fri, Nov 14, 2008 at 10:20 AM, nt94043 <[EMAIL PROTECTED]> wrote: > > On Nov 13, 8:13 pm, "Dan Pou" <[EMAIL PROTECTED]> wrote: > > I just had success by adding root. > > > > I added the udev rule, restarted udev, killed existing server, sudo ./adb > > devices. > > Ok, I didn't know what you mean by "adding root", but this gave me a > clue that got things working, sort of: > If I kill the server (adb kill-server) and then run one "adb devices" > query as root, it starts up the server as root and from then on, until > I kill the server again, I can run "adb devices" as a normal user and > it seems to communicate with the root-level process via a socket to do > its business. > > Someone at Android: This is wrong, right? Please tell me you don't > actually expect me to run this dev tool as root. Give me proper > documentation about what it needs permissions to and I'll be happy to > set it all up, but I'm not planning to run it as root. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
