How to connect HBuilder to genymotion Simulator
Background description:
Hbuilder is quite useful, fast, and simple. However, when running hbuilder, the running menu shows how to connect to the default simulator, however, the default simulator is too slow to connect to the genymotion simulator.
Symptom:
After hbuilder and genymotion are installed, after the simulator is started, hbuilder is completely inactive and cannot find the started simulator, let alone run it.
Problem Analysis:
My computer already has an android sdk environment and environment variables configured, so when you run adb, the adb under android will be started, while genymotion and hbuilder both have their own adb.
The directories are as follows: (example)
. \ Adt-bundle-windows-x86_64-20140321 \ sdk \ platform-tools
. \ HBuilder \ tools
. \ Genymobile \ Genymotion \ tools
So it's easy to get confused. Maybe there are some pods on your pc, like mobile assistants, all of which have their own adb.
Solution:
Worker Process [before kill, you need to know the ip address and port of the startup simulator. For more information, see note 2]. Then, start hbuilder, Enter cmd, enter hbuilder's tools directory, and run:
. \ Adb connect 192.168.56.101: 5555
Therefore, hbuilder connects to the simulator.
Note:
1. you cannot save the previous one. \, specify the current path. Because the path environment variable contains the path of androidsdk, it will run to the adb. When the adb starts, it will kill the current adb first, you must specify the adb of the running hbuilder;
2. After a bunch of IPs and ports are reached, after the killall adb.exe process starts the genymotion simulator, go to the genymotion tools directory and run:. \ adb devices (also cannot be omitted. \). The ip address and port of the simulator are displayed in the list;
3. If you know which software adb.exe is running before, right-click adb.exe in the task manager and choose open file location from the shortcut menu.
Okay, you're done!