I was also able to get adb to see my devices as a normal user, but with a small quirk. Note: I am using Ubuntu Gutsy (7.10).
I have written it up here: http://william.quartz.googlepages.com/mobile%3Agoogleg1 But basically, I have to start the adb deamon a certain way, as follows: kill server if running, then "sudo adb devices". After doing some research it appears that while adb is starting, if you ask it to find devices while it is forking, it can find them because the forker is still running under the same id that is forking the server. But, if I use the sequence: "sudo adb start-server", then "sudo adb devices", it can't find any. I am not sure why but it works. * daemon not running. starting it now * * daemon started successfully * List of devices attached HT846GZ40581 device So basically, I make sure the deamon isn't running, then I do "sudo adb devices". Weird, but it works. Hmmm... On Nov 17 2008, 10:19 pm, Chris Jordan <[email protected]> wrote: > Thanks Marc! > > That worked for me on Fedora 6. The only thing I had to do different > was: > > adb kill-server > adb start-server > > Thanks again, > > -Chris > > On Oct 24, 12:23 am, Wanted unique nickname <[email protected]> > wrote: > > > Wow, that totally worked. For those who are interested, here is my > > complete Suse example: > > > Before you connect the g1 via usb > > > [create the udev rules file, and choose a number lower than the > > default rules file] > > /etc/udev/rules.d/11-android.rules > > > [copy the following text to that file, and replace "username", all one > > line] > > SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c02", > > MODE="0666", NAME="username" > > > [start the adb daemon] > > adb > > * daemon not running. starting it now * > > * daemon started successfully * > > > [connect the phone, and check devices] > > adb devices > > HT840GZ14538 device > > > -Marc > > > On Oct 23, 5:09 pm, shyamal <[email protected]> wrote: > > > > It seems that the device needs to be owned by the user running 'adb'. > > > At a first approximation anyway; I've worked on Android for a full > > > three days or something..... Adding OWNER='yourusername' should fix > > > it. > > > > Works for me on a Debian (Testing) system where I mount it to to /dev/ > > > sdb (though I had to use SUBSYSTEMS, not SUBSYSTEM, with the default > > > udev config files). > > > > /Shyamal > > > > On Oct 22, 8:20 pm, Wanted unique nickname <[email protected]> > > > wrote: > > > > > I was able to write the following udev rule, but running "adbdevices" > > > > does not show any device. What doesadblook 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 whyadbdevices > > > > returns nothing... little help here? > > > > > -Marc > > > > > On Oct 22, 7:33 pm, Wanted unique nickname <[email protected]> > > > > wrote: > > > > > > Does anyone know how to perform Step 3 for developing on SuseLinux? > > > > > When I run dmesg I get some relevant info, but I don't know enough > > > > > about udev to make this work on Suse... > > > > > > usb 1-10: new high speed USB device using ehci_hcd and address 10 > > > > > usb 1-10: new device found, idVendor=0bb4, idProduct=0c02 > > > > > usb 1-10: new device strings: Mfr=3, Product=2, SerialNumber=1 > > > > > usb 1-10: Product: Android Phone > > > > > usb 1-10: Manufacturer: HTC > > > > > usb 1-10: SerialNumber: HT840GZ14538 > > > > > usb 1-10: configuration #1 chosen from 1 choice > > > > > scsi18 : SCSI emulation for USB Mass Storage devices > > > > > usb-storage: device found at 10 > > > > > usb-storage: waiting for device to settle before scanning > > > > > scsi 18:0:0:0: Direct-Access HTC Android Phone 0100 PQ: 0 > > > > > ANSI: 2 > > > > > sd 18:0:0:0: [sdc] Attached SCSI removable disk > > > > > sd 18:0:0:0: Attached scsi generic sg4 type 0 > > > > > usb-storage: device scan complete > > > > > > -Marc > > > > > > On Oct 22, 12:02 pm, "Xavier Ducrohet" <[email protected]> wrote: > > > > > > > We just updated the documentation. > > > > > > > Developing on devices is explained > > > > > > here:http://code.google.com/android/intro/develop-and-debug.html#developin... > > > > > > > On Tue, Oct 21, 2008 at 11:45 PM, bhines <[email protected]> wrote: > > > > > > > > this sounds like my problem as well. > > > > > > > > This really should be mentioned > > > > > > > onhttp://code.google.com/android/intro/develop-and-debug.html > > > > > > > > thanks, > > > > > > > > -Ben > > > > > > > > On Oct 21, 8:42 pm, nkijak <[email protected]> wrote: > > > > > > >> That possibly did the trick. I had to restart the phone. Maybe > > > > > > >> for > > > > > > >> the "Debug when USB" thing to take effect? > > > > > > > >> Thanks > > > > > > > >> On Oct 21, 11:33 pm, "Xavier Ducrohet" <[email protected]> wrote: > > > > > > > >> > To debug on devices you need to set the 'debuggable' attribute > > > > > > >> > of the > > > > > > >> > application node to true (in AndroidManifest.xml). > > > > > > > >> > Make sure to set it back to false before releasing your > > > > > > >> > application. > > > > > > > >> > Xav > > > > > > > >> > On Tue, Oct 21, 2008 at 8:24 PM, nkijak <[email protected]> > > > > > > >> > wrote: > > > > > > > >> > > I can't seem to get the eclipse debugger to attach to theG1. > > > > > > >> > > I can > > > > > > >> > > select "Debug" from the run menu and it will compile and > > > > > > >> > > launch the > > > > > > >> > > app on the phone but eclipse never enters the debug > > > > > > >> > > perspective (or > > > > > > >> > > even asks to). The phone sits with a "Waiting for Debugger" > > > > > > >> > > message > > > > > > >> > > dialog. > > > > > > >> > > When I enter the Android perspective I can see the device > > > > > > >> > > attached, > > > > > > >> > > see log entries, take screenshots but I cannot see process > > > > > > >> > > listings > > > > > > >> > > and "restartingadb" results in 11 failed attempts to connect. > > > > > > >> > > Is there some other configuration I need to adjust in > > > > > > >> > > eclipse, perhaps > > > > > > >> > > a port number? > > > > > > > >> > > Thanks, > > > > > > >> > > Nick --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
