Develop Reference

Android studio emulator wrong ownership on runtime directory

When I start the emulator in Android Studio :
(Used Ubuntu 18.04.3 LTS)
Emulator: Warning: QStandardPaths: wrong ownership on runtime
directory /run/user/1000/snap.android-studio, 0 instead of 1000
((null):0, (null))
Emulator: Warning: QXcbIntegration: Cannot create platform OpenGL
context, neither GLX nor EGL are enabled ((null):0, (null))

There are two problems:
a) likely that snap install is crap, better install the standalone version of Android Studio
or run sudo chown -R 1000:1000 /run/user/1000/snap.android-studio to fix the permissions.
b) you need to install GL drivers, assuming you have a suitable graphics card available.
One can check these GL drivers with glxinfo -B.

Android Studio Emulator: Process finished with exit code 3 [duplicate]

I have been messing around with android studio and I ended up installing cocos2dx and using an arm cpu emulator to work with cocos2dx. I have recently seen a message prompting for an update for the android emulator service so I installed it and now my emulator crashes while trying to boot and gives this error in the logcat - this is the error it gave me
19:36 Emulator: **
19:36 Emulator: ERROR:/buildbot/src/android/emu-3.0-release/external/qemu/fpu/softfloat.c:486:round_canonical: code should not be reached
19:36 Emulator: Warning: QObject::~QObject: Timers cannot be stopped from another thread ((null):0, (null))
19:36 ADB rejected shell command (getprop): closed
19:36 Emulator: Process finished with exit code 3
I have no idea what this means but I know it has something to do with the update I downloaded, is there any way to roll back the update maybe?

I've come across the same issue on Windows 10: the current version of Android Emulator (Nov 14, 2018: 28.0.16) crashes or freezes as soon as a virtual ARM device is started. When I start it from command line, it prints
Emulator:
ERROR:/buildbot/src/android/emu-3.0-release/external/qemu/fpu/softfloat.c:486:round_canonical:
code should not be reached
As a temporary solution, I downgraded the emulator to an older version and the problem disappeared.
Here you can find Android Emulator 27.2.9:
Windows: https://dl.google.com/android/repository/emulator-windows-4773671.zip
Mac: https://dl.google.com/android/repository/emulator-darwin-4773671.zip
Linux: https://dl.google.com/android/repository/emulator-linux-4773671.zip
Steps to downgrade the emulator:
Stop all instances of the emulator and close Android Studio;
Open Android SDK directory. Its location can be found in the settings: Android Studio->File->Settings->Appearance & Behavior->System Settings->Android SDK->Android SDK Location;
Move existing 'emulator' directory somewhere outside of Android SDK (if you just rename and leave it there, AVD Manager will find it and start using again);
Unpack one of emulator-*-4266726.zip into the SDK directory;
Launch Android Studio and don't update Android Emulator until it's fixed.
Related answer: How to downgrade Android Emulator

I've come across the same issue on Windows 10,I upgrade Android Emulator 28.0.16 to 28.0.20 also solve the error.

qemu-system-i386 quit unexpectedly when starting AVD (Android Virtual Device) on a Mac (illegal instruction 4)

