StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PONexus 7 not visible over USB via "adb devices" from Windows 7 x64
text
Body
copied!<p>I have done the obvious -- the USB driver was installed from the latest Android SDK, and USB debugging was turned on in the tablet.</p> <p>When the <a href="https://en.wikipedia.org/wiki/Nexus_7_%282012_version%29" rel="nofollow noreferrer">Nexus 7</a> is connected, the device shows up in the Windows <a href="http://en.wikipedia.org/wiki/Device_Manager" rel="nofollow noreferrer">Device Manager</a> as "Android Phone" / "Android Composite ADB Device", with the properties showing driver version 6.0.0.0, so the correct driver is installed and working.</p> <p>This also proves the device is in USB debugging mode, because if it is not it shows up in Windows under "Portable Devices" / "Nexus 7".</p> <p>The problem is that <code>adb devices</code> shows no devices, and <a href="http://en.wikipedia.org/wiki/Eclipse_%28software%29" rel="nofollow noreferrer">Eclipse</a> also (not surprisingly) also does not offer the Nexus 7 as a hardware device to run an app on.</p> <p>I have rebooted both devices without effect.</p> <p>The only debugging I can figure out is enable <code>ADB_TRACE=all</code>, but this tells me nothing:</p> <pre><code>mkh@MULE ~/AppData/Local/Android/android-sdk/platform-tools $ export ADB_TRACE=all mkh@MULE ~/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 ***NOTHING SHOWN***** </code></pre> <p>What am I doing wrong?</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload