The system ui isn't responding in android emulator (Flutter)

Question

After starting the avd in android studio, the system ui is not responding message comes in the android emulator. So, how can i fix it ?

Solution 1

1.Open AVD Manager. 2.Click to edit button for your device. 3.Select Hardware in the Graphics drop down menu.

Solution 2

I used to face this problem every time I started my AVD. Also the cold boot option was just a temporary fix for me.

I checked the android version that I had installed on my emulator, and noticed the ABI version was x86.

To fix that, I made a new android emulator, and in the selecting system image section, I chose the X86_64 version.

That fixed the problem for me.

Solution 3

On OS X, I am able to solved it by steps:

Open Android Studio. Navigate to Configure > AVD Manager. Under Actions > dropdown triangle on the right > Cold Boot Now:

Solution 4

I was constantly annoyed by this and would often click on Wait, then realize after some time the tremendous amount of time wasted.

I fixed it by creating a new emulator (ctrl + shirt + a -> "avd", select avd manager):

• Choose create new device, select Pixel 4 or Pixel 4 XL for example
• Then instead of selecting recommended system image, selected "API Level S, ABI x86_64 (former device was only x86), Target Android API S (Google Play). Beware it will take 1.3GB and download, although fast will take a little bit -> go grab a cup of coffee. Finish? Click on Next.
• In advanced settings (show), increase RAM from 512 to 1024.

Now I don't have this problem anymore.

Solution 5

I finally found what causes this in my case. Once I resize, after a couple of minutes I got that error. So:

DON'T RESIZE YOUR EMULATOR WINDOW !!!!

I still got that message from time to time, but not that often.

View more solutions

Comments

[Mobina]

Check this answer: stackoverflow.com/a/16402304/9902765

[Abir Ahsan]

It's working now ?

[houtengzhi]

This answer works well for me. stackoverflow.com/a/66753570/6180340

[ccpizza]

Long click on the Power icon until the android native reboot/shutdown overlay appears and click "Power Off" or "Restart"

[Aadn]

its a temporary fix for a few mins. Atleast in my case that is what happens.

[Zain]

unfortunately this option is grayed out

[Ayoub Boumzebra]

Actually, this problem seems to be limited to devices with Play Store available, so Nexus 5X and Nexus 5 images will be forced to use Automatic Graphics, but all other devices allow you to choose either Automatic, Hardware or Software graphics.

[The incredible Jan]

"Nexus S image"? There are no device specific system images. It's only the name, the device picture and some settings. The system is always a virtualized x86.

[stolsvik]

Spot on for my case, yes.

[Valentin Yuryev]

It was grayed out but I changed the system image to x86-64 and now it works. I hope, it fixes this issue. It takes a time to check it.

[omiwrench]

This is a temporary mitigation, not a solution.

[Mihai]

Worked on Linux as well.

[Vikash Parajuli]

Works temporarily

[Hassan Ansari]

It does fixes but it's a temporary fix.

[JustCurious]

Solved in my case. Thanks.

[Yusuf Khan]

any idea what is actual reason? is this an emulator issue or code?

[AKTanara]

Didn't work. My Issue was what Pouya Heydari told about X86 & X86_64 versions...

[Wenzhong Hu]

right, you are basically rebooting your emulator, which is not a "solution" :)

[BiasInput]

The steps can be found in an other answer stackoverflow.com/a/67524561/8184729

[colriot]

If this option is grayed for you, just edit it directly in config.ini of your AVD. On Mac path would be: $HOME/.android/avd/MyAvdName.avd/config.ini. Change value of hw.gpu.mode from auto to host → hw.gpu.mode=host

[petestmart]

Mine was greyed out so I deleted it and created a new one. Whatever time I may have lost by having to resetup a new device is easily worth the time lost using an unbearably slow emulator.