Bootloops & Coffee: The Daily Grind of an AOSP Developer
summary
Reports running a vendor-agnostic EFI app GBL on devboards, chainloaded via U-Boot, to standardize boot behavior and require vendors to implement a few EFI protocols; page-size agnostic builds move to 16K page-size builds, showing 5–10% perf gain at ~9% RAM cost by aligning binaries and filesystems; testing covers 13 kernel variants across seven userspace combos; notes include UUID case-sensitivity, an ashmem compatibility shim for MEFD, frequent GKI symbol/module breakages, and migration to the Android latest release workflow.
AI-written summary · about
chapters (14)
- 0:00Welcome
- 1:04Linaro’s AOSP role
- 3:10Tracking AOSP features
- 3:32Bootloader fragmentation
- 7:31AOSP builds page size
- 9:59Notable AOSP additions
- 12:07Common AOSP breakages
- 15:00Upstream project challenges
- 17:51Mesa Freedreno issues
- 19:16AOSP policy shifts
- 21:28Missing Pixel configs impact
- 22:35Community devboards
- 24:42Closing remarks
- 25:49Q&A
related talks
33mAndroid Boot, DRTM, UKIs
33mGeneric BootLoader on Android Platforms
37mA Developer's Diary: The Trials and Triumphs of Maintaining Devboards in AOSP
25mBootStomp: On the Security of Bootloaders in Mobile Devices
38mHow to Enable Android (AOSP) on Your Developer Board
43mEmbedded Android #3 - Native Android user-space
43mEmbedded Android #1 - Android Internals
24mImproving the Bootup Speed of AOSP