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

后端 未结 17 2635
陌清茗
陌清茗 2020-12-07 14:14

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 i

相关标签:
17条回答
  • 2020-12-07 15:06

    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.

    0 讨论(0)
  • 2020-12-07 15:08

    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

    0 讨论(0)
  • 2020-12-07 15:08

    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

    0 讨论(0)
  • 2020-12-07 15:10

    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
    0 讨论(0)
  • 2020-12-07 15:10

    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.

    0 讨论(0)
  • 2020-12-07 15:11

    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.

    0 讨论(0)
提交回复
热议问题