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 ?

Check this answer: https://stackoverflow.com/a/16402304/9902765 — Mobina, Aug 12 '20 at 08:04
This answer works well for me. https://stackoverflow.com/a/66753570/6180340 — houtengzhi, Jul 01 '21 at 02:08
Long click on the Power icon until the android native reboot/shutdown overlay appears and click "Power Off" or "Restart" — ccpizza, Mar 17 '22 at 15:03
Thanks @ccpizza! So far, your suggestion to long click the power icon is the *only* method that's worked for me so far. — Henke, Jan 09 '23 at 16:21

score 118 · Answer 1 · answered Nov 19 '20 at 08:23

118

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

answered Nov 19 '20 at 08:23

Cihangir

1,892
1
11
16

89

unfortunately this option is grayed out – Zain Jan 20 '21 at 22:30
16

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. – Ayoub Boumzebra Jan 22 '21 at 09:05
2

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. – Valentin Yuryev Apr 22 '21 at 12:35
2

any idea what is actual reason? is this an emulator issue or code? – Yusuf Khan Jun 17 '21 at 03:01
Didn't work. My Issue was what Pouya Heydari told about X86 & X86_64 versions... – AKTanara Jul 20 '21 at 08:17
14

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` – colriot Oct 05 '21 at 18:18
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. – petestmart Nov 27 '21 at 18:17
@Zain You can change it when creating a new device. – Cactusroot Oct 01 '22 at 09:37
Using this option results in the emulator failing to open with the message **The emulator process for AVD Pixel_XL_API_33 has terminated.** – andreszs Jul 20 '23 at 14:38

Pouya Heydari · Answer 2 · 2022-02-21T14:57:20.843

58

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.

edited Feb 21 '22 at 14:57

answered May 01 '21 at 11:56

Pouya Heydari

2,496
26
39

5

The steps can be found in an other answer https://stackoverflow.com/a/67524561/8184729 – BiasInput Aug 26 '21 at 13:10

score 34 · Answer 3 · answered Dec 08 '20 at 10:21

34

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:

answered Dec 08 '20 at 10:21

MohammedYakub M.

2,893
5
31
42

Spot on for my case, yes. – stolsvik Apr 06 '21 at 19:03
18

This is a temporary mitigation, not a solution. – omiwrench May 12 '21 at 06:55
Worked on Linux as well. – Mihai May 18 '21 at 19:18
Works temporarily – Viks May 20 '21 at 05:50
It does fixes but it's a temporary fix. – Hassan Ansari Jun 01 '21 at 09:59
Solved in my case. Thanks. – JustCurious Jun 13 '21 at 15:57
2

right, you are basically rebooting your emulator, which is not a "solution" :) – Wenzhong Hu Jul 20 '21 at 08:37

score 32 · Answer 4 · edited Feb 12 '23 at 18:38

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 + shift + 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 be a 1.3GB download, and will take a little while. Finished? Click on Next.
In advanced settings (show), increase RAM from 512 to 1024.

Now I don't have this problem anymore.

Increasing RAM helped me. I've also increased "hw.cpu.ncore" param by one — Victor Cold, Apr 19 '23 at 01:10

despotbg · Answer 5 · 2021-07-09T14:38:32.603

7

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.

edited Jul 09 '21 at 14:38

answered Jul 08 '21 at 14:53

despotbg

740
6
12

gustavoknz · Answer 6 · 2021-04-22T17:05:15.437

6

On Windows 10, I just wiped the data from the emulator image and started it again. However, as Aadn commented below, this is only a temporary solution.

edited Apr 22 '21 at 17:05

answered Dec 24 '20 at 11:40

gustavoknz

482
1
6
12

10

its a temporary fix for a few mins. Atleast in my case that is what happens. – Aadn Jan 11 '21 at 00:14
Also set RAM to **2048** mb, keep **Software** graphics, and disable both **Multi-Core CPU** and **Device Frame**. – andreszs Jul 20 '23 at 14:59

score 3 · Answer 7 · edited Mar 04 '22 at 15:16

3

I had the same problem and solved it by navigating to the AVD Manager by

Tools > AVD Manager > Right Click the emulator > Wipe all data > Switch on the virtual device.

It worked for me just fine, you can also use it when you are troubleshooting the problem with the emulator in android studio.

edited Mar 04 '22 at 15:16

Hamza Sharaf

811
9
25

answered Mar 04 '22 at 04:35

grace remce

51
3

Wipe all data was the key for me – Amir Jul 03 '22 at 15:10

score 1 · Answer 8 · answered Apr 26 '23 at 12:26

1

If you are running the emulator inside a VM (as I am) then your only option is probably to increase the number of cores the emulator can use.

Edit your device emulators config.ini file:

/home/${USER}/.android/avd/${DEVICE_NAME}.avd/config.ini

And increase the number of cores from the default of 2 to something higher. eg:

hw.cpu.ncore=6

answered Apr 26 '23 at 12:26

TomDotTom

6,238
3
41
39

This worked for me even though I'm not running inside a VM. – Prasad De Zoysa May 24 '23 at 03:19

score 0 · Answer 9 · answered Jan 16 '21 at 11:05

0

After installing the latest system images and creating an emulator using that. My problem is gone.

answered Jan 16 '21 at 11:05

Arda Kaplan

1,720
1
15
23

Vishal Agrawal · Answer 10 · 2021-04-07T11:17:24.390

Instead of clicking "Stop" just click on "wait" and the Emulator will work fine.

And If it is taking too much time in loading make sure you have installed the "HAXM installer" in SDK tools , Also make sure "Hyper V" option is also unchecked in "Turn Windows features on or off" in Control Panel --> Program and features.

Only After unchecking this feature you can install the HAXM installer.

After doing this the Emulator will not take time to load , but still it can show the error "System UI isn't responding", as I told in starting just click on "wait" and it will run smoothly.

score 0 · Answer 11 · answered Jan 02 '22 at 07:55

I solved my problem using this solution from https://stackoverflow.com/a/66265270/5128831

It seems even though intel HAXM shows as installed on SDK Tools, it wasnt really installed so i had to go to below location and manually reinstall (intelhaxm-android) file.
C:\Users\SUHAIL\AppData\Local\Android\Sdk\extras\intel\Hardware_Accelerated_Execution_Manager
if the file doesnt exist in that location, that means it wasnt downloaded and you will have to download the file online

score 0 · Answer 12 · answered Dec 04 '22 at 18:26

0

Change RAM of your emulator to bigger value. That's works for me)

answered Dec 04 '22 at 18:26

Yuriy Kravets

19
1

score -1 · Answer 13 · answered Sep 09 '21 at 03:44

-1

Just follow this instruction hope it will be solved.

answered Sep 09 '21 at 03:44

Musfiq Shanta

1,298
13
9

Arif Frenk · Answer 14 · 2021-10-27T07:56:40.063

-1

You can download "Google APIs intel x86 atom_64 system image" from your sdk manager of your android version. This technique worked for me!!

edited Oct 27 '21 at 07:56

answered Oct 27 '21 at 07:41

Arif Frenk

29
3

score -1 · Answer 15 · answered May 15 '23 at 20:46

-1

Changing of the emulator API. That's what helped me. It's better to try different ones. I've got the 31 one.

Nothing else worked for me!

answered May 15 '23 at 20:46

urhope

1

1

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community May 15 '23 at 23:39

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

15 Answers15

Linked