Android 16

Introduction and context

Android 16 is the sixteenth major version of the Android operating system family, developed by Google. It occupies a specific position in the platform's release sequence, immediately following Android 15, which serves as its predecessor, and preceding Android 17, which is designated as its successor. Its numerical designation reflects the continuity of a version line that has progressively incorporated new security capabilities, interface elements, accessibility features, and development tools with each iteration.

Regarding its fundamental architecture, Android 16 is built upon a monolithic Linux kernel, maintaining the technical foundation that has characterized the entire Android family since its inception. The system operates under an open-source software model, which permits the inspection, modification, and redistribution of the source code within the terms established by the project. In terms of supported platform architectures, the version supports four instruction set families: ARM, ARM64, x86, and x86-64, covering both 32-bit and 64-bit processors present in mobile devices, tablets, emulators, and development environments.

The development ecosystem associated with Android 16 encompasses a broad set of components, tools, languages, and projects that enable the creation, packaging, distribution, and maintenance of applications. The following table presents a grouped overview of the elements that constitute this ecosystem:

The coexistence of these elements—ranging from the ART runtime, which progressively replaced Dalvik as the primary interpreter, to design tools such as Jetpack Compose and the Skia rendering engine—configures a development environment that allows creators to build native, hybrid, or hardware-access applications, as well as participate in the open evolution of the system itself through AOSP. This collective framework defines the technical basis upon which the specific novelties of Android 16, described in the subsequent sections, are established.

Technical Specifications and Requirements

Android 16 is internally identified as API 36, the platform level that developers must declare as their target to access the system's new capabilities. This API level marks the boundary between backward compatibility and the use of interfaces introduced in this iteration.

The reference technical parameters for the stable release are summarized in the following table:

The global version of Android 16 ships with Google Mobile Services (GMS) as a preinstalled service suite, ensuring the availability of the Play Store, Google Assistant, Google account, and associated synchronization services on the devices that receive it.

The update policy is defined as post-stable-release: once the final version is published, subsequent revisions (security patches, bug fixes, and incremental improvements) are distributed through the manufacturer's standard update channels, without the user needing to request a full new image.

The first device series to ship with Android 16 preinstalled out of the box is the Pixel 9 series. Among the devices that received the version at its initial launch are the Pixel 9, Pixel 10, Samsung S25, Samsung S26, OnePlus 13, and OnePlus 14, reflecting simultaneous distribution across Google's own hardware and major industry manufacturers.

User Interface and Design

Android 16 introduces a set of visual and interaction changes that affect the overall appearance of the system. The most notable is the announcement of Material 3 Expressive, a design language that Google has presented as an evolution of the Material system. However, in the stable release of Android 16, this design is not available; its presence has been detected and activated only in the Settings app during the Beta 3 phase. Additionally, manufacturer interfaces may add, modify, or delay the experience, meaning that the actual adoption of Material 3 Expressive varies by device.

In the area of dark theme, Android 16 expands the ability to force dark mode in apps that do not implement it natively. The feature allows darkening many light apps even when those apps do not supply their own native dark theme. The corresponding option in Settings has been renamed to “Make more apps dark”. As a limitation, some apps, screens, and manufacturer builds may not respond identically to the application of the expanded dark theme.

The status bar undergoes a specific graphical change: the Wi-Fi icon is now represented with three segments, replacing the previous representation of four arcs. This visual adjustment aims for a more immediate reading of signal strength.

The lock screen receives several improvements in this version:

• Expanded customization: Lock screen customization options already present in previous versions are maintained and extended, allowing the user to adapt the background and the arrangement of elements.
• Lock screen widgets (beta): Android 16 introduces the possibility of placing widgets directly on the lock screen. This feature is in beta status and supports a maximum of 3 widgets per page.
• Sensitive notification redaction: The system can hide the content of notifications considered sensitive when the device is in higher-risk scenarios, such as being without a Wi-Fi connection and without a recent unlock. Under these conditions, the notification text is replaced by a generic redaction to prevent the exposure of private information in case of unauthorized access to the locked device.

Notification Management and Live Updates

