Building Embedded Systems with AOSP - Why You Should Consider, Best Practices and...
summary
AOSP gives a ready-made UI, media/camera stack, AI runtime and OTA support but demands heavy infrastructure: expect a 200 GB checkout that grows to ~500 GB when building, multi-hour builds and beefy SSD/CPU machines. Key wins include a generic kernel image strategy, verified boot/verity and hardware keystore for security, and a mature emulator ecosystem (AVD, Goldfish, Cuttlefish). Recommended workflow: use Gerrit + CI pipeline with containerized builds, style checks and hardware/emulator tests; vendor BSP quality and limited upstream contribution remain frequent pain points.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:07Why consider AOSP
- 3:42AOSP basics vs Android
- 7:01AOSP embedded advantages
- 13:42AOSP pain points
- 19:53When to choose AOSP
- 23:32Best practices for AOSP
- 28:12Vendor BSPs and boards
- 31:08Gerrit and CI for AOSP
- 33:17Emulator and testing in AOSP
- 35:07Q&A
related talks
35mAOSP customization
40mAOSP customization
51mEmbedded Android #2 - Working with the AOSP
37mAOSP Development Environment
32mAndroid Open Source: What more can we do with Android?
44mAOSP Developers Birds of a Feather
17mDeploying Android AOSP at Scale
38mHow to Enable Android (AOSP) on Your Developer Board