I downloaded Genymotion Android emulators for Oracle VirtualBox (http://www.genymotion.com/) on my Windows 7 PC, created a virtual Jelly Bean with Google Apps device. How do I e
You can get IP Genymotion Virtual Device Manager,then use the command like this
adb connect your ip
If you launch the VM with the the launchpad (genymotion binary where you download the VMs) and you set the Android SDK path into the application parameters the connection is automatic and you don't need to run adb connect
You can find the information in the Genymotion Docs.
We need to connect with IP address to the emulator, so look for the IP address of the running emulator (it's shown in the emulator title bar) and use something like:
adb connect 192.168.56.102:5555
Afterward adb
works normally. You may also find out the IP address of a running emulator by starting "Genymotion Shell" and typing 'devices list'
I also find out that occasionally I have to do the above when the emulator is running for a longer time and somehow ADB disconnects from it.
Greg
Just Go To the Genymotion Installation Directory and then in folder tools you will see adb.exe there open command prompt here and run adb commands
I know it's way too late to answer this question, but I'll just post the solution that worked for me, in case someone runs into trouble again in the future.
I tried using genymotion's own adb tools and the original Android SDK ones, and even purging and reinstalling adb from my system, but nothing worked. I kept getting the error:
adb server is out of date. killing...
cannot bind 'tcp:5037'
ADB server didn't ACK
*failed to start daemon*
error:
So I tried adb connect [ip]
as suggested here, but I didn't work either, the same error came up.
What finally worked for me was downloading ADT, and running adb directly from the downloaded folder, instead of the system-wide command. So adb devices
will give me the error above, but /yourdownloadpath/adb devices
works just fine for me.
Hope it helped.
Connect didn't work for me, The problem was that Genymotion uses its own dk-tools and you need to change it to custom SDK tools.
More info: https://stackoverflow.com/a/26630862/4154438