Does Android 4.0 emulator always have a crash Launcher?

Question

I am trying to create an Android 4.0 emulator. I tried this process on a fairly fast computer in both Linux and Windows (Phenom II X6 w / 8G RAM), and every time I get a “unfortunate launch launcher” when I try to see the launcher menu.

I tried having a RAM size up to 1024 M, but nothing helps. Is this just a bitten emulator?

Answer 1

I experienced the same problem several times. All I did was change the RAM size to 512, and the heap to 32. Stay fine ...

@racs suggested that changing the emulator skin in the AVD manager would also help. Try it ...

Check if this helps.

Answer 2

I also encounter the same issue after updating the latest SDK. I came up with the following solution after spending several hours,

Problem: "Unfortunately, the launcher is stopped." This is because the path of the AVD code is not assigned properly in the AVD config.ini

For example. My name is AVD AVD_4.0.3_WSVGA

before fixing skin.path = AVD_4.0.3_WSVGA

so I changed the skin path as follows: skin.path = platforms / android-15 / shells / WSVGA

you can find config.ini

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

Answer 3

Try using a different API level.

I got this idea here , and it worked with Nexus 7 AVD at API level 17 with an ARM processor on OS X, and it seems OK.

Answer 4

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

Answer 5

He decided for me when I change a bunch of VMs from 16 to 32

Answer 6

Update your Android SDK Manager and try again, check these links Adding SDK components

Answer 7

Do you have a snapshot download? if so, you can try disabling it.

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

Answer 8

My solution was to start the emulator first.

Simply put: the android emulator died of fatigue when I tried to run the application before the emulator managed to load correctly.

Answer 9

None of the answers given here helped me. In the end, I solved the problem by switching to the advanced settings of my virtual device in Android Virtual Device Manager. My SD card was installed at 9 MB, and it is recommended that you install it at least 10 MB. When I set this to a higher value, it fixes the problem.

Answer 10

I solved mine by increasing the heap size to 128.

Answer 11

I had the same problem and I had to do factory reset on my phone twice to get rid of this. But then I realized that the problem always occurred when I tested one specific application, and therefore the problem was narrowed down. I also saw the error file, and it showed the OOM fault lines.

Then I checked my last changes inside this application, and I was surprised to find that the logo of the user application that I used to replace ic_launcher was huge in size, because of which every time I started this application, System Launcher tried to open him and eventually with OOM.

I know, I know, that sounds weird, but believe me, that was a problem. I reduced the size and tested again, and everything was fine.

Note. I even tried to test my friend on the phone and also crashed my launcher .;)

Answer 12

I had the same problem, I decided, now you have to reset your adb,

• open the emulator and Goto DDMS mode → click the following Screen Capture (Drop Down) button → Reset.adb. Or
• Goto Run → Cmd → goto Path (platforms and tools in Android sdk) → adb kill-server 2.1 Goto Run → Cmd → goto Path (platforms and tools in Android sdk) → adb start-server that it, restart the emulator, I’m sure that it will work.

Answer 13

I have encountered this problem before. The main cause of this problem is the size of RAM. You cannot set the RAM size to more than 800 MB. In my case, set the RAM size to 700 MB and it works correctly. Therefore, try changing the size of the RAM.