Develop Reference

Error 1073741819 when launching AVD in Android Studio

I've been playing around with settings of OpenGL renderer in AVD.
Once I finished, closed the editor and tried to launch the virtual device, the following error with code 1073741819 was thrown.
ERROR: Invalid GPU mode 'angle9', use one of: host swiftshader_indirect. If you're already using one of those modes, the emulator installation may be corrupt. Please re-install the emulator.
However, there is no possibility switching the settings back. Manualy editing config files of the virtual device wont help anyway. Neither reinstalling or deleting Android Studio at all.

The only solution came from following steps:
1. Locate the emulator location
Hit the SDK tools icon in order to get the exact location
2. Launch emulator manually
> cd C:\Users\jakub.meinlschmidt\AppData\Local\Android\Sdk\emulator
> emulator -list-avds
Nexus_S_API_29
> emulator -avd Nexus_S_API_29 -gpu host
If your virtual device is not appearing the list, try to reboot your computer (worked for me).
3. Open AVD Editor
Once you successfully launch your virtual device, navigate to the OpenGL settings (as shown in the first picture) and switch to a different option.

Failed to boot android virtual device (AVD) when data is stored on USB memory stick

After successfully setting up a new virtual device with Android Virtual Device manager, booting fails and reports the following error:
10:28 Emulator: emulator: ERROR: A snapshot operation for 'Nexus_5X_API_28' is pending and timeout has expired. Exiting...
10:28 Emulator: Process finished with exit code 1
This sounds similar to a previous question by Anjan Biswas, yet with a possibly different context:
- OS: OpenSuse Leap 42.3
- Android Studio 3.2.1: installed and run from exfatfs memory stick
- .android/avd/{my device} directory holds no "*.lock" file
- The user running Android Virtual Device manager is also the actual owner of .android/avd directory tree.
The message happens exclusively when emulator data is actually saved on the memory stick (either through a symbolic link or by setting ANDROID_SDK_HOME environnement variable).
Explicitely:
- When emulator data is saved on HDD in "/home/{user}/.android" everything works just fine.
- When emulator data is saved on memory stick in "{exfatfs mount point}/.android" error occurs.
- Tried with fat32 file system with same issue.
Looking for a fix to avoid saturate /home with large android virtual device cache.
Many thanks

I also encountered the same problem, it seems to be the problem of exfat format.
I tried to mount an apfs disk and the problem disappeared.

Android Emulator is not working after update