I installed Android Studio on my Mac (Macbook Pro, August 2017, OSX 10.12.4), then started up, created a hello world project and created an AVD (Android Virtual Device, Nexus 5) to run my project on it.
The error shows when I try to run my project on the simulator (pressing the play button) or when I try to start up the emulator itself.
Here's a screenshot of the error:
Here's the beginning of the stack trace:
Process: qemu-system-i386 [5779]
Path: /Users/USER/Library/Android/*/qemu-system-i386
Identifier: qemu-system-i386
Version: 0
Code Type: X86-64 (Native)
Parent Process: studio [4683]
Responsible: qemu-system-i386 [5779]
User ID: 502
Date/Time: 2017-08-22 13:20:02.612 +0100
OS Version: Mac OS X 10.12.4 (16E195)
Report Version: 12
Anonymous UUID: A816A6BA-C97F-6831-E59F-1431A005F23C
Sleep/Wake UUID: 48F2FC89-DF11-4A13-ACEB-E81AF10174B0
Time Awake Since Boot: 15000 seconds
Time Since Wake: 7900 seconds
System Integrity Protection: enabled
Crashed Thread: 4
Exception Type: EXC_CRASH (SIGILL)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Illegal instruction: 4
Termination Reason: Namespace SIGNAL, Code 0x4
Terminating Process: qemu-system-i386 [5779]
And here is the full stack trace: https://pastebin.com/raw/Btt2igX4

Disabling / Uninstalling CylancePROTECT solved this issue for me.
sudo launchctl remove com.cylance.agent_service
The same software was also preventing me from compiling go programs.
Some memory protection is at the source of the problem. Here is the relevant article for some fine tuning of CylancePROTECT that could resolve the issue with uninstalling completely the software: runtime: bsdthread_register fatal error (CylancePROTECT)

I solved it by go to ADV manager -> Select Virtual Device -> edit icon -> Select Graphics to Software GELS-2.0

Android Emulator and OpenGL ES3: EGL_BAD_CONFIG

I am running an Android Virtual Device on my Ubuntu host.
It is using the CPU/ABI Intel Atom (x86) and I am using the host GPU.
The emulator is using a Kernel-based Virtual Machine.
This works splendidly as long as I use an OpenGL ES2 context.
If my app attempts to create an OpenGL ES3 context however, using...
const EGLint contextAttribs[] = {
EGL_CONTEXT_CLIENT_VERSION, 3,
EGL_NONE
};
context = eglCreateContext(display, config, NULL, contextAttribs);
...then I get an EGL_BAD_CONFIG error:
I/biplane ( 2839): EGL: vendor Android version 1.4 Android META-EGL
I/biplane ( 2839): EGL: client apis OpenGL_ES
I/biplane ( 2839): number of EGL configurations that match our preferred criteria: 1
I/biplane ( 2839): R8 G8 B8 A8 DEPTH24
E/EGL_emulation( 2839): tid 2852: eglCreateContext(919): error 0x3005 (EGL_BAD_CONFIG)
Requesting ES3 on a hardware mobile device, works well.
But when requesting it from the emulator, it fails.
The host machine is perfectly capable of doing OpenGL ES3.0, ES3.1 and ES3.2 as can be seen from glxinfo:
$ glxinfo | grep ES3
GL_ARB_ES2_compatibility, GL_ARB_ES3_1_compatibility,
GL_ARB_ES3_2_compatibility, GL_ARB_ES3_compatibility,
GL_NV_ES3_1_compatibility, GL_NV_bindless_multi_draw_indirect,
GL_ARB_ES2_compatibility, GL_ARB_ES3_1_compatibility,
GL_ARB_ES3_2_compatibility, GL_ARB_ES3_compatibility,
GL_NV_ES3_1_compatibility, GL_NV_bindless_multi_draw_indirect,
Is there a way to run OpenGL ES3 apps on an Android Virtual Device on top of kvm?

Running GLES3 apps in the emulator is supported in Android Studio 3.0 and higher.
At the time of writing, preview builds of this version are available.
See: https://android-developers.googleblog.com/2017/05/android-studio-3-0-canary1.html
After launching the emulator, you need to change a setting, and restart the emulator as depicted below.
Also, make sure your app requests an ES3 context, because the Android sample code gles3jni does not do so.
UPDATE jun 2018
In the latest Android Studio, I can no longer select OpenGL ES3.1, even though it is the same PC.
To make it work, I had to add a file to ~/.android/ directory.
cd ~/.android/
$ echo "GLESDynamicVersion = on" >> ~/.android/advancedFeatures.ini

Notice :
OpenGL SE should be opened in emulator > Setting > Advanced
Not in the ADB page.

About HAXM in Windows 10 14393 on My Surface Pro 4

I install Windows 10 new version today (14393/1607) on My Surface Pro 4 . But When I install intel haxm to use x86/x64 android simulator, it can not start .
I uncheck hyper-v on the Control Panel -> Program. I restart my computer haxm start fail too. It give me this :
CPU acceleration status: Unable to open HAXM device: ERROR_FILE_NOT_FOUND
I try to run this script it reruen this : (sc query intelhaxm)
SERVICE_NAME: intelhaxm
TYPE : 1 KERNEL_DRIVER
STATE : 1 STOPPED
WIN32_EXIT_CODE : 577 (0x241)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
I run another script , it return this :
[SC] StartService: OpenService FAILED 5:
Access is denied.
Who can help me to solve this ? Thx !
PS : I have no any firewall in my computer . My device is Surface Pro 4

Since I clean installed my Windows 10 1607 last night during the haxm installation a windows popup tells me that the driver signature is rejected.
I suspect Intel must first update their driver signature for haxm to work again.
further reference: Windows Blog about driver signature changes in 1607

Checking the blog link you can see that disabling Secure Boot will disable this check. After I disabled Secure Boot the driver worked fine.