Well if you are a mobile developer you would try developing apps for several platforms. I know I do And when you do you need to test the apps you build on either real devices or on Emulators. Most of us test the apps on the emulators first and then go for the real device.
As you know, Android Emulator is just F***ing ridiculously slow when it comes to testing on it. One way of giving the Android Emulator an ADRENALIN SHOT is to use the Intel Hardware Accelerated Execution Manager (HAXM) to boot the performance of the Android Emulator. I have written a post about this. You can find it here.
But sometimes when you try to install HAXM you run in to this error even when you have all the requirements fulfilled.
On windows platform this happens when you have Hyper-V enabled in your system. I ran in to this problem when I try to install HAXM with Hyper-V enabled. I do Windows Phone development. I LOVE WP so I need to have Hyper-V enabled to use the AWESOMEWindows Phone Emulator. I recently started developing for Android as well so I needed to have both Development tools installed on my Windows 8.1 installation. But when I try to install HAXM to boost my Android Emulator the problem starts.
You need to have Hyper-V disabled in Windows to use HAXM with your Android Emulator. So there is a fix for this by editing your Boot Configuration. The end result is that you will have 2 boot configurations for Android and Windows Phone development. Enough chit chat. Let’s get down to business
Open up a Command Prompt with Administrator privileges and enter the following command.
1
| bcdedit /copy {current} /d “Windows 8.1 – Pro – No Hypervisor” |
This copies your current boot configuration with the name you specified with in quotes (in this case the name is Windows 8.1 – Pro – No Hypervisor). You will see a message after stating “The entry was successfully copied to { identifier }” with the id of the new Boot configuration. See the image bellow.
Then type the following command in the command prompt.
1
| bcdedit |
This will now show you all the boot configurations available in your system. You can see the previous Boot configuration and the new boot configuration at the bottom with the name you gave (actually the name is the description ) Look closely at the bottom of the information. You can see that the value “hypervisorlaunchtype” is set to “Auto”. To disable Hyper-V we need to change this value. Look at the image bellow.
Copy the unique identifier of the copied boot configuration. Next type the following command in to the command prompt
1
| bcdedit /set {identifier} hypervisorlaunchtype off |
here in the { identifier }, replace it with the unique identifier you copied (that is of the new boot configuration you copied). Then you should get a message that the operation completed successfully. See the image below.
Then run the bcdedit command again in the prompt. Now you can see in the new boot configuration ‘hypervisorlaunchtype’ is set to off. See below.
Now its done folks you are good to go. Restart your PC. Just before the login screen you will be presented a screen saying “Choose an Operating System”. There you can see the Old boot configuration and the newly created boot configuration. To install HAXM you need to click and boot in to the new boot configuration. In this case it’s the Second option. ‘Windows 8.1 Pro – No Hypervisor’.See the image bellow.
The system will restart at this point. Don’t worry. It’s normal When you load a new configuration from the above screen the system will restart. That mean if you change from the current boot configuration to the new one or vice versa the system need to restart. If you boot in to the same configuration you used last time, it will boot up without restarting.
There it is guys no go on and install the HAXM software and enjoy an Android Emulator on steroids If you don’t remember how to do this, here is the link to the post where I explain it.
0 comments:
Post a Comment