score:79

Accepted answer

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.

  1. 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.

  2. Both machines are fully up-to-date ADT (Eclipse 4.2.x and Android 4.2.2 (API 17) SDK environments.

  3. Editing, or even Deleting the emulator and then recreating it did NOT fix it.

  4. 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.

  1. 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.

score: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

score:0

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

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

score: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.

score:0

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

score:0

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

enter image description here

score:0

It might be a little late, but 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.

I downloaded the X86_64 version and I have not faced that annoying error anymore.

score: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

score:28

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?


Related Query

More Query from same tag