Re: [Chrome DevTools] Can't find device, missing a step?

[Sam Dutton]

You might want to try a different USB cable -- I think some are power only. 

And, just to check, you might want to double check you followed all the steps in https://developers.google.com/chrome-developer-tools/docs/remote-debugging.

Sam

On 8 February 2013 15:47, Corey Megown <corey....@gmail.com> wrote:

Hi everyone, first attempt at using remote debugger so please bear with me :)

Here are the exact steps in which I did things, but I still cannot get any devices listed via command line:

1. Downloaded Android SDK
2. Unzipped into Downloads directory
3. Opened command line, traversed to: C:\Users\[name]\Downloads\adt-bundle-windows-x86_64\adt-bundle-windows-x86_64\sdk\platform-tools
4. Ran command 'adb devices'
5. Result: "List of devices attached" (nothing displayed after that)

Before anyone asks:

1. Yes I have USB debugging turned on on my phone
2. Yes I have USB debugging turned on in Chrome for Android.
   
3. Yes my device is connected via USB to my machine.

Any feedback and/or tips are greatly appreciated! I'd be very interested in learning how to utilize remote debugging for my mobile projects in the future.

Thanks!

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Mikhail Naganov]

Hi Corey,

What device are you using, and what version of Android is on it?

You can try googling "adb empty list of devices windows" for getting an endless source of suggestions.

[Corey Megown]

@Sam Dutton I am using the micro-USB cable that came with my phone, so I'll definitely give another cable a go. Thanks for posting that link, but that's where I was getting my instructions from originally. I'll post back once I have a chance to try a different cable!

@Mikhail Naganov I've got a Droid Razr running Android 4.0.4. I'll try search for that after trying a different power cable as Sam mentioned.

Thanks for your suggestions guys!

To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.

[Corey Megown]

Turns out it wasn't my cable, but instead it was that certain drivers weren't being installed like they should. Someone suggested downloading PdaNet+, and sure enough I was able to get my device to show up via 'adb devices' right away. So as far as this post is concerned the issue is resolved.

Technically it's not, since we discovered an internal bug through this, but thank you so much for your help guys! Really appreciated!

[Mikhail Naganov]

Sorry, I didn't find this article initially, but yes, for development under Windows, you need an OEM-provided USB driver: http://developer.android.com/tools/extras/oem-usb.html

--

You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.

[jaredwilli]

I've got this same problem only I have been using pdanet all along and now it no longer works for me. I've tried all things I can imagine to get it to work again. It charges still but doesn't see the device no matter what I do.

Uninstalled and installed all things did factory reset did recovery did try multiple usb plugs and ports and computers. What is the issue here exactly anyone know??