Related
After updating AS now emulator quits every time I start it. Below is the screenshot I managed to capture before it disappeared.
In the logs the following are printed
14:49 Emulator: WARNING: change of renderer detected.
14:49 Emulator: C:\Users\Nux\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe:
error while loading state for instance 0x0 of device 'goldfish_pipe'
14:49 Emulator: deleteSnapshot: for default_boot
14:49 Emulator: qemu: unsupported keyboard cmd=0x84
14:49 Emulator: qemu: unsupported keyboard cmd=0x84
14:49 Emulator: Process finished with exit code 0
I already tried the following:
Delete all my virtual devices and created new ones.
Wipe Emulator data.
Tried to lunch emulator manually in AVD.
Launch emulator with the option "Cold boot now".
And none of them worked. Any help will be appreciated!
I had the same problem and this worked for me.
I had the same problem. What worked for me:
Editing the AVD configuration and on Graphics I selected "Software".
Lower uncheck "Device Frame".(without this step it was keeping crashing).
Wipe data
Cold boot.
And now it works fine. Hope my advice will help to anyone.
I solved this problem.
If riot games are installed on your computer, stop Riot Vanguard and try again.
enter image description here
I experienced the same issue when updating Android Studio to version 3.4.
What worked for me was editing the AVD configuration and on Graphics I selected "Software -GLES 1.0". This made my emulator successfully boot up again.
Then I just went back to the Graphics configuration and selected "Hardware - GLES 2.0" again, which made my emulator go back to its usual performance.
Hope that helps!
if your using visual studio to run your emulator .
1-restart your pc.
2-run your emulator from android studio first.
this solved my problem.
I found a blog post which allowed me to fix the problem. Follow these steps:
In Tools > SDK Manager, make sure HAXM is installed and up-to-date. You can also manually install it from Github and restart Android Studio.
Open environment variables and add a new variable ANDROID_SDK_HOME, set the value to C:\Users\<yourUserNameHere>\AppData\Local\Android\Sdk
Go to C:\Users\<yourUserNameHere>\.android and copy the avd folder to C:\Users\<yourUserNameHere>\AppData\Local\Android\Sdk
Now open Android Studio and try again.
Had same problem and fixed by:
Start - Turn windows features on or off - (checking) Hyper-V - Reboot
Hyper-V "lets you create and run a software version of a computer, called a virtual machine. Each virtual machine acts like a complete computer, running an operating system and programs." - Microsoft docs
NB I also installed android emulator components like HAXM for Visual Studio 2022 Community, but this didn't fix problem on it's own.
In the Android virtual Manager -> Actions -> arrow down -> Cold Boot Now. And ready.
I recently experienced this problem.
I updated my windows 10 1904 to 2004, this solved my problem
If you use Windows10. Update your windows 10 1904 to 2004, this way I solved my problem
I was trying to create an emulator for Android 10 (the one for Android 9.0 worked fine) but I also got the error:
Resetting for cold boot: emulation engine failed
After some digging on the World Wide Web I found that I did not have the Android SDK 10.0 (Q) installed.
Steps (from Android Studio):
Step 1: Open SDK Manager (Tools -> SDK Manager)
Step 2: Choose your missing Android SDK and click Apply
Step 3: Wipe the data from existing virtual device (Tools -> AVD Manager -> Right-click on virtual device -> Wipe Data)
After the installation I right-clicked on my already existing virtual device and choose Wipe Data. I'm not sure it this is necessary though. Note that the same error - Resetting for cold boot: emulation engine failed - appeared but then it booted up correctly.
I was creating an emulator for Android API 30 and nothing of the above worked for me.
What solved my issue is:
ensuring the x86_x64 processor is selected when creating the new emulator
make sure that Hyper-V is running on your machine (type Windows features in the search bar and scroll down to Hyper-V)
Restart your machine and the emulator will hopefully work :)
I tried almost every solutions given by google. Since it was my first time installing Android Studio and got an error upon installing it, really frustrate me. The solution that works from me is this:
Ensure the x86_x64 processor is selected when creating the new emulator
make sure that Hyper-V is running on your machine (type Windows features in the search bar and scroll down to Hyper-V)
Restart your machine and the emulator will hopefully work :)
Since it gave me an error in the error list, I knew what to install. So I opened up command prompt and typed in:
dotnet workload install wasm-tools-net6
And it's now downloading the required tools to run the Android emulator. (wasm-tools-net6 was included in the error message - yours may differ).
I tried to run my Hello World application in Android Studio. I got the following error:
Emulator: ERROR: x86 emulation currently requires hardware
acceleration!
Please ensure Intel HAXM is properly installed and usable.
CPU acceleration status: HAX kernel module is not installed!
Can you tell me what I can do with the error?
As per this response, the complete steps are:
1) Open SDK Manager (In Android Studio, go to Tools > Android > SDK Manager) and Download Intel x86 Emulator Accelerator (HAXM installer) if you haven't.
2) Now go to your SDK directory C:\users\%USERNAME%\AppData\Local\Android\sdk\extras\intel\Hardware_Accelerated_Execution_Manager\ and run the file named intelhaxm-android.exe.
In case you get an error like "Intel virtualization technology (vt,vt-x) is not enabled". Go to your BIOS settings and enable Hardware Virtualization.
3) Restart Android Studio and then try to start the AVD again.
It might take a minute or 2 to show the emulator window.
[edit]
The Android developer page has been updated with an excellent guide to get an emulator up and running.
[/edit]
Install the Intel x86 Emulator Accelerator using the Android SDK Manager
If you have Android Studio installed, you can start the SDK manager via Tools -> Android -> SDK Manager.
The Android SDK Manager does not actually install HAXM, it just downloads it. In the top of the Android SDK manager window, you can find where the installer is located on your PC. Please open the subfolder extras\intel\Hardware_Accelerated_Execution_Manager, and run the installer manually: intelhaxm-android.exe.
To use the intel HAXM, you need to have a CPU with virtualization support:
Before attempting to use this type of acceleration, you should first
determine if your development system’s CPU supports one of the
following virtualization extensions technologies:
Intel Virtualization Technology (VT, VT-x, vmx) extensions
AMD Virtualization (AMD-V, SVM) extensions (only supported for Linux)
[edit]
As of Nov 27, 2019, Google has released an emulator for AMD CPUs.
[/edit]
If your CPU does not have virtualization support, you could use an ARM emulator instead:
You can edit an existing, or add a new Virtual Device in the Android
Virtual device Manager, and change CPU/ABI to ARM.
If that option is not available, you may need to change the target API of the Virtual Device, or download an
ARM system image for the API version you want using the Android SDK
manager.
I was able to resolve my problem of the missing acceleration with the following workflow on Windows 10, Lenovo, Intel Core i7 CPU:
Changed to the HAXM setup folder:
C:\Users\\AppData\Local\Android\Sdk\extras\intel\Hardware_Accelerated_Execution_Manager
Opened a cmd (MS-DOS) shell Window and executed haxm_check.exe to check whether CPU supports HAXM - it outputs in my case:
VT support -- yes
NX support -- yes
So, I knew this most be a setup problem. So, I started the setup program intelhaxm-android.exe in the same folder with Admin account and removed the installed components. After that, I've attempted to re-install with the same setup program and got this output:
So, I went into the CPU section of the BIOS and turned on acceleration/Virtualization - went back to the setup program and re-ran it, this time I was pleased to see this output:
After that, I restarted Android Studio and used Tools>AVD Manager to define a new image for an emulator. I was then able to see the emulator starting up succesfully by clicking the play button in the list of emulators in the AVD Manager's list:
or by
- Opening a sample project that compiles OK
- using File > Sync Project with Gradle Files (to build all artifacts)
- Select the app item in the Android (TW) and click Run > Run 'app'
- Select the previously configured Emaulator showed me this :-)
Hope this helps to troubleshoot others with their problems that are really caused by a bad setup implementation since the missing acceleration option was silently swallowed by the Android Studio setup program ... :-(
Simple Solution :
Open Android SDK manager, on top side you can see the "Android SDK Location" go to that location and follow this path
\extras\intel\Hardware_Accelerated_Execution_Manager
here you will get "intelhaxm-android.exe" install this setup.
If you are using an AMD CPU, AMD Virtualization (CPUs such as Ryzen) is now officially supported. Make sure you have virtualization switched on in the BIOS.
In "Turn Windows Features On or Off" (you can find it through Windows Search), you'll need to enable
Windows Hypervisor Platform on Windows 10 17134.1 (1803) April 2018 update or newer (commonly not mentioned in articles)
Hyper-V
Once you restart and start up the emulator (an x86 build), it should start booting up without the mentioned error.
On Mac, the Android SDK gets installed at: /Users/username/Library/Android/sdk/, therefore, you will need to run the script as sudo, as follows:
sudo sh /Users/username/Library/Android/sdk/extras/intel/Hardware_Accelerated_Execution_Manager/silent_install.sh
If all goes well, the script prints the message: "Silent installation Pass!"
Then, restart Android Studio and run your app with the desired AVD.
I wasted too much time on this, I find that the AVAST is the issue!!!
If you have AVAST installed in you system, you have to:
Go to settings tab --> troubleshooting, then you should UNCHECK the
"enable hardware-assisted virtualization"
Restart your PC, the install the intelhaxm-android.exe if it is not installed.
You can find it:
C:\Users\{YOURUSERNAME}\AppData\Local\Android\sdk\extras\intel\Hardware_Accelerated_Execution_Manager
Right click on your my computer icon and the CPU will be listed on the properties page. Or open device manager and look at the CPU.
It must be an Intel processor that supports VT and NX bit (XD) - you can check your CPU # at http://ark.intel.com
Also make sure hyperV off bcdedit /set hypervisorlaunchtype off
XD bit is on bcdedit /set nx AlwaysOn
Use the installer from https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager
If you're using Avast, disable "Enable hardware-assisted virtualization" under: Settings > Troubleshooting. Restart the PC and try to run the HAXM installation again
If you recently installed Docker on Windows OS, you need to turn off the Hyper-V feature. See the top answer of VT Not Supported when Installing HAXM
I solved this Issue by enabling virtualization technology from system Settings.
Just followed these steps
Restart my Computer
Continuously press Esc and then F10 to enter BIOS setup
configuration
Check Virtualization technology
Your system settings may be changed According to your Computer. You can google (how to enable virtualizatino for YOUR_PC_NAME).
I hope it helps.
A more detailed answer for dummies like me:
Open the SDK manager
Select the SDK Tools tab.
Download – Make sure that intel x86 Emulator Accelerator (HAXM) is downloaded.
Install – Now that HAXM is downloaded, make sure it is installed. In the SDK window it will show you where the SDK is located on your computer:
Click/tap 3 times quickly to highlight this text and copy the folder location. Open the file explorer and paste in the file location. From here you can search “hax” to find the folder location for HAXM stuff. Once a file comes up in the search results, right click and select “open file location”. For me the location was C:\Users\Datu1\AppData\Local\Android\Sdk\extras\intel\Hardware_Accelerated_Execution_Manager . Find the file intelhaxm-android.exe and open/run it.
Follow the instructions when it runs. You may wish to run haxm_check as an administrator (it’s in this same folder), but it may or may not work for you. The surefire way to tell if you can run hardware acceleration and if it’s enabled is to go to your computer’s bios settings from the startup menu.
BIOS settings – Make sure hardware acceleration is enabled in your BIOS settings. The way to do this may vary a bit from system to system. You may need to press f10 or esc on startup. But with most (updated) Windows 10 computers you can access the BIOS settings by doing the following: type “advanced startup” in the Windows search bar; click on “change advanced startup uptions:” when it comes up. Click “Restart now”. After your computer restarts click on Troubleshoot.
Click advanced options >firmware settings, then restart to change EUFI firmware settings. Wait for the restart then select the menu option for bios settings. With Intel processors the steps will be as follows or similar:
Press the right arrow to go to the Configuration tab. Arrow down to Intel Virtual/Virtualizaion Technology and turn it on (should say Enabled).
Exit and save changes.
If Virtual Technology was previously disabled in your bios settings You will need to run the intelhaxm-android.exe file now to install haxm.
Try restarting Android Studio and running your emulator again. If it’s still not working, restart your computer and try again, it should work.
NOTE: if you have Windows Hyper-V turned on this will cause you to not be able to run haxm. If you are having an issue with Hyper-V, make sure it is turned off in your settings: search in the Windows bar for “hyper”; the search result should take you to “Turn Windows features on or off”. Then make sure all the Hyper-V boxes are unchecked.
One more possible reason: you installed HAXM and then updated BIOS settings by disabling virtualization. Or, updated BIOS version. Please check BIOS settings again, and be sure virtualization enabled.
I had the same issue. In my case I found two issues causing the problem
I had Hyper-V running, I think if any Virtualization programs running you need to uninstall
I was running under Standard Account / Not Administrator
Open Android SDK manager,"intelhaxm-86 emulator" install that
Windows Users Only
This is a bit late but just figured that some answers are to go to the bios settings but for me, I was able to resolve this by just disabling the hyper-v feature. We do this by following these steps:
You should install the intel hardware acceleration first on sdk manager than you can start to create your virtual device on AVD manager
Enable virtualization Technology
This is worked in my case
Restart Computer
Continuously press Esc and then F10 to enter BIOS setup
configuration
Check Virtualization technology
My PC is HP Zbook
1. Boot the unit to BIOS (Reboot the unit and keep tapping on F10).
Navigate to Advanced>Device or System Configuration> Click on the check box Virtualization Technology (VTx) and Virtualization Technology for Directed I/O (VTd)
Save changes and Exit.
For me the following solution worked:
1] Going to BIOS setting and enabling Virtualization.
This steps worked on Mint 17.2 Rafaela:
Open a terminal and input this: sudo apt-get install qemu-kvm
Restart your pc and enable virtualization technology on your BIOS setup
In terminal again, insert this: sudo kvm-ok
In the android sdk manager it says that it has hardware accelerator already installed but I think it is only downloaded not installed.I just manually installed the intelhaxm-android.exe and it worked for me.
plus I had docker installed , there were some answers to disable Hyper-V features, therefore I did that too, but not sure whether it helped or not.
I experienced the same issue, but after turning off Hyper-V and enabling VT-x on my BIOS I still couldn't install the intelhaxm-android.exe program.
To fix my issue I had to turn off Windows defender Memory integrity
check here for steps -> https://github.com/intel/haxm/issues/105
I had the same issue even when hardware acceleration installed. My solutions was uninstalling and reinstalling it using SDK Manager. Make sure you restart the Android studio after then.
I already had HAXM installed, but it was an older version. Then I updated from SDK manager, then emulator worked!
This answer works for latest update on Windows 10 version 1709. Not tried with other version. But i hope it'll work.
I also ran into similar issue in my windows 10 system. I disabled Hyper-V and I tried all the answers posted here. But after that also i faced the same issue. So after lot of try, made it work using an documentation available in haxm manual. The document menntioned to use a tool named Device Guard and Credential Guard hardware readiness tool provided by Microsoft to disable Hyper-V along with some other features(Remember not only Hyper-V. So little cautios) completely. Follow the below steps to do that.
Download the latest version of the tool from here.
Unzip.
Open an elevated (i.e. Run as administrator) Command Prompt and run the below command by changing the extrated path and the respective version number.
#powershell -ExecutionPolicy RemoteSigned -Command "X:\path\to\dgreadiness_v3.6\DG_Readiness_Tool_v3.6.ps1 -Disable"
Reboot.
Then if you try to install intel haxm, it'll work.
In case of latest update check the docs available in official intel haxm development link.
Hope it helps someone.
For those who still have problems with this, you can try using an alternative Android emulator such as Genymotion.
I'm using Ryzen 5 processor with latest Windows 10 update installed (1809), but still can't install HAXM. So, what I did to resolve this was:
Enable Hardware Virtualization in BIOS settings
Enable Hypervisor Platform in Windows Feature
Install Genymotion with Virtual Box -- select for personal use
Install Genymotion Android Studio plugin -- find this in Android Studio plugins settings
You're good to go from here.
I am Developing android application using Eclipse. I got error HAX Kernal is not installed. I installed Intel HAXM using SDK manager. Even though the problem is occurred. Hiper-V is also disabled in my windows feature.
I forget my BIOS Password. So i am not tried using BIOS Setup. Please help me to enable Intel Visualization Technology(VT-X) without BIOS Setup
I got Below Error:
Please help me to enable Intel Visualization Technology(VT-X) without BIOS Setup
That is not possible, sorry. Contact your PC manufacturer for assistance in getting into your BIOS setup.
I was having the same problem and I had solved it by myself
Don,t worry here is the simple solution for you:
Go to your standalone SDK Manager, and find for Intel_HAXM type of package in Extras section. In worst case if it is already ind=stalled then try to update or reinstall it.
Select that package and then install it from the SDK Manager.
Now here is the important part, Go to "C:\Android\sdk\extras\intel\Hardware_Accelerated_Execution_Manager" and then open "intelhaxm-android.exe" .
Install it. If it says that your computer already has this installed , do you want to update it, then go for the same.
Restart your Android Studio or eclipse, and now everything is fine.
I just installed Android Studio without any problems. But when I run the emulator, I get an error:
Cannot Launch AVD in emulator. Output: emulator emulator: ERROR: x86 emulation currently requires hardware acceleration!
Please ensure Intel HAXM is properly installed and usable.
CPU acceleration status: HAX kernel module is not installed!
I have found a lot of similar posts and I have tried a few things but nothing has worked so far so I decided to make a post.
What I've tried:
Install HAXM through Android Studio
Download it separately through Intel
The error I get for the second option is
This computer meets the requirements for HAXM, but intel VT-x is not turned on. HAXM cannot be installed until VT-x is enabled
So I went into my BIOS but it was already turned on so nothing else I can do there.
Any suggestions?
HAXM stands for "Hardware Accelerated Execution Manager". It is used for launching Emulators and must be installed and in usable status.
Please note that Emulator launching means Virtualisation. So, we need to ensure that Intel Hardware to launch Virtualisation Technology(VT) is enabled in our machine.
So, here 2 things are there
HAXM is installed and VT is enabled?
HAXM is usable?
Following are the steps:
Step.1) Ensure that HAXM is installed.
In Eclipse env.
In Android SDK env. (Click "SDK Manager ==> SDK tools tab")
Close your Eclipse/Android SDK IDE.
Please note only the installer is downloaded at this stage and not actually installed.
Step.2) Launch the installer.
Android SDK path:==> C:\users\%username%\AppData\Local\Android\sdk. In this directory, go to extras → Intel → Hardware_Accelerated_Execution_Manager and run the file named "intelhaxm-android.exe".
In most cases, the installer launcher should launch. But in some cases, you may encounter this error:
Just make sure that your machine has Hardware Virtualisation Technology(VT) Enabled.
Restart your machine, and keep pressing F1+F2 for the BIOS option and Enable VT as follow.
Again repeat Step.2)
Step.3)
Restart the machine.
a.) Go to Control Panel → Program and Feature.
b.) Click on Turn Window Features on and off. A window opens.
c.) Uncheck Hyper-V option and restart your system.
Now, you can Start HAXM installation without any error.
And then Start your Emulator.
I had this problem for a while too.
I'm not sure if you've done this already but after installing HAXM through Android Studio, you must run the installer located at:
/sdk/extras/intel/Hardware_Accelerated_Execution_Manager/
If you've already done this or it's still not working, try disabling any anti-virus software you have. Apparently it can prevent HAXM from installing.
If it's still not working, check out this post for more help: HAXM error but vt-x is enabled
I also got this problem. Relax. Go through the following steps:
Go to SDK Manager in Tools > Android > SDK Manager, go to launch Standalone SDK Manager, then check the Intel x86 Emulator Accelarator(HAXM Installer)
Then downnload intel haxm from https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager , haxm-windows_v6_0_1.zip (6.0.1) for Windows.
Now we have to enable VT-X from The BIOS, go to settings > Change PC settings > Update and Recovery > In Recovery, go to advanced , Restart now > Trouble Shoot (advanced options) > Advanced options > UEFI Firmware settings > Restart. It will take you to BIOS page , click F10 for BIOS settings , in that go to System > System Configuration . Under that , virtualization technology will appear . Enable it by clicking Enter. Then Exit and Save.
Hopefully !! This will works . Good luck.
When I got this problem, this is wat I did, I tried everything else until I opened my Android Studio as an administrator, then I went to Tools >> Android >> Android SDK Manager, from there, opened tools tab, then extras, then check HAXM, then I was able to install HAXM. Hope it helps someone
I was running Android Studio 3.1.3, and I was very much frustrated with it, as the AVD was not running at all! In anger, I deleted Android Studio and downloaded it all again (now, the version was 3.1.4).
Originally, I had done a "Standard" installation, but this time I did a "Custom" installation, making sure to check the "Android Emulator" and "Intel HAXM Installer" options. This guarantees that the correct components are installed. Now you can create the AVDs.
I faced this problem then I enable VMX in Bios And It solved my problem.
confirm whether the control panel-program-can find "HAXM", if installed, this is a wrong installation.
reinstall "HAXM" in the SDK Tool of Android Studio.
The method is applicable to confirming that the parameters of the BIOS have been set correctly.
I think it's a problem with the SDK reference in Project Structure, but when I click run and I choose Launch Emulator nothing appears.
I had the same problem. I just created the AVD with 768 MB RAM and it did run fine!
UPDATE: November 2022
This answer was almost from 10 years ago and will most propably not work on current version of Android Studio.
I had a similar problem... Android Emulator doesn't open.
You need to discover the reason of this... You could run your emulator from the command line. For this you could copy and paste your command line from "Run" or "AVD" Android Studio console.
For example:
"{path}\android-sdk\tools\emulator.exe -avd Default_Nexus_5 -netspeed
full -netdelay none"
When you launch it from a command line terminal, It give you a message with the error.
In my case it was useful for discover the problem:
..\android-sdk\tools>emulator: ERROR: x86 emulation
currently requires hardware acceleration! Please ensure Intel HAXM is
properly installed and usable. CPU acceleration status: HAX kernel
module is not installed!
I needed to activate GPU acceleration with a tool to enable it on my machine.
I solved it installing from SDK Manager the tool HAXM...
I had another problem... For example i had assigned a bad url for skin path of my virtual device...
To solve it I have configured my virtual device with a valid skin from my platform sdk: '{path}\android-sdk\platforms\android-{number}\skins{SCREEN_SIZE}'
Now it is opening fine.
Update 8/8/2019:
For newer version of Android SDK, emulator path should be:
"{path}\android-sdk\emulator\emulator.exe"
reference (thank you #CoolMind)
In my case the android hangs at start up. I solved by wiping user data and forcing a cold boot, using Android Virtual Device Manager (Tools->AVD Manager)
It seems that "Waiting for target device to come online ..." is a generic message that appears, always, when the emulator can not start properly. And what's the cause of that? As you can see, there could be many causes.
I think the best way to find the concrete error with the emulator is to start it within a terminal. So:
1 - Open a terminal and go to this folder:~/Android/Sdk/tools
2 - Start the emulator with this command:
./emulator -avd EMULATOR_NAME -netspeed full -netdelay none
You can see the name of your (previously created with AVD Manager) emulators with this command:
./emulator -list-avds
If everything is ok, the program doesn't start, and it writes in the terminal the concrete error.
In my case, the application says that there is a problem loading the graphic driver ("libGL error: unable to load driver: r600_dri.so"). As it is explained here, it seems that Google packaged with Android Studio an old version of one library, and the emulator fails when it tries to use my graphic card.
The solution? Very easy: to use the system libraries instead of the packaged in Android Studio. How? Adding "-use-system-libs" at the end of the command. So:
./emulator -avd EMULATOR_NAME -netspeed full -netdelay none -use-system-libs
The definitive solution is to set the ANDROID_EMULATOR_USE_SYSTEM_LIBS environment variable to 1 for your user/system. With this change, when I run the emulator within Android Studio, it will also load the system libraries.
PS 1 - The easiest way I found to set the environment variable, it's to modify the script that launches the Android Studio (studio.sh, in my case it is inside /opt/android-stuido/bin), and add at the beginning this:
export ANDROID_EMULATOR_USE_SYSTEM_LIBS=1
PS 2 - I work with Debian Jessie and Android Studio 2.2.3. My graphic card is an ATI Radeon HD 6850 by Sapphire.
UPDATE December 2017: I had the same problem with Debian Stretch and Android Studio 3.0.1 (same graphic card). The same solution works for me.
1) Open SDK Manager and Download Intel x86 Emulator Accelerator (HAXM installer) if you haven't.
2) Now go to your SDK directory (C:\users\username\AppData\Local\Android\sdk, generally). In this directory Go to extra > intel > Hardware_Accelerated_Execution_Manager and run the file named "intelhaxm-android.exe".
In case you get an error like "Intel virtualization technology (vt,vt-x) is not enabled". Go to your BIOS settings and enable Hardware Virtualization.
3) Restart Android Studio and then try to start the AVD again.
It might take a minute or 2 to show the emulator window.
If you are new to Android studio, you need to follow few basics steps in configuring the emulator.
Make sure you have proper SDK installed
Make sure you have Intel HAXM & virtualization option enabled in your BIOS
Configure emulator correctly, download the Intel X86 Atom system image for better performance.
Go through this blog, http://www.feelzdroid.com/2015/05/android-studio-emulator-not-working-solution.html
Here they have explained clearly, what are the problems you face while running & resolution for the same.
With Ubuntu, I had the same problem. I solved it by changing file /dev/kvm permission to 777:
sudo chmod 777 /dev/kvm
you need to install "Android Emulator"
Go to
SDK Manger -> Appearance & Behavior -> System Settings -> Android SDK -> SDK Tools.
and set a hook at Android Emulator
I had the same issue in Android Studio 2.3.3 on Mac OS X 10.12.6 and the issue was caused by Android Studio using an old version of HAXM (6.0.3 when it should have been 6.2.1):
$ kextstat | grep intel
148 0 0xffffff7f8342c000 0x14000 0x14000 com.intel.kext.intelhaxm (6.0.3) 50449AFC-F7C6-38A0-B820-233E8A050FD6 <7 5 4 3 1>
Removing and reintalling HAXM from within Android Studio according to the instructions didn't work: https://software.intel.com/en-us/android/articles/installation-instructions-for-intel-hardware-accelerated-execution-manager-mac-os-x
Instead, download the HAXM installer manually or if that link expires, find it under https://software.intel.com/en-us/android/tools under Intel® Hardware Accelerated Execution Manager (Intel® HAXM).
After running the installer, it now shows that the current version of HAXM is installed:
$ kextstat | grep intel
169 0 0xffffff7f83472000 0x1d000 0x1d000 com.intel.kext.intelhaxm (6.2.1) 7B6ABC56-699C-3449-A0EC-BEB36C154E3C <7 5 4 3 1>
After upgrading HAXM manually, I'm able to launch x86_64 emulators.
Old answer, which might work instead (note that this didn't work for me for x86_64 images):
Create a new device:
Tools->Android->AVD Manager
+ Create Virtual Device
Tablet -> Nexus 7 -> Next
The Recommended tab should be highlighted.
Even though I had the API Level 25 SDK installed, it showed:
Nougat Download 25 x86 Android 7.1.1 (Google APIs)
So I clicked Download link which seems to have repaired the API Level 25 SDK. I finished creating my new device and it ran fine.
Unfortunately I had already deleted my old device, so if this works for someone else, please leave a comment here to let us know if your original device worked afterwards, thanks!
I'd like to post a link to this answer as it might help out any persons in this thread running into issues starting a virtual device with more then 768 mb of memory;
How to make an AVD with > 768MB RAM To emulate Galaxy devices
I have similar problem but I have solved it by switching to "Android 4.2.2 armeabi-v7a" (I needed to test it on Jelly Bean) in my AVD and it fixed the problem for me.
What seems to happen is that my processor is AMD and Intel X86 hardware emulation couldn't start. So I changed to use "API" other than "x86" (even though it recommended me to use x86). Hope this helps.
I spent several hours on this problem. What worked for me was opening the Tools->Android->SDK Manager, choosing Android SDK under System Settings on the left of the screen and going to the SDK tools tab. I then unchecked the settings for Android emulator and the Intel x86 Emulator Accelerator. I applied these changes, restarted Android Studio and then re-checked these option and applied the changes. The program reinstalled the emulator components and things seem to work. Hope this helps someone.
In Android Studio 2.3.3 I was able to get my AVD to start and run by changing Graphics in the Emulated Performance section from Automatic to Software-GLES 2.0:
I was able to infer this after following the advice at https://stackoverflow.com/a/44931679/1843329 and doing:
$ ./emulator -avd Nexus_4_API_21 -use-system-libs
which resulted in:
emulator: ERROR: Could not initialize OpenglES emulation, use '-gpu off' to disable it.
And when I did:
./emulator -avd Nexus_4_API_21 -use-system-libs -gpu off
the emulator then launched.
Wipe data of AVD like that picture and run your program. it's work for me.
If anyone is still having trouble with launching the avm take note of the android studio event log when you try to run the avm. When I tried running the avm android studio mentioned that my environment variable ANDROID_SDK_HOME was set to the same place as ANDROID_HOME and it shouldn't be. It recommends deleting the variable ANDROID_SDK_HOME which I did and then restarted android studio and avm started working.
Access the BIOS setting and turn on the virtualization feature. Mine was together with options like cpu fan speeds and stuffs.
Then make sure that Hyper-V is turned off in the windows features ON/OFF.
Then reinstall the intel HAXM, this should fix this issue.
edit this file:
sudo nano .android/avd/your_emulator.avd/config.ini
change lines
hw.gpu.enabled = yes
hw.gpu.mode = auto
to
hw.gpu.enabled = no
hw.gpu.mode = off
It works for me !
just check out if you have this problem "vt-x is disabled in bios"
in this case you need to enable virtualization technology bios
It probably won't start because you
no CPU is installed, then follow this answer: Unable to create Android AVD because of Target and CPU/ABI settings?
OR
don't have the correct SDK downloaded
If you migrated your project from Eclipse chances are that on running an emulator you will get stuck with this message not seeing anything else:
Waiting for device.
If you open the device manager you probably see something like this:
Just recreate your devices.
I've faced similar problem. You can edit the configuration or create new AVD with higher RAM. Also try increasing Heap to 128. Emulator will work smoothly even without HAXM
I had the same problem. I just Created New AVD with 768 MB RAM and it did run fine for me. I Used for API 22(Lollipop Version).
Besides using an external emulator such as bluestacks, you can also create a new new AVD and choose a system image with an ABI of armeabi-v7a with an API level of 21, instead of choosing ABI of x86 which fails.
I was having the same problem, i tried this and it worked. hope this will be useful as well.
Check if the following tools are installed or not in the Android SDK Manager as shown in this picture:
One reason could be that the chosen ABI does not fit to your system. For me, only arm64 is working.
I had the same problem on Windows 10, after I moved my android-SDK folder to D:/ as I was low on space on c:/.
It turned out that the Android emulator looks for Android SDK via Global (environment) Variables, not the path defined inside Android Studio.
So I edited the Environment variable of ANDROID_HOME and that was it.
If your emulator worked fine but suddenly it doesn't, just restart the machine and run again.It worked for me.
I faced the same problem. From some research that I did, I realized that my computer does not support virtualization. So I had to install BLUESTACKS.
Believe me it worked...you can also try it.
Just go to your directory C:\Android\sdk\platform-tools and double click adb
Ensure that your bluestack is running.
When you try to run the project, it automatically shows up to run with the bluestacks....just choose the bluestack and you are done.
If you want the setup of bluestack, just google it you can have a number of sites to download from for free.
I performed the procedure below, and was successful.
Execute this command down.
npx react-native info
This command return the log file the npm (example)
C:\Users\Robinho\AppData\Local\npm-cache\_logs\2020-11-22T19_35_23_842Z-debug.log
In my case was permission in dir file in windows SO.
I restarted my computer clicked F1 for the Bios setting and checked the virtualization technology box and saved the changes. The AVD worked without glitches after my computer booted. This article explains it. Hope somebody finds this helpful.
I was having this same problem. I decided to create (see the button at the lower-left). I defined the image to match my device and that seems to work.
I am thinking with Android Studio at version 1.0.1, there are still plenty of bugs.