Android 16 restructures the notification experience with a set of features designed to reduce visual clutter and keep users informed about ongoing processes. These updates range from automatic grouping of alerts to the inclusion of advanced processing-generated summaries and the integration of live updates for delivery and transportation services.

Automatic Notification Grouping

The system groups notifications from the same application to reduce clutter in the notification panel. Instead of displaying each alert individually, automatic grouping consolidates them under a single item, simplifying readability when an application generates multiple messages in a short period.

Availability limitation: Notification behavior can vary by device maker and software build, meaning the final presentation of grouping is not identical across all devices.

Notification Organizer by Categories

The notification organizer allows users to group and silence lower-priority categories, such as promotions, news, and social alerts. This ensures that notifications not requiring immediate attention remain grouped in a discreet block without disappearing entirely, preserving the ability to review them later.

Availability limitation: Google indicated that the organizer would roll out in stages, so its presence is not guaranteed simultaneously on all devices at the time of the update.

advanced processing Notification Summaries

Android 16 incorporates the ability to generate notification summaries using advanced processing, allowing users to obtain a synthesis of accumulated messages rather than reading them one by one.

Availability limitation: This feature was added in the December release and is subject to a staged rollout as well as device or language availability. Not all devices or language configurations will receive it immediately.

Live Updates

The Live Updates feature keeps compatible delivery and ride-share progress visible directly within the notification experience. Users can track the status of an order or the location of a vehicle without needing to open the corresponding application, as the information updates in real time within the notification panel.

Availability limitation: The source application must explicitly support the feature for live updates to appear. Additionally, the device manufacturer may modify the visual appearance of these notifications, so their presentation may differ between brands.

Progress-Centered Notifications

Android 16 Beta 1 introduced progress-centered notifications, a format that prioritizes the visualization of task or process progress over descriptive text. This approach complements live updates and reinforces the concept of the notification panel acting as a real-time tracking center.

Availability Summary

Desktop Mode and Windows

Android 16 incorporates desktop-style windowing, a feature that allows compatible large-screen devices to open, move, and resize multiple application windows on a single display. This capability transforms interaction on large screens, bringing the experience closer to that of a traditional desktop operating system while retaining Android's native application management logic.

Origin and evolution

Desktop mode is not an exclusive novelty of Android 16: it was officially introduced in Android 15 QPR1, where the foundations for floating window management and the taskbar were established. Android 16 inherits and consolidates this architecture, incorporating refinements in the interface and the behavior of control elements.

Taskbar and control elements

The taskbar is located at the bottom of the screen, maintaining a fixed position that facilitates access to window management functions. Among its key elements are:

• Minimize button: available from Android 16 Beta 3, it allows reducing an active window to the taskbar without closing it.
• Recent apps carousel: the mini taskbar includes a carousel that displays up to 6 recent apps, offering quick access to switch between open windows.
• Duplicate navigation handle fix: a defect that caused a duplicate navigation handle to appear in the small taskbar was fixed, eliminating visual and functional redundancy.

Availability and limitations

Desktop-style windowing functionality is not universally available. Its use requires compatible hardware, manufacturer support, and appropriate app behavior. In practice, this means that not all large-screen devices or all applications are prepared to operate in multi-window mode, so the experience may vary significantly depending on the device model and the installed software catalog.

Accessibility and Hearing Aids

Android 16 includes specific accessibility improvements designed for hearing aid users. These enhancements were introduced starting with the beta 1 release and focus on integration with hearing devices that utilize the Bluetooth LE Audio (LEA) standard.

LEA Hearing Aid Features

Within the suite of accessibility improvements for hearing aids, Android 16 beta 1 includes two specific capabilities:

• Ambient volume controls for LEA hearing aids: This feature allows users to adjust the volume of ambient sound that the hearing aid lets through, facilitating the regulation of how much of the surrounding environment is perceived through the hearing device.
• Phone as microphone input for LEA calls: This enables the use of the phone's microphone as the audio input source during a call made through a LEA-compatible hearing aid, improving the clarity of the voice transmitted to the interlocutor.

Availability

