Android Studio cannot connect via ADB on OSX

Question

I have worked a bit with Android Studio on OSX 10.7.5, and it looks very promising. However, I had a problem trying to run the application on my device.

When you press the start button, the AS claims to be "waiting for ADB." After a while, he expires and says that "ADB is not responding ...".

I tried rebooting and restarting adb using adb-killserver and adb-startserver many times, but it will not connect. When running adb devices or starting through eclipse everything works fine.

Someone got ideas, I would be very grateful!

Answer 1

EDIT: This really solved my problem, so this is an accepted answer. It seems this answer also helps a lot of people, but it did not work for me.

Here is what I did to finally make it work. I don’t know which of these steps caused my working copy, since it seemed to me very random, but I will put them in order.

• Remove AS
• Remove old adb path from bash
• Turn off the firewall (or at least check which connections are made by the AS and various USB drivers and allow them).
• Install AS
• Change the target device under Run → Change Configurations
• Launch
• It works ... maybe! ... ...
• Change topic
• Reboot
• Does not work
• Disconnect and connect the device
• It should work if you do not try to reboot and disconnect / reconnect until this happens.

Answer 2

In OS X, the following steps solved my problem:

• Disconnect Android devices,
• Close Android Studio;
• Force termination of the "adb" process from the activity monitor;
• Launch Android Studio.

Answer 3

I found a problem when I use genymotion. Finally, I realized that the problem is that the adb location does not match the android site. Therefore, you must update the adb of your genymotion. Step: Genymotion Settings → ADB → Using Custom Android SDK Tools

Answer 4

I had the same issue with Android Studio 0.5.3. I would recommend restarting the computer if the hell of a kill-server, the adb start-server method does not work.

Answer 5

I just happened on my Mac Mini, and it ended up working (recognizing the Nexus 5) when I plugged the cable into another USB port on the back ...

Answer 6

To launch the application on the device, I had to edit the launch configuration for the application by going to the Run menu and selecting Change configurations .

I selected the configuration with the name of my application and changed the Target Device to a USB device , which allowed me to run the application from the device. I used to get similar behavior to what you describe. Perhaps you have a completely different problem :(

Answer 7

I had the same thing. As soon as I turned off my device, the ADB Pending Notification disappeared and it worked. I think you cannot start AS when the device is connected.

Answer 8

Span said you have to do strange things, but sometimes it works (weird = reinstall, reboot using the word "maybe"). We must understand that this may be due to some bad settings in the OS that have been changed, but you do not remember about it.

But my business was even weirder! :)

The reason that Windows does not limit you to having many firewalls, it could be the key! Firewalls may not allow some applications to connect to another, you should also check it out.

I described it in: here

Assuming the crash course starts with Android Studio:

• disconnect the Internet connection (for security),
• uninstall Android Studio,
• delete the .gradle and .AndroidStudio folder from your home directory,
• remove all firewalls correctly, reinstall and configure them to allow,
• delete all av as above
• check the internal Windows firewall (or iptables on Linux :))
• install Android Studio.

If this does not work, and you want your OS not to be reinstalled - make a virtual machine with Windows and try. If it does not work, reinstall the system: (

Sincerely.