A Developer's Diary: The Trials and Triumphs of Maintaining Devboards in AOSP
summary
Linaro keeps Qualcomm DragonBoard 845c and RB5 up-to-date in AOSP, running 13 Android kernel combinations across four userlands via LKFT, and documents frequent failures from bad repo syncs and manifest/Android.bp churn. Major pain points are boot image header churn and GKI boot regressions caused by symbol-list and protected-module changes; firmware blobs must move to vendor hosting so builds fetch them pre-build. Upstreaming Mesa breaks often, including a persistent Mesa runtime crash that required switching binaries or shipping firmware in ramdisk as a workaround.
AI-written summary · about
chapters (22)
- 0:00AOSP devboard maintenance intro
- 1:03Devboards in AOSP and Linaro
- 3:12Choosing AOSP devboard
- 4:36Linaro's Android support role
- 6:23AOSP codebase challenges
- 7:05Android release vs AOSP branch
- 9:19AOSP sync pitfalls
- 10:44Device manifests and framework changes
- 11:25AOSP build tools evolution
- 12:08Kernel patches and Linux limits
- 12:51Bootloader and partition issues
- 13:33GKI boot failure troubleshooting
- 16:47Non-tech AOSP hurdles
- 17:51Firmware blobs policy changes
- 18:12Upstream Linux and Mesa tracking
- 19:17Unstable device node names
- 20:23Convincing kernel devs of bugs
- 21:47Freedreno and OpenGL in AOSP
- 24:12Updating external AOSP projects
- 25:58Experimenting with device build configurations
- 27:07Key takeaways
- 27:39Q&A on WebView and devboards
related talks
14mAOSP Devboards
24mThe Devboards Community for Android- 24mThe Devboards Community for Android
38mHow to Enable Android (AOSP) on Your Developer Board- 38mHow to Enable Android (AOSP) on Your Developer Board
44mAOSP Developers Birds of a Feather
26mBootloops & Coffee: The Daily Grind of an AOSP Developer
23mAOSP Device Upstreaming and Development with X15