HelloAndroid] 5554 emulator is disabled! Cancel launch com.example.helloandroid.HelloAndroid!

Question

I am new to Android. Follow the instructions of HelloAndroid using Eclipse. After starting HelloAndroid, AVD "xian_avd2" dined, but stop there, there is no "Hello, Android" displayed on AVD. Similar to Waiting for HOME ('android.process.acore') to be launched ...

I do not know how to solve this, please help. thanks wang813

[2010-01-29 00:12:13 - HelloAndroid]------------------------------ [2010-01-29 00:12:13 - HelloAndroid]Android Launch! [2010-01-29 00:12:13 - HelloAndroid]adb is running normally. [2010-01-29 00:12:13 - HelloAndroid]Performing com.example.helloandroid.HelloAndroid activity launch [2010-01-29 00:12:13 - HelloAndroid]Automatic Target Mode: Preferred AVD 'xian_avd2' is not available. Launching new emulator. [2010-01-29 00:12:14 - HelloAndroid]Launching a new emulator with Virtual Device 'xian_avd2' [2010-01-29 00:12:37 - HelloAndroid]New emulator found: emulator-5554 [2010-01-29 00:12:37 - HelloAndroid]Waiting for HOME ('android.process.acore') to be launched... [2010-01-29 00:13:59 - HelloAndroid]emulator-5554 disconnected! Cancelling 'com.example.helloandroid.HelloAndroid activity launch'! 

Answer 1

• Open Android Virtual Device Manager
• select the AVD that you use for your application.
• Click the "Start" button and wait for the appearance of a new form ("Launch Options").
• Check the "Wipe user data" box and click the "Run" button.

That should work.

--- OR ---

• Open Android Virtual Device Manager
• Remove the AVD you are using for your application.
• Create a new AVD.
• Launch a new AVD.

This should also work.

Answer 2

Try using the command emulator -avd emulator_name -wipe-data

Answer 3

The problem that I discovered is that the project does not have the corresponding virtual device defined for it in the AVD manager.

So, the recommended steps in eclipse are:

• Go to the "Project" section → Properties-> Android.
• In the right pane, see which row is marked in the target assembly of the project.
  Remember the number of the target platform that appears on the selected line.
• Go to the Windows section → AVD Manager.
• Check the list of existing Android Android devices for a device that matches the platform level and API set for your project (see step # 2 above).
• If there is no line containing AVD for your platform (as I suspect), add it using the "Create" button.
• The Create New Virtual Android Device window opens. set a new device name. in the "Target" selection box, select the correct platform for your project.

Enjoy the emulator again!

Answer 4

I had a similar problem - in the end, I did not expect long enough until the emulator started the OS before trying to install the application. Launch the emulator, and then wait for the main screen to appear before launching the application in Eclipse.

Answer 5

Perhaps this is an AVD problem for an existing machine. Try to create a new AVD from the AVD Manager and delete the old one.

Answer 6

This can happen on slow computers when the emulator does not start on time. When it eventually starts, it no longer connects to ADB. The solution is to restart ADB so that it reconnects to the emulator. You can do this by doing the following at a command prompt:

 adb kill-server adb start-server 

Answer 7

For me, I believe that this was due to an unexpected power failure during the operation of the emulator. If it is not closed, it meant that my session was still cached. (Sometimes I get these errors too):

 [2012-06-08 05:05:06 - Emulator] WARNING: Data partition already in use. Changes will not persist! [2012-06-08 05:05:06 - Emulator] WARNING: SD Card image already in use: C:\Users\Ben\.android\avd\Ben-Android.avd/sdcard.img [2012-06-08 05:05:06 - Emulator] WARNING: Cache partition already in use. Changes will not persist! 

If this happened to you, pull up the command line, go to your android-sdk \ tools and follow the top messages corrected: emulator -avd emulator_name -wipe-data p>

Answer 8

I solved this (Mac) by following these steps:

• Run emulator
• Store the emulator (no matter what the error)
• Make sure the emulator main screen appears.
• go to the window → Show perspective → DDMS → In the "Devices" panel → in the "Angular drop-down menu" drop-down menu → Reset adb

Hope this helps

Answer 9

didn’t work for me:

 ./emulator -noaudio @androidDev1 

so i used:

 ./emulator @androidDev1 

and it works great! :)

Also check out the Eclipse IDE:

 Windows->Preferences->Android->Launch->Options 

It must be empty

Answer 10

I had the same problem, I deleted my AVD and recreated it - after that I do not see such problems.

Answer 11

also the same problem for me ..

go to the DDMS page → select "Device" → "Go" to "Window" → "Navigation" → "Show browse menu" → reset adb .. it works for me.

Answer 12

Disable the snapshot and do not use it. This is what solved this problem in my case

Answer 13

delete avd and create another one helped me

Answer 14

Try again 1 time. If this happens again

Go to Project-> clean and

Right-click your project and select update.

Answer 15

This worked on Linux for me:

• Launch the emulator (Wait until the emulator main screen loads)
• Click Window> Open Perspective> DDMS
• In the Devices panel, click the drop-down menu> Reset adb
• Run project

Answer 16

It boils down to just creating an AVD with moderate settings, at least by fixing it for me. Although every time I close it, I have to create a new one. Guess just wait for the patch.

Click the Android Device Manager button on the second toolbar.

Click Create.

Set up a mid-range device, basically just select a phone model from the middle of the list, which is not a tablet. The memory should fill it on its own, and then just put as 20 MB for the SD card.

Click Start. Now AVD launches and loads the Android OS.

Then run the application on the specified device.

Once you get this problem, it seems like it will remain if you do not complete the full reinstall ... Basically, always start AVD, let it get to the Android main screen, and then run the application. Thus, Eclipse does not overload the sluggish emulator.

Answer 17

And I got a solution from here . This works great for me.