Just upgraded from Android Studio 4.1 to ArcticFox 2020.3.1.
Emulator was working fine in 4.1 but now nothing shows. Sometimes the status line says 'waiting for emulator to start...' for a few seconds, but otherwise nothing, no error messages.
As part of the upgrade, it recommended to use the HAXM accelerator which I installed.
I have checked this thread but it hasn't helped (it refers to a much older version of Studio).
The app runs OK on a real device.
I have tried adding a new (different) virtual device; same problem. I also have the same problem on two upgraded PCs (Windows 10)
Found the answer in these two threads:
emulator process terminated
cannot find vulkan-1
But puzzled why these weren't offered as solutions when I added my question.
Related
I have the adb.exe at "../AppData\Local\Android\Sdk\platform-tools\adb.exe" and even checked the virus chest of antivirus everything is fine.
But still get the dialogue box saying
"adb.exe is obsolete and has serious performance problems".
What worked out for me was after
Create Virtual Device
Choose a device
select Q API Level 29 image with target as Android 10.0 (Google APIs)
not just Android 10.0
and proceed as usual.
Hope its useful for you!
Maybe a bit late but the accepted solution didn't work for me. However the following did:
SDK Manager -> SDK Tools
Delete current Android SDK Build-Tools even if it is the latest version. In my case, I observed it also uninstalled a lot of previous versions
Restart Adroid Studio
Install the latest Android SDK Build-Tools
Restart Adroid Studio
I suspect the problem happened due to some sort of error in incremental updates of adb
First post--be gentle. Can't find any posts on Android Studio 4.0, so I hope this isn't a repeat. I updated Android Studio from 3.6.3 to 4.0 on Windows 10 (1909). Had created a couple of virtual devices in 3.6.3 (a Pixel 2 running API 28 and a Pixel 3 running API 29)--both worked great in AS-3.6.3 and I could develop apps, compile, load, and run them with no problem.
After the update to AS-4.0, the virtual devices no longer appear in the devices box at the top of the GUI--it just says "No Devices". When I open the AVD Manager, I can see them, and I can start them (although when I start them I get a pop-up saying "AVD Manager: Unable to locate adb"), but I can't get any code to download and execute on it. On the Pixel 3 emulator, I also get another pop-up saying "Detected ADB: Could not automatically detect an ADB binary.", and it gives instructions to resolve it, which don't make any difference (jump into extended controls and toggle "Use detected ADB location").
When I try to open a past project and run it, I get the same behavior--no devices found.
I've also tried making new emulators, hoping the new setup would recognize them, but to no avail. Tried starting and restarting AS, as well as the computer, also to no avail. I have Android SDK Build-Tools 30-rc4, the latest Android SDK Command-line Tools, Android Emulator 30.0.12 Android SDK Platform-Tools 30.0.1, and the Intel x86 Emulator Accelerator all installed.
I've Googled and spoken words of fierce power over this for several days now. Any suggestions for how to get AS-4.0 to recognize the emulators? I've resisted uninstalling everything and starting over--was hoping it was just a configuration thing.
Thanks in advance,
Uber
After some more Googling, I found the answer here (I think my constraint of wanting an answer for AS-4.0 specifically kept me from finding it):
Could not automatically detect an ADB binary - Android Studio
I had to redownload the SDK platform-tools zip file and reinstall it. I don't know why the old one got messed up with the migration from AS-3.6.3 to 4.0, but there you go--such is life with complicated software.
As soon as I replaced the old platform-tools directory with the new one, all my old emulators showed up and I was back in business.
Thanks anyway!
Uber
I've searched all over the web for the past 3 days and can't seem to find a solution. I've done everything mentioned in this post:
Android emulator not showing in Visual Studio
It seems all the 'working' solutions to this problem has been stated in what this guy says he did in his original post, including restarting ADB server (kill and start), restarting my computer, reinstalling emulator and HAMX, installing and running as an admin, changing the timeout delay, reinstalling almost everything, making sure my emulator is installed, etc.
It keeps saying Gradle build finished in 475ms, etc and then waiting for target device to come online for like 5-10 minutes and nothing happens. No emulator shows up. I can't seem to find the solution to this and I am on the verge of giving up, I really need Android Studio to work so I can start on my app.
Can I please get some guidance with this?
If it's relevant, I'm using a Mac.
Have you tried this. Go to the emulator settings and set the Graphics Emulation mode to Software GLES. The default mode will be automatic. I am not sure how it works, but that worked for me on two Linux machines. Being software emulation, the performance of the emulator will not be as good as when using hardware graphics. It seems to be a bug with the SDK.
For me the only thing that worked in macos was to disable docker before starting Studio.
Wipe the data of your Android virtual Device and then start the emulator.
I was using Android studio 4.2 and faced this issue.
No Solutions worked for me so I just erased android studio files. Updated to Android Studio Arctic Fox.
Link to remove android studio files from mac : How to completely uninstall Android Studio on Mac?
For Windows : How to completely uninstall Android Studio from windows(v10)?
Yesterday, I installed Android Studio's latest version on Ubuntu. Everything ran fine, until I ran the "Hello World!" program. It asked me to create a virtual device. While creating the device, it shows me an error that the AVD manager cannot find a system image. This makes no sense since I have already installed the latest SDK (API level 25, Android 7.1.1). I downloaded the system image from the AVD manager itself, but to no avail.
Can someone help me sort the damn thing out? I switched from Windows to Linux due to the plethora of problems with Android Studio on Windows. But the thing's bugging once again. Here is a screen shot:
I recently upgraded Android Studio to 2.0 (Windows) which broke the emulator.
The symptom is that the emulator starts a (single thread) process that takes about 100% of its CPU. Nothing shows on the screen.
Of course, this worked like a charm before the update.
Few things I tried:
Used an AVD created before and after the update
Increased AVD memory to 1G
Delete / Install Android Studio
Used different CPU Architecture (Arm & x86)
Used different versions of API (21 & 23)
I had the same problem I had to reinstall android studio all over again, After that open your SDK monitor press on launch stand alone SDK manager, There scroll down and check if the emulator is installed properly if not install it.
I hope this answer helped you since that's what I did and it works.
A temporary solution:
Go into the AVD Manager, select the Virtual device, and click "Edit"
Find "Emulated Performance" -> Graphics, and switch that from auto (or hardware) to Software.
It won't have quite the performance, but this worked for me. Seems to be that Android Studio 2.0 doesn't play well with certain graphics cards or something.