I need help to get what could be wrong with the emulator in Android Studio. After the last update it shows in this way (image). I've tried to update the emulator, delete the virtual device and create a new one but it still showing this size. Does anyone know if it's a configuration problem or where should I look for?
Emulator display
The problem is often caused by problems with HAXM\HAXM issues also conflicts with other virtualization technologies, that could be incorrect settings, or an out-of-date HAXM driver. Try to reinstalling the HAXM driver.
Related
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
When I first start the emulator in Android Studio I get an information message,
guest hasn't come online in 7 seconds retrying
I am curious as to how to stop this because while it is on my screen for about 40 seconds I cannot do anything in the emulator.
Actually 'Cold Boot Now' may work in this situation
I had the same problem. Selecting Cold Boot Now in AVD manager solves the problem.
But I have to open AVD manager each time when I want to launch Emulator and I just want to click on Run app button and select device, without opening AVD manager.
To solve this: open AVD manager -> Edit device -> Show Advanced Settings -> Boot option -> select Cold Boot instead of Quick boot.
tools->Android->AVD Manager
Choose the device then Cold Boot Now
maybe it's bug from intel haxm 6.2.1, because after i update i got same problem.
I solved by recreate emulator and testing again
I managed to solve this issue by updating the .ini file manually. (I was not able to find a corresponding setting in the GUI.)
The location of the .ini file, relative to your home directory, is:
~/.android/avd/MyDevice.avd/config.ini
where MyDevice refers to the configured device name.
Depending on your operating system, you may find your home directory according https://en.wikipedia.org/wiki/Home_directory.
Change the entry within config.ini from no to yes:
fastboot.forceColdBoot=yes
I specified AVD memory 2048 Mbyte instead of 1536 Mbyte. Things
started to work again. (I'm developing on macbook.)
I tried "Kuldeep Chandel" solution which is to duplicate AVD and my app runs again too. Because of that I specified RAM again as 1536
Mbyte. Guess what... It worked...
I think AVD confuses to handle things and we need to duplicate the current AVD, and use it instead of the problematic one.
In "Your Virual Device" - Click on Duplicate OR Duplicate your Device. It will work like Charm.
I faced this issue on using Android API 28 emulator with Android Studio 3.0.1. Android API 28 requires Studio 3.1 and above. Once I updated Studio to 3.1.4 and Android Emulator to the latest version, it worked.
Seting default settings for problem device from Android Device Manager resolved issue for me.
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)?
When I select any emulator, I'm getting this weird old red phone. The screen is super small and I can't see anything. I've tried searching, but it looks like no one else has had this problem. Does anyone recognize it? My emulators did work fine, but I had to uninstall and reinstall Android Studio because it broke. After reinstalling, this is what's happening :/
Open AVD Manager in Android studio
Select the target emulator and click edit
Click Show Advanced Setting
In the Boot Option section select Cold Boot
Click on Finish
This solved my problem
Go to Tools>Android>AVD Manager and remove all device than add again. Hopefully this will fix your problem. I had exact issue when I moved my sdk folder.
You can try genymotion as your emulator. Its faster and more stable than android studio's emulator. Search on Google for more information.
I had the exact same problem.
I removed all existing devices from my AVD manager and re-installed one which is required. The problem went away.
When I try to open Android Device Monitor, this shows up:
As far as I recall, I never had this problem until macOS Sierra. And I'm worried it will screw up my environment if I follow what the pop up says.
In case anyone has this problem and manage to get Android Device Monitor running, can you please share your solution?
Note:
I'm using Android Studio 2.2.3