Develop Reference

Failed to install *.apk on device 'emulator-5554' error

[2015-01-21 14:27:38 - FirstAndroidProject] Launching a new emulator with Virtual Device 'Android_5.0.1'
[2015-01-21 14:27:51 - FirstAndroidProject] New emulator found: emulator-5554
[2015-01-21 14:27:51 - FirstAndroidProject] Waiting for HOME ('android.process.acore') to be launched...
[2015-01-21 14:30:52 - FirstAndroidProject] HOME is up on device 'emulator-5554'
[2015-01-21 14:30:52 - FirstAndroidProject] Uploading FirstAndroidProject.apk onto device 'emulator-5554'
[2015-01-21 14:30:53 - FirstAndroidProject] Installing FirstAndroidProject.apk...
[2015-01-21 14:33:00 - FirstAndroidProject] Failed to install FirstAndroidProject.apk on device 'emulator-5554!
[2015-01-21 14:33:00 - FirstAndroidProject] (null)
[2015-01-21 14:33:01 - FirstAndroidProject] Launch canceled!
This is my very first Android app. I tried every possible way explained in solutions provided in stackoverflow.com but every time I launched the app I get the above error in the console.
But on every time I opened the icon in the menu list in the emulator after the above message is displayed, the app opens successfully. What is actually meant by the above error?

Kill your adb manually in the your processes after close the emulator, restart your eclipse..

Clean your project and restart the emulator. Then, try launching the app again.

How to resolve uploading project.apk onto Device Timeout

I am attempting to launch my application but this is what I get. I am using Eclipse with ADD.I am trying to run this project but it seems it cant get uploaded on the virtual device
any suggestions on how I could resolve this ?
[2012-10-05 04:44:10 - Android_Test] ------------------------------
[2012-10-05 04:44:10 - Android_Test] Android Launch!
[2012-10-05 04:44:10 - Android_Test] adb is running normally.
[2012-10-05 04:44:10 - Android_Test] Performing com.example.android_test.MainActivity activity launch
[2012-10-05 04:44:10 - Android_Test] Automatic Target Mode: launching new emulator with compatible AVD 'TestDevice'
[2012-10-05 04:44:10 - Android_Test] Launching a new emulator with Virtual Device 'TestDevice'
[2012-10-05 04:44:12 - Android_Test] New emulator found: emulator-5554
[2012-10-05 04:44:12 - Android_Test] Waiting for HOME ('android.process.acore') to be launched...
[2012-10-05 04:45:04 - Android_Test] HOME is up on device 'emulator-5554'
[2012-10-05 04:45:04 - Android_Test] Uploading Android_Test.apk onto device 'emulator-5554'
[2012-10-05 04:45:09 - Android_Test] Failed to install Android_Test.apk on device 'emulator-5554': timeout
[2012-10-05 04:45:09 - Android_Test] Launch canceled!

Go to > Window menu >Preferences > Android > DDMS > increase value of ADB connection Time out
if this not works then try..
Reset ADB from DDMS > Devices > Reset ADB (down arrow from right corner)
if this fails then you have to restart your AVD

Android Development on Eclipse: Always opens new emulator

