Develop Reference

Android studio emulator always get freeze

I am working on andorid and my emulator is working fine but now whenever I try to run my project my emulator always get freeze I have also added that picture. Any help to resolve this issue?

That's Windows 11 right? A lot of people seem to be having issues and there's an issue about it on Google's tracker:
Android Studio Emulator is not working on Windows 11 using WHPX
Android Studio Emulator is not working on Windows 11 when WSL2 is installed
If none of that applies (the question shows how to run the emulator from a terminal, so you can see what the output is) then I'd try in this order:
close the emulator and make sure there are no emulator processes running in Task Manager
reboot and try again
do a Cold Boot in the AVD manager (clears the emulator state)
delete the AVD and create a new one
but given that it's hanging like that partway through initialisation, it might be an issue with the emulator process itself. Some stuff to try anyway

Try delete this emulator and create some new emulator.

I am not able to start my AVD or Emulator in android Studio

While running Emulator its shows Emulator was Killed.
In Activity Log I can see an error named as:
"Emulator: Process finished with exit code -1073741515 (0xC0000135)"
I have tried---->
To clean/wipe and cold reset
Even I have tried by creating a new Emulator with RAM size 4 Gb also. But still, I faced the same problem which I had encountered earlier.
My IDE and SDK are updated.
I had also tried to configure my AVD's Graphics from Automatic to Software-GLS 2.0 but that doesn't work too.
But the same project can be run on my Android Phone.
My PC's Virtualisation is "Enabled"
Please Help me with that...

There's some suggestions in here about running the emulator from the command line, so you get some more useful info.
Since you mentioned RAM size, make sure you have enough local storage on the virtual device too - I've had a lot of problems where I've tried to keep it low (it'll be fine! I'm only installing one small app!) and the emulator misbehaves and won't run properly

Android Studio Emulator and "Process finished with exit code 0"

I've updated android studio from 3.0 to 3.0.1 but when I launch Emulator it didn't get launched and gives message in event log:
Emulator: Process finished with exit code 0

You need to check:
Your size on disk is not full - this's often happen due to creation of some virtual devices that are unused
The RAM size of emulator is not minimum as your requirements
One more thing that I personally use: Use Pen Drive as a RAM
Updated:
Use HDD as RAM
Right Click on “This PC or My Computer” and Select Properties.
Now Click on “Advance System Settings”.
Now in “System Properties” you have to select “Advanced” tab.
Now click on “Settings” Under “Performance”.
Now in “Performance Option” again you have to select “Advanced” tab.
Now click on “change“ under “Virtual Memory”.
Un-check “Automatically manage paging file size of all drivers” and select “Custom size”.
In Custom Size enter the amount of data According to “Space available” which is written there.
Click on “set” button and Click on OK.
Now it will ask you to restart your Computer or Laptop.
Another work around steps (tested) :
Restart your Android Studio
Create new device in your AVD Manager
Increase the RAM size of the Emulator

I restarted Android Studio and create a new device in AVD MANAGER then I have increased the RAM size of emulator and it works nicely.
UPDATED
Sometimes it happens when you close emulator during building the App in to emulator.

I also faced the same error. After a few hours I figured it out.
I hope it helps you :
Go to Tools ==> SDK Menager ==>Android SDK
(Appearange&Behavior=>System settings=>Android SDK)==>SDK Tools==>Intel x86 Emulator Accelerator(install this).
It will solve your problem.I hope it helps.

I had this problem and it took me nearly 2 days to resolve...
I had moved my SDK location, due to the system drive being full, and it seems that someone, somewhere at Android Studio central has hard-coded the path to the HaxM driver installer. As my HamX driver was out of date, the emulator wouldn't start.
Solution: navigate to [your sdk location]\extras\intel\Hardware_Accelerated_Execution_Manager and run the intelhaxm-android.exe installer to update yourself to the latest driver.

I had this issue in Android Studio 3.1 :
I only have on board graphics. Went to Tools -> AVD Manager -> (Edit this AVD) under Actions -> Emulated Performance (Graphics): select "Software GLES 2.0".

