Develop Reference

Android Studio - emulators will not run anymore on windows! Why?

For a while I was able to run my app in the android emulator that was installed with Android Studio.
I have since updated SDKs and installed some x86 emulators with SDK manager and now none of the emulators will run properly no matter what I do..
They won't run if I select the run button in android Studio and they won't run if I select the run button I AVD manager.
If I view windows task manager I can see the emulator starting up but they just crash before the emulator window appears.
So what do I do here? Uninstall bloody Android Studio and start over???? Because nothing else that I have googled on this problem works.
All the solutions others have proposed appear to be very vague and a result of random trial and error rather than inside knowledge.
I have tried deleting my emulators and creating new ones.
I have tried wiping data in AVD manager.
I have tried changing the SDK versions in the emulators.
I have tried switching between ARM and X86 system images.
I have tried switching between 'Software GLES' and 'Automatic'
None of them fixes the problem.
The emulators start up in task manager but crash before anything becomes visible while android studio waits in vane for the device to start up.

Android emulator crashing on Mac

When I try to launch Android emulator, it crashes on Mac OS X. It was working some time ago, but now it isn't and I don't have an idea why.
Crash log: http://pastebin.com/04MjCqaS
Terminal log in verbose mode: http://pastebin.com/L6y6rUr0

Same issue here, I'm running a mac mini with 8GB of RAM and MacOS Lion. It used to work with the old AVD with some random crashes every now and then but since the last update to APi 17 it's a pain in the neck.
The ADT bundle doesn't work at all. After tweaking the memory limits on eclipse.ini file it throws random memory errors. Also it's not been able to download and install the m2e (maven to eclipse) plugin.
I moved to IntelliJ and I'm able to launch AVD manager but none of the "old" created devices work. If I create a new one and I launch it it works until I close it, then I have to restart the Mac and create a new device. Also it randomly shows errors when I want to delete those old created virtual devices.
Also the DDMS fails to start. I launch it, shows its icon on the Dock but it doesn't respond until I force close.
What a Nightmare.
** EDIT **
I found at android dev bug tracker this issue when you're running 2 screens: here
This is happening to me with the android emulator. I solved it like this:
cd ~/.android/avd
ls *.avd
Now choose the emulator that is crashing and
cd name_of_the_emulator.avd
touch emulator-user.ini
vi emulator-user.ini
And now reset window.x, that's window.x=0
exit and run the emulator.
If you move and close the emulator to the secondary screen it will crash the next time you want to run it.

Kill your Docker process
One problem I have seen multiple time is with Docker. Android Emulator crashes when Docker is running on Mac.

I was following the PhoneGap "Getting Started" guide for Android, and when I got to "Deploy to Emulator," after I created a new AVD, my Mac would crash and reboot. I stumbled on this thread, but thought it worth mentioning that what actually solved the problem for me was an Intel patch for the Hardware Accelerated Execution Manager located here: http://software.intel.com/en-us/articles/intel-hardware-accelerated-execution-manager

This is because Android SDK use some deprecated libraries of Mac OS X. I have the same problem (sometimes even kernel panic) before I start use android device. Maybe in future versions of Android SDK this problem will be fixed.

I just updated the Android SDK manager to the latest Android 4.2 (API 17) level updates, and now all my old AVD's crash. The newly created one using API 17 works, however.

I have the same issue. You can try to create a new AVD with the appropriate API level. I am able to run these the first time(s) after creating. That seems to be a memory error.
My AVDs are able to run the first time after reboot. After this they keeps crashing.

I had the same issue using mac 10.6 and 2 monitors one through a usb adapter to HDMI.
I have tried all of this suggestions and nothing did work.
I ended up creating a new user into my mac and with the same android sdk and same eclipse with a new workspace did work.
I'm not sure whether just creating a new workspace would do the tweak, I didn't try it.
for those who come across to this annoy issue worth to try it before switch to a new account.

You can delete your emulators from ~/.android/avd
Then create new emulators.

Android Emulator won't launch, no console output or errors

