Well, I suggest you check the permissions *and* ownership of /dev/
android.
On my Debian system I used OWNER="username" (not NAME="android").
On my Debian system I also had to use SUBSYSTEMS="usb" (and not
SUBSYSTEM="usb").
Both are critical. The first is because Debian by default will mount
the usb
device (/dev/sdb in my case) owned as user root and group floppy. By
setting
OWNER I make /dev/sdb owned by *me*. That allows adb to detect it
AFAICT.
Second, SUBSYSTEM and SUBSYSTEMS are different. On my Debian system
the G1 device matches "usb" only if you search up from the tree.
Otherwise do a "man udev" to figure it out. If your G1 is being
mounted as
/dev/android consider doing "udevinfo -a -p /block/android" and
examine the output
and have fun.....
As far as I know, the device must be owned by you and readable by you.
The next
step would be to look at the adb source, but I've still got to fetch
that 1.6G source tree.
Cheers!
Shyamal
On Oct 24, 8:07 pm, ______ <[EMAIL PROTECTED]> wrote:
> No joy on Fedora either... the /dev/android link is created but "adb
> devices" doesn't show any devices.
>
> On Oct 24, 1:31 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> wrote:
>
> > just tried this and it doesn't work on ubuntu. i tried it your way and
> > the way on googles site but neither work. the device just keeps being
> > seen as a USB Mass Storage device.
>
> > On Oct 23, 10:23 pm, 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 theudevrules 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
> > > >udevconfig files).
>
> > > > /Shyamal
>
> > > > On Oct 22, 8:20 pm, Wanted unique nickname <[EMAIL PROTECTED]>
> > > > wrote:
>
> > > > > I was able to write the followingudevrule, but running "adbdevices"
> > > > > does not show any device. What doesadblook for when its scanning
> > > > > for devices?
>
> > > > > Here is myrulein /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
> > > > >ruleworks 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
> > > > > > aboutudevto 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
-~----------~----~----~----~------~----~------~--~---
