Android Emulator boots with flashy “Android”, but the application never starts and I don’t see any main screen

Question

Android Emulator is loaded using flashy "Android", but the application never starts, and I will not see any main screen even after waiting 30 minutes. I am using a PC with 2 GB RAM, but I can not see the hOme screen on Emullator .. The console is like

[2012-02-26 17:36:52 - SDK Manager] Created AVD 'GingerBread2.3.3' based on Android 2.3.3, ARM (armeabi) processor, [2012-02-26 17:36:52 - SDK Manager] with the following hardware config: [2012-02-26 17:36:52 - SDK Manager] hw.lcd.density=160 [2012-02-26 17:36:52 - SDK Manager] vm.heapSize=24 [2012-02-26 17:36:52 - SDK Manager] hw.ramSize=256 [2012-02-26 17:37:11 - test_ball_handler] New emulator found: emulator-5554 [2012-02-26 17:37:11 - test_ball_handler] Waiting for HOME ('android.process.acore') to be launched... [2012-02-26 17:42:00 - test_ball_handler] ------------------------------ [2012-02-26 17:42:00 - test_ball_handler] Android Launch! [2012-02-26 17:42:00 - test_ball_handler] adb is running normally. [2012-02-26 17:42:00 - test_ball_handler] Performing com.eg.a.Test_ball_handlerActivity activity launch [2012-02-26 17:42:00 - test_ball_handler] Automatic Target Mode: using existing emulator 'emulator-5554' running compatible AVD 'GingerBread2.3.3' [2012-02-26 17:42:00 - test_ball_handler] Uploading test_ball_handler.apk onto device 'emulator-5554' [2012-02-26 17:42:01 - test_ball_handler] Installing test_ball_handler.apk... [2012-02-26 17:44:15 - test_ball_handler] Failed to install test_ball_handler.apk on device 'emulator-5554! [2012-02-26 17:44:15 - test_ball_handler] (null) [2012-02-26 17:44:15 - test_ball_handler] Launch canceled! [2012-02-26 17:47:56 - test_ball_handler] ------------------------------ 

Answer 1

Try changing the ADB connection timeout. I think this is the default, which is up to 5000 ms, and I changed mine to 10000 ms to get rid of this problem. If you are in Eclipse, you can do this by going through Window -> Preferences, and then into DDMS for Android.

Answer 2

It is not uncommon for AVD to be born (or become) corrupt / wrong. The solution for this is to create a new AVD (with the same settings) and remove the damaged / incorrect.

Another possible problem is that AVD can eat a lot of your processor, so if your system is already in the city of struggle, the chances of downloading and starting AVD are beautiful.