Develop Reference

Ubuntu : ADB not responding. If you'd like to retry, then please manually kill "adb" and click 'Restart'

I am using Ubuntu 14.04 LTS and just installed a fresh version of Android Studio, and written Hello World program, and now trying to run it, but everytime I am getting:
ADB not responding. If you'd like to retry, then please manually kill "adb" and click 'Restart'
I found many questions on SO, but none of them solution worked for me...

This kind of error mostly comes if you have already opened eclipse and studio both.
Solution: Close Eclipse if opened and "File -> Invalidate Caches / Restart...." from your android studio.

Try below steps:
Close the Eclipse/studio if running
Go to the Android SDK platform-tools directory in Command Prompt
type adb kill-server (Eclipse should be closed before issuing these commands)
then type adb start-server
No error message is thrown while starting ADB server, then adb is started successfully.
Now you can start Eclipse/studio again.

ADB not responding in android studio

The dialog has 3 options: Wait more, Restart and Cancel. But all of them gives me the same result, i.e. a message Waiting for ADB appears and I can't do anything with Android Studio.
I have to kill the program using windows task manager! I'm using windows 7.
I tried some steps like rebuild project and clean project but it didn't work correctly....I also try kill the adb.exe in Task manager ..but it not show in the Task manager sometimes.
Can anyone help me on this?
the main problem is adb.exe not found in Task manager..

Open command prompt and type in the below command
adb kill-server
then start server using the below command
adb start-server
This could remove any potential "waiting for adb" message if your adb server is not started correctly
Note: you may want to have adb in path variable

Android app is not launching in Emulator

When I am trying to launch an app in the emulator through Eclipse, the app is not launching and I am not getting any error also.
WHen I check in the target section of project properties, I can't see any AVD in the list even though I created a new AVD and it is running.

Your android emulator might fails to connect eclipse DDMS tool and ask for adb to start manually. In that case you can start or stop the adb using the command prompt.So, I recommend running in a single command line:
sudo adb kill-server && sudo adb start-server
If not works please switch To Android Studio .Eclipse is dead .

ADT keeps crashing all the time

I have problem in launching the adb or running my application my ADT keeps crashing or keeps not responding i already tried some ADB KILL-SERVER,ADB START-SERVER but it's not working i also tried to put the full path of platform tools in the environment variables but no lucks.I also tried to manual kill the adb.exe in task manager and restart my ADT but still it will hang or keeps not responding.I am using windows 7 32bit.
Thank you in advance.

Try to update your Android SDK tools with SDK manager. Make sure that no other process is running on port 5037. ADB runs on port 5037 by default.
Post the error messages that you get when you launch adb from command prompt.

Eclipse DDMS not showing Emulator on restart [duplicate]

This question already has answers here:
Adb won't start
(21 answers)
Eclipse error "ADB server didn't ACK, failed to start daemon"
(23 answers)
Closed 6 years ago.
I'm running Eclipse: Helios. Here's the issue. When I leave my Android Emulator running for about 20 minutes while I'm programming, if I try to install and run my application, I receive this error in the console:
[2011-07-12 12:27:55 - DatePrinter] Failed to install DatePrinter.apk
on device 'emulator-5554': Connection refused: connect
[2011-07-12 12:27:55 - DatePrinter] java.net.ConnectException:
Connection refused: connect
[2011-07-12 12:27:55 - DatePrinter] Launch canceled!
If I close the emulator and run the project again, a new emulator launches and the console shows the emulator starting but the app does not install and the emulator does not show up in DDMS.
If I go to the terminal and type in adb devices, I get this error message
ADB Server didn't ACK
*failed to start daemon*
error cannot connect to daemon
The only way I can fix it that I've found is to close eclipse, kill the adb.exe process and restart eclipse.
Any ideas what could be causing this error/how to debug it?
Edit: Starting the emulator through SDK manager does not yield any positive results either.
Edit 2: Running adb kill-server and adb start-server yields the same message "ADB Server didn't ACK" although it prints a "daemon not started, starting it now on port 5037" right before that.

Though I did not have the same problem as you did. In case of connectivity problems with emulator and Eclipse I use the following:
In the DEVICES window of Eclipse (DDMS perspective) drop down menu (in the upper right corner of the window) select "Reset ADB".
This solves most of connectivity problems, which otherwise will require restart.

Try this
adb kill-server
adb start-server
Check whether adb path has been added to environment variable, otherwise try to re-install the SDK itself.

I had the same problem. In the folder C:/../android-sdk/platform-tools, the following commands didn't work.
adb kill-server
Did nothing, and
adb start-server
resulted in an error.
So I killed the adb process with the task manager and used adb start-server again. And it works.

Here is a way to do it:
Open Task Manager
Select adb and end the process
Go to Eclipse and reset adb
Run your app

Check your Anti virus program control dialogs e.g Norton Antivirus and ZoneAlarm 2010.
Make sure that
eclipse.exe
emulator.exe
emulator-arm.exe
have input and outbound and network connections!