CODEWITHSUNDEEP
androidandroid-emulator
umar
umar

Reputation: 3133

Android Adb error

Please guide me about this error 

2011-05-02 18:37:20 - SimpleOptionMenu] The connection to adb is down, and a severe error has occured.
[2011-05-02 18:37:20 - SimpleOptionMenu] You must restart adb and Eclipse.
[2011-05-02 18:37:20 - SimpleOptionMenu] Please ensure that adb is correctly located at 'F:\android-sdk-windows\platform-tools\adb.exe' and can be executed.

It was working fine and now i am getting this error . I have restarted eclipse but nothing happed . Thanks

Upvotes: 2

Views: 1622

Answers (4)

gsbabil
gsbabil

Reputation: 7703

I just posted the response below here: adb kill-server not responding?. I am duplicating it here too as Google considers this thread as one of the top hits.

If zombie adb process is not the issue i.e. there's no adb.exe in the task-manager list, the problem is usually adb ports e.g. 5555, 5554, 5037 etc., being taken by other applications.

Solutions:

  1. On all Windows: find the process taking one of those ports using netstat -bn and kill it from task-manager Ctrl+Shift+Esc is the shortcut.

  2. On Windows 7 and 8: there's this new tool called Resource Monitor. It'll also allow you to find out the blocked port and blocking process under the network tab.

  3. On Linux: the similar is done with netstat -pn. Feel free to use your grep foo as needed and kill the blocking process with kill or pkill.

  4. Change Default ADB Port: Apparently default ADB port can be changed as described here by setting up an environmental variable before launching ADB. Give it shot. It'll allow more flexibility if you don't want to kill the blocking processes.

Upvotes: 0

faradaj
faradaj

Reputation: 3689

When I faced with this problem, resetting adb is usually the solution.

If this not solves, unplugging-replugging the device works. I never have had to restart Eclipse.

By the way, Reset adb option can be found in DDMS(Dalvik Debug Monitor Server)'s Devices tab.

Upvotes: 4

umar
umar

Reputation: 3133

I do not know the reason but restating up my system worked for me :) !!!

Upvotes: 1

Jim Clay
Jim Clay

Reputation: 1003

I have had this error from time to time too, and restarting Eclipse has fixed it. My best guess is that you had the misfortune of getting the error twice in a row. Try restarting again and see if it goes away.

Writing this post has had the unfortunate effect of making me realize that the Android SDK bears a striking resemblance to Windows.

Upvotes: 3

Related Questions