Recently I updated my Android SDK and emulator. After that I'm not able to run the 'Hello world' program. While loading the emulator I am getting warnings and error like this.
OpenGL backend 'angle' without OpenGL ES 1.x library detected. Using GLESv2 only.
emulator: WARNING: encryption is off
TextureDraw: Could not create/link program: Failed to create D3D shaders.
Hax is enabled
Hax ram_size 0x40000000
HAX is working and emulator runs in fast virt mode.
audio: Failed to create voice `goldfish_audio'
qemu-system-i386.exe: warning: opening audio output failed
audio: Failed to create voice `goldfish_audio_in'
qemu-system-i386.exe: warning: opening audio input failed
audio: Failed to create voice `dac'
audio: Failed to create voice `adc'
draw: no program
draw: no program
.
.
.
ANGLE: egl::`anonymous-namespace'::CreateDisplayFromAttribs: make D3D display
ANGLE: D3D9: rx::Renderer9::generateConfigs
I tried lots of uninstall and update, downgrade of sdk, etc., but nothing is working and I'm not able to get the exact problem.
I have installed 2 SDK platforms:
Android 7.0
Android 4.2
My SDK tools are:

I had the same problem, the solution is to change "the amount of physical RAM" when you create a virtual device android... make 512 MB because your computer can't read a space (1.5 GB ) in RAM.
How to create a virtual device correctly to solve this problem?
First, open Android Studio, then click Tools > Android > AVD Manager.
Second, click Create virtual Device after choose a device (for example : nexus 4) and click Next and Select a system Image, then click Next.
Third, click Show Advanced Settings; scroll until you see "RAM" and change the value to a lower value, for example 512MB.

Error in running sample android application on an emulator

I am new in android development.
I created the sample hello world and try to run it on a emulated nexus 7 system.
I am using android studio 1.8.14.
When I run the application, I am getting this message in andoid studio:
Waiting for device.
Target device: test_nexus_7 [emulator-5554]
Uploading file
local path: C:\Users\m\AndroidStudioProjects\MyApplication\app\build\outputs\apk\app-debug.apk
remote path: /data/local/tmp/com.example.m.myapplication
Installing com.example.m.myapplication
DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/com.example.m.myapplication"
Error: Could not access the Package Manager. Is the system running?
what is the problem and how can I fix it?

It may be a known bug. Does this solve your issue?
"2 Error: could not access the package manager. Is the system running?
You may have gotten this error while attempting to run an Android application on an emulator or device using Android Studio. The most common cause of this error is simple: You have to manually unlock your Android Virtual Device by swiping the “lock” icon on the screen. Security measures prevent the emulator from letting you connect the debugger before doing this."
Read more at http://www.airpair.com/android/bugs-annoying-android-developers#1vMSj7GfowjRvMLG.99
Other suggestions: wait for the emulator to fully start up, which could take longer than you expected, or try debugging on an Android device, which is faster and has access to native functionality, rather than in an emulator.

Error: Could not access the Package Manager. Is the system running? - At Android Studio

I installed android studio and tried to run easy projects.
But I caught strange error message:
Waiting for device.
/usr/local/idea/android-studio/sdk/tools/emulator -avd Nexus-4-18-xhdpi -netspeed full -netdelay none
emulator: emulator window was out of view and was recentered
Device connected: emulator-5554
Device is online: emulator-5554
Target device: Nexus-4-18-xhdpi [emulator-5554]
Uploading file
local path: /home/nazar/Documents/coursera-android/Examples/HelloAndroid/out/production/HelloAndroid/HelloAndroid.apk
remote path: /data/local/tmp/course.examples.HelloWorld.HelloWorld
Installing course.examples.HelloWorld.HelloWorld
DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/course.examples.HelloWorld.HelloWorld"
Error: Could not access the Package Manager. Is the system running?
I couldn't figure out why this happen?
I installed sdk version and configured emulator. Any suggestions?
Here is emulator confiuration:
Update:
I tried to install Genymotion device and use few virtual devices, but caught:
Waiting for device.
Target device: genymotion-nexus_4___4_4_2___api_19___768x1280-192.168.56.101:5555
Uploading file
local path: /home/nazar/Documents/coursera-android/Examples/HelloAndroid/out/production/HelloAndroid/HelloAndroid.apk
remote path: /data/local/tmp/course.examples.HelloWorld.HelloWorld
Installing course.examples.HelloWorld.HelloWorld
DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/course.examples.HelloWorld.HelloWorld"
WARNING: linker: libdvm.so has text relocations. This is wasting memory and is a security risk. Please fix.
Error: Could not access the Package Manager. Is the system running?
How to solve this error?

First make sure you are running Android Studio version above 0.3.2 because there was some issue reported regarding the same in AS 0.3.2 . If it is not you can update it from Help >Check for update.
If you are already running AS above 0.3.2 :
Seems like issue is with your emulator not with Android Studio. It may happen that you are trying to install application before even the emulator started properly.
Wait till the home screen appears in the emulator before trying to install any application.
Also try to install any apk in Emulator from command line
Steps to install
Go to $Android_SDK_DIR\platform-tools, right click there keeping
shift key pressed and Chose "Open Command Window here".
Run command adb devices to make sure yout emulator is running
properly. It will show all your running emulators.
Now if emulators are showing properly, type the command adb install
YOUR_FULL_APK_PATH , YOUR_FULL_APK_PATH is of any .apk file path in
your system.
Please update if this works fine.

The most common cause of this error is simple: You have to manually unlock your Android Virtual Device by swiping the “lock” icon on the screen. Security measures prevent the emulator from letting you connect the debugger before doing this.
The problem is resolved:
In Android Studio
Start run/debug
if you see the message
Do not closed the AVD, just click on run/debug again, the Application will be running when you unlock the application.

The same problem but different solution, I modified my Virtual Device, I changed Memory option and Internal Storage, and it works fine.
RAM:512 , VM HEap: 192, Internal Storage=200, SD Card Size: 200 for Device Nexus 4 android 4.2.2.

In my case this error was caused by SELinux. I got to set SELinux to permissive.
adb shell su 0 setenforce 0

I had this issue, but I found that simply killing the emulator and restarting it worked. There seems to be some sort of race condition where the emulator has not initialized before Android Studio tries to launch the apk and so you get the package error.

I had this too, and using this config worked for me :
Device: Nexus One
Target: Android 4.2.2 -api level 17
CPU/ABI: ARM (armeabi-v7a)
Keyboard: Hardware keyboard present
Memory Options:
RAM: 512
VM Heap: 192
Iternal Storage: 200
SD Card:
Size:200

This Is Worked for me
1)Close Solution.
2)Close Emulator.
3)Run Emulator and Wait till it launch completely and shows Home Screen.
4)After that only Open Solution And Clean,Rebuild and Try to deploy Application.

The same happened to me right now. I don't know if there is another but for me the following worked:
Opened AVD (Android Virtual Device) Manager
Started virtual device
Hit the Run button again (that one at status bar)
Explanation: The problem happened because of timeout. Once device had started, the Android Studio could comunicate with him. (v 0.5.3)

Remove this emulator (in the AVD)
Install this emulator (in the AVD) :)