Z zxxdaro Member Licensed User Longtime User Dec 23, 2011 #1 I have recently upgraded to the full version from the trial version. I have the SDK manager and a phone emulator running on the PC/. however now when I try to compile and run a program I get this message. Can someone please help me as this is very frustrating. I have of course tryed restarting the ADB server. Rebooting my PC and googling! ADB server didn't ACK * failed to start daemon * error: cannot connect to daemon Restarting ADB Server may solve this problem. Tools - Restart ADB Server
I have recently upgraded to the full version from the trial version. I have the SDK manager and a phone emulator running on the PC/. however now when I try to compile and run a program I get this message. Can someone please help me as this is very frustrating. I have of course tryed restarting the ADB server. Rebooting my PC and googling! ADB server didn't ACK * failed to start daemon * error: cannot connect to daemon Restarting ADB Server may solve this problem. Tools - Restart ADB Server
Erel B4X founder Staff member Licensed User Longtime User Dec 23, 2011 #2 This is a problem with Android SDK. Try to uninstall it and install it again. Upvote 0
Z zxxdaro Member Licensed User Longtime User Dec 23, 2011 #3 Erel said: This is a problem with Android SDK. Try to uninstall it and install it again. Click to expand... Thanks I did precisely that but it has not changed anything. I am still getting the error message. Upvote 0
Erel said: This is a problem with Android SDK. Try to uninstall it and install it again. Click to expand... Thanks I did precisely that but it has not changed anything. I am still getting the error message.
Erel B4X founder Staff member Licensed User Longtime User Dec 25, 2011 #4 You can use B4A-Bridge instead of ADB. Have you seen this link: "ADB server didn't ACK" error while trying to access with sdk - xda-developers Upvote 0
You can use B4A-Bridge instead of ADB. Have you seen this link: "ADB server didn't ACK" error while trying to access with sdk - xda-developers
latch Active Member Licensed User Longtime User Dec 16, 2012 #5 I think this is caused by the fact that adb.exe has been moved to /platform-tools and b4a is not looking for it there. Upvote 0
I think this is caused by the fact that adb.exe has been moved to /platform-tools and b4a is not looking for it there.
margret Well-Known Member Licensed User Longtime User Dec 16, 2012 #6 I had a few issues like this a while back once Google made their change. I finally uninstalled the old(Previous Install) Android and installed the new one and fixed all the issues. The new SDK Manager is much better and I am glad I took the time to do it. Upvote 0
I had a few issues like this a while back once Google made their change. I finally uninstalled the old(Previous Install) Android and installed the new one and fixed all the issues. The new SDK Manager is much better and I am glad I took the time to do it.
