Develop Reference

Android Emulator process terminated

When I try to run the emulator after few seconds it shows "The emulator process for AVD "DEVICE NAME" has terminated" on latest android studio electric el.
I have an AMD processor laptop. and I am doing flutter projects on android studio. Even just opening android studio with new project its showing same process termination as above.
These are the things I have tried to solve the emulator process termination down below:
*I tried installing uninstalling android studio
*I tried installing previous version of android studio
*I tried copy pasting JRE and JDE file in c:/program file/android/android
*I tried installing command process tool (latest) in SDK manager
*I tried installing latest android emulator.
*I tried installing other version of android like 10,11,12,13
*I tried installing different phones like pixel 2,3,4.. (with or without play store and x86,x64)
*I tried Vulkan = off, GLDirectMem = on (C:\Users\yourusername.android folder advancedFeatures.ini,)
*I have more then 100GB disc space
*I have increased 2gb to 20gb (2000mb) in AVD manager phone advanced settings.
*I have terminated all the background process and restart even did restarting the pc
*I tried reinstalling windows
*I tried renaming to vulkan-1.dll
As I have AMD processor (Intel x86 Emulator Accelerator (HAXM installer)) this doesn't work
*I changed ANDROID_HOME path on environment variables.
even I tried every other thing like the link down below:
Android Emulator The emulator process for AVD was killed. Windows Intel
I just need to run the AVD manager or the emulator for flutter.
Update: I just tried android 9.0 (pie) and then I was able to change Emulated Performance Graphics from automatic to software and it was running but when I selected It to hardware it throws same error message. Can any one please fix the emulator problem. I cant test any app on emulator.

Android Studio emulator being killed

For some reason ever since I updated Android Studio to version 4.1, whenever I try to run the emulator I get this error:
Error while waiting for device: The emulator process for AVD Pixel_2_API_29 was killed.
I have tried reinstalling android studio, cold booting the device and literally everything I could think of.

newbie here but wanted to learn more about developing apps, so downloaded Android Studio to do an intro lesson and was frustrated by the same issue -emulator was "killed" before opening. Well, I think I saw a vague suggestion somewhere to uninstall Emulator using SDK Manager (SDK Manager - System Settings - Android SDK - SDK Tools), then reinstalling from same place (SDK Manager). Voila! It worked for me. The emulator works and I see my virtual device. As a newbie you can imagine how cryptic this all was for me, but it's one way to learn, I guess!

Waiting for Target Device to Come Online

I recently updated to Android Studio 2.3, and now when I try to run the application, the emulator does not come online. It times out after 300 seconds.
Additionally, The app has been experiencing a FATAL EXCEPTION ERROR (OOM), and I am not sure how to fix that either, or if that is part of the emulator problem.
Any help is much appreciated. Again, my knowledge in the program is very limited so if your answer can be kept simple, that would be great.

Following worked for me on Android Studio 3.x.
Step 1:
Open AVD Manager.
Step 2:
Right click and Wipe data for the virtual device you're testing on.

I too had the same problem, then I went to AVD manager and right click on the emulator and stopped it and I RUN the application again and this time it worked.
It may be a temporary solution but works for the time being.
Tools -> AVD manager -> right-click on the emulator you are using -> Stop
Now Run your application again.
Note: Sometimes closing the emulator directly is not working for the above-mentioned problem but stopping it from the AVD manager as mentioned is working.

In case you are on Mac, ensure that you exit Docker for Mac. This worked for me.

Three days on this, and I believe there's a race condition between adb and the emulator. On a request to run an app, with no emulator already running, you see the "Initializing ADB", then the emulator choice, it starts and you get "Waiting for target to come online". An adb kill-server, or a kill -9, or an "End Process" of adb with the task manager will cause adb to die, restart, your APK installs and you're good to go. It does seem funky to me that an "adb kill-server" causes adb to die and then restart here, but that's another mystery, maybe.

Another case is Android Emulator should be reinstalled. This can happen, when you install a higher version of Android Studio, then update SDK for it, and go back to previous one.
Tools - Android - SDK Manager - SDK Tools - Android Emulator -
uncheck, apply, check, apply
Disable Docker app if you have it (Mac users).
Restart emulator:
Tools - Android - AVD Manager
(or kill adb process in task manager).

Go to AVD Manager in your Android Studio.Right Click on your emulator,and then select wipe data.Then run your app again.
The emulator will perform a clean boot and then install your apk then your app will finally run.
Summary:AVD Manager---Right Click Emulator----Wipe Data----Run App Again
If the problem presists,then simply go back to your avd manager ,uninstall emulator,then add a new emulator.Once the new emulator is added,in your avd manager,run the emulator...Then run your app.
Its much simpler if you have an emulator already running from the onset before running your application for the first time

