#Android studio emulator 2.3 not working mac android
Rosetta 2 is amazing, but when it comes to the default Android Emulator it falls over because it can not run Kernel extensions and doesn't support VMs that are doing x86_64 virtualization. We are working on a native emulator that will run arm64 system images with virtualization on arm based Macs. There are still many issues, but apps work at a basic level. In AVD Manager go to the Other Images tab as by default it doesn't show the ARM64 images. Support for downloading the M1-based emulator was added to SDK Manager, so it's not necessary to go to the Github releases page to download a standalone. Now you should see "Virtual Device" under Device Connector (just next to build icon) Run your App and it should start in Native M1 Android Emulator. Android studio can currently run with the M1 chipset using Rosetta, that translate machine code from Intel to ARM. The latest Canary build of Android Studio (15 as of writing this) brings initial native support for M1 Macs. Thankfully, Google is working on a solution. Because this is a recent transition, Apple has built-in a compatibility layer to allow x86-based programs to run on M1 Macs, and it seems to work pretty well. The problem with this preview build is that you can't change the emulator device type As blunt as it may sound, but updating the emulator which you’re running could simply end your problem, for eg.
![android studio emulator 2.3 not working mac android studio emulator 2.3 not working mac](https://support.stylemixthemes.com/storage/stm-manuals/June2020/17.png)
![android studio emulator 2.3 not working mac android studio emulator 2.3 not working mac](https://www.vogella.com/tutorials/Android/img/androidstudio_create_avd70.png)
I'm running the emulator from Android Studio Arctic Fox, using Pixel 5 with API 31 Android 12 Preview 'S' arm64 (apparently has to run an arm64 image, to work on M1?) This is the first preview.
![android studio emulator 2.3 not working mac android studio emulator 2.3 not working mac](https://i.ytimg.com/vi/oRuEF3Iw554/hqdefault.jpg)
Information is provided in the previous answer. As I said in the previous post, these configurations are workarounds until stable versions are released, however, for me, they have been useful and I guess that someone in the same situation as me can benefit from that.