[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] ------------------------------
答案 0 :(得分:3)
尝试更改ADB连接超时。 我认为它默认为5000毫秒,我把我改为10000毫秒来解决这个问题。如果您在Eclipse中,可以通过浏览Window - >来完成此操作。首选项然后它在Android下的DDMS中。
答案 1 :(得分:1)
AVD出生(或变得)腐败/行为不端并不罕见。解决方法是制作一个新的AVD(具有相同的设置)并删除损坏/行为不端的。
另一个可能的问题是AVD会耗尽你的很多CPU,所以如果你的系统已经处于困境中,那么AVD启动和运行良好的可能性很小。