In AVD Manager,
Go to Edit Icon on AVD Manager for selected Device.
Click on show advanced settings and increase ram size from 1500 mb to 2 GB.
Then it works.
NOTE: Some virtual devices do not allow you to update RAM, but if so, try installing Nexus 4. because it does.
NOTE2: If still doesnt work, dont give up. just uninstall and reinstall the device with changing RAM again. in some cases this is how it works
NOTE3: If still doesnt work, this means your pc doesnt have enough ram space. so increase the ram to 3gb. it might work but it will suffer
NOTE4: If still doesnt work, try it with multicore 2 instead of 4.
NOTE5: Still doesnt work. Close the Android Studio and NEVER open it back :)

Docker installation selected Hyper-V on windows by default. Deselect the Hyper-v b
This worked for me.

I was able to get past this by making sure all my SDKs were up to date. (Mac OS 10.13.3, Android Studio 3.0.1). I went to Android Studio -> Check for Updates... and let it run. Once my Android 5.0/5.1 (API level 21/22) SDKs were updated to revision 2:
After doing this update, I was able to run the emulator without crashing out immediately with a "Emulator: Process finished with exit code 0" error.

None of the solutions worked for me. I upgraded my previous Android Studio to 3.0.1 and received this issue while trying to restart the emulator.
What worked for me was deleting Android Studio from Windows 'Add or Remove Programs'. Then go to C:\Users[User] and delete any android-related folders (.android, .AndroidStudioX.X, Android).
Next go to C:\Users[User]\AppData\Local and delete any Android-related folders there. Restart your system and re-download android studio from their official site (https://developer.android.com/studio/index.html). Install Android Studio from fresh and don't import any old settings.
When Android Studio finishes installing, I launched AVD from 'Tools > Android > AVD Manager', created a pixel 2 device with 4096mb of RAM running Android API P x86. Start it up and it works!

This can be solved by the following step:
Please ensure "Windows Hypervisor Platform" is installed. If it's not installed, install it, restart your computer and you will be good to go.

Android Studio Emulator: Process finished with exit code 1. Maybe disk drive is FULL. You can delete some virtual devices unused. It works for me.
it's next to the edit in your virtual manager devices menu (the arrow down)

I also had the same problem.I fix this problem by editing Graphics of AVD.
Tools > Androids > AVD Manager > Actions > Edit > Show Advance Settings > Graphics -> Software.
I hope this solution help u!

You can try to delete the emulator and reinstall it this usually does the trick for me. Sometimes you also run into hiccups on your computer so try restarting your computer. Your computer may not be able to handle android studio if so there is nothing you can do. Consequently, you may not have the right ram requirements. Finally, If all else fails you can try to delete then reinstall android studio.

I solved this issue by offing all of advantage features of my graphics card in its settings(Nvidaa type). It started to throw such hanging error less a lot. But finally I found a simplier way: In avd manager you need to put less resolution for the avd. Say, 400x800. Then I reenabled graphics card features again and now it runs all ok. (I suspect my graphics card or cpu are weaker than needed. )

In my case, Emulator: Process finished with exit code 0 error started after I pressed on Restart in the Emulator.
It happened because in Android Studio 3.0 and up versions, the emulator saves the states of the current screen to launch it very quickly at next time. So when I pressed on Restart it closes emulator by saving state as Restart. So when I launch/start the emulator, it executes the Save States as Restart and then after emulator is not started automatically. So basically it stuck in to Save States of Restart.
I don't want to delete existing emulator and create a new one.
My default Boot Option of Emulator was Quick boot in AVD.
By doing Cold Boot Now from AVD (Android Virtual Device) Manager, it starts emulator again in normal mode without Save State.
Cold boot start emulator as from power up.

I was getting the following error when starting the emulator and none of the answers fixed it.
Emulator: Process finished with exit code -1073741515 (0xC0000135)
Finally I found that Visual C++ is not installed in my system. If it is not installed please install Visual C++ and check.
Please find the link below to download latest Visual C++.
https://support.microsoft.com/en-in/help/2977003/the-latest-supported-visual-c-downloads

Error while waiting for device: Timed out after 300seconds waiting for emulator to come online

I have been trying to use android studio emulator but I can not run my App on the Emulator. When I Run my App it shows the emulator with following details:
Hax is enabled
Hax ram_size 0x40000000
HAX is working and emulator runs in fast virt mode.
Console on port 5554; ADB on port 5555
After that it takes to next TAB Launching app and shows waiting for the device to come online. After that it shows error:
Error while waiting for device: Time out after 300 seconds waiting for emulator to come online.
Anyone know any solution.

Although there could be various reasons for this behaviour....
Mostly it may be due to error in system images or the API version you are using
better you download latest system images and make sure the compatibilty of API version you are using.
If problem exists
I would like to suggest some fixes:
Try them
1)Uninstall/Reinstall Android SDK to folder.
OR
2) delete the emulator and create another emulator targeted at the appropriate API Level.
OR
3)create a new Virtual Device.
OR
4)set "Max VM application heap size" hardware property to 192 or higher and pick the QVGA skin.
hope it helps.