After trying all these solutions without success the one that fixed my problem was simply changing the Graphics configuration for the virtual device from Auto to Software (tried hardware first without success)

This solution works for me :
Tools -> AVD Manager -> click drop down arrow -> select Cold Boot Now

Below steps work for me
Close running emulator
Go to AVD Manager
Choose available emulator
In that action tab (last one), click on drop down arrow & select COLD BOOT NOW
Finally run your application

Seems like Android Studio (using version 3.5.1) gets into a weird state after a while. This worked for me.
File -> Invalidate Caches / Restart -> Invalidate and Restart

Go to AVD Manager right click on your device and select Wipe Data and Cold Boot Now.
For me it worked correctly.

After trying almost all the solutions listed above, what finally worked for me was to create a new virtual device using a "Google APIs" image instead of a "Google Play" image.

Seems that in my case the problem was in that the "Google APIs ARM EABI v7a System Image" wasn't automatically installed during installation of Android Studio.
After installing the image, the emulator began to work.
Screenshot of the SDK manager

Did not read all the answers. Anyway Accepted one didn't work for me. What did was upgrading the android studio to last stable version and then created a new virtual device. I guess my nexus 5p virtual device got out of sync with the android studio environment.

This worked for me on Android studio 4+ and Mac OS
Delete all AVD's that you currently have.
Go to Preferences > Appearance & Behavior > System Settings >
Android SDK > SDK Tools
Uninstall Android Emulator
Restart Android Studio.
Re-install Android Emulator from the same place.
Create a new emulator!