I am trying to run the Android emulator on a 64 bit Windows 7 machine. I have installed the Android SDK, JDK, Eclipse, and the Android plugins for Eclipse. From the SDK Manager, I have installed the Android SDK Tools, as well as all of the files for Android 4.1 (API 16).
From Eclipse, when I want to open the emulator I select the AVD Manager and click on a device that I have created. The AVD Manager says that the virtual device is a valid device. When I launch the machine, a box pops up that says "Starting Android Emulator," and there is a loading bar right below it. The bar will get to about 95%, and then the box will disappear and nothing will happen. There will be no errors and no messages in the console output box in Eclipse. I get similar behavior when I try to launch the emulator by running an app from Eclipse.
I have tried uninstalling and reinstalling the SDK to a new directory, as well as downloading a different version of Eclipse (I am currently using Eclipse Java EE, earlier I was using Eclipse Classic 4.2). I also tried downloading the API 15 platform and using that as a virtual device, and I still have the same issues.
I have checked my task manager, and the only new process that is ever created is adb.exe, and this only happens when I try to run my app, but not when I start the emulator on its own.
Any idea what might be causing this, or what methods I might use to troubleshoot this that will actually give me some kind of error message, rather than just disappearing and not doing anything? Thanks.
Edit: When I try to run the emulator from the AVD Manager directly, I get the same behavior as when running through Eclipse (loading box pops up, then disappears, then nothing).

Try to use BlueStacks emulator instead standart. It work much more faster and reliably. You can download it from http://bluestacks.com. After installing reboot the system. I think all be fine.

I had the same problem. Enabling Host GPU emulation worked for me.

Android SDK 2 emulator works but 3 doesn't

I have read this thread Android emulator refuses to boot
and tried to apply the solutions, none did work for emulator 3. I even tried to add my d:\androidsk folder to path and android_sdk_home environment variables, it doesn't solve the problem: it just shows _android on the black screen for hours.
I have installed reinstalled multiple times also already.
What else could I do ?
I got the last version tools from today google sdk site.
Update: I have started several times, I got it work once but with error message "Activity launcher forced to close", I have to click wait multiple times to see android desktop.
When I close the VM and tries again with the same I cannot make it work again.
This I tried on 2 machines:
Netbook eeePC 1215B (AMD c60 if I remember well) and Windows Tablet EP21 (intel core i5)
Why on earth do some people downvote this question ? I'm not the only one who got that problem, are they ashame that Android sdk is so buggy ?

Android Emulator doesn't work as expected

I'm new to Android Development and am currently trying to develop my first application
I started with the tuturial available here: Tutorial
I just setup the complete environment for android development:
OS: Windows 7 x64, CPU: 3 GHZ AMD Phenom II X4, RAM: 8GB.
IDE: Eclipse IDE for Java Developers (Version: Indigo Service Release 1)
I downloaded the SDK from here http://developer.android.com/sdk/index.html
Then i followed the instructions from the tutorial.
However my problem is: When I run the application as an Android Application the emulator gets started, but then get stuck at the following screen:
Even after waiting for more than 30 minutes or even 1 hour it displays still the same screen.
There was only one "problem" while installing the Java JDK:
- For the JRE was already a newer version installed. (Installed: "Java(TM) 7 Update 2 (64-bit)" I however downloaded the latest sdk from the oracle site. I don't know if the runtime und the sdk must have the same version...
In addition I was yesterday once I able to start the emulator and as long as I let it run it worked quite well... I could even debug the application... However, if I now tried to start the device from eclipse it crashed instantly. Same thing if I start it from de AVD Manager directly ("From Snapshot" or with "Wipe User Data" doesn't matter...). So I deleted the device and created a new one with the same options. Now however I am again stuck at the screen above.
I have no idea of how the whole emulator works. In addition there is A LOT of information in the internet available about crashes and so on (lots of them for earlier releases of the AVD, however I havn't found anything that helped my out.
It would be quite useful to know how the emulator usually works. And maybe getting a hint, what I could do to.
Thanks in advance...

I had a similar issue when updating from the JDK 6 to 7, and solved it by going back to the JDK 6. I still cannot use the JDK 7 for a mysterious reason.