Related
I have an error when running my app using android studio, but before that it was working okay until an update(Android API27), I have tried uninstalling it but nothing,the warning am getting is;
Emulator:Warning:Quick Boot/Snapshot not supported on this machine.A
CPU + UG feature is currently needed. We will address this in a future
release.
How do I resolve this problem?
a friend just told me the solution, so please find it here!
The issues have to do with the specific device you're trying to emulate and the processor you have (intel core 2 or older)
To solve it:
Create a new emulator
Select the device you would like to emulate.
On the next page with the header "System Image" select the tab "other images"
Download and select an image that is listed as armeabi-v7a under the ABI column.
That image should run successfully with your processor.
That's the solution! Hope it helps :)
The issue might be your CPU hardware. AVD Google API levels 21+ do not run well on CPUs that do not support Extended Page Tables (EPT) and Unrestricted Guest (UG), such as Core 2 Duo. Your best option is to try a system image with AVD Google API level <= 20 on those type of CPUs. You still will see the warning but the emulator will boot up.
Update:
I had further issues and it seems the only way to boot to a usable system image is to go with an armeabi-v7a version on Core 2 Duo chips.
I had the same problem.
I tried to update my HAXM on my windows-7 using this resource file from the official site - software.intel.com. Also available from the Intel HAXM github page.
So as I said after updating my HAXM-Windows from version 6.1 to 7.1.0
my Emulator in Android Studio started to work!!!
Change your Emulator Performance under Tools>ADK Manager to Software - GLES 2.0. This will work if your AVD isn’t among the ones with the playstore icon
see if intel virtualization technology is turn on in your bios. worked for me.
I had the same problem with Hyper-V, so I created a new BCD entry to disable it and be able to install HAXM:
bcdedit /copy "{current}" /d "no Hyper-V"
bcdedit /set "{GUID}" hypervisorlaunchtype off
The message still appears, but the emulator is running with the latest API version and the x86 ABI.
I had the same problem and my cpu is "Intel(R) Core(TM) i3-2350M - 2.30GHz". to resolve it follow the steps:
check the virtualization in bios is Enabled (for intel CPU)
remove intel HAXM from "Add or Remove program" (if exist)
in SDK Manager -> SDK Tools check "Intel x86 Emulator Accelerator (HAXM installer)" and wait to download the program.
go to file explorer to "android SDK location"\extras\intel\Hardware_Accelerated_Execution_Manager and then run "intelhaxm-android.exe"
Reference: official intel video for HAXM
Now go to AVD manager and create an emulator. then run the emulator. if it runs with problem and doesn't work properly (the same as me), as the android studio suggestion create an x86 emulator:
click on the "Create Virtual Device" then select a device and next
Select x86 Images Tab and select one of x86 (ABI) and download it then next
continue to finish and create the emulator.
run the emulator.
I hope it's useful.
I was trying Android Studio - successfully installed it but couldn't launch the emulator and the error message was Intel Haxm wasn't installed. I checked my setting and realized it was installed.
I tried to re-run it several times and the same thing happened.
I tried to install SDK 17 and the error was still there.
May I know what might be causing this? And how should we solve it?
Thank you.
You was created an AVD with Intel Atom system image, so make sure that your CPU is Intel. If yes, see this instructions about installing HAXM on your computer.
If HAXM won't to be installed, please make sure that your CPU is strong enough to use HAXM. Then, change the system image of your AVD to ARM-v7 or Armeabi.
System image also called with CPU type of the emulator on AVD.
Another option to run Android Apps on computer:
If you are not able to use Android Studio Emulator (at all after trying above given solutions), then you can use Genymotion. It comes with free as well as paid versions. You can download this software on your Windows/Mac/Linux based computer and configure it with Android Studio/Eclipse.
Watch this video for more details: Install and configure Genymotion with Android Studio
Genymotion is fast and reliable and also has latest (till Lollipop 5.0) android support and provides many emulator themes as well.
I hope this answer helps you if above mentioned solution doesn't work.
I have not enabled Hyper V or hardware acceleration and don't want to either.
Is there any way that I can start android emulator for Intel x86 Atom Without hardware acceleration on Windows 8
I have created AVDs with every combination possible and each one has failed to start the AVD emulator instance , throwing the same error when starting
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!
OR is it that, the images given for Intel Atom 86 and 64 cannot run without HARDWARE ACCELERATION AND hyper V for API 21 and 19
I have found lots of similar question and read almost all documentation, but it is not clear if they can or cannot run without hyper v and hardware acceleration, hence this direct question
How do you test on android in such cases ?
In current AVD manager you can't. You just have the opportunity to use ARM images which will not need hardware virtualization.
To run ARM images:
Open AVD manager.
Create a new 'Virtual Device' OR right click an existing image and select 'Duplicate'
Choose arm* instead of x86/x64.
Continue with the wizard.
Run!
Although this is the available solution but still a slow one !!
You can still force the use of the soft x86 emulator by running it from the command line and using the -no-accel option, i.e.
from the SDK/tools directory:
emulator -avd AVD_NAME -memory 768 -no-accel -gpu on
BUT this still won't work with the current (V24) SDK, because the current x86 system images crash the soft x86 emulator :-(
The only way I got this working again was to downgrade the SDK tools to V22.3 from here:
http://dl-ssl.google.com/android/repository/tools_r22.3-windows.zip and to buld an AVD using a downgraded system image, for instance https://dl-ssl.google.com/android/repository/sys-img/android/sysimg_x86-17_r02.zip. (So this is no help if you need to test on more recent versions of Android).
Google have moved on to an updated version of their emulator based on a more recent version of qemu, and provide binaries for arm and mips emulators, but have omitted to ship the x86 equivalent (there is no emulator-ranchu-x86.exe and emulator64-ranchu-x86.exe). If they did so, or if someone else went to the trouble of setting up and compiling their emulator source with the "x86" flag on, then _x86 soft emulation could conceivably be made to work again.
Short Answer: No. Until recently(about 1 month ago), you could do that but with the latest updates, it is not possible. (see Update to Android SDK Tools 23.0.5 and avd doesn't start).
I was doing something similar: Doing development in a virtual machine and hence couldn't use the Hardware acceleration features as they are available only in the host machine. I was using Intel x86 images with Use Host GPU option; as they were much faster than the ARM version even without hardware acceleration. But then, after this update, my emulator AVDs which were working earlier are no longer starting with the same exact error message. Also, both genymotion and Xamarin Android emulators can't be used as they also need hardware acceleration(they are actually VMs which use Hardware acceleration for speed, and hence can't be run inside another VM).
I have found this solution but haven't tried it yet. The basic idea is that to still develop inside a VM; but for testing connect to an Emulator running on the host machine(and this Emulator VM can now use the hardware acceleration feature).
Same issue as in Error in launching AVD:
1) Install the Intel x86 Emulator Accelerator (HAXM installer) from the Android SDK Manager;
2) Run (for Windows):
{SDK_FOLDER}\extras\intel\Hardware_Accelerated_Execution_Manager\intelhaxm.exe
or (for OSX):
{SDK_FOLDER}\extras\intel\Hardware_Accelerated_Execution_Manager\IntelHAXM_1.1.1_for_10_9_and_above.dmg
3) Start the emulator.
The usage of the Hardware acceleration depends on the System Image you choose on the emulator.
So,
Go to AVD manager, create virtual device, select hardware, click next.
Choose the System Image that does not require HAXM (hardware
acceleration) for running. (That is appears at the right bottom of
System image window.)
Note: for other systems that require HAXM, there no way to run them without hardware acceleration.
use bluestacks as a emulator for best performance. blusestack working fast without hardware based emulation
To connect bluestack to android studio.
Close Android Studio.
Go to adb.exe location.(Bydefault its C:\Users\Tarun\AppData\Local\Android\sdk\platform-tools)
Run adb connect localhost:5555 from this location.
Start Android Studio and you will get Blue Stack as emulator when you run your app.
Is there any way that I can start android emulator for intel x86 atom Without hardware acceleration on windows 8
Not with the standard Android SDK emulator, as it requires Intel's HAXM, and HAXM wants virtualization extensions to be enabled.
Whether Genymotion or something else from another independent developer can support your desired combination, I cannot say.
refer intel.com's requirements : Important: Intel HAXM cannot be used on systems without an Intel processor, or with an Intel processor that lacks the hardware features described in the "Hardware Requirements" section above.To determine the capabilities of your Intel processor
[Installation Instructions for Intel® Hardware Accelerated Execution Manager ] https://software.intel.com/en-us/android/articles/installation-instructions-for-intel-hardware-accelerated-execution-manager-mac-os-x
My PC does not support vt-x, I can not use android studio 1.0.2.
yes is possible to run your android emulator without have a hardware accelerator.
In fact to do that, you need to open your android virtual device.
When you reached to system image configure, it suggest you which version of android image you want to use.
Whatever version of android system image that you select,you need to make sure that,ABI is armeabi-v7a and, you target is System image ameabi-v7a with google APIs.
And then complete the rest of task and check out your emulator.
You need "VT-x supported processor" at least to run Android emulator with Hardware acceleration.
If you have enabled or installed "Hyper-V" in your windows 8 then please remove it and disable the "Hyper threading" and enable "Virtualization".
I've run into the same problem, I found the solution at http://developer.android.com/tools/devices/emulator.html#vm-windows
Just follow this simple steps:
Start the Android SDK Manager, select Extras and then select Intel Hardware Accelerated Execution Manager.
After the download completes, run [sdk]/extras/intel/Hardware_Accelerated_Execution_Manager/IntelHAXM.exe
Follow the on-screen instructions to complete installation.
I have a pc with intel c2d without hardware accelaration i am having same problem in android studio. firstly i get bored with android studio and installed eclipse+sdk+adt then i have installed every thing and started emulator it worked then the same emulator worked in android studio for direct launching application in android studio and i have also runned the sample app that emulator so you can run android studio without virtualization technique even your processor does not sopport vt-x
When Run 'app' (green triangle):
In Device Chooser select Launch emulator and click the button [...]
Rigth click on Nexus (or other) click on Duplicate
In the O.S. (Android 6.0 example) click change:
Clic on Show downloadable system images.
Look for armeabi-v7a O.S. and click download.
Set this O.S. in the device.
Finish, and choose this Device for the emulation.
So I am a beginner to Android development and decided I would start learning based on the Android site itself how to make android apps. I thought a good place to start would be making my first emulator and running a minimal hello world program.
Using the Android Guide:
http://developer.android.com/tools/devices/managing-avds.html
It instructs how to make an emulator but the appearance of my AVD is radically different than the one they are using and I have encountered an error with it which I cannot find online literature to fix:
Specifically the process they give to make a new virtual device is hit "new" (in my case I am guessing that is the same thing as "create" since there is no "new "button on the most recent version of AVD manager)
And after that a form appears, I am supposed to fill up the form with relevant Virtual Device information and hit "ok" to create the device.
Except... after filling all the information I still cannot hit "ok". The button is greyed out, and I have done everything exactly as the android guide told me. What should I do to fix this? I have the form displayed below notice the greyed out ok button on the bottom right corner.
The problem is in the field: "CPU/ABI: No System images installed for this target". To rectify, open up the Android SDK Manager and download/install a System Image.
For example, when I open the Android SDK Manager, I expand the Android 4.4.2 (API 19) and install the ARM EABI v7a System Image (and for giggles, I might install the Intel image as well).
Whilst there, make sure you have other bits you might need for development (but not necessarily for the emulator) like the SDK and I'd definitely recommend downloading the sources, samples, SDK Tools, SDK Platform-tools and SDK Build-Tools.
You can use a later API version if you like, but API 19 has been released into production at the time of writing.
After which, you can restart the AVD and you'll be able to select the a CPU and create the emulator.
I suggest you should add all the "Android System Images" to your Android SDK Manager.
For that,
Open your SDK Manager from Windows -> Android SDK Manager.
Now expand each Android API versions then check Google and Intel X86 both system images and also check Intel HAXM Installer in the Extras.
Download and install them.
After successful install, the status changes to be as "Installed".
Try this also:
Now if your system have a Processor that have a feature called as Intel Virtualization Technology, then Intel X86 images will be huge benefit for you. because it supports Intel® Hardware Accelerated Execution Manager (Intel® HAXM).
To check that your processor support HAXM or not : Click Here
You need to manually install the Intel HAXM in your system. Follow these steps for that.
First of all go to - adt -> extras -> intel -> Hardware_Accelerated_Execution_Manager
Make sure that Intel Virtualization is enabled from BIOS Settings.
Now install Intel HAXM in your system and select amount of memory(i prefer to set it as default value).
After installation create new AVD which should have a Target of API Level xx
Now set the CPU/ABI as Intel Atom(x86).
If you are on Windows then do not set RAM value more than 768 MB while setting up an emulator.
Run the emulator. It will be blazing fast then ordinary one.
Hope it will be helpful for you. :)
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.