AOSP customization
summary
AOSP is >100 GB across over 1,000 git repositories and builds on Linux; the emulator image builds out of the box while Pixel devices need vendor binary blobs. Useful tools: repo for syncing manifests, lunch and make to build, AIDEGen to generate IDE projects, and GitLab to import thousands of repos. Practical recipes include embedding a Gradle app as a privileged system APK (convert signing keys into JKS), exporting an emulator ZIP and properties XML, and creating a “cheat” SDK from intermediate classes so hidden system APIs compile. Use cs.android.com to search the code.
AI-written summary · about
chapters (23)
- 0:00Introduction to AOSP
- 1:11AOSP structure overview
- 2:37AOSP build images explained
- 4:02Building for emulator
- 5:08Building for Google devices
- 5:50Using Lineage for customization
- 6:53Customization options in AOSP
- 8:22AOSP tooling requirements
- 10:56Setting up a build server
- 11:38Recommended development tools
- 12:24GitLab for AOSP source control
- 14:11AOSP tooling repo and lunch
- 17:21AOSP build systems
- 18:49First AOSP build steps
- 19:50AIDEGen for IDE integration
- 21:16Developing for AOSP framework
- 21:59System apps development flow
- 24:26Embedding app in AOSP build
- 27:44Creating emulator images
- 30:56Deploying system apps locally
- 33:46Using restricted APIs in AOSP
- 36:16Custom SDK for local development
- 39:10Searching AOSP codebase
related talks
35mAOSP customization
38mBuilding Embedded Systems with AOSP - Why You Should Consider, Best Practices and...
51mEmbedded Android #2 - Working with the AOSP
32mAndroid Open Source: What more can we do with Android?
37mAOSP Development Environment
41mThe AOSP Build System
35mDeveloping system apps without AOSP
46mIntroduction to AOSP, or How to Spend a Night Building Android