The availability of these hearing aid controls is subject to two simultaneous requirements: the hearing aid must be compatible with Bluetooth LE Audio, and the Android device must offer support for this functionality. If either of these elements is absent, the hearing aid control options will not be accessible in the system settings.

Camera and media

Android 16 introduces a set of improvements focused on multimedia capture and processing, covering photography, video recording, and automatic exposure. These updates were distributed across the version's beta iterations, with specific contributions in Beta 1 and Beta 2.

Ultra HDR

The version includes support for the Ultra HDR format, which expands the dynamic range of captured images. In the Beta 2 iteration, specific improvements to Ultra HDR image rendering were introduced, refining the final output quality compared to early tests of the format.

Advanced Professional Video

Among the features presented in Beta 1 is Advanced Professional Video, a recording capability designed for more demanding workflows that complements the existing video capture options on the platform.

Night Mode Scene Detection

Beta 1 also incorporated Night Mode Scene Detection. This function allows the system to identify the type of scene in low-light conditions and automatically adjust capture parameters, optimizing the result without manual user intervention.

Hybrid Auto Exposure in Camera2

At the API level, Android 16 adds support for hybrid auto exposure modes in the Camera2 interface. This capability, confirmed in Beta 2, allows camera applications to combine exposure strategies more flexibly, providing developers with additional control over light balance in complex scenes.

Collectively, these enhancements reinforce Android 16's position as a multimedia capture platform, expanding both the options available to end users and the low-level tools accessible to camera application developers.

Developer Platform and Migration

The upgrade to Android 16 is designed to minimize the workload for development teams, as no major rewrite is required for most applications. However, the platform introduces mandatory structural changes and new API capabilities that require specific code adaptations to ensure compatibility and proper functionality on the latest devices.

Mandatory Changes and Compatibility

One of the most significant changes is the mandatory edge-to-edge content. Starting with this version, applications must render their interface extending to the edges of the screen, and the option to disable this functionality has been completely removed. Developers must adjust their designs to properly manage safe areas and system bars.

Regarding navigation, migration or disabling of the predictive back gesture is required. Applications must adapt to this new interaction model or explicitly disable it if it is not compatible with their user flow. Additionally, compatibility with three-button navigation has been reinforced, ensuring that interfaces function correctly regardless of the navigation method selected by the user.

New APIs and Platform Capabilities

Android 16 incorporates a series of new programming interfaces aimed at improving application functionality and system management:

• App Functions API: Allows applications to expose and manage specific functions in a more integrated manner with the system.
• Generic Range APIs: Facilitate the definition and handling of value ranges in a more flexible and standardized way.
• Health and wellness permissions: Introduce a specific permission framework for applications that handle data related to the user's health and wellness, improving privacy and control.
• Fixed-rate work scheduling optimization: Improves the efficiency in executing background tasks that require strict periodicity.

System Features and Utilities

The platform also adds support for specific hardware and software features that developers can integrate into their applications:

• Linux terminal in AVF: Incorporates the ability to run a Linux terminal within the Android Virtualization Framework (AVF) environment, opening possibilities for developing applications that require a more robust command-line environment.
• Default contacts account: Establishes a function to define and manage the default contacts account, simplifying interaction with the device's address book.
• Virtual device owner overrides: Allows enterprise device administrators to apply specific overrides for virtual devices, improving fleet management in corporate environments.

Customization and Data Entry

To improve the user experience and accessibility, adjustments have been introduced in the presentation of information and interaction with forms:

• Vertical text: Support for rendering text in vertical orientation, useful for specific interfaces or languages that require it.
• Required Form Fields: New capabilities to define and validate required fields in forms, improving the accuracy of data entry.
• Measurement system settings: The preferred measurement system (metric or imperial) is now configurable by the user in the System > Languages & region path, and applications can query this preference to adapt the presentation of units of measurement.

These changes, along with the complementary descriptions provided in the platform documentation, allow developers to adapt their applications progressively, maintaining stability and leveraging the new capabilities of Android 16 without needing to completely restructure their existing codebases.

Development and Release Timeline

The development cycle for Android 16 has included public milestones that allow tracing the platform's evolution from its initial test versions to beta iterations. One of the initial reference points was Developer Preview 2, released on December 18, 2024. This build, identified by the number BP21.241121.009, incorporated the December 2024 security patch level, establishing an updated security baseline for development devices.

Beta 1 Iteration

The first beta version of Android 16 focused on stabilizing critical features and correcting specific errors that affected the user experience. Among the main corrections documented in this phase are:

• Battery drain: Fixed excessive energy consumption caused by background apps.
• Camera stability: Resolved camera screen flicker when adjusting zoom during video recording.
• Media notifications: Fixed a failure that prevented launching the corresponding app from an ongoing media notification.
• NFC payments: Fixed NFC payment failures derived from null pointer errors.

In addition to these corrections, Beta 1 documented several known issues that persisted in the version. These included failures in simulated touch events via ADB or accessibility services, as well as issues in the Google TV app, which presented a blank screen when reopened and startup failures with error messages. A ClassNotFoundException related to the LazyValue class was also recorded, along with an issue regarding YouTube audio playback in the background after minimizing the application.

Beta 2 Iteration

The second beta iteration continued the refinement process, addressing system stability issues and specific application problems. The highlighted corrections in this phase were:

• Call stability: Fixed freezes and unexpected restarts during calls.
• Google Home app: Fixed intermittent crashes in the application.
• IME behavior: Fixed the behavior of the input method (IME) in STATE_ALWAYS_HIDDEN mode when using the language selector.
• WebView stability: Fixed system UI crashes when interacting with elements within WebViews.
• Class errors: Fixed ClassNotFoundException errors related to LazyValue that had persisted from the previous iteration.

Regarding known issues in Beta 2, failures in simulated touch events with ADB or accessibility services remained documented. Similarly, issues in Google TV persisted, including the blank screen when reopening the app and the startup failure with an error message, as well as the issue of YouTube audio playback in the background after minimizing the application.

Technical Assessment

The security architecture of Android 16 is distinguished by a deep integration of protection mechanisms at both the operating-system level and the user-services level. The inclusion of Advanced Protection Mode represents a significant shift in consolidating multiple layers of defense, although its operability is conditioned by the availability of Google services and the specifications of the device. This limitation means that the security experience is not uniform across the ecosystem, as protection settings and supported functions can depend on the specific hardware and the manufacturer's configuration.

On the memory and system-integrity front, the Memory Tagging Extension (MTE) and intrusion logging strengthen the platform's ability to detect exploits. However, the deployment of intrusion logging is scheduled for later in the year, indicating that this capability will not be immediately available at initial launch. Likewise, local network protection is in a beta-testable phase, suggesting that its final implementation may evolve before full stabilization. Identity verification through auto-confirm unlock with PIN, which relies on biometric verification, adds a layer of access control that complements these background protections.

For developers, the scope of migration to Android 16 is characterized by its compatibility with existing code. The update does not require a major rewrite for most applications, which eases the transition for engineering teams. This continuity allows the migration focus to center on adapting to new APIs and mandatory behavior changes, such as edge-to-edge content management, without the need to restructure the main codebase of existing applications.

The actual degree of feature availability for end users is marked by considerable heterogeneity. Features such as desktop-style windowing require compatible hardware, explicit manufacturer support, and the application in question must support windowed behavior. Similarly, hearing-aid controls depend on compatibility with Bluetooth LE Audio and device support, while live updates require the source app to support the feature, and the manufacturer may modify their visual appearance.

In the realm of interface and personalization, Material 3 Expressive is not available in the stable release, and manufacturer interfaces may add, modify, or delay this experience. The expanded dark theme presents variations, as some apps, screens, and manufacturer builds may not respond identically. Notification management also exhibits this fragmentation: automatic grouping can vary by device maker and software build, the notification organizer was rolled out in stages, and advanced processing notification summaries, added in the December release, are subject to a staged rollout and to device or language availability. This combination of factors positions Android 16 as a version that prioritizes security and developer compatibility, while the end-user experience depends heavily on each manufacturer's specific implementation and the maturity of the associated services.