The google repository you got linked was it, but it's outdated now. Open Android Studio (in rosetta, yes), download an ARM64 image from the SDK manager and create an AVD. It will work ( crashed the first time for me, but worked afterwards). Disregard Android Studio's warning about your CPU not having vt-d enabled. The emulator can be used to run ARM64-based Android apps on a Mac. The native hardware virtualization of the M1 SoCs is used via Qemu. This is the same tool that is also used to virtualize Windows on the M1. ARM32 applications do not work - the list of restrictions is quite long overall. Google emphasizes that the emulator is a first preview. Android emulator on Mac M1 You’re now watching this thread and will receive emails when there’s activity. Click again to stop watching or visit your profile/homepage to manage your watched threads. Android emulator on Mac M1 You’re now watching this thread and will receive emails when there’s activity. Click again to stop watching or visit your profile/homepage to manage your watched threads.

-->

This article explains how to use the Android Device Manager to createand configure Android Virtual Devices (AVDs) that emulate physical Androiddevices. You can use these virtual devices to run and test your appwithout having to rely on a physical device.

After you have verified that hardware acceleration is enabled (asdescribed inHardware Acceleration for Emulator Performance),the next step is to use the Android Device Manager (also referred toas the Xamarin Android Device Manager) to create virtual devices thatyou can use to test and debug your app.

Android Device Manager on Windows

This article explains how to use the Android Device Manager to create,duplicate, customize, and launch Android virtual devices.

You use the Android Device Manager to create and configure AndroidVirtual Devices (AVDs) that run in theAndroid Emulator.Each AVD is an emulator configuration that simulates a physical Androiddevice. This makes it possible to run and test your app in a variety ofconfigurations that simulate different physical Android devices.

Requirements

To use the Android Device Manager, you will need the following items:

Visual Studio 2019 Community, Professional, or Enterprise.
OR Visual Studio 2017 version 15.8 or later is required. Visual StudioCommunity, Professional, and Enterprise editions are supported.
Visual Studio Tools for Xamarin version 4.9 or later.
The Android SDK must be installed (seeSetting up the Android SDK for Xamarin.Android).Be sure to install the Android SDK at its default location if itis not already installed: C:Program Files (x86)Androidandroid-sdk.
The following packages must be installed (via theAndroid SDK Manager):
- Android SDK Tools version 26.1.1 or later
- Android SDK Platform-Tools 27.0.1 or later
- Android SDK Build-Tools 27.0.3 or later
- Android Emulator 27.2.7 or later.
These packages should be displayed with Installed status as seen inthe following screenshot:

Launching the Device Manager

Launch the Android Device Manager from the Tools menu byclicking Tools > Android > Android Device Manager:

If the following error dialog is presented on launch, see theTroubleshooting section for workaroundinstructions:

Main Screen

When you first launch the Android Device Manager, it presents a screenthat displays all currently-configured virtual devices. For eachvirtual device, the Name, OS (Android Version), Processor,Memory size, and screen Resolution are displayed:

When you select a device in the list, the Start button appears onthe right. You can click the Start button to launch the emulatorwith this virtual device:

After the emulator starts with the selected virtual device, theStart button changes to a Stop button that you can use to haltthe emulator:

New Device

To create a new device, click the New button (located in the upperright-hand area of the screen):

Clicking New launches the New Device screen:

To configure a new device in the New Device screen, use thefollowing steps:

Give the device a new name. In the following example, the new deviceis named Pixel_API_27:
Select a physical device to emulate by clicking the Base Devicepull-down menu:
Select a processor type for this virtual device by clicking theProcessor pull-down menu. Selecting x86 will provide thebest performance because it enables the emulator to take advantageof hardware acceleration.The x86_64 option will also make use of hardware acceleration,but it runs slightly slower than x86 (x86_64 is normallyused for testing 64-bit apps):
Select the Android version (API level) by clicking the OSpull-down menu. For example, select Oreo 8.1 - API 27 to createa virtual device for API level 27:
If you select an Android API level that has not yet been installed, theDevice Manager will display A new device will be downloadedmessage at the bottom of the screen – it will download andinstall the necessary files as it creates the new virtual device:
If you want to include Google Play Services APIs in your virtualdevice, enable the Google APIs option. To include the GooglePlay Store app, enable the Google Play Store option:
Note that Google Play Store images are available only for some basedevice types such as Pixel, Pixel 2, Nexus 5, and Nexus 5X.
Ld player for mac os. Edit any properties that you need to modify. To make changes toproperties, seeEditing Android Virtual Device Properties.
Add any additional properties that you need to explicitly set. TheNew Device screen lists only the most commonly-modifiedproperties, but you can click the Add Property pull-down menu(at the bottom) to add additional properties:
You can also define a custom property by selecting Custom.. atthe top of the property list.
Click the Create button (lower right-hand corner) to create thenew device:
You might get a License Acceptance screen. Click Accept ifyou agree to the license terms:
The Android Device Manager adds the new device to the list ofinstalled virtual devices while displaying a Creating progressindicator during device creation:
When the creation process is complete, the new device is shown inthe list of installed virtual devices with a Start button,ready to launch:

Edit Device

To edit an existing virtual device, select the device and click theEdit button (located in the upper right-hand corner of the screen):

Clicking Edit launches the Device Editor for the selected virtual device:

The Device Editor screen lists the properties of the virtual deviceunder the Property column, with the corresponding values of each property inthe Value column. When you select a property, a detailed descriptionof that property is displayed on the right.

To change a property, edit its value in the Value column.For example, in the following screenshot the hw.lcd.density propertyis being changed from 480 to 240:

After you have made the necessary configuration changes, click the Save button.For more information about changing virtual device properties, seeEditing Android Virtual Device Properties.

Additional Options

Additional options for working with devices are available from theAdditional Options (…) pull-down menu in the upperright-hand corner:

The additional options menu contains the following items:

Duplicate and Edit – Duplicates the currently-selecteddevice and opens it in the New Device

M1 Mac Android Emulator