Develop Reference

Emulator Takes Much Time and at the end it Fail

I am new to developing Android applications. My first application takes too much time to load, and fails at the end.
I'm using a Windows 8 laptop with 4GB of RAM and an Intel processor. I'm writing all of this because I saw an answer regarding Windows.
[2014-03-08 07:26:52 - Mytest] Android Launch! [2014-03-08 07:26:52 -
Mytest] adb is running normally.
[2014-03-08 07:26:52 - Mytest] Performing
com.example.mytest.MainActivity activity launch
[2014-03-08 07:26:53 - Mytest] Automatic Target Mode: launching new
emulator with compatible AVD 'nnt'
[2014-03-08 07:26:53 - Mytest] Launching a new emulator with Virtual
Device 'nnt'
[2014-03-08 07:27:15 - Mytest] New emulator found: emulator-5554
[2014-03-08 07:27:15 - Mytest] Waiting for HOME
('android.process.acore') to be launched
[2014-03-08 07:39:36 - Mytest] HOME is up on device 'emulator-5554'
[2014-03-08 07:39:36 - Mytest] Uploading Mytest.apk onto device
'emulator-5554'
[2014-03-08 07:39:36 - Mytest] Installing Mytest.apk...
[2014-03-08 07:41:51 - Mytest] Failed to install Mytest.apk on device
'emulator-5554!
[2014-03-08 07:41:51 - Mytest] (null) [2014-03-08 07:41:51 - Mytest]
Launch canceled!
Please let me know.

I have had this problem before. I have tried following steps.
Plug-in your charger, if it's not connected.
Start emulator from AVD - manager, this works for most of the time.

Try Genymotion emulator, it is free for personal use and it works smooth. You also can use Eclipse plug-in.
Get it here: Genymotion
If you having troubles with installation, here is User Guide.
I am using it and I am very happy.

AVD is not working properly

I am trying to create a android application in eclipse .When i am running the application it is showing
[2013-06-26 11:14:41 - FirstApp] Android Launch!
[2013-06-26 11:14:41 - FirstApp] adb is running normally.
[2013-06-26 11:14:41 - FirstApp] Performing com.example.firstapp.MainActivity activity launch
[2013-06-26 11:14:41 - FirstApp] Automatic Target Mode: launching new emulator with compatible AVD 'Test'
[2013-06-26 11:14:41 - FirstApp] Launching a new emulator with Virtual Device 'Test'
[2013-06-26 11:14:50 - FirstApp] New emulator found: emulator-5554
[2013-06-26 11:14:50 - FirstApp] Waiting for HOME ('android.process.acore') to be launched...
[2013-06-26 11:16:24 - FirstApp] HOME is up on device 'emulator-5554'
[2013-06-26 11:16:24 - FirstApp] Uploading FirstApp.apk onto device 'emulator-5554'
[2013-06-26 11:16:25 - FirstApp] Installing FirstApp.apk...
[2013-06-26 11:18:30 - FirstApp] Failed to install FirstApp.apk on device 'emulator-5554!
[2013-06-26 11:18:30 - FirstApp] (null)
[2013-06-26 11:18:30 - FirstApp] Launch canceled!

I also faced the same issue once and one of the following should work for you:-
Restart the virtual device with the option Wipe User Data checked and then run the app. That works for me,
Simply restart the device and check,
Restart the device after changing the VM heap size.
If restarting the device doesn't work, try increasing the upload timeout to something really huge like 20000 ms. It's at Window → Preferences → Android → DDMS → "ADB connection time out (ms)".

Please post your AndroidManifest.xml code as well. I think u didn't placed the below code for Activity to be launched.
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
If any logcat errors/warnings present, please post them as well. So, that we can help much better.

Try and format the log output so that its better readable. However, most likely you have something wrong in your Manifest. Check adb logcat (or the Logcat Tab in the DDMS perspective) while the app is installed. You should see some info there on what exactly android does not like with your application.

Why is the emulator in eclipse restarting?

I am following http://developer.android.com/training/basics/firstapp/running-app.html
and trying to run my first android app on the emulator on my PC.
The emulator is running (started from eclipse)
I managed to lauch myFirst App via eclipse as described, although in this tutorial it should be added you have to wait minutes before the emulator is up and running.
Now my problem is that when I modify myFirstApp, and wnat to test it, that eclipse keeps starting a new emulator:
[2012-10-15 19:32:44 - MyFirstApp] ------------------------------
[2012-10-15 19:32:44 - MyFirstApp] Android Launch!
[2012-10-15 19:32:44 - MyFirstApp] adb is running normally.
[2012-10-15 19:32:45 - MyFirstApp] Performing com.example.myfirstapp.MainActivity activity launch
[2012-10-15 19:32:45 - MyFirstApp] Automatic Target Mode: Preferred AVD 'Hobbit' is not available. Launching new emulator.
[2012-10-15 19:32:45 - MyFirstApp] Launching a new emulator with Virtual Device 'Hobbit'
This is extremely annoying, because of the performance penalty to launch a complete emulator.
But what is even more frustrating that I get back the very first version of MyFirstApp in this new emulator.
When I restart myself the emulator from scratch I see this in the console:
[2012-10-15 19:55:42 - MyFirstApp] New emulator found: emulator-5554
[2012-10-15 19:55:42 - MyFirstApp] Waiting for HOME ('android.process.acore') to be launched...
[2012-10-15 19:56:57 - MyFirstApp] emulator-5554 disconnected! Cancelling 'com.example.myfirstapp.MainActivity activity launch!'
Why? The emulator is still running at this point. This cannot be the normal way of working. Can anybody help me out?

