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.
Related
After upgrade Android studio to 4.1.2 and enable the option of "Launch in a tool Windows" (Settings -> Tools -> Emulator) in my windows 10 machine, the emulator stop working.
The error i getting is:
The emulator process for AVD Pixel_3_API_29 was killed.
When i disable the "Launch in a tool Windows" the emulator start without problem.
Make sure you also have the latest version of the Android SDK tools by going into Tools -> SDK Manager and then click on the SDK tools tab to check that every package has the latest version.
I would personally recommend sticking to using the emulator in a separate window until a new update since even when it works, the "tool Window" emulator still has some bugs and advanced options are yet unavailable.
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.
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 recently got into Xamarin development. I have a lot of experience in Xcode making iOS apps and the iOS side was very straight forward. Now I'm trying to implement Android. I downloaded a Hello World example to get my bearings. When I run it I have no problems getting the simulator to show up (MonoForAndroid_API_10 and MonoForAndroid_API_12) but the actual application doesn't run, and does not show up anywhere on the simulator. Essentially whenever I use run or run with in Xamarin on Android, it pulls up a fully functioning, albeit empty simulator.
How do I get my application to run on the emulator?
Like the other commenters, this is most likely just a symptom of slow emulator on your machine. I'm running Xamarin-Android development on my 2010-era OSX machine in mavericks with 8GB RAM, and it is slow-slow-slow, but usable. Try to find the Intel x86 speeds improvements (look for HAXM) and you will find that the emulator will be much much faster.
And yeah, get a real handset and plug it in to your computer: always much faster than emulation.
later edit Get Genymotion for Mac OSX or for PC/Windows or PC/Linux. It's way way way faster than the other emulators. I have since found that this is as fast, or faster, than running the App on my connected Android phone. It's certainly simpler in not having to have the device plugged into one of my USB ports, and allows me to code and test on the train. http://www.genymotion.com/
Don't know if my issue was the same but finally this troubleshooting helped me to run emulator https://msdn.microsoft.com/en-us/library/mt228282.aspx#ADB.
I was missing key Android SDK Tools with string value Path in registry Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node
I've created it manually and it worked.
UPDATE
Before I got the issue with running emulator, I couldn't see it in Visual Studio. The reason was I've installed VS Android Emulator through standalone installation, not through VS Installer. It had to be installed there as well.
I had the similar issue, and then I deleted the existing device simulator and reinstalled again and it started working.
As I use a different SDK, in my case
Go to Tools > Options > Xamarin and set the Android SDK path.
Sometime Visual Studio changes this configuration;
2020 Update:
I followed the most voted comment, however, with Visual Studio 2019 updated recently, the steps have changed a little. Here is what previously worked:
WHAT WORKED BEFORE
"Don't know if my issue was the same but finally this troubleshooting helped me to run emulator https://msdn.microsoft.com/en-us/library/mt228282.aspx#ADB. I was missing key Android SDK Tools with string value Path in registry Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node
I've created it manually and it worked."
WHAT TO DO INSTEAD
Nothing. Don't mess with the path.
WHAT WORKED BEFORE
"Before I got the issue with running emulator, I couldn't see it in Visual Studio. The reason was I've installed VS Android Emulator through standalone installation, not through VS Installer. It had to be installed there as well."
Previous instructions image
WHAT TO DO INSTEAD
a. Go to Tools located at the top of the VS window, Get Tools and Features, go to Individual components, using the search tool in the pop up box, search "emulator", once you get the result, make sure both Google Android Emulator (API Level 25)(local install) and Intel Hardware Accelerated Execution Manager (HAXM) (local install) are both checked.
b. Close the solution(s) and restart VS then reopen the solution(s).
c. To deploy the app on the emulator, click Start button to spin up the emulator, left click on your Android project, then click Deploy. You should be able to see your app on your emulator's app menu.
Updated Instructions image
Worked for ME
Sometimes you close the android Emulator but not POWEROFF the Emulator.
this problem happens when emulator shutdown un-properly.
Restart Your EMULATOR
First start your emulator
Then restart your emulator by pressing down the power button and select restart option in your android emulator.
I enabled Hyper-V acceleration based on microsoft documentations: https://learn.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/hardware-acceleration?tabs=vswin&pivots=windows#accelerating-with-hyper-v
Basically you need to turn on these two windows features from the control panel (Turn windows features on of off):
Hyper-V.
Windows hypervisor platform.
then from visual studio go to: Tools >> Android >> Android SDK manager >> Tools >> make sure that "Android emulator" version is 27.0.1 or higher, if not, you will find in the same screen a button below to update it.
I did this on windows 10 64-bit, with VS 2017 Community 15.9.5