Android 9.+ emulator does not start - android

All AVD images work on my machine except for Android 9.+ (Google Play) & Android 9.+ (Google APIs) (the Android Studio emulator for Android Q beta).
I just downloaded the most recent images. From android-Q/google_apis_playstore/x86/build.prop:
ro.system.build.version.incremental=5506116
ro.system.build.version.release=10
ro.system.build.version.sdk=28
I am using Android Emulator version 29.0.11.
However, when I start these up, I see the device frame with a black screen. I get no error message, just nothing. It stays like this indefinitely.
Is there any way to debug this or is this a common issue?
Update: on another device (same image), I got the following screen instead of a black screen, however, there is still nothing I can do:

You need to configure correctly the Hardware Acceleration for your Emulator. Please, follow these steps:
1) Install the Intel HAXM driver if you are on Windows and have Intel, follow these steps:
Open the SDK Manager.
Click the SDK Update Sites tab and then select Intel HAXM.
Click OK.
After the download finishes, run the installer. Typically, you can find the installer in the following location: sdk\extras\intel\Hardware_Accelerated_Execution_Manager\intelhaxm-android.exe
Use the wizard to complete the installation.
After installing Intel HAXM, confirm that the virtualization driver is operating correctly by entering the following command in a Command Prompt window:
sc query intelhaxm
You should see a status message that includes the following information:
SERVICE_NAME: intelhaxm
...
STATE : 4 RUNNING
...
For Linux, check this link
For Mac, check this link
2) Open AVD Manager on Android Studio:
Edit the Virtual Device where you set target Android Q
Click Show Advanced Settings.
Set Graphics to Automatic or Hardware.

In my case all other emulators started, except Q. I have all needed SDK and AVDs.
But every time emulator didn't start without any error.
I saw Emulator in Android Studio doesn't start and found a way to understand a reason. I started from avd path:
D:\Android\emulator\emulator.exe -avd Pixel_2_API_29 -netspeed full -netdelay none
and got an error: PANIC: Broken AVD system path. Check your ANDROID_SDK_ROOT value [D:\Android]!. In PANIC: Broken AVD system path. Check your ANDROID_SDK_ROOT value I found that we should read config.ini inside 'Pixel_2_API_29.avd' folder and detect the line
image.sysdir.1=system-images\android-29\google_apis_playstore\x86\
I understood that I missed android-29 image in SDK path!
I knew that moved SDK and AVD folders from C:... to D:\Android, but SDK was kept in two folders.
And I forgot to change one system variable (ANDROID_HOME):
So I changed it to D:\Android and restarted the PC.
After restarting I deleted old SDK folder (in 'AppData\Local\Android'). Then I started again:
D:\Android\emulator\emulator.exe -avd Pixel_2_API_29 -netspeed full -netdelay none

