Develop Reference

Failed to install HelloWorld.apk on device

[2015-04-27 22:12:51 - HelloWorld] ------------------------------
[2015-04-27 22:12:51 - HelloWorld] Android Launch!
[2015-04-27 22:12:51 - HelloWorld] adb is running normally.
[2015-04-27 22:12:51 - HelloWorld] Performing com.example.helloworld.MainActivity activity launch
[2015-04-27 22:12:51 - HelloWorld] Automatic Target Mode: launching new emulator with compatible AVD 'Android1'
[2015-04-27 22:12:51 - HelloWorld] Launching a new emulator with Virtual Device 'Android1'
[2015-04-27 22:14:14 - HelloWorld] New emulator found: emulator-5554
[2015-04-27 22:14:14 - HelloWorld] Waiting for HOME ('android.process.acore') to be launched...
[2015-04-27 22:17:28 - HelloWorld] HOME is up on device 'emulator-5554'
[2015-04-27 22:17:28 - HelloWorld] Uploading HelloWorld.apk onto device 'emulator-5554'
[2015-04-27 22:17:35 - HelloWorld] Installing HelloWorld.apk...
[2015-04-27 22:20:05 - HelloWorld] Failed to install HelloWorld.apk on device 'emulator-5554!
[2015-04-27 22:20:05 - HelloWorld] (null)
[2015-04-27 22:20:06 - HelloWorld] Launch canceled!
I am getting this error message. Changed DDMS time, checked manifest file for target SDK version, uninstalled and installed ADT plugin, deleted and created AVD, but I did not disable USB debugging. How to do that? Also any other thing I need to do?

USB debugging can be turned off and on in the Developer Settings on your device. You must have developer options turned on to use this. In case you don't, go into About Phone and tap on the Kernel Version 6 times (or until it says you are now a developer).

AVD Not Booting E/dalvikvm No valid entries found in bootclasspath

I'm unable to start my AVD. I've uninstalled and installed it 2nd time. Still the same. I have kept the AVD for approx half an hour, Still no luck.
Below is the Console log i get when try to run the Application in AVD.
[2014-02-12 20:43:02 - HelloAndroid] ------------------------------
[2014-02-12 20:43:02 - HelloAndroid] Android Launch!
[2014-02-12 20:43:02 - HelloAndroid] adb is running normally.
[2014-02-12 20:43:02 - HelloAndroid] Performing com.example.helloandroid.MainActivity activity launch
[2014-02-12 20:43:02 - HelloAndroid] Automatic Target Mode: Unable to detect device compatibility. Please select a target device.
[2014-02-12 20:43:05 - HelloAndroid] Launch canceled!
[2014-02-12 20:44:38 - HelloAndroid] ------------------------------
[2014-02-12 20:44:38 - HelloAndroid] Android Launch!
[2014-02-12 20:44:38 - HelloAndroid] adb is running normally.
[2014-02-12 20:44:38 - HelloAndroid] Performing com.example.helloandroid.MainActivity activity launch
[2014-02-12 20:44:38 - HelloAndroid] Automatic Target Mode: Unable to detect device compatibility. Please select a target device.
[2014-02-12 20:44:49 - HelloAndroid] Launching a new emulator with Virtual Device 'AVD_for_Nexus_4_by_Google'
[2014-02-12 20:45:23 - Emulator] bind: Permission denied
[2014-02-12 20:45:23 - HelloAndroid] New emulator found: emulator-5558
[2014-02-12 20:45:23 - HelloAndroid] Waiting for HOME ('android.process.acore') to be launched...
And attached is the logcat when starting the AVD from AVD Manager.
http://sdrv.ms/1bWRKru

I think there is a problem in mounting the data partition or its not available.
In a real device, if you have not flashed the data partition properly, with fastboot, the same issue will occur.

Failed to install JudoApp.apk on device 'emulator-5554

I have checked my api level of the device and the program i'm creating. I have also restarted my eclipse and the problem still does not seem to resolve. is there any other solutions to this ?
[2014-02-15 19:31:39 - JudoApp] New emulator found: emulator-5554
[2014-02-15 19:31:39 - JudoApp] Waiting for HOME ('android.process.acore') to be launched...
[2014-02-15 19:42:15 - JudoApp] HOME is up on device 'emulator-5554'
[2014-02-15 19:42:15 - JudoApp] Uploading JudoApp.apk onto device 'emulator-5554'
[2014-02-15 19:42:16 - JudoApp] Installing JudoApp.apk...
[2014-02-15 19:44:37 - JudoApp] Failed to install JudoApp.apk on device 'emulator-5554!
[2014-02-15 19:44:37 - JudoApp] (null)
[2014-02-15 19:44:38 - JudoApp] Launch canceled!

change ADB connection timeout from ddms (default is 5.000,change it to 10.000)

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.