Closed Bug 1598440 Opened 5 years ago Closed 6 months ago

Webrender on android emulator fails to initialize

Categories

(Core :: Graphics: WebRender, defect, P3)

Unspecified
Android
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: ktaeleman, Unassigned)

References

Details

Problem

On certain platforms (Linux with AMD for example), Webrender does not initialize on the android emulator even after forcing it as it requires OpenGL ES 3.0.

Google has added support for OpenGL ES 3.0 in Android Studio 3 (2017), but it is only whitelisted for specific devices/drivers.

Workaround

To force enable the emulator to allow OpenGL ES 3, you can run this on host:
echo "GLESDynamicVersion = on" >> ~/.android/advancedFeatures.ini

source: https://stackoverflow.com/questions/24874066/does-the-android-emulator-support-opengl-es-3-0

I wonder if this is also Bug 1584659? I will try to investigate.

Priority: -- → P3

It obviously does work in automation, but I don't think it did work for me locally, using mach android-emulator to launch the emulator. I notice that code writes the file to SDK root dir, whereas Kris' command (which worked for me) writes it to ~/. android. I don't recall having to use it on my old desktop, but I definitely did on my new one. So I'm pretty confused. Maybe I'm misremembering, or my old desktop's drivers were whitelisted, or maybe the presence of ~/.android or an env dir is making it look there rather than SDK root. 🤷🏻‍♂️

Actually, I'm guessing ./mach android-emulator won't set the use_gles3 flag? Isn't that set by the test harness only when --enable-webrender is used?

Ah yes, that's true. Might need to expose that via a ./mach android-emulator option.

Blocks: wr-android
Blocks: wr-android-testing
No longer blocks: wr-android
Severity: normal → S3

I just set up a fresh workstation, and ./mach bootstrap, ./mach android-emulator gives me an emulator with ES3. I guess older computers might not get this by default, but people should be able to find the workaround. And we have been using the workaround on CI for ages. So I think we can close this.

Status: NEW → RESOLVED
Closed: 6 months ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.