Develop Reference

android studio emulator won't start/show up

I'm new to Android/Kotlin programming (not to programming in general) and I'm following the Kotlin Basics course on developer.android.com.
The very first lesson after having installed Android Studio is to create a Virtual Device and run an extremely basic app on it.
However I can't get the emulator to work. The very first time I tried, it opened a small window with a progress bar but it became unresponsive at around 1/4 progress and I had to eventually kill it.
Since then it just won't start/open.
After I click run, the code compiles and the Event Log within Android Studio says Executing tasks[...] then Gradle build finished[...] and that's it. Nothing happens beyond that and the Emulator window says "No emulators are currently running".
However:
Some emulator-related processes have been started. Those processes stay alive even after closing Android Studio..
If I try to start the AVD from within the device manager, I get an error message that the device is already running
I am unable to delete these .lock files without killing the aforementioned processes
What I could find:
The Windows Event Viewer shows an Application Error
The Android Studio log file also shows an Error
I don't know what to do with either of these messages, though
What I tried
Killing the emulator processes, removing the *.lock files and trying again.
Creating a different AVD (different device, different version of Android)
Completely reinstalling Android Studio and the SDK following the accepted answer to this question: How to completely uninstall Android Studio from windows(v10)?.
None of this had any effect.
I'm running Android Studio Arctic Fox (2020.3.1 Patch 4) on Windows 10 Pro (10.0.19042 Build 19042).
I am able to run the app on my actual phone but down the line I would like to be able to test apps on different types of devices or without having to always use my physical one.
All help would be greatly appreciated.

By running and emulator.exe command in a command prompt, I was able to see yet another error message, the same one as in this post: emulator: incompatible HAX module version 3 requirs minimum version 4, and the answer to that post from user Harold Sota (as well as the comment under it from Harun, more specific to my situation) solved the issue.

VM Ubuntu: Android Emulator won't start from Eclipse

I have created a VM Ubuntu 14.04 using Vmware Player, and I've installed the ADT environment for Android Development.
I have created a new Android emulator using the shortcuts present in Eclipse; when I tried to start emulator I got the following known error:
Starting emulator for AVD 'AVD_for_Nexus_5_by_Google'
ERROR: 32-bit Linux Android emulator binaries are DEPRECATED, to use them
you will have to do at least one of the following:
- Use the '-force-32bit' option when invoking 'emulator'.
- Set ANDROID_EMULATOR_FORCE_32BIT to 'true' in your environment.
Either one will allow you to use the 32-bit binaries, but please be
aware that these will disappear in a future Android SDK release.
Consider moving to a 64-bit Linux system before that happens.
I fixed it in both ways: putting a variable in my .bashrc:
export ANDROID_EMULATOR_FORCE_32BIT=true
and also setting the emulator option in the Eclipse preference dialog:
Nevertheless, every time I try to start the emulator I got always the same error.
The wierd thing is that if I try to start the emulator from a bash window, it starts normally.
This could have been a boring workaround, but I would have been happy anyway. The problem is that when I try to deploy an application from Eclipse, the emulator started in this way is shown as "Offline" and I cannot run any application on it. Possibly I can upload the apk into the emulator from the command line, but debugging the app would become a bit harder.
Has anyone got the same problem or does know how to fix it?

I found out a partial solution for connecting eclipse to the running emulator started by command line: the emulator MUST be started with no snapshots.
Indeed, if I start the emulator without snaspshots, it become "online" in DDMS, and I can finally use it.
Although this could be a bit annoying, because starting the emulator from scratch every time it takes a long time, at least I have a way to use it.
On the other hand, I don't know exactly the reason of this behavior, if someone has an answer it will be appreciated.
Moreover, I still do not have idea why I'm not able to start the emulator from Eclipse.

running android emulator from worklight

I wish to run an application on android virtual device (I've created it). I right-click on the
Android project (which was created after I added the android environment) and choose "Run as Android Application". The emulator launches but it remains just a black window (and I wait a lot, nothing happens). Console writes "Build successful" and that's it. What might be the problem? API level is 18 (4.3). Platform Windows 7. Thanks.
Details: created a project, added hybrid application, added adaptors, deployed and run multiple times (just in browser), installed android in eclipse, added android environment, added AVD (had some old ones that didn't work, deleted them and created a new one following advises here).

It sounds like the problem is with your Android emulator.
First, can you start the emulator by itself, and see it work properly? You can start it from AVD itself. The emulator usually takes a long time to start, especially if you are running the ARM emulator instead of the x86 one.
If that works, can you run an empty Android app? You can go to File - New Project - Android Application Project, and after you create it, you should be able to run it and see an empty application.
If that works, can you try with an empty Worklight application? That way we can see if it is your specific application or something to do with Worklight.

Android Device Window Chooser not working after updating device

I've always used my android phone for development but after installing the last software update on my device (4.2.2) it suddenly stopped working and would appear offline in eclipse's Device Window Chooser.
I'm not able to send applications to it for testing or access it with the adb-shell. I have developer options turned on and debugging mode enabled. I'm using Eclipse Helios on Ubuntu linux.
When I launch Eclipse the following window will show up
and after clicking on the check for updates I get the following error:
Unable to read repository at jar:file:/home/matteo/Downloads/ADT-18.0.0.zip!/site.xml.
error in opening zip file</code>.
Last thing, if I open Window->Preferences and go on Android I see this:
This question is not a duplicate of Android device chooser - My device seems offline (of which I read every single line). It's a request for some rigorous solution from the community. In fact non of the proposed solutions helped me in getting my device to appear online, as you can see in the attached snapshot.
Please help me! Any suggestion will be very appreciated! ;D

Ok open sdk manager /sdk/tools/android now download the sdk for your new android version. In my case it was API 17. Once its done you should be ready.
If you still got some issue be sure that you have the last version of the ADT installed. Installing it again http://developer.android.com/sdk/installing/installing-adt.html
Now you should be ready to go.

This application, or a library it uses, is using NSQuickDrawView, which has been deprecated. Apps should cease use of QuickDraw and move to Quartz

how can we solve this types of the error -> "This application, or a library it uses, is using NSQuickDrawView, which has been deprecated. Apps should cease use of QuickDraw and move to Quartz."

This is a problem with Mac OSX and the Eclipse Android emulators. There is nothing wrong with your code. It seems to happen at it's own whim. I find that starting the emulator on its own (Window>Android SDK and AVD Manager, select the emulator and click Start...) and then running the build once the emulator is online seems to eliminate it, but this could be pure superstition. Nonetheless, it will work on your Mac if she is in the right mood.
http://groups.google.com/group/android-developers/browse_thread/thread/f10995f2a829229d

This is a probleme with osx Emulator.
You can ignore this warning but to test your app you must:
1-launch your emulator by running your app (you will have warning message)
2- wait for emulator to start completly
3
. Since emulator and wait for it to start and then relaunch your app.