Develop Reference

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.

ida pro sigstop android mediaserver

I have to debug libmedia.so on Android 5.1 (LG G4) with kernel 3.10. I use IDA Pro 6.8. After I'm attached to the mediaserver process, in the segment view, IDA shows the code segment of libmedia.so with exact starting and ending addresses (controlled in /proc/pid/maps) but the routine's addresses of libmedia.so are outside the code segment of the libmedia.so. Ignoring that and going on with debugging, I set a breakpoint at the startInput routine, called when the microphone is needed. After setting the breakpoint, IDA returns:
F75EC260: got SIGSTOP signal (Stop unblockable) (exc.code 13, tid 8552)
The address 0xF75EC260 is in the libc.so and corresponds to instruction:
svc 0
Has anyone encountered this problem? Is there any anti-debug protection in Android 5.1? In previous versions of Android, there are no problems with debugging.

Xperia z1 compact Android Lollipop Unable to read from '/sys/class/leds/wled:backlight/max_current'

After android 5 lollipop update I have a lot of error message on adb logcat console:
280-300/? E/leds-amami﹕ Unable to read from '/sys/class/leds/wled:backlight/max_current'
from ps
system 280 1 14284 1044 ffffffff 00000000 S /system/bin/illumination_service
It is hard to develop on android with this message every 50ms
Is there a solution or we must hope in an update?

Waiting for Sony answer I have found a workaround to exclude from logcat the booring message. I have realized a regex filter on Android Studio as in the image

Deploying a Qt application on virtual Android device

I am trying for several days to simply deploy a qt 5 application to an Android machine. I have done the following:1. Install AVD Manager and use a template device(NexusS, 343RAM, 480x800)2. Start the device with start->run->cmd-> "emulator-arm #NexusS", emulator start without a problem.3. Qt 5.1 creator->New Project->Qt quick2(built-in types)->3.1.Select build kit: Android for arm(gcc 4.7, Qt 5.1.1)4.In project settings says that mingw32-make is not found and I set it to the path that I found in qt(Qt5.1.1_Android_x86\Tools\mingw48_32\bin\mingw32-make.exe)
5.Build the app, it builds ok6.Run the app.(the NexusS device remained open)
In the application Output I get:
E/libEGL ( 848): called unimplemented OpenGL ES API
E/libEGL ( 848): called unimplemented OpenGL ES API
W/Qt ( 848): opengl\qopenglshaderprogram.cpp:319 (bool QOpenGLShaderPrivate::compile(QOpenGLShader*)): QOpenGLShader::compile(Vertex): failed"
W/Qt ( 848): opengl\qopenglshaderprogram.cpp:319 (bool QOpenGLShaderPrivate::compile(QOpenGLShader*)): QOpenGLShader::compile(Fragment): failed
E/libEGL ( 848): called unimplemented OpenGL ES API
......
And the NexusS emulator enters the application, for ~1 sec displays the name of the application and after that it displays a grey screen and remaines in the grey screen until i exit the app.
Any ideas?

Android VM crashes on Launch Mac

I have a problem.
I've been working with Android in Eclipse for the past 4-5 weeks now and never had a problem with the VM (they were slow, yes. But never crashed).
Now, I believe since 4.2 when I started working on a new project for uni (deadline next week) my 4.2 VM suddently starts crashing on launch, because of "Kernel Panic" (resport at the end).
I wanted to ask if there is anything I could do, maybe download a hotfix or anything. Both the API and Eclipse are pretty much up to date or might there be something wrong with my computer?
(Somehow even my old VMs (2.3.3, 3.1 and 4.1) crash on launch 99% of the time)
Any advice would be highly appreciated. Here the beginning of the Crash-Log:
Process: emulator64-arm [1334] Path:
/Users/USER/*/emulator64-arm Identifier: emulator64-arm Version:
??? Code Type: X86-64 (Native) Parent Process: eclipse [1156]
User ID: 501
Date/Time: 2012-12-01 00:25:27.469 +0100 OS Version: Mac OS
X 10.8.2 (12C2034) Report Version: 10
Interval Since Last Report: 130686 sec Crashes Since Last
Report: 96 Per-App Crashes Since Last Report: 32 Anonymous
UUID: ABE51F99-F7A9-2595-016E-C47FFD1F6C50
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes:
KERN_INVALID_ADDRESS at 0x0000000000000000
VM Regions Near 0:
-->
__TEXT 0000000100000000-0000000100247000 [ 2332K] r-x/rwx SM=COW /Users/USER/*
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

Do you have two screens? if yes, did you launch avd/vm on secondary screen last time?
If yes, then check config vm file at:
cd ~/.android/avd/
ls -la => here you see all avds
cd [your_vm.avd]
joe emulator-user.ini => edit this config file and see value
window.x = 2054 - this is stupid value, cause says where to display emulator window. Value is set cause emulator window was displayed at second screen on x position 2054 but as I say it's bug at avd. Simply change it to better value to display window at your main screen so like my case:
window.x = 954
window.y = 199
uuid = 1342941165631
Save config file, start eclipse, start your avd/vm and all must run well.

It looks like this happens when an external monitor is connected. Try disconnecting your external monitor and then start emulator. You can attach it back after the emulator starts.

I had the same problem. Yesterday it worked fine. Today crashes with EXC_BAD_ACCESS. Then I noticed that the audio I was listening to stopped for half a second when launching the AVD. I though that might have something to do with it. I stopped iTunes I was listening to, restarted the AVD and yes success. No crash, it started up nicely.