Android studio can't connect through ADB on OSX

Question

I\'ve been working a bit with Android Studio on OSX 10.7.5 and it looks very promising. I\'ve run into a problem when trying to launch an application on my device however.

Answer 1

I just had this happen on my Mac Mini and it ended up working (recognizing the Nexus 5) when I plugged the cable into a different USB port on the back...

Answer 2

I had the same thing happen. As soon as I unplugged my device, the "Waiting for ADB" notification disappeared and it worked. I guess you can't start AS when a device is plugged in.

Answer 3

Span said that you should do strange things, but sometimes it works (strange = reinstall, reboot using word 'maybe'). We should understand that it could be, because of some bad settings in OS which had been changed, but you do not remember about it.

But my case was even stranger! :)

Cause Windows do not limit you to have many Firewalls it could be the key! Firewalls might not permit some apps to connect withother, you should check also it.

I described it in: here

Assuming the crash course to start Android Studio:

• disable connection to internet (for security),
• uninstall Android Studio,
• remove .gradle and .AndroidStudio folder from your home directory,
• remove all firewalls right way, reinstall & set them up to allow,
• remove all av's the same as above,
• check Windows internal firewall (or iptables in Linux :) ),
• install Android Studio.

If it do not work and you want to have your OS not reinstalled - make VM with Windows and try. If not work - reinstall system :(

Regards.

Answer 4

I found the problem when I using the genymotion. At last, I realized the problem is that the adb location is not the same as the android studio. So you should update the adb of your genymotion. The step: Genymotion settings -> ADB -> Use custom Android SDK tools

Answer 5

On the OS X the following steps solved my problem:

1. Disconnect your Android devices;
2. Quit Android Studio;
3. Force Quit process 'adb' from the Activity Monitor;
4. Start Android Studio.

Answer 6

In order to get my application running on a device, I needed to edit the run configuration for the app by going into the Run menu and selecting Edit Configurations.

I selected the configuration that had my app's name and changed the Target Device to USB Device which then allowed me to run the app from a device. Beforehand I was getting similar behavior to what you describe. It is possible yours is an entirely different issue :(