Formatted my computer with windows 8.1 pro and upgraded it to windows 10 pro, both x64.
Enabled Hyper-V on BIOS and on Windows Features, but no success. Disabled and enabled again, rebooted and nothing... Also reinstalled Visual Studio Emulator for Android and never works.
Always I get the error "You have been added to the Hyper-V Administrators security group. Please sign out of your computer for the permissions to take effect" when I try to run a android device.
What could I do for solve this?
Screenshots below:
You should install Intel HAXM instead of enabling Hyper-V for the Android emulator. Only the Windows Phone emulators require Hyper-V, and HAXM and Hyper-V cannot be active simultaneously, which means that enabling one disables the other.
Also, dealing with emulators from Visual Studio itself is not recommended as it proved to be messy and unrealiable. Instead, you should manage the entire Android SDK and its emulators from the Android SDK tools standalone installer (not Android Studio). Follow these instructions to install the Android SDK tools 24 standalone GUI and immediately update them to SDK tools 27, which includes the latest Android emulators.
Then, create the emulators from Android AVD Manager, and start your desired emulator. Whenever you deploy to emulator from Visual Studio, it will use the already running emulator, so you don't need to choose one from VS itself.
Related
I have a question about running an app through the emulator on android studio.
My emulator device is able to turn on, but when running the app, install never completes so the app times out. I have tried invalidating cache and restarting, and I have installed the sdk platforms that are the same as the emulators and project, but these changes did not work. My computer cannot install emulator hypervisor driver for AMD processors or intel x86 Emulator accelerator, but I don't think it is necessary for the app to run since my emulator can turn on, right? also, any app has never successfully run on android studio.
The is no code other than the hello world that comes up automatically. This is an empty project with a minimum sdk of api: android 4.1. The device I am using is a pixel 2 with an api of 22. (size on disk 3.5 GB) for tools, I have android SDK build-tools 33, android emulator (31.3.10), and android sdk platform- tools (33.0.3) installed.
I have tried every forum that has the same issue as me but if you think there is one that can help me, please share it thanks.
Android Emulators aren't always the best so expect random failures. This is what I would try:
Make sure the app compiles properly (make sure you see BUILD SUCCESSFUL in your bottom "Build" Tab in Android Studio)
Make sure you have updated Android Studio and Android Emulator, Android Build Tools, SDKs etc.
Create and use a device with a higher API version. Ideally one with Play Store.
Depending on your development machine you might want to try a different architecture (ABI). Try x86 or x86_64 instead of what you've already tried.
In rare cases your existing emulator images get corrupted. Uninstall them in your SDK manager (Show Package Details) and install them again.
If possible try running the app on a real device (follow online instructions to enable USB debugging etc.) to verify the emulator is the problem.
I have been trying to install Xamarin for the first time. I have it installed and i have the first dummy project open. I haven't made any changes to it i am just trying to run it. (F5)
The first thing i am getting is
I click the learn more which brings me to Hardware Acceleration for Emulator Performance (Hyper-V & HAXM)
Hyper-v is enabled via bios on this machine i know this becomes i also have docker on this machine which runs just fine using hyper-v. I ran though all the settings in this webpage and it doesnt seam to fix the problem.
I searched the whole page i cant find anything about what windows spring creators update (Redstone 4) is.
If i go though Tools -> Android -> Android device manager. I get the following screen.
The here link brings me to the same place as before. (Hyper-V & HAXM)](https://learn.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/hardware-acceleration?tabs=vswin)
If i try and run anyway the emulator starts but its not starting with the project.
SystemInfo
Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.
Hyper-v is running Docker has been using it for months. Yes i disable docker when running this project.
winver
Windows version says Version 1803 (OS build 17134.228) .
Visual studio version
Visual studio 15.8.2
Tools > Android > Android SDK Manager in Visual Studio.
Android emulator is at 27.3.9 Android SDK tools is at 26.1.1
What am i doing wrong how do you run an android project using Xamarin.
How to start Xamarin emulator first time (Redstone 4)
If you want to use Hyper-V to accelerate your Android Emulator, you needs verifying support for Hyper-V:
Verify that your Windows Version is at least 1803
Enable windows features
Install Visual Studio 15.8 or later
Install the Android Emulator package 27.2.7 or later
Make sure you have enabled the Virtualization Technology on your device. You could find it via:
Task Manager -> Performance -> Virtualization -> Enable or Disable.
Can I run Android Studio and Android SDK emulator in a Microsoft hyper-v virtual machine? Please read carefully.
I already use Hyper-V a lot for other purposes. Now I need to develop a app for Android.
I've installed a new virtual machine (windows 10) and installed Android Studio. I cannot run the android emulator because it's lacking the 'intel HAXM software'.
I read a lot about that it's not possible to install Hyper-V NEXT to Android Studio, but non of the post actually say anything about installing in a Hyper-V machine.
Refer to this link:
How to run Android Studio on Windows without disabling Hyper-V
The solution (if you do not want to disable Hyper-V) is to use Microsoft’s Android emulator, which is a free download here.
In order to use this with Android Studio, you need to run the emulator first. Then, in Android Studio, go to Run > Edit Configurations... and select Show Device Chooser Dialog under Deployment Target Options.
Run your project, and select the VS Emulator, ignoring the invitation to “Turn off Hyper-V”.
Hyper-V added support for nested virtualization in the Windows 10 Anniversary Update (released August 2016) and Windows Server 2016. However, the only Microsoft-supported usage of nested virtualization is running Hyper-V within the VM, not HAXM. From the official documentation, "Virtualization applications other than Hyper-V are not supported in Hyper-V virtual machines, and are likely to fail."
That said, the change log for the latest release of HAXM reports that Intel "Fixed an issue with Hyper-V nested virtualization support, which had prevented Android Emulator from booting." So while it isn't supported by Microsoft, it seems running HAXM nested in a Hyper-V VM may be possible.
If that's the case, to get HAXM working in a Hyper-V VM, you will need to enable nesting for that VM. Run this command on the VM while it is in the OFF state:
Set-VMProcessor -VMName <VMName> -ExposeVirtualizationExtensions $true
After that, you should be able to install the latest version of HAXM within the VM, allowing use of the Android Emulator. Again, I haven't personally verified this, and it isn't supported by Microsoft, so your mileage may vary.
Full disclosure: I work at Microsoft on the Hyper-V team.
[Edit 7/2/2018]: Android Emulator support for Hyper-V acceleration was announced earlier this year, and is currently in preview. See the announcement post for details.
Microsoft posted a link to allow Hyper-V as hardware accelerator for android emulator run in windows.
The link is here
Here is the instructions.
Enter About in the Windows search box.
Select About your PC in the search results.
Scroll down in the About dialog to the Windows specifications section.
Verify that the Version is at least 1803.
Enter windows features in the Windows search box and make sure both Hyper-V and Windows Hypervisor Platform are checked.
Open SDK manager in Android Studio, make sure your Android Emulator version is at least 27.2.7.
Restart your computer, and relaunch your Android Emulator in AVD Manager in Android Studio.
Confirmed: Running Windows 10 version 1803, with Hyper-V and Windows Hypervisor platform enabled, Android Studio's Emulator works. I am using Android Studio 3.2.1 and Android Emulator 28.0.22.
Just make sure before you start with the steps suggested by lotosbin you complete the following:
Open an admin command prompt and enter the following; then restart the emulator.
`reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Android SDK Tools" /v Path /d %localappdata%\Android\sdk`
Or update the registry manually:
In regedit, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node.
Create a new key named Android SDK Tools(if not there already).
Navigate to that key.
Create a new string value named Path. Set its value to the location of your Android SDK, which will be like C:\Users\YourName\AppData\Local\Android\sdk.
Microsoft has announced a better solution
Today, at Build 2018, we announced a preview of the Google Android
emulator that’s compatible with Hyper-V, available on the Windows 10
April 2018 Update. This enables developers with Hyper-V enabled on
their machines to use a hardware accelerated Android emulator, without
needing to switch to Intel’s HAXM hypervisor. Amazing work was done by
the Windows Hyper-V team, with help from the Xamarin team, to make to
this happen.
Just to complement #lotosbin's answer and add an additional information. This information is regarding when you are trying to start your app in Microsoft's standalone Android emulator from Android Studio.
On the Select Deployment Target window there are two sections namely:
Connected Devices - It shows up physical android devices attached to your computer through USB port e.g. mobile, tablet if you want to deploy your app into an actual device
Available Virtual Devices - It shows up Android virtual emulators which are build from specific device definition e.g. Nexus 5X API 28
Interestingly, Microsoft's Android emulator shows up in Connected Devices section. So Android Studio treats Microsoft's Android emulator as a physical device instead even though it is a virtual emulator only. Please see the screenshot below:
Additionally, you can check the health and current status of Microsoft's Android emulator inside Hyper-V Manager also as shown in below screenshot:
Can I run Android Studio and Android SDK emulator in a Microsoft hyper-v virtual machine? Please read carefully.
I already use Hyper-V a lot for other purposes. Now I need to develop a app for Android.
I've installed a new virtual machine (windows 10) and installed Android Studio. I cannot run the android emulator because it's lacking the 'intel HAXM software'.
I read a lot about that it's not possible to install Hyper-V NEXT to Android Studio, but non of the post actually say anything about installing in a Hyper-V machine.
Refer to this link:
How to run Android Studio on Windows without disabling Hyper-V
The solution (if you do not want to disable Hyper-V) is to use Microsoft’s Android emulator, which is a free download here.
In order to use this with Android Studio, you need to run the emulator first. Then, in Android Studio, go to Run > Edit Configurations... and select Show Device Chooser Dialog under Deployment Target Options.
Run your project, and select the VS Emulator, ignoring the invitation to “Turn off Hyper-V”.
Hyper-V added support for nested virtualization in the Windows 10 Anniversary Update (released August 2016) and Windows Server 2016. However, the only Microsoft-supported usage of nested virtualization is running Hyper-V within the VM, not HAXM. From the official documentation, "Virtualization applications other than Hyper-V are not supported in Hyper-V virtual machines, and are likely to fail."
That said, the change log for the latest release of HAXM reports that Intel "Fixed an issue with Hyper-V nested virtualization support, which had prevented Android Emulator from booting." So while it isn't supported by Microsoft, it seems running HAXM nested in a Hyper-V VM may be possible.
If that's the case, to get HAXM working in a Hyper-V VM, you will need to enable nesting for that VM. Run this command on the VM while it is in the OFF state:
Set-VMProcessor -VMName <VMName> -ExposeVirtualizationExtensions $true
After that, you should be able to install the latest version of HAXM within the VM, allowing use of the Android Emulator. Again, I haven't personally verified this, and it isn't supported by Microsoft, so your mileage may vary.
Full disclosure: I work at Microsoft on the Hyper-V team.
[Edit 7/2/2018]: Android Emulator support for Hyper-V acceleration was announced earlier this year, and is currently in preview. See the announcement post for details.
Microsoft posted a link to allow Hyper-V as hardware accelerator for android emulator run in windows.
The link is here
Here is the instructions.
Enter About in the Windows search box.
Select About your PC in the search results.
Scroll down in the About dialog to the Windows specifications section.
Verify that the Version is at least 1803.
Enter windows features in the Windows search box and make sure both Hyper-V and Windows Hypervisor Platform are checked.
Open SDK manager in Android Studio, make sure your Android Emulator version is at least 27.2.7.
Restart your computer, and relaunch your Android Emulator in AVD Manager in Android Studio.
Confirmed: Running Windows 10 version 1803, with Hyper-V and Windows Hypervisor platform enabled, Android Studio's Emulator works. I am using Android Studio 3.2.1 and Android Emulator 28.0.22.
Just make sure before you start with the steps suggested by lotosbin you complete the following:
Open an admin command prompt and enter the following; then restart the emulator.
`reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Android SDK Tools" /v Path /d %localappdata%\Android\sdk`
Or update the registry manually:
In regedit, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node.
Create a new key named Android SDK Tools(if not there already).
Navigate to that key.
Create a new string value named Path. Set its value to the location of your Android SDK, which will be like C:\Users\YourName\AppData\Local\Android\sdk.
Microsoft has announced a better solution
Today, at Build 2018, we announced a preview of the Google Android
emulator that’s compatible with Hyper-V, available on the Windows 10
April 2018 Update. This enables developers with Hyper-V enabled on
their machines to use a hardware accelerated Android emulator, without
needing to switch to Intel’s HAXM hypervisor. Amazing work was done by
the Windows Hyper-V team, with help from the Xamarin team, to make to
this happen.
Just to complement #lotosbin's answer and add an additional information. This information is regarding when you are trying to start your app in Microsoft's standalone Android emulator from Android Studio.
On the Select Deployment Target window there are two sections namely:
Connected Devices - It shows up physical android devices attached to your computer through USB port e.g. mobile, tablet if you want to deploy your app into an actual device
Available Virtual Devices - It shows up Android virtual emulators which are build from specific device definition e.g. Nexus 5X API 28
Interestingly, Microsoft's Android emulator shows up in Connected Devices section. So Android Studio treats Microsoft's Android emulator as a physical device instead even though it is a virtual emulator only. Please see the screenshot below:
Additionally, you can check the health and current status of Microsoft's Android emulator inside Hyper-V Manager also as shown in below screenshot:
I an having trouble debugging my native Android app. My Visual Studio 2015 (preview) installation does not show any emulator in the dropdown list.
I saw one comment here saying that Hyper-V must be enabled. Is that true? If yes, how to enable Hyper-V on my Windows 7 x64 machine? Is it possible to install Hyper-V on Windows 7 x64?
Your Windows 7 machine should already have Hyper-V on it. You may need to reboot, get into the BIOS settings and look for a switch that enables Hyper-V. A lot of manufacturers disable it by default.
Once you've done so, take a look at http://developer.android.com/tools/devices/emulator.html for more instructions on downloading and running emulators.
There's a new Android emulator written by Microsoft included with Visual Studio 2015 and it requires Hyper-V. Hyper-V is not available for use on a Windows 7 guest OS. You will have to upgrade to Windows 8 Pro (you'd probably choose 8.1) to use the new emulator.
It might still be possible to use the "old" Google-provided emulator with VS 2015 but I haven't found information about that.