Develop Reference

android emulator doesn't display my first 'standard' helloWorld app

The standard new app HelloWorld doesn't run as it in the Android emulator.
On Apple Mac, I created an AVD : Nexus7-4.3-JellyBean ( Android 4.3 API 18 , CPU/ABI ARM(armabi-v7a) RAM 343 VM Heap 32 / Storage 200 MiB / SD Card 128 MiB)
then running HelloWorld from Eclipse ADT , I get the following in the console log ( no error stated ...)
[2013-12-07 16:11:22 - HelloWorld] ------------------------------
[2013-12-07 16:11:22 - HelloWorld] Android Launch!
[2013-12-07 16:11:22 - HelloWorld] adb is running normally.
[2013-12-07 16:11:22 - HelloWorld] Performing com.example.helloworld.MainActivity activity launch
[2013-12-07 16:11:22 - HelloWorld] Automatic Target Mode: launching new emulator with compatible AVD 'Nexus7-4.3-JellyBean'
[2013-12-07 16:11:22 - HelloWorld] Launching a new emulator with Virtual Device 'Nexus7-4.3-JellyBean'
The emulator is launched, it displays the Android log, then unlocking it with Fn F2 I get the home page and I can see the list of apps BUT HelloWorld is not there.
Why can't I see any information or at least any error?

Try resetting your adb as explained in

The Console log is not complete yet, after starting the emulator, apk installing will start then launching,
Try to manually start the emulator then run your app and choose the already running emulator and see what happen.
- I wanted to post this as a comment but it takes 50 reputation to do so :)

Android Emulator on Eclipse Not Working

I've been following the instructions found at http://developer.android.com/training/basics/firstapp/running-app.html to run the Hello World app on Eclipse's AVD, but the AVD does not launch and I get the following messages:
[2013-01-20 00:20:59 - MyFirstApp] ------------------------------
[2013-01-20 00:20:59 - MyFirstApp] Android Launch!
[2013-01-20 00:20:59 - MyFirstApp] adb is running normally.
[2013-01-20 00:20:59 - MyFirstApp] Performing com.example.myfirstapp.MainActivity activity launch
[2013-01-20 00:21:00 - MyFirstApp] Automatic Target Mode: launching new emulator with compatible AVD 'TestAVD'
[2013-01-20 00:21:00 - MyFirstApp] Launching a new emulator with Virtual Device 'TestAVD'
[2013-01-20 00:21:48 - Emulator] Failed to create Context 0x3005
[2013-01-20 00:21:48 - Emulator] emulator: WARNING: Could not initialize OpenglES emulation, using software renderer.
[2013-01-20 00:21:48 - Emulator] Failed to allocate memory: 8
[2013-01-20 00:21:48 - Emulator]
[2013-01-20 00:21:48 - Emulator] This application has requested the Runtime to terminate it in an unusual way.
[2013-01-20 00:21:48 - Emulator] Please contact the application's support team for more information.
Also, an error window popped up saying that the ARM emulator exe has stopped working. Any thoughts?

OP of this thread has similar error message,
emulator: WARNING: Could not initialize OpenglES emulation, using software renderer
Hope it helps!

Check 2 things:
That you are using 512MB of RAM (the emulator doesn't work properly
with more)
Try turning 'Host GPU' off

Try running emulator from the command line with GPU option and make sure that it is working or not.
-gpu off
Even if it result into the error, go to the eclipse, Right Click on the project and select run my projects as an "Android application". Emulator should start.
You can also give a try with enabling/disabling GPU emulation option for the selected emulator from the AVD manager.
To enable/disable GPU emulation :
Goto AVD manager -> select android virtual device -> click on Edit ->
Hardware tab -> enable/disable GPU emulation.
Hope it will work.

I got this error when trying to run an emulator with a higher resolution than I had my display set to.

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!! :)

Could not start virtual device from eclipse

when I configured my Eclipse with ADT and SDK, I created a new android project, and then I right click the project name and select the Run As -> Android Application, but I got the error message in the console like this:
[2011-07-25 19:11:01 - Android] ------------------------------
[2011-07-25 19:11:01 - Android] Android Launch!
[2011-07-25 19:11:01 - Android] adb is running normally.
[2011-07-25 19:11:01 - Android] Performing com.android.Activity01 activity launch
[2011-07-25 19:11:01 - Android] Automatic Target Mode: launching new emulator with compatible AVD '2.1'
[2011-07-25 19:11:01 - Android] Launching a new emulator with Virtual Device '2.1'
[2011-07-25 19:11:01 - Emulator] invalid command-line parameter: by.
[2011-07-25 19:11:01 - Emulator] Hint: use '#foo' to launch a virtual device named 'foo'.
[2011-07-25 19:11:01 - Emulator] please use -help for more information
so, how can I fix this problem?

I had the same problem. I have Win 7 64b
I do 3 things.
Uninstall Android SDK from c://Program Files (x86)\ bla bla lba
Install Android SDK to c://Android/Sdk/blablaba
Reset the Eclipse path to SDK in Windows/Preference -> Andriod ->
Browse Folder for SDK...
All things start to work. I guess that critical for SDK is to be installed in the folder with spaces in the Folder name.

Hello Android works on my phone but not on Emulator

I am trying to learn about Android development. I have installed Eclipse (3.6.2) the ADT plugin (10.0.1) and the Android SDK (r11 off the official site) all are installed as 32 bit but my OS is Windows 7 64-bit.
What happens is I run my app (HelloAndroid) and the emulator and I see the main wallpaper screen but then then nothing happens! I have looked on the emulator for the app and cannot find it anywhere.
My console output is shown below...
[2011-05-20 19:14:20 - HelloAndroid] ------------------------------
[2011-05-20 19:14:20 - HelloAndroid] Android Launch!
[2011-05-20 19:14:20 - HelloAndroid] adb is running normally.
[2011-05-20 19:14:20 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch
[2011-05-20 19:14:20 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'Android2.1'
[2011-05-20 19:14:20 - HelloAndroid] Launching a new emulator with Virtual Device 'Android2.1'
My AVD (Android Virtual Device) is set up as the tutorial suggests and the target is Android2.1-update1-API Level 7.
I have installed this app on my phone (HTC Hero, Android 2.1) and it works fine, but before I try and write other applications I need to get the emulator working, has anyone encountered this issue before?
I have looked online and cannot find a solution that solves my problem.
Thanks for your help in advance.

You can use adb to install your app. Find the bin directory in your eclipse workspace. There should be a YOUR_PROJECT_NAME.apk file there. To install it, from the command line, run:
adb install -r YOUR_PROJECT_NAME.apk
You will need adb in your path.

Start the emulator, switch to the logcat view in Eclipse (Window -> show view -> other ... -> logcat).
Clear the console output for logcat.
Try to deploy your application.
What does the output in logcat say? Does it display an error message?