Update Android Emulator to API level 29+
Categories
(GeckoView :: General, task, P2)
Tracking
(Not tracked)
People
(Reporter: sotaro, Unassigned)
References
(Blocks 4 open bugs)
Details
(Whiteboard: [geckoview:m113?][geckoview:2024H2?])
Current Android emulator(24) caused rendering problem when accelerated canvas is enabled. The problem was addressed when Android emulator was more than 24. But updating Android Emulator caused another test failures.
| Reporter | ||
Updated•3 years ago
|
| Reporter | ||
Comment 1•3 years ago
•
|
||
overlay support (Bug 1810658 and Bug 1810659) is going to use ASurfaceControl. It needs API level 29+. If we want to test it on Android Emulator, it needs to be updated to API level 29+.
AHardwareBuffer needs API level 26+.
Comment 2•3 years ago
|
||
Is this something that you're going to be working on?
| Reporter | ||
Comment 3•3 years ago
•
|
||
For the time being, there are no plans to work on. I am busy for another bugs.
Updated•3 years ago
|
| Reporter | ||
Comment 4•3 years ago
|
||
Test results with current m-c.
Updated•3 years ago
|
Updated•3 years ago
|
Comment 5•3 years ago
|
||
Test result of emulator of Adnroid API level 29
I guess that many failures depends on heap/RAM size. And I guess some reftest failures depends on font, so we add/use "android_version" condition.
Actually, emulator version of mac M1 build environment is Android 30. It might be better that 29 for macOS developers.
Comment 6•2 years ago
|
||
A note: isolated process doesn't support Android 10+ yet; also, we would want to be testing isolated process builds on both Android <=9 and Android >=10, at least until the minimum supported Android version is 10
Updated•1 year ago
|
Comment 7•1 year ago
|
||
I haven't tested this lately, but bug 1797617 shows some tests that will need to be corrected depending on the API bump.
Comment 8•9 months ago
|
||
We are using Android 14 emulator.
Description
•