VT-x enabled but Studio cant use it - android-studio

Good afternoon
I can't start virtual device I created because "VT-x or SVM not supported". Lets say VT-x is required for Oracle Virtualbox and other emulators, I have VT-x enabled and I use many emulators without problems.
"Troubleshoot" window of Studio provides an option to use AVD based on ARM system image (10x slower), but when I create new device, the "Next" / "Finish" buttons are disabled if I select any image except of x86 image.
I have VT-x enabled in BIOS. All tutorials how to fix similar bugs are related to enable of this option. Both type of Graphics in the VM options (hardware or Software) tested.
System: Windows 7 x64, AMD 6 core CPU, few years ago I was running Android Studio and AVDs at the same hardware under Windows 2003 (Probably, Studio 2.0) and it worked.
Any ideas?

Related

AMD Ryzen can't start Android Emulator: x86 Emulation Hardware Acceleration problem

I just installed Android Studio 3.3.2 on Windows 10 for the second time.
The first time i installed it i had no problems, i followed the steps to emulate an Android device by enabling SVM mode in bios and i have turned on Hyper-V feature in Windows (services included). Everything worked fine and i used that configuration for a month.
The processor i use is an AMD Ryzen 3 1300x.
Recently i installed Windows 10 on SSD as the main operating system and i downloaded Android Studio and all. Now i repeated all the steps i did the first time but it doesn't work and gives me "Emulator: emulator: ERROR: x86 emulation currently requires hardware acceleration!".
I tried to create 3 different devices with 3 different API Level: 28, 27 and 26. None of which worked.
The Android Studio version i installed is up to date and i downloaded it two times to be sure nothing was wrong with the files.

Android Studio Emulator error "Emulator: CPU acceleration status: Unable to open HAXM device: ERROR_FILE_NOT_FOUND"

I was able to use Emulator in the android studio without any problems. Since today I am getting the error as:
"Emulator: CPU acceleration status: Unable to open HAXM device: ERROR_FILE_NOT_FOUND".
Virtualization is enabled in BIOS, Intel Hardware Accelerated Execution Manager is installed in control panel - programs.
Also tried installing intelhaxm-android.exe from android sdk folder.
Please help with the error.
(i7/16gb/windows 10).
I solved that problem following steps
disabling Hyper-v
reinstalling HAXM
- Android studio -> SDK Manager -> SDK Tools -> Intel x86 Emulator Accelerator
Use Hyper-V instead of HAXM
I had the same error. Disabling Hyper-V avoided this error however it also stopped Docker from working properly.
To use both the Android Emulator and Docker on Windows 10 you need to:
Uninstall the Hardware Accelerated Execution Manager (HAXM)
Enable Hyper-V (check by running "Get-WindowsOptionalFeature -FeatureName Microsoft-Hyper-V-All -Online" in PowerShell running as Administrator)
Enable Windows Hypervisor Platform
Restart your computer
Enable Virtualization Technology in your computer's BIOS
Enable Hardware Enforced Data Execution Prevention in the BIOS
Enable Hyper-V and Windows Hypervisor Platform in Control Panel\Programs\Programs and Features -> Turn Windows features on or off
Enable Windows Hypervisor
Microsoft recommends that you use Hyper-V instead of HAXM to accelerate the Android emulator (detailed instructions).
I had the same issue, and solved it by disabling the Hyper-V hypervisor on Windows (from the "Activate/Deactivate Windows Functionalities" menu).
1st you uninstall the hexm everywhere also in android studio :
Download haxm version haxm-macosx_v7_0_0.zip from here Click Me
And Follow this steps : Haxm error in android studio 3.0 with windows requires a digitally signed driver
You can disable hyper-v or you can visit here
You can't run a VM-accelerated emulator inside another VM, such as a VM hosted by VirtualBox, VMWare, or Docker. You must run the Android emulator directly on your system hardware
For me Hyper-V hypervisor was not installed but still I got the error. What I did was I went to SDK Manager->SDK Tools and there I unchecked Intel x86 Emulator Accelerator clicked apply. Closed my Android studio and then reopened Android studio and again went to SDK Manager->SDK Tools and installed Intel x86 Emulator Accelerator by checking the item and clicking apply. And it started working fine.
I had the same problem, but I need Hyper-V for Docker.
So according to the official documentation, you have 3 choices (the second solution helped me):
You have an Intel processor and do not need to run Hyper-V at the same time as the Android Emulator.
Use Intel HAXM.
You have an Intel processor and do need to run Hyper-V at the same time as the Android Emulator.
Use WHPX.
You have an AMD processor.
Use WHPX.
See: https://developer.android.com/studio/run/emulator-acceleration#choose-windows-hypervisor

Android virtual device cannot start on Windows 7

Whenever I try to create a virtual device in Android Studio it always returns this error:
Intel HAXM is required to run this AVD.Enable VT-x in your BIOS security settings.
I have installed haxm 6.1.2 and it's not working. My computer is with Intel Core i5-2450m CPU. From Intel's website, it shows that it supports virtualization. But I have not been able to figure out how to enable the virtualization.
I think the virtualization isn't enabled in your BIOS settings.
Open boot menu by pressing F2 just before your system starts. Go to System Security. Make sure that VIRTUAL TECHNOLOGY VTX is checked, then hit F10 to save.
I hope this will work.

failed to Install HAXM while installing android studio

Failed to install intel HAXM.
This computer meets the requirments for HAXM, but intel virtualization technology (VT-x) is not turned on. HAXM cannot be installed until VT-x is enabled.
This message appears in between installation process, though after installation studio is running. Please let me know effects of HAXM installation failure on studio. How to correct??
HAXM will speed up your emulator (in my experience dramatically).
VT-x is enabled via your machines bios (look for references to virtualisation and ensure they are enabled).
There's little downside to enabling virtualisation in your bios to get the benefits of HAXM but if you don't want to bother it won't stop you using Android Studio.

Enabling Virtualization with no option in BIOS (Windows 8.1 basic, Samsung laptop)

I downloaded and installed Android Studio but I am not able to install Intel-HAXM (hardware-acceleration for the emulator) because I am unable to turn on virtualization.
I downloaded Speccy and it says virtualization is disabled.
I got into BIOS using F2 on startup and it says Intel VT-x is disabled but there is no option to enable it.
When I run Android Studio I get an error saying I need Intel-HAXM installed. When I try to install intel-HAXM (running as admin) I get an error saying "This computer does not support Intel virtualization technology. HAXM can not be installed".
My laptop is a Samsung NP355V5C running a recent update to Windows 8.1 Basic. I do not have Hyper-V as that is only available for higher levels of Windows 8.1
Also I don't believe I'm qualified to hack my BIOS. Please help me find a way to enable virtualization or to use Android Studio for development without using Intel-HAXM.
Please help me find a way to enable virtualization
See if there is a BIOS update from Samsung. It is possible, though somewhat unlikely, that they have added the ability to toggle Intel virtualization extensions in a BIOS update.
Outside of that, you would need to buy a new computer.
to use Android Studio for development without using Intel-HAXM
Use the ARM emulator images instead of x86 emulator images. These do not require HAXM. However, they run a lot slower than their x86 counterparts.
Here is a screenshot of the AVD Manager from Android Studio:
The "ABI" column indicates what CPU architecture that AVD will use. Those that are listed as armeabi-v7a are ARM images, and they will work on your notebook without HAXM.
However, as I mentioned, they will be very slow, particularly for higher-resolution screens. I suggest using some fairly low-resolution screens (e.g., Nexus S) to get by.

Resources