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.
Related
So today, until now my avd device launched and it didn't have any problem at all. I were updating through Android SDK Manager and launching an app on the same time but when avd device showed up after 1 minute I got an error message that Windows have to close the app.
My current AVD device is custom:
900x600 Android 4.3 - API Level 18 Intel Atom Memory Options: Ram:
760 VM Heap: 32 Internal Storage: 200 Mib Use Host Gpu (ticked)
When my app was closed I tryed to see if there is any problem at config.ini. And I changed
ORIGINAL: disk.dataPartition.size=200M
MODIFIED: disk.dataPartition.size=200MB
ORIGINAL: hw.ramSize=760
MODIFIED: hw.ramSize=760MB
and tryed to launch it again, but it didn't work and then I checked again from my device manager that RAM didn't have a value!!! Also I tryed to change the resolutionbut it didn't work.
So this is keep happening. Every time I save it and then fix config.ini but emulator stops.
I tryed to use different device from the list, but they didn't launch either.
This the message from my console also:
[2014-03-06 12:49:28 - ] Dx
trouble writing output: already prepared
[2014-03-06 12:49:32 - ] ------------------------------
[2014-03-06 12:49:32 - ] Android Launch!
[2014-03-06 12:49:32 - ] adb is running normally.
[2014-03-06 12:49:32 - ] Performing com.example. .MainActivity activity launch
[2014-03-06 12:49:32 - ] Automatic Target Mode: launching new emulator with compatible AVD 'AVDPanos'
[2014-03-06 12:49:32 - ] Launching a new emulator with Virtual Device 'AVDPanos'
[2014-03-06 12:49:37 - Emulator] emulator: Failed to open the HAX device!
[2014-03-06 12:49:37 - Emulator] HAX is not working and emulator runs in emulation mode
[2014-03-06 12:49:37 - Emulator]
[2014-03-06 12:49:37 - Emulator] emulator: Open HAX device failed
[2014-03-06 12:49:37 - Emulator]
[2014-03-06 12:49:38 - Emulator] creating window 0 0 900 600
[2014-03-06 12:49:38 - ] New emulator found: emulator-5554
[2014-03-06 12:49:38 - ] Waiting for HOME ('android.process.acore') to be launched...
[2014-03-06 12:49:59 - ] emulator-5554 disconnected! Cancelling 'com.example. .MainActivity activity launch'!
Any help?
attempts to decrease the ram 528 and uncheck the gpu
and read http://software.intel.com/en-us/android/articles/installation-instructions-for-intel-hardware-accelerated-execution-manager-windows
I also face with the same issue, pap. When I run the project on the emulator, and face with the same issue, I re-run the project (without closing/restarting anything viz. Emulator, Eclipse or the machine). Then it works fine. Try this scenario from your end as well. Hope it works for you as well.
I tryed to do what ViramV and Tomazini couple of times (thanks both for your help), but didn't work for me. So I had reinstall the whole package of eclipse from the beginning, because I couldn't find any other way to do it.
i have installed eclipse and android sdk manager, installed files for android 4.22 in sdk and tried to run a sample android project.. but am getting the following error
[2014-02-06 15:28:08 - myFirstApp] Android Launch!
[2014-02-06 15:28:08 - myFirstApp] adb is running normally.
[2014-02-06 15:28:08 - myFirstApp] Performing com.example.myfirstapp.MainActivity activity launch
[2014-02-06 15:28:08 - myFirstApp] Automatic Target Mode: launching new emulator with compatible AVD 'AVD_233'
[2014-02-06 15:28:08 - myFirstApp] Launching a new emulator with Virtual Device 'AVD_233'
[2014-02-06 15:28:17 - Emulator] Failed to allocate memory: 8
[2014-02-06 15:28:17 - Emulator]
[2014-02-06 15:28:17 - Emulator] This application has requested the Runtime to terminate it in an unusual way.
[2014-02-06 15:28:17 - Emulator] Please contact the application's support team for more information.
i tried the following..
1) accessed C:\Users\user\.android\avd\user.avd\config.ini and changed hw.ramSize=1024MB
2)accessed avd and edited memory optionfrom 1024mb s to 512mb
its still not working... thanks in advance..
Try setting your RAM to 512 MB. It Worked for me..
If it is not working for you, Try reducing your RAM and VM heap further.
First try your emulator with some LDPI models(2.7 inch)..
I am new to Android, and am just starting to work through the examples in "Learn Android App Development". When I try to "run as Android application", I get the following errors...
[2013-10-12 19:39:18 - Hello_World] ------------------------------
[2013-10-12 19:39:18 - Hello_World] Android Launch!
[2013-10-12 19:39:18 - Hello_World] adb is running normally.
[2013-10-12 19:39:18 - Hello_World] Performing chapter.two.hello_world.MainActivity activity launch
[2013-10-12 19:39:19 - Hello_World] Automatic Target Mode: launching new emulator with compatible AVD 'Android_4.2_Emulator_Nexus_7'
[2013-10-12 19:39:19 - Hello_World] Launching a new emulator with Virtual Device 'Android_4.2_Emulator_Nexus_7'
[2013-10-12 19:39:27 - Emulator] extension WGL_ARB_make_current_read was not found
[2013-10-12 19:39:27 - Emulator] extension WGL_EXT_swap_control was not found
[2013-10-12 19:39:27 - Emulator] Failed to create pbuf surface for FB 0x3004
[2013-10-12 19:39:27 - Emulator] emulator: WARNING: Could not initialize OpenglES emulation, using software renderer.
[2013-10-12 19:39:29 - Emulator] emulator: warning: opening audio output failed
[2013-10-12 19:39:29 - Emulator]
[2013-10-12 19:39:33 - Emulator] emulator: emulator window was out of view and was recentered
[2013-10-12 19:39:33 - Emulator]
[2013-10-12 19:39:33 - Hello_World] New emulator found: emulator-5554
[2013-10-12 19:39:33 - Hello_World] Waiting for HOME ('android.process.acore') to be launched...
[2013-10-12 19:40:57 - Hello_World] emulator-5554 disconnected! Cancelling 'chapter.two.hello_world.MainActivity activity launch'!
The two lines with "not found" at the end, and the very last line are actually in red ink.
Being brand new to Android development, I am not sure where the error is actually coming from. Is it related to the fact that I am doing this on a Windows 7 x64 VMware VM, is it related to the host system (also a Windows 7 x64 system), is it related to the graphics card and its software, OpenGL, position of Mars in relationship to Venus, screen resolution, etc.??? My hardware is a HP pavilion AMD three Core processor.
This is my first game and i choosed AndEngine library. My avd configuration have its target as Android 4.2.2 API Level 17 and GPU emulation enabled. Yet I am getting the following error in my console
[2013-08-29 22:05:13 - AndEngine1] Android Launch!
[2013-08-29 22:05:13 - AndEngine1] adb is running normally.
[2013-08-29 22:05:14 - AndEngine1] Performing com.example.andengine1.MainActivity activity launch
[2013-08-29 22:05:25 - AndEngine1] Launching a new emulator with Virtual Device 'small2'
[2013-08-29 22:06:52 - Emulator] creating window 0 0 240 432
[2013-08-29 22:06:53 - AndEngine1] New emulator found: emulator-5554
[2013-08-29 22:06:53 - AndEngine1] Waiting for HOME ('android.process.acore') to be launched...
[2013-08-29 22:08:11 - AndEngine1] emulator-5554 disconnected! Cancelling 'com.example.andengine1.MainActivity activity launch'!
[2013-08-29 22:09:02 - Emulator] sdk/emulator/opengl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glGetUniformLocation:1380 error 0x501
[2013-08-29 22:09:04 - Emulator] sdk/emulator/opengl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glGetUniformLocation:1380 error 0x501
[2013-08-29 22:09:04 - Emulator] sdk/emulator/opengl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glUseProgram:1911 error 0x501
[2013-08-29 22:09:04 - Emulator] sdk/emulator/opengl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glGetUniformLocation:1380 error 0x501
[2013-08-29 22:09:12 - Emulator] sdk/emulator/opengl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glUseProgram:1911 error 0x501
[2013-08-29 22:09:15 - Emulator] sdk/emulator/opengl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glUseProgram:1911 error 0x501
and so on
Pls help me regarding this to fix the issue.
Thanks in advance.
You need to install 'intel X86' in the extras section in the SDK Manager .
After installing 'intel X86' also if your system is showing problem such as "HXA not installed " , that means you have to check whether your system supports virtualization .
Suppose your system doesnt support virtualization , then you can't run your game on emulator .
Emulator requires virtualization enabled in the system .
If your system doesn't support virtualization , then
You should run using real smart phone which has android OS in it to test your game.
stems
If your system supports virtualization , then you have to enable virtualization to run your game on emulator .
Virtualization(VT) is a hardware related thing. Some sy
I need a new emulator in my android, I created this:
but when launched, it doesnt work:
[2013-01-14 09:36:31 - 3CBike] ------------------------------
[2013-01-14 09:36:31 - 3CBike] Android Launch!
[2013-01-14 09:36:31 - 3CBike] adb is running normally.
[2013-01-14 09:36:31 - 3CBike] Performing com.usualbike.cbike.SplashScreen activity launch
[2013-01-14 09:36:31 - 3CBike] Automatic Target Mode: Preferred AVD 'android4' is not available. Launching new emulator.
[2013-01-14 09:36:31 - 3CBike] Launching a new emulator with Virtual Device 'android4'
[2013-01-14 09:36:34 - Emulator] emulator: warning: opening audio input failed
[2013-01-14 09:36:34 - Emulator]
[2013-01-14 09:36:34 - Emulator] emulator: emulator window was out of view and was recentered
[2013-01-14 09:36:34 - Emulator]
[2013-01-14 09:36:34 - 3CBike] New emulator found: emulator-5554
[2013-01-14 09:36:34 - 3CBike] Waiting for HOME ('android.process.acore') to be launched...
it is open but now are 09:59 and only this is shown
Do I have some mistake in the configuration?
Here are a few things you can try since you've said your computer has a good enough configuration:
Try changing some of the AVD's values, by adding more ram, increase
SD card. (Window > Android SDK and AVD Manager > Edit the AVD)
Try checking the "Snapshot" option when editing the AVD, it will save
the last state and load that instead of a full boot.
Try mixing and matching.
The emulator takes ages to start on my laptop (not very good spec, but once it starts, it will run fine as long as I don't close it)
If none of the options above help you, you can try using virtual box as describe here. I haven't tried it myself, but seen it running, and it does boot up really quickly, and give you the same sort of functionality