Android emulator error: "System UI has stopped"

Question

I have recently set up my Android development environment. Every thing is alright but when I run my emulator it takes to much time with an error dialog on the emulator screen says- "Unfortunately, System UI has stopped" and no application runs on it. I have recently shifted to 64bit windows7 and using JDK7 and eclipse juno for 64bit. My emulator configuration is given below: enter image description here

can anyone suggest me what is wrong with it?

Try deleting the current AVD profile and create a new one. Sometimes it worked for me. Try to decrease the screen size and also RAM size. — HemChe, Mar 28 '13 at 09:48

score 83 · Accepted Answer · edited Jul 08 '21 at 11:25

This is still "unanswered", but it probably has been resolved.

I just want to share my experience and clarify a few things, some of which may not matter. Anyway, if this helps someone else that's great.

I had this problem on one machine (a new, but slower machine), but not another (the faster one) when running a 4.0.3 emulator. It is not a hardware problem though, and CPU speed doesn't make a difference.
Both machines are fully up-to-date ADT (Eclipse 4.2.x and Android 4.2.2 (API 17) SDK environments.
Editing, or even Deleting the emulator and then recreating it did NOT fix it.
The best solution is to locate and update the config.ini file. In Windows 7 (x64) I found the config.ini file in %USERPROFILE%\.android\avd. It was located in a folder ICS_4.0.3_API_15.avd [*see AVD names below].

NOTE: First make sure you have “show hidden files, folder, or drives” turned on in Explorer or you won't see the ".android" folder.

Not sure it matters, but my entry said hw.mainKeys=no, not hw.mainKeys=false as some have suggested. Changing it to hw.mainKeys=yes seems to have fixed the problem.

AVD Names - Your AVD name will be different from mine. I just add the Release name/API level in the name so I can quickly scan the list and go to a release, such as Honeycomb, Ice Cream Sandwich, Jelly Bean, etc. (e.g., ICS_4.0.3_API_15.avd)

There's more information in another thread at < Unfortunately System UI has stopped >. It starts by asking a seemingly tangential question, but gets to the same place.

Thanks it solve ui problem but yet it will display an launcher crash issue. — CoronaPintu, May 31 '13 at 05:10
By default, the android tool creates the AVD directory inside ~/.android/avd/ (on Linux/Mac) — Waqleh, May 26 '14 at 13:28
Worked for me on an 10.1 in. android 4.0.4 emulator I downloaded today, though there are still some popups showing like, when changing the background, it says "Unfortunately, the process com.android.launcher has stopped" — niCad, Mar 08 '17 at 05:50
For me it was the exact opposite -.-' I had to disable main keys to have soft keys back, then it worked. API 26 - emu 27.3.10-4969155 — Shockwaver, Sep 05 '18 at 11:52

score 30 · Answer 2 · answered Jan 31 '19 at 17:03

30

This issues has happened to me a few times, and has always been resolved by cold booting the emulator.

On OS X:

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

Here is a photo of what the menu looks like

I'm not sure what this looks like on Windows, maybe someone can confirm that it is similar?

answered Jan 31 '19 at 17:03

Matthew McCord

471
5
9

1

Works great, and the interface is the same on Linux. Very likely the same on Windows as well. – rednuht Feb 20 '19 at 12:21
Android Studio 2021 -> Tools -> AVD Manager – Miguel Tepale Jul 16 '21 at 16:57
In 2022 it's Tools -> Device Manager. – rwst Feb 22 '22 at 17:29

score 8 · Answer 3 · answered May 02 '13 at 18:12

8

What seems to have worked for me and others is to change the hw.mainKeys setting in your config.ini to true:

hw.mainKeys=true

answered May 02 '13 at 18:12

Glenn Reimche

81
2

score 0 · Answer 4 · answered Mar 28 '13 at 10:27

0

Close avd and eclipse then Delete .android file created in your user folder then try to create a new emulator this help me most of the time.It may helps you

answered Mar 28 '13 at 10:27

ravi

64
10

score 0 · Answer 5 · edited May 23 '17 at 12:09

My case. Android SDK was placed here D:\android-sdk\ for a nearly year ago. After one of recently SDK updates I'v got "Unfortunately, System UI has stopped". I'v created number of divices with different RAM amount, VM heap size, screen size, API level(problem seems to be only on API14+), etc. At finish i noticed that new devices was created at the location C:\users\XuserX\.android\avd After reading this post solution was simple: create ANDROID_SDK and ANDROID_SDK_HOME system variables with value d:\android-sdk\

Hope this post helps somebody.

score 0 · Answer 6 · answered Jul 27 '13 at 06:32

0

just switch off and on hte button in emulator ... it can remove that problem

answered Jul 27 '13 at 06:32

Udit Kumawat

654
1
8
21

score 0 · Answer 7 · answered Mar 28 '14 at 19:43

0

This is also happening if your device definition name has " character in the name, like Kindle Fire HD 7".

Once I removed the apostrophe symbol, error was gone.

answered Mar 28 '14 at 19:43

sandalone

41,141
63
222
338

score 0 · Answer 8 · answered Dec 04 '19 at 18:26

0

In Android Studio Tools -> AVD manager -> Actions -> dropdown▾-> Wipe Data

answered Dec 04 '19 at 18:26

Nagibaba

4,218
1
35
43

score 0 · Answer 9 · edited Mar 17 '21 at 22:06

0

Go AVD Manager and just click "Wipe Data" for your emulator in Android Studio.

edited Mar 17 '21 at 22:06

Dharman

30,962
25
85
135

answered Jan 06 '21 at 08:41

canerkaseler

6,204
45
38

Android emulator error: "System UI has stopped"

9 Answers9

Linked

Related