Android 11 (R) emulator was not working for my case. I fixed it with the following steps.
Step 1:
Go to SDK manager -> SDK Platforms and install your required API level ( Like Android 11.0, Android 10.0, etc. For my case Android 11.0 was not installed that's why it was not working )
Step 2: Go to SDK manager -> SDK Tools and install Intel Emulator Accelerator (HAXM installed) if not yet installed. If you are a windows user then make sure that windows firewall is deactivated for a while otherwise it will not be installed and generate an error.
Step 3: Wipe data and Cold boot the device from ADV manager.
If the above steps are not worked then Invalidate caches and Restart your android studio as well as the PC.

I fixed it by reinstalling Android Studio entirely.
Actually, I just wanted to reinstall the Android SDK, however, you seem to need to install a stable version of Android Studio for that. After that, I set everything up the same way again and ran the beta version and now it works.

Had the same problem on macOS. Found out that I didn't have enough space on disk to create 'userdata partition'. So check that.

Related

emulator: incompatible HAX module version 3 requirs minimum version 4

where is problem?
emulator: incompatible HAX module version 3 requirs minimum version 4
emulator: no accelarator found
emulator: failed to intialize HAX: invalid argument
Open SDK Manager and update HAXM.
Tools > SDK Manager > SDK Tools > Intel x86 Emulator Accelerator (HAXM installer)
First of all go to Tools>SDK Manager>SDK Tools.
Then you can see the list of SDK developer tools available.
The tools which were already installed are checked and others are unchecked. Moreover, you can see the status as 'Not installed' or 'Installed'.
Most probably, 'Intel x86 Emulator Accelerator (HAXM installer)' is checked in your system. First uncheck it and then click on Apply button. Then program will redirect you for uninstallation of the accelerator.
After you get the message as Uninstallation successful, tick the checkbox again and click Apply button which will trigger the installation again.
After installation Go to Tools>AVD Manager and run whatever Virtual device you want.
I had faced the same error in the past while I was running Android Studio on my windows and after that I did research on the issue and I realized that I must start the HAXM installer manually so that I can use it:
I went to my Android SDK folder in my case it was C:\Users[user's name]\AppData\Local\Android\Sdk\extras\intel\Hardware_Accelerated_Execution_Manager\ and there I found that intelhaxm-android.exe file, I clicked on the file and allowed it to finish
The installation process after that I launched my avd device again then it ran properly for me.
Hope this solution will help you in resolving your issues.
In my case after updating HAXM installer through SDK manager,
I installed "intelhaxm-android.exe" (In windows OS) from path:
\sdk\extras\intel\Hardware_Accelerated_Execution_Manager
try this one:
Turn on "virtualisation" option in the BIOS setup while your PC/laptop boots up .
If its already switched on,
re-install haxm.exe and while installing, increase the size allotted to it. At least 2 GB.
now, it should run properly.
I too had the same issue. As the error message states, the installed HAX module is older version and cannot be compatible now. Go to Tools--> SDK Manager--> Click on SDK Tools tab and you can see the 'Intel x86 Emulator Accelerator (HAXM installer)' will be having an update.
Just check the check box and click on Apply and it will install the newer version. That's it.
Tip: Updating the remaining items is a best way to protect yourself from the future error.
For Windows and VIsual Studio:
It turns out that installing and uninstalling HAXM from the Android SDK menu does not mean installing or uninstalling in reality.
Everything worked for me before, but I did not return to this for a long time. So, I had HAXM installed, but the old version. For some reason, Visual Studio could neither update nor uninstall it. When installing a new version, the old one was not replaced and was considered a priority, so installing the new version without removing the old one did not help.
So, how I fixed the error:
"Removed" HAXM via Android SDK menu.
Checked Device manager for HAXM entry (I did not delete anything here because I did not find it)
Removed old HAXM folder from C:\Windows\System32\DRVSTORE\intelhaxm_*
Launched the broken old HAXM installer to remove HAXM registry keys. Before manual intervention, he did not want to work, citing the absence of some kind of .msi file.
Rebooted PC
I made sure that the old HAXM was removed from the system with the command: C:\Program Files (x86)\Android\android-sdk\emulator> .\emulator-check.exe accel
"Installed" HAXM via Android SDK menu. (At this step, nothing was installed - the command from the previous step still reported that there was no HAXM.)
Installed HAXM from Intel official repository: https://github.com/intel/haxm/releases
With command from step 6, I made sure that HAXM was installed correctly (for example, the output on my PC is shown):
PS C:\Program Files (x86)\Android\android-sdk\emulator> .\emulator-check.exe accel
accel:
0
HAXM version 7.7.0 (4) is installed and usable.
accel
After that, emulator should work. Perhaps Android Device Manager will glitch showing that the device emulator is already running (but I did not find qemu* and emulator processes). Probably, this can be solved more accurately, but I just deleted the existing device and created it again.

"No emulator installed" error in Android Studio even though Intel HAXM is up and running

Complete newbie, fresh Android Studio install, trying to run an emulator ends up coughing a "No emulator installed" error. Clicking the Install Emulator link does nothing. Trouble is, I've gone through tens of how-to articles and StackOverflow questions and did everything mentioned in those, to no avail.
What I have:
Windows 10, Android Studio 2.3.3
CPU: i7, supports HAXM
BIOS: "Virtualization" under Advanced tab is Enabled. It doesn't mention Intel or "Vt-x" or anything like that, just "Virtualization", but I guess that's it
Windows' Hyper-V is disabled
I enabled anything that mentions Google API, Emulator, or Intel in the SDK Manager. Here is how it looks on the SDK Platforms, SDK Tools and SDK Update Sites tabs:
I installed Intel HAXM manually, via its downloaded installer.
In the Terminal, if it type ...\sdk\tools>emulator-check accel, it says:
accel: 0 HAXM version 6.2.1 (4) is installed and usable. accel
If I type sc query intelhaxm, I get:
SERVICE_NAME: intelhaxm
TYPE : 1 KERNEL_DRIVER
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
First time I have met that problem I resolved it by uninstalling and removing all traces of Android Studio and installing it again. Next time when the same problem occurred on another machine I have found easier way to solve the problem:
Go to Android SDK location and remove "emulator" and "system-images"
directories. The default path to SDK is "C:\Users\User\AppData\Local\Android\Sdk"
In the Android Studio launch SDK manager, go to
"Appearance & Behavior > System Settings > Android SDK" menu, select "SDK
Tools" tab and check "Intel x86 Emulator Accelerator (HAXM
installer)" and "Android Emulator" checkboxes and click apply. Some
download and setup actions should occur at that point
Go to AVD manager, delete all AVDs and create new AVD you need.
The Emulator started successfully after that.
Hi simply go to your SDK then SDK tools and click to Uncheck Android emulator to uninstall it , then download and reinstall through SDK tools Android emulator. This work for me
I hope it will helpful to you.
I solved by removing /emulator folder and re-installing via sdk manager.
I had this issue on Linux with i7 processor and 32GB or RAM. This was a reinstall of the Linux OS and it had worked fine before. What I discovered was that the emulator doesn't like my video card, and setting the Hardware Acceleration to Auto caused it to select hardware and crash! Manually setting Hardware Acceleration to Software solved my issues.
Go to "Control Panel\System and Security\System" and open your Device Manager. Once Device Manager opens, go to Display Adapters and select the name of your graphics driver. Select the "Driver" tab, then click "Update Driver". This completely fixed the issue for me.
Here is the path to follow :
goto this location "C:\Users\User\AppData\Local\Android\Sdk"
delete emulator folder.
then go setting in android studio
chick android sdk
sdk tools
select sdk emulator and apply
emulotor will be installed.

Unable to launch android emulator in Mac

I have been working on an android project, I am using android studio on my iMAC[Software OS X 10.9.5, Graphics Intel HD Graphics 5000 1024 MB, Processor 1.4 GHz Intel Core i5].
When i try to open my application on an android emulator it get this 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!
I can find so many similar issues with solution on Google & SO, but i am unable to use those solutions for MAC???
I followed all the steps given here but with no luck, still unable to launch emulator. I think there is something to do with mac os.
Can anyone tell me how to do this on MAC ??
Thanks
First, make sure that the Intel HAXM is up to date. You update it by opening the SDK and selecting it in the list. (As of 2016-07-08, the latests HAXM version is 6.0.3).
Then, 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 ~/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 know I'm late, but here it goes.
Delete all AVD's that you currently have.
Go to Preferences >> Android SDK >> SDK Tools
Uninstall Android Emulator
Restart Android Studio.
Re-install Android Emulator from the same place.
Create a new emulator. And Voila !
What i personally did, in the process of fixing this.
I actually re-installed entire android studio. Followed this
Fixed my $PATH variables. Followed this
Then i tried re-installing Android Emulator, which worked for me.
Hope this Helps.
Problem in my case turned out to my .zshrc where my ANDROID_HOME was exported to a wrong value. Take a look at your .bashrc or .zshrc

ERROR: x86 HAX kernel module is not installed! But it is installed

This is a problem that I've researched and googled but have not found any answers for that I haven't already tried. I'm using android studio kit to learn how to develop android application but I can't get pass launching the avd emulator. I set the path for the sdk in environment variables like this:
Here is a screenshot of where I installed intel HAXM in the sdk.
Here is the error message:
Can somebody out there give me some advise on how to solve this problem. Thank you sincerely.
The SDK Manager only downloads HAXM. It does not actually install it. For Windows, in the extras\ directory in your SDK installation, you should find an intel\ directory. Drill down inside of there to find a self-installing .EXE file. Run that and follow the prompts in the wizard. Note that you may need to reboot to update your BIOS settings to enable virtualization extensions.
See also this outstanding Android tools issue.
Unless you chose a different location from Google's recommended one when installing the SDK, the path to Intel HAX installer should be %userprofile%\AppData\Local\Android\sdk\extras\intel\Hardware_Accelerated_Execution_Manager which you can open via Windows Run. Then the following explorer window opens:
Click and run intelhaxm-android.exe installer.
In the next window, leave RAM share for the emulator on the default 1024 MB. Continue and finish the installation.
Run your application in Android Studio and select your emulator (Here, Nexus 5 API 21 X86).
The emulator runs as follows:

Emulator in Android Studio doesn't start

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.

Categories

Resources