Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

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

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 ?

like image 470
Annchit R Sarma Avatar asked Aug 12 '20 06:08

Annchit R Sarma


People also ask

How do I fix system UI not responding in Android emulator?

Still displaying 'System UI not responding' error message, then wipe data and restart the emulator. Go to Tools⇾AVD manager⇾click on the disclosure-open icon ⇾swipe data. delete it and add a new lower API device, maybe work well.

How do I fix system UI isn't responding?

Simple Solutions To Fix Android SystemUI Has Stopped Error Sometimes, the issue can be resolved simply by restarting your device. To do this, press and hold the power button until you see the power menu. From there, select "Restart." Update your apps: Out-of-date apps can sometimes cause this error.

How do I run flutters on Android emulator?

Creating Connection. Choose Device: Open your VS Code and from the bottom right corner of your home screen click on the Flutter Device option. Select Device: When you click on the Flutter Device icon, list of available devices will open up in the command palette. Select the emulator you just created.

What does system UI not responding mean?

If you have downloaded some 3rd-party apps from unknown resources, then it may lead to your system UI not working on Android cause these third-party apps may conflict with your android system UI and your android operating system not being able to grant permission for those apps. Uninstall an App on the Phone.


6 Answers

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

like image 111
Cihangir Avatar answered Oct 18 '22 04:10

Cihangir


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.

like image 40
Pouya Heydari Avatar answered Oct 18 '22 05:10

Pouya Heydari


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:

like image 29
MohammedYakub Moriswala Avatar answered Oct 18 '22 03:10

MohammedYakub Moriswala


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.

like image 25
Antonin GAVREL Avatar answered Oct 18 '22 04:10

Antonin GAVREL


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.

like image 6
despotbg Avatar answered Oct 18 '22 03:10

despotbg


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.

like image 5
gustavoknz Avatar answered Oct 18 '22 04:10

gustavoknz