Android Device Emulator- Error Message: 'Unfortunately, Launcher Has Stopped'

[SergeyKostrov]

I wonder if somebodyhad experienced an error message 'Unfortunately, Launcher Has Stopped' in Android Device Emulator.
I have that errorfrom time to time andit is not clear what causes it. A screenshot is enclosed:



Best regards,
Sergey

[Bernard]

Sergey!
On what platform runs Android Device Emulator?If it is Windows you can run your emulator under debugger.Please set windbg as a postmortem debugger and try to run your app maybe debugger's break-in will be trigerred by some unhandled exception in theemulator code.You can also tryto do some investigation and find how it Launcher is implemented.For example if it is an DLL loaded by an emulator you can set a conditional breakpoint on dllmain call and single-step through the code.
Other thing you can do is to use an IDA disassembler and find the address of the string being displayed when Launcher crashes.When you have an address (probably global variable) you can set the conditional breakpoint on this address it should be some of the windowing procedures which gets string address to be displayed.From this point you can try to reconstruct the call stack simply by going through the return addresses pushed on the stack.
Btw Look for minidump file when Launcher crashes.

[Bernard]

On what platform runs Android Device Emulator

I see that this is a windows application.Please read my previous post.

[Alexander_W_Intel]

Sergey,

if that happens, please look into the adb log. You should find there more information about the crash happened. To do that run the following command on your host machine:

[bash]adb logcat[/bash]

Thanks,

Alex

[Alexander_W_Intel]

Quoting iliyapolak

On what platform runs Android Device Emulator

I see that this is a windows application.Please read my previous post.

It's an Android* application inside the emulator which is crashing. Debugging the emulator might be not the best approach to rootcause the issue.

Alex

[Bernard]

It's an Android* application inside the emulator which is crashing

Because of word 'Launcher' being displayed I thought that some of Emulator component is crashing in such a case windbg should have been helpful to pinpoint the problem.

[SergeyKostrov]

Quoting Alexander Weggerle (Intel)

...It's an Android* application inside the emulator which is crashing. Debugging the emulator might be not the best approach to rootcause the issue.
Alex

Absolutely agreeand I simply don't have time to do this.All Androidsource codesare available...

Iexperienced that error with emulator from Level 14 API and didn't see it when testing emulator from Level 15 API.
I've used a system image 'ARMeabi-v7a' to create AVD. I think I need to look atIntel system image as well.

Best regards,
Sergey

[SergeyKostrov]

Quoting Alexander Weggerle (Intel)

...if that happens, please look into the adb log. You should find there more information about the crash
happened. To do that run the following command on your host machine:

adblogcat

Thank you! Today is my second day with Android and a"pressure is mounting"...

My question is why emulator for ARM CPUsis so slow? Is it faster for x86 CPUs?

My currentconfiguration is as follows:

- Android 4.0.3 ( API 15 )
- AVD was created based on a system image 'ARMeabi-v7a'

Best regards,
Sergey

[Bernard]

Absolutely agreeand I simply don't have time to do this.All Androidsource codesare available

@Sergey
What is the 'Launcher' is it part of an Emulator?

[SergeyKostrov]

Hi Iliya,

Quoting iliyapolak

Absolutely agreeand I simply don't have time to do this.All Androidsource codesare available

@Sergey
What is the 'Launcher' is it part of an Emulator?

Yes.I think this isaService of an Android Deviceor Emulator...

[SergeyKostrov]

Quoting Sergey Kostrov

...My currentconfiguration is as follows:

- Android 4.0.3 ( API 15 )
- AVD was created based on a system image 'ARMeabi-v7a'

Itested anew AVD based on a system image forIntel 'x86Atom'. Here is another screenshot:

[Bernard]

Yes.I think this isaService of an Android Deviceor Emulator...

How is the Emulator implemented?Is it a.dll image?

[Alexander_W_Intel]

Quoting Sergey Kostrov

My question is why emulator for ARM CPUsis so slow? Is it faster for x86 CPUs?

The ARM CPU is completely emulated. That means that every ARM instructions needs to be translated to an x86 instruction and than run on your host machine. Because of this overhead it is really slow.

If you run a normal x86 image in the emulator the situation is similar if you not use the Intel HAXM. The Intel HAXM can accelerate the x86 images, so that parts of the code will run nativelyon your host machine and give you a much better performance.

The install instructions can be found here:http://software.intel.com/en-us/articles/installation-instructions-for-intel-hardware-accelerated-execution-manager-windows/

Alex

[Alexander_W_Intel]

Quoting iliyapolak

Absolutely agreeand I simply don't have time to do this.All Androidsource codesare available

@Sergey
What is the 'Launcher' is it part of an Emulator?

The Launcher is the application that provides the homescreen for Android. So this is part of Android and have nothing todo with the emulator.

[Bernard]

The Launcher is the application that provides the homescreen for Android. So this is part of Android and have nothing todo with the emulator

Thanks for explaining this.Finally understood :)

[SergeyKostrov]

Quoting iliyapolak

Yes.I think this isaService of an Android Deviceor Emulator...

How is the Emulator implemented?

[SergeyK]Itlooks like it is a Java application.

Is it a.dll image?

There are three executables in a '..\Android-SDK\Tools' folder:
emulator.exe
emulator-arm.exe
emulator-x86.exe

[SergeyKostrov]

Here is a screenshot of AndroidSDK Manager with installed packages:



I didn't have any problems with installation of these packagesand my main concern is performance of Android emulator for ARM & x86 CPUs.

[SergeyKostrov]

Quoting Alexander Weggerle (Intel)

...
The Launcher is the application that provides the homescreen for Android. So this is part of Android and have nothing todo with the emulator.

Alexander, I'm interested to get some numbersfor your computer:

- How long does it take to load an emulator for ARM CPUs?
- How long does it take to load an emulator forx86 CPUs?

Best regards,
Sergey

[Bernard]

emulator.exe
emulator-arm.exe
emulator-x86.exe

So its an exe image and two binary-translators implemented also as an exe image.Was there any emulator.exe related crash?

[SergeyKostrov]

Quoting Alexander Weggerle (Intel)

Quoting iliyapolak

Absolutely agreeand I simply don't have time to do this.All Androidsource codesare available

@Sergey
What is the 'Launcher' is it part of an Emulator?

The Launcher is the application that provides the homescreen for Android...

Here is a technical detail:The problem/issueis related to 'com.android.launcher' Java class.

[SergeyKostrov]

Quoting iliyapolak

emulator.exe
emulator-arm.exe
emulator-x86.exe

So its an exe image and two binary-translators implemented also as an exe image. Was there any emulator.exe related crash?

No. I pressed 'OK' and emulator continued to load something...