How to run Android Studio emulator on M1 Mac? - android-studio

I'm having a devil of a time using the Android Emulator on my new M1 Mac. My Android project compiles fine, and I can run it on a hardware device. But I'm not able to run it on the Emulator.
I followed instructions carefully, and set up an arm64-based emulator running API 31. When I press the "Run" button in Android Studio, the emulator opens and boots normally. However, Android Studio is never able to launch my app on it. I see a message "Waiting for all target devices to come online", and that's it.
I have of course tried restarting the emulator, restarting Android Studio, rebooting my computer, and wiping the data from the emulator. I have also made sure that Developer mode is enabled in the emulated Android environment and "USB Debugging" is turned on.
Another suggestion I saw was to un-check "Enable ADB Integration" in Android Studio. This option doesn't exist in my copy of Android Studio, although I did some further research and found that it is now called "Use libusb backend" instead. It is unchecked by default. I tried checking it anyway, and that didn't help.
I'm at a loss as to what to do next. I really need to be able to test my app in the emulator as my inventory of physical devices is fairly limited.
Thanks,
Frank

Download Android Studio Preview, create emulator (API 30 or S), now you can use emulator on both preview or stable Android Studio.

Related

Emulator not working in Android Studio Dolphin

I'm using AS 2021.3.1.17 on Windows 10.
My emulator is Pixel 3a with API 28 (Pie).
Whenever I try to run my code, it says "gradle build finished" and "launch succeeded" but the emulator page still says "No emulator are currently running."
I've tried:
reinstalling AS
updating the gradle plugin to 7.4
wiping the emulator data
cold boot
deleting it and making a new one
changing graphics from 'automatic' but it's disabled and unclickable
I've tried both solution on here and both doesn't work either.
Sometimes the Android Studio emulator does not work.
It is better to use similar software like GenieMotion along with the emulator.
In general, my suggestion is to migrate from Windows to Linux, Linux does not have many problems and your emulator works most of the time.
But be sure to use other emulators and don't limit yourself to your Android Studio emulator

Android Studio Emulator no more considering Swipes on Notebook Touchscreens as Input

I upgraded to Android Studio Bumblebee 2021.1.1 and realized that I cannot fully control the emulator with the touchscreen of my notebook anymore. Press events on the touchscreen (like mouse clicks) are still recognized correctly, but when I swipe nothing happens in the emulator.
Unfortunately, I did not note down the previous version of Android Studio that I had installed before, but with previous Android Studio versions I was always able to fully control the Android emulator via the touchscreen (as if I was actually testing my app on a real mobile phone).
My Google searches did not show any results related to this issue. Does anyone have an idea what the root cause could be and if it is possible to fix it?
Disabling launch in tool window in Settings::Tools::Emulator fixed it for me (requires emulator restart to take effect).
Credits to YuriBlaise on reddit

Stuck at the "waiting for all target devices to come online" message even though emulator is already running Android Studio 4.2.2

I am having trouble running an .apk file on an emulator in android studio (4.2.2). I am using an M1 chip Mac so I've chosen the S api with arm64 CPU. I cannot seem to get android studio to recognize the emulator is running. I've attached an image to show that the emulator is running properly . Any help would be appreciated! I've tried wiping the emulated data as well as reinstalling the emulator. For reference I am using Andoid Emulator version 30.7.5 and Android SDK tools version 30.0.2.
Wiping emulator data solved it for me

android studio emulator not selectable

I want to start coding with flutter, so i decided to download android studio.I created an avd called "Pixel 2 API 28" with android pie. When i want to select the pixel 2 as the avd device, the programme tells me that theres no avd, but on the right i can see the avd i created. When i put my cursor on it, it says "not applicable for the main.dart configuration". i have HAXM installed and Hyper-V is disabled, but i also tried it with both being active. I used the default code, which appears when you launch android studio.
Please help!!!
Edit:
I somehow managed to select it now, but i get this error: Running multiple emulators with the same AVD is an experimental feature. Please use -read-only flag to enable this feature.
Try starting the emulator from avd and then check if the device is showing up there if not try running
flutter devices
If the device shows there you can try running
flutter run -d <your-device-name>
You can also check whether the android sdk is configured with flutter try running
flutter config --android-sdk /path/andriod/sdk
hope it helps
Close Android Studio and Run again as Administrator
This is Only the solution i got after working hard for 3 days.

Android Studio selects wrong target device: always runs app on first selected one

How can I debug other than the first device in Android Studio?
I have two Genymotion devices Nexus 5 and Nexus 6, I can run both successfully but when I try to run/debug app from android studio no matter what device I choose it always runs first selected device.
Initially I thought it is genymotion issue but, it was not the case because same happens if I connect real device. Even though device appears in device chooser dialog but it looks like android studio internally doesn't see it.
Stopping debugging for current device before selecting new device helped me. (Red square)
Here is the solution
First: Go to run configuration in android studio
Then: Select the emulator you want
Finally: Run it
It's a bug in Android Studio, supossedly fixed in 1.5.1 but I have 1.5.1 and the bug is still present. Suggested workaround from Google dev is to "close the debug tab once it is done":
https://code.google.com/p/android/issues/detail?id=195167

Resources