I was also facing this timeout error. Here is the solution worked for me
Launch Task Manager -> Search for adb.exe in process list->End the process->Try relaunching the emulator it will start.

This helped me:
https://www.youtube.com/watch?v=avcOIrtimMU
Click on app: edit configurations;
In Launch Options: choose Specific Activity
In Activity: specify your main class: com.example.budgetapp.MainActivity
And, run.

This Worked for me:
GoTo SDK Manager -> SDK Tools -> Check that the android emulator has the latest version and If doesn't install the updates.
I had the same error described here.
Hope This Helps

Check updates.... Emulator had an update.
After I updated worked fine.

I went through a lot of posts. But none of them seemed to work for me. Every time I tried to start the emulator, the process seemed to be "not responding" after a minute or so. I tried restarting my PC, adb, created new devices, even re-installed Android Emulator, but nothing worked.
Surprisingly enough, what worked though was to move the emulator out of Android Studio.
Go to Preferences -> search for Emulator -> Uncheck Launch in a tool window
I am using Mac M1 Pro with Android Studio Bumblebee | 2021.1.1

Open the AVD Manager.
Create a new AVD or edit an existing AVD.
In the Verify Configuration page, specify the Emulated Performance: Graphics change to sofware or hadware
good luck

I tried everything here and other questions too, but the only solution for me was to create a new AVD.
Also downgraded from Pixel3XL to Pixel2, not sure if it matters. (Kept same android version)

Android studio 1.x AVD not running?

I'm a newbie android developer ,since i upgraded to Andoid Studio 1.x from beta ,things became a lot easy , creating the AVD and managing SDK is managed better by the IDE now ,
I used the Default Nexus 5 config to setup an AVD,however can you please tell me how to safely turn it off ,I cant find any poweroff button , i have Intel HAXM set up and working fine, I got an error saying AVD instance aldready running etc asking me to delete the avd from user/android/avd/... which i did ,
WHen i created it i can run it just once, when i close and reopen studio and try to run again i get the following message
AVD Nexus_5_API_21 is already running.
If that is not the case, delete the files at
C:\Users\S****\.android\avd/Nexus_5_API_21.avd/*.lock
and try again
And what system image to use for the AVD, whats the difference between the ARM ,ATOM 86,ATOM 64 and googdle API images for the same android version, i use a windows 8.1 PC 64Bit running on a vt-x suported intel core i5 , 4200 u processor , which image should i use ,
Please Note i couldnt find solutons elsewhere and i doubt its an offtopic question as its about setting up a programming tool.
Btw the task manager shows a 32 bit emulator running
Thanks!

Here you Are :
when you click on turn on/off button emulator will be start/finish , also Remember after start emulator for first time you don't need to reOpen it!

Delete all files and directories with extetion .Lock at C:\Users\user_name.android\avd\emulator_name.avd\files.Lock and try Again.

Go to Tools>>Android>>Enable ADB Integration select this, It worked for me.

make sure sdk and avd manager added to your IDE correctly.
answer of your second question is,when you play your app in IDE a emulator will be run and on emulator toolbox you can turn off or turn on your emulator and also you can see your app running or not

I meet this situation today, but the file *.lock was deleted (not by me) when i run this emulater failed with error tips like
AVD Nexus_5_API_21 is already running.
If that is not the case, delete the files at
C:\Users\S****.android\avd/Nexus_5_API_21.avd/*.lock
so in the end, i duplicated this emulator and located the copy emulator's location and find the .*lock file and then i deleted it and it worked.