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
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'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.
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
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!! :)
[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