Embedded Android #2 - Working with the AOSP
summary
Android source comes as ~150–200 git repos fetched with repo sync and a manifest; builds run on Ubuntu 64-bit via build/envsetup.sh then lunch and make -j, producing ramdisk, system.img and userdata.img that boot in the emulator. Builds are IO‑heavy—Gingerbread ~30 minutes, Jelly Bean ~80 minutes on a laptop—so use ccache, SSD or tmpfs. Useful helpers are mm, m, croot and adb. CTS runs overnight (tens of hours). Adding a device is a few files and vendor setup.sh and yields a build quickly though hardware support still needs HAL/kernel work.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:04What to expect
- 2:10Understanding the Android Open Source Project
- 3:59Getting AOSP with repo
- 5:46AOSP source tree
- 14:49AOSP vs Linaro trees
- 16:59System requirements
- 17:41Build environment setup
- 18:48Build and run emulator
- 20:12AOSP dev workflow tips
- 23:09Speed up AOSP build
- 26:18AOSP build system
- 27:21Android.mk recipes
- 30:32Output images explained
- 31:36Using ADB to interact with the system
- 32:58Custom SDK/NDK from AOSP
- 34:23Managing Android APIs
- 37:40Building NDK from AOSP
- 38:25Compatibility Test Suite
- 43:08Custom hardware support
- 49:31Summary
related talks
35mAOSP customization
40mAOSP customization
32mAndroid Open Source: What more can we do with Android?
37mAOSP Development Environment
38mHow to Enable Android (AOSP) on Your Developer Board
38mBuilding Embedded Systems with AOSP - Why You Should Consider, Best Practices and...- 38mHow to Enable Android (AOSP) on Your Developer Board
37mWorking with custom Android devices