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.

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

Problems launching a virtual machine using the android avd manager [duplicate]

I have installed and set up Eclipse and the plugin ADT in order to work with Android SDK. So far so good. But when I try to launch a VM(virtual Machine) for any android platform that I choose (for example: android 3.2) I just get the skin launched together with a keyboard console and phone buttons, it seems to boot up to a state and then does nothing but displays the android logo on the main vm screen and that's all it does - no more!, no VM functionality!, what's going on? Have I missed out some step? Please help...
Have been waiting sometimes over 10 mins in each case for the emulator to start.
I launched/ran an Android project test sample; 'hello world' from the eclipse environment after installing the ADT plugin for Android These are the error messages I had displayed in the console ddms:
[2012-04-30 14:31:20 - HelloAndroid]
[2012-04-30 14:31:20 - HelloAndroid] Android Launch!
[2012-04-30 14:31:20 - HelloAndroid] adb is running normally.
[2012-04-30 14:31:20
- HelloAndroid] Performing com.example.helloandroid.HelloAndroidActivity activity launch
[2012-04-30 14:31:20 - HelloAndroid] Automatic Target Mode: launching
new emulator with compatible AVD
'leighs_basic_hardware_secound_virtual_device'
[2012-04-30 14:31:20 -
HelloAndroid] Launching a new emulator with Virtual Device
'leighs_basic_hardware_secound_virtual_device'
[2012-04-30 14:31:40 -
Emulator] Warning: No DNS servers found
[2012-04-30 14:31:52 -
Emulator] emulator: emulator window was out of view and was recentered
[2012-04-30 14:31:52 - Emulator]
[2012-04-30 14:31:53 - HelloAndroid]
New emulator found: emulator-5554
[2012-04-30 14:31:53 - HelloAndroid]
Waiting for HOME ('android.process.acore') to be launched...
[2012-04-30 14:49:03 - HelloAndroid] HOME is up on device
'emulator-5554' [2012-04-30 14:49:03 - HelloAndroid] Uploading
HelloAndroid.apk onto device 'emulator-5554'
[2012-04-30 14:49:03 -
HelloAndroid] Installing HelloAndroid.apk...
[2012-04-30 14:51:38 -
HelloAndroid] Failed to install HelloAndroid.apk on device
'emulator-5554!
[2012-04-30 14:51:38 - HelloAndroid] (null)
[2012-04-30 14:51:39 - HelloAndroid] Launch canceled!
At no point have I have anything but the Android logo displayed on my emulator. I have tried various platform emulators - none of them are performing!
A second lot of errors I received back on a test run after I checked the user data wiped in the Run configuration menu was: result
: [2012-04-30 17:20:27 - Emulator] Failed to allocate memory: 1455
[2012-04-30 17:20:27 - Emulator]
[2012-04-30 17:20:27 - Emulator] This
application has requested the Runtime to terminate it in an unusual
way.
[2012-04-30 17:20:27 - Emulator] Please contact the application's
support team for more information.
Bench mark results of my computer using Novabench incase anyone wants to check, are:
30/04/2012 17:45:59 Microsoft Windows 7 Starter Intel Atom N550
1.50GHz # 1500 MHz Graphics Card: Intel(R) Graphics Media Accelerator 3150
1014 MB System RAM (Score: 78) - RAM Speed: 1610 MB/s
CPU Tests (Score: 70) - Floating Point Operations/Second: 24110532 -
Integer Operations/Second: 43813828 - MD5 Hashes Generated/Second:
159380
Graphics Tests (Score: 1) - 3D Frames Per Second: 3
Hardware Tests (Score: 6) - Primary Partition Capacity: 87 GB - Drive
Write Speed: 14 MB/s

Do you Run your project or only start an emulator? After starting emulator, click Run button and select "Run as Android project".

I am not sure how long you waited, but starting the emulator the first time (before you have a snapshot) can take quite a long time. Depending on you hardware it can take more than 10 minutes to launch.

I had a similar issue which was solved by creating a new emulator and running it. You can check progress in Devices view through DDMS. Sometimes, this problem may occur when a snapshot enabled emulator hangs because of error, which can be solved by starting the emulator with user data wiped.

Emulator thread automatically cuts off if for some time you have not done any activity on it..
so.. keep running your app to keep emulator on LIVE!
My advice - if you having an android phone.. please usb debug it and Debug your application on your phone... You will feel relieved from the long durations of the emulator........ to run!! :)

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.

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.