66

I'm trying to make an Android 4.0 emulator. I've tried this process on a fairly fast computer in both Linux and Windows(Phenom II X6 w/ 8G of RAM) and every time I get "unfortunately, launcher has stopped" when I try to look at the menu of the launcher.

enter image description here

I have tried having the RAM size all the way up to 1024M, but nothing seems to help it. Is this just a borked emulator or what?

Earlz
  • 62,085
  • 98
  • 303
  • 499
  • 11
    I updated VM Heap size 256 and stopped – user2022622 Jan 29 '13 at 17:35
  • As Balavishnu's answer suggests, it seems the default heap size (16) is too small. It is a pretty blatant bug that the emulated device doesn't work in its default configuration. Have you filed a bug with Google? – Mechanical snail Apr 13 '13 at 21:34
  • 1
    You don't need 1 GB RAM for your emulator for testing a single app! May be its a bug, I haven't filed that bug. If my answer helped you to some extend, please accept my ans. – Niko May 14 '13 at 04:50
  • 1
    Hi I was getting same error with 32 heap set it to 64 and worked perfectly for me! – Louwki Nov 29 '15 at 17:52

13 Answers13

47

I have experienced this same problem, several times. All I did was changed the RAM size to 512, and heap to 32. Rest all good...

@racs here suggested that changing the emulator skin in the AVD manager might also help. Give it a try...

Check if this helps.

Niko
  • 1,367
  • 1
  • 13
  • 37
  • 2
    Person that was experiencing this problem here. Can confirm that this fixed it for me. Thanks. – yiati Jun 20 '13 at 18:21
  • 3
    Adjusting the memory setting wasn't working for me. However, when I changed the emulator skin in the AVD manager then suddenly these annoying pop-up errors disappeared at once. – racs Oct 09 '13 at 01:15
  • 1
    Same here except that I went up to 1024 RAM and 64 HEAP – Sebastien FERRAND Feb 19 '14 at 13:05
  • after changing the RAM size 512, and heap to 32. giving emulator: ERROR: Unable to load VM from snapshot. The snapshot has been saved for a different hardware configuration. Whats next ? please advise. – Ashfaque Apr 11 '14 at 05:27
6

I'm also facing the same issue after updating latest SDK. I come up with following solution after spending few hours,

The problem is "unfortunately, launcher has stopped". This happens because of the AVD skin path not properly assigned in AVD's config.ini

For Ex. My AVD name is AVD_4.0.3_WSVGA

before fix skin.path=AVD_4.0.3_WSVGA

so I changed skin path as follows, skin.path=platforms/android-15/skins/WSVGA

you can find config.ini

in linux(Ubuntu) /home/[username]/.android/avd/[your avd name]/config.ini

Jayabal
  • 3,619
  • 3
  • 24
  • 32
4

Try a different API level.

I got that idea here, and it worked a Nexus 7 AVD at API level 17 with an ARM CPU on OS X and it seems to be OK.

caseyboardman
  • 799
  • 2
  • 11
  • 26
1

It's solved for me When I change VM heap from 16 to 32

Plugie
  • 1,289
  • 17
  • 25
0

Have you got "load from snapshot" on? if so you could try turning that off.

I also read here https://android.stackexchange.com/questions/23842/unfortunately-launcher-has-stopped-error-after-4-0-4-ota-upgrade were someone suggested clearing the launchers data in app settings.

Community
  • 1
  • 1
Thomas
  • 435
  • 6
  • 20
0

chage confing file in --> .android->avd->youavdfoldername->config
open file and change
hw.dPad=yes
hw.mainKeys=yes

PankajAndroid
  • 2,689
  • 3
  • 27
  • 41
0

My solution was that you had to let the emulator boot up beforehand first.

To put it simply: the android emulator died from exhaustion when I tried to launch the app before the emulator had had time to boot up properly.

Amici Nybråten
  • 57
  • 7
0

None of the answers listed here helped me. I eventually fixed the problem by going to the advanced settings for my Virtual Device in Android Virtual Device Manager. My SD card was set to 9MB and it's recommended to set this to at least 10MB. When I set this to a higher value it fixed the problem. enter image description here

medinasod
  • 375
  • 3
  • 9
0

I solved mine by increasing the heap size to 128.

mor222
  • 400
  • 7
  • 16
0

I had the same issue and I had to do factory reset on my phone twice to get rid of this. But I then realized that the issue always happened when I was testing one particular app and thus the prob was narrowed down. Also I saw the error file and it showed OOM crash lines.

I then checked my last changes within that application and I found out to my surprise that the custom app logo which I was using replacing ic_launcher was huge in size due to which everytime I ran that application System launcher tried opening it and ended up with OOM.

I know, I know it sounds weird but trust me this was the issue. I reduced the size and tested again and things were working fine.

Note - I even tried testing on my friend's phone and crashed his launcher too. ;)

Atul O Holic
  • 6,692
  • 4
  • 39
  • 74
0

Update your Android SDK Manager & try it again, check this links Adding SDK Components

Mr. Sajid Shaikh
  • 7,051
  • 4
  • 21
  • 35
-1

I had also same problem, I resolved,now you should reset your adb,

  1. open the emulator and Goto DDMS mode -->click next button of Screen Capture(Drop Down)-->Reset.adb. Or
  2. Goto Run-->Cmd-->goto Path(platforms and tool in Android sdk)-->adb kill-server 2.1 Goto Run-->Cmd-->goto Path(platforms and tool in Android sdk)-->adb start-server that's it,restart emulator am sure it will work..
kleopatra
  • 51,061
  • 28
  • 99
  • 211
Vela
  • 87
  • 11
-1

I faced this problem before. The root cause of this issue is the RAM size. You cannot set the RAM size greater than 800MB. In my case, in set the RAM size to 700MB and it works properly. So try to change you RAM size.

lalala la
  • 9