Failed to install HelloAndroid.apk on device emulator-5554!

I saw questions posted on this issue. I understand that it takes several minutes for the emulator to configure itself and run. But if Im getting a specific error:

[2011-05-13 08:41:36 - HelloAndroid] ------------------------------ [2011-05-13 08:41:36 - HelloAndroid] Android Launch! [2011-05-13 08:41:36 - HelloAndroid] adb is running normally. [2011-05-13 08:41:36 - HelloAndroid] Performing com.santiapps.helloandroid.HelloAndroid activity launch [2011-05-13 08:41:36 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'my_avd' [2011-05-13 08:41:36 - HelloAndroid] Launching a new emulator with Virtual Device 'my_avd' [2011-05-13 08:41:49 - Emulator] 2011-05-13 08:41:49.650 emulator[411:903] Warning once: This application, or a library it uses, is using NSQuickDrawView, which has been deprecated. Apps should cease use of QuickDraw and move to Quartz. [2011-05-13 08:41:50 - Emulator] emulator: emulator window was out of view and was recentred [2011-05-13 08:41:50 - Emulator] [2011-05-13 08:41:50 - HelloAndroid] New emulator found: emulator-5554 [2011-05-13 08:41:50 - HelloAndroid] Waiting for HOME ('android.process.acore') to be launched... [2011-05-13 08:44:33 - HelloAndroid] WARNING: Application does not specify an API level requirement! [2011-05-13 08:44:33 - HelloAndroid] Device API version is 12 (Android 3.1) [2011-05-13 08:44:33 - HelloAndroid] HOME is up on device 'emulator-5554' [2011-05-13 08:44:33 - HelloAndroid] Uploading HelloAndroid.apk onto device 'emulator-5554' [2011-05-13 08:44:34 - HelloAndroid] Installing HelloAndroid.apk... [2011-05-13 08:47:20 - HelloAndroid] Failed to install HelloAndroid.apk on device 'emulator-5554! [2011-05-13 08:47:20 - HelloAndroid] (null) [2011-05-13 08:47:22 - HelloAndroid] Launch canceled! [2011-05-13 08:53:55 - HelloAndroid] ------------------------------ [2011-05-13 08:53:55 - HelloAndroid] Android Launch! [2011-05-13 08:53:55 - HelloAndroid] adb is running normally. [2011-05-13 08:53:55 - HelloAndroid] Performing com.santiapps.helloandroid.HelloAndroid activity launch [2011-05-13 08:53:55 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'my_avd' [2011-05-13 08:53:55 - HelloAndroid] Launching a new emulator with Virtual Device 'my_avd' [2011-05-13 08:54:06 - Emulator] 2011-05-13 08:54:06.327 emulator[460:903] Warning once: This application, or a library it uses, is using NSQuickDrawView, which has been deprecated. Apps should cease use of QuickDraw and move to Quartz. [2011-05-13 08:54:06 - Emulator] emulator: emulator window was out of view and was recentred [2011-05-13 08:54:06 - Emulator] [2011-05-13 08:54:06 - HelloAndroid] New emulator found: emulator-5554 [2011-05-13 08:54:06 - HelloAndroid] Waiting for HOME ('android.process.acore') to be launched... [2011-05-13 09:08:07 - Emulator] emulator: ERROR: unexpected qemud char. channel close 

Could it be that I have a bad configuration ...?

+16
android
May 13, '11 at 15:14
source share
9 answers

wait until the emulator is fully configured, and then test your application. Also, I would leave you AVD open, so you don’t have to wait so long every time you launch your application.

When it shows a red letter, do not close anything - leave it there, and then press the start button again. Worked like a charm.

+46
May 15 '11 at a.m.
source share

I had the same problem, but I tried to change the timeout of the ADB connection. 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.

+8
Mar 06 '13 at 6:20
source share

Try it: create another emulator in AVD Manager and try to run the application in a new emulator. Hope this helps you.

+3
May 13 '11 at 15:50
source share

You may need to increase the size of the device. For some Honeycomb AVDs, a default of 256 by default is not enough, and it caused me the same problem. Try at least 512.

+1
Mar 21 '12 at 12:15
source share

Go to the window and preferences and increase the connection timeout (ms), which is 500 by default. Also change the base local port of the debugger to more than 9000 in my case, if it works.

0
May 10 '13 at
source share

See Related Post

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
0
Sep 05 '13 at 5:37 on
source share

Valen's answer is correct, although it’s nice to know when to start the application and when not suitable, start the application . Open the device perspective. The next time you want to run the application, first open the “Android Virtual Device Manager” and start your avd, then click on the device’s view and watch how your emulator processes one by one as soon as it is done (it won’t be fast wait .. but at least you have an idea of ​​what is happening .... the progress indicator is perfect for this place), click on your project and launch the Android application. In the device perspective, another process will appear with the package name of your application. Once this happens, your application runs on the device and it can be tested.

0
Sep 01 '14 at 0:03
source share

I noticed this error when the emulator is not fully loaded, "android" flashes on the screen. In other words, it is not yet ready to install the application.

Wait until you see that the emulator is completely ready, which means that the “android” has disappeared and the device screen is displayed on the emulator. Now run it and the application loads smoothly.

0
Sep 10 '15 at 14:10
source share

Restart the ADB server from DMOZ or refer to this guide. How to solve. Failed to install .apk

0
Dec 30 '15 at 10:10
source share



All Articles