AOSP customization
summary
AOSP builds from more than 1,000 git repos, >100 GB of source that can grow to ~250 GB compiled, and can be developed with Android Studio by using the emulator (no vendor blobs) or by importing Pixel BSP blobs; the workflow uses repo to sync manifests, GitLab to mirror repos, and make emulator_image_zip to produce an AVD package. Builds take hours without a beefy Linux server; a dedicated server plus Tailscale cuts iteration time (reported faster than Google’s 40 min). To use hidden system APIs create a custom SDK from the AOSP intermediate android.jar.
AI-written summary · about
chapters (6)
- 0:00Introduction to AOSP
- 7:31AOSP structure and customization
- 15:02Essential AOSP tools
- 20:49Framework and app development
- 30:45Accessing restricted APIs
- 34:27Searching AOSP codebase
related talks
40mAOSP customization
51mEmbedded Android #2 - Working with the AOSP
38mBuilding Embedded Systems with AOSP - Why You Should Consider, Best Practices and...
37mAOSP Development Environment
41mThe AOSP Build System
32mAndroid Open Source: What more can we do with Android?
35mDeveloping system apps without AOSP
17mDeploying Android AOSP at Scale