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!! :)
Related
So everything was working fine, today I opened android studio and try to run the emulator, and it wont start. I will provide the errors in an image bellow.
I tried wiping the emulators data , and disabled the antivirus, I tried new device...
Please help I need it :(
ERRORS OF EMULATOR PICTURE
11:45 AM Gradle sync started
11:45 AM Gradle sync finished in 2 s 250 ms (from cached state)
11:46 AM Executing tasks: [clean, :app:assembleDebug] in project D:\AndroidStudioProjects\AudioVideo
11:47 AM Gradle build finished in 47 s 998 ms
11:47 AM Executing tasks: [:app:assembleDebug] in project D:\AndroidStudioProjects\AudioVideo
11:47 AM Gradle build finished in 20 s 141 ms
11:48 AM Emulator: emulator: WARNING: EmulatorService.cpp:448: Cannot find certfile: C:\Users\User.android\emulator-grpc.cer security will be disabled.
11:48 AM Emulator: Started GRPC server at 127.0.0.1:8554
11:48 AM Emulator: C:\Users\User\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe: error while loading state for instance 0x0 of device 'goldfish_pipe'
11:48 AM Emulator: deleteSnapshot: for default_boot
11:48 AM Emulator: Process finished with exit code 0
11:49 AM Executing tasks: [:app:assembleDebug] in project D:\AndroidStudioProjects\AudioVideo
11:49 AM Gradle build finished in 5 s 906 ms
Possible solutions
Invalidate/Restart Android studio
Open AVD Manager select you emulator and wipe Data from the dropdown
Installing Intel latest Intel HAXM
or delete current emulator and install new one
I want to say, that any possible solution did not work for me, I lost 4 hours working on that. I quit and installed Genymotion , I can tell that it runned smoother than the android emulator.
When I run my codes, the android ADB detect the emulator as offline, although I have turned on the emulator. I am using AMD processor. I'm running armebiv7 device image.
Here's the error that I get.
emulator: WARNING: Crash service did not start
emulator: WARNING: Classic qemu does not support SMP. The hw.cpu.ncore > option from your config file is ignored.
emulator: Listening for console connections on port: 5554
emulator: Serial number of this emulator (for ADB): emulator-5554
emulator: WARNING: UpdateCheck: Failure: Error
Thanks!
Please help I am getting the following error While launching AVD
Cannot launch AVD in emulator.
Output:
emulator: WARNING: VM heap size set below hardware specified minimum of 256MB
Warning: requested ram_size 1536M too big, reduced to 512M
emulator: WARNING: Setting VM heap size to 384MB
WARNING: unable to configure any DNS servers, name resolution will not work
Hax is enabled
Hax ram_size 0x20000000
HAX is working and emulator runs in fast virt mode.
console on port 5554, ADB on port 5555
emulator: emulator window was out of view and was recentered
emulator: WARNING: UpdateCheck: Failure: Error
emulator: WARNING: UpdateCheck: failed to get the latest version, skipping check (current version '25.1.7'
Cannot launch AVD in emulator.
Output:
emulator: WARNING: VM heap size set below hardware specified minimum of 256MB
Warning: requested ram_size 1536M too big, reduced to 512M
emulator: WARNING: Setting VM heap size to 384MB
WARNING: unable to configure any DNS servers, name resolution will not work
Hax is enabled
Hax ram_size 0x20000000
HAX is working and emulator runs in fast virt mode.
console on port 5554, ADB on port 5555
emulator: emulator window was out of view and was recentered
emulator: WARNING: UpdateCheck: Failure: Error
emulator: WARNING: UpdateCheck: failed to get the latest version, skipping check (current version '25.1.7'
screenshot of error
How much RAM did you configure HAXM for when it installed? If you installed HAXM to use 512M, then your AVD isn't going to be able to use more than that.
I'd try installing it again: https://software.intel.com/en-us/android/articles/installation-instructions-for-intel-hardware-accelerated-execution-manager-mac-os-x
I am having issues opening Eclipse on my Mac. There is no loading screen, it just crashes instantly after it is booted. Is anyone able to trace the path? This is my first time using Eclipse, so I am not very experienced.
The basic crash log (Shortened):
Process: eclipse [1371]
Path: /Users/USER/Desktop/Eclipse.app/Contents/MacOS/eclipse
Identifier: org.eclipse.platform.ide
Version: 4.4.2 (4.4.2.M20150204-1700)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: eclipse [1371]
User ID: 501
Date/Time: 2015-06-12 19:00:02.778 +0100
OS Version: Mac OS X 10.10.3 (14D136)
Report Version: 11
Anonymous UUID: *********************
Time Awake Since Boot: 9700 seconds
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000000000003c
The full log can be found here.
Any help is appreciated. Have a great day folks. :)
There are several solutions for you. You could dual boot windows and install Eclipse and then see if it works. Or you could try other IDEs for example if you are using Eclipse to develop android apps then you could try Android Studio. Or if you are doing java applications then you could try Intellij IDEA.
i followed all the instructions in the tutorials, but from some reason i can't create the emulator....
what eclipsed showed me after trying to run:
[2013-09-06 12:24:30 - The New Boston] ------------------------------
[2013-09-06 12:24:30 - The New Boston] Android Launch!
[2013-09-06 12:24:30 - The New Boston] adb is running normally.
[2013-09-06 12:24:30 - The New Boston] Performing com.TheNewBoston.travis.StartingPoint activity launch
[2013-09-06 12:24:30 - The New Boston] Automatic Target Mode: launching new emulator with compatible AVD 'droidX'
[2013-09-06 12:24:30 - The New Boston] Launching a new emulator with Virtual Device 'droidX'
[2013-09-06 12:24:33 - Emulator] Failed to allocate memory: 8
[2013-09-06 12:24:33 - Emulator]
[2013-09-06 12:24:33 - Emulator] This application has requested the Runtime to terminate it in an unusual way.
[2013-09-06 12:24:33 - Emulator] Please contact the application's support team for more information.
In IDE menu click on windows option. Go in android virtual device manager. If you created any emulator click on that emulator. then edit and in memory options. change RAM size to 256, 512 or 1024. Hope its work.