Go to Run -> Run Configuration in eclipse. Select your application and update the target tab at right side to "Always prompt to pick device"

If the emulator is running and doesnt show in Devices then try to reset adb.
In eclipse: Device tab-> Dropbown - > reset abd

hello world fails to show up in emulator

I followed Hello World tutorial exactly. Emulator comes up but fails to show Hello World text. Here's the log info:
[2011-11-26 20:06:57 - HelloAndroid] Android Launch!
[2011-11-26 20:06:57 - HelloAndroid] adb is running normally.
[2011-11-26 20:06:57 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch
[2011-11-26 20:06:57 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'AndroidPhone'
[2011-11-26 20:06:57 - HelloAndroid] Launching a new emulator with Virtual Device 'AndroidPhone'
[2011-11-26 20:07:09 - HelloAndroid] New emulator found: emulator-5554
[2011-11-26 20:07:09 - HelloAndroid] Waiting for HOME ('android.process.acore') to be launched...
[2011-11-26 20:45:37 - HelloAndroid] HOME is up on device 'emulator-5554'
[2011-11-26 20:45:37 - HelloAndroid] Uploading HelloAndroid.apk onto device 'emulator-5554'
[2011-11-26 20:45:38 - HelloAndroid] Installing HelloAndroid.apk...
After about 1/2 hour, this shows up in the log...
[2011-11-26 20:48:59 - HelloAndroid] Failed to install HelloAndroid.apk on device 'emulator-5554!
[2011-11-26 20:48:59 - HelloAndroid] (null)
[2011-11-26 20:49:02 - HelloAndroid] Launch canceled!
I’ve read posts on similar problem. I’ve tried many suggested solutions including restarting Eclipse, rebooting and restarting eclipse, creating a new project in eclipse, starting emulator first with “wipe user data” box checked, increasing the emulator time-out period from 5000 to 20000, unlocking emulator by clicking and dragging mouse, clicking Menu and Home buttons on emulator, and running the Layout version. Nothing worked. I’m using Android 4.0 AVD and Eclipse Build id: 20110916-0149 and the latest JDC on a Dell Inspiron 1501 laptop.
It’s hard to believe Google would make this discouraging example as the first impression new users experience. Hopefully someone can help.

When you have the "Failed to install HelloAndroid.apk on device 'emulator-5554!", try to wait some seconds,
dont close the VM and
reclick on "Launch Buton"

When you create a new Activity project, it effectively creates a Hello World app. Create a new project. Don't modify it. Just run it. If you don't see a Hello world message, check your install.

emulator: ERROR: the user data image is used by another emulator. aborting

[2011-02-09 23:59:11 - Timerproject] ------------------------------
[2011-02-09 23:59:11 - Timerproject] Android Launch!
[2011-02-09 23:59:11 - Timerproject] adb is running normally.
[2011-02-09 23:59:11 - Timerproject] Performing acarin.timetracker.project.ezhil.Timerproject activity launch
[2011-02-09 23:59:11 - Timerproject] Automatic Target Mode: Preferred AVD 'MA_AVD_2.3.1' is not available. Launching new emulator.
[2011-02-09 23:59:11 - Timerproject] Launching a new emulator with Virtual Device 'MA_AVD_2.3.1'
[2011-02-09 23:59:31 - Timetracker] New emulator found: emulator-5554
[2011-02-09 23:59:31 - Timetracker] Waiting for HOME ('android.process.acore') to be launched...
[2011-02-10 00:01:40 - Timetracker] HOME is up on device 'emulator-5554'
[2011-02-10 00:01:40 - Timetracker] Uploading Timetracker.apk onto device 'emulator-5554'
[2011-02-10 00:01:40 - Timetracker] Installing Timetracker.apk...
[2011-02-10 00:04:11 - Timetracker] Failed to install Timetracker.apk on device 'emulator-5554!
[2011-02-10 00:04:11 - Timetracker] (null)
[2011-02-10 00:04:11 - Timetracker] Launch canceled!
i run the Timerproject but another timetrack project is only running the same timetracker project also doest responding

just close the already running emulator and start a new emulator more over if that doesn't works too close the eclipse too

If you're running Eclipse, and you've started the app from within (using Run As->Android App), then it should reuse the existing AVD. If it can't find it, then it will try to start another emulator and fail with the error you're seeing. Check the system Path environment variable and make sure it's including the SDK directory. If it doesn't then you'll see this error (I had the same problem; turned out I misspelled Program Files as Program Fiiles).
Hope this helps.

Open command prompt browse your adb path like
cd C:\Program Files\Android\android-sdk\platform-tools
type the command
adb kill-server && adb start-server
this will resolve your problem