If Genymotion does appear to be using the version of ADB you expected it to use, then you might want to run which adb and subsequently readlink '$(which adb)'. Using that process ID, we can determine which version of ADB is executing via ls -la /proc/ADB_PROCESS_ID/ (Obviously, substitute in the numerical process ID.)įor example, I can see that the ADB server running on my side is /opt/genymobile/genymotion/tools/adb, as is pictured below: That should tell you the process ID of the ADB server that is listening for connections. To confirm which version is being used by Genymotion (i.e., to make sure it is respecting your configurations), run the following: netstat -tlpn | grep -i adb This issue definitely occurs when you attempt to connect with a version of ADB that does not match the version being used by Genymotion. It sounds like Genymotion may not be respecting the configuration you put in place.Īs shown in that screenshot. I would try connecting with the Genymotion-provided version. I have definitely encountered that error message when trying to connect to a Genymotion VM using the Android SDK platform-tools ADB instead of using the Genymotion-provided version however, I have not attempted to configure Genymotion to use the Android SDK-provided ADB.

Adb kill-server mac emulator