problem
Use adb command when given as follows:
1 adb server is out of date. killing... 2 ADB server didn't ACK 3 * failed to start daemon * 4 error:
problem causes
adb.exe conflicting versions of different software. And android_sdk version called adb command / adb version in the platform-tools directory is not the same as a result of (ie, may not be invoked android_sdk / platform-tools directory under adb).
Solution
In my previous example:
1. First View Genymotion sdk path configured to maintain consistent and Android_sdk the SDK path, as shown below:
2. Check whether the environment variable is configured with multiple adb path that leads when the command-line invocation to call the wrong version of adb
(1) Search in this computer adb.exe, you can see that in addition Android_sdk there adb.exe, Monkey also has adb.exe, you may have other.
3. Check whether the system call is Android_sdk in adb.exe.
(1) Open the command line, type adb version:
C:\WINDOWS\system32>adb version
The results are as follows: adb version is 1.0.32
Android Debug Bridge version 1.0.32
(2) into the path Android_sdk sdk configuration, perform adb.exe:
C:\WINDOWS\system32>cd /d D:\Android_sdk\android-sdk-windows\platform-tools\ D:\Android_sdk\android-sdk-windows\platform-tools>adb.exe version
The results are as follows: adb version is 1.0.41
Android Debug Bridge version 1.0.41 Version 29.0.2-5738569 Installed as D:\Android_sdk\android-sdk-windows\platform-tools\adb.exe
(3) comparison: From the above we can see two versions of adb is inconsistent, indicating Android_sdk we call adb when not in use adb.exe. Other adb.exe version before viewing Step 1 isolated, and if (1) the step results in step 2 of the same version number, then the problem lies on it, or call us directly in the open adb time, probably called it, not Android_sdk in adb.exe.
(4) verify (3) step. Go to the top under the adb.exe found in other directories, perform adb.exe version, in my Monkey directory adb.exe example:
D:\Android_sdk\android-sdk-windows\platform-tools>cd /d D:\Monkey\platform-tools_r22-windows\platform-tools
D:\Monkey\platform-tools_r22-windows\platform-tools>adb.exe version
The results are as follows: adb version is 1.0.32
Android Debug Bridge version 1.0.32
This version can be seen above the same, so the problem lies in its body, we only need to remove adb.exe to this directory, call adb again when you will find that the problem has been resolved.