Distributing Over-the-Air Updates for Android OS
summary
AOSP generates over‑the‑air packages directly from target files using the OTAA from target files script and the platform includes a sample updater app; full packages are ~1 GB while delta updates can shrink to ~5 MB. Devices need an AB partition layout (or dynamic partitions to resize) to allow background flashing to slot B and safe rollback, builds typically require ~64 GB RAM and 400 GB disk and 40–50 minutes on a beefy server, and releases must be signed and served via staged channels.
AI-written summary · about
chapters (18)
- 0:00Android OS updates intro
- 3:16Why updates matter
- 5:45OTA update process overview
- 6:48Building updates with AOSP
- 9:19Hardware for compiling Android
- 11:48AB partition layout config
- 13:57Dynamic partitions for updates
- 15:21Device config for OTA updates
- 16:46Generating update packages
- 18:31Delta vs full updates
- 20:16Metadata for update packages
- 22:01Testing OTA client reliability
- 23:47Signing updates securely
- 25:35Update distribution channels
- 26:58Installing Android updates
- 29:43Recovery-based installation
- 31:50Background install with A/B slots
- 33:13OTA implementation takeaways
related talks
29mAndroid 10 OTA update: Internals introduction
47mUpdating an Android device, okay but how does it work? The secrets of OTA (fr)
35mAOSP customization
32mAndroid Open Source: What more can we do with Android?
17mDeploying Android AOSP at Scale
40mAOSP customization
51mEmbedded Android #2 - Working with the AOSP
38mBuilding Embedded Systems with AOSP - Why You Should Consider, Best Practices and...