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:
- Power cycling machine and device
- Switching USB ports Unplugging all
- USB except for the sole (non-split)
- cable to the device Multiple cables
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/
Note that the setting for "USB Debugging" on the devices seems to unset under certain conditions. In my case this is what happened... So if you come across this for OS X, hopefully that is your issue, otherwise perhaps try the steps above. To enable USB Debugging:
- Settings --> Applications --> Development --> USB Debugging.
I had this problem, turned out to be a bad cable not connecting properly.
For completeness, I often find that running adb kill-server followed by adb devices will often cause the offending device to show up again. For some specific devices (eg. my Thunderbolt) I've also found I need to physically unplug the USB from the thunderbolt and plug it back in again.
I can second the point regarding easytether. Calling kextunload didn't seem to make a difference, but after also removing the EasyTether network connection from System Preferences, my device does indeed appear when i call "./adb devices"
This worked for me on my mac:
Declare your application as "debuggable" in your Android Manifest.
In the AndroidManifest.xml file, add android:debuggable="true" to the element.
Note: If you manually enable debugging in the manifest file, be sure to disable it before you build for release (your published application should usually not be debuggable).
来源：https://stackoverflow.com/questions/4435031/adb-devices-list-empty-snow-leopard