Nexus 7 not visible to adb over usb (WIndows 7 x64, up to date Jelly Bean sdk)

Showing 1-6 of 6 messages
Nexus 7 not visible to adb over usb (WIndows 7 x64, up to date Jelly Bean sdk) mkh 8/10/12 8:39 AM
Trying to force feed myself Windows to build character, and the seemly trivial thing of plugging in a Nexus 7 to a Dell xps 15z Tand debugging a "hello world" app on it from Eclipse Juno with the latest ADT plugin has me stumped.

Developer options were turned on, and USB debugging enabled.

The device just does not show up, not in Eclipse, or in "adb devices".

The first time I had not installed the USB driver from the sdk. In this case the Nexus 7 shows up in the WIndows devices under "Portable Devices" and a filesystem can be browsed from Windows.

Next I installed the google USB driver. Now the Nexus 7 shows up in the Windows devices as "Android Phone"/"Android composite ADB interface", and at that point I thought I was moments away from looking at "Hello World" and moving on to something interesting, but wait, there's more, adb remained blind to the Nexus7.

Any ideas, or suggestions for debugging this problem would be appreciated...

Re: Nexus 7 not visible to adb over usb (WIndows 7 x64, up to date Jelly Bean sdk) goodG 8/10/12 10:18 AM
http://support.asus.com/download/ModelList.aspx?SLanguage=en&keyword=nexus%207&type=1

my personal advice is just to avoid programming on Windows, it's a nightmare.
Re: Nexus 7 not visible to adb over usb (WIndows 7 x64, up to date Jelly Bean sdk) mkh 8/11/12 8:23 AM
The driver there appears to be the same as the one in the android SDK. I installed it anyway, and the result is the same -- 

PS C:\Users\mkh\AppData\Local\Android\android-sdk\platform-tools> $env:ADB_TRACE='all'
PS C:\Users\mkh\AppData\Local\Android\android-sdk\platform-tools> $env:ADB_TRACE
all
PS C:\Users\mkh\AppData\Local\Android\android-sdk\platform-tools> ./adb devices
system/core/adb/adb.c::main():Handling commandline()
system/core/adb/adb_client.c::adb_query():adb_query: host:devices
system/core/adb/adb_client.c::_adb_connect():_adb_connect: host:version
system/core/adb/sysdeps_win32.c::socket_loopback_client():socket_loopback_client: port 5037 type tcp => fd 100
system/core/adb/transport.c::writex():writex: fd=100 len=4: 30303063 000c
system/core/adb/transport.c::writex():writex: fd=100 len=12: 686f73743a76657273696f6e host:version
system/core/adb/transport.c::readx():readx: fd=100 wanted=4
system/core/adb/transport.c::readx():readx: fd=100 wanted=4 got=4
4f4b4159 OKAY
system/core/adb/adb_client.c::_adb_connect():_adb_connect: return fd 100
system/core/adb/adb_client.c::adb_connect():adb_connect: service host:devices
system/core/adb/transport.c::readx():readx: fd=100 wanted=4
system/core/adb/transport.c::readx():readx: fd=100 wanted=4 got=4
30303034 0004
system/core/adb/transport.c::readx():readx: fd=100 wanted=4
system/core/adb/transport.c::readx():readx: fd=100 wanted=4 got=4
30303164 001d
system/core/adb/sysdeps_win32.c::adb_close():adb_close: 100(lo-client:5037)
system/core/adb/adb_client.c::_adb_connect():_adb_connect: host:devices
system/core/adb/sysdeps_win32.c::socket_loopback_client():socket_loopback_client: port 5037 type tcp => fd 101
system/core/adb/transport.c::writex():writex: fd=101 len=4: 30303063 000c
system/core/adb/transport.c::writex():writex: fd=101 len=12: 686f73743a64657669636573 host:devices
system/core/adb/transport.c::readx():readx: fd=101 wanted=4
system/core/adb/transport.c::readx():readx: fd=101 wanted=4 got=4
4f4b4159 OKAY
system/core/adb/adb_client.c::_adb_connect():_adb_connect: return fd 101
system/core/adb/adb_client.c::adb_connect():adb_connect: return fd 101
system/core/adb/transport.c::readx():readx: fd=101 wanted=4
system/core/adb/transport.c::readx():readx: fd=101 wanted=4 got=4
30303030 0000
system/core/adb/transport.c::readx():readx: fd=101 wanted=0
system/core/adb/transport.c::readx():readx: fd=101 wanted=0 got=0

system/core/adb/sysdeps_win32.c::adb_close():adb_close: 101(lo-client:5037)
List of devices attached

PS C:\Users\mkh\AppData\Local\Android\android-sdk\platform-tools>
Re: Nexus 7 not visible to adb over usb (WIndows 7 x64, up to date Jelly Bean sdk) mkh 8/16/12 9:15 AM
I'm happy to answer my own question.

1) Can't blame Windows!

2) When the Nexus 7 is plugged in there is a persistent notification that indicates "CONNECT AS / Media Device (MTP)". In this state adb devices will not show the Nexus. Not exactly obvious why, but I you select the second option "Camera (PTP)" the device is available for debugging. This choice is persistent, and I'm guessing that with a band new device it will connect as MTP until told otherwise.
Re: Nexus 7 not visible to adb over usb (WIndows 7 x64, up to date Jelly Bean sdk) Compguru910 8/23/12 6:12 AM
In MTP my Nexus 7 displays just fine. What I think you are having a problem with is the actual driver for the Nexus 7. What I had to do was install the Google USB driver for it, instead of the Asus one because it has adb problems. If you want I can send you the driver and screenshot of mine working in MTP mode.
Michal Mlynarcik 10/8/12 7:25 AM <This message has been deleted.>