[android-emulator] Waiting for HOME ('android.process.acore') to be launched

I tried working the Hello World application and the emulator freezes after it flashes the Android start screen. The home page is not shown. The last display on the console is

Waiting for HOME ('android.process.acore') to be launched...

I tried reinstalling Eclipse and Android again. It still did not work. Also the console does not show any errors. The log cat has the following errors:

06-18 20:39:11.543: ERROR/flash_image(544): can't find recovery partition 06-18 20:39:11.843: ERROR/vold(538): Error opening switch name path '/sys/class/switch/test2' (No such file or directory) 06-18 20:39:11.843: ERROR/vold(538): Error bootstrapping switch '/sys/class/switch/test2' (m) 06-18 20:39:11.843: ERROR/vold(538): Error opening switch name path '/sys/class/switch/test' (No such file or directory) 06-18 20:39:11.843: ERROR/vold(538): Error bootstrapping switch '/sys/class/switch/test' (m) 06-18 20:46:31.842: ERROR/MemoryHeapBase(578): error opening /dev/pmem: No such file or directory 06-18 20:46:31.892: ERROR/SurfaceFlinger(578): Couldn't open /sys/power/wait_for_fb_sleep or /sys/power/wait_for_fb_wake 06-18 20:46:32.313: ERROR/GLLogger(578): couldn't load library (Cannot find library) 06-18 20:46:33.634: ERROR/GLLogger(578): couldn't load library (Cannot find library)

What worked for me was to delete the AVD from the AVD manager and create a new one. Then go to
Run >Run Configurations, select the target tab and choose the new AVD.

SOLUTION:

Run the emulator from the command line:

sdk/tools> ./emulator-x86 -avd <DeviceName> -partition-size 1024 -gpu on

Then I launched the app from the command line as well (using built-in Cordova/PhoneGap tools):

myapp/cordova> ./run

BACKGROUND

I believe this is some sort of hardware compatibility issue. I came across this problem when following the PhoneGap 2.4.0 Getting Started Instructions. I followed their advice to install the Intel Hardware Accelerated Execution Manager, and I think this is the source of my trouble. Eclipse uses the emulator64-x86 program (in the sdk/tools folder) to launch the emulator. I could not find any way inside of Eclipse to change this but I found by following the "Tips & Tricks" section of the Intel HAXM web page that I could get the emulator to run successfully from the command line by using the emulator-x86 program instead. I'm not sure why the emulator64-x86 program doesn't work on my system. I confirmed at the Apple website that I do have a 64-bit processor.

My system:

• OSX 10.6.8
• 2x2.26 GHx Quad-core Intel Xeon
• 6 GB RAM
• ADT v21.1.0-569685
• Eclipse 3.8.0

My AVD:

• Device: Nexus One
• Target: Android 4.2.2 - API Level 17
• CPU: Intel Atom (x86)
• RAM: 512
• Internal Storage: 256
• SD Card: 128

Options:

• Click on the HOME Button on the Emulator. Wait for may be 2 seconds.... This always works for me!!!

or

• Go with Shreya's suggestion (one with most suggestions and edited by Gray).

I get this problem all the time and have lost many hours of potential productivity and education while I try to fix it. The only thing that works for me is the combination of three other good answers:

1. Project -> Clean
2. Delete all the AVDs and create new ones
3. If an attempt to run still hangs too long on 'Waiting for HOME' (over two minutes) or the emulator keeps rebooting every minute or so, try Run as Android App several times, choosing the same existing emulator instance (I always choose runs manually).

It's odd that no one has a clue why this problem comes up, what causes it or what is going on internally. The only clue I can supply is that DDMS shows a few lines like "Class not found for preloading: libcore.base.CollectionUtils" during the 'Waiting for HOME' pause.

I had only 12 Mb for the SD Card in the AVD device.

Increasing it to 2 Gb solved the issue.

This problem occurs because while creating the AVD manager in the "Create new Android virtual device(AVD)" dialog window ,"Snapshot" was marked as "Enabled" by me.

Solution:

Create a new AVD manager with the "Enabled" checkbox not checked and then try running the project with the newly created AVD manager as "Target" , the problem will not occur anymore

I increased the virtual device SD card size from 500MB to 2GiB, the problem solved.

Following steps worked for me: 1. Goto Project -> Clean. 2. Delete your previous AVD and create a new one.

I solved this issue by creating a new virtual device and launching it from the AVD manager. The device takes a few minutes to start, you just have to wait. Then you can run your application on the already started device.

It worked for me when I selected 'Use Host GPU' option under 'Emulation Options:'.

You can find the option under Edit window of the virtual device.

I created a new device. Deleted the previous one.

I noticed this is an old post. However I just ran into the same problem and found a solution. A) Make sure you have the CPU/ABI is atom B)Ram is 2048 C)VM Heap is 256 D)Internal Storage is 200 E)Make sure to check the Use Host GPU F)Device is Nexus 5 (My personal choice) G)Android 4.4.2 API Level 19

I faced the same problem. However, it worked after i went to Project->Clean... Don't know why it happened though. Hope this helps

Following steps worked for me: 1. Goto Project -> Clean. 2. Delete your previous AVD and create a new one.

The solution which worked for me is, when you get the message:

Waiting for HOME ('android.process.acore') to be launched...

Wait for few seconds and then right click on the project and click run as Android application once again.

None of these solutions worked for me. Instead, what worked was to go to a command line tool (or terminal in Mac), CD into the SDK/platform-tools directory, and then run this:

adb kill-server

then run this:

adb start-server

After I did this everything worked again. Why? Who knows.

On my MAC the path to the platform-tools folder was $HOME/Installations/adt-bundle-mac-x86_64-20130522/sdk/platform-tools It will probably be somewhere else on your machine.

I also found this page that presents some helpful steps:

http://android.okhelp.cz/android-emulator-wont-run-application-started-from-eclipse/

What worked for me was enabling the checkbox "Use Host GPU" when creating or editing the AVD (Android Virtual Device). This checkbox was not enabled by default.