Android Internals for Developers
summary
Explains how Android actually runs apps: the kernel uses an OOM killer that ranks processes (example session shows ~30 processes and the camera triggers kills), wake locks minimize CPU wake time, init launches daemons including zygote forks without exec so new apps share preloaded VM state, binder IPC sends parcels via transact/onTransact through the kernel, AIDL generates proxy and stub glue, and system_server’s Activity/Window/Package managers compute per‑process OOM scores and manage tasks, stacks and lifecycle transitions.
AI-written summary · about
chapters (15)
- 0:00Introduction to Android internals
- 1:28Android kernel fundamentals
- 3:57Out of memory killer in Android
- 6:31Wake clocks and battery optimization
- 7:58Init process and system startup
- 9:04Zygote and app process creation
- 13:01Process isolation and security model
- 14:46Binder IPC mechanism explained
- 23:45System server and core managers
- 24:49Window manager and UI handling
- 26:12Package manager and app resolution
- 27:15Activity manager lifecycle
- 32:56Memory management and OOM scoring
- 36:09Starting a new activity walkthrough
- 39:49Q&A session
related talks
43mAndroid Internals for Developers
40mAndroid Internals
43mEmbedded Android #1 - Android Internals
24mAndroid Internals - Package Manager
32mInside Android: Context, Binder IPC, Zygote
50mBirth, Life and Death, or What Happens to an App in the System
15mInvestigating Internals With Stoic
01h 08mAndroid Plateform Anatomy