It should be noted, however, that prior to these recent errors and crashes in being able to run the Android Intel emulators I could successfully run the Android Intel Emulators from the AVD manager even though Hyper-V was enabled AND with running Windows Phone emulators (requires Hyper-V) side by side to the Android Intel Emulator without having any crashing issues of the Intel Android Emulator. I disabled Hyper-V to install the latest HAXM release but re-enabled it after HAXM was successfully installed. if you have any questions or issues getting HAXM working, I'd be happy to help. If you're still having trouble getting host GPU acceleration to work, your best option is probably to check with the official Google Android Developer Tools reference/support site ( ) and the support community there. The Google documentation for the Android SDK (, section title "Configuring Graphics Acceleration") has this to say about Graphics Acceleration:Īs you can see, Graphics Acceleration is an experimental feature of the Android SDK, and doesn't work with some types of applications or in conjunction with some other features (like snapshots). Graphics Acceleration ("use host GPU") is a feature of the Android SDK, and is not the same thing as HAXM. You can tell if HAXM hardware acceleration is active when an Android Virtual Device starts up in the emulator, and you see the message "HAX is working and emulator runs in fast virt mode", You can see more about setting up an Android Virtual Device with HAXM in this post. HAXM is hardware based acceleration for the emulator, and runs independently from Host GPU acceleration. HAXM is not the same as Host GPU acceleration.
I think we're talking about two different things here.
0 kommentar(er)
