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.

AVD showing only "Android" in emulator

Android Launch!
[2013-06-17 15:38:53 - Numberconverter] adb is running normally.
[2013-06-17 15:38:53 - Numberconverter] Performing com.example.channu.Numbersystem activity launch
[2013-06-17 15:39:00 - Numberconverter] Launching a new emulator with Virtual Device 'AMMA'
[2013-06-17 15:39:05 - Numberconverter] New emulator found: emulator-5554
[2013-06-17 15:39:05 - Numberconverter] Waiting for HOME ('android.process.acore') to be launched...

Nothing is wrong.
Waiting for HOME ('android.process.acore') to be launched...
Means that it is actually waiting for the OS to be loaded on the emulator. This usually takes a few minutes depending upon the configuration of the system you are using.
Just wait for a few minutes and you would be able to see the usual Android OS loaded on the emulator.
The usual console output when you launch an app on a new emulator is something like:
[2013-06-17 16:06:52 - FirstRun] New emulator found: emulator-5554
[2013-06-17 16:06:52 - FirstRun] Waiting for HOME ('android.process.acore') to be launched...
[2013-06-17 16:08:00 - FirstRun] HOME is up on device 'emulator-5554'
[2013-06-17 16:08:00 - FirstRun] Uploading FirstRun.apk onto device 'emulator-5554'
[2013-06-17 16:08:01 - FirstRun] Installing FirstRun.apk...
[2013-06-17 16:08:30 - FirstRun] Success!
[2013-06-17 16:08:30 - FirstRun] Starting activity dev.swm.firstrun.MainActivity on device emulator-5554
[2013-06-17 16:08:32 - FirstRun] ActivityManager: Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=dev.swm.firstrun/.MainActivity }

you can, wait for few seconds and then right click on the project and click run as Android application once again.
also, The only thing that works for me is the combination of three other good answers:
1- Project -> Clean
2- Delete all the AVDs and create new ones
3- If an attempt to run still hangs too long on 'Waiting for HOME' (over two minutes) or the emulator keeps rebooting every minute or so, try Run as Android App several times, choosing the same existing emulator instance (I always choose runs manually).
It's odd that no one has a clue why this problem comes up, what causes it or what is going on internally. The only clue I can supply is that DDMS shows a few lines like "Class not found for preloading: libcore.base.CollectionUtils" during the 'Waiting for HOME' pause.
if not try doing that and see if you can start & see if everything
works.
1) try using Emulator command
2) in Eclipse, Window->Adnroid SDK & AVD manager ->Virtual Devices,
then select the AVD, press Start button

After you see the starting as shown above by swayam's answer in Eclipse "Console", "charging" screen appears, but then I pressed the "Menu" button on the right side and my program displayed and functions correctly. Just a newbie trying to help.

It's a memory Problem. Increase the ammount of RAM, I had the same problem and increasing the RAM worked.
Best of luck

I set higher ram 756MB and then clicked on use host GPU and it did work after that. Win8 and used Nexus5 emulator API 19.

Create new Avd of the same Api you using and try it will work

I used to have the same problem and managed to solve it by disabling Hyper-V (provided that you are running a Windows machine).
To do that, go to Control Panel -> Add/Remove Programs -> Turn Windows Features on or off -> Uncheck Hyper-V
There is one thing though: the Hyper-V feature is not available in Home versions of Windows. Also disabling it prevents you from using Windows Phone emulators, so keep that in mind.

Had the same problem. Even the side buttons were not appearing. I increased the ram from 512 to 750mb, and it worked like a charm.

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

Cannot run Android apps with eclipse on OS X 10.6

Running Eclipse 3.5.2 (Classic) in OS X 10.6.7 with the ADT plugin. I have the SDK installed and have run the SDK and AVD Manager to install all available platforms and tools. I have an AVD setup with Android 2.2 as the target API, and have configured the example 'Hello, Android' app for Android 2.1 Update 1, so compatibility should not be an issue. When I Run the application, it starts up the emulator, but gives me an error before the android startup animation appears. Here is the output in the Console window of Eclipse:
[2011-04-10 06:45:40 - HelloAndroid] ------------------------------
[2011-04-10 06:45:40 - HelloAndroid] Android Launch!
[2011-04-10 06:45:40 - HelloAndroid] adb is running normally.
[2011-04-10 06:45:40 - HelloAndroid] Performing com.twopoint7.testing.HelloAndroid activity launch
[2011-04-10 06:45:40 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'testDroid'
[2011-04-10 06:45:40 - HelloAndroid] Launching a new emulator with Virtual Device 'testDroid'
[2011-04-10 06:46:04 - Emulator] 2011-04-10 06:46:04.613 emulator[997: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-04-10 06:46:04 - HelloAndroid] New emulator found: emulator-5554
[2011-04-10 06:46:04 - HelloAndroid] Waiting for HOME ('android.process.acore') to be launched...
[2011-04-10 06:47:22 - HelloAndroid] emulator-5554 disconnected! Cancelling 'com.twopoint7.testing.HelloAndroid activity launch'!
Any advice on what might be going wrong would be greatly appreciated. I've found lots of posts (here and on other forums) that seem to indicate the NSQuickDrawView vs. Quartz warning seems to be a problem across the board but doesn't have a solution yet. I'm more concerned with the "emulator-5554 disconnected..." bit and the fact that I can't seem to run any apps in the emulator. Any other info I can provide which would be helpful? Any insight?
Thanks in advance for your time!

I guess you need to reset your adb after launch the emulator. In eclipse, go to window -> show view -> other -> device(under android folder).
In the device view, find and reset adb. Then run your apps.