Android 採用分層架構,從底層硬件抽象到上層應用框架,每層職責清晰、接口標準化。本文基於 Android 10+ (Project Treble 後) 架構,詳細解析六大層級組件、跨層通信機制 (HIDL/AIDL/JNI)、啟動流程與安全邊界。
+---------------------------------------------------------------+
| System Apps (系統應用) Settings, Phone, Launcher, ... |
+---------------------------------------------------------------+
| Java API Framework (Java 框架層) ActivityManager, WindowManager, |
| PackageManager, ContentProvider, View System, Notification... |
+---------------------------------------------------------------+
| Android Runtime (ART) Core Libs, GC, JIT/AOT, Profiling |
+---------------------------------------------------------------+
| Native C/C++ Libraries SurfaceFlinger, MediaCodec, SQLite, |
| OpenGL ES, Vulkan, WebRTC, libc++, liblog, libutils... |
+---------------------------------------------------------------+
| HAL (Hardware Abstraction Layer) 標準化 C 接口: Audio, Camera, |
| Graphics (Gralloc), Sensors, GPS, WiFi, Bluetooth, DRM... |
+---------------------------------------------------------------+
| Linux Kernel (內核) Drivers: Binder, Ashmem, Logger, |
| WakeLock, USB, Display, GPU, Power Management, SELinux... |
+---------------------------------------------------------------+
.hal 文件),供 Framework 調用,屏蔽硬件實現差異。audio.primary、camera.device、graphics.composer 等。core-libart, core-icu, okhttp, bouncycastle...) 實現 Java API。system_server 進程:ActivityManagerService (AMS)、WindowManagerService (WMS)、PackageManagerService (PMS)、NotificationManagerService、PowerManagerService 等。signature/privileged) 訪問隱藏 API。| 路徑 | 機制 | 典型場景 |
|---|---|---|
| Java Framework ↔ Native | JNI (Java Native Interface) | MediaCodec、Canvas 繪製、藍牙 |
| Framework (system_server) ↔ App Process | Binder IPC (AIDL 定義接口) | startActivity、queryContentProvider |
| Framework ↔ HAL | HIDL / AIDL (Android 10+ 推 AIDL) | 相機配置、音頻路由、顯示合成 |
| HAL ↔ Kernel Driver | ioctl / sysfs / netlink | 硬件控制、中斷處理 |
init.rc 解析啟動服務zygote (孵化器進程),預加載類/資源,fork 子進程啟動 system_server 與 App 進程system_server 啟動核心系統服務 (AMS, WMS, PMS...)掌握架構分層與通信機制,是進行 Framework 定製、系統優化、安全審計、跨層調試的前提。