This should be a really simple one. I am doing the Hello Android tutorial and I was able to get my app to install into the emulator. However, when I go to run again (with no changes) the eclipse environment insists on launching a new emulator instead of connecting to the existing one. How do I fix that? My development environment is a Mac Mini running Mac OS 10.6.8.
Thanks.
New Update:
I have found the answer:
First I read this [question linked above by Mangusto][1]
Use same android emulator everytime
Then I realized that what one really needs to do, if the emulator is opening and initializing slowly, is to start the emulator, wait for it to initialize, and then attach to it the manual way described in the link above. Automatic does not work if your emulator is starting slowly as it disconnects as I described in the update below.
Thanks for the responses.
Update:
Below is the print out from eclipse (I tried to link image but could not due to my user level. I need reputation level of 10 or more). I had already tried the suggestion below about automatic vs manual. I think the issue is that while the apk file was installed it did not automatically launch in the emulator. Therefore, eclipse disconnected from the emulator. I was able to see my application by navigating to the apps within the android emulator.
[2011-11-24 08:25:34 - SDK Manager] Created AVD 'myAvd' based on Android 4.0, ARM (armeabi-v7a) processor,
[2011-11-24 08:25:34 - SDK Manager] with the following hardware config:
[2011-11-24 08:25:34 - SDK Manager] hw.lcd.density=240v
[2011-11-24 08:25:34 - SDK Manager] vm.heapSize=24
[2011-11-24 08:25:34 - SDK Manager] hw.ramSize=512
[2011-11-24 08:29:17 - HelloAndroid] ------------------------------
[2011-11-24 08:29:17 - HelloAndroid] Android Launch!
[2011-11-24 08:29:17 - HelloAndroid] adb is running normally.
[2011-11-24 08:29:17 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch
[2011-11-24 08:29:17 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'myAvd'
[2011-11-24 08:29:17 - HelloAndroid] Launching a new emulator with Virtual Device 'myAvd'
[2011-11-24 08:29:25 - Emulator] 2011-11-24 08:29:25.377 emulator-arm[984:80b] 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-11-24 08:29:25 - HelloAndroid] New emulator found: emulator-5554
[2011-11-24 08:29:25 - HelloAndroid] Waiting for HOME ('android.process.acore') to be launched...
[2011-11-24 08:31:29 - HelloAndroid] HOME is up on device 'emulator-5554'
[2011-11-24 08:31:29 - HelloAndroid] Uploading HelloAndroid.apk onto device 'emulator-5554'
[2011-11-24 08:31:29 - HelloAndroid] Installing HelloAndroid.apk...
[2011-11-24 08:33:36 - HelloAndroid] Failed to install HelloAndroid.apk on device 'emulator-5554!
[2011-11-24 08:33:36 - HelloAndroid] (null)
[2011-11-24 08:33:36 - HelloAndroid] Failed to install HelloAndroid.apk on device 'emulator-5554': Connection reset by peer
[2011-11-24 08:33:36 - HelloAndroid] com.android.ddmlib.InstallException: Connection reset by peer
[2011-11-24 08:33:36 - HelloAndroid] Launch canceled!
[2011-11-24 08:34:55 - HelloAndroid] ------------------------------
[2011-11-24 08:34:55 - HelloAndroid] Android Launch!
[2011-11-24 08:34:55 - HelloAndroid] adb is running normally.
[2011-11-24 08:34:55 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch
[2011-11-24 08:34:55 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'myAvd'
[2011-11-24 08:34:55 - HelloAndroid] Launching a new emulator with Virtual Device 'myAvd'
[2011-11-24 08:35:03 - Emulator] WARNING: Data partition already in use. Changes will not persist!
[2011-11-24 08:35:05 - Emulator] WARNING: Cache partition already in use. Changes will not persist!
[2011-11-24 08:35:06 - Emulator] 2011-11-24 08:35:06.756 emulator-arm[1004:80b] 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-11-24 08:35:06 - HelloAndroid] New emulator found: emulator-5556
[2011-11-24 08:35:06 - HelloAndroid] Waiting for HOME ('android.process.acore') to be launched...
[2011-11-24 08:35:11 - HelloAndroid] emulator-5556 disconnected! Cancelling 'com.example.helloandroid.HelloAndroid activity launch'!
[2011-11-24 08:42:36 - HelloAndroid] ------------------------------
[2011-11-24 08:42:36 - HelloAndroid] Android Launch!
[2011-11-24 08:42:36 - HelloAndroid] adb is running normally.
[2011-11-24 08:42:36 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch
[2011-11-24 08:42:36 - HelloAndroid] Automatic Target Mode: Preferred AVD 'myAvd' is not available. Launching new emulator.
[2011-11-24 08:42:36 - HelloAndroid] Launching a new emulator with Virtual Device 'myAvd'

Its because your application Target mode has set to manual. To solve :
Right Click on your project-> Run as -> Select Run Configurations ->
In that select Target Tab ->Select Automatic instead of manual
Click on Apply and run.
Now your app doesn't prompt for a device.
For a reverse case Select Manual.
Hope it helps.

Go to DDMS Perspective and if you can't see any emulator device on the list, Find the "View menu" dropdown on the "Devices" window on the left, and click Reset ADB.
After adb restarted it should be able to show all of your devices again.

Me also had the same problem.First of all clean your project.Take the DDMS mode in the eclipse .Here you are able to handle the devices in the emulator.There you can see the emulator control.From there select your device and run it.Hope it will solve your problem.

I had BlueStacks android app player installed. Its an application that runs on mac and pc allowing you to emulate android. Looks like it uses the android emulator under the covers. To uninstall on mac, go to Library>bluestacksplayer and uninstall app ... .solved the emulator 5554 problem.

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

Ive seen the questions posted about this issue. I understand it takes several minutes for the emulator to configure itself and launch. But if Im getting the 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
couldnt it be I have a bad configuration...?

wait for the emulator to setup completely and then test your app. Also, I would leave you AVD open so you dont have to wait so long everytime you run your application.
When it shows the red writing, don't close anything - leave it there and then press the run button again. Worked like a charm.

I was facing the same problem but i tried changing the ADB connection timeout. I think it defaults that to 5000ms and I changed mine to 10000ms to get rid of that problem. If you are in Eclipse, you can do this by going through Window -> Preferences and then it is in DDMS under Android.

Try this: create another emulator in AVD Manager and try to run your application in the new emulator.
Hope this might help you

You may need to increase the device ram size. For some Honeycomb AVDs at least, the default of 256 is insufficient, and caused me the same problem. Try at least 512.

Go to window and preference and increase the ADB connection time out(ms) which is 500 by default. Also change the base local debugger port to more than 9000 in my case it worked.

See Related post
This worked on Linux for me:
Run Emulator (Wait for the home screen of the Emulator to load)
Click Window > Open Perspective > DDMS
In Devices Panel, click on drop down menu > Reset adb
Run project

Valen answer is correct although its nice to know when to start running the app and when is not ok to start the app.Open the devices perspective. The next time you want to run an app first open the 'Android virtual device Manager' and run your avd then click on the device perspective and watch your emulator processes one by one firing up.. as soon this is done (its not fast you have to wait .. but at least you have some idea of whats going on .... a progress bar would be ideal for this place), click on your project and run as android app. On the devices perspective one more process will appear with the name of the package of your app. As soon as this happen your app is running on the device and it can be tested.

I have noticed this error when the emulator has not loaded fully, "android" is flashing on your screen. In other words, it is not yet ready for the application to be installed.
Just wait till you see that the emulator is fully ready, meaning the "android" has vanished and the device screen is visible on the emulator. Now run it and the application loads smoothly.

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

Android device not found

I'm trying to build "Hello, Android" with the Android SDK, but Android won't say "hello" to me.
I build with the 2.6 version of the SDK and run in Eclipse on Win XP. (I've installed the plug-in.)
Here's what I get:
[2009-09-23 16:35:19 -
HelloAndroid]Android Launch!
[2009-09-23 16:35:19 -
HelloAndroid]adb is running normally.
[2009-09-23 16:35:19 -
HelloAndroid]Performing
com.example.helloandroid.HelloAndroid
activity launch
[2009-09-23 16:35:19 -
HelloAndroid]Automatic Target Mode:
launching new emulator with compatible
AVD 'my_avd'
[2009-09-23 16:35:19 -
HelloAndroid]Launching a new emulator
with Virtual Device 'my_avd'
[2009-09-23 16:35:21 -
HelloAndroid]New emulator found:
emulator-5554
[2009-09-23 16:35:21 -
HelloAndroid]Waiting for HOME
('android.process.acore') to be
launched...
[2009-09-23 16:36:20 -
HelloAndroid]HOME is up on device
'emulator-5554'
[2009-09-23 16:36:20 -
HelloAndroid]Uploading
HelloAndroid.apk onto device
'emulator-5554'
[2009-09-23 16:36:30 -
HelloAndroid]Installing
HelloAndroid.apk...
[2009-09-23 16:36:43 -
HelloAndroid]Success!
[2009-09-23 16:36:44 -
HelloAndroid]Starting activity
com.example.helloandroid.HelloAndroid
on device
[2009-09-23 16:36:44 -
HelloAndroid]Launch error:
device (emulator-5554) request
rejected: device not found

I got this to work. It may be a timing issue. Have to press Menu button on emulator keypad to unlock the screen. Then the output is displayed.