Android Framework

This topic is for developers who want to understand how Android actually runs. The focus is not API usage. It is how app processes, system services, the Binder driver, and the Framework layer cooperate.

Learning Path

  1. Start with processes, threads, and the message loop.
  2. Then study Binder IPC and build a mental model for cross-process calls.
  3. Move on to system services and the app-to-Framework interaction path.
  4. Finally, fill in ContentProvider, permissions, and security boundaries.

Core Articles

System Startup, Processes, and Services

Problems This Topic Helps Answer

  • Why do Android apps and system services have to work through Binder?
  • How are AMS, WMS, PMS, and similar services called from app-side code?
  • How do the main thread, Handler, and Binder thread pool divide responsibility?
  • Why is ContentProvider both a data API and a cross-process boundary?
  • Where does permission enforcement happen: before the call, during the call, or inside the system service?

Next Step

After this topic, continue with Android Performance Optimization. The clearer the Framework path is, the easier it becomes to diagnose cold start, ANR, rendering, and memory issues.