audience

WindowManager is the core Android system service responsible for managing the lifecycle, composition, layering, and input routing of all visual windows on a device. Operating within the system server process, it functions as the grand traffic cop for your display, ensuring that the System UI (like the status bar), background system alerts, and multiple application windows seamlessly and securely share the screen. The Core Architectural Components

To understand how WindowManager functions under the hood, you have to look at its multi-layered split between client-side application code and server-side system processing:

+———————————————————–+ | Application Process | | [View Tree] -> [ViewRootImpl] -> [WindowManagerGlobal] | +———————————————————–+ | (Binder IPC) v +———————————————————–+ | System Server Process | | [WindowManagerService (WMS)] | +———————————————————–+ | (Local Socket) v +———————————————————–+ | SurfaceFlinger Process | | [Composes Layers & Draws to Screen] | +———————————————————–+

WindowManager (Client Interface): This is the local interface available to your application process. When you call addView() or manipulate a window layout, you interact with WindowManagerImpl, which passes the command to WindowManagerGlobal.

ViewRootImpl: The literal bridge between your view hierarchy and the WindowManager. It handles the measuring, layout, and drawing of views, and communicates window changes back to the system.

WindowManagerService (WMS): The heavy-lifting engine running inside the system_server process. WMS handles z-ordering (determining which window sits on top), window tokens, visibility states, screen rotation animations, and window layouts globally across all running apps.

SurfaceFlinger: While WMS determines where windows go, SurfaceFlinger handles the actual composite rendering. WMS allocates a “Surface” (a canvas layer) for an app via WMS, the app draws to it, and SurfaceFlinger composites all surfaces onto the physical hardware display. Key Responsibilities Under the Hood 1. Z-Ordering and Layer Enforcements

WMS organizes windows hierarchically using Window Types (e.g., Application, Sub-Windows, and System Windows). Each type is assigned a strict base layer priority. For instance, an input method (keyboard) or an incoming call screen will always have a higher z-index priority than a standard application window to ensure critical system tools remain accessible. 2. Input Event Routing

WindowManagerService is closely tied to the InputManagerService. When a user touches the screen, WMS uses its global knowledge of window bounds, z-ordering, and focus states to determine precisely which window should receive the raw touch or key event, quickly routing it down to the correct client process. 3. Token-Based Security (WindowToken)

To prevent apps from maliciously injecting windows or hijacking other apps, WMS utilizes an internal authentication object called a WindowToken. The ActivityManagerService (AMS) issues a token when an Activity starts. The app must present this token to WMS to prove it has authorization to display a window on the screen. WindowManager vs. Jetpack WindowManager

As the Android ecosystem has grown to include foldables, dual-screens, and multi-window environments, Google unbundled window management capabilities from the hardcoded system core:

Core Framework WindowManager: The low-level framework service managing the strict primitives of layers, inputs, and screens.

Jetpack WindowManager: A modern client-side library built as a backward-compatible wrapper. Under the hood, it interacts with device-specific WindowManager Extensions provided by OEMs to expose cutting-edge display properties. It allows developers to seamlessly calculate WindowMetrics (for responsive UI design) and safely track physical device attributes like FoldingFeature hinge tracking without crashing older OS versions. Summary Table: Component Breakdown Role Under the Hood WindowManagerImpl Application App Local client API implementing ViewManager. ViewRootImpl Application App Coordinates view layouts and forwards paint commands. WindowManagerService system_server Manages tokens, z-ordering, focus, and system animations. SurfaceFlinger Native System

Composites raw graphics buffers directly to display hardware.

If you are debugging a specific window layout or building a feature that modifies the screen layout, let me know: Unbundling the stable WindowManager | Android Developers