As a general rule, I recommend you to avoid using the emulators at all. They are slow and unreliable. If you can't use a real device then use one of the virtual machines (genymotion for example) instead.
Thank you for your reply. Im using Genymotion. I had no problem at all till now and suddenly from 2 days im stuck with this error. The virtual device runs properly but my app does not get installed.
I had the same problem after I updated the Android SDK. Seems that Genymotion uses its own ADB server which is incompatible with the current SDK. You can point Genymotion to use the Android's ADB instead of its own. From the Genymotion FAQ
How do I automatically connect my virtual device to the ADB tool?
@James Chamblin Thank you so much for the valuable info. I updated genymotion to the latest version recently when i updated my Android SDK but dint realize it was using the old ADB.
I have the same issue, but it affects Bluestacks, Genymotion and all real devices. MoboRobo can connect to real devices, but ADB DEVICES on the command line returns "ADB server didn't ACK" as does B4A. This was working two weeks ago. I went on holiday and now it doesn't work. Any ideas?
Thank you. I will try that. I have it working now, after I uninstalled Kies and MoboRobo. MoboRobo installed a new version yesterday which seems to have caused the problem. Earlier versions of MoboRobo did not interfere with adb so if you have on that is working do not install an update!
I've tried both the post #6 and post #9 solutions and am still getting the "
ADB server didn't ACK" error when I try to connect to GenyMotion. Anyone have a solution?
I've tried both the post #6 and post #9 solutions and am still getting the "
ADB server didn't ACK" error when I try to connect to GenyMotion. Anyone have a solution?