I'm running into an issue with the android SDK where it doesn't recognize devices plugged in via usb:
$adb start-server * daemon not running. starting it now on port 5037 * * daemon started successfully * $adb devices List of devices attached
(list is empty, other sdk tools don't recognize the devices either)
According to the SDK documentation, on Mac OS X, this should "just work". (Setting up a Device for Development)
It's worked for me in the past, but seems to have just stopped. Is there an OS X solution to this problem? (On other operating systems presumably you have to fiddle with USB drivers)
Have tried:
Make sure your device is not connected as a media device. Can confirm that this is critical! On Android 5.0, go to Settings -> Storage -> menu -> USB computer connection and make sure 'Media device (MTP)' is disabled. When it's disabled 'adb devices' lists the device, when enabled not.
Failed ADB connections usually have one root cause: bad Android USB drivers that load in place of the right ones. Windows doesn't make it easy to remove the wrong drivers, unfortunately. But before attempting to troubleshoot an ADB connection, first enable USB debugging on your phone if it's not on already.
Another thing for people searching who are still stumped (as I was for some time)...
I had this exact same issue and just figured out what helped for me. I had installed EasyTether and it was interfering with this even after I thought I uninstalled it.
Here's the solution from the EasyTether website:
ADB on Mac OS X stops recognizing the attached device after installing EasyTether driver. Use kextload/kextunload to unload from memory the EasyTetherUSBEthernet.kext kernel extension manually. It is in /System/Library/Extensions/
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With