It's probably a matter of permissions on the device file. The examples for Ubuntu specify MODE=”0666″, perhaps there is a way to do this in Debian as well. Then you won't have to start adb as root (althogh it should be harmless, it's an extra step).
-- Kostya 2011/2/19 ydm <[email protected]> > You're great! Thank you! Now it works! > > On Feb 19, 4:55 pm, Alessandro Pellizzari <[email protected]> wrote: > > On Sat, 19 Feb 2011 05:03:00 -0800, ydm wrote: > > > $ ./adb devices > > > * daemon not running. starting it now on port 5037 * * daemon started > > > successfully * > > > List of devices attached > > > ???????????? no permissions > > > > I also tried creating udev rules bot got nowhere. > > > > I now initialise adb server as root: > > > > # adb start-server > > > > then work as user: > > > > $ adb devices > > > > Bye. > > -- > 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 > -- 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