I discovered that having a running instance of Docker on my machine (OSX) prevented the Android Emulator from running (see Android Studio Unable to run AVD)
Previously, my emulator would appear to start, then fail before any device window was shown.
I also had to use 'kill -9' (as per #MarkDubya ) to get Android Studio to connect to the virtual device.

Like urupvog's answer, make sure that you aren't running any other virtual machines like VirtualBox. When I restarted my computer, AVD worked until I started Vagrant for backend development (then it wouldn't launch).
See Android emulator and virtualbox cannot run at same time for more info.

Check you don't have the deviced unauthorized, unauthorized devices reply the same error in the Android Studio, check the emulator once is on with the adb command.
$ adb devices
List of devices attached
emulator-5554 unauthorized
If you have of this way the emulator the Android Studio is waiting for be authorized and maybe this can solve the problem.
Authorized Devices
This is a error I have solved in Windows 10 with Android Studio 2.3.3

Fix for this issue is simple :
Go to SDK tools > SDK Tools
Check Android Emulator and click Apply
and sometimes you might see there's an update available next to it, you just need to let it finish the update

For those stuck on this problem on a device and not the emulator, make sure your app isn't set as the device owner.

Question is too old but may be helpful to someone in future.
After search many things, most of them is not worked for me. SO, as per my try This solution is worked for me. In short uninstall and install "Android SDK Tools" in Android SDK.
Few steps for that are below:-
go to "SDK Manager" in Android Studio
go to "SDK Tools" tab
Uninstall "Android SDK Tools" (means remove check(uncheck) ahead of "Android SDK Tools" and Apply then OK)
Close and Restart Android Studio
Install "Android SDK Tools" (means check ahead of "Android SDK Tools" and Apply then OK)
Image of Uninstall and Install Android SDK Tools again

The problem is that there is no link between ide and the emulator.
In our case - we lowered version of android for the app, that frustrated ide in emulator linking.
If we install Android 25 and bind project to it, and AVD Device on Android 25 as well - it links and apllies changes on the fly. If we downgrade to Android 14 and device on android 14 - it doesn't.
Used Android Studio 2.3.
To play with versions you can set in Gradle Scripts - build.gradle (Module: app):
android {
compileSdkVersion 25
defaultConfig {
minSdkVersion 15
targetSdkVersion 15
}
}
As a result app won't run on an Android 25 device with a message:
Installation failed with message Failed to finalize session : -26:
Package ru.asv.test new target SDK 15 doesn't support runtime
permissions but the old target SDK 25 does.. It is possible that this
issue is resolved by uninstalling an existing version of the apk if it
is present, and then re-installing.
WARNING: Uninstalling will remove the application data!

I also ran into this problem and probably found the solution that may help. The key is launching the AVD in the emulator first then run your App.
Following are the steps:
In the Your Virtual Devices screen, select the device you just created and click Launch this AVD in the emulator
Once the emulator is booted up, click the app module in the Project window and then select Run → Run
In the Select Deployment Target window, select the emulator and click OK.

For Linux users using KVM and facing this problem try setting the Graphics option on the Android Virtual Device to Software instead of Automatic or Hardware . As previously mentioned in this answer.
I can confirm that the method works for Arch Linux, Ubuntu 16.04, as well as windows with or without a proprietary graphics card using Android Studio version 2.3.1+

I am working on notebook, Windows 8. I solved this issue change mode from battery saving mode to balanced mode. Before that, an emulator didn't work and I see "Target Device to Come Online". Also didn't work Genymotion

I had a similar problem when updated my android studio. Somehow it changed my SDK path. I just changed it to my updated SDK path and it worked.
Android Studio -> File -> Settings -> Appearance & Behaviour -> System Settings -> Android SDK
Here you will find Android SDK location just click on edit link in front of that and browse and select the Android SDK from the file browser. Select and click on Apply.
Select AVD manager and start Emulator. This solution worked for me.

Go to terminal and type android avd. Select your AVD and select "Edit". Make sure you do not see No CPU/ABI system image available for this target - it will show in red font at the bottom. Change the target to the one that is available or download the ABI image. Sometimes, if you create an AVD from inside Android Studio, it does not ensure this requirement.

None of solutions above worked for me, so I had to wipe content of
C:\Users\your_name\.android\avd
and re-create emulated device

I've had the same problem (AVD not coming online) in a Linux system. In my case, I have solved it setting this environment variable:
$ export ANDROID_EMULATOR_USE_SYSTEM_LIBS = 1
This case is documented here: https://developer.android.com/studio/command-line/variables.html#studio_jdk

Finally, I solve this problem by setting the right export path in bash file:
export ANDROID_HOME=/Users/[username]/Library/Android/sdk

Eclipse hanging when launching android application

I've been having this problem in eclipse whereby my project builds fine, but when I run the application, eclipse hangs and either freezes or throws up a launch error like below
[2012-11-02 14:17:31 - Unexpected error while launching logcat. Try reselecting the device.] device not found
com.android.ddmlib.AdbCommandRejectedException: device not found
at com.android.ddmlib.AdbHelper.setDevice(AdbHelper.java:752)
at com.android.ddmlib.AdbHelper.executeRemoteCommand(AdbHelper.java:373)
at com.android.ddmlib.Device.executeShellCommand(Device.java:462)
at com.android.ddmuilib.logcat.LogCatReceiver$1.run(LogCatReceiver.java:110)
at java.lang.Thread.run(Unknown Source)
I've also got this error file Picture of error file
I'm not sure how to pinpoint the source of this problem. I'm using android sdk 4.1.2(APK 16) and android ADT 21 (Preview) on eclipse indigo on a windows 64bit machine. I've also installed the latest available drivers for my device, nexus 7
The same issue occurs whether I try to run on a device or on an emulator so I'm a bit lost as to where to start the troubleshooting...

You might try to set higher memory limitations in your Eclipse.ini. The actual launch of your application requires more memory due to building the APK, where before that point of time only the Java compiler was involved.
Additionally you may try to work around your problem by starting the AVD manually from the Android AVD manager dialog (which can be reached via one of the toolbar buttons). Then launch your app only after the emulator has been fully started.

eclipse with android doesnt run application stuck at pre-launch chech stage

A serious problem working with android dev with eclipse (with the plugin and sdk installed)
when trying to run an application to the emulator - the progress bar shows:
Launching: Performing pre-launch check..
and stucks there- doesn't continue even after a couple of hours.
I tried killing the adb process, running the emulator before the app and with 'wipe user info'
but nothing helps - just stuck at this stage
I also tried the answers at this thread but didn't help (mostly the same suggestion I already tried)
edit: sometimes(I'm not sure all the times) I'm getting this in the logs:
[2011-11-26 11:28:14 - hierarchyviewer]Unable to get view server
version from device emulator-5554 [2011-11-26 11:28:14 -
hierarchyviewer]Unable to get view server protocol version from device
emulator-5554 [2011-11-26 11:28:16 - hierarchyviewer]Unable to debug
device emulator-5554
any ideas?

solved this myself, seems to be a problem with updgrading the andoid sdk before the adt plugin or vice versa or what ever. anyway to solve had to:
remove all the android plugin
uninstall eclipse (if relevent and delete the whole folder)
also delete the .metadata folder in the eclipse workspace and restart the computer(always a good suggestion/
reinstall/update the android sdk
= reinstall/unzip eclipse
reinstall the ADT plugin
have fun

That's curious... I have the same problem however when I deployed my android's app that's launched in my device and for my surprise I can read the LogCat
Try seen on system device administrator if your device it's recognized by the system.