genymotion

I accidentally selected the wrong folder when Genymotion prompted to select the installation directory. How do I change it? Look at Window > Preferences > Genymobile > Genymotion. You will then be able to modify the previous entry. 来源： https://stackoverflow.com/questions/18901248/how-to-change-genymotion-installation-directory-path-in-eclipse

I've tried the commands from Google adb shell dumpsys battery unplug adb shell dumpsys deviceidle step on both "PREVIEW - Google Nexus 6P - 6.0.0 - API 23 - 1440x2560" and "PREVIEW - Google Nexus 5X - 6.0.0 - API 23 - 1080x1920" virtual devices from Genymotion but unfortunately cannot put anyone to idle mode. Always after second command I see Stepped to: ACTIVE . Then trying adb shell dumpsys deviceidle force-idle I see Unable to go idle; not enabled . This is strange because Genymotion states in release note ( https://www.genymotion.com/#!/release-notes ) for version 2.6.0, which I use, that

I am having the problem where I am not able to debug my application using chrome debugger. It is too sluggish and heavy to use android studio and use its terminal. Being a javascript styled application(Developing on React native), Android Studio debugging doesn't suit well. I am able to see the device in chrome(advanced settings). But, when I click on "Debug in Chrome", I get the following error- Chrome connected Devices- I am running the following commands in my terminal so that my device gets connected via reverse port forwarding- react-native start > /dev/null 2>&1 & adb reverse tcp:8081

Reference: Genymotion how to debug with Chrome Dev Tools I'm also trying to get chrome developer tools to work with a genymotion emulator. However, when I follow all of the steps recommended (including at the above link), I don't get the "inspect" link. See: http://neu14.com/demos/screenshot.png Note: I found out that the default browser on the android devices, at least on most of the prior os versions is not Chrome. Finding an apk to download for Chrome android compatible versions, without an actual google play account, is quite challenging? It took me ages to get the remote debugging working

Started a new project, and this occurred to me: I am using Genymotion as my emulator. Not sure what causes this problem. I tried: Rebuilding the project Made sure I have enough space in my emulator (I have 4.5gb left) Check if it's already installed in the emulator , it hasn't. Open terminal, and type adb shell to access the emulator shell. Type settings put global verifier_verify_adb_installs 0 on the shell. I think this is related to the recent Google Play Services update. The verifier is more strict. This command in essence disables the Verify Apps option. From this article . you have to

Genymotion is unable to start android virtual devices on my machine. The Genymotion logs do not contain any relevant message. Instead, to debug the issue, I've launched the VM using vanilla virtualbox. The VM boots, and at some point starts to repeat the following message over and over again: init: sys_prop: permission denied uid:1000 name:androVM.gles.first_try init: untracked pid <some number> exited init: untracked pid <some other number> exited The Genymotion FAQ suggests that the output of glewinfo could help with troubleshooting. I've made it available here. Any ideas how to solve this?