Databases
StackOverflow2013
Postsdbo
POAndroid adb (OSX Lion) does not recognize Galaxy Nexus, Jelly Bean
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid adb (OSX Lion) does not recognize Galaxy Nexus, Jelly Bean
    text
    copied!<p>I've been developing my first android apps on Eclipse installed on OSX Lion. I would like to use my Jelly Beans Galaxy Nexus for debugging, but the <a href="http://developer.android.com/tools/help/adb.html" rel="nofollow noreferrer">Android Device Bridge (adb)</a> can't find the device:</p> <pre><code>./adb devices * daemon not running. starting it now on port 5037 * * daemon started successfully * List of devices attached </code></pre> <ul> <li>The phone is in debugging mode.</li> <li>The phone is recognizable as a camera (PTP), but not as a media device (MTP). ADB does not work regardless of PTP\MTP setting.</li> <li>I have restarted noth the phone and the mac</li> <li>Following <a href="https://stackoverflow.com/questions/9401049/samsung-galaxy-nexus-doesnt-appear-under-adb-devices-on-os-x">this advice</a>, I've installed <a href="http://www.android.com/filetransfer/" rel="nofollow noreferrer">Android File Transfer</a>. The ATF recognizes the device, but no luck with the ADB.</li> </ul> <p>Any ideas?</p> <p><strong>Addendum:</strong> I have <a href="https://code.google.com/p/android/issues/detail?id=37059&amp;thanks=37059&amp;ts=1346842671" rel="nofollow noreferrer">reported a bug</a> for this. Workarounds are still most welcome!</p> <p><strong>Sep 5 13:28 UTC - Workaround #1: Dropbox:</strong> I've moved the OSX Eclipse workspace to Dropbox and installed Dropbox on the device. The APK is written to <code>bin/</code>, and I re-install it from the Dropbox app after each successful build.</p> <p><img src="https://i.stack.imgur.com/Rsn6h.png" alt="enter image description here"></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