[android-developers] Re: ADB via USB
http://forum.xda-developers.com/showthread.php?p=2918876 On Oct 24, 2:06 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Yeah. I'm wating for a x64 driver myself :-\ > > On Oct 23, 12:28 pm, "Declan Shanaghy" <[EMAIL PROTECTED]> wrote: > > > But is the driver x64 compatible? > > > -Original Message- > > From: android-developers@googlegroups.com > > > [mailto:[EMAIL PROTECTED] On Behalf Of plusminus > > Sent: Thursday, October 23, 2008 8:57 AM > > To: Android Developers > > Subject: ***SPAM*** [android-developers] Re: ADB via USB > > > Btw: I've compiled a list of steps to debug on Windows(Vista) with a > > Driver-Download: > > > >http://href.to/Jo5 > > > Regards, plusminushttp://anddev.org > > # Worlds largest Android Development Community / Tutorials > > > On 23 Okt., 11:48, Ed Burnette <[EMAIL PROTECTED]> wrote: > > > I see the doc has been changed to say "Windows (32-bit only)". I tried > > > it on a Win32 (XP) machine and it worked fine. Any tips on how to port > > > the driver to Win64? > > > > On Oct 22, 4:20 pm, Ed Burnette <[EMAIL PROTECTED]> wrote: > > > > > It's not working for me. The device driver won't install, and I get > > > > this error from Vista64: > > > > > Description: > > > > Windows detected a new device attached to your computer, but could > > > > not find the driver software it needs to make the device usable. Each > > > > device manufacturer typically includes driver software of a CD that > > > > comes with the device, or as a download from its website. The hardware > > > > ID of your device is USB\VID_0BB4&PID_0C02&REV_0100&MI_01. > > > > > Problem signature: > > > > Problem Event Name: PnPDriverNotFound > > > > Architecture: x64 > > > > Hardware Id: USB\VID_0BB4&PID_0C02&REV_0100&MI_01 > > > > OS Version: 6.0.6001.2.1.0.256.4 > > > > Locale ID: 1033 > > > > > On Oct 22, 3:03 pm, "Xavier Ducrohet" <[EMAIL PROTECTED]> wrote: > > > > > > Hi Mark, > > > > > > We just updated the doc regarding developing on devices, for all > > platforms. > > > >http://code.google.com/android/intro/develop-and-debug.html#developin... > > > > > > Xav --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
I have a signed release build of a test app, the .apk can be loaded into the emulator and works just fine. When I attempt to load it into a real G1 the box blue-screens immediately and reboot before I can see anything. Details 32-bit Windows XP SP3 Pro ADB can see the device when connected via USB adb install xxx.apk blue screen Any ideas? TIA, mike collins --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
Works fine for me with the daemon running as my usual non-root server. I suspect there's some other issue here. Device permissions maybe? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
I have ubuntu 8.10 and adb from sdk not working for me. I build sdk from source and then it see my phone. Try to copy adb from: http://ironphone.ru/wp-content/uploads/2008/11/adb.tar.gz to your sdk/tools folder. Don't forget to backup old adb file. If it's not working for you, try to build sdk from source. vol: > In a move sure to spark envy, my G1 was delivered today. I wanted to > play with an app I have been developing on my phone, so I plugged in > my USB cable, set the "Debug when USB plugged in" option, and tried to > use adb. No joy. No setting I used seemed to do anything. Is there a > special "allow adb access" command on the G1? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
On Nov 15, 4:56 pm, nt94043 <[EMAIL PROTECTED]> wrote: > Isn't that the exact same set of instructions I'm saying don't work? > I've done all that. There is still a permissions problem unless I run > the adb server as root. Yup; I missed that part of the thread early on. Sorry about that. The steps I listed were the only ones I needed to get this working on an Ubuntu 8.10 system. No clue then why it's different there. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
I can't say for sure that you have the same problem as I had, but it sounds like it. I am running Debian testing with procbususb mounted. To find out if you have procbususb mounted type: mount | grep proc If it is (ie you see procbususb listed), you need the line listed for "Dapper" If you don't you will need the other line for "Gusty/Hardy". I don't see any harm in using both lines (it will match one of them that way) in the android rules file. The root access problem will come from the udev rule not matching, so the device ownership is not adjusted. As a side note, I know that older versions of udev (particularly Red hat Enterprise Linux 4) do not have the same udev support. I think if you copy both lines from the help page into the udev/rules.d/50-android file it should work. If it does not, you may have an older version which uses a separate permissions file. The important things for diagnosing the problem would be the following: distribution (Debian/Ubuntu/Red Hat Enterprise Linux/Fedora/Suse/Gentooetc) udevd --version (udev it the dynamic device node creation system, the rules help setup device access) uname -r (kernel version) mount | grep procbus (using usb_device instead of usb for udev match) Another check is to see if /sys/class/usb_device/ exists. Make sure you reload udev after modifying rules (either sudo /etc/init.d/udev reload or restart) Isn't that the exact same set of instructions I'm saying don't work? > I've done all that. There is still a permissions problem unless I run > the adb server 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 android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
On Nov 14, 12:05 pm, willfe <[EMAIL PROTECTED]> wrote:
> Try creating a file called /etc/udev/rules.d/50-android.rules and
> plugging the following line into it:
>
> SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
>
> Reload udev's configuration (/etc/init.d/udev reload) and try again as
> a normal user.
Isn't that the exact same set of instructions I'm saying don't work?
I've done all that. There is still a permissions problem unless I run
the adb server 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 android-developers@googlegroups.com
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
-~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
Ok, so now I get it, I just had to follow the "Dapper" rule in the adb docs. http://androidcommunity.com/forums/f4/how-to-install-apps-using-adb-4482/ Since my system makes a usb_device, that is the subsystem rule I have to use, instead of usb. I guess Ubuntu removed procbususb in newer versions (I found a lot of reports of VMware failing because of dependency) About the procbususb, to check, run `mount |grep procbus` to see if you have it mounted. So the moral of the story would be to add both rules if you are not sure. That is at least more restrictive than using sudo/root. My personal prefence is to add android group and keep 0664 mode, then add users to adroid group. Thanks for the help. On Sat, Nov 15, 2008 at 9:22 AM, Mark Murphy <[EMAIL PROTECTED]>wrote: > > Dan Pou wrote: > > Whoops, i forgot to mention my kernel version > > Debian 2.6.26-1-amd64 > > Linux 2.6.24-19-generic > > > Out of curiousity, what does udevinfo -q path -n /dev/bus/usb/004/010 > > print? > > It's now 004/011 after having unplugged and replugged the G1 in. > > /devices/pci:00/:00:1d.7/usb4/4-1/4-1.4/4-1.4.3 > > > I am assuming you have procbususb mounted. > > *shrugs shoulders* > > Whatever the Ubuntu 8.04 default is, I suppose. I don't recall fussing > with it. > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
Dan Pou wrote: > Whoops, i forgot to mention my kernel version > Debian 2.6.26-1-amd64 Linux 2.6.24-19-generic > Out of curiousity, what does udevinfo -q path -n /dev/bus/usb/004/010 > print? It's now 004/011 after having unplugged and replugged the G1 in. /devices/pci:00/:00:1d.7/usb4/4-1/4-1.4/4-1.4.3 > I am assuming you have procbususb mounted. *shrugs shoulders* Whatever the Ubuntu 8.04 default is, I suppose. I don't recall fussing with it. -- Mark Murphy (a Commons Guy) http://commonsware.com _The Busy Coder's Guide to Android Development_ Version 1.4 Published! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
> There is no /sys/class/usb_device on Ubuntu 8.04 on my PC. > > Whoops, i forgot to mention my kernel version Debian 2.6.26-1-amd64 We may be running different versions of sysfs - I see the endpoints too, but none of the usbdevX.XX_epXX/dev seem to correlate with the usb_device under my tree. Out of curiousity, what does udevinfo -q path -n /dev/bus/usb/004/010 print? I am assuming you have procbususb mounted. Mine points to the usb_device (it increments every time I plug in). > The closest match to what you're seeking is /sys/class/usb_endpoint, but > then I have five entries of possible relevance: > > usbdev4.10_ep00 > usbdev4.10_ep01 > usbdev4.10_ep02 > usbdev4.10_ep81 > usbdev4.10_ep82 > > > udevd --version reports 125 for me > > 117 here. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
Dan Pou wrote: > There seems to be some problems with udev matching the rules. I don't > seem to get a match looking at `/sbin/udevadm test` on the device. > > Can someone who adb works without root permission copy some output from > these commands? > > udevadm test /sys/class/usb_device/usbdev7.13/ > > where 7.13 is replaced with the results of: > > lsusb |grep 'High Tech' > > (mine says Bus 007 Device 013: ID 0bb4:0c02 High Tech Computer Corp.) There is no /sys/class/usb_device on Ubuntu 8.04 on my PC. The closest match to what you're seeking is /sys/class/usb_endpoint, but then I have five entries of possible relevance: usbdev4.10_ep00 usbdev4.10_ep01 usbdev4.10_ep02 usbdev4.10_ep81 usbdev4.10_ep82 > udevd --version reports 125 for me 117 here. -- Mark Murphy (a Commons Guy) http://commonsware.com Android Training on the Ranch! -- Mar 16-20, 2009 http://www.bignerdranch.com/schedule.shtml --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
There seems to be some problems with udev matching the rules. I don't seem to get a match looking at `/sbin/udevadm test` on the device. Can someone who adb works without root permission copy some output from these commands? udevadm test /sys/class/usb_device/usbdev7.13/ where 7.13 is replaced with the results of: lsusb |grep 'High Tech' (mine says Bus 007 Device 013: ID 0bb4:0c02 High Tech Computer Corp.) udevd --version reports 125 for me The final (problematic line) for me is: udev_node_add: creating device node '/dev/bus/usb/007/013', major=189, minor=780, mode=0664, uid=0, gid=0 rather than 0666. Ideally it would be better to have a udev command with group="android" or something with mode="0664" --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
On Nov 14, 4: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.
Try creating a file called /etc/udev/rules.d/50-android.rules and
plugging the following line into it:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Reload udev's configuration (/etc/init.d/udev reload) and try again as
a normal user.
This is on an Ubuntu 8.10 (Intrepid Ibex) installation (64-bit). Works
fine here after that change. Presumably (given the idVendor tag) this
will only work for the G1.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
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
-~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
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 android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
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 android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
I just had success by adding root. I added the udev rule, restarted udev, killed existing server, sudo ./adb devices. I still get the USB message on the phone though, but HT839GZ26011 appears in devices. On Thu, Nov 13, 2008 at 9:16 PM, nt94043 <[EMAIL PROTECTED]> wrote: > > On Nov 13, 5:12 pm, Mark Murphy <[EMAIL PROTECTED]> wrote: > > Out of curiosity, are you using the original mini-USB cable? I seem to > > recall having a bit of odd behavior when I tried using other, seemingly > > compatible mini-USB cables. > > Yep. However, I'd love to know what exactly the difference is, and > when it matters. That cable is annoyingly short and, of course, I > don't want to have to carry it back and forth with me, so would like > to be able to use a regular mini-usb. With my old HTC devices (8125, > 8925) I pretty much threw the "special" cable in a drawer and did all > my debugging with the same mini-usb cable that worked with most every > other device on the planet these days. Why they gotta be special? > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
On Nov 13, 5:12 pm, Mark Murphy <[EMAIL PROTECTED]> wrote: > Out of curiosity, are you using the original mini-USB cable? I seem to > recall having a bit of odd behavior when I tried using other, seemingly > compatible mini-USB cables. Yep. However, I'd love to know what exactly the difference is, and when it matters. That cable is annoyingly short and, of course, I don't want to have to carry it back and forth with me, so would like to be able to use a regular mini-usb. With my old HTC devices (8125, 8925) I pretty much threw the "special" cable in a drawer and did all my debugging with the same mini-usb cable that worked with most every other device on the planet these days. Why they gotta be special? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
nt94043 wrote: > On Nov 13, 3:23 pm, Mark Murphy <[EMAIL PROTECTED]> wrote: >> You should have Settings > Application Settings > Development > USB >> debugging turned on. That will prevent the question [about mounting the SD >> card] from being asked and >> may clear up your problem. > > I definitely have that setting on, and it definitely does not prevent > the question from being asked. Does that indicate a problem? It's certainly strange. With USB debugging turned on, not only don't I get prompted about mounting the SD card, but the device itself is not mounted, in that the Ubuntu desktop does not try to assign a /media mount to it. Out of curiosity, are you using the original mini-USB cable? I seem to recall having a bit of odd behavior when I tried using other, seemingly compatible mini-USB cables. -- Mark Murphy (a Commons Guy) http://commonsware.com _The Busy Coder's Guide to Android Development_ Version 1.4 Published! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
On Nov 13, 3:23 pm, Mark Murphy <[EMAIL PROTECTED]> wrote: > You should have Settings > Application Settings > Development > USB > debugging turned on. That will prevent the question [about mounting the SD > card] from being asked and > may clear up your problem. I definitely have that setting on, and it definitely does not prevent the question from being asked. Does that indicate a problem? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
nt94043 wrote: > > > On Nov 13, 2:52 pm, Mark Murphy <[EMAIL PROTECTED]> wrote: >> Here was my solution: >> >> 1. Shut down any emulators, DDMSes, Eclispes, or other Android-enabled >> tools. >> 2. Run adb kill-server, reboot, or otherwise get rid of the running adb >> daemon. > > I gave it a shot, but the only thing that changed was the messages > 'adb devices' gives before failing to list any devices: > > $ adb devices > * daemon not running. starting it now * > * daemon started successfully * > List of devices attached > > $ > > Any other ideas? Since upgrading to rc29, my phone now asks me if I > want to mount the sd card on the computer when I usb-plug it. Does it > matter how I answer that question? (I've tried it both ways, but it > would be nice to know so I could reduce the number of permutations I > have to try when trying to get this to work) You should have Settings > Application Settings > Development > USB debugging turned on. That will prevent the question from being asked and may clear up your problem. -- Mark Murphy (a Commons Guy) http://commonsware.com Android Training on the Ranch! -- Mar 16-20, 2009 http://www.bignerdranch.com/schedule.shtml --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
On Nov 13, 2:52 pm, Mark Murphy <[EMAIL PROTECTED]> wrote: > Here was my solution: > > 1. Shut down any emulators, DDMSes, Eclispes, or other Android-enabled > tools. > 2. Run adb kill-server, reboot, or otherwise get rid of the running adb > daemon. I gave it a shot, but the only thing that changed was the messages 'adb devices' gives before failing to list any devices: $ adb devices * daemon not running. starting it now * * daemon started successfully * List of devices attached $ Any other ideas? Since upgrading to rc29, my phone now asks me if I want to mount the sd card on the computer when I usb-plug it. Does it matter how I answer that question? (I've tried it both ways, but it would be nice to know so I could reduce the number of permutations I have to try when trying to get this to work) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
nt94043 wrote: > I've been searching for information on how to troubleshoot "adb > devices" not working > (on ubuntu for me), and am coming up very short. Here was my solution: 1. Shut down any emulators, DDMSes, Eclispes, or other Android-enabled tools. 2. Run adb kill-server, reboot, or otherwise get rid of the running adb daemon. 3. ??? 4. PROFIT! (in other words, steps #1 and #2 were sufficient) Worked for me when I ran into this problem early on. Since then, device recognition has behaved just fine for me (Ubuntu 8.04), recognizing the device within a second or two of it being plugged in. FWIW, I have no /dev/android. -- Mark Murphy (a Commons Guy) http://commonsware.com _The Busy Coder's Guide to Android Development_ Version 1.4 Published! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
I have the same problem (Debian testing/64bit). It was my understanding that this may have something to do with udev marking the device as usb storage and locking out debug bridge. If anyone has any ideas, please share. On Nov 13, 2008 2:06 PM, "nt94043" <[EMAIL PROTECTED]> wrote: On Oct 25, 4:20 pm, "Dan Morrill" <[EMAIL PROTECTED]> wrote: > We are working on a 64-bit build of the ADB driver for Windows. We'll get > it out just as soon as we get it built, tested, and packaged for a release. I've been searching for information on how to troubleshoot "adb devices" not working (on ubuntu for me), and am coming up very short. I see tons of posts from people who say it lists no devices, but no responses from anyone at google about what to do next. Can someone respond? I have the /etc/udev/rules.d/ file created and a /dev/sdb device is being created when I plug in my device, but "adb devices" simply lists nothing. I've found pages theorizing about there needing to be a /dev/android and it needing to be owned by the user who is running adb, but lots of experimentation has turned up nothing. I would like to get cracking with some on-device debugging, but as far as I can tell, it can't be done. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
On Oct 25, 4:20 pm, "Dan Morrill" <[EMAIL PROTECTED]> wrote: > We are working on a 64-bit build of the ADB driver for Windows. We'll get > it out just as soon as we get it built, tested, and packaged for a release. I've been searching for information on how to troubleshoot "adb devices" not working (on ubuntu for me), and am coming up very short. I see tons of posts from people who say it lists no devices, but no responses from anyone at google about what to do next. Can someone respond? I have the /etc/udev/rules.d/ file created and a /dev/sdb device is being created when I plug in my device, but "adb devices" simply lists nothing. I've found pages theorizing about there needing to be a /dev/android and it needing to be owned by the user who is running adb, but lots of experimentation has turned up nothing. I would like to get cracking with some on-device debugging, but as far as I can tell, it can't be done. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
We are working on a 64-bit build of the ADB driver for Windows. We'll get it out just as soon as we get it built, tested, and packaged for a release. - Dan On Sat, Oct 25, 2008 at 10:15 AM, Vince Castellano <[EMAIL PROTECTED]>wrote: > > On Oct 24, 12:06 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > Yeah. I'm wating for a x64 driver myself :-\ > > > > On Oct 23, 12:28 pm, "Declan Shanaghy" <[EMAIL PROTECTED]> wrote: > > > > > But is the driver x64 compatible? > > > > Same problem here, wish there was a way to ping google on this so that > they can see it as more people needing this. In the mean time, > virtualbox with Ubuntu will work, though it's hardly an optimal > solution. > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
On Oct 24, 12:06 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Yeah. I'm wating for a x64 driver myself :-\ > > On Oct 23, 12:28 pm, "Declan Shanaghy" <[EMAIL PROTECTED]> wrote: > > > But is the driver x64 compatible? > Same problem here, wish there was a way to ping google on this so that they can see it as more people needing this. In the mean time, virtualbox with Ubuntu will work, though it's hardly an optimal solution. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
Yeah. I'm wating for a x64 driver myself :-\ On Oct 23, 12:28 pm, "Declan Shanaghy" <[EMAIL PROTECTED]> wrote: > But is the driver x64 compatible? > > -Original Message- > From: android-developers@googlegroups.com > > [mailto:[EMAIL PROTECTED] On Behalf Of plusminus > Sent: Thursday, October 23, 2008 8:57 AM > To: Android Developers > Subject: ***SPAM*** [android-developers] Re: ADB via USB > > Btw: I've compiled a list of steps to debug on Windows(Vista) with a > Driver-Download: > > >http://href.to/Jo5 > > Regards, plusminushttp://anddev.org > # Worlds largest Android Development Community / Tutorials > > On 23 Okt., 11:48, Ed Burnette <[EMAIL PROTECTED]> wrote: > > I see the doc has been changed to say "Windows (32-bit only)". I tried > > it on a Win32 (XP) machine and it worked fine. Any tips on how to port > > the driver to Win64? > > > On Oct 22, 4:20 pm, Ed Burnette <[EMAIL PROTECTED]> wrote: > > > > It's not working for me. The device driver won't install, and I get > > > this error from Vista64: > > > > Description: > > > Windows detected a new device attached to your computer, but could > > > not find the driver software it needs to make the device usable. Each > > > device manufacturer typically includes driver software of a CD that > > > comes with the device, or as a download from its website. The hardware > > > ID of your device is USB\VID_0BB4&PID_0C02&REV_0100&MI_01. > > > > Problem signature: > > > Problem Event Name: PnPDriverNotFound > > > Architecture: x64 > > > Hardware Id: USB\VID_0BB4&PID_0C02&REV_0100&MI_01 > > > OS Version: 6.0.6001.2.1.0.256.4 > > > Locale ID: 1033 > > > > On Oct 22, 3:03 pm, "Xavier Ducrohet" <[EMAIL PROTECTED]> wrote: > > > > > Hi Mark, > > > > > We just updated the doc regarding developing on devices, for all > platforms. > > >http://code.google.com/android/intro/develop-and-debug.html#developin... > > > > > Xav --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
But is the driver x64 compatible? -Original Message- From: android-developers@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of plusminus Sent: Thursday, October 23, 2008 8:57 AM To: Android Developers Subject: ***SPAM*** [android-developers] Re: ADB via USB Btw: I've compiled a list of steps to debug on Windows(Vista) with a Driver-Download: > http://href.to/Jo5 Regards, plusminus http://anddev.org # Worlds largest Android Development Community / Tutorials On 23 Okt., 11:48, Ed Burnette <[EMAIL PROTECTED]> wrote: > I see the doc has been changed to say "Windows (32-bit only)". I tried > it on a Win32 (XP) machine and it worked fine. Any tips on how to port > the driver to Win64? > > On Oct 22, 4:20 pm, Ed Burnette <[EMAIL PROTECTED]> wrote: > > > It's not working for me. The device driver won't install, and I get > > this error from Vista64: > > > Description: > > Windows detected a new device attached to your computer, but could > > not find the driver software it needs to make the device usable. Each > > device manufacturer typically includes driver software of a CD that > > comes with the device, or as a download from its website. The hardware > > ID of your device is USB\VID_0BB4&PID_0C02&REV_0100&MI_01. > > > Problem signature: > > Problem Event Name: PnPDriverNotFound > > Architecture: x64 > > Hardware Id: USB\VID_0BB4&PID_0C02&REV_0100&MI_01 > > OS Version: 6.0.6001.2.1.0.256.4 > > Locale ID: 1033 > > > On Oct 22, 3:03 pm, "Xavier Ducrohet" <[EMAIL PROTECTED]> wrote: > > > > Hi Mark, > > > > We just updated the doc regarding developing on devices, for all platforms. > > > >http://code.google.com/android/intro/develop-and-debug.html#developin... > > > > Xav > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
Btw: I've compiled a list of steps to debug on Windows(Vista) with a Driver-Download: > http://href.to/Jo5 Regards, plusminus http://anddev.org # Worlds largest Android Development Community / Tutorials On 23 Okt., 11:48, Ed Burnette <[EMAIL PROTECTED]> wrote: > I see the doc has been changed to say "Windows (32-bit only)". I tried > it on a Win32 (XP) machine and it worked fine. Any tips on how to port > the driver to Win64? > > On Oct 22, 4:20 pm, Ed Burnette <[EMAIL PROTECTED]> wrote: > > > It's not working for me. The device driver won't install, and I get > > this error from Vista64: > > > Description: > > Windows detected a new device attached to your computer, but could > > not find the driver software it needs to make the device usable. Each > > device manufacturer typically includes driver software of a CD that > > comes with the device, or as a download from its website. The hardware > > ID of your device is USB\VID_0BB4&PID_0C02&REV_0100&MI_01. > > > Problem signature: > > Problem Event Name: PnPDriverNotFound > > Architecture: x64 > > Hardware Id: USB\VID_0BB4&PID_0C02&REV_0100&MI_01 > > OS Version: 6.0.6001.2.1.0.256.4 > > Locale ID: 1033 > > > On Oct 22, 3:03 pm, "Xavier Ducrohet" <[EMAIL PROTECTED]> wrote: > > > > Hi Mark, > > > > We just updated the doc regarding developing on devices, for all > > > platforms. > > > >http://code.google.com/android/intro/develop-and-debug.html#developin... > > > > Xav > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
I see the doc has been changed to say "Windows (32-bit only)". I tried it on a Win32 (XP) machine and it worked fine. Any tips on how to port the driver to Win64? On Oct 22, 4:20 pm, Ed Burnette <[EMAIL PROTECTED]> wrote: > It's not working for me. The device driver won't install, and I get > this error from Vista64: > > Description: > Windows detected a new device attached to your computer, but could > not find the driver software it needs to make the device usable. Each > device manufacturer typically includes driver software of a CD that > comes with the device, or as a download from its website. The hardware > ID of your device is USB\VID_0BB4&PID_0C02&REV_0100&MI_01. > > Problem signature: > Problem Event Name: PnPDriverNotFound > Architecture: x64 > Hardware Id: USB\VID_0BB4&PID_0C02&REV_0100&MI_01 > OS Version: 6.0.6001.2.1.0.256.4 > Locale ID: 1033 > > On Oct 22, 3:03 pm, "Xavier Ducrohet" <[EMAIL PROTECTED]> wrote: > > > Hi Mark, > > > We just updated the doc regarding developing on devices, for all platforms. > > >http://code.google.com/android/intro/develop-and-debug.html#developin... > > > Xav --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
I work in Gentoo, and I don't automount any USB device. Oddly, accessing the G1 was surprisingly easy. I created a directory in my home and mounted: sudo mount /dev/sdb ~/g1 ls ~/g1 showed the folders on the SD card. I found it odd that the mountpoint was actually sdb as opposed to sdb1 or something like that. Using adb to list devices showed the G1 connected. From there, I could interface with it just as I would the emulator. Not sure if this will help anyone using other distros or Windows, but I figure I'll drop it here anyway just in case. On Oct 22, 4:20 pm, Ed Burnette <[EMAIL PROTECTED]> wrote: > It's not working for me. The device driver won't install, and I get > this error from Vista64: > > Description: > Windows detected a new device attached to your computer, but could > not find the driver software it needs to make the device usable. Each > device manufacturer typically includes driver software of a CD that > comes with the device, or as a download from its website. The hardware > ID of your device is USB\VID_0BB4&PID_0C02&REV_0100&MI_01. > > Problem signature: > Problem Event Name: PnPDriverNotFound > Architecture: x64 > Hardware Id: USB\VID_0BB4&PID_0C02&REV_0100&MI_01 > OS Version: 6.0.6001.2.1.0.256.4 > Locale ID: 1033 > > On Oct 22, 3:03 pm, "Xavier Ducrohet" <[EMAIL PROTECTED]> wrote: > > > Hi Mark, > > > We just updated the doc regarding developing on devices, for all platforms. > > >http://code.google.com/android/intro/develop-and-debug.html#developin... > > > Xav --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
It's not working for me. The device driver won't install, and I get this error from Vista64: Description: Windows detected a new device attached to your computer, but could not find the driver software it needs to make the device usable. Each device manufacturer typically includes driver software of a CD that comes with the device, or as a download from its website. The hardware ID of your device is USB\VID_0BB4&PID_0C02&REV_0100&MI_01. Problem signature: Problem Event Name: PnPDriverNotFound Architecture: x64 Hardware Id: USB\VID_0BB4&PID_0C02&REV_0100&MI_01 OS Version: 6.0.6001.2.1.0.256.4 Locale ID:1033 On Oct 22, 3:03 pm, "Xavier Ducrohet" <[EMAIL PROTECTED]> wrote: > Hi Mark, > > We just updated the doc regarding developing on devices, for all platforms. > > http://code.google.com/android/intro/develop-and-debug.html#developin... > > Xav > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
Hi Mark, We just updated the doc regarding developing on devices, for all platforms. http://code.google.com/android/intro/develop-and-debug.html#developingondevicehardware Xav On Wed, Oct 22, 2008 at 9:16 AM, Mark Murphy <[EMAIL PROTECTED]> wrote: > > Xavier Ducrohet wrote: >> Developing on a device is very similar to using the emulator. >> Once you have enabled USB debugging in your device, it'll just work, >> as adb and DDMS will see your device. > > I'm in the same boat as the OP. Here are details: > > On the G1, I have "USB debugging" and "Stay awake" both checked. I also > have the "Use for USB storage" option unchecked, though I've tried it > both ways. > > I plug the G1 into my Ubuntu 8.04 machine via a powered USB hub, and it > is recognized: > > Oct 22 12:07:51 nc8000 kernel: [1073867.494452] usb 4-1.4.3: new high > speed USB device using ehci_hcd and address 19 > Oct 22 12:07:51 nc8000 kernel: [1073867.627427] usb 4-1.4.3: > configuration #1 chosen from 1 choice > Oct 22 12:07:51 nc8000 kernel: [378864.537868] scsi9 : SCSI emulation > for USB Mass Storage devices > Oct 22 12:07:56 nc8000 kernel: [1073876.329063] scsi 9:0:0:0: > Direct-Access HTC Android Phone0100 PQ: 0 ANSI: 2 > Oct 22 12:07:57 nc8000 kernel: [1073876.345904] sd 9:0:0:0: [sdc] > Attached SCSI removable disk > Oct 22 12:07:57 nc8000 kernel: [1073876.346023] sd 9:0:0:0: Attached > scsi generic sg3 type 0 > > But I get no love from adb: > > [EMAIL PROTECTED]:~$ adb devices > List of devices attached > emulator-5554 device > > It shows my running emulator instance and nothing else. > > If I close up the emulator and try the steps all over again: > > [EMAIL PROTECTED]:~$ adb devices > List of devices attached > > What's curious is that I don't get "no device" per the instructions. I > also see no sign of it via lspci -v or lspci -vv. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com > > Android Training on the Ranch! -- Mar 16-20, 2009 > http://www.bignerdranch.com/schedule.shtml > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
Xavier Ducrohet wrote: > Developing on a device is very similar to using the emulator. > Once you have enabled USB debugging in your device, it'll just work, > as adb and DDMS will see your device. I'm in the same boat as the OP. Here are details: On the G1, I have "USB debugging" and "Stay awake" both checked. I also have the "Use for USB storage" option unchecked, though I've tried it both ways. I plug the G1 into my Ubuntu 8.04 machine via a powered USB hub, and it is recognized: Oct 22 12:07:51 nc8000 kernel: [1073867.494452] usb 4-1.4.3: new high speed USB device using ehci_hcd and address 19 Oct 22 12:07:51 nc8000 kernel: [1073867.627427] usb 4-1.4.3: configuration #1 chosen from 1 choice Oct 22 12:07:51 nc8000 kernel: [378864.537868] scsi9 : SCSI emulation for USB Mass Storage devices Oct 22 12:07:56 nc8000 kernel: [1073876.329063] scsi 9:0:0:0: Direct-Access HTC Android Phone0100 PQ: 0 ANSI: 2 Oct 22 12:07:57 nc8000 kernel: [1073876.345904] sd 9:0:0:0: [sdc] Attached SCSI removable disk Oct 22 12:07:57 nc8000 kernel: [1073876.346023] sd 9:0:0:0: Attached scsi generic sg3 type 0 But I get no love from adb: [EMAIL PROTECTED]:~$ adb devices List of devices attached emulator-5554 device It shows my running emulator instance and nothing else. If I close up the emulator and try the steps all over again: [EMAIL PROTECTED]:~$ adb devices List of devices attached What's curious is that I don't get "no device" per the instructions. I also see no sign of it via lspci -v or lspci -vv. -- Mark Murphy (a Commons Guy) http://commonsware.com Android Training on the Ranch! -- Mar 16-20, 2009 http://www.bignerdranch.com/schedule.shtml --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
Hi, the USB driver for windows is available at: http://dl.google.com/android/android_usb_windows.zip We'll be posting more information tomorrow, but it's pretty straight forward. Download, unarchive and then point the new hardware wizard to the driver folder. Developing on a device is very similar to using the emulator. Once you have enabled USB debugging in your device, it'll just work, as adb and DDMS will see your device. Make sure you set the debuggable attribute (in the application node) to true in the manifest so that you can debug your application. Xav On Tue, Oct 21, 2008 at 7:48 PM, marstein <[EMAIL PROTECTED]> wrote: > > I am running Vista, and when I enable the Application/Development/USB > debugging setting, the 'found new hardware' dialog comes up and cannot > find a driver. I assume this is the reason why 'adb devices' does not > give any results. Sigh. > > What I would like to see is instructions how to get the G1 attached to > a Vista development machine (which device drivers to install, commands > to issue so that the docs section on adb works), and then how to make > it all work in Eclipse. So I can Run a program on the device, not the > emulator. > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
I am running Vista, and when I enable the Application/Development/USB debugging setting, the 'found new hardware' dialog comes up and cannot find a driver. I assume this is the reason why 'adb devices' does not give any results. Sigh. What I would like to see is instructions how to get the G1 attached to a Vista development machine (which device drivers to install, commands to issue so that the docs section on adb works), and then how to make it all work in Eclipse. So I can Run a program on the device, not the emulator. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
Hey, you can try lsusb or lsusb -v -v to see what android has attached as, but it's not going to be storage. It's probably network or serial though. -- tmzt on #htc-linux on irc.freenode.org --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
[android-developers] Re: ADB via USB
Actually, to clarify, I'm using ubuntu 8.04. I tried adb -d shell, adb -p /dev/sdb shell, adb shell. Android automounted on /dev/sdb, though when I specified debug mode it seemed to unmount itself. On Oct 20, 8:09 pm, vol <[EMAIL PROTECTED]> wrote: > In a move sure to spark envy, my G1 was delivered today. I wanted to > play with an app I have been developing on my phone, so I plugged in > my USB cable, set the "Debug when USB plugged in" option, and tried to > use adb. No joy. No setting I used seemed to do anything. Is there a > special "allow adb access" command on the G1? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~--~~~~--~~--~--~---
