Xamarin Android Player cannot run API emulators 21 or higher

Question

I am using Xamarin Studio and Xamarin Android Player on my Windows 10 PC.

I'm having trouble starting Lollipop / Marshmallow devices (API 21/23) using XAP, but on the other hand, starting Kitkat (API 19) works prefectly.

I downloaded the required SDK for Android, tried to reinstall everything again and again, but nothing works.

This seems to be due to wiring because it is not a problem with Virtual Box, neither with my PC, nor with my XAP installation (if that was, why does Kitkat work?).

I tried every solution I could find, but nothing works.

Any ideas on what might cause this problem? (If additional information is required, I will gladly add :)

EDIT

It doesn’t matter if I run the device through VS / XS / XAP. It all comes down to the same problem, but for simplicity, let me say that I run them directly through XAP. Here is a screenshot of what happens when I launch Lollipop (this is API 22, not 21, for some strange reason):

Within 5 minutes, the following occurs:

Than, forever:

And after a few hours he talks about loading or something like that, and then reboots to the first position.

With Kitkat, it is just beginning :).

Answer 1

you probably missed the intel HAXM update .. it might be possible duplication: Android 5.0 (API level 21) AVD does not start Intel Atom x86_64

Answer 2

Firstly, it is difficult to identify the problem without additional information. Please list or a screenshot of the build error that you get when trying to debug your application on the XAP emulator.

But in agreement ... during the past week I had a problem with similar symptoms. In my case, I had to update the project packages so that the Xamarin Forms project runs on higher Android APIs.

Help on how to update packages: https://developer.xamarin.com/guides/cross-platform/application_fundamentals/nuget_walkthrough/#Package_Updates

Answer 3

It is possible that hyper-v is causing the problem: "VirtualBox and Hyper-V cannot coexist on the same computer . "

Try disabling it using bcedit as described in the link. For more information see this discussion.

Answer 4

After starting the xamarin-android player, manually start the virtual box. You should see the device indicated on the left. There is a good chance that he will say “stalled”. If it says nothing but Launch, try reselling it or launching it.

Answer 5

I also had problems with XAP, and instead I decided to use Genymotion .

Answer 6

Have you tried Genemotion

I think this is the best Android emulator.

Answer 7

I would post a comment, but my reputation is too low. I do not know if this emulator works with Xamarin studio, but if you are using Visual Studio, this may be an option for you.

Answer 8

Here is the solution:

I had a similar problem and fixed the problem as follows.

• remove existing device simulator

• install simulator again

• deploy the solution again.