Starting March 27, 2025, we recommend using android-latest-release instead of aosp-main to build and contribute to AOSP. For more information, see Changes to AOSP.

Android 16 Compatibility Definition

1. Introduction

This document enumerates the requirements that must be met in order for devices to be compatible with Android 16.

The use of "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" is per the IETF standard defined in RFC2119.

As used in this document, a "device implementer" or "implementer" is a person or organization developing a hardware/software solution running Android 16. A "device implementation" or "implementation" is the hardware/software solution so developed.

To be considered compatible with Android 16, device implementations MUST meet the requirements presented in this Compatibility Definition, including any documents incorporated via reference.

Where this definition or the software tests described in section 10 is silent, ambiguous, or incomplete, it is the responsibility of the device implementer to ensure compatibility with existing implementations.

For this reason, the Android Open Source Project is both the reference and preferred implementation of Android. Device implementers are STRONGLY RECOMMENDED to base their implementations to the greatest extent possible on the "upstream" source code available from the Android Open Source Project. While some components can hypothetically be replaced with alternate implementations, it is STRONGLY RECOMMENDED to not follow this practice, as passing the software tests will become substantially more difficult. It is the implementer's responsibility to ensure full behavioral compatibility with the standard Android implementation, including and beyond the Compatibility Test Suite. Finally, note that certain component substitutions and modifications are explicitly forbidden by this document.

Many of the resources linked to in this document are derived directly or indirectly from the Android SDK and will be functionally identical to the information in that SDK's documentation. In any cases where this Compatibility Definition or the Compatibility Test Suite disagrees with the SDK documentation, the SDK documentation is considered authoritative. Any technical details provided in the linked resources throughout this document are considered by inclusion to be part of this Compatibility Definition.

1.1 Document Structure

1.1.1. Requirements by Device Type

Section 2 contains all of the requirements that apply to a specific device type. Each subsection of Section 2 is dedicated to a specific device type.

All the other requirements, that universally apply to any Android device implementations, are listed in the sections after Section 2. These requirements are referenced as "Core Requirements" in this document.

1.1.2. Requirement ID

Requirement ID is assigned for MUST requirements.

The ID is assigned for MUST requirements only.
STRONGLY RECOMMENDED requirements are marked as [SR] but ID is not assigned.
The ID consists of : Device Type ID - Condition ID - Requirement ID (e.g. C-0-1).

Each ID is defined as below:

Device Type ID (see more in 2. Device Types)
- C: Core (Requirements that are applied to all Android device implementations)
- H: Android Handheld device
- T: Android Television device
- A: Android Automotive implementation
- W: Android Watch implementation
- Tab: Android Tablet implementation
Condition ID
- When the requirement is unconditional, this ID is set as 0.
- When the requirement is conditional, 1 is assigned for the 1st condition and the number increments by 1 within the same section and the same device type.
Requirement ID
- This ID starts from 1 and increments by 1 within the same section and the same condition.

1.1.3. Requirement ID in Section 2

The Requirement IDs in Section 2 have two parts. The first corresponds to a section ID as described above. The second part identifies the form factor and the form-factor specific requirement.

section ID that is followed by the Requirement ID described above.

The ID in Section 2 consists of : Section ID / Device Type ID - Condition ID - Requirement ID (e.g. 7.4.3/A-0-1).

2. Device Types

The Android Open Source Project provides a software stack that can be used for a variety of device types and form factors. To support security on devices, the software stack, including any replacement OS or an alternate kernel implementation, is expected to execute in a secure environment as described in section 9 and elsewhere within this CDD. There are a few device types that have a relatively better established application distribution ecosystem.

This section describes those device types, and additional requirements and recommendations applicable for each device type.

All Android device implementations that do not fit into any of the described device types MUST still meet all requirements in the other sections of this Compatibility Definition.

2.1 Device Configurations

For the major differences in hardware configuration by device type, see the device-specific requirements that follow in this section.

2.2. Handheld Requirements

An Android Handheld device refers to an Android device implementation that is typically used by holding it in the hand, such as an mp3 player, phone, or tablet.

Android device implementations are classified as a Handheld if they meet all the following criteria:

Have a power source that provides mobility, such as a battery.
Have a physical diagonal screen size in the range of 4 inches to 8 inches.
Have a touchscreen input interface.

The additional requirements in the rest of this section are specific to Android Handheld device implementations.

2.2.1. Hardware

Handheld device implementations:

[7.1.1.1/H-0-1] MUST have at least one Android-compatible display that measures at least 2.2" on the short edge and 3.4" on the long edge.
[7.1.1.3/H-SR-1] Are STRONGLY RECOMMENDED to provide users an affordance to change the display size (screen density).
[7.1.1.1/H-0-2] MUST support GPU composition of graphic buffers at least as large as the highest resolution of any built-in display.
[7.1.1.1/H-0-3]* MUST map each UI_MODE_NORMAL display made available for third party applications onto an unobstructed physical display area that is at least 2.2" inches on the short edge and 3.4" inches on the long edge.
[7.1.1.3/H-0-1]* MUST set the value of DENSITY_DEVICE_STABLE to be 92% or greater than the actual, physical density of the corresponding display.

If handheld device implementations include support for Vulkan, they:

[7.1.4.2/H-1-1] MUST satisfy the requirements specified by the Android Baseline 2021 profile.

If handheld device implementations declare support of any 64-bit ABI (with or without any 32-bit ABI) and return false for ActivityManager.isLowRamDevice(), they:

[7.1.4.2/H-2-1] MUST support Vulkan 1.1.

If Handheld device implementations claim support for high dynamic range displays through Configuration.isScreenHdr(), they:

[7.1.4.5/H-1-1] MUST advertise support for the EGL_EXT_gl_colorspace_bt2020_pq, EGL_EXT_surface_SMPTE2086_metadata, EGL_EXT_surface_CTA861_3_metadata, VK_EXT_swapchain_colorspace, and VK_EXT_hdr_metadata extensions.

Handheld device implementations:

[7.1.4.6/H-0-1] MUST report whether the device supports the GPU profiling capability via a system property graphics.gpu.profiler.support.

If Handheld device implementations declare support via a system property graphics.gpu.profiler.support, they:

[7.1.4.6/H-1-1] MUST report as output a protobuf trace that complies with the schema for GPU counters and GPU renderstages defined in the Perfetto documentation.
[7.1.4.6/H-1-2] MUST report conformant values for the device's GPU counters following the gpu counter trace packet proto.
[7.1.4.6/H-1-3] MUST report conformant values for the device's GPU RenderStages following the render stage trace packet proto.
[7.1.4.6/H-1-4] MUST report a GPU Frequency tracepoint as specified by the format: power/gpu_frequency.

Handheld device implementations:

[7.1.5/H-0-1] MUST include support for legacy application compatibility mode as implemented by the upstream Android open source code. That is, device implementations MUST NOT alter the triggers or thresholds at which compatibility mode is activated, and MUST NOT alter the behavior of the compatibility mode itself.
[7.2.1/H-0-1] MUST include support for third-party Input Method Editor (IME) applications.
[7.2.3/H-0-2] MUST send both the normal and long press event of the Back function (KEYCODE_BACK) to the foreground application. These events MUST NOT be consumed by the system and CAN be triggered by outside of the Android device (e.g. external hardware keyboard connected to the Android device).
[7.2.3/H-0-3] MUST provide the Home function on all the Android-compatible displays that provide the home screen.
[7.2.3/H-0-4] MUST provide the Back function on all the Android-compatible displays and the Recents function on at least one of the Android-compatible displays.
[7.2.4/H-0-1] MUST support touchscreen input.
[7.2.4/H-SR-1] Are STRONGLY RECOMMENDED to launch the user-selected assist app, in other words the app that implements VoiceInteractionService, or an activity handling the ACTION_ASSIST on long-press of KEYCODE_MEDIA_PLAY_PAUSE or KEYCODE_HEADSETHOOK if the foreground activity does not handle those long-press events.
[7.3.1/H-SR-1] Are STRONGLY RECOMMENDED to include a 3-axis accelerometer.

If Handheld device implementations include a 3-axis accelerometer, they:

[7.3.1/H-1-1] MUST be able to report events up to a frequency of at least 100 Hz.

If Handheld device implementations include a GPS/GNSS receiver and report the capability to applications through the android.hardware.location.gps feature flag, they:

[7.3.3/H-2-1] MUST report GNSS measurements, as soon as they are found, even if a location calculated from GPS/GNSS is not yet reported.
[7.3.3/H-2-2] MUST report GNSS pseudoranges and pseudorange rates, that, in open-sky conditions after determining the location, while stationary or moving with less than 0.2 meter per second squared of acceleration, are sufficient to calculate position within 20 meters, and speed within 0.2 meters per second, at least 95% of the time.

If Handheld device implementations include a 3-axis gyroscope, they:

[7.3.4/H-3-1] MUST be able to report events up to a frequency of at least 100 Hz.
[7.3.4/H-3-2] MUST be capable of measuring orientation changes up to 1000 degrees per second.

Handheld device implementations that can make a voice call and indicate any value other than PHONE_TYPE_NONE in getPhoneType:

[7.3.8/H] SHOULD include a proximity sensor.

Handheld device implementations:

[7.3.11/H-SR-1] Are STRONGLY RECOMMENDED to support pose sensor with 6 degrees of freedom.

Handheld device implementations that include support for Bluetooth LE:

[7.4.3/H-SR-1] Are STRONGLY RECOMMENDED to support Bluetooth LE Data Packet Length Extension.

Note: This requirement [7.4.3/H-SR-1] will become MUST in a future Android release.

If device implementations include support for 802.11 (Wi-Fi) they:

[7.4.2.4/H-1-1] MUST include support for Wi-Fi Passpoint.

If devices support Wi-Fi Neighbor Awareness Networking (NAN) protocol by declaring PackageManager.FEATURE_WIFI_AWARE and Wi-Fi Location (Wi-Fi Round Trip Time — RTT) by declaring PackageManager.FEATURE_WIFI_RTT, then they:

[7.4.2.5/H-1-1] MUST report the range accurately to within +/-1 meter at 160 MHz bandwidth at the 68th percentile (as calculated with the Cumulative Distribution Function), +/-2 meters at 80 MHz bandwidth at the 68th percentile, +/-4 meters at 40 MHz bandwidth at the 68th percentile, and +/-8 meters at 20 MHz bandwidth at the 68th percentile at distances of 10 cm, 1 m, 3 m, and 5 m, as observed via the WifiRttManager#startRanging Android API.
[7.4.2.5/H-SR-1] Are STRONGLY RECOMMENDED to report the range accurately to within +/-1 meter at 160 MHz bandwidth at the 90th percentile (as calculated with the Cumulative Distribution Function), +/-2 meters at 80 MHz bandwidth at the 90th percentile, +/-4 meters at 40 MHz bandwidth at the 90th percentile, and +/-8 meters at 20 MHz bandwidth at the 90th percentile at distances of 10 cm, as observed via the WifiRttManager#startRanging Android API.

It is STRONGLY RECOMMENDED to follow the measurement setup steps specified in Presence Calibration.

If Handheld device implementations declare FEATURE_BLUETOOTH_LE, they:

[7.4.3/H-1-3] MUST measure and compensate for Rx offset to ensure the median BLE RSSI is -50dBm +/-15 dB at 1m distance from a reference device transmitting at ADVERTISE_TX_POWER_HIGH.
[7.4.3/H-1-4] MUST measure and compensate for Tx offset to ensure the median BLE RSSI is -50dBm +/-15 dB when scanning from a reference device positioned at 1m distance and transmitting at ADVERTISE_TX_POWER_HIGH.

If Handheld device implementations include a logical camera device that lists capabilities using CameraMetadata.REQUEST_AVAILABLE_CAPABILITIES_LOGICAL_MULTI_CAMERA, they:

[7.5.4/H-1-1] MUST have normal field of view (FOV) by default and it MUST be between 50 and degrees.

Handheld device implementations:

[7.6.1/H-0-1] MUST have at least 4 GB of non-volatile storage available for application private data (a.k.a. "/data" partition).
[7.6.1/H-0-2] MUST return "true" for ActivityManager.isLowRamDevice() when there is less than 1GB of memory available to the kernel and userspace.

If Handheld device implementations declare support of only a 32-bit ABI:

[7.6.1/H-1-1] The memory available to the kernel and userspace MUST be at least 416MB if the default display uses framebuffer resolutions up to qHD (e.g. FWVGA).
[7.6.1/H-2-1] The memory available to the kernel and userspace MUST be at least 592MB if the default display uses framebuffer resolutions up to HD+ (e.g. HD, WSVGA).
[7.6.1/H-3-1] The memory available to the kernel and userspace MUST be at least 896MB if the default display uses framebuffer resolutions up to FHD (e.g. WSXGA+).
[7.6.1/H-4-1] The memory available to the kernel and userspace MUST be at least 1344MB if the default display uses framebuffer resolutions up to QHD (e.g. QWXGA).

If Handheld device implementations declare support of any 64-bit ABI (with or without any 32-bit ABI):

[7.6.1/H-5-1] The memory available to the kernel and userspace MUST be at least 816MB if the default display uses framebuffer resolutions up to qHD (e.g. FWVGA).
[7.6.1/H-6-1] The memory available to the kernel and userspace MUST be at least 944MB if the default display uses framebuffer resolutions up to HD+ (e.g. HD, WSVGA).
[7.6.1/H-7-1] The memory available to the kernel and userspace MUST be at least 1280MB if the default display uses framebuffer resolutions up to FHD (e.g. WSXGA+).
[7.6.1/H-8-1] The memory available to the kernel and userspace MUST be at least 1824MB if the default display uses framebuffer resolutions up to QHD (e.g. QWXGA).

Note that the "memory available to the kernel and userspace" above refers to the memory space provided in addition to any memory already dedicated to hardware components such as radio, video, and so on that are not under the kernel's control on device implementations.

If Handheld device implementations include less than or equal to 1GB of memory available to the kernel and userspace, they:

[7.6.1/H-9-1] MUST declare the feature flag android.hardware.ram.low.
[7.6.1/H-9-2] MUST have at least 1.1 GB of non-volatile storage for application private data (a.k.a. "/data" partition).

If Handheld device implementations include more than 1GB of memory available to the kernel and userspace, they:

[7.6.1/H-10-1] MUST have at least 4GB of non-volatile storage available for application private data (a.k.a. "/data" partition).
SHOULD declare the feature flag android.hardware.ram.normal.

If Handheld device implementations include greater than or equal to 2GB and less than 4GB of memory available to the kernel and userspace, they:

[7.6.1/H-SR-1] Are STRONGLY RECOMMENDED to support only 32-bit userspace (both apps and system code)

If Handheld device implementations include less than 2GB of memory available to the kernel and userspace, they:

[7.6.1/H-1-1] MUST only support a single ABI (either 64-bit only or 32-bit only).

Handheld device implementations:

[7.6.2/H-0-1] MUST NOT provide an application shared storage smaller than 1 GiB.
[7.7.1/H] SHOULD include a USB port supporting peripheral mode.

If handheld device implementations include a USB port with a controller operating in peripheral mode, they:

[7.7.1/H-1-1] MUST implement the Android Open Accessory (AOA) API.

If Handheld device implementations include a USB port supporting host mode, they:

[7.7.2/H-1-1] MUST implement the USB audio class as documented in the Android SDK documentation.

Handheld device implementations:

[7.8.1/H-0-1] MUST include a microphone.
[7.8.2/H-0-1] MUST have an audio output and declare android.hardware.audio.output.

If Handheld device implementations are capable of meeting all the performance requirements for supporting VR mode and include support for it, they:

[7.9.1/H-1-1] MUST declare the android.hardware.vr.high_performance feature flag.
[7.9.1/H-1-2] MUST include an application implementing android.service.vr.VrListenerService that can be enabled by VR applications via android.app.Activity#setVrModeEnabled.

If Handheld device implementations include one or more USB-C port(s) in host mode and implement (USB audio class), in addition to requirements in section 7.7.2, they:

[7.8.2.2/H-1-1] MUST provide the following software mapping of HID codes:

Function	Mappings	Context	Behavior
A	HID usage page: 0x0C HID usage: 0x0CD Kernel key: `KEY_PLAYPAUSE` Android key: `KEYCODE_MEDIA_PLAY_PAUSE`	Media playback	Input: Short press Output: Play or pause
		Media playback	Input: Long press Output: Launch voice command Sends: `android.speech.action.VOICE_SEARCH_HANDS_FREE` if the device is locked or its screen is off. Sends `android.speech.RecognizerIntent.ACTION_WEB_SEARCH` otherwise
		Incoming call	Input: Short press Output: Accept call
		Incoming call	Input: Long press Output: Reject call
		Ongoing call	Input: Short press Output: End call
		Ongoing call	Input: Long press Output: Mute or unmute microphone
B	HID usage page: 0x0C HID usage: 0x0E9 Kernel key: `KEY_VOLUMEUP` Android key: `VOLUME_UP`	Media playback, Ongoing call	Input: Short or long press Output: Increases the system or headset volume
C	HID usage page: 0x0C HID usage: 0x0EA Kernel key: `KEY_VOLUMEDOWN` Android key: `VOLUME_DOWN`	Media playback, Ongoing call	Input: Short or long press Output: Decreases the system or headset volume
D	HID usage page: 0x0C HID usage: 0x0CF Kernel key: `KEY_VOICECOMMAND` Android key: `KEYCODE_VOICE_ASSIST`	All. Can be triggered in any instance.	Input: Short or long press Output: Launch voice command

[7.8.2.2/H-1-2] MUST trigger ACTION_HEADSET_PLUG upon a plug insert, but only after the USB audio interfaces and endpoints have been properly enumerated in order to identify the type of terminal connected.

When the USB audio terminal types 0x0302 is detected, they:

[7.8.2.2/H-2-1] MUST broadcast Intent ACTION_HEADSET_PLUG with "microphone" extra set to 0.

When the USB audio terminal types 0x0402 is detected, they:

[7.8.2.2/H-3-1] MUST broadcast Intent ACTION_HEADSET_PLUG with "microphone" extra set to 1.

When API AudioManager.getDevices() is called while the USB peripheral is connected they:

[7.8.2.2/H-4-1] MUST list a device of type AudioDeviceInfo.TYPE_USB_HEADSET and role isSink() if the USB audio terminal type field is 0x0302.
[7.8.2.2/H-4-2] MUST list a device of type AudioDeviceInfo.TYPE_USB_HEADSET and role isSink() if the USB audio terminal type field is 0x0402.
[7.8.2.2/H-4-3] MUST list a device of type AudioDeviceInfo.TYPE_USB_HEADSET and role isSource() if the USB audio terminal type field is 0x0402.
[7.8.2.2/H-4-4] MUST list a device of type AudioDeviceInfo.TYPE_USB_DEVICE and role isSink() if the USB audio terminal type field is 0x603.
[7.8.2.2/H-4-5] MUST list a device of type AudioDeviceInfo.TYPE_USB_DEVICE and role isSource() if the USB audio terminal type field is 0x604.
[7.8.2.2/H-4-6] MUST list a device of type AudioDeviceInfo.TYPE_USB_DEVICE and role isSink() if the USB audio terminal type field is 0x400.
[7.8.2.2/H-4-7] MUST list a device of type AudioDeviceInfo.TYPE_USB_DEVICE and role isSource() if the USB audio terminal type field is 0x400.
[7.8.2.2/H-SR-1] Are STRONGLY RECOMMENDED upon connection of a USB-C audio peripheral, to perform enumeration of USB descriptors, identify terminal types and broadcast Intent ACTION_HEADSET_PLUG in less than 1000 milliseconds.

For Handheld device implementations that declare android.hardware.audio.output and android.hardware.microphone, see the RTL and TTL requirements in section 5.6.

A linear resonant actuator (LRA) is a single-mass spring system which has a dominant resonant frequency where the mass translates in the direction of desired motion.

If Handheld device implementations include at least one general purpose 7.10 linear resonant actuator, they:

[7.10/H] SHOULD position the placement of the actuator near the location where the device is typically held or touched by hands.
[7.10/H] SHOULD move the haptic actuator in the X-axis (left-right) of the device's natural orientation.

If Handheld device implementations have a general purpose haptic actuator which is X-axis linear resonant actuator (LRA), they:

[7.10/H] SHOULD have the resonant frequency of the X-axis LRA be under 200 Hz.

If handheld device implementations follow haptic constants mapping, they:

[7.10/H]* SHOULD verify the implementation status by running android.os.Vibrator.areAllEffectsSupported() and android.os.Vibrator.arePrimitivesSupported() APIs.
[7.10/H]* SHOULD perform a quality assessment for haptic constants.
[7.10/H]* SHOULD verify and update if needed the fallback configuration for unsupported primitives as described in the implementation guidance for constants.

2.2.2. Multimedia

Handheld device implementations MUST support the following audio encoding and decoding formats and make them available to third-party applications:

[5.1/H-0-1] AMR-NB
[5.1/H-0-2] AMR-WB
[5.1/H-0-3] MPEG-4 AAC Profile (AAC LC)
[5.1/H-0-4] MPEG-4 HE AAC Profile (AAC+)
[5.1/H-0-5] AAC ELD (enhanced low delay AAC)

Handheld device implementations MUST support the following video encoding formats and make them available to third-party applications:

[5.2/H-0-1] H.264 AVC
[5.2/H-0-2] VP8
[5.2/H-0-3] AV1

Handheld device implementations MUST support the following video decoding formats and make them available to third-party applications:

[5.3/H-0-1] H.264 AVC
[5.3/H-0-2] H.265 HEVC
[5.3/H-0-3] MPEG-4 SP
[5.3/H-0-4] VP8
[5.3/H-0-5] VP9
[5.3/H-0-6] AV1

2.2.3. Software

Handheld device implementations:

[3.2.3.1/H-0-1] MUST have an application that handles the ACTION_GET_CONTENT, ACTION_OPEN_DOCUMENT, ACTION_OPEN_DOCUMENT_TREE, and ACTION_CREATE_DOCUMENT intents as described in the SDK documents, and provide the user affordance to access the document provider data by using DocumentsProvider API.
[3.2.3.1/H-0-2]* MUST preload one or more applications or service components with an intent handler, for all the public intent filter patterns defined by the following application intents listed here.
[3.2.3.1/H-SR-1] Are STRONGLY RECOMMENDED to preload an email application which can handle ACTION_SENDTO or ACTION_SEND or ACTION_SEND_MULTIPLE intents to send an email.
[3.4.1/H-0-1] MUST provide a complete implementation of the android.webkit.Webview API.
[3.4.2/H-0-1] MUST include a standalone Browser application for general user web browsing.
[3.8.1/H-SR-1] Are STRONGLY RECOMMENDED to implement a default launcher that supports in-app pinning of shortcuts, widgets and widgetFeatures.
[3.8.1/H-SR-2] Are STRONGLY RECOMMENDED to implement a default launcher that provides quick access to the additional shortcuts provided by third-party apps through the ShortcutManager API.
[3.8.1/H-SR-3] Are STRONGLY RECOMMENDED to include a default launcher app that shows badges for the app icons.
[3.8.2/H-SR-1] Are STRONGLY RECOMMENDED to support third-party app widgets.
[3.8.3/H-0-1] MUST allow third-party apps to notify users of notable events through the Notification and NotificationManager API classes.
[3.8.3/H-0-2] MUST support rich notifications.
[3.8.3/H-0-3] MUST support heads-up notifications.
[3.8.3/H-0-4] MUST include a notification shade, providing the user the ability to directly control (e.g. reply, snooze, dismiss, block) the notifications through user affordance such as action buttons or the control panel as implemented in the AOSP.
[3.8.3/H-0-5] MUST display the choices provided through RemoteInput.Builder setChoices() in the notification shade.
[3.8.3/H-SR-1] Are STRONGLY RECOMMENDED to display the first choice provided through RemoteInput.Builder setChoices() in the notification shade without additional user interaction.
[3.8.3/H-SR-2] Are STRONGLY RECOMMENDED to display all the choices provided through RemoteInput.Builder setChoices() in the notification shade when the user expands all notifications in the notification shade.
[3.8.3.1/H-SR-1] Are STRONGLY RECOMMENDED to display actions for which Notification.Action.Builder.setContextual is set as true in-line with the replies displayed by Notification.Remoteinput.Builder.setChoices.
[3.8.4/H-SR-1] Are STRONGLY RECOMMENDED to implement an assistant on the device to handle the Assist action.

If Handheld device implementations support MediaStyle notifications they:

[3.8.3.1/H-SR-2] Are STRONGLY RECOMMENDED to provide a user affordance (for example, output switcher) accessed from system UI that allows users to switch among appropriate available media routes (for example, Bluetooth devices and routes provided to MediaRouter2Manager) when an app posts a MediaStyle notification with a MediaSession token.

If device implementations including the recents function navigation key as detailed in section 7.2.3 alter the interface, they:

[3.8.3/H-1-1] MUST implement the screen pinning behavior and provide the user with a settings menu to toggle the feature.

If Handheld device implementations support Assist action, they:

[3.8.4/H-SR-2] Are STRONGLY RECOMMENDED to use long press on HOME key as the designated interaction to launch the assist app as described in section 7.2.3. MUST launch the user-selected assist app, in other words the app that implements VoiceInteractionService, or an activity handling the ACTION_ASSIST intent.

If Handheld device implementations support conversation notifications and group them into a separate section from alerting and silent non-conversation notifications, they:

[3.8.4/H-1-1]* MUST display conversation notifications ahead of non conversation notifications with the exception of ongoing foreground service notifications and importance:high notifications.

If Android Handheld device implementations support a lock screen, they:

[3.8.10/H-1-1] MUST display the Lock screen Notifications including the Media Notification Template.

If Handheld device implementations support a secure lock screen, they:

[3.9/H-1-1] MUST implement the full range of device administration policies defined in the Android SDK documentation.

If Handheld device implementations include support for ControlsProviderService and Control APIs and allow third-party applications to publish device controls, then they:

[3.8.16/H-1-1] MUST declare the feature flag android.software.controls and set it to true.
[3.8.16/H-1-2] MUST provide a user affordance with the ability to add, edit, select, and operate the user's favorite device controls from the controls registered by the third-party applications through the ControlsProviderService and the Control APIs.
[3.8.16/H-1-3] MUST provide access to this user affordance within three interactions from a default Launcher.
[3.8.16/H-1-4] MUST accurately render in this user affordance the name and icon of each third-party app that provides controls via the ControlsProviderService API as well as any specified fields provided by the Control APIs.
[3.8.16/H-1-5] MUST provide a user affordance to opt out of app designated auth-trivial device controls from the controls registered by the third-party applications through the ControlsProviderService and the Control Control.isAuthRequired API.
[3.8.16/H-1-6] Device implementations MUST accurately render the user affordance as follows:
- If the device has set config_supportsMultiWindow=true and the app declares the metadata META_DATA_PANEL_ACTIVITY in the ControlsProviderService declaration, including the ComponentName of a valid activity (as defined by the API), then the app MUST embed said activity in this user affordance.
- If the app does not declare metadata META_DATA_PANEL_ACTIVITY, then it MUST render the specified fields as provided by the ControlsProviderService API as well as any specified fields provided by the Control APIs.
[3.8.16/H-1-7] If the app declares the metadata META_DATA_PANEL_ACTIVITY, it MUST pass the value of the setting defined in [3.8.16/H-1-5] using EXTRA_LOCKSCREEN_ALLOW_TRIVIAL_CONTROLS when launching the embedded activity.

Conversely, If Handheld device implementations do not implement such controls, they:

[3.8.16/H-2-1] MUST report null for the ControlsProviderService and the Control APIs.
[3.8.16/H-2-2] MUST declare the feature flag android.software.controls and set it to false.

If handheld device implementations are not running in lock task mode, when content is copied to the clipboard they:

[3.8.17/H-1-1] MUST present a confirmation to the user that data has been copied to the clipboard (e.g., a thumbnail or alert of "Content copied."). Additionally, include here an indication if clipboard data will be synced across devices.

Handheld device implementations:

[3.10/H-0-1] MUST support third-party accessibility services.
[3.10/H-SR-1] Are STRONGLY RECOMMENDED to preload accessibility services on the device comparable with or exceeding functionality of the Switch Access and TalkBack (for languages supported by the preinstalled Text-to-speech engine) accessibility services as provided in the talkback open source project.
[3.11/H-0-1] MUST support installation of third-party TTS engines.
[3.11/H-SR-1] Are STRONGLY RECOMMENDED to include a TTS engine supporting the languages available on the device.
[3.13/H-SR-1] Are STRONGLY RECOMMENDED to include a Quick Settings UI component.

If Android handheld device implementations declare FEATURE_BLUETOOTH or FEATURE_WIFI support, they:

[3.16/H-1-1] MUST support the companion device pairing feature.

If the navigation function is provided as an on-screen, gesture-based action:

[7.2.3/H] The gesture recognition zone for the Home function SHOULD be no higher than 32 dp in height from the bottom of the screen.

If Handheld device implementations provide a navigation function as a gesture from anywhere on the left and right edges of the screen:

[7.2.3/H-0-1] The navigation function's gesture area MUST be less than 40 dp in width on each side. The gesture area SHOULD be 24 dp in width by default.

If Handheld device implementations support a secure lock screen and have greater than or equal to 2GB of memory available to the kernel and userspace, they:

[3.9/H-1-2] MUST declare the support of managed profiles via the android.software.managed_users feature flag.

If Android handheld device implementations declare the support for camera via android.hardware.camera.any they:

[7.5.4/H-1-1] MUST honor the android.media.action.STILL_IMAGE_CAMERA and android.media.action.STILL_IMAGE_CAMERA_SECURE intent and launch the camera in still image mode as described in the SDK.
[7.5.4/H-1-2] MUST honor the android.media.action.VIDEO_CAMERA intent to launch the camera in video mode as described in the SDK.

If device implementation's settings application implements a split functionality, using activity embedding, then they:

[3.2.3.1/ H-1-1] MUST have an activity that handles the Settings#ACTION_SETTINGS_EMBED_DEEP_LINK_ACTIVITY intent when split functionality is on. The Activity MUST be protected by android.permission.LAUNCH_MULTI_PANE_SETTINGS_DEEP_LINK and it MUST start the activity of the Intent parsed from Settings#EXTRA_SETTINGS_EMBEDDED_DEEP_LINK_INTENT_URI.

If device implementations allow users to place calls of any sort, they

[7.4.1.2/H-0-1] MUST declare the feature flag android.software.telecom.
[7.4.1.2/H-0-2] MUST implement the telecom framework.

2.2.4. Performance and Power

[8.1/H-0-1] Consistent frame latency. Inconsistent frame latency or a delay to render frames MUST NOT happen more often than 5 frames in a second, and SHOULD be below 1 frames in a second.
[8.1/H-0-2] User interface latency. Device implementations MUST ensure low latency user experience by scrolling a list of 10K list entries as defined by the Android Compatibility Test Suite (CTS) in less than 36 secs.
[8.1/H-0-3] Task switching. When multiple applications have been launched, re-launching an already-running application after it has been launched MUST take less than 1 second.

Handheld device implementations:

[8.2/H-0-1] MUST ensure a sequential write performance of at least 5 MB/s.
[8.2/H-0-2] MUST ensure a random write performance of at least 0.5 MB/s.
[8.2/H-0-3] MUST ensure a sequential read performance of at least 15 MB/s.
[8.2/H-0-4] MUST ensure a random read performance of at least 3.5 MB/s.

If Handheld device implementations include features to improve device power management that are included in AOSP or extend the features that are included in AOSP, they:

[8.3/H-1-1] MUST provide user affordance to enable and disable the battery saver feature.
[8.3/H-1-2] MUST provide user affordance to display all apps that are exempted from App Standby and Doze power-saving modes.

Handheld device implementations:

[8.4/H-0-1] MUST provide a per-component power profile that defines the current consumption value for each hardware component and the approximate battery drain caused by the components over time as documented in the Android Open Source Project site.
[8.4/H-0-2] MUST report all power consumption values in milliampere hours (mAh).
[8.4/H-0-3] MUST report CPU power consumption per each process's UID. The Android Open Source Project meets the requirement through the uid_cputime kernel module implementation.
[8.4/H-0-4] MUST make this power usage available via the adb shell dumpsys batterystats shell command to the app developer.
[8.4/H] SHOULD be attributed to the hardware component itself if unable to attribute hardware component power usage to an application.

If Handheld device implementations include a screen or video output, they:

[8.4/H-1-1] MUST honor the android.intent.action.POWER_USAGE_SUMMARY intent and display a settings menu that shows this power usage.

Handheld device implementations:

[8.5/H-0-1] MUST provide a user affordance to see all apps with either active foreground services or user-initiated jobs, including the duration of each of these services since it started as described in the SDK document.
[8.5/H-0-2]MUST provide a user affordance to stop an app that is running a foreground service or a user-initiated job.

2.2.5. Security Model

Handheld device implementations:

[9/H-0-1] MUST declare the android.hardware.security.model.compatible feature.
[9.1/H-0-1] MUST allow third-party apps to access the usage statistics via the android.permission.PACKAGE_USAGE_STATS permission and provide a user-accessible mechanism to grant or revoke access to such apps in response to the android.settings.ACTION_USAGE_ACCESS_SETTINGS intent.

Device implementations MUST declare support for android.software.credentials and:

[9/H-0-2] MUST honor the android.settings.CREDENTIAL_PROVIDER intent to allow selection of a preferred provider for the Credential Manager. This provider will be enabled for Autofill and will also be the default location to save new credentials entered through the Credential Manager.
[9/H-0-3] MUST support at least 2 concurrent credential providers and provide a user affordance in the Setting app to enable or disable providers.

If device implementations declare support for android.hardware.telephony, they:

[9.5/H-1-1] MUST NOT set UserManager.isHeadlessSystemUserMode to true.

Handheld device implementations:

[9.11/H-0-2] MUST back up the keystore implementation with an isolated execution environment.
[9.11/H-0-3] MUST have implementations of RSA, AES, ECDSA, and HMAC cryptographic algorithms and MD5, SHA-1, and SHA-2 family hash functions to properly support the Android Keystore system's supported algorithms in an area that is securely isolated from the code running on the kernel and above. Secure isolation MUST block all potential mechanisms by which kernel or userspace code might access the internal state of the isolated environment, including DMA. The upstream Android Open Source Project (AOSP) meets this requirement by using the Trusty implementation, but another ARM TrustZone-based solution or a third-party reviewed secure implementation of a proper hypervisor-based isolation are alternative options.
[9.11/H-0-4] MUST perform the lock screen authentication in the isolated execution environment and only when successful, allow the authentication-bound keys to be used. Lock screen credentials MUST be stored in a way that allows only the isolated execution environment to perform lock screen authentication. The upstream Android Open Source Project provides the Gatekeeper Hardware Abstraction Layer (HAL) and Trusty, which can be used to satisfy this requirement.
[9.11/H-0-5] MUST support key attestation where the attestation signing key is protected by secure hardware and signing is performed in secure hardware. The attestation signing keys MUST be prevented from being used as permanent device identifiers.

Note: To meet this requirement, you must share the same attestation key for a given SKU unless at least 100,000 units of that SKU are produced. If more than 100,000 units of that SKU are produced, a different key MAY be used for each group of 100,000 units after that. Alternatively, the Remote Key Provisioning solution may be used to provision short-lived attestation keys to the device.

Note that if a device implementation is already launched on an earlier Android version, such a device is exempted from the requirement to have a keystore backed by an isolated execution environment and support the key attestation, unless it declares the android.hardware.fingerprint feature which requires a keystore backed by an isolated execution environment.

When Handheld device implementations support a secure lock screen, they:

[9.11/H-1-1] MUST allow the user to choose the shortest sleep timeout, that is a transition time from the unlocked to the locked state, as 15 seconds or less.
[9.11/H-1-2] MUST provide user affordance to hide notifications and disable all forms of authentication except for the primary authentication described in 9.11.1 Secure Lock Screen. The AOSP meets the requirement as lockdown mode.

If device implementations have a secure lock screen and include one or more trust agent, which implements the TrustAgentService System API, they:

[9.11.1/H-1-1] MUST challenge the user for one of the recommended primary authentication methods (eg: PIN, pattern, password) more frequently than once every 72 hours.

If Handheld device implementations include multiple users and do not declare the android.hardware.telephony feature flag, they:

[9.5/H-2-1] MUST support restricted profiles, a feature that allows device owners to manage additional users and their capabilities on the device. With restricted profiles, device owners can quickly set up separate environments for additional users to work in, with the ability to manage finer-grained restrictions in the apps that are available in those environments.

If Handheld device implementations include multiple users and declare the android.hardware.telephony feature flag, they:

[9.5/H-3-1] MUST NOT support restricted profiles but MUST align with the AOSP implementation of controls to enable /disable other users from accessing the voice calls and SMS.

If Handheld device implementations set UserManager.isHeadlessSystemUserMode to true, they

[9.5/H-4-1] MUST NOT include support for eUICCs, nor for eSIMs with calling capability.

[9.5/H-4-2] MUST NOT declare support for android.hardware.telephony.

Restricted settings

Restricted Settings provides a user with visible warnings and solicits user confirmation in order to grant permissions for each application that is either:

Being installed after being downloaded through an application (for example, a messaging application or a browser) other than an "app store" application identified by PackageManager as PACKAGE_DOWNLOADED_FILE.
Being installed from a local file (for example, the application was sideloaded) identified by PackageManager as PACKAGE_SOURCE_LOCAL_FILE.

For any of the Enforced Permissions and their associated identifiers listed in [9.8/H-0-5] below.

Such applications are labeled "Covered Applications" for the requirements listed in this section.

Device implementations:

[9.8/H-0-1] MUST implement Restricted Settings as outlined above for the following:
- Special permissions
  - Accessibility (AppOpsManager.OPSTR_BIND_ACCESSIBILITY_SERVICE)
  - Notification listener (AppOpsManager.OPSTR_ACCESS_NOTIFICATIONS)
  - Device admin apps (Manifest.permission.BIND_DEVICE_ADMIN)
  - Display over other apps (AppOpsManager.OPSTR_SYSTEM_ALERT_WINDOW)
  - Usage access (AppOpsManager.OPSTR_GET_USAGE_STATS)
- Roles (Default apps)
  - Dialer (RoleManager.ROLE_DIALER)
  - SMS (RoleManager.ROLE_SMS)
- Runtime permissions
  - SMS runtime (Manifest.permission_group.SMS)
[9.8/H-0-2] MUST enable Restricted Settings as the default and are STRONGLY RECOMMENDED to not have any user affordance which allows a user to disable Restricted Settings for all applications.
[9.8/H-0-3] MUST ensure user confirmation is obtained for each Covered Application before any of the Enforced Permissions can be granted.
[9.8/H-0-4] MUST only allow user confirmation to enable restricted settings to be obtained from the Covered Application's AppInfo page, using the EnhancedConfirmationManager API.
[9.8/H-0-5] Are STRONGLY RECOMMENDED to integrate with and call EnhancedConfirmationManager for all special permissions, to dynamically determine if they are a restricted setting.
- Alarms and reminders: AppOpsManager.OPSTR_SCHEDULE_EXACT_ALARM
- All file access: AppOpsManager.OPSTR_MANAGE_EXTERNAL_STORAGE
- Display over other apps: AppOpsManager.OPSTR_SYSTEM_ALERT_WINDOW
- Install unknown apps: AppOpsManager.OPSTR_REQUEST_INSTALL_PACKAGES
- Manage media: AppOpsManager.OPSTR_MANAGE_MEDIA
- Modify system settings: AppOpsManager.OPSTR_WRITE_SETTINGS
- Picture-in-picture: AppOpsManager.OPSTR_PICTURE_IN_PICTURE
- Turn screen on: AppOpsManager.OPSTR_TURN_SCREEN_ON
- Full-screen notifications: AppOpsManager.OPSTR_USE_FULL_SCREEN_INTENT
- Wi-Fi control: AppOpsManager.OPSTR_CHANGE_WIFI_STATE
- Accessibility: AppOpsManager.OPSTR_BIND_ACCESSIBILITY_SERVICE
- Notification listener: AppOpsManager.OPSTR_ACCESS_NOTIFICATIONS
- Usage access: AppOpsManager.OPSTR_GET_USAGE_STATS
- Device admin: Manifest.permission.BIND_DEVICE_ADMIN
- Do not disturb: Manifest.permission.MANAGE_NOTIFICATIONS

Android, through the System API VoiceInteractionService supports a mechanism for secure always-on hotword detection without mic access indication and always-on query detection, without mic or camera access indication.

If Handheld device implementations support the System API HotwordDetectionService or another mechanism for hotword detection without mic access indication, they:

[9.8/H-1-1] MUST make sure the hotword detection service can only transmit data to the System, ContentCaptureService, or on-device speech recognition service created by SpeechRecognizer#createOnDeviceSpeechRecognizer().
[9.8/H-1-2] MUST make sure the hotword detection service can only transmit mic audio data or data derived from it to the system server through HotwordDetectionService API, or to ContentCaptureService through ContentCaptureManager API.
[9.8/H-1-3] MUST NOT supply mic audio that is longer than 30 seconds for an individual hardware-triggered request to the hotword detection service.
[9.8/H-1-4] MUST NOT supply buffered mic audio older than 8 seconds for an individual request to the hotword detection service.
[9.8/H-1-5] MUST NOT supply buffered mic audio older than 30 seconds to the voice interaction service or similar entity.
[9.8/H-1-6] MUST NOT allow more than 100 bytes of data (excluding audio streams) to be transmitted out of the hotword detection service on each successful hotword result.
[9.8/H-1-7] MUST NOT allow more than 5 bits of data to be transmitted out of the hotword detection service on each negative hotword result.
[9.8/H-1-8] MUST only allow transmission of data out of the hotword detection service on a hotword validation request from the system server.
[9.8/H-1-9] MUST NOT allow a user-installable application to provide the hotword detection service.
[9.8/H-1-10] MUST NOT surface in the UI quantitative data about mic usage by the hotword detection service.
[9.8/H-1-11] MUST log the number of bytes included in every transmission from the hotword detection service to allow inspectability for security researchers.
[9.8/H-1-12] MUST support a debug mode that logs raw contents of every transmission from the hotword detection service to allow inspectability for security researchers.
[9.8/H-1-14] MUST display the microphone indicator, as described in section 9.8.2, when a successful hotword result is transmitted to the voice interaction service or similar entity.
[9.8/H-1-15] MUST ensure that audio streams provided on successful hotword results are transmitted one-way from the hotword detection service to the voice interaction service.
[9.8/H-SR-1] Are STRONGLY RECOMMENDED to notify users before setting an application as the provider of the hotword detection service.
[9.8/H-SR-2] Are STRONGLY RECOMMENDED to disallow the transmission of unstructured data out of the hotword detection service.
[9.8/H-SR-3] Are STRONGLY RECOMMENDED to restart the process hosting the hotword detection service at least once every hour or every 30 hardware-trigger events, whichever comes first.

If device implementations include an application that uses the System API HotwordDetectionService, or similar mechanism for hotword detection without mic usage indication, the application:

[9.8/H-2-1] MUST provide explicit notice to the user for each hotword phrase supported.
[9.8/H-2-2] MUST NOT preserve raw audio data, or data derived from it, through the hotword detection service.
[9.8/H-2-3] MUST NOT transmit from the hotword detection service, audio data, data that can be used to reconstruct (wholly or partially) the audio, or audio contents unrelated to the hotword itself, except to the ContentCaptureService or on-device speech recognition service.

If Handheld device implementations support the System API VisualQueryDetectionService or another mechanism for query detection without mic and/or camera access indication, they:

[9.8/H-3-1] MUST make sure the query detection service can only transmit data to the System, or ContentCaptureService, or on-device speech recognition service (created by SpeechRecognizer#createOnDeviceSpeechRecognizer()).
[9.8/H-3-2] MUST NOT allow any audio or video information to be transmitted out of the VisualQueryDetectionService, except to ContentCaptureService or on-device speech recognition service.
[9.8/H-3-3] MUST display a user notice in System UI when device detects user intent to engage with the Digital Assistant Application (e.g by detecting user presence via camera).
[9.8/H-3-4] MUST display a microphone indicator and display the detected user query in the UI right after the user query is detected.
[9.8/H-3-5] MUST NOT allow a user-installable application to provide the visual query detection service.

If Handheld device implementations declare android.hardware.microphone, they:

[9.8.2/H-4-1] MUST display the microphone indicator when an app is accessing audio data from the microphone, but not when the microphone is only accessed by HotwordDetectionService, SOURCE_HOTWORD, ContentCaptureService or apps holding the roles called out in section 9.1 with CDD identifier [C-4-X].
[9.8.2/H-4-2] MUST display the list of Recent and Active apps using microphone as returned from PermissionManager.getIndicatorAppOpUsageData(), along with any attribution messages associated with them.
[9.8.2/H-4-3] MUST not hide the microphone indicator for system apps that have visible user interfaces or direct user interaction.
[9.8.2/H-4-4] MUST display the list of Recent and Active apps using the microphone as returned from PermissionManager.getIndicatorAppOpUsageData(), along with any attribution messages associated with them.

If Handheld device implementations declare android.hardware.camera.any, they:

[9.8.2/H-5-1] MUST display the camera indicator when an app is accessing live camera data, but not when the camera is only being accessed by app(s) holding the roles called out in section 9.1 with CDD identifier [C-4-X].
[9.8.2/H-5-2] MUST display Recent and Active apps using camera as returned from PermissionManager.getIndicatorAppOpUsageData(), along with any attribution messages associated with them.
[9.8.2/H-5-3] MUST not hide the camera indicator for system apps that have visible user interfaces or direct user interaction.

Verified Boot is a feature that ensures the integrity of the device software. If device implementations support the feature, they:

[9.10/H-1-1] MUST verify all read-only partitions mounted during the Android boot sequence, and the VBMeta digest must include all these verified partitions in its calculation.

2.2.6. Developer Tools and Options Compatibility

Handheld device implementations (* Not applicable for Tablet):

[6.1/H-0-1]* MUST support the shell command cmd testharness.

Handheld device implementations:

Perfetto
- [6.1/H-0-2] MUST expose a /system/bin/perfetto binary to the shell user which cmdline complies with the perfetto documentation.
- [6.1/H-0-3] The perfetto binary MUST accept as input a protobuf config that complies with the schema defined in the perfetto documentation.
- [6.1/H-0-4] The perfetto binary MUST write as output a protobuf trace that complies with the schema defined in the perfetto documentation.
- [6.1/H-0-5] MUST provide, through the perfetto binary, at least the data sources described in the perfetto documentation.
- [6.1/H-0-6] The perfetto traced daemon MUST be enabled by default (system property persist.traced.enable).

2.2.7. Handheld Media Performance Class

See Section 7.11 for the definition of media performance class.

2.2.7.1. Media

If Handheld device implementations return android.os.Build.VERSION_CODES.U for android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS, they:

MUST meet the media requirements listed in Android 14 CDD section 2.2.7.1.

If Handheld device implementations return android.os.Build.VERSION_CODES.V for android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS, they:

[5.1/H-1-1] MUST advertise the maximum number of hardware video decoder sessions that can be run concurrently in any codec combination via the CodecCapabilities.getMaxSupportedInstances() and VideoCapabilities.getSupportedPerformancePoints() methods.
[5.1/H-1-2] MUST support 6 instances of 8-bit (SDR) hardware video decoder sessions (AVC, HEVC, VP9, AV1, or later) in any codec combination running concurrently with 3 sessions at 1080p resolution@30 fps and 3 sessions at 4K resolution@30fps. For all sessions, there MUST NOT be more than 1 frame dropped per second. AV1 codecs are only required to support 1080p resolution, but are still required to support 6 instances at 1080p30fps.
[5.1/H-1-3] MUST advertise the maximum number of hardware video encoder sessions that can be run concurrently in any codec combination via the CodecCapabilities.getMaxSupportedInstances() and VideoCapabilities.getSupportedPerformancePoints() methods.
[5.1/H-1-4] MUST support 6 instances of 8-bit (SDR) hardware video encoder sessions (AVC, HEVC, VP9, AV1, or later) in any codec combination running concurrently with 4 sessions at 1080p resolution@30 fps and 2 sessions at 4K resolution@30fps. For all sessions, there MUST NOT be more than 1 frame dropped per second. AV1 codecs are only required to support 1080p resolution, but are still required to support 6 instances at 1080p30fps.
[5.1/H-1-5] MUST advertise the maximum number of hardware video encoder and decoder sessions that can be run concurrently in any codec combination via the CodecCapabilities.getMaxSupportedInstances() and VideoCapabilities.getSupportedPerformancePoints() methods.
[5.1/H-1-6] MUST support 6 instances of 8-bit (SDR) hardware video decoder and hardware video encoder sessions (AVC, HEVC, VP9, AV1, or later) in any codec combination running concurrently with 3 sessions at 4K@30fps resolution, out of which at most 2 are encoder sessions and 3 sessions at 1080p resolution. For all sessions, there MUST NOT be more than 1 frame dropped per second. AV1 codecs are only required to support 1080p resolution, but are still required to support 6 instances at 1080p30fps.
[5.1/H-1-19] MUST support 3 instances of 10-bit (HDR) hardware video decoder and hardware video encoder sessions (AVC, HEVC, VP9, AV1, or later) in any codec combination running concurrently at 4K@30fps resolution out of which at most 1 is an encoder session, which could be configured in RGBA_1010102 input format through a GL surface. For all sessions, there MUST NOT be more than 1 frame dropped per second. HDR metadata generation by the encoder is not required if encoding from the GL surface. AV1 codec sessions are only required to support 1080p resolution even when this requirement calls for 4K.
[5.1/H-1-7] MUST have a codec initialization latency of 40 ms or less for a 1080p or smaller video encoding session for all hardware video encoders when under load. Load here is defined as a concurrent 1080p to 720p video-only transcoding session using hardware video codecs together with the 1080p audio-video recording initialization. For Dolby vision codec, the codec initialization latency MUST be 50 ms or less.
[5.1/H-1-8] MUST have a codec initialization latency of 30 ms or less for a 128 kbps or lower bitrate audio encoding session for all audio encoders when under load. Load here is defined as a concurrent 1080p to 720p video-only transcoding session using hardware video codecs together with the 1080p audio-video recording initialization.
[5.1/H-1-9] MUST support 2 instances of secure hardware video decoder sessions (AVC, HEVC, VP9, AV1, or later) in any codec combination running concurrently at 1080p resolution@30 fps for both 8-bit (SDR) and 10-bit HDR content. For all sessions, there MUST NOT be more than 1 frame dropped per second.
[5.1/H-1-10] MUST support 3 instances of non-secure hardware video decoder sessions together with 1 instance of secure hardware video decoder session (4 instances total) (AVC, HEVC, VP9, AV1, or later) in any codec combination running concurrently with 3 sessions at 4K resolution@30fps which includes one secure decoder session and 1 nn-secure session at 1080p resolution@30fps where at most 2 sessions can be in 10-bit HDR. For all sessions, there MUST NOT be more than 1 frame dropped per second. AV1 codec sessions are only required to support 1080p resolution even when this requirement calls for 4K.
[5.1/H-1-11] MUST support a secure decoder for every hardware AVC, HEVC, VP9, or AV1 decoder on the device.
[5.1/H-1-12] MUST have a codec initialization latency of 40 ms or less for a 1080p or smaller video decoding session for all hardware video decoders when under load. Load here is defined as a concurrent 1080p to 720p video-only transcoding session using hardware video codecs together with the 1080p audio-video playback initialization. For Dolby vision codec, the codec initialization latency MUST be 50 ms or less.
[5.1/H-1-13] MUST have a codec initialization latency of 30 ms or less for a 128 kbps or lower bitrate audio decoding session for all audio decoders when under load. Load here is defined as a concurrent 1080p to 720p video-only transcoding session using hardware video codecs together with the 1080p audio-video playback initialization.
[5.1/H-1-14] MUST support AV1 hardware decoder Main 10, Level 4.1 with film grain effect over GPU composition.
[5.1/H-1-15] MUST have at least 1 hardware video decoder supporting 4K60.
[5.1/H-1-16] MUST have at least 1 hardware video encoder supporting 4K60.
[5.1/H-1-21] MUST support FEATURE_DynamicColorAspect for all hardware video decoders (AVC, HEVC, VP9, AV1, or later). Note: This means applications can update the color aspects of the video content during the decoding session. Decoders that support 10-bit and 8-bit content MUST support dynamically switching between 8- and 10-bit content in Surface mode. Decoders that support HDR transfer function MUST support dynamically switching between SDR and HDR content.
[5.1/H-1-22] MUST support encoding, decoding, GPU-editing and displaying video content in portrait aspect ratio regardless of the rotation metadata for the largest Camera supported resolution or 4K whichever is less. Note: this includes HDR profiles if codec supports HDR. AV1 codecs are only required to support 1080p resolution. This requirement is only for hardware codecs, GPU and the DPU.
[5.3/H-1-1] MUST NOT drop more than 1 frame in 10 seconds (i.e., less than 0.167 percent frame drop) for a 4K 60 fps video session under load.
[5.3/H-1-2] MUST NOT drop more than 1 frame in 10 seconds during a video resolution change in a 60 fps video session under load for a 4K session.
[5.6/H-1-1] MUST have a tap-to-tone latency of 80 milliseconds or less using the CTS Verifier tap-to-tone test.
[5.6/H-1-2] MUST have a round-trip audio latency of 80 milliseconds or less over at least one supported data path.
[5.6/H-1-3] MUST support >= 24-bit audio for stereo output over 3.5 mm audio jacks if present and over USB audio if supported through the entire data path for low latency and streaming configurations. For the low latency configuration, AAudio should be used by the app in low-latency callback mode. For the streaming configuration, a Java AudioTrack should be used by the app. In both the low latency and streaming configurations, the HAL output sink should accept either AUDIO_FORMAT_PCM_24_BIT, AUDIO_FORMAT_PCM_24_BIT_PACKED, AUDIO_FORMAT_PCM_32_BIT or AUDIO_FORMAT_PCM_FLOAT for its target output format.
[5.6/H-1-4] MUST support >= 4 channel USB audio devices.
[5.6/H-1-5] MUST support class compliant MIDI devices and declare the MIDI feature flag.
[5.6/H-1-9] MUST support at least 12 channel mixing. This implies the capability to open an AudioTrack with 7.1.4 channel mask and properly spatialise or downmix all channels to stereo.
[5.6/H-SR] Are STRONGLY RECOMMENDED to support 24 channel mixing with at least support for 9.1.6 and 22.2 channel masks.
[5.7/H-1-2] MUST support MediaDrm.SECURITY_LEVEL_HW_SECURE_ALL with the below content decryption capabilities.

Minimum Sample size	4 MiB
Minimum Number of Subsamples - H264 or HEVC	32
Minimum Number of Subsamples - VP9	9
Minimum Number of Subsamples - AV1	288
Minimum subsample buffer size	1 MiB
Minimum Generic crypto buffer size	500 KiB
Minimum Number of concurrent sessions	30
Minimum Number of keys per session	20
Minimum Total Number of Keys (all sessions)	80
Minimum Total Number of DRM Keys (all sessions)	6
Message Size	16 KiB
Decrypted Frames per Second	60 fps

[5.1/H-1-17] MUST have at least 1 hardware image decoder supporting AVIF Baseline Profile.
[5.1/H-1-18] MUST support AV1 encoder which can encode up to 480p resolution at 30fps and 1Mbps.
[5.1/H-1-20] MUST support the Feature_HdrEditing feature for all hardware AV1 and HEVC encoders present on the device at 4K resolution or the largest Camera-supported resolution, whichever is less.
[5.12/H-SR] Are Strongly Recommended to support support the Feature_HdrEditing feature for all hardware AV1 and HEVC encoders present on the device.
[5.12/H-1-2] MUST support RGBA_1010102 color format for all hardware AV1 and HEVC encoders present on the device.
[5.12/H-1-3] MUST advertise support for the EXT_YUV_target extension to sample from YUV textures in both 8 and 10-bits.
[7.1.4/H-1-1] MUST have at least 6 hardware overlays in the Display processing unit (DPU), with at least 2 of them capable of displaying 10-bit video content.

If Handheld device implementations return android.os.Build.VERSION_CODES.V for android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS and they include support for a hardware AVC or HEVC encoder, they:

[5.2/H-2-1] MUST meet the minimum quality target defined by the video encoder rate-distortion curves for hardware AVC and HEVC codecs, as defined in Run Performance Class 14 (PC14)-Video encoding quality (VEQ) tests.

2.2.7.2. Camera

If Handheld device implementations return android.os.Build.VERSION_CODES.U for android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS, they:

MUST meet the media requirements listed in Android 14 CDD section 2.2.7.2.

If Handheld device implementations return android.os.Build.VERSION_CODES.V for android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS, they:

[7.5/H-1-1] MUST have a primary rear facing camera with a resolution of at least 12 megapixels supporting video capture at 4K@30fps, 1080p@60fps, and 720p@60fps. The primary rear-facing camera is the rear-facing camera with the lowest camera ID.
[7.5/H-1-2] MUST have a primary front facing camera with a resolution of at least 6 megapixels and support video capture at 1080p@30fps. The primary front-facing camera is the front-facing camera with the lowest camera ID.
[7.5/H-1-3] MUST support android.info.supportedHardwareLevel property as FULL or better for back primary and LIMITED or better for front primary camera.
[7.5/H-1-4] MUST support CameraMetadata.SENSOR_INFO_TIMESTAMP_SOURCE_REALTIME for both primary cameras.
[7.5/H-1-5] MUST have camera2 JPEG capture latency < 1000 ms for 1080p resolution as measured by the CTS camera PerformanceTest under ITS lighting conditions (3000K) for both primary cameras.
[7.5/H-1-6] MUST have camera2 startup latency (open camera to first preview frame) < 500 ms as measured by the CTS camera PerformanceTest under ITS lighting conditions (3000K) for both primary cameras.
[7.5/H-1-8] MUST support CameraMetadata.REQUEST_AVAILABLE_CAPABILITIES_RAW and android.graphics.ImageFormat.RAW_SENSOR for the primary back camera.
[7.5/H-1-9] MUST have a rear-facing primary camera supporting 720p or 1080p @ 240fps.
[7.5/H-1-10] MUST have min ZOOM_RATIO < 1.0 for the primary cameras if there is an ultrawide RGB camera facing the same direction.
[7.5/H-1-11] MUST implement concurrent front-back streaming on primary cameras.
[7.5/H-1-12] MUST support CONTROL_VIDEO_STABILIZATION_MODE_PREVIEW_STABILIZATION for the primary back camera.
[7.5/H-1-13] MUST support LOGICAL_MULTI_CAMERA capability for the primary rear-facing camera if there are more than 1 RGB rear-facing cameras.
[7.5/H-1-14] MUST support STREAM_USE_CASE capability for both primary front and primary back camera.
[7.5/H-1-15] MUST support Night mode extensions via both CameraX and Camera2 extensions for primary cameras.
[7.5/H-1-16] MUST support DYNAMIC_RANGE_TEN_BIT capability for the primary cameras.
[7.5/H-1-17] MUST support CONTROL_SCENE_MODE_FACE_PRIORITY and face detection (STATISTICS_FACE_DETECT_MODE_SIMPLE or STATISTICS_FACE_DETECT_MODE_FULL) for the primary cameras.
[7.5/H-1-18] MUST support JPEG_R for the primary rear and primary front cameras.
[7.5/H-1-19] MUST support CONTROL_VIDEO_STABILIZATION_MODE_PREVIEW_STABILIZATION for 1080p HLG10 preview with maximum-size 16:9 aspect ratio JPEG, and for 720p HLG10 preview with maximum-size 16:9 aspect ratio JPEG stream combinations for the primary rear camera.
[7.5/H-1-20] MUST by default output JPEG_R for the primary rear and primary front cameras in the native camera app.

2.2.7.3. Hardware

If Handheld device implementations return android.os.Build.VERSION_CODES.U for android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS, they:

MUST meet the media requirements listed in Android 14 CDD section 2.2.7.3.

If Handheld device implementations return android.os.Build.VERSION_CODES.V for android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS, they:

[7.1.1.1/H-2-1] MUST have screen resolution of at least 1080p.
[7.1.1.3/H-2-1] MUST have screen density of at least 400 dpi if the device's screen width is < 600 dp.
[7.1.1.3/H-3-1] MUST have a HDR display supporting at least 1000 nits average.
[7.6.1/H-2-1] MUST have at least 8 GB of physical memory, with at least 6.64 GB available to the kernel as reported by android.app.ActivityManager.MemoryInfo.totalMem.

2.2.7.4. Performance

If Handheld device implementations return android.os.Build.VERSION_CODES.U for android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS, they:

MUST meet the performance requirements listed in Android 14 CDD section 2.2.7.4.

If Handheld device implementations return android.os.Build.VERSION_CODES.V for android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS, they:

[8.2/H-1-1] MUST ensure a sequential write performance of at least 150 MB/s.
[8.2/H-1-2] MUST ensure a random write performance of at least 10 MB/s.
[8.2/H-1-3] MUST ensure a sequential read performance of at least 250 MB/s.
[8.2/H-1-4] MUST ensure a random read performance of at least 100 MB/s.
[8.2/H-1-5] MUST ensure a parallel sequential read and write performance with 2x read and 1x write performance of at least 50 MB/s.

2.2.7.5. Graphics

If Handheld device implementations return android.os.Build.VERSION_CODES.V for android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS, they:

[7.1.4.1/H-1-2] MUST support the EGL_IMG_context_priority and EGL_EXT_protected_content extensions.
[7.1.4.1/H-1-3] MUST support VkPhysicalDeviceProtectedMemoryFeatures.protectedMemory and VK_KHR_global_priority.

2.3. Television Requirements

An Android Television device refers to an Android device implementation that is an entertainment interface for consuming digital media, movies, games, apps, and/or live TV for users sitting about ten feet away (a "lean back" or "10-foot user interface").

Android device implementations are classified as a Television if they meet all the following criteria:

Have provided a mechanism to remotely control the rendered user interface on the display that might sit ten feet away from the user.
Have an embedded screen display with the diagonal length larger than 24 inches OR include a video output port, such as VGA, HDMI, DisplayPort, or a wireless port for display.

The additional requirements in the rest of this section are specific to Android Television device implementations.

2.3.1. Hardware

Television device implementations:

[7.2.2/T-0-1] MUST support D-pad.
[7.2.3/T-0-1] MUST provide the Home and Back functions.
[7.2.3/T-0-2] MUST send both the normal and long press event of the Back function (KEYCODE_BACK) to the foreground application.
[7.2.6.1/T-0-1] MUST include support for game controllers and declare the android.hardware.gamepad feature flag.
[7.2.7/T] SHOULD provide a remote control from which users can access non-touch navigation and core navigation keys inputs.

If Television device implementations include a 3-axis gyroscope, they:

[7.3.4/T-1-1] MUST be able to report events up to a frequency of at least 100 Hz.
[7.3.4/T-1-2] MUST be capable of measuring orientation changes up to 1000 degrees per second.

Television device implementations:

[7.4.3/T-0-1] MUST support Bluetooth and Bluetooth LE.
[7.6.1/T-0-1] MUST have at least 4 GB of non-volatile storage available for application private data (a.k.a. "/data" partition).

If Television device implementations include a USB port that supports host mode, they:

[7.5.3/T-1-1] MUST include support for an external camera that connects through this USB port but is not necessarily always connected.

If TV device implementations are 32-bit:

[7.6.1/T-1-1] The memory available to the kernel and userspace MUST be at least 896MB if any of the following densities are used:
- 400dpi or higher on small/normal screens
- xhdpi or higher on large screens
- tvdpi or higher on extra large screens

If TV device implementations are 64-bit:

[7.6.1/T-2-1] The memory available to the kernel and userspace MUST be at least 1280MB if any of the following densities are used:
- 400dpi or higher on small/normal screens
- xhdpi or higher on large screens
- tvdpi or higher on extra large screens

Television device implementations:

[7.8.1/T] SHOULD include a microphone.
[7.8.2/T-0-1] MUST have an audio output and declare android.hardware.audio.output.

2.3.2. Multimedia

Television device implementations MUST support the following audio encoding and decoding formats and make them available to third-party applications:

[5.1/T-0-1] MPEG-4 AAC Profile (AAC LC)
[5.1/T-0-2] MPEG-4 HE AAC Profile (AAC+)
[5.1/T-0-3] AAC ELD (enhanced low delay AAC)

Television device implementations MUST support the following video encoding formats and make them available to third-party applications:

[5.2/T-0-1] H.264
[5.2/T-0-2] VP8
[5.2/T-0-3] AV1

Television device implementations:

[5.2.2/T-SR-1] Are STRONGLY RECOMMENDED to support H.264 encoding of 720p and 1080p resolution videos at 30 frames per second.

Television device implementations MUST support the following video decoding formats and make them available to third-party applications:

[5.3.3/T-0-1] MPEG-4 SP
[5.3.4/T-0-2] H.264 AVC
[5.3.5/T-0-3] H.265 HEVC
[5.3.6/T-0-4] VP8
[5.3.7/T-0-5] VP9
[5.3.1/T-0-6] MPEG-2
[5.3.2/T-0-7] AV1

Television device implementations MUST support MPEG-2 decoding, as detailed in Section 5.3.1, at standard video frame rates and resolutions up to and including:

[5.3.1/T-1-1] HD 1080p at 29.97 frames per second with Main Profile High Level.
[5.3.1/T-1-2] HD 1080i at 59.94 frames per second with Main Profile High Level. They MUST deinterlace interlaced MPEG-2 video and make it available to third-party applications.

Television device implementations MUST support H.264 decoding, as detailed in Section 5.3.4, at standard video frame rates and resolutions up to and including:

[5.3.4/T-1-1] HD 1080p at 60 frames per second with Baseline Profile
[5.3.4/T-1-2] HD 1080p at 60 frames per second with Main Profile
[5.3.4/T-1-3] HD 1080p at 60 frames per second with High Profile Level 4.2

Television device implementations with H.265 hardware decoders MUST support H.265 decoding, as detailed in Section 5.3.5, at standard video frame rates and resolutions up to and including:

[5.3.5/T-1-1] HD 1080p at 60 frames per second with Main Profile Level 4.1

If Television device implementations with H.265 hardware decoders support H.265 decoding and the UHD decoding profile, they:

[5.3.5/T-2-1] MUST support the UHD decoding profile at 60 frames per second with Main10 Level 5 Main Tier profile

Television device implementations MUST support VP8 decoding, as detailed in Section 5.3.6, at standard video frame rates and resolutions up to and including:

[5.3.6/T-1-1] HD 1080p at 60 frames per second decoding profile

Television device implementations with VP9 hardware decoders MUST support VP9 decoding, as detailed in Section 5.3.7, at standard video frame rates and resolutions up to and including:

[5.3.7/T-1-1] HD 1080p at 60 frames per second with profile 0 (8 bit color depth)

If Television device implementations with VP9 hardware decoders support VP9 decoding and the UHD decoding profile, they:

[5.3.7/T-2-1] MUST support the UHD decoding profile at 60 frames per second with profile 0 (8 bit color depth).
[5.3.7/T-SR1] Are STRONGLY RECOMMENDED to support the UHD decoding profile at 60 frames per second with profile 2 (10 bit color depth).

Television device implementations:

[5.5/T-0-1] MUST include support for system Master Volume and digital audio output volume attenuation on supported outputs, except for compressed audio passthrough output (where no audio decoding is done on the device).

If Television device implementations do not have a built in display, but instead support an external display connected via HDMI, they:

[5.8/T-0-1] MUST set the HDMI output mode to the highest resolution for the chosen pixel format that works with 50Hz or 60Hz refresh rate for the external display, depending on the video refresh rate for the region the device is sold in.
[5.8/T-SR-1] Are STRONGLY RECOMMENDED to provide a user configurable HDMI refresh rate selector.
[5.8] SHOULD set the HDMI output mode refresh rate to either 50Hz or 60Hz, depending on the video refresh rate for the region the device is sold in.

If Television device implementations do not have a built in display, but instead support an external display connected via HDMI, they:

[5.8/T-1-1] MUST support HDCP 2.2.

If Television device implementations do not support UHD decoding, but instead support an external display connected via HDMI, they:

[5.8/T-2-1] MUST support HDCP 1.4

2.3.3. Software

Television device implementations:

[3/T-0-1] MUST declare the features android.software.leanback and android.hardware.type.television.
[3.2.3.1/T-0-1] MUST preload one or more applications or service components with an intent handler, for all the public intent filter patterns defined by the following application intents listed here.
[3.4.1/T-0-1] MUST provide a complete implementation of the android.webkit.Webview API.

If Android Television device implementations support a lock screen, they:

[3.8.10/T-1-1] MUST display the Lock screen Notifications including the Media Notification Template.

Television device implementations:

[3.8.14/T-SR-1] Are STRONGLY RECOMMENDED to support picture-in-picture (PIP) mode multi-window.
[3.10/T-0-1] MUST support third-party accessibility services.
[3.10/T-SR-1] Are STRONGLY RECOMMENDED to preload accessibility services on the device comparable with or exceeding functionality of the Switch Access and TalkBack (for languages supported by the preinstalled Text-to-speech engine) accessibility services as provided in the talkback open source project.

If Television device implementations report the feature android.hardware.audio.output, they:

[3.11/T-SR-1] Are STRONGLY RECOMMENDED to include a TTS engine supporting the languages available on the device.
[3.11/T-1-1] MUST support installation of third-party TTS engines.

The Android Television Input Framework (TIF) simplifies the delivery of live content to Android Television devices. TIF provides a standard API to create input modules that control Android Television devices.

Television device implementations:

[3/T-0-2] MUST declare the platform feature android.software.live_tv.
[3/T-0-3] MUST support all TIF APIs such that an application which uses these APIs and the third-party TIF-based inputs service can be installed and used on the device.

The Android Television Tuner Framework (TF) unifies the handling of live content from Tuner with streaming content from IP on Android Television devices. The Tuner Framework provides a standard API to create input services that use Android Television Tuner.

If device implementations support Tuner, they:

[3/T-1-1] MUST support all Tuner Framework APIs such that an application which uses these APIs can be installed and used on the device.

2.3.4. Performance and Power

[8.1/T-0-1] Consistent frame latency. Inconsistent frame latency or a delay to render frames MUST NOT happen more often than 5 frames in a second, and SHOULD be below 1 frames in a second.
[8.2/T-0-1] MUST ensure a sequential write performance of at least 5MB/s.
[8.2/T-0-2] MUST ensure a random write performance of at least 0.5MB/s.
[8.2/T-0-3] MUST ensure a sequential read performance of at least 15MB/s.
[8.2/T-0-4] MUST ensure a random read performance of at least 3.5MB/s.

If Television device implementations include features to improve device power management that are included in AOSP or extend the features that are included in AOSP, they:

[8.3/T-1-1] MUST provide user affordance to enable and disable the battery saver feature.

If Television device implementations do not have a battery they:

[8.3/T-1-2] MUST register the device as a batteryless device as described in Supporting Batteryless Devices.

If Television device implementations have a battery they:

[8.3/T-1-3] MUST provide user affordance to display all apps that are exempted from App Standby and Doze power-saving modes.

Television device implementations:

[8.4/T-0-1] MUST provide a per-component power profile that defines the current consumption value for each hardware component and the approximate battery drain caused by the components over time as documented in the Android Open Source Project site.
[8.4/T-0-2] MUST report all power consumption values in milliampere hours (mAh).
[8.4/T-0-3] MUST report CPU power consumption per each process's UID. The Android Open Source Project meets the requirement through the uid_cputime kernel module implementation.
[8.4/T] SHOULD be attributed to the hardware component itself if unable to attribute hardware component power usage to an application.
[8.4/T-0-4] MUST make this power usage available via the adb shell dumpsys batterystats shell command to the app developer.

2.3.5. Security Model

Television device implementations:

[9/T-0-1] MUST declare the android.hardware.security.model.compatible feature.
[9.11/T-0-1] MUST back up the keystore implementation with an isolated execution environment.
[9.11/T-0-2] MUST have implementations of RSA, AES, ECDSA and HMAC cryptographic algorithms and MD5, SHA-1, and SHA-2 family hash functions to properly support the Android Keystore system's supported algorithms in an area that is securely isolated from the code running on the kernel and above. Secure isolation MUST block all potential mechanisms by which kernel or userspace code might access the internal state of the isolated environment, including DMA. The upstream Android Open Source Project (AOSP) meets this requirement by using the Trusty implementation, but another ARM TrustZone-based solution or a third-party reviewed secure implementation of a proper hypervisor-based isolation are alternative options.
[9.11/T-0-3] MUST perform the lock screen authentication in the isolated execution environment and only when successful, allow the authentication-bound keys to be used. Lock screen credentials MUST be stored in a way that allows only the isolated execution environment to perform lock screen authentication. The upstream Android Open Source Project provides the Gatekeeper Hardware Abstraction Layer (HAL) and Trusty, which can be used to satisfy this requirement.
[9.11/T-0-4] MUST support key attestation where the attestation signing key is protected by secure hardware and signing is performed in secure hardware. The attestation signing keys MUST be prevented from being used as permanent device identifiers.

Note: To meet this requirement, you must share the same attestation key for a given SKU unless at least 100,000 units of that SKU are produced. If more than 100,000 units of that SKU are produced, a different key MAY be used for each group of 100,000 units after that. Alternatively, the Remote Key Provisioning solution may be used to provision short-lived attestation keys to the device.

If Television device implementations support a secure lock screen, they:

[9.11/T-1-1] MUST allow the user to choose the Sleep timeout for transition from the unlocked to the locked state, with a minimum allowable timeout up to 15 seconds or less.

If Television device implementations include multiple users and do not declare the android.hardware.telephony feature flag, they:

[9.5/T-2-1] MUST support restricted profiles, a feature that allows device owners to manage additional users and their capabilities on the device. With restricted profiles, device owners can quickly set up separate environments for additional users to work in, with the ability to manage finer-grained restrictions in the apps that are available in those environments.

If Television device implementations include multiple users and declare the android.hardware.telephony feature flag, they:

[9.5/T-3-1] MUST NOT support restricted profiles but MUST align with the AOSP implementation of controls to enable /disable other users from accessing the voice calls and SMS.

If Television device implementations declare android.hardware.microphone, they:

[9.8.2/T-4-1] MUST display the microphone indicator when an app is accessing audio data from the microphone, but not when the microphone is only accessed by HotwordDetectionService, SOURCE_HOTWORD, ContentCaptureService, or apps holding the roles called out in Section 9.1 Permissions with CDD identifier C-3-X.
[9.8.2/T-4-2] MUST not hide the microphone indicator for system apps that have visible user interfaces or direct user interaction.

If Television device implementations declare android.hardware.camera.any, they:

[9.8.2/T-5-1] MUST display the camera indicator when an app is accessing live camera data, but not when the camera is only being accessed by app(s) holding the roles called out in Section 9.1 Permissions with CDD identifier [C-3-X].
[9.8.2/T-5-2] MUST not hide the camera indicator for system apps that have visible user interfaces or direct user interaction.

2.3.6. Developer Tools and Options Compatibility

Television device implementations:

Perfetto
- [6.1/T-0-1] MUST expose a /system/bin/perfetto binary to the shell user which cmdline complies with the perfetto documentation.
- [6.1/T-0-2] The perfetto binary MUST accept as input a protobuf config that complies with the schema defined in the perfetto documentation.
- [6.1/T-0-3] The perfetto binary MUST write as output a protobuf trace that complies with the schema defined in the perfetto documentation.
- [6.1/T-0-4] MUST provide, through the perfetto binary, at least the data sources described in the perfetto documentation.
- [6.1/T-0-5] The perfetto traced daemon MUST be enabled by default (system property persist.traced.enable).

2.4. Watch Requirements

An Android Watch device refers to an Android device implementation intended to be worn on the body, perhaps on the wrist.

Android device implementations are classified as a Watch if they meet all the following criteria:

Have a screen with the physical diagonal length in the range from 1.1 to 2.5 inches.
Have a mechanism provided to be worn on the body.

The additional requirements in the rest of this section are specific to Android Watch device implementations.

2.4.1. Hardware

Watch device implementations:

[7.1.1.1/W-0-1] MUST have a screen with the physical diagonal size in the range from 1.1 to 2.5 inches.
[7.2.3/W-0-1] MUST have the Home function available to the user, and the Back function except for when it is in UI_MODE_TYPE_WATCH.
[7.2.4/W-0-1] MUST support touchscreen input.
[7.3.1/W-SR-1] Are STRONGLY RECOMMENDED to include a 3-axis accelerometer.

If Watch device implementations include a GPS/GNSS receiver and report the capability to applications through the android.hardware.location.gps feature flag, they:

[7.3.3/W-1-1] MUST report GNSS measurements, as soon as they are found, even if a location calculated from GPS/GNSS is not yet reported.
[7.3.3/W-1-2] MUST report GNSS pseudoranges and pseudorange rates, that, in open-sky conditions after determining the location, while stationary or moving with less than 0.2 meter per second squared of acceleration, are sufficient to calculate position within 20 meters, and speed within 0.2 meters per second, at least 95% of the time.

If Watch device implementations include a 3-axis gyroscope, they:

[7.3.4/W-2-1] MUST be capable of measuring orientation changes up to 1000 degrees per second.

Watch device implementations:

[7.4.3/W-0-1] MUST support Bluetooth.
[7.6.1/W-0-1] MUST have at least 1 GB of non-volatile storage available for application private data (a.k.a. "/data" partition).
[7.6.1/W-0-2] MUST have at least 416 MB memory available to the kernel and userspace.
[7.8.1/W-0-1] MUST include a microphone.
[7.8.2/W] MAY have audio output.

2.4.2. Multimedia

No additional requirements.

2.4.3. Software

Watch device implementations:

[3/W-0-1] MUST declare the feature android.hardware.type.watch.
[3/W-0-2] MUST support uiMode = UI_MODE_TYPE_WATCH.
[3.2.3.1/W-0-1] MUST preload one or more applications or service components with an intent handler, for all the public intent filter patterns defined by the following application intents listed here.

Watch device implementations:

[3.8.4/W-SR-1] Are STRONGLY RECOMMENDED to implement an assistant on the device to handle the Assist action.

Watch device implementations that declare the android.hardware.audio.output feature flag:

[3.10/W-1-1] MUST support third-party accessibility services.
[3.10/W-SR-1] Are STRONGLY RECOMMENDED to preload accessibility services on the device comparable with or exceeding functionality of the Switch Access and TalkBack (for languages supported by the preinstalled Text-to-speech engine) accessibility services as provided in the talkback open source project.

If Watch device implementations report the feature android.hardware.audio.output, they:

[3.11/W-SR-1] Are STRONGLY RECOMMENDED to include a TTS engine supporting the languages available on the device.
[3.11/W-0-1] MUST support installation of third-party TTS engines.

2.4.4. Performance and Power

If Watch device implementations include features to improve device power management that are included in AOSP or extend the features that are included in AOSP, they:

[8.3/W-SR-1] Are STRONGLY RECOMMENDED to provide user affordance to display all apps that are exempted from App Standby and Doze power-saving modes.
[8.3/W-SR-2] Are STRONGLY RECOMMENDED to provide user affordance to enable and disable the battery saver feature.

Watch device implementations:

[8.4/W-0-1] MUST provide a per-component power profile that defines the current consumption value for each hardware component and the approximate battery drain caused by the components over time as documented in the Android Open Source Project site.
[8.4/W-0-2] MUST report all power consumption values in milliampere hours (mAh).
[8.4/W-0-3] MUST report CPU power consumption per each process's UID. The Android Open Source Project meets the requirement through the uid_cputime kernel module implementation.
[8.4/W-0-4] MUST make this power usage available via the adb shell dumpsys batterystats shell command to the app developer.
[8.4/W] SHOULD be attributed to the hardware component itself if unable to attribute hardware component power usage to an application.

2.4.5. Security Model

Watch device implementations:

[9/W-0-1] MUST declare the android.hardware.security.model.compatible feature.

If Watch device implementations include multiple users and do not declare the android.hardware.telephony feature flag, they:

[9.5/W-1-1] MUST support restricted profiles, a feature that allows device owners to manage additional users and their capabilities on the device. With restricted profiles, device owners can quickly set up separate environments for additional users to work in, with the ability to manage finer-grained restrictions in the apps that are available in those environments.

If Watch device implementations include multiple users and declare the android.hardware.telephony feature flag, they:

[9.5/W-2-1] MUST NOT support restricted profiles but MUST align with the AOSP implementation of controls to enable /disable other users from accessing the voice calls and SMS.

If device implementations have a secure lock screen and include one or more trust agent, which implements the TrustAgentService System API, they:

[9.11.1/W-1-1] MUST challenge the user for one of the recommended primary authentication methods (eg: PIN, pattern, password) more frequently than once every 72 hours.

2.5. Automotive Requirements

Android Automotive implementation refers to a vehicle head unit running Android as an operating system for part or all of the system and/or infotainment functionality.

Android device implementations are classified as an Automotive if they declare the feature android.hardware.type.automotive or meet all the following criteria.

Are embedded as part of, or pluggable to, an automotive vehicle.
Are using a screen in the driver's seat row as the primary display.

The additional requirements in the rest of this section are specific to Android Automotive device implementations.

2.5.1. Hardware

Automotive device implementations:

[7.1.1.1/A-0-1] MUST have a screen at least 6 inches in physical diagonal size.
[7.1.1.1/A-0-2] MUST have a screen size layout of at least 750 dp x 480 dp.

Automotive device implementations:

[7.1.1.1/A-0-3] MUST support GPU composition of graphic buffers at least as large as the highest resolution of any built-in display.

If Automotive device implementations support Concurrent Multi-user (where multiple Android users can interact with the device concurrently, each using their own display when config_multiuserVisibleBackgroundUsers is enabled), they:

[7.1.1.1/A-1-1] MUST have a separate screen of at least 6 inches in physical diagonal size for each occupant zone for the main display. This should be tagged as CarOccupantZoneManager.DISPLAY_TYPE_MAIN for each occupant zone.
[7.1.1.1/A-1-2] MUST have a screen size layout of at least 750 dp x 480 dp for each main display.

If Automotive device implementations support OpenGL ES 3.1, they:

[7.1.4.1/A-0-1] MUST declare OpenGL ES 3.1 or higher.
[7.1.4.1/A-0-2] MUST support Vulkan 1.1.
[7.1.4.1/A-0-3] MUST include Vulkan loader and export all symbols.

If Automotive device implementations include support for Vulkan, they:

[7.1.4.2/A-1-1] MUST satisfy the requirements specified by the Android Baseline 2021 profile

If Automotive device implementations claim support for high dynamic range displays through Configuration.isScreenHdr(), they:

[7.1.4.5/A-1-1] MUST advertise support for the EGL_EXT_gl_colorspace_bt2020_pq, EGL_EXT_surface_SMPTE2086_metadata, EGL_EXT_surface_CTA861_3_metadata, VK_EXT_swapchain_colorspace, and VK_EXT_hdr_metadata extensions.

Automotive device implementations:

[7.1.4.6/A-0-1] MUST report whether the device supports the GPU profiling capability via a system property graphics.gpu.profiler.support.

If Automotive device implementations declare support via a system property graphics.gpu.profiler.support, they:

[7.1.4.6/A-1-1] MUST report as output a protobuf trace that complies with the schema for GPU counters and GPU RenderStages defined in the Perfetto documentation.
[7.1.4.6/A-1-2] MUST report conformant values for the device's GPU counters following the gpu counter trace packet proto.
[7.1.4.6/A-1-3] MUST report conformant values for the device's GPU RenderStages following the render stage trace packet proto.
[7.1.4.6/A-1-4] MUST report a GPU Frequency tracepoint as specified by the format: power/gpu_frequency.

Automotive device implementations:

[7.1.5/A-0-1] MUST include support for legacy app compatibility mode as implemented by the upstream Android open source code. That is, device implementations MUST NOT alter the triggers or thresholds at which compatibility mode is activated, and MUST NOT alter the behavior of the compatibility mode itself.

Automotive device implementations:

[7.1.7/A-0-1] MUST configure secondary displays in the driver's line of sight as FLAG_PRIVATE.
[7.2.3/A-0-1] MUST provide the Home function and MAY provide Back and Recent functions.
[7.2.3/A-0-2] MUST send both the normal and long press event of the Back function (KEYCODE_BACK) to the foreground application.
[7.3/A-0-1] MUST implement and report GEAR_SELECTION, NIGHT_MODE, PERF_VEHICLE_SPEED and PARKING_BRAKE_ON.
[7.3/A-0-2] The value of the NIGHT_MODE flag MUST be consistent with dashboard day/night mode and SHOULD be based on ambient light sensor input. The underlying ambient light sensor MAY be the same as Photometer.
[7.3/A-0-3] MUST provide sensor additional info field TYPE_SENSOR_PLACEMENT as part of SensorAdditionalInfo for every sensor provided.
[7.3/A-SR1] MAY dead reckon Location by fusing GPS/GNSS with additional sensors. If Location is dead reckoned, it is STRONGLY RECOMMENDED to implement and report the corresponding Sensor types and/or Vehicle Property IDs used.
[7.3/A-0-4] The Location requested via LocationManager#requestLocationUpdates() MUST NOT be map matched.
[7.3.1/A-0-4] MUST comply with the Android car sensor coordinate system.
[7.3/A-SR-1] Are STRONGLY_RECOMMENDED to include a 3-axis accelerometer and 3-axis gyroscope.
[7.3/A-SR-2] Are STRONGLY_RECOMMENDED to implement and report TYPE_HEADING sensor.

[7.3/A-1-1] MUST set the NIGHT_MODE flag value consistently with the dashboard day/night mode across all displays, including the rear seat displays.

If Automotive device implementations include an accelerometer, they:

[7.3.1/A-1-1] MUST be able to report events up to a frequency of at least 100 Hz.

If device implementations include a 3-axis accelerometer, they:

[7.3.1/A-SR-1] Are STRONGLY RECOMMENDED to implement the composite sensor for limited axes accelerometer.

If Automotive device implementations include an accelerometer with less than 3 axes, they:

[7.3.1/A-1-3] MUST implement and report TYPE_ACCELEROMETER_LIMITED_AXES sensor.
[7.3.1/A-1-4] MUST implement and report TYPE_ACCELEROMETER_LIMITED_AXES_UNCALIBRATED sensor.

If Automotive device implementations include a gyroscope, they:

[7.3.4/A-2-1] MUST be able to report events up to a frequency of at least 100 Hz.
[7.3.4/A-2-3] MUST be capable of measuring orientation changes up to 250 degrees per second.
[7.3.4/A-SR-1] Are STRONGLY RECOMMENDED to configure the gyroscope's measurement range to +/-250dps in order to maximize the resolution possible.

If Automotive device implementations include a 3-axis gyroscope, they:

[7.3.4/A-SR-2] Are STRONGLY RECOMMENDED to implement the composite sensor for limited axes gyroscope.

If Automotive device implementations include a gyroscope with less than 3-axes, they:

[7.3.4/A-4-1] MUST implement and report TYPE_GYROSCOPE_LIMITED_AXES sensor.
[7.3.4/A-4-2] MUST implement and report TYPE_GYROSCOPE_LIMITED_AXES_UNCALIBRATED sensor.

If Automotive device implementations include a GPS/GNSS receiver, but do not include cellular network-based data connectivity, they:

[7.3.3/A-3-1] MUST determine location the very first time the GPS/GNSS receiver is turned on or after 4+ days within 60 seconds.
[7.3.3/A-3-2] MUST meet the time-to-first-fix criteria as described in 7.3.3/C-1-2 and 7.3.3/C-1-6 for all other location requests (i.e requests which are not the first time ever or after 4+ days). The requirement 7.3.3/C-1-2 is typically met in vehicles without cellular network-based data connectivity, by using GNSS orbit predictions calculated on the receiver, or using the last known vehicle location along with the ability to dead reckon for at least 60 seconds with a position accuracy satisfying 7.3.3/C-1-3, or a combination of both.

If automotive device implementations include a TYPE_HEADING sensor, they:

[7.3.4/A-4-3] MUST be able to report events up to a frequency of at least 1 Hz.
[7.3.4/A-SR-3] STRONGLY_RECOMMENDED to report events up to a frequency of at least 10 Hz.
SHOULD be in reference to true north.
SHOULD be available even when the vehicle is still.
SHOULD have a resolution of at least 1 degree.

Automotive device implementations:

[7.4.3/A-0-1] MUST support Bluetooth and SHOULD support Bluetooth LE.
[7.4.3/A-0-2] Android Automotive implementations MUST support the following Bluetooth profiles:
- Phone calling over Hands-Free Profile (HFP).
- Media playback over Audio Distribution Profile (A2DP).
- Media playback control over Remote Control Profile (AVRCP).
- Contact sharing using the Phone Book Access Profile (PBAP).
[7.4.3/A-SR-1] Are STRONGLY RECOMMENDED to support Message Access Profile (MAP) if the device has the driver occupant zone.

[7.4.3/A-1-1] MUST be independent and NOT interfere with other users' BT experience.

Automotive device implementations:

[7.4.5/A] SHOULD include support for cellular network-based data connectivity.
[7.4.5/A] MAY use the System API NetworkCapabilities#NET_CAPABILITY_OEM_PAID constant for networks that should be available to system apps.

If device implementations include support for AM/FM broadcast radio and expose the functionality to any application, they:

[7.4/A-1-1] MUST declare support for FEATURE_BROADCAST_RADIO.

A rear-facing camera means a world-facing camera which can be located at any place on the vehicle and is facing the outside of the vehicle cabin; that is, it images scenes on the far side of the vehicle body, like the rear-view camera.

A front-facing camera means a user-facing camera which can be located at any place on the vehicle and is facing inside of the vehicle cabin; that is it images the user, such as for video conferencing and similar applications.

Automotive device implementations:

[7.5/A-SR-1] Are STRONGLY RECOMMENDED to include one or more world-facing cameras.
MAY include one or more user-facing cameras.
[7.5/A-SR-2] Are STRONGLY RECOMMENDED to support concurrent streaming of multiple cameras.

If Automotive device implementations include at least one camera which is world-facing then, for such a camera, they:

[7.5/A-1-1] MUST be oriented so that the long dimension of the camera aligns with the X-Y plane of Android automotive sensor axes.
[7.5/A-SR-3] Are STRONGLY RECOMMENDED to have either fixed-focus or EDOF (Extended Depth of Field) hardware.
[7.5/A-1-2] MUST have the primary world-facing camera as the world-facing camera with the lowest camera ID.

If Automotive device implementations include at least one camera which is user-facing then, for such a camera:

[7.5/A-2-1] The primary user-facing camera MUST be the user-facing camera with the lowest camera ID.
MAY be oriented so that the long dimension of the camera aligns with the X-Y plane of Android automotive sensor axes.

If Automotive device implementations include a camera which is accessible via either android.hardware.Camera or android.hardware.camera2 API, then they:

[7.5/A-3-1] MUST comply with the core camera requirements in section 7.5.

If Automotive device implementations include a camera which is not accessible via either android.hardware.Camera or android.hardware.camera2 API, then they:

[7.5/A-4-1] MUST be accessible via Extended View System service.

If Automotive device implementations include one or more cameras accessible via Extended View System Service, for such a camera, they:

[7.5/A-5-1] MUST NOT rotate or horizontally mirror the camera preview.
[7.5/A-SR-4] Are STRONGLY RECOMMENDED to have a resolution of at least 1.3 megapixel.

If automotive device implementations include one or more cameras which are accessible via both Extended View System Service and android.hardware.Camera or android.hardware.Camera2 API then, for such a camera, they:

[7.5/A-6-1] MUST report the same Camera ID.

If Automotive device implementations provide a proprietary camera API, they:

[7.5/A-7-1] MUST implement such a camera API using android.hardware.camera2 API or Extended View System API.

Automotive device implementations:

[7.6.1/A-0-1] MUST have at least 4 GB of non-volatile storage available for application private data (/data partition).
[7.6.1/A] SHOULD format the data partition to offer improved performance and longevity on flash storage (for example, using f2fs file system).

If Automotive device implementations provide shared external storage via a portion of the internal non-removable storage, they:

[7.6.1/A-SR-1] Are STRONGLY RECOMMENDED to reduce I/O overhead on operations performed on the external storage, for example by using SDCardFS.

[7.6.1/A-1-1] MUST have, on a single AAOS instance, at least 4 GB for each concurrent Android user of non-volatile storage available for application private data (/data partition).

If Automotive device implementations are 64-bit:

[7.6.1/A-2-1] The memory available to the kernel and userspace MUST be at least 816 MB per main display if any of the following densities are used:
- 280 dpi or lower on small/normal screens
- ldpi or lower on extra large screens
- mdpi or lower on large screens
[7.6.1/A-2-2] The memory available to the kernel and userspace MUST be at least 944 MB per main display if any of the following densities are used:
- xhdpi or higher on small/normal screens
- hdpi or higher on large screens
- mdpi or higher on extra large screens
[7.6.1/A-2-3] The memory available to the kernel and userspace MUST be at least 1280 MB per main display if any of the following densities are used:
- 400 dpi or higher on small/normal screens
- xhdpi or higher on large screens
- tvdpi or higher on extra large screens
[7.6.1/A-2-4] The memory available to the kernel and userspace MUST be at least 1824 MB per main display if any of the following densities are used:
- 560 dpi or higher on small/normal screens
- 400 dpi or higher on large screens
- xhdpi or higher on extra large screens

Automotive device implementations:

[7.7.1/A] SHOULD include a USB port supporting peripheral mode.

If Automotive device implementations include a USB port with a controller operating in peripheral mode, they:

[7.7.1/A-1-1] MUST implement the Android Open Accessory (AOA) API.

If Automotive device implementations include a USB port supporting host mode, they:

[7.7.2/A-1-1] MUST implement the USB audio class as described in the Android SDK documentation.

Automotive device implementations:

[7.8.1/A-0-1] MUST include a microphone.

Automotive device implementations:

[7.8.2/A-0-1] MUST have an audio output and declare android.hardware.audio.output.

[7.8.2/A-1-1] MUST have an audio output device for each main display for concurrent multiple user systems.
[7.8.2/A-1-2] MUST have a Driver audio zone covering the global cabin speaker. The front passenger zone can share the driver's audio zone or can have its own audio output.

When the AudioManager.getDevices() API is called while the USB peripheral is connected, they:

[7.8.2.2/A-1-1] MUST list a device of type AudioDeviceInfo.TYPE_USB_HEADSET and role isSink() if the USB audio terminal type field is 0x0302.
[7.8.2.2/A-1-2] MUST list a device of type AudioDeviceInfo.TYPE_USB_HEADSET and role isSink() if the USB audio terminal type field is 0x0402.
[7.8.2.2/A-1-3] MUST list a device of type AudioDeviceInfo.TYPE_USB_HEADSET and role isSink() if the USB audio terminal type field is 0x0603.
[7.8.2.2/A-1-4] MUST list a device of type AudioDeviceInfo.TYPE_USB_HEADSET and role isSink() if the USB audio terminal type field is 0x0400.

2.5.2. Multimedia

Automotive device implementations MUST support the following audio encoding and decoding formats and make them available to third-party applications:

[5.1/A-0-1] MPEG-4 AAC Profile (AAC LC)
[5.1/A-0-2] MPEG-4 HE AAC Profile (AAC+)
[5.1/A-0-3] AAC ELD (enhanced low delay AAC)

Automotive device implementations MUST support the following video encoding formats and make them available to third-party applications:

[5.2/A-0-1] H.264 AVC
[5.2/A-0-2] VP8

Automotive device implementations MUST support the following video decoding formats and make them available to third-party applications:

[5.3/A-0-1] H.264 AVC
[5.3/A-0-2] MPEG-4 SP
[5.3/A-0-3] VP8
[5.3/A-0-4] VP9

Automotive device implementations are STRONGLY RECOMMENDED to support the following video decoding:

[5.3/A-SR-1] H.265 HEVC

[5.5.3/A-1-1] MUST define identical volume curves for all audio output streams mapping to the same volume-group as defined in the car audio configuration file.

2.5.3. Software

Automotive device implementations:

[3/A-0-1] MUST declare the feature android.hardware.type.automotive.
[3/A-0-2] MUST support uiMode = UI_MODE_TYPE_CAR.
[3/A-0-3] MUST support all public APIs in the android.car.* namespace.

If Automotive device implementations provide a proprietary API using android.car.CarPropertyManager with android.car.VehiclePropertyIds, they:

[3/A-1-1] MUST NOT attach special privileges to system application's use of these properties, or prevent third-party applications from using these properties.
[3/A-1-2] MUST NOT replicate a vehicle property that already exists in the SDK.

Automotive device implementations:

[3.2.1/A-0-1] MUST support and enforce all permissions constants as documented by the Automotive Permission reference page.
[3.2.3.1/A-0-1] MUST preload one or more applications or service components with an intent handler, for all the public intent filter patterns defined by the following application intents listed here.

Automotive device implementations:

[3.2.3.1/A-0-2] MUST have an app that handles the ACTION_GET_CONTENT, ACTION_OPEN_DOCUMENT, ACTION_OPEN_DOCUMENT_TREE, and ACTION_CREATE_DOCUMENT intents as described in the SDK documents, and provide the user affordance to access the document provider data by using DocumentsProvider API.

If Automotive device implementation's settings application implements a split functionality, using activity embedding, they:

[3.2.3.1/A-1-1] MUST have an activity that handles the Settings#ACTION_SETTINGS_EMBED_DEEP_LINK_ACTIVITY intent when split functionality is on. The Activity MUST be protected by android.permission.LAUNCH_MULTI_PANE_SETTINGS_DEEP_LINK, and it MUST start the activity of the Intent parsed from Settings#EXTRA_SETTINGS_EMBEDDED_DEEP_LINK_INTENT_URI.

[3.4.1/A-0-1] MUST provide a complete implementation of the android.webkit.Webview API.

[3.8/A-1-1] MUST implement the following predefined list of UserRestrictions for full secondary users that are not the current foreground user, but have UI access to the display assigned to them. The list of UserRestrictions are DISALLOW_CONFIG_LOCALE, DISALLOW_CONFIG_BLUETOOTH, DISALLOW_BLUETOOTH, DISALLOW_CAMERA_TOGGLE, and DISALLOW_MICROPHONE_TOGGLE.
[3.8/A-1-2] MUST NOT allow full secondary users that are not the current foreground user but have UI access to the display assigned to them to change day/night mode, locale, date, time, time zone, or display color features (including Brightness, Night Light, Digital Wellbeing grayscale, and Reduce Bright Colors) for any other user via Settings or from an API.

Automotive device implementations:

[3.8.3/A-0-1] MUST display notifications that use the Notification.CarExtender API when requested by third-party applications.
[3.8.4/A-SR-1] Are Strongly Recommended to implement an assistant on the device to handle the Assist action.

If Automotive device implementations include a push-to-talk button, they:

[3.8.4/A-1-1] MUST use a short press of the push-to-talk button as the designated interaction to launch the user-selected assist app, in other words the app that implements VoiceInteractionService.

Automotive device implementations:

[3.8.3.1/A-0-1] MUST correctly render resources as described in the Notifications on Automotive OS SDK documentation.
[3.8.3.1/A-0-2] MUST display PLAY and MUTE for notification actions in the place of those provided through Notification.Builder.addAction()
[3.8.3.1/A] SHOULD restrict the use of rich management tasks such as per-notification-channel controls. MAY use UI affordance per application to reduce controls.

If Automotive device implementations support User HAL properties, they:

[3.9.3/A-1-1] MUST implement all of the User lifecycle properties
- INITIAL_USER_INFO, SWITCH_USER, CREATE_USER, REMOVE_USER.

Automotive device implementations:

[3.14/A-0-1] MUST include a UI framework to support third-party apps using the media APIs as described in section 3.14.
[3.14/A-0-2] MUST allow the user to safely interact with Media Applications while driving.
[3.14/A-0-3] MUST support the CAR_INTENT_ACTION_MEDIA_TEMPLATE implicit Intent action with the CAR_EXTRA_MEDIA_PACKAGE extra.
[3.14/A-0-4] MUST provide an affordance to navigate into a Media Application's preference activity, but MUST only enable it when Car UX Restrictions are not in effect.
[3.14/A-0-5] MUST display error messages set by Media Applications, and MUST support the optional extras ERROR_RESOLUTION_ACTION_LABEL and ERROR_RESOLUTION_ACTION_INTENT.
[3.14/A-0-6] MUST support an in-app search affordance for apps that support searching.
[3.14/A-0-7] MUST respect CONTENT_STYLE_BROWSABLE_HINT and CONTENT_STYLE_PLAYABLE_HINT definitions when displaying the MediaBrowser hierarchy.

If Automotive device implementations include a default launcher app, they:

[3.14/A-1-1] MUST include media services and open them with the CAR_INTENT_ACTION_MEDIA_TEMPLATE intent.

Automotive device implementations:

[3.8/A] MAY restrict the application requests to enter a full screen mode as described in immersive documentation.
[3.8/A] MAY keep the status bar and the navigation bar visible at all times.
[3.8/A] MAY restrict the application requests to change the colors behind the system UI elements, to ensure those elements are clearly visible at all times.

If Automotive device implementations allow users to place calls of any sort, they:

[7.4.1.2/A-1-1] MUST declare the feature flag android.software.telecom.
[7.4.1.2/A-1-2] MUST implement the telecom framework.

2.5.4. Performance and Power

[8.1/A-0-1] Consistent frame latency. Inconsistent frame latency or a delay to render frames MUST NOT happen more often than 5 frames in a second, and SHOULD be below 1 frame in a second.
[8.1/A-0-2] User interface latency. Device implementations MUST ensure low latency user experience by scrolling a list of 10K list entries as defined by the Android Compatibility Test Suite (CTS) in less than 36 seconds.
[8.1/A-0-3] Task switching. When multiple apps have been launched, re-launching an already-running application after it has been launched MUST take less than 1 second.

Automotive device implementations:

[8.2/A-0-1] MUST report the number of bytes read and written to non-volatile storage per each process's UID so the stats are available to developers through System API android.car.storagemonitoring.CarStorageMonitoringManager. The Android Open Source Project meets the requirement through the uid_sys_stats kernel module.

Automotive device implementations:

[8.2/A-0-2] MUST ensure a sequential write performance of at least 5 MB/s.
[8.2/A-0-3] MUST ensure a random write performance of at least 0.5 MB/s.
[8.2/A-0-4] MUST ensure a sequential read performance of at least 15 MB/s.
[8.2/A-0-5] MUST ensure a random read performance of at least 3.5 MB/s.

If Automotive device implementations return android.os.Build.VERSION_CODES.U or greater for android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS, they:

[8.2/A-1-1] MUST ensure a sequential write performance of at least 150 MB/s.
[8.2/A-1-2] MUST ensure a random write performance of at least 10 MB/s.
[8.2/A-1-3] MUST ensure a sequential read performance of at least 250 MB/s.
[8.2/A-1-4] MUST ensure a random read performance of at least 100 MB/s.
[8.2/A-1-5] MUST ensure a parallel sequential read and write performance with 2x read and 1x write performance of at least 50 MB/s.

[8.3/A-1-3] MUST support Garage Mode.
[8.3/A] SHOULD be in Garage Mode for at least 15 minutes after every drive unless:
- The battery is drained.
- No idle jobs are scheduled.
- The driver exits Garage Mode.
[8.4/A-0-1] MUST provide a per-component power profile that defines the current consumption value for each hardware component and the approximate battery drain caused by the components over time as documented in the Android Open Source Project site.
[8.4/A-0-2] MUST report all power consumption values in milliampere hours (mAh).
[8.4/A-0-3] MUST report CPU power consumption per each process's UID. The Android Open Source Project meets the requirement through the uid_cputime kernel module implementation.
[8.4/A] SHOULD be attributed to the hardware component itself if unable to attribute hardware component power usage to an application.
[8.4/A-0-4] MUST make this power usage available via the adb shell dumpsys batterystats shell command to the app developer.

2.5.5. Security Model

If Automotive device implementations support multiple users, they:

[9.5/A-1-1] MUST NOT allow users to interact with nor switch into the Headless System User, except for device provisioning.
[9.5/A-1-2] MUST switch into a Secondary User before BOOT_COMPLETED.
[9.5/A-1-3] MUST support the ability to create a Guest User even when the maximum number of Users on a device has been reached.

If Automotive device implementations support the System API VisualQueryDetectionService or another mechanism for query detection without mic and/or camera access indication, they:

[9.8/A-1-1] MUST make sure the query detection service can only transmit data to the System, ContentCaptureService, or on-device speech recognition service (created by SpeechRecognizer#createOnDeviceSpeechRecognizer()).
[9.8/A-1-2] MUST NOT allow any audio or video information to be transmitted out of the VisualQueryDetectionService, except to ContentCaptureService or on-device speech recognition service.
[9.8/A-1-3] MUST display a user notice in System UI when the device detects user intent to engage with the Digital Assistant Application (such as by detecting user presence via camera).
[9.8/A-1-4] MUST display a microphone indicator and display the detected user query in the UI immediately after the user query is detected.
[9.8/A-1-5] MUST NOT allow a user-installable application to provide the visual query detection service.

If Automotive device implementations declare android.hardware.microphone, they:

[9.8.2/A-1-1] MUST display the microphone indicator when an app is accessing audio data from the microphone, but not when the microphone is only accessed by HotwordDetectionService, SOURCE_HOTWORD, ContentCaptureService or apps holding the roles called out in section 9.1 with CDD identifier [C-4-X].
[9.8.2/A-1-2] MUST not hide the microphone indicator for system apps that have visible user interfaces or direct user interaction.
[9.8.2/A-1-3] MUST provide a user affordance to toggle the microphone in the Settings app.

If Automotive device implementations declare android.hardware.camera.any, then they:

[9.8.2/A-2-1] MUST display the camera indicator when an app is accessing live camera data, but not when the camera is only being accessed by app(s) holding the roles as defined in Section 9.1 Permissions with CDD identifier [C-4-X].
[9.8.2/A-2-2] MUST not hide the camera indicator for system apps that have visible user interfaces or direct user interaction.
[9.8.2/A-2-3] MUST provide a user affordance to toggle the camera in the Settings app.
[9.8.2/A-2-4] MUST display Recent and Active apps using camera as returned from PermissionManager.getIndicatorAppOpUsageData(), along with any attribution messages associated with them.

Automotive device implementations:

[9/A-0-1] MUST declare the android.hardware.security.model.compatible feature.
[9.11/A-0-1] MUST back up the keystore implementation with an isolated execution environment.
[9.11/A-0-2] MUST have implementations of RSA, AES, ECDSA and HMAC cryptographic algorithms and MD5, SHA-1, and SHA-2 family hash functions to properly support the Android Keystore system's supported algorithms in an area that is securely isolated from the code running on the kernel and above. Secure isolation MUST block all potential mechanisms by which kernel or userspace code might access the internal state of the isolated environment, including DMA. The upstream Android Open Source Project (AOSP) meets this requirement by using the Trusty implementation, but another ARM TrustZone-based solution or a third-party reviewed secure implementation of a proper hypervisor-based isolation are alternative options.
[9.11/A-0-3] MUST perform the lock screen authentication in the isolated execution environment and only when successful, allow the authentication-bound keys to be used. Lock screen credentials MUST be stored in a way that allows only the isolated execution environment to perform lock screen authentication. The upstream Android Open Source Project provides the Gatekeeper Hardware Abstraction Layer (HAL) and Trusty, which can be used to satisfy this requirement.
[9.11/A-0-4] MUST support key attestation where the attestation signing key is protected by secure hardware and signing is performed in secure hardware. The attestation signing keys MUST be prevented from being used as permanent device identifiers.

Note: To meet this requirement, you must share the same attestation key for a given SKU unless at least 100,000 units of that SKU are produced. If more than 100,000 units of that SKU are produced, a different key MAY be used for each group of 100,000 units after that. Alternatively, the Remote Key Provisioning solution may be used to provision short-lived attestation keys to the device.

Automotive device implementations:

[9.14/A-0-1] MUST gatekeep messages from Android framework vehicle subsystems, e.g., allowlisting permitted message types and message sources.
[9.14/A-0-2] MUST watchdog against denial of service attacks from the Android framework or third-party apps. This guards against malicious software flooding the vehicle network with traffic, which may lead to malfunctioning vehicle subsystems.

2.5.6. Developer Tools and Options Compatibility

Automotive device implementations:

Perfetto
- [6.1/A-0-1] MUST expose a /system/bin/perfetto binary to the shell user which cmdline complies with the perfetto documentation.
- [6.1/A-0-2] The perfetto binary MUST accept as input a protobuf config that complies with the schema defined in the perfetto documentation.
- [6.1/A-0-3] The perfetto binary MUST write as output a protobuf trace that complies with the schema defined in the perfetto documentation.
- [6.1/A-0-4] MUST provide, through the perfetto binary, at least the data sources described in the perfetto documentation.
- [6.1/A-0-5] The perfetto traced daemon MUST be enabled by default (system property persist.traced.enable).

2.6. Tablet Requirements

An Android Tablet device refers to an Android device implementation that typically meets all the following criteria:

Used by holding in both hands.
Does not have a clamshell or convertible configuration.
Physical keyboard implementations used with the device connect by means of a standard connection (e.g. USB, Bluetooth).
Has a power source that provides mobility, such as a battery.
Has a screen display size greater than 7" and less than 18", measured diagonally.

Tablet device implementations have similar requirements to handheld device implementations. The exceptions are indicated by an * in that section and noted for reference in this section.

2.6.1. Hardware

Gyroscope

If Tablet device implementations include a 3-axis gyroscope, they:

[7.3.4/Tab-1-1] MUST be capable of measuring orientation changes up to 1000 degrees per second.

Minimum Memory and Storage (Section 7.6.1)

The screen densities listed for small/normal screens in the handheld requirements are not applicable to tablets.

Virtual Reality Mode (Section 7.9.1)

Virtual Reality High Performance (Section 7.9.2)

Virtual reality requirements are not applicable to tablets.

2.6.2. Security Model

Keys and Credentials (Section 9.11)

Refer to Section [9.11].

If Tablet device implementations include multiple users and do not declare the android.hardware.telephony feature flag, they:

[9.5/T-1-1] MUST support restricted profiles, a feature that allows device owners to manage additional users and their capabilities on the device. With restricted profiles, device owners can quickly set up separate environments for additional users to work in, with the ability to manage finer-grained restrictions in the apps that are available in those environments.

If Tablet device implementations include multiple users and declare the android.hardware.telephony feature flag, they:

[9.5/T-2-1] MUST NOT support restricted profiles but MUST align with the AOSP implementation of controls to enable /disable other users from accessing the voice calls and SMS.

2.6.2. Software

[3.2.3.1/Tab-0-1] MUST preload one or more applications or service components with an intent handler, for all the public intent filter patterns defined by the following application intents listed here.

3. Software

3.1. Managed API Compatibility

The managed Dalvik bytecode execution environment is the primary vehicle for Android applications. The Android application programming interface (API) is the set of Android platform interfaces exposed to applications running in the managed runtime environment.

Device implementations:

[C-0-1] MUST provide complete implementations, including all documented behaviors, of any documented API exposed by the Android SDK or any API decorated with the "@SystemApi" marker in the upstream Android source code.
[C-0-2] MUST support/preserve all classes, methods, and associated elements marked by the TestApi annotation (@TestApi).
[C-0-3] MUST NOT omit any managed APIs, alter API interfaces or signatures, deviate from the documented behavior, or include no-ops, except where specifically allowed by this Compatibility Definition.
[C-0-4] MUST still keep the APIs present and behave in a reasonable way, even when some hardware features for which Android includes APIs are omitted. See section 7 for specific requirements for this scenario.
[C-0-5] MUST NOT allow third-party apps to use non-SDK interfaces, which are defined as methods and fields in the Java language packages that are in the boot classpath in AOSP, and that do not form part of the public SDK. This includes APIs decorated with the @hide annotation but not with a @SystemAPI, as described in the SDK documents and private and package-private class members.
[C-0-6] MUST ship with each and every non-SDK interface on the same restricted lists as provided via the provisional and denylist flags in prebuilts/runtime/appcompat/hiddenapi-flags.csv path for the appropriate API level branch in the AOSP.
[C-0-7] MUST support the signed config dynamic update mechanism to remove non-SDK interfaces from a restricted list by embedding signed configuration in any APK, using the existing public keys present in AOSP.

However they:
- MAY, if a hidden API is absent or implemented differently on the device implementation, move the hidden API into the denylist or omit it from all restricted lists.
- MAY, if a hidden API does not already exist in the AOSP, add the hidden API to any of the restricted lists.
[C-0-8] MUST NOT support installing applications targeting an API level less than 24.

3.1.1. Android Extensions

Android supports extending the managed API surface of a particular API level by updating the extension version for that API level. The android.os.ext.SdkExtensions.getExtensionVersion(int apiLevel) API returns the extension version of the provided apiLevel, if there are extensions for that API level.

Android device implementations:

[C-0-1] MUST preload the AOSP implementation of both the shared library ExtShared and services ExtServices with versions greater than or equal to the minimum versions allowed per each API level. For example, Android 7.0 device implementations, running API level 24 MUST include at least version 1.
[C-0-2] MUST only return valid extension version number that have been defined by the AOSP.
[C-0-3] MUST support all the APIs defined by the extension versions returned by android.os.ext.SdkExtensions.getExtensionVersion(int apiLevel) in the same manner as other managed APIs are supported, following the requirements in section 3.1.

3.1.2. Android Library

Due to Apache HTTP client deprecation, device implementations:

[C-0-1] MUST NOT place the org.apache.http.legacy library in the bootclasspath.
[C-0-2] MUST add the org.apache.http.legacy library to the application classpath only when the app satisfies one of the following conditions:
- Targets API level 28 or lower.
- Declares in its manifest that it needs the library by setting the android:name attribute of <uses-library> to org.apache.http.legacy.

The AOSP implementation meets these requirements.

3.2. Soft API Compatibility

In addition to the managed APIs from section 3.1, Android also includes a significant runtime-only "soft" API, in the form of such things as intents, permissions, and similar aspects of Android applications that cannot be enforced at application compile time.

3.2.1. Permissions

[C-0-1] Device implementers MUST support and enforce all permission constants as documented by the Permission reference page. Note that section 9 lists additional requirements related to the Android security model.

3.2.2. Build Parameters

The Android APIs include a number of constants on the android.os.Build class that are intended to describe the current device.

[C-0-1] To provide consistent, meaningful values across device implementations, the table below includes additional restrictions on the formats of these values to which device implementations MUST conform.

Parameter	Details
VERSION.RELEASE	The version of the currently-executing Android system, in human-readable format. This field MUST have one of the string values defined in Permitted Version Strings for Android 16.
VERSION.SDK	The version of the currently-executing Android system, in a format accessible to third-party application code. For Android 16, this field MUST have the integer value 16_INT.
VERSION.SDK_INT	The version of the currently-executing Android system, in a format accessible to third-party application code. For Android 16, this field MUST have the integer value 16_INT.
VERSION.INCREMENTAL	A value chosen by the device implementer designating the specific build of the currently-executing Android system, in human-readable format. This value MUST NOT be reused for different builds made available to end users. A typical use of this field is to indicate which build number or source-control change identifier was used to generate the build. The value of this field MUST be encodable as printable 7-bit ASCII and match the regular expression `^[^ :\/~]+$`.
BOARD	A value chosen by the device implementer identifying the specific internal hardware used by the device, in human-readable format. A possible use of this field is to indicate the specific revision of the board powering the device. The value of this field MUST be encodable as 7-bit ASCII and match the regular expression `^[a-zA-Z0-9_-]+$`.
BRAND	A value reflecting the brand name associated with the device as known to the end users. MUST be in human-readable format and SHOULD represent the manufacturer of the device or the company brand under which the device is marketed. The value of this field MUST be encodable as 7-bit ASCII and match the regular expression `^[a-zA-Z0-9_-]+$`.
SUPPORTED_ABIS	The name of the instruction set (CPU type + ABI convention) of native code. See section 3.3. Native API Compatibility.
SUPPORTED_32_BIT_ABIS	The name of the instruction set (CPU type + ABI convention) of native code. See section 3.3. Native API Compatibility.
SUPPORTED_64_BIT_ABIS	The name of the second instruction set (CPU type + ABI convention) of native code. See section 3.3. Native API Compatibility.
CPU_ABI	The name of the instruction set (CPU type + ABI convention) of native code. See section 3.3. Native API Compatibility.
CPU_ABI2	The name of the second instruction set (CPU type + ABI convention) of native code. See section 3.3. Native API Compatibility.
DEVICE	A value chosen by the device implementer containing the development name or code name identifying the configuration of the hardware features and industrial design of the device. The value of this field MUST be encodable as 7-bit ASCII and match the regular expression `^[a-zA-Z0-9_-]+$`. This device name MUST NOT change during the lifetime of the product.
FINGERPRINT	A string that uniquely identifies this build. It SHOULD be reasonably human-readable. It MUST follow this template: $(BRAND)/$(PRODUCT)/ $(DEVICE):$(VERSION.RELEASE)/$(ID)/$(VERSION.INCREMENTAL):$(TYPE)/$(TAGS) For example: acme/myproduct/ mydevice:16/LMYXX/3359:userdebug/test-keys The fingerprint MUST NOT include whitespace characters. The value of this field MUST be encodable as 7-bit ASCII.
HARDWARE	The name of the hardware (from the kernel command line or /proc). It SHOULD be reasonably human-readable. The value of this field MUST be encodable as 7-bit ASCII and match the regular expression `^[a-zA-Z0-9_-]+$`.
HOST	A string that uniquely identifies the host the build was built on, in human-readable format. There are no requirements on the specific format of this field, except that it MUST NOT be null or the empty string ("").
ID	An identifier chosen by the device implementer to refer to a specific release, in human-readable format. This field can be the same as android.os.Build.VERSION.INCREMENTAL, but SHOULD be a value sufficiently meaningful for end users to distinguish between software builds. The value of this field MUST be encodable as 7-bit ASCII and match the regular expression `^[a-zA-Z0-9._-]+$`.
MANUFACTURER	The trade name of the Original Equipment Manufacturer (OEM) of the product. There are no requirements on the specific format of this field, except that it MUST NOT be null or the empty string (""). This field MUST NOT change during the lifetime of the product.
SOC_MANUFACTURER	The trade of name of the manufacturer of the primary system on chip (SOC) used in the product. Devices with the same SOC manufacturer should use the same constant value. Please ask the SOC manufacturer for the correct constant to use. The value of this field MUST be encodable as 7-bit ASCII, MUST match the regular expression `^([0-9A-Za-z ]+)`, MUST NOT start or end with whitespace, and MUST NOT be equal to "unknown". This field MUST NOT change during the lifetime of the product.
SOC_MODEL	The model name of the primary system on a chip (SOC) used in the product. Devices with the same SOC model should use the same constant value. Please ask the SOC manufacturer for the correct constant to use. The value of this field MUST be encodable as 7-bit ASCII and match the regular expression `^([0-9A-Za-z ._/+-]+)$`, MUST NOT start or end with whitespace, and MUST NOT be equal to "unknown". This field MUST NOT change during the lifetime of the product.
MODEL	A value chosen by the device implementer containing the name of the device as known to the end user. This SHOULD be the same name under which the device is marketed and sold to end users. There are no requirements on the specific format of this field, except that it MUST NOT be null or the empty string (""). This field is STRONGLY RECOMMENDED to NOT change during the lifetime of the product.
PRODUCT	A value chosen by the device implementer containing the development name or code name of the specific product (SKU) that MUST be unique within the same brand. MUST be human-readable, but is not necessarily intended for view by end users. The value of this field MUST be encodable as 7-bit ASCII and match the regular expression `^[a-zA-Z0-9_-]+$`. This product name MUST NOT change during the lifetime of the product.
ODM_SKU	An optional value chosen by the device implementer that contains SKU (Stock Keeping Unit) used to track specific configurations of the device, for example, any peripherals included with the device when sold. The value of this field MUST be encodable as 7-bit ASCII and match the regular expression `^([0-9A-Za-z.,_-]+)$`.
SERIAL	MUST return "UNKNOWN".
TAGS	A comma-separated list of tags chosen by the device implementer that further distinguishes the build. The tags MUST be encodable as 7-bit ASCII and match the regular expression `^[a-zA-Z0-9._-]+` and MUST have one of the values corresponding to the three typical Android platform signing configurations: release-keys, dev-keys, and test-keys.
TIME	A value representing the timestamp of when the build occurred.
TYPE	A value chosen by the device implementer specifying the runtime configuration of the build. This field MUST have one of the values corresponding to the three typical Android runtime configurations: user, userdebug, or eng.
USER	A name or user ID of the user (or automated user) that generated the build. There are no requirements on the specific format of this field, except that it MUST NOT be null or the empty string ("").
SECURITY_PATCH	A value indicating the security patch level of a build. It MUST signify that the build is not in any way vulnerable to any of the issues described up through the designated Android Public Security Bulletin. It MUST be in the format [YYYY-MM-DD], matching a defined string documented in the Android Public Security Bulletin or in the Android Security Advisory, for example "2015-11-01".
BASE_OS	A value representing the FINGERPRINT parameter of the build that is otherwise identical to this build except for the patches provided in the Android Public Security Bulletin. It MUST report the correct value and if such a build does not exist, report an empty string ("").
BOOTLOADER	A value chosen by the device implementer identifying the specific internal bootloader version used in the device, in human-readable format. The value of this field MUST be encodable as 7-bit ASCII and match the regular expression `^[a-zA-Z0-9._-]+$`.
getRadioVersion()	MUST (be or return) a value chosen by the device implementer identifying the specific internal radio/modem version used in the device, in human-readable format. If a device does not have any internal radio/modem it MUST return NULL. The value of this field MUST be encodable as 7-bit ASCII and match the regular expression `^[a-zA-Z0-9._-,]+$`.
getSerial()	MUST (be or return) a hardware serial number, which MUST be available and unique across devices with the same MODEL and MANUFACTURER. The value of this field MUST be encodable as 7-bit ASCII and match the regular expression `^[a-zA-Z0-9]+$`.

3.2.3. Intent Compatibility

3.2.3.1. Common Application Intents

Android intents allow application components to request functionality from other Android components. The Android upstream project includes a list of applications which implement several intent patterns to perform common actions.

Device implementations:

[C-SR-1] Are STRONGLY RECOMMENDED to preload one or more applications or service components with an intent handler, for all the public intent filter patterns defined by the following application intents listed here and provide fulfillment i.e. meet with the developer expectation for these common application intents as described in the SDK.

Please refer to Section 2 for mandatory application intents for each device type.

3.2.3.2. Intent Resolution

[C-0-1] As Android is an extensible platform, device implementations MUST allow each intent pattern referenced in section 3.2.3.1, except for Settings, to be overridden by third-party applications. The upstream Android open source implementation allows this by default.
[C-0-2] Device implementers MUST NOT attach special privileges to system applications' use of these intent patterns, or prevent third-party applications from binding to and assuming control of these patterns. This prohibition specifically includes but is not limited to disabling the "Chooser" user interface that allows the user to select between multiple applications that all handle the same intent pattern.
[C-0-3] Device implementations MUST provide a user interface for users to modify the default activity for intents.
However, device implementations MAY provide default activities for specific URI patterns (e.g. http://play.google.com) when the default activity provides a more specific attribute for the data URI. For example, an intent filter pattern specifying the data URI "http://www.android.com" is more specific than the browser's core intent pattern for "http://".

Android also includes a mechanism for third-party apps to declare an authoritative default app linking behavior for certain types of web URI intents. When such authoritative declarations are defined in an app's intent filter patterns, device implementations:

[C-0-4] MUST attempt to validate any intent filters by performing the validation steps defined in the Digital Asset Links specification as implemented by the Package Manager in the upstream Android Open Source Project.
[C-0-5] MUST attempt validation of the intent filters during the installation of the application and set all successfully validated URI intent filters as default app handlers for their URIs.
MAY set specific URI intent filters as default app handlers for their URIs, if they are successfully verified but other candidate URI filters fail verification. If a device implementation does this, it MUST provide the user appropriate per-URI pattern overrides in the settings menu.
MUST provide the user with per-app App Links controls in Settings as follows:
- [C-0-6] The user MUST be able to override holistically the default app links behavior for an app to be: always open, always ask, or never open, which must apply to all candidate URI intent filters equally.
- [C-0-7] The user MUST be able to see a list of the candidate URI intent filters.
- The device implementation MAY provide the user with the ability to override specific candidate URI intent filters that were successfully verified, on a per-intent filter basis.
- [C-0-8] The device implementation MUST provide users with the ability to view and override specific candidate URI intent filters if the device implementation lets some candidate URI intent filters succeed verification while some others can fail.

3.2.3.3. Intent Namespaces

[C-0-1] Device implementations MUST NOT include any Android component that honors any new intent or broadcast intent patterns using an ACTION, CATEGORY, or other key string in the android.* or com.android.* namespace.
[C-0-2] Device implementers MUST NOT include any Android components that honor any new intent or broadcast intent patterns using an ACTION, CATEGORY, or other key string in a package space belonging to another organization.
[C-0-3] Device implementers MUST NOT alter or extend any of the intent patterns listed in section 3.2.3.1.
Device implementations MAY include intent patterns using namespaces clearly and obviously associated with their own organization. This prohibition is analogous to that specified for Java language classes in section 3.6.

3.2.3.4. Broadcast Intents

Third-party applications rely on the platform to broadcast certain intents to notify them of changes in the hardware or software environment.

Device implementations:

[C-0-1] MUST broadcast the public broadcast intents listed here in response to appropriate system events as described in the SDK documentation. Note that this requirement is not conflicting with section 3.5 as the limitation for background applications are also described in the SDK documentation. Also certain broadcast intents are conditional upon hardware support, if the device supports the necessary hardware they MUST broadcast the intents and provide the behavior inline with SDK documentation.

3.2.3.5. Conditional Application Intents

Android includes settings that provide users an easy way to select their default applications, for example for Home screen or SMS.

Where it makes sense, device implementations MUST provide a similar settings menu and be compatible with the intent filter pattern and API methods described in the SDK documentation as below.

If device implementations report android.software.home_screen, they:

[C-1-1] MUST honor the android.settings.HOME_SETTINGS intent to show a default app settings menu for Home Screen.

If device implementations report android.hardware.telephony.calling, they:

[C-2-1] MUST provide a settings menu that will call the android.provider.Telephony.ACTION_CHANGE_DEFAULT intent to show a dialog to change the default SMS application.
[C-2-2] MUST honor the android.telecom.action.CHANGE_DEFAULT_DIALER intent to show a dialog to allow the user to change the default Phone application.
- MUST use the user-selected default Phone app's UI for incoming and outgoing calls except for emergency calls, which would use the preinstalled Phone app.
[C-2-3] MUST honor the android.telecom.action.CHANGE_PHONE_ACCOUNTS intent to provide user affordance to configure the ConnectionServices associated with the PhoneAccounts, as well as a default PhoneAccount that the telecommunications service provider will use to place outgoing calls. The AOSP implementation meets this requirement by including a "Calling Accounts option" menu within the "Calls" settings menu.
[C-2-4] MUST allow android.telecom.CallRedirectionService for an app that holds the android.app.role.CALL_REDIRECTION role.
[C-2-5] MUST provide the user affordance to choose an app that holds the android.app.role.CALL_REDIRECTION role.
[C-2-6] MUST honor the android.intent.action.SENDTO and android.intent.action.VIEW intents and provide an activity to send/display SMS messages.
[C-SR-1] Are STRONGLY RECOMMENDED to honor android.intent.action.ANSWER, android.intent.action.CALL, android.intent.action.CALL_BUTTON, android.intent.action.VIEW & android.intent.action.DIAL intents with a preloaded dialer application which can handle these intents and provide fulfillment as described in the SDK.

If device implementations report android.hardware.nfc.hce, they:

[C-3-1] MUST honor the android.settings.NFC_PAYMENT_SETTINGS intent to show a default app settings menu for Contactless payment.
[C-3-2] MUST honor android.nfc.cardemulation.action.ACTION_CHANGE_DEFAULT intent to show an activity which opens a dialog to ask the user to change the default card emulation service for a certain category as described in the SDK.

If device implementations report android.hardware.nfc, they:

[C-4-1] MUST honor these intents android.nfc.action.NDEF_DISCOVERED, android.nfc.action.TAG_DISCOVERED & android.nfc.action.TECH_DISCOVERED, to show an activity which fulfils developer expectations for these intents as described in the SDK.

If device implementations report android.hardware.bluetooth, they:

[C-5-1] MUST honor the 'android.bluetooth.adapter.action.REQUEST_ENABLE' intent and show a system activity to allow the user to turn on Bluetooth.
[C-5-2] MUST honor the 'android.bluetooth.adapter.action.REQUEST_DISCOVERABLE' intent and show a system activity that requests discoverable mode.

If device implementations support the DND feature, they:

[C-6-1] MUST implement an activity that would respond to the intent ACTION_NOTIFICATION_POLICY_ACCESS_SETTINGS, which for implementations with UI_MODE_TYPE_NORMAL it MUST be an activity where the user can grant or deny the app access to DND policy configurations.

If device implementations allow users to use third-party input methods on the device, they:

[C-7-1] MUST provide a user-accessible mechanism to add and configure third-party input methods in response to the android.settings.INPUT_METHOD_SETTINGS intent.

If device implementations support third-party accessibility services, they:

[C-8-1] MUST honor the android.settings.ACCESSIBILITY_SETTINGS intent to provide a user-accessible mechanism to enable and disable the third-party accessibility services alongside the preloaded accessibility services.

If device implementations include support for Wi-Fi Easy Connect and expose the functionality to third-party apps, they:

[C-9-1] MUST implement the Settings#ACTION_PROCESS_WIFI_EASY_CONNECT_URI Intent APIs as described in the SDK documentation.

If device implementations provide the data saver mode, they:

[C-10-1] MUST provide a user interface in the settings, that handles the Settings.ACTION_IGNORE_BACKGROUND_DATA_RESTRICTIONS_SETTINGS intent, allowing users to add applications to or remove applications from the allow list.

If device implementations do not provide the data saver mode, they:

[C-11-1] MUST have an activity that handles the Settings.ACTION_IGNORE_BACKGROUND_DATA_RESTRICTIONS_SETTINGS intent but MAY implement it as a no-op.

If device implementations declare support for the camera via android.hardware.camera.any, they:

[C-12-3] MUST handle and MUST only allow preinstalled Android applications to handle the following intents MediaStore.ACTION_IMAGE_CAPTURE, MediaStore.ACTION_IMAGE_CAPTURE_SECURE, and MediaStore.ACTION_VIDEO_CAPTURE as described in the SDK document.

If device implementations report android.software.device_admin, they:

[C-13-1] MUST honor the intent android.app.action.ADD_DEVICE_ADMIN to invoke a UI to bring the user through adding the device administrator to the system (or allowing them to reject it).
[C-13-2] MUST honor the intents android.app.action.PROVISION_MANAGED_PROFILE, android.app.action.SET_NEW_PARENT_PROFILE_PASSWORD, android.app.action.SET_NEW_PASSWORD & android.app.action.START_ENCRYPTION and have an activity to provide fulfillment for these intents as described in SDK here.

If device implementations declare the android.software.autofill feature flag, they:

[C-14-1] MUST fully implement the AutofillService and AutofillManager APIs and honor the android.settings.REQUEST_SET_AUTOFILL_SERVICE intent to show a default app settings menu to enable and disable autofill and change the default autofill service for the user.

If device implementations include a pre-installed app or wish to allow third-party apps to access the usage statistics, they:

[C-SR-2] are STRONGLY RECOMMENDED provide user-accessible mechanism to grant or revoke access to the usage stats in response to the android.settings.ACTION_USAGE_ACCESS_SETTINGS intent for apps that declare the android.permission.PACKAGE_USAGE_STATS permission.

If device implementations intend to disallow any apps, including pre-installed apps, from accessing the usage statistics, they:

[C-15-1] MUST still have an activity that handles the android.settings.ACTION_USAGE_ACCESS_SETTINGS intent pattern but MUST implement it as a no-op, that is to have an equivalent behavior as when the user is declined for access.

If device implementations surface links to the activities specified by AutofillService_passwordsActivity in Settings or links to user passwords through a similar mechanism, they:

[C-16-1] MUST surface such links for all installed autofill services.

If device implementations support the VoiceInteractionService and have more than one application using this API installed at a time, they:

[C-18-1] MUST honor the android.settings.ACTION_VOICE_INPUT_SETTINGS intent to show a default app settings menu for voice input and assist.

If device implementations report the feature android.hardware.audio.output, they:

[C-SR-3] Are STRONGLY RECOMMENDED to honor android.intent.action.TTS_SERVICE, android.speech.tts.engine.INSTALL_TTS_DATA & android.speech.tts.engine.GET_SAMPLE_TEXT intents have an activity to provide fulfillment for these intents as described in SDK here.

Android includes support for interactive screensavers, previously referred to as Dreams. Screen Savers allow users to interact with applications when a device connected to a power source is idle or docked in a desk dock. Device Implementations:

SHOULD include support for screen savers and provide a settings option for users to configure screen savers in response to the android.settings.DREAM_SETTINGS intent.

If device implementations report android.hardware.nfc.uicc or android.hardware.nfc.ese, they:

[C-19-1] MUST implement the NfcAdapter.ACTION_TRANSACTION_DETECTED Intent API (as "EVT_TRANSACTION" defined by the GSM Association technical specification TS.26 - NFC Handset Requirements).

3.2.4. Activities on secondary/multiple displays

If device implementations allow launching normal Android Activities on more than one display, they:

[C-1-1] MUST set the android.software.activities_on_secondary_displays feature flag.
[C-1-2] MUST guarantee API compatibility similar to an activity running on the primary display.
[C-1-3] MUST land the new activity on the same display as the activity that launched it, when the new activity is launched without specifying a target display via the ActivityOptions.setLaunchDisplayId() API.
[C-1-4] MUST destroy all activities, when a display with the Display.FLAG_PRIVATE flag is removed.
[C-1-5] MUST securely hide content on all screens when the device is locked with a secure lock screen, unless the app opts in to show on top of lock screen using Activity#setShowWhenLocked() API.
SHOULD have android.content.res.Configuration which corresponds to that display in order to be displayed, operate correctly, and maintain compatibility if an activity is launched on secondary display.

If device implementations allow launching normal Android Activities on secondary displays and a secondary display has the android.view.Display.FLAG_PRIVATE flag:

[C-3-1] Only the owner of that display, system, and activities that are already on that display MUST be able to launch to it. Everyone can launch to a display that has android.view.Display.FLAG_PUBLIC flag.

3.3. Native API Compatibility

Native code compatibility is challenging. For this reason, device implementers are:

[C-SR-1] STRONGLY RECOMMENDED to use the implementations of the libraries listed below from the upstream Android Open Source Project.

3.3.1. Application Binary Interfaces

Managed Dalvik bytecode can call into native code provided in the application .apk file as an ELF .so file compiled for the appropriate device hardware architecture. As native code is highly dependent on the underlying processor technology, Android defines a number of Application Binary Interfaces (ABIs) in the Android NDK.

Device implementations:

[C-0-1] MUST be compatible with one or more defined Android NDK ABIs.
[C-0-2] MUST include support for code running in the managed environment to call into native code, using the standard Java Native Interface (JNI) semantics.
[C-0-3] MUST be source-compatible (i.e. header-compatible) and binary-compatible (for the ABI) with each required library in the list below.
[C-0-5] MUST accurately report the native Application Binary Interface (ABI) supported by the device, via the android.os.Build.SUPPORTED_ABIS, android.os.Build.SUPPORTED_32_BIT_ABIS, and android.os.Build.SUPPORTED_64_BIT_ABIS parameters, each a comma separated list of ABIs ordered from the most to the least preferred one.
[C-0-6] MUST report, via the above parameters, a subset of the following list of ABIs and MUST NOT report any ABI not on the list.
- armeabi (no longer supported as a target by the NDK)
- armeabi-v7a
- arm64-v8a
- x86
- x86-64
- riscv64
[C-0-7] MUST make all the following libraries, providing native APIs, available to apps that include native code:
- libaaudio.so (AAudio native audio support)
- libamidi.so (native MIDI support, if feature android.software.midi is claimed as described in Section 5.9)
- libandroid.so (native Android activity support)
- libc (C library)
- libcamera2ndk.so
- libdl (dynamic linker)
- libEGL.so (native OpenGL surface management)
- libGLESv1_CM.so (OpenGL ES 1.x)
- libGLESv2.so (OpenGL ES 2.0)
- libGLESv3.so (OpenGL ES 3.x)
- libicui18n.so
- libicuuc.so
- libjnigraphics.so
- liblog (Android logging)
- libmediandk.so (native media APIs support)
- libm (math library)
- libneuralnetworks.so (Neural Networks API)
- libOpenMAXAL.so (OpenMAX AL 1.0.1 support)
- libOpenSLES.so (OpenSL ES 1.0.1 audio support)
- libRS.so
- libstdc++ (Minimal support for C++)
- libvulkan.so (Vulkan)
- libz (Zlib compression)
- JNI interface
[C-0-8] MUST NOT add or remove the public functions for the native libraries listed above.
[C-0-9] MUST list additional non-AOSP libraries exposed directly to third-party apps in /vendor/etc/public.libraries.txt.
[C-0-10] MUST NOT expose any other native libraries, implemented and provided in AOSP as system libraries, to third-party apps targeting API level 24 or higher as they are reserved.
[C-0-11] MUST export all the OpenGL ES 3.1 and Android Extension Pack function symbols, as defined in the NDK, through the libGLESv3.so library. Note that while all the symbols MUST be present, section 7.1.4.1 describes in more detail the requirements for when the full implementation of each corresponding functions are expected.
[C-0-12] MUST export function symbols for the core Vulkan 1.1 function symbols, as well as the VK_KHR_surface, VK_KHR_android_surface, VK_KHR_swapchain, VK_KHR_maintenance1, and VK_KHR_get_physical_device_properties2 extensions through the libvulkan.so library. Note that while all the symbols MUST be present, section 7.1.4.2 describes in more detail the requirements for when the full implementation of each corresponding functions are expected.
SHOULD be built using the source code and header files available in the upstream Android Open Source Project.

Note that future releases of Android may introduce support for additional ABIs.

3.3.2. 32-bit ARM Native Code Compatibility

If device implementations report the support of the armeabi ABI, they:

[C-3-1] MUST also support armeabi-v7a and report its support, as armeabi is only for backwards compatibility with older apps.

If device implementations report the support of the armeabi-v7a ABI, for apps using this ABI, they:

[C-2-1] MUST include the following lines in /proc/cpuinfo, and SHOULD NOT alter the values on the same device, even when they are read by other ABIs.
- Features:, followed by a list of any optional ARMv7 CPU features supported by the device.
- CPU architecture:, followed by an integer describing the device's highest supported ARM architecture (e.g., "8" for ARMv8 devices).
[C-2-2] MUST always keep the following operations available, even in the case where the ABI is implemented on an ARMv8 architecture, either through native CPU support or through software emulation:
- SWP and SWPB instructions.
- CP15ISB, CP15DSB, and CP15DMB barrier operations.
[C-2-3] MUST include support for the Advanced SIMD (a.k.a. NEON) extension.

3.4. Web Compatibility

3.4.1. WebView Compatibility

If device implementations provide a complete implementation of the android.webkit.Webview API, they:

[C-1-1] MUST report android.software.webview.
[C-1-2] MUST use the Chromium Project build from the upstream Android Open Source Project on the Android 16 branch for the implementation of the android.webkit.WebView API.

[C-1-3] The user agent string reported by the WebView for apps targeting SDK level 35 and lower MUST be in the following format:

Mozilla/5.0 (Linux; Android $(VERSION); \[$(MODEL)\] \[Build/$(BUILD)\]; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 $(CHROMIUM_VER) Mobile Safari/537.36
- The value of the $(VERSION) string MUST be the same as the value for android.os.Build.VERSION.RELEASE.
- The $(MODEL) string MAY be empty, but if not empty it MUST have the same value as android.os.Build.MODEL.
- "Build/$(BUILD)" MAY be omitted, but if present the $(BUILD) string MUST be the same as the value for android.os.Build.ID.
- The value of the $(CHROMIUM_VER) string MUST be the version of Chromium in the upstream Android Open Source Project.
- Device implementations MAY omit Mobile in the user agent string.

The WebView component SHOULD include support for as many HTML5 features as possible and if it supports the feature SHOULD conform to the HTML5 specification.
[C-1-4] MUST render the provided content or remote URL content in a process that is distinct from the application that instantiates the WebView. Specifically the separate renderer process MUST hold lower privilege, run as a separate user ID, have no access to the app's data directory, have no direct network access, and only have access to the minimum-required system services over Binder. The AOSP implementation of WebView meets this requirement.

Note that if device implementations are 32-bit or declare the feature flag android.hardware.ram.low, they are exempted from C-1-3.

3.4.2. Browser Compatibility

If device implementations include a standalone Browser application for general web browsing, they:

[C-1-1] MUST support each of these APIs associated with HTML5:
[C-1-2] MUST support the HTML5/W3C webstorage API and SHOULD support the HTML5/W3C IndexedDB API. Note that as the web development standards bodies are transitioning to favor IndexedDB over webstorage, IndexedDB is expected to become a required component in a future version of Android.
MAY ship a custom user agent string in the standalone Browser application.
SHOULD implement support for as much of HTML5 as possible on the standalone Browser application (whether based on the upstream WebKit Browser application or a third-party replacement).

However, If device implementations do not include a standalone Browser application, they:

[C-2-1] MUST still support the public intent patterns as described in section 3.2.3.1.

3.5. API Behavioral Compatibility

Device implementations:

[C-0-9] MUST ensure that API behavioral compatibility is applied for all installed apps unless they are restricted as described in Section 3.5.1.
[C-0-10] MUST NOT implement the allowlisting approach that ensures API behavioral compatibility only for apps that are selected by device implementers.

The behaviors of each of the API types (managed, soft, native, and web) must be consistent with the preferred implementation of the upstream Android Open Source Project. Some specific areas of compatibility are:

[C-0-1] Devices MUST NOT change the behavior or semantics of a standard intent.
[C-0-2] Devices MUST NOT alter the lifecycle or lifecycle semantics of a particular type of system component (such as Service, Activity, ContentProvider, etc.).
[C-0-3] Devices MUST NOT change the semantics of a standard permission.
Devices MUST NOT alter the limitations enforced on background applications. More specifically, for background apps:
- [C-0-4] they MUST stop executing callbacks that are registered by the app to receive outputs from the GnssMeasurement and GnssNavigationMessage.
- [C-0-5] they MUST rate-limit the frequency of updates that are provided to the app through the LocationManager API class or the WifiManager.startScan() method.
- [C-0-6] if the app is targeting API level 25 or higher, they MUST NOT allow to register broadcast receivers for the implicit broadcasts of standard Android intents in the app's manifest, unless the broadcast intent requires a "signature" or "signatureOrSystem" protectionLevel permission or are on the exemption list.
- [C-0-7] if the app is targeting API level 25 or higher, they MUST stop the app's background services, just as if the app had called the services' stopSelf() method, unless the app is placed on a temporary allowlist to handle a task that's visible to the user.
- [C-0-8] if the app is targeting API level 25 or higher, they MUST release the wakelocks the app holds.
[C-0-11] Devices MUST return the following security providers as the first seven array values from the Security.getProviders() method, in the given order and with the given names (as returned by Provider.getName()) and classes, unless the app has modified the list via insertProviderAt() or removeProvider(). Devices MAY return additional providers after the specified list of providers below.
1. AndroidNSSP - android.security.net.config.NetworkSecurityConfigProvider
2. AndroidOpenSSL - com.android.org.conscrypt.OpenSSLProvider
3. CertPathProvider - sun.security.provider.CertPathProvider
4. AndroidKeyStoreBCWorkaround - android.security.keystore.AndroidKeyStoreBCWorkaroundProvider
5. BC - com.android.org.bouncycastle.jce.provider.BouncyCastleProvider
6. HarmonyJSSE - com.android.org.conscrypt.JSSEProvider
7. AndroidKeyStore - android.security.keystore.AndroidKeyStoreProvider

The above list is not comprehensive. The Compatibility Test Suite (CTS) tests significant portions of the platform for behavioral compatibility, but not all. It is the responsibility of the implementer to ensure behavioral compatibility with the Android Open Source Project. For this reason, device implementers SHOULD use the source code available via the Android Open Source Project where possible, rather than re-implement significant parts of the system.

3.5.1. Application Restriction

If device implementations implement a proprietary mechanism to restrict apps (e.g. changing or restricting API behaviors that are described in the SDK) and that mechanism is more restrictive than the Restricted App Standby Bucket, they:

[C-1-1] MUST allow the user to see the list of restricted apps.
[C-1-2] MUST provide user affordance to turn on / off all of these proprietary restrictions on each app.
[C-1-3] MUST not automatically apply these proprietary restrictions without evidence of poor system health behavior, but MAY apply the restrictions on apps upon detection of poor system health behavior like stuck wakelocks, long running services, and other criteria. The criteria MAY be determined by device implementers but MUST be related to the app's impact on the system health. Other criteria that are not purely related to the system health, such as the app's lack of popularity in the market, MUST NOT be used as criteria.
[C-1-4] MUST not automatically apply these proprietary restrictions for apps when a user has turned off app restrictions manually, and MAY suggest the user to apply these proprietary restrictions.
[C-1-5] MUST inform users if these proprietary restrictions are applied to an app automatically. Such information MUST be provided in the 24-hour period preceding the application of these proprietary restrictions.
[C-1-6] MUST return true for the ActivityManager.isBackgroundRestricted() method for any API calls from an app.
[C-1-7] MUST NOT restrict the top foreground app that is explicitly used by the user.
[C-1-8] MUST suspend these proprietary restrictions on an app whenever a user starts to explicitly use the app, making it the top foreground application.
[C-1-10] MUST provide a public and clear document or website that describes how proprietary restrictions are applied. This document or website MUST be linkable from the Android SDK documents and MUST include:
- Triggering conditions for proprietary restrictions.
- What and how an app can be restricted.
- How an app can be exempted from such restrictions.
- How an app can request an exemption from proprietary restrictions, if they support such an exemption for apps the user can install.

If an app is pre-installed on the device and has never been explicitly used by a user for more than 30 days, [C-1-3] [C-1-5] are exempted.

If device implementations extend the app restrictions that are implemented in AOSP, they:

[C-2-1]MUST follow the implementation described in this document.

3.5.2. Application Hibernation

If device implementations include App Hibernation that is included in AOSP or extends the feature that is included in AOSP, then they:

[C-1-1] MUST meet all the requirements in section 3.5.1 except for [C-1-6] and [C-1-3].
[C-1-2] MUST only apply the restriction on the app for a user when there is evidence that the user has not used the app for some period of time. This duration is STRONGLY RECOMMENDED to be one month or longer. Usage MUST be defined by either explicit user interaction via the UsageStats#getLastTimeVisible() API or anything that would cause an app to leave the force-stopped state, including service bindings, content provider bindings, explicit broadcasts, etc., which will be tracked by a new API UsageStats#getLastTimeAnyComponentUsed().
[C-1-3] MUST only apply restrictions affecting all device users when there is evidence that the package has not been used by ANY user for some period of time. This duration is STRONGLY RECOMMENDED to be one month or longer.
[C-1-4] MUST NOT render the app unable to respond to activity intents, service bindings, content provider requests, or explicit broadcasts.

App Hibernation in AOSP meets the above requirements.

3.6. API Namespaces

Android follows the package and class namespace conventions defined by the Java programming language. To ensure compatibility with third-party applications, device implementers MUST NOT make any prohibited modifications (see below) to these package namespaces:

java.*
javax.*
sun.*
android.*
androidx.*
com.android.*

That is, they:

[C-0-1] MUST NOT modify the publicly exposed APIs on the Android platform by changing any method or class signatures, or by removing classes or class fields.
[C-0-2] MUST NOT add any publicly exposed elements (such as classes or interfaces, or fields or methods to existing classes or interfaces) or Test or System APIs to the APIs in the above namespaces. A "publicly exposed element" is any construct that is not decorated with the "@hide" marker as used in the upstream Android source code.

Device implementers MAY modify the underlying implementation of the APIs, but such modifications:

[C-0-3] MUST NOT impact the stated behavior and Java-language signature of any publicly exposed APIs.
[C-0-4] MUST NOT be advertised or otherwise exposed to developers.

However, device implementers MAY add custom APIs outside the standard Android namespace, but the custom APIs:

[C-0-5] MUST NOT be in a namespace owned by or referring to another organization. For instance, device implementers MUST NOT add APIs to the com.google.* or similar namespace: only Google may do so. Similarly, Google MUST NOT add APIs to other companies' namespaces.
[C-0-6] MUST be packaged in an Android shared library so that only apps that explicitly use them (via the <uses-library> mechanism) are affected by the increased memory usage of such APIs.

Device implementers MAY add custom APIs in native languages, outside of the NDK APIs, but the custom APIs:

[C-1-1] MUST NOT be in a NDK library or a library owned by another organization as described here.

If a device implementer proposes to improve one of the package namespaces above (such as by adding useful new functionality to an existing API, or adding a new API), the implementer SHOULD visit source.android.com and begin the process for contributing changes and code, according to the information on that site.

Note that the restrictions above correspond to standard conventions for naming APIs in the Java programming language; this section simply aims to reinforce those conventions and make them binding through inclusion in this Compatibility Definition.

3.7. Runtime Compatibility

Device implementations:

[C-0-1] MUST support the full Dalvik Executable (DEX) format and Dalvik bytecode specification and semantics.
[C-0-2] MUST configure Dalvik runtimes to allocate memory in accordance with the upstream Android platform, and as specified by the following table. (See section 7.1.1 for screen size and screen density definitions.)
SHOULD use Android RunTime (ART), the reference upstream implementation of the Dalvik Executable Format, and the reference implementation's package management system.
SHOULD run fuzz tests under various modes of execution and target architectures to assure the stability of the runtime. Refer to JFuzz and DexFuzz in the Android Open Source Project website.

Note that memory values specified below are considered minimum values and device implementations MAY allocate more memory per application.

Screen Layout	Screen Density	Minimum Application Memory
Android Watch	120 dpi (ldpi)	32MB
	140 dpi (140dpi)
	160 dpi (mdpi)
	180 dpi (180dpi)
	200 dpi (200dpi)
	213 dpi (tvdpi)
	220 dpi (220dpi)	36MB
	240 dpi (hdpi)
	280 dpi (280dpi)
	320 dpi (xhdpi)	48MB
	360 dpi (360dpi)	48MB
	400 dpi (400dpi)	56MB
	420 dpi (420dpi)	64MB
	480 dpi (xxhdpi)	88MB
	560 dpi (560dpi)	112MB
	640 dpi (xxxhdpi)	154MB
small/normal	120 dpi (ldpi)	32MB
	140 dpi (140dpi)
	160 dpi (mdpi)
	180 dpi (180dpi)	48MB
	200 dpi (200dpi)
	213 dpi (tvdpi)
	220 dpi (220dpi)
	240 dpi (hdpi)
	280 dpi (280dpi)
	320 dpi (xhdpi)	80MB
	360 dpi (360dpi)	80MB
	400 dpi (400dpi)	96MB
	420 dpi (420dpi)	112MB
	480 dpi (xxhdpi)	128MB
	560 dpi (560dpi)	192MB
	640 dpi (xxxhdpi)	256MB
large	120 dpi (ldpi)	32MB
	140 dpi (140dpi)	48MB
	160 dpi (mdpi)	48MB
	180 dpi (180dpi)	80MB
	200 dpi (200dpi)
	213 dpi (tvdpi)
	220 dpi (220dpi)
	240 dpi (hdpi)
	280 dpi (280dpi)	96MB
	320 dpi (xhdpi)	128MB
	360 dpi (360dpi)	160MB
	400 dpi (400dpi)	192MB
	420 dpi (420dpi)	228MB
	480 dpi (xxhdpi)	256MB
	560 dpi (560dpi)	384MB
	640 dpi (xxxhdpi)	512MB
xlarge	120 dpi (ldpi)	48MB
	140 dpi (140dpi)	80MB
	160 dpi (mdpi)	80MB
	180 dpi (180dpi)	96MB
	200 dpi (200dpi)
	213 dpi (tvdpi)
	220 dpi (220dpi)
	240 dpi (hdpi)
	280 dpi (280dpi)	144MB
	320 dpi (xhdpi)	192MB
	360 dpi (360dpi)	240MB
	400 dpi (400dpi)	288MB
	420 dpi (420dpi)	336MB
	480 dpi (xxhdpi)	384MB
	560 dpi (560dpi)	576MB
	640 dpi (xxxhdpi)	768MB

3.8. User Interface Compatibility

3.8.1. Launcher (Home Screen)

Android includes a launcher application (home screen) and support for third-party applications to replace the device launcher (home screen).

If device implementations allow third-party applications to replace the device home screen, they:

[C-1-1] MUST declare the platform feature android.software.home_screen.
[C-1-2] MUST return the AdaptiveIconDrawable object when the third-party application use <adaptive-icon> tag to provide their icon, and the PackageManager methods to retrieve icons are called.

If device implementations include a default launcher that supports in-app pinning of shortcuts, they:

[C-2-1] MUST report true for ShortcutManager.isRequestPinShortcutSupported().
[C-2-2] MUST have user affordance asking the user before adding a shortcut requested by apps via the ShortcutManager.requestPinShortcut() API method.
[C-2-3] MUST support pinned shortcuts and dynamic and static shortcuts as documented on the App Shortcuts page.

Conversely, if device implementations do not support in-app pinning of shortcuts, they:

[C-3-1] MUST report false for ShortcutManager.isRequestPinShortcutSupported().

If device implementations implement a default launcher that provides quick access to the additional shortcuts provided by third-party apps through the ShortcutManager API, they:

[C-4-1] MUST support all documented shortcut features (e.g. static and dynamic shortcuts, pinning shortcuts) and fully implement the APIs of the ShortcutManager API class.

If device implementations include a default launcher app that shows badges for the app icons, they:

[C-5-1] MUST respect the NotificationChannel.setShowBadge() API method. In other words, show a visual affordance associated with the app icon if the value is set as true, and do not show any app icon badging scheme when all of the app's notification channels have set the value as false.
MAY override the app icon badges with their proprietary badging scheme when third-party applications indicate support of the proprietary badging scheme through the use of proprietary APIs, but SHOULD use the resources and values provided through the notification badges APIs described in the SDK, such as the Notification.Builder.setNumber() and the Notification.Builder.setBadgeIconType() API.

If device implementations support monochrome icons, these icons:

[C-6-1] MUST be used only when a user explicitly enables them (e.g. via Settings or wallpaper picker menu).

3.8.2. Widgets

Android supports third-party app widgets by defining a component type and corresponding API and lifecycle that allows applications to expose an "AppWidget" to the end user.

If device implementations support third-party app widgets, they:

[C-1-1] MUST declare support for platform feature android.software.app_widgets.
[C-1-2] MUST include built-in support for AppWidgets and expose user interface affordances to add, configure, view, and remove AppWidgets
[C-1-3] MUST be capable of rendering widgets that are 4 x 4 in the standard grid size. See the App Widget DesignGuidelines in the Android SDK documentation for details.
MAY support application widgets on the lock screen.

If device implementations support third-party app widgets and in-app pinning of shortcuts, they:

[C-2-1] MUST report true for AppWidgetManager.html.isRequestPinAppWidgetSupported().
[C-2-2] MUST have user affordance asking the user before adding a shortcut requested by apps via the AppWidgetManager.requestPinAppWidget() API method.

3.8.3. Notifications

Android includes Notification and NotificationManager APIs that allow third-party app developers to notify users of notable events and attract users' attention using the hardware components (e.g. sound, vibration and light) and software features (e.g. notification shade, system bar) of the device.

3.8.3.1. Presentation of Notifications

If device implementations allow third-party apps to notify users of notable events, they:

[C-1-1] MUST support notifications that use hardware features, as described in the SDK documentation, and to the extent possible with the device implementation hardware. For instance, if a device implementation includes a vibrator, it MUST correctly implement the vibration APIs. If a device implementation lacks hardware, the corresponding APIs MUST be implemented as no-ops. This behavior is further detailed in section 7.
[C-1-2] MUST correctly render all resources (icons, animation files, etc.) provided for in the APIs, or in the Status/System Bar icon style guide, although they MAY provide an alternative user experience for notifications than that provided by the reference Android Open Source implementation.
[C-1-3] MUST honor and implement properly the behaviors described for the APIs to update, remove and group notifications.
[C-1-4] MUST provide the full behavior of the NotificationChannel API documented in the SDK.
[C-1-5] MUST provide a user affordance to block and modify a certain third-party app's notification per each channel and app package level.
[C-1-6] MUST also provide a user affordance to display deleted notification channels.
[C-1-7] MUST correctly render all resources (images, stickers, icons, etc.) provided through Notification.MessagingStyle alongside the notification text without additional user interaction. For example, MUST show all resources including icons provided through android.app.Person in a group conversation that is set through setGroupConversation.
[C-SR-1] Are STRONGLY RECOMMENDED to provide an affordance for the user to control the notifications that are exposed to apps that have been granted the Notification Listener permission. The granularity MUST be so that the user can control for each such notification listener what notification types are bridged to this listener. The types MUST include "conversations", "alerting", "silent", and "important ongoing" notifications.
[C-SR-2] Are STRONGLY RECOMMENDED provide an affordance for users to specify apps to exclude from notifying any specific notification listener.
[C-SR-3] Are STRONGLY RECOMMENDED to automatically surface a user affordance to block a certain third-party app's notification per each channel and app package level after the user dismisses that notification multiple times.
SHOULD support rich notifications.
SHOULD present some higher priority notifications as heads-up notifications.
SHOULD have a user affordance to snooze notifications.
MAY only manage the visibility and timing of when third-party apps can notify users of notable events to mitigate safety issues such as driver distraction.

Android 11 introduces support for conversation notifications, which are notifications that use MessagingStyle and provides a published People Shortcut ID.

Device implementations:

[C-SR-4] Are STRONGLY RECOMMENDED to group and display conversation notifications ahead of non conversation notifications with the exception of ongoing foreground service notifications and importance:high notifications.

If device implementations support conversation notifications and the app provides the required data for bubbles, they:

[C-SR-5] Are STRONGLY RECOMMENDED to display this conversation as a bubble. The AOSP implementation meets these requirements with the default System UI, Settings, and Launcher.

If device implementations support rich notifications, they:

[C-2-1] MUST use the exact resources as provided through the Notification.Style API class and its subclasses for the presented resource elements.
SHOULD present each and every resource element (e.g. icon, title and summary text) defined in the Notification.Style API class and its subclasses.

Heads up notifications are notifications that are presented to the user as they come in independently of the surface the user is on. If device implementations support heads-up notifications, then they:

[C-3-1] MUST use the heads-up notification view and resources as described in the Notification.Builder API class when heads-up notifications are presented.
[C-3-2] MUST display the actions provided through Notification.Builder.addAction() together with the notification content without additional user interaction as described in the SDK.

3.8.3.2. Notification Listener Service

Android includes the NotificationListenerService APIs that allow apps (once explicitly enabled by the user) to receive a copy of all notifications as they are posted or updated.

Device implementations:

[C-0-1] MUST correctly and promptly update notifications in their entirety to all such installed and user-enabled listener services, including any and all metadata attached to the Notification object.
[C-0-2] MUST respect the snoozeNotification() API call, and dismiss the notification and make a callback after the snooze duration that is set in the API call.

If device implementations have a user affordance to snooze notifications, they:

[C-1-1] MUST reflect the snoozed notification status properly through the standard APIs such as NotificationListenerService.getSnoozedNotifications().
[C-1-2] MUST make this user affordance available to snooze notifications from each installed third-party app's, unless they are from persistent/foreground services.

3.8.3.3. DND (Do not Disturb) / Priority Mode

If device implementations support the DND feature (also called Priority Mode), they:

[C-1-1] MUST, for when the device implementation has provided a means for the user to grant or deny third-party apps to access the DND policy configuration, display Automatic DND rules created by applications alongside the user-created and predefined rules.
[C-1-3] MUST honor the suppressedVisualEffects values passed along the NotificationManager.Policy and if an app has set any of the SUPPRESSED_EFFECT_SCREEN_OFF or SUPPRESSED_EFFECT_SCREEN_ON flags, it SHOULD indicate to the user that the visual effects are suppressed in the DND settings menu.

3.8.3.4. Sensitive Notification Protection

Sensitive notification information includes content such as one-time passwords, one-time confirmation codes, and similar authentication or reset codes that can appear in notifications to users.

If device implementations allow third-party apps to notify users of notable events, they:

[C-1-1] MUST redact sensitive notification information from being passed to notification listeners, unless the listener service is one of:
- System signed apps with a uid < 10000
- System UI
- Shell
- Designated Companion Device App (defined by CompanionDeviceManager)
- SYSTEM_AUTOMOTIVE_PROJECTION role
- SYSTEM_NOTIFICATION_INTELLIGENCE role
- HOME role

The AOSP implementation of NotificationAssistantServices exemplifies and meets these requirements. See android.ext.services.notification for an example.

3.8.4. Assist APIs

Android includes the Assist APIs to allow applications to elect how much information of the current context is shared with the assistant on the device.

If device implementations support the Assist action, they:

[C-2-1] MUST indicate clearly to the end user when the context is shared, by either:
- Each time the assist app accesses the context, displaying a white light around the edges of the screen that meet or exceed the duration and brightness of the Android Open Source Project implementation.
- For the preinstalled assist app, providing a user affordance less than two navigations away from the default voice input and assistant app settings menu, and only sharing the context when the assist app is explicitly invoked by the user through a hotword or assist navigation key input.
[C-2-2] The designated interaction to launch the assist app as described in section 7.2.3 MUST launch the user-selected assist app, in other words the app that implements VoiceInteractionService, or an activity handling the ACTION_ASSIST intent.

3.8.5. Alerts and Toasts

Applications can use the Toast API to display short non-modal strings to the end user that disappear after a brief period of time, and use the TYPE_APPLICATION_OVERLAY window type API to display alert windows as an overlay over other apps.

If device implementations include a screen or video output, they:

[C-1-1] MUST provide a user affordance to block an app from displaying alert windows that use the TYPE_APPLICATION_OVERLAY. The AOSP implementation meets this requirement by having controls in the notification shade.
[C-1-2] MUST honor the Toast API and display Toasts from applications to end users in some highly visible manner.

3.8.6. Themes

Android provides "themes" as a mechanism for applications to apply styles across an entire Activity or application.

Android includes a "Holo" and "Material" theme family as a set of defined styles for application developers to use if they want to match the Holo theme look and feel as defined by the Android SDK.

If device implementations include a screen or video output, they:

[C-1-1] MUST NOT alter any of the Holo theme attributes exposed to applications.
[C-1-2] MUST support the "Material" theme family and MUST NOT alter any of the Material theme attributes or their assets exposed to applications.
[C-1-3] MUST either set the "sans-serif" font family to Roboto version 2.x for the languages that Roboto supports, or provide a user affordance to change the font used for the "sans-serif" font family to Roboto version 2.x for the languages that Roboto supports.
[C-1-4] MUST generate dynamic color tonal palettes as specified in the AOSP documentation of Settings.THEME_CUSTOMIZATION_OVERLAY_PACKAGES (see android.theme.customization.system_palette and android.theme.customization.theme_style).
[C-1-5] MUST generate dynamic color tonal palettes using color theme styles enumerated in the Settings.THEME_CUSTOMIZATION_OVERLAY_PACKAGES documentation (see android.theme.customization.theme_styles), namely TONAL_SPOT, VIBRANT, EXPRESSIVE, SPRITZ, RAINBOW, FRUIT_SALAD, andMONOCHROMATIC.

"Source color" used to generate dynamic color tonal palettes when sent with android.theme.customization.system_palette (as documented in Settings.THEME_CUSTOMIZATION_OVERLAY_PACKAGES).
[C-1-6] MUST have a CAM16 chroma value of 5 or larger.
- SHOULD be derived from the wallpaper via com.android.systemui.monet.ColorScheme#getSeedColors, which provides multiple valid source colors to pick one from.
- SHOULD use the value 0xFF1B6EF3, if none of the provided colors meet the above source color requirement.

Android also includes a "Device Default" theme family as a set of defined styles for application developers to use if they want to match the look and feel of the device theme as defined by the device implementer.

Device implementations MAY modify the Device Default theme attributes exposed to applications.

Android supports a variant theme with translucent system bars, which allows application developers to fill the area behind the status and navigation bar with their app content. To enable a consistent developer experience in this configuration, it is important the status bar icon style is maintained across different device implementations.

If device implementations include a system status bar, they:

[C-2-1] MUST use white for system status icons (such as signal strength and battery level) and notifications issued by the system, unless the icon is indicating a problematic status or an app requests a light status bar using the WindowInsetsController#APPEARANCE_LIGHT_STATUS_BARS flag.
[C-2-2] Android device implementations MUST change the color of the system status icons to black (for details, refer to R.style) when an app requests a light status bar.

3.8.7. Live Wallpapers

Android defines a component type and corresponding API and lifecycle that allows applications to expose one or more "Live Wallpapers" to the end user. Live wallpapers are animations, patterns, or similar images with limited input capabilities that display as a wallpaper, behind other applications.

Hardware is considered capable of reliably running live wallpapers if it can run all live wallpapers, with no limitations on functionality, at a reasonable frame rate with no adverse effects on other applications. If limitations in the hardware cause wallpapers and/or applications to crash, malfunction, consume excessive CPU or battery power, or run at unacceptably low frame rates, the hardware is considered incapable of running live wallpaper. As an example, some live wallpapers may use an OpenGL 2.0 or 3.x context to render their content. Live wallpaper will not run reliably on hardware that does not support multiple OpenGL contexts because the live wallpaper use of an OpenGL context may conflict with other applications that also use an OpenGL context.

Device implementations capable of running live wallpapers reliably as described above SHOULD implement live wallpapers.

If device implementations implement live wallpapers, they:

[C-1-1] MUST report the platform feature flag android.software.live_wallpaper.

3.8.8. Activity Switching

The upstream Android source code includes the overview screen, a system-level user interface for task switching and displaying recently accessed activities and tasks using a thumbnail image of the application's graphical state at the moment the user last left the application.

Device implementations including the recents function navigation key as detailed in section 7.2.3 MAY alter the interface.

If device implementations including the recents function navigation key as detailed in section 7.2.3 alter the interface, they:

[C-1-1] MUST support at least up to 7 displayed activities.
SHOULD at least display the title of 4 activities at a time.
SHOULD display highlight color, icon, screen title in recents.
SHOULD display a closing affordance ("x") but MAY delay this until user interacts with screens.
SHOULD implement a shortcut to switch easily to the previous activity.
SHOULD trigger the fast-switch action between the two most recently used apps, when the recents function key is tapped twice.
SHOULD trigger the split-screen multiwindow-mode, if supported, when the recents functions key is long pressed.
MAY display affiliated recents as a group that moves together.
[C-SR-1] Are STRONGLY RECOMMENDED to use the upstream Android user interface (or a similar thumbnail-based interface) for the overview screen.

3.8.9. Input Management

Android includes support for Input Management and support for third-party input method editors.

If device implementations allow users to use third-party input methods on the device, they:

[C-1-1] MUST declare the platform feature android.software.input_methods and support IME APIs as defined in the Android SDK documentation.

3.8.10. Lock Screen Media Control

The Remote Control Client API is deprecated from Android 5.0 in favor of the Media Notification Template that allows media applications to integrate with playback controls that are displayed on the lock screen.

3.8.11. Screen savers (previously Dreams)

See section 3.2.3.5 for settings intent to congfigure screen savers.

3.8.12. Location

If device implementations include a hardware sensor (e.g. GPS) that is capable of providing the location coordinates, they

[C-1-2] MUST display the current status of location in the Location menu within Settings.
[C-1-3] MUST NOT display location modes in the Location menu within Settings.

3.8.13. Unicode and Font

Android includes support for the emoji characters defined in Unicode 10.0.

If device implementations include a screen or video output, they:

[C-1-1] MUST be capable of rendering these emoji characters in color glyph.
[C-1-2] MUST include support for:
- Roboto 2 font with different weights—sans-serif-thin, sans-serif-light, sans-serif-medium, sans-serif-black, sans-serif-condensed, sans-serif-condensed-light for the languages available on the device.
- Full Unicode 7.0 coverage of Latin, Greek, and Cyrillic, including the Latin Extended A, B, C, and D ranges, and all glyphs in the currency symbols block of Unicode 7.0.
[C-1-3] MUST NOT remove or modify NotoColorEmoji.tff in the system image. (It is acceptable to add a new emoji font to override emoji in NotoColorEmoji.tff)
SHOULD support the skin tone and diverse family emoji as specified in the Unicode Technical Report #51.

If device implementations include an IME, they:

SHOULD provide an input method to the user for these emoji characters.

Android includes support to render Myanmar fonts. Myanmar has several non-Unicode compliant fonts, commonly known as "Zawgyi," for rendering Myanmar languages.

If device implementations include support for Burmese, they:

[C-2-1] MUST render text with Unicode compliant font as default; non-Unicode compliant font MUST NOT be set as default font unless the user chooses it in the language picker.
[C-2-2] MUST support a Unicode font and a non-Unicode compliant font if a non-Unicode compliant font is supported on the device. Non-Unicode compliant font MUST NOT remove or overwrite the Unicode font.
[C-2-3] MUST render text with non-Unicode compliant font ONLY IF a language code with script code Qaag is specified (e.g. my-Qaag). No other ISO language or region codes (whether assigned, unassigned, or reserved) can be used to refer to non-Unicode compliant font for Myanmar. App developers and web page authors can specify my-Qaag as the designated language code as they would for any other language.

3.8.14. Multi-windows

If device implementations have the capability to display multiple activities at the same time, they:

[C-1-1] MUST implement such multi-window mode(s) in accordance with the application behaviors and APIs described in the Android SDK multi-window mode support documentation and meet the following requirements:

~~[C-1-2] MUST honor android:resizeableActivity that is set by an app in the AndroidManifest.xml file as described in this SDK.~~

[C-1-3] MUST NOT offer split-screen or freeform mode if the screen height is less than 440 dp and the screen width is less than 440 dp.
[C-1-4] An activity MUST NOT be resized to a size smaller than 220dp in multi-window modes other than Picture-in-Picture.
Device implementations with screen size xlarge SHOULD support freeform mode.

If device implementations support multi-window mode(s), and the split screen mode, they:

[C-2-2] MUST crop the docked activity of a split-screen multi-window but SHOULD show some content of it, if the Launcher app is the focused window.
[C-2-3] MUST honor the declared AndroidManifestLayout_minWidth and AndroidManifestLayout_minHeight values of the third-party launcher application and not override these values in the course of showing some content of the docked activity.

If device implementations support multi-window mode(s) and Picture-in-Picture multi-window mode, they:

[C-3-1] MUST launch activities in picture-in-picture multi-window mode when the app is: * Targeting API level 26 or higher and declares android:supportsPictureInPicture * Targeting API level 25 or lower and declares both android:resizeableActivity and android:supportsPictureInPicture.
[C-3-2] MUST expose the actions in their SystemUI as specified by the current PIP activity through the setActions() API.
[C-3-3] MUST support aspect ratios greater than or equal to 1:2.39 and less than or equal to 2.39:1, as specified by the PIP activity through the setAspectRatio() API.
[C-3-4] MUST use KeyEvent.KEYCODE_WINDOW to control the PIP window; if PIP mode is not implemented, the key MUST be available to the foreground activity.
[C-3-5] MUST provide a user affordance to block an app from displaying in PIP mode; the AOSP implementation meets this requirement by having controls in the notification shade.
[C-3-6] MUST allocate the following minimum width and height for the PIP window when an application does not declare any value for AndroidManifestLayout_minWidth and AndroidManifestLayout_minHeight:
- Devices with the Configuration.uiMode that is set other than UI_MODE_TYPE_TELEVISION MUST allocate a minimum width and height of 108 dp.
- Devices with the Configuration.uiMode that is set to UI_MODE_TYPE_TELEVISION MUST allocate a minimum width of 240 dp and a minimum height of 135 dp.

If device implementations include more than one Android-compatible display areas and make such areas available to apps, they:

[C-4-1] MUST support multi-window mode.

If device implementations support multi-window mode(s), they:

[C-5-1] MUST implement the correct version of the Window Manager Extensions API level as described in WindowManager Extensions.

3.8.15. Display Cutout

Android supports a Display Cutout as described in the SDK document. The DisplayCutout API defines an area on the edge of the display that may not be functional for an application due to a display cutout or curved display on the edge(s).

If device implementations include display cutout(s), they:

[C-1-5] MUST NOT have cutout(s) if the device's aspect ratio is 1.0(1:1).
[C-1-2] MUST NOT have more than one cutout per edge.
[C-1-3] MUST honor the display cutout flags set by the app through the WindowManager.LayoutParams API as described in the SDK.
[C-1-4] MUST report correct values for all cutout metrics defined in the DisplayCutout API.

3.8.16. Device Controls

Android includes ControlsProviderService and Control APIs to allow third-party applications to publish device controls for quick status and action for users.

See Section 2_2_3 for device-specific requirements.

3.8.17. Clipboard

Device implementations:

[C-0-1] MUST NOT send clipboard data to any component, activity, service, or across any network connection, without explicit user action (e.g., pressing a button on the overlay) or indication of content being sent, except for services mentioned in 9.8.6 Content Capture and App Search.

If device implementations generate a user-visible preview when content is copied to the clipboard for any ClipData item where ClipData.getDescription().getExtras() contains android.content.extra.IS_SENSITIVE, they:

[C-1-1] MUST redact the user visible preview

The AOSP reference implementation satisfies these clipboard requirements.

3.9. Device Administration

Android includes features that enable device policy controller applications to perform device administration functions at the system level, such as enforcing password policies or performing remote wipe, through the Device Policy Manager APIs.

3.9.1. Device Provisioning

3.9.1.1. Device owner provisioning

If device implementations declare android.software.device_admin, they:

[C-1-1] MUST support enrolling a Device Policy Controller (DPC) as a Device Owner app as described below:
- When the device implementation has neither users nor user data configured, it:
  - [C-1-5] MUST enroll the DPC application as the Device Owner app or enable the DPC app to choose whether to become a Device Owner or a Profile Owner, if the device declares Near-Field Communications (NFC) support via the feature flag android.hardware.nfc and receives an NFC message containing a record with MIME type MIME_TYPE_PROVISIONING_NFC.
  - [C-1-8] MUST send the ACTION_GET_PROVISIONING_MODE intent after device owner provisioning is triggered so that the DPC app can choose whether to become a Device Owner or a Profile Owner, depending on the values of android.app.extra.PROVISIONING_ALLOWED_PROVISIONING_MODES, unless it can be determined from context that there is only one valid option.
  - [C-1-9] MUST send the ACTION_ADMIN_POLICY_COMPLIANCE intent to the Device Owner app if a Device Owner is established during provisioning regardless of the provisioning method used. The user must not be able to proceed in the Setup Wizard until the Device Owner app finishes.
- When the device implementation has users or user data, it:
  - [C-1-7] MUST not enroll any DPC application as the Device Owner App any more.

3.9.1.2. Managed profile provisioning

If device implementations declare android.software.managed_users, they:

[C-1-1] MUST declare android.software.device_admin and implement the APIs allowing a Device Policy Controller (DPC) application to become the owner of a new Managed Profile.

[C-1-3] MUST provide the following user affordances within the Settings to indicate to the user when a particular system function has been disabled by the Device Policy Controller (DPC):
- A consistent icon or other user affordance (for example the upstream AOSP info icon) to represent when a particular setting is restricted by a Device Admin.
- A short explanation message, as provided by the Device Admin via the setShortSupportMessage.
- The DPC application's icon.
[C-1-4] MUST launch the handler for ACTION_PROVISIONING_SUCCESSFUL intent in the work profile if a Profile Owner is established when provisioning is initiated by the android.app.action.PROVISION_MANAGED_PROFILE intent and the DPC has implemented the handler.
[C-1-5] MUST send ACTION_PROFILE_PROVISIONING_COMPLETE broadcast to the work profile DPC when provisioning is initiated by the android.app.action.PROVISION_MANAGED_PROFILE intent.
[C-1-6] MUST send the ACTION_GET_PROVISIONING_MODE intent after profile owner provisioning is triggered so that the DPC app can choose whether to become a Device Owner or a Profile Owner except when provisioning is triggered by the intent android.app.action.PROVISION_MANAGED_PROFILE.
[C-1-7] MUST send the ACTION_ADMIN_POLICY_COMPLIANCE intent to the work profile when a Profile Owner is established during provisioning regardless of which provisioning method is used except when provisioning is triggered by the intent android.app.action.PROVISION_MANAGED_PROFILE. The user must not be able proceed in the Setup Wizard until the Profile Owner app finishes.
[C-1-8] MUST send ACTION_MANAGED_PROFILE_PROVISIONED broadcast to the personal profile DPC when a Profile Owner is established, regardless of the provisioning method used.

3.9.2. Managed Profile Support

If device implementations declare android.software.device_admin and android.software.managed_users, they:

[C-1-1] MUST support managed profiles via the android.app.admin.DevicePolicyManager APIs.
[C-1-2] MUST allow one and only one managed profile to be created.
[C-1-3] MUST use an icon badge (similar to the AOSP upstream work badge) to represent the managed applications and widgets and other badged UI elements such as "Recents & Notifications".
[C-1-4] MUST display a notification icon (similar to the AOSP upstream work badge) to indicate when user is within a managed profile application.
[C-1-5] MUST display a toast indicating that the user is in the managed profile if and when the device wakes up (ACTION_USER_PRESENT) and the foreground application is within the managed profile.
[C-1-6] Where a managed profile exists, MUST show a visual affordance in the Intent 'Chooser' to allow the user to forward the intent from the managed profile to the primary user or vice versa, if enabled by the Device Policy Controller.
[C-1-7] Where a managed profile exists, MUST expose the following user affordances for both the primary user and the managed profile:
- Separate accounting for battery, location, mobile data and storage usage for the primary user and managed profile.
- Independent management of VPN Applications installed within the primary user or managed profile.
- Independent management of applications installed within the primary user or managed profile.
- Independent management of accounts within the primary user or managed profile.
[C-1-8] MUST ensure the preinstalled dialer, contacts and messaging applications can search for and look up caller information from the managed profile (if one exists) alongside those from the primary profile, if the Device Policy Controller permits it.
[C-1-9] MUST ensure that it satisfies all the security requirements applicable for a device with multiple users enabled (see section 9.5), even though the managed profile is not counted as another user in addition to the primary user.
[C-1-10] MUST ensure that the screenshot data is saved in the work profile storage when a screenshot is captured with a topActivity window that has focus (the one the user interacted with last among all activities) and belongs to a work profile app.
[C-1-11] MUST NOT capture any other screen content (system bar, notifications or any personal profile content) except for the work profile application window/windows when saving a screenshot to the work profile (to ensure that personal profile data is not saved in the work profile).

If device implementations declare android.software.device_admin, android.software.managed_users and android.software.secure_lock_screen, they:

[C-2-1] MUST support the ability to specify a separate lock screen meeting the following requirements to grant access to apps running in a managed profile only.
- Device implementations MUST honor the DevicePolicyManager.ACTION_SET_NEW_PASSWORD intent and show an interface to configure a separate lock screen credential for the managed profile.
- The lock screen credentials of the managed profile MUST use the same credential storage and management mechanisms as the parent profile, as documented on the Android Open Source Project Site.
- The DPC password policies MUST apply to only the managed profile's lock screen credentials unless called upon the DevicePolicyManager instance returned by getParentProfileInstance.
When contacts from the managed profile are displayed in the preinstalled call log, in-call UI, in-progress and missed-call notifications, contacts and messaging apps they SHOULD be badged with the same badge used to indicate managed profile applications.

3.9.3. Managed User Support

If device implementations declare android.software.device_admin and android.software.managed_users, they:

[C-1-1] MUST provide a user affordance to logout from the current user and switch back to the primary user in multiple-user session when isLogoutEnabled returns true. The user affordance MUST be accessible from the lock screen without unlocking the device.

If device implementations declare android.software.device_admin and provide an on-device user affordance to add additional secondary Users, they:

[C-SR-1] Are STRONGLY RECOMMENDED show the same AOSP Device Owner consent disclosures that were shown in the flow initiated by android.app.action.PROVISION_MANAGED_DEVICE, prior to allowing accounts to be added in the new secondary User, so users understand that the device is managed.

3.9.4. Device Policy Management Role Requirements

If device implementations declare android.software.device_admin ~~or android.software.managed_users~~, they:

[C-1-1] MUST support the device policy management role as defined in section 9.1. The application that holds the device policy management role MAY be defined by setting config_devicePolicyManagement to the package name. The package name MUST be followed by a colon (:) and the signing certificate, unless the application is preloaded.

If a package name is not defined for config_devicePolicyManagement as described above:

[C-2-1] Device implementations MUST support provisioning without a device policy management role holder application (AOSP provides a reference implementation).

If a package name is defined for config_devicePolicyManagement as described above:

[C-3-1] The application MUST be installed on all profiles for a user.
[C-3-2] Device implementations MAY define an application that updates the device policy management role holder before provisioning by setting config_devicePolicyManagementUpdater.

If a package name is defined for config_devicePolicyManagementUpdater as described above:

[C-4-1] The application MUST be preinstalled on the device.
[C-4-2] The application MUST implement an intent filter which resolves android.app.action.UPDATE_DEVICE_POLICY_MANAGEMENT_ROLE_HOLDER.

3.9.5. Device Policy Resolution Framework

If device implementations declare android.software.device_admin ~~or android.software.managed_users~~, they:

[C-1-1] MUST resolve device policy conflicts as documented in Device Policy Resolution Framework.

3.10. Accessibility

Android provides an accessibility layer that helps users with disabilities to navigate their devices more easily. In addition, Android provides platform APIs that enable accessibility service implementations to receive callbacks for user and system events and generate alternate feedback mechanisms, such as text-to-speech, haptic feedback, and trackball/d-pad navigation.

If device implementations support third-party accessibility services, they:

[C-1-1] MUST provide an implementation of the Android accessibility framework as described in the accessibility APIs SDK documentation.
[C-1-2] MUST generate accessibility events and deliver the appropriate AccessibilityEvent to all registered AccessibilityService implementations as documented in the SDK.
[C-1-4] MUST provide a user affordance to control accessibility services that declare the AccessibilityServiceInfo.FLAG_REQUEST_ACCESSIBILITY_BUTTON. Note that for device implementations with a system navigation bar, they SHOULD allow the user to have the option for a button in the system's navigation bar to control these services.

If device implementations include preinstalled accessibility services, they:

[C-2-1] MUST implement these preinstalled accessibility services as Direct Boot Aware apps when the data storage is encrypted with File Based Encryption (FBE).
SHOULD provide a mechanism in the out-of-box setup flow for users to enable relevant accessibility services, as well as options to adjust the font size, display size and magnification gestures.

3.11. Text-to-Speech

Android includes APIs that allow applications to make use of text-to-speech (TTS) services and allows service providers to provide implementations of TTS services.

If device implementations reporting the feature android.hardware.audio.output, they:

[C-1-1] MUST support the Android TTS framework APIs.

If device implementations support installation of third-party TTS engines, they:

[C-2-1] MUST provide user affordance to allow the user to select a TTS engine for use at system level.

3.13. Quick Settings

Android provides a Quick Settings UI component that allows quick access to frequently used or urgently needed actions.

If device implementations include a Quick Settings UI component and support third-party Quick Settings, they:

[C-1-1] MUST allow the user to add or remove the tiles provided through the quicksettings APIs from a third-party app.
[C-1-2] MUST NOT automatically add a tile from a third-party app directly to the Quick Settings.
[C-1-3] MUST display all the user-added tiles from third-party apps alongside the system-provided quick setting tiles.

3.14. Media UI

If device implementations include non-voice-activated applications (the Apps) that interact with third-party applications through MediaBrowser or MediaSession, the Apps:

[C-1-2] MUST clearly display icons obtained via getIconBitmap() or getIconUri() and titles obtained via getTitle() as described in MediaDescription. May shorten titles to comply with safety regulations (e.g. driver distraction).
[C-1-3] MUST show the third-party application icon whenever displaying content provided by this third-party application.
[C-1-4] MUST allow the user to interact with the entire MediaBrowser hierarchy. MAY restrict the access to part of the hierarchy to comply with safety regulations (e.g. driver distraction), but MUST NOT give preferential treatment based on content or content provider.
[C-1-5] MUST consider double tap of KEYCODE_HEADSETHOOK or KEYCODE_MEDIA_PLAY_PAUSE as KEYCODE_MEDIA_NEXT for MediaSession.Callback#onMediaButtonEvent.

3.15. Instant Apps

If device implementations support Instant Apps, they MUST satisfy the following requirements:

[C-1-1] Instant Apps MUST only be granted permissions that have the android:protectionLevel set to "instant".
[C-1-2] Instant Apps MUST NOT interact with installed apps via implicit intents unless one of the following is true:
- The component's intent pattern filter is exposed and has CATEGORY_BROWSABLE
- The action is one of ACTION_SEND, ACTION_SENDTO, ACTION_SEND_MULTIPLE
- The target is explicitly exposed with android:visibleToInstantApps
[C-1-3] Instant Apps MUST NOT interact explicitly with installed apps unless the component is exposed via android:visibleToInstantApps.
[C-1-4] Installed Apps MUST NOT see details about Instant Apps on the device unless the Instant App explicitly connects to the installed application.
Device implementations MUST provide the following user affordances for interacting with Instant Apps. The AOSP meets the requirements with the default System UI, Settings, and Launcher. Device implementations:
- [C-1-5] MUST provide a user affordance to view and delete Instant Apps locally cached for each individual app package.
- [C-1-6] MUST provide a persistent user notification that can be collapsed while an Instant App is running in the foreground. This user notification MUST include that Instant Apps do not require installation and provide a user affordance that directs the user to the application info screen in Settings. For Instant Apps launched via web intents, as defined by using an intent with action set to Intent.ACTION_VIEW and with a scheme of "http" or "https", an additional user affordance SHOULD allow the user not to launch the Instant App and launch the associated link with the configured web browser, if a browser is available on the device.
- [C-1-7] MUST allow running Instant Apps to be accessed from the Recents function if the Recents function is available on the device.
[C-1-8] MUST preload one or more applications or service components with an intent handler for the intents listed in the SDK here and make the intents visible for Instant Apps.

3.16. Companion Device Pairing

Android includes support for companion device pairing to more effectively manage association with companion devices and provides the CompanionDeviceManager API for apps to access this feature.

If device implementations support the companion device pairing feature, they:

[C-1-1] MUST declare the feature flag FEATURE_COMPANION_DEVICE_SETUP.
[C-1-2] MUST ensure the APIs in the android.companion package is fully implemented.
[C-1-3] MUST provide user affordances for the user to select/confirm a companion device is present and operational, which MUST use the same message as implemented in AOSP without addition or modification.

3.17. Heavyweight Apps

If device implementations declare the feature FEATURE_CANT_SAVE_STATE, then they:

[C-1-1] MUST have only one installed app that specifies cantSaveState running in the system at a time. If the user leaves such an app without explicitly exiting it (for example by pressing home while leaving an active activity the system, instead of pressing back with no remaining active activities in the system), then device implementations MUST prioritize that app in RAM as they do for other things that are expected to remain running, such as foreground services. While such an app is in the background, the system can still apply power management features to it, such as limiting CPU and network access.
[C-1-2] MUST provide a UI affordance to chose the app that won't participate in the normal state save/restore mechanism once the user launches a second app declared with cantSaveState attribute.
[C-1-3] MUST NOT apply other changes in policy to apps that specify cantSaveState, such as changing CPU performance or changing scheduling prioritization.

If device implementations don't declare the feature FEATURE_CANT_SAVE_STATE, then they:

[C-1-1] MUST ignore the cantSaveState attribute set by apps and MUST NOT change the app behavior based on that attribute.

3.18. Contacts

Android includes Contacts Provider APIs to allow applications to manage contact information stored on the device. Contact data that is entered directly into the device is typically synchronized with a web service, but the data MAY also only reside locally on the device. Contacts that are only stored on the device are referred to as local contacts.

RawContacts are "associated with" or "stored in" an Account when the ACCOUNT_NAME, and ACCOUNT_TYPE, columns for the raw contacts match the corresponding Account.name and Account.type fields of the account.

Default local account: an account for raw contacts that are only stored on the device and not associated with an Account in the AccountManager, which are created with null values for the ACCOUNT_NAME, and ACCOUNT_TYPE, columns.

Custom local account: an account for raw contacts that are only stored on the device and not associated with an Account in the AccountManager, which are created with ~~at least one~~ non-null values for both the ACCOUNT_NAME and ACCOUNT_TYPE columns.

Device implementations:

[C-SR-1] Are STRONGLY RECOMMENDED to not create custom local accounts.

If device implementations use a custom local account:

[C-1-1] The ACCOUNT_NAME, of the custom local account MUST be returned by ContactsContract.RawContacts.getLocalAccountName
[C-1-2] The ACCOUNT_TYPE, of the custom local account MUST be returned by ContactsContract.RawContacts.getLocalAccountType

[C-1-3] Raw contacts that are inserted by third party applications with the default local account (i.e. by setting null values for ACCOUNT_NAME and ACCOUNT_TYPE) MUST be inserted to the custom local account.

[C-1-3] Raw contacts inserted by third-party applications without specifying an account MUST be inserted to the device's default contact account. If the default contact account is DEFAULT_ACCOUNT_STATE_LOCAL or DEFAULT_ACCOUNT_STATE_NOT_SET, these raw contacts MUST be stored in the custom local account.

[C-1-4] Raw contacts inserted into the custom local account MUST not be removed when accounts are added or removed.
[C-1-5] Delete operations performed against the custom local account MUST result in raw contacts being purged immediately (as if the CALLER_IS_SYNCADAPTER param was set to true), even if the CALLER\_IS\_SYNCADAPTER param was set to false or not specified.

3.19. Language Settings

Device implementations:

[C-0-1] MUST NOT provide any user affordance to select gender-specific language treatment for languages that do not support gender specific translations. Refer to grammatical resources for more information.

4. Application Packaging Compatibility

Devices implementations:

[C-0-1] MUST be capable of installing and running Android ".apk" files as generated by the "aapt" tool included in the official Android SDK.
- As the above requirement may be challenging, device implementations are RECOMMENDED to use the AOSP reference implementation's package management system.
[C-0-2] MUST support verifying ".apk" files using the APK Signature Scheme v3.1, APK Signature Scheme v3, APK Signature Scheme v2 and JAR signing.
[C-0-3] MUST NOT extend either the .apk, Android Manifest, Dalvik bytecode, or RenderScript bytecode formats in such a way that would prevent those files from installing and running correctly on other compatible devices.
[C-0-4] MUST NOT allow apps other than the current "installer of record" for the package to silently uninstall the app without any user confirmation, as documented in the SDK for the DELETE_PACKAGE permission. The only exceptions are the system package verifier app handling PACKAGE_NEEDS_VERIFICATION intent and the storage manager app handling ACTION_MANAGE_STORAGE intent.
[C-0-5] MUST have an activity that handles the android.settings.MANAGE_UNKNOWN_APP_SOURCES intent.
[C-0-6] MUST NOT install application packages from unknown sources, unless the app that requests the installation meets all the following requirements:
- It MUST declare the REQUEST_INSTALL_PACKAGES permission or have the android:targetSdkVersion set at 24 or lower.
- It MUST have been granted permission by the user to install apps from unknown sources.
SHOULD provide a user affordance to grant/revoke the permission to install apps from unknown sources per application, but MAY choose to implement this as a no-op and return RESULT_CANCELED for startActivityForResult(), if the device implementation does not want to allow users to have this choice. However, even in such cases, they SHOULD indicate to the user why there is no such choice presented.
[C-0-7] MUST display a warning dialog with the warning string that is provided through the system API PackageManager.setHarmfulAppWarning to the user before launching an activity in an application that has been marked by the same system API PackageManager.setHarmfulAppWarning as potentially harmful.
SHOULD provide a user affordance to choose to uninstall or launch an application on the warning dialog.
[C-0-8] MUST implement support for Incremental File System as documented here.
[C-0-9] MUST support verifying .apk files using the APK Signature Scheme v4 and APK Signature Scheme v4.1.

5. Multimedia Compatibility

Device implementations:

[C-0-1] MUST support the media formats, encoders, decoders, file types, and container formats defined in section 5.1 for each and every codec declared by MediaCodecList.
[C-0-2] MUST declare and report support of the encoders, decoders available to third-party applications via MediaCodecList.
[C-0-3] MUST be able to properly decode and make available to third-party apps all the formats it can encode. This includes all bitstreams that its encoders generate and the profiles reported in its CamcorderProfile.

Device implementations:

SHOULD aim for minimum codec latency, in others words, they
- SHOULD NOT consume and store input buffers and return input buffers only once processed.
- SHOULD NOT hold onto decoded buffers for longer than as specified by the standard (e.g. SPS).
- SHOULD NOT hold onto encoded buffers longer than required by the GOP structure.

All of the codecs listed in the section below are provided as software implementations in the preferred Android implementation from the Android Open Source Project.

Please note that neither Google nor the Open Handset Alliance make any representation that these codecs are free from third-party patents. Those intending to use this source code in hardware or software products are advised that implementations of this code, including in open source software or shareware, may require patent licenses from the relevant patent holders.

5.1. Media Codecs

5.1.1. Audio Encoding

See more details in 5.1.3. Audio Codecs Details.

If device implementations declare android.hardware.microphone, they MUST support encoding the following audio formats and make them available to third-party apps:

[C-1-1] PCM/WAVE
[C-1-2] FLAC
[C-1-3] Opus

All audio encoders MUST support:

[C-3-1] PCM 16-bit native byte order audio frames via the android.media.MediaCodec API.

5.1.2. Audio Decoding

See more details in 5.1.3. Audio Codecs Details.

If device implementations declare support for the android.hardware.audio.output feature, they must support decoding the following audio formats:

[C-1-1] MPEG-4 AAC Profile (AAC LC)
[C-1-2] MPEG-4 HE AAC Profile (AAC+)
[C-1-3] MPEG-4 HE AACv2 Profile (enhanced AAC+)
[C-1-4] AAC ELD (enhanced low delay AAC)
[C-1-11] xHE-AAC (ISO/IEC 23003-3 Extended HE AAC Profile, which includes the USAC Baseline Profile, and ISO/IEC 23003-4 Dynamic Range Control Profile)
[C-1-5] FLAC
[C-1-6] MP3
[C-1-7] MIDI
[C-1-8] Vorbis
[C-1-9] PCM/WAVE including high-resolution audio formats up to 24 bits, 192 kHz sample rate, and 8 channels. Note that this requirement is for decoding only, and that a device is permitted to downsample and downmix during the playback phase.
[C-1-10] Opus

If device implementations support the decoding of AAC input buffers of multichannel streams (i.e. more than two channels) to PCM through the default AAC audio decoder in the android.media.MediaCodec API, the following MUST be supported:

[C-2-1] Decoding MUST be performed without downmixing (e.g. a 5.0 AAC stream must be decoded to five channels of PCM, a 5.1 AAC stream must be decoded to six channels of PCM).
[C-2-2] Dynamic range metadata MUST be as defined in "Dynamic Range Control (DRC)" in ISO/IEC 14496-3, and the android.media.MediaFormat DRC keys to configure the dynamic range-related behaviors of the audio decoder. The AAC DRC keys were introduced in API 21, and are: KEY_AAC_DRC_ATTENUATION_FACTOR, KEY_AAC_DRC_BOOST_FACTOR, KEY_AAC_DRC_HEAVY_COMPRESSION, KEY_AAC_DRC_TARGET_REFERENCE_LEVEL and KEY_AAC_ENCODED_TARGET_LEVEL.
[C-SR-1] It is STRONGLY RECOMMENDED that requirements C-2-1 and C-2-2 above are satisfied by all AAC audio decoders.

When decoding USAC audio, MPEG-D (ISO/IEC 23003-4):

[C-3-1] Loudness and DRC metadata MUST be interpreted and applied according to MPEG-D DRC Dynamic Range Control Profile Level 1.
[C-3-2] The decoder MUST behave according to the configuration set with the following android.media.MediaFormat keys: KEY_AAC_DRC_TARGET_REFERENCE_LEVEL and KEY_AAC_DRC_EFFECT_TYPE.

MPEG-4 AAC, HE AAC, and HE AACv2 profile decoders:

MAY support loudness and dynamic range control using ISO/IEC 23003-4 Dynamic Range Control Profile.

If ISO/IEC 23003-4 is supported and if both ISO/IEC 23003-4 and ISO/IEC 14496-3 metadata are present in a decoded bitstream, then:

ISO/IEC 23003-4 metadata SHALL take precedence.

All audio decoders MUST support outputting:

[C-6-1] PCM 16-bit native byte order audio frames via the android.media.MediaCodec API.

[C-7-1] MUST be able to be configured by the application using the decoding with the key KEY_MAX_OUTPUT_CHANNEL_COUNT to control whether the content is downmixed to stereo (when using a value of 2) or is output using the native number of channels (when using a value equal or greater to that number). For instance a value of 6 or greater would configure a decoder to output 6 channels when fed 5.1 content.
[C-7-2] When decoding, the decoder MUST advertise the channel mask being used on the output format with the KEY_CHANNEL_MASK key, using the android.media.AudioFormat constants (example: CHANNEL_OUT_5POINT1).

If device implementations support audio decoders other than the default AAC audio decoder and are capable of outputting multi-channel audio (i.e. more than 2 channels) when fed compressed multi-channel content, then:

[C-SR-2] The decoder is STRONGLY RECOMMENDED to be able to be configured by the application using the decoding with the key KEY_MAX_OUTPUT_CHANNEL_COUNT to control whether the content is downmixed to stereo (when using a value of 2) or is output using the native number of channels (when using a value equal or greater to that number). For instance a value of 6 or greater would configure a decoder to output 6 channels when fed 5.1 content.
[C-SR-3] When decoding, the decoder is STRONGLY RECOMMENDED to advertise the channel mask being used on the output format with the KEY_CHANNEL_MASK key, using the android.media.AudioFormat constants (example: CHANNEL_OUT_5POINT1).

5.1.3. Audio Codecs Details

Format/Codec	Details	File Types/Container Formats to be supported
G.711 μ-law and A-law	Support for mono/stereo/5.1 content sampled at 8 kHz	WAVE (.wav)
MPEG-4 AAC Profile (AAC LC)	Support for mono/stereo/5.0/5.1 content with standard sampling rates from 8 to 48 kHz.	3GPP (.3gp) MPEG-4 (.mp4, .m4a) ADTS raw AAC (.aac, ADIF not supported) MPEG-TS (.ts, not seekable, decode only) Matroska (.mkv, decode only)
MPEG-4 HE AAC Profile (AAC+)	Support for mono/stereo/5.0/5.1 content with standard sampling rates from 16 to 48 kHz.	3GPP (.3gp) MPEG-4 (.mp4, .m4a)
MPEG-4 HE AACv2 Profile (enhanced AAC+)	Support for mono/stereo/5.0/5.1 content with standard sampling rates from 16 to 48 kHz.	3GPP (.3gp) MPEG-4 (.mp4, .m4a)
AAC ELD (enhanced low delay AAC)	Support for mono/stereo content with standard sampling rates from 16 to 48 kHz.	3GPP (.3gp) MPEG-4 (.mp4, .m4a)
USAC	Support for mono/stereo content with standard sampling rates from 7.35 to 48 kHz.	MPEG-4 (.mp4, .m4a)
AMR-NB	4.75 to 12.2 kbps sampled @ 8 kHz	3GPP (.3gp)
AMR-WB	9 rates from 6.60 kbit/s to 23.85 kbit/s sampled @ 16 kHz, as defined at AMR-WB, Adaptive Multi-Rate - Wideband Speech Codec	3GPP (.3gp)
FLAC	For both encoder and decoder: at least Mono and Stereo modes MUST be supported. Sample rates up to 192 kHz MUST be supported; 16-bit and 24-bit resolution MUST be supported. FLAC 24-bit audio data handling MUST be available with floating point audio configuration.	FLAC (.flac) MPEG-4 (.mp4, .m4a, decode only) Matroska (.mkv, decode only)
MP3	Mono/Stereo 8-320Kbps constant (CBR) or variable bitrate (VBR)	MP3 (.mp3) MPEG-4 (.mp4, .m4a, decode only) Matroska (.mkv, decode only)
MIDI	MIDI Type 0 and 1. DLS Version 1 and 2. XMF and Mobile XMF. Support for ringtone formats RTTTL/RTX, OTA, and iMelody	Type 0 and 1 (.mid, .xmf, .mxmf) RTTTL/RTX (.rtttl, .rtx) iMelody (.imy)
Vorbis	Decoding: Support for mono, stereo, 5.0 and 5.1 content with sampling rates of 8000, 12000, 16000, 24000, and 48000 Hz. Encoding: Support for mono and stereo content with sampling rates of 8000, 12000, 16000, 24000, and 48000 Hz.	Ogg (.ogg) MPEG-4 (.mp4, .m4a, decode only) Matroska (.mkv) Webm (.webm)
PCM/WAVE	PCM codec MUST support 16-bit linear PCM and 16-bit float. WAVE extractor must support 16-bit, 24-bit, 32-bit linear PCM and 32-bit float (rates up to limit of hardware). Sampling rates MUST be supported from 8 kHz to 192 kHz.	WAVE (.wav)
Opus	Decoding: Support for mono, stereo, 5.0 and 5.1 content with sampling rates of 8000, 12000, 16000, 24000, and 48000 Hz. Encoding: Support for mono and stereo content with sampling rates of 8000, 12000, 16000, 24000, and 48000 Hz.	Ogg (.ogg) MPEG-4 (.mp4, .m4a, decode only) Matroska (.mkv) Webm (.webm)

5.1.4. Image Encoding

See more details in 5.1.6. Image Codecs Details.

Device implementations MUST support encoding the following image encoding:

[C-0-1] JPEG
[C-0-2] PNG
[C-0-3] WebP
[C-0-4] AVIF
- Devices must support BITRATE_MODE_CQ and Baseline Profile.

If device implementations support HEIC encoding via android.media.MediaCodec for media type MIMETYPE_IMAGE_ANDROID_HEIC, they:

[C-1-1] MUST provide a hardware-accelerated HEVC encoder codec that supports BITRATE_MODE_CQ bitrate control mode, HEVCProfileMainStill profile and 512 x 512 px frame size.

5.1.5. Image Decoding

See more details in 5.1.6. Image Codecs Details.

Device implementations MUST support decoding the following image encoding:

[C-0-1] JPEG
[C-0-2] GIF
[C-0-3] PNG
[C-0-4] BMP
[C-0-5] WebP
[C-0-6] Raw
[C-0-7] AVIF (Baseline Profile)

If device implementations support HEVC video decoding, they:

[C-1-1] MUST support HEIF (HEIC) image decoding.

Image decoders that support a high bit-depth format (9+ bits per channel):

[C-2-1] MUST support outputting an 8-bit equivalent format if requested by the application, for example, via the ARGB_8888 config of android.graphics.Bitmap.

5.1.6. Image Codecs Details

Format/Codec	Details	Supported File Types/Container Formats
JPEG	Base+progressive	JPEG (.jpg)
GIF		GIF (.gif)
PNG		PNG (.png)
BMP		BMP (.bmp)
WebP		WebP (.webp)
Raw		ARW (.arw), CR2 (.cr2), DNG (.dng), NEF (.nef), NRW (.nrw), ORF (.orf), PEF (.pef), RAF (.raf), RW2 (.rw2), SRW (.srw)
HEIF	Image, Image collection, Image sequence	HEIF (.heif), HEIC (.heic)
AVIF (Baseline Profile)	Image, Image collection, Image sequence Baseline Profile	HEIF container (.avif)

Image encoder and decoders exposed through the MediaCodec API

[C-1-1] MUST support YUV420 8:8:8 flexible color format (COLOR_FormatYUV420Flexible) through CodecCapabilities.
[C-SR-1] STRONGLY RECOMMENDED to support RGB888 color format for input Surface mode.
[C-1-3] MUST support at least one of a planar or semiplanar YUV420 8:8:8 color format: COLOR_FormatYUV420PackedPlanar (equivalent to COLOR_FormatYUV420Planar) or COLOR_FormatYUV420PackedSemiPlanar (equivalent to COLOR_FormatYUV420SemiPlanar). They are STRONGLY RECOMMENDED to support both.

5.1.7. Video Codecs

For acceptable quality of web video streaming and video-conference services, device implementations SHOULD use a hardware VP8 codec that meets the requirements.

If device implementations include a video decoder or encoder:

[C-1-1] Video codecs MUST support output and input bytebuffer sizes that accommodate the largest feasible compressed and uncompressed frame as dictated by the standard and configuration but also not overallocate.
[C-1-2] Video encoders and decoders MUST support YUV420 8:8:8 flexible color formats (COLOR_FormatYUV420Flexible) through CodecCapabilities.
[C-1-3] Video encoders and decoders MUST support at least one of a planar or semiplanar YUV420 8:8:8 color format: COLOR_FormatYUV420PackedPlanar (equivalent to COLOR_FormatYUV420Planar) or COLOR_FormatYUV420PackedSemiPlanar (equivalent to COLOR_FormatYUV420SemiPlanar). They are STRONGLY RECOMMENDED to support both.
[C-SR-1] Video encoders and decoders are STRONGLY RECOMMENDED to support at least one of a hardware optimized planar or semiplanar YUV420 8:8:8 color format (YV12, NV12, NV21 or equivalent vendor optimized format.)
[C-1-5] Video decoders that support a high bit-depth format (9+ bits per channel) MUST support outputting an 8-bit equivalent format if requested by the application. This MUST be reflected by supporting an YUV420 8:8:8 color format via android.media.MediaCodecInfo.

If device implementations advertise HDR profile support through Display.HdrCapabilities, they:

[C-2-1] MUST support HDR static metadata parsing and handling.

If device implementations advertise intra refresh support through FEATURE_IntraRefresh in the MediaCodecInfo.CodecCapabilities class, they:

[C-3-1] MUST support the refresh periods in the range of 10 - 60 frames and accurately operate within 20% of configured refresh period.

Unless the application specifies otherwise using the KEY_COLOR_FORMAT format key, video decoder implementations:

[C-4-1] MUST default to the color format optimized for hardware display if configured using Surface output.
[C-4-2] MUST default to a YUV420 8:8:8 color format optimized for CPU reading if configured to not use Surface output.

5.1.8. Video Codecs List

Format/Codec	Details	File Types/Container Formats to be supported
H.263		3GPP (.3gp) MPEG-4 (.mp4) Matroska (.mkv, decode only)
H.264 AVC	See section 5.2 and 5.3 for details	3GPP (.3gp) MPEG-4 (.mp4) MPEG-2 TS (.ts, not seekable) Matroska (.mkv, decode only)
H.265 HEVC	See section 5.3 for details	MPEG-4 (.mp4) Matroska (.mkv, decode only)
MPEG-2	Main Profile	MPEG2-TS (.ts, not seekable) MPEG-4 (.mp4, decode only) Matroska (.mkv, decode only)
MPEG-4 SP		3GPP (.3gp) MPEG-4 (.mp4) Matroska (.mkv, decode only)
VP8	See section 5.2 and 5.3 for details	WebM (.webm) Matroska (.mkv)
VP9	See section 5.3 for details	WebM (.webm) Matroska (.mkv)
AV1	See section 5.2 and section 5.3 for details	MPEG-4 (.mp4) Matroska (.mkv, decode only)

5.1.9. Media Codec Security

Device implementations MUST ensure compliance with media codec security features as described below.

Android includes support for OMX, a cross-platform multimedia acceleration API, as well as Codec 2.0, a low-overhead multimedia acceleration API.

If device implementations support multimedia, they:

[C-1-1] MUST provide support for media codecs either via OMX or Codec 2.0 APIs (or both) as in the Android Open Source Project and not disable or circumvent the security protections. This specifically does not mean that every codec MUST use either the OMX or Codec 2.0 API, only that support for at least one of these APIs MUST be available, and support for the available APIs MUST include the security protections present.
[C-SR-1] Are STRONGLY RECOMMENDED to include support for Codec 2.0 API.

If device implementations do not support the Codec 2.0 API, they:

[C-2-1] MUST include the corresponding OMX software codec from the Android Open Source Project (if it is available) for each media format and type (encoder or decoder) supported by the device.
[C-2-2] Codecs that have names starting with "OMX.google." MUST be based on their Android Open Source Project source code.
[C-SR-2] Are STRONGLY RECOMMENDED that the OMX software codecs run in a codec process that does not have access to hardware drivers other than memory mappers.

If device implementations support Codec 2.0 API, they:

[C-3-1] MUST include the corresponding Codec 2.0 software codec from the Android Open Source Project (if it is available) for each media format and type (encoder or decoder) supported by the device.
[C-3-2] MUST house the Codec 2.0 software codecs in the software codec process as provided in the Android Open Source Project to make it possible to more narrowly grant access to software codecs.
[C-3-3] Codecs that have names starting with "c2.android." MUST be based on their Android Open Source Project source code.

5.1.10. Media Codec Characterization

If device implementations support media codecs, they:

[C-1-1] MUST return correct values of media codec characterization via the MediaCodecInfo API.

In particular:

[C-1-2] Codecs with names starting with "OMX." MUST use the OMX APIs and have names that conform to OMX IL naming guidelines.
[C-1-3] Codecs with names starting with "c2." MUST use the Codec 2.0 API and have names that conform to Codec 2.0 naming guidelines for Android.
[C-1-4] Codecs with names starting with "OMX.google." or "c2.android." MUST NOT be characterized as vendor or as hardware-accelerated.
[C-1-5] Codecs that run in a codec process (vendor or system) that have access to hardware drivers other than memory allocators and mappers MUST NOT be characterized as software-only.
[C-1-6] Codecs not present in the Android Open Source Project or not based on the source code in that project MUST be characterized as vendor.
[C-1-7] Codecs that utilize hardware acceleration MUST be characterized as hardware accelerated.
[C-1-8] Codec names MUST NOT be misleading. For example, codecs named "decoders" MUST support decoding, and those named "encoders" MUST support encoding. Codecs with names containing media formats MUST support those formats.

If device implementations support video codecs:

[C-2-1] All video codecs MUST publish achievable frame rate data for the following sizes if supported by the codec:

	SD (low quality)	SD (high quality)	HD 720p	HD 1080p	UHD
Video resolution	176 x 144 px (H263, MPEG2, MPEG4) 352 x 288 px (MPEG4 encoder, H263, MPEG2) 320 x 180 px (VP8, VP8) 320 x 240 px (other)	704 x 576 px (H263) 640 x 360 px (VP8, VP9) 640 x 480 px (MPEG4 encoder) 720 x 480 px (other, AV1)	1408 x 1152 px (H263) 1280 x 720 px (other, AV1)	1920 x 1080 px (other than MPEG4, AV1)	3840 x 2160 px (HEVC, VP9, AV1)

[C-2-2] Video codecs that are characterized as hardware accelerated MUST publish performance points information. They MUST each list all supported standard performance points (listed in PerformancePoint API), unless they are covered by another supported standard performance point.
Additionally they SHOULD publish extended performance points if they support sustained video performance other than one of the standard ones listed.

5.2. Video Encoding

If device implementations support any video encoder and make it available to third-party apps, and set the
MediaFormat.KEY_BITRATE_MODE to BITRATE_MODE_VBR so that the encoder operates in Variable bitrate mode, then, as long as it does not impact the minimum quality floor, the encoded bitrate :

SHOULD NOT be, over one sliding window, more than 15% over the bitrate between intraframe (I-frame) intervals.
SHOULD NOT be more than 100% over the bitrate over a sliding window of 1 second.

If device implementations support any video encoder and make it available to third-party apps and set the MediaFormat.KEY_BITRATE_MODE to BITRATE_MODE_CBR so the encoder operates in constant bitrate mode, then the encoded bitrate:

[C-SR-2] is STRONGLY RECOMMENDED to NOT be more than 15% over the target bitrate over a sliding window of 1 second.

If device implementations include an embedded screen display with the diagonal length of at least 2.5 inches or include a video output port or declare the support of a camera via the android.hardware.camera.any feature flag, they:

[C-1-1] MUST include the support of at least one of the VP8 or H.264 video encoders, and make it available for third-party applications.
SHOULD support both VP8 and H.264 video encoders, and make it available for third-party applications.

If device implementations support any of the H.264, VP8, VP9 or HEVC video encoders and make it available to third-party applications, they:

[C-2-1] MUST support dynamically configurable bitrates.
SHOULD support variable frame rates, where video encoder SHOULD determine instantaneous frame duration based on the timestamps of input buffers, and allocate its bit bucket based on that frame duration.

If device implementations support the MPEG-4 SP video encoder and make it available to third-party apps, they:

SHOULD support dynamically configurable bitrates for the supported encoder.

If device implementations provide hardware accelerated video or image encoders, and support one or more attached or pluggable hardware camera(s) exposed through the android.camera APIs:

[C-4-1] all hardware accelerated video and image encoders MUST support encoding frames from the hardware camera(s).
SHOULD support encoding frames from the hardware camera(s) through all video or image encoders.

If device implementations provide HDR encoding, they:

[C-SR-1] are STRONGLY RECOMMENDED to provide a plugin for the seamless transcoding API to convert from HDR format to SDR format.

5.2.1. H.263

If device implementations support H.263 encoders and make it available to third-party apps, they:

[C-1-1] MUST support QCIF resolution (176 x 144) using Baseline Profile Level 45. SQCIF resolution is optional.

5.2.2. H.264

If device implementations support H.264 codec, they:

[C-1-1] MUST support Baseline Profile Level 3. However, support for ASO (Arbitrary Slice Ordering), FMO (Flexible Macroblock Ordering) and RS (Redundant Slices) is OPTIONAL. Moreover, to maintain compatibility with other Android devices, it is RECOMMENDED that ASO, FMO and RS are not used for Baseline Profile by encoders.
[C-1-2] MUST support the SD (Standard Definition) video encoding profiles in the following table.
SHOULD support Main Profile Level 4.
SHOULD support the HD (High Definition) video encoding profiles as indicated in the following table.

If device implementations report support of H.264 encoding for 720p or 1080p resolution videos through the media APIs, they:

[C-2-1] MUST support the encoding profiles in the following table.

	SD (Low quality)	SD (High quality)	HD 720p	HD 1080p
Video resolution	320 x 240 px	720 x 480 px	1280 x 720 px	1920 x 1080 px
Video frame rate	20 fps	30 fps	30 fps	30 fps
Video bitrate	384 Kbps	2 Mbps	4 Mbps	10 Mbps

5.2.3. VP8

If device implementations support VP8 codec, they:

[C-1-1] MUST support the SD video encoding profiles.
SHOULD support the following HD (High Definition) video encoding profiles.
[C-1-2] MUST support writing Matroska WebM files.
SHOULD provide a hardware VP8 codec that meets the WebM project RTC hardware coding requirements, to ensure acceptable quality of web video streaming and video-conference services.

If device implementations report support of VP8 encoding for 720p or 1080p resolution videos through the media APIs, they:

[C-2-1] MUST support the encoding profiles in the following table.

	SD (Low quality)	SD (High quality)	HD 720p	HD 1080p
Video resolution	320 x 180 px	640 x 360 px	1280 x 720 px	1920 x 1080 px
Video frame rate	30 fps	30 fps	30 fps	30 fps
Video bitrate	800 Kbps	2 Mbps	4 Mbps	10 Mbps

5.2.4. VP9

If device implementations support VP9 codec, they:

[C-1-2] MUST support Profile 0 Level 3.
[C-1-1] MUST support writing Matroska WebM files.
[C-1-3] MUST generate CodecPrivate data.
SHOULD support the HD decoding profiles as indicated in the following table.
[C-SR-1] are STRONGLY RECOMMENDED to support the HD decoding profiles as indicated in the following table if there is a hardware encoder.

	SD	HD 720p	HD 1080p	UHD
Video resolution	720 x 480 px	1280 x 720 px	1920 x 1080 px	3840 x 2160 px
Video frame rate	30 fps	30 fps	30 fps	30 fps
Video bitrate	1.6 Mbps	4 Mbps	5 Mbps	20 Mbps

If device implementations claim to support Profile 2 or Profile 3 through the Media APIs:

Support for 12-bit format is OPTIONAL.

5.2.5. H.265

If device implementations support H.265 codec, they:

[C-1-1] MUST support Main Profile Level 3 up to 512 x 512 resolution.
[C-SR-1] are STRONGLY RECOMMENDED to support the 720 x 480 SD profile and the HD encoding profiles as indicated in the following table if there is a hardware encoder.

	SD	HD 720p	HD 1080p	UHD
Video resolution	720 x 480 px	1280 x 720 px	1920 x 1080 px	3840 x 2160 px
Video frame rate	30 fps	30 fps	30 fps	30 fps
Video bitrate	1.6 Mbps	4 Mbps	5 Mbps	20 Mbps

5.2.6. AV1

If device implementations support AV1 codec then, they:

[C-1-1] MUST support Main Profile including 8-bit and 10-bit content.
[C-1-2] MUST publish performance data i.e. report performance data via the getSupportedFrameRatesFor() or getSupportedPerformancePoints() APIs for supported resolutions in the table below.
[C-1-3] MUST accept HDR metadata and output it to the bitstream

If AV1 encoder is hardware accelerated, then it:

[C-2-1] MUST support up to and including HD1080p encoding profile from the table below:

	SD	HD 720p	HD 1080p	UHD
Video resolution	720 x 480 px	1280 x 720 px	1920 x 1080 px	3840 x 2160 px
Video frame rate	30 fps	30 fps	30 fps	30 fps
Video bitrate	5 Mbps	8 Mbps	16 Mbps	50 Mbps

5.3. Video Decoding

If device implementations support VP8, VP9, H.264, or H.265 codecs, they:

[C-1-1] MUST support dynamic video resolution and frame rate switching through the standard Android APIs within the same stream for all VP8, VP9, H.264, and H.265 codecs in real time and up to the maximum resolution supported by each codec on the device.

5.3.1. MPEG-2

If device implementations support MPEG-2 decoders, they:

[C-1-1] MUST support the Main Profile High Level.

5.3.2. H.263

If device implementations support H.263 decoders, they:

[C-1-1] MUST support Baseline Profile Level 30 (CIF, QCIF and SQCIF resolutions @ 30fps 384kbps) and Level 45 (QCIF and SQCIF resolutions @ 30fps 128kbps).

5.3.3. MPEG-4

If device implementations with MPEG-4 decoders, they:

[C-1-1] MUST support Simple Profile Level 3.

5.3.4. H.264

If device implementations support H.264 decoders, they:

[C-1-1] MUST support Main Profile Level 3.1 and Baseline Profile. Support for ASO (Arbitrary Slice Ordering), FMO (Flexible Macroblock Ordering) and RS (Redundant Slices) is OPTIONAL.
[C-1-2] MUST be capable of decoding videos with the SD (Standard Definition) profiles listed in the following table and encoded with the Baseline Profile and Main Profile Level 3.1 (including 720p30).
SHOULD be capable of decoding videos with the HD (High Definition) profiles as indicated in the following table.

If the height that is reported by the Display.getSupportedModes() method is equal or greater than the video resolution, device implementations:

[C-2-1] MUST support the HD 720p video decoding profiles in the following table.
[C-2-2] MUST support the HD 1080p video decoding profiles in the following table.

	SD (Low quality)	SD (High quality)	HD 720p	HD 1080p
Video resolution	320 x 240 px	720 x 480 px	1280 x 720 px	1920 x 1080 px
Video frame rate	30 fps	30 fps	60 fps	30 fps (60 fps^Television)
Video bitrate	800 Kbps	2 Mbps	8 Mbps	20 Mbps

5.3.5. H.265 (HEVC)

If device implementations support H.265 codec, they:

[C-1-1] MUST support the Main Profile Level 3 Main tier and the SD video decoding profiles as indicated in the following table.
SHOULD support the HD decoding profiles as indicated in the following table.
[C-1-2] MUST support the HD decoding profiles as indicated in the following table if there is a hardware decoder.

If the height that is reported by the Display.getSupportedModes() method is equal to or greater than the video resolution, then:

[C-2-1] Device implementations MUST support at least one of H.265 or VP9 decoding of 720, 1080 and UHD profiles.

	SD (Low quality)	SD (High quality)	HD 720p	HD 1080p	UHD
Video resolution	352 x 288 px	720 x 480 px	1280 x 720 px	1920 x 1080 px	3840 x 2160 px
Video frame rate	30 fps	30 fps	30 fps	30/60 fps (60 fps^{Television with H.265 hardware decoding})	60 fps
Video bitrate	600 Kbps	1.6 Mbps	4 Mbps	5 Mbps	20 Mbps

If device implementations claim to support an HDR Profile through the Media APIs:

[C-3-1] Device implementations MUST accept the required HDR metadata from the application, as well as support extracting and outputting the required HDR metadata from the bitstream and/or container.
[C-3-2] Device implementations MUST properly display HDR content on the device screen or on a standard video output port (e.g., HDMI).

5.3.6. VP8

If device implementations support VP8 codec, they:

[C-1-1] MUST support the SD decoding profiles in the following table.
SHOULD use a hardware VP8 codec that meets the requirements.
SHOULD support the HD decoding profiles in the following table.

If the height as reported by the Display.getSupportedModes() method is equal or greater than the video resolution, then:

[C-2-1] Device implementations MUST support 720p profiles in the following table.
[C-2-2] Device implementations MUST support 1080p profiles in the following table.

	SD (Low quality)	SD (High quality)	HD 720p	HD 1080p
Video resolution	320 x 180 px	640 x 360 px	1280 x 720 px	1920 x 1080 px
Video frame rate	30 fps	30 fps	30 fps (60 fps^Television)	30 (60 fps^Television)
Video bitrate	800 Kbps	2 Mbps	8 Mbps	20 Mbps

5.3.7. VP9

If device implementations support VP9 codec, they:

[C-1-1] MUST support the SD video decoding profiles as indicated in the following table.
SHOULD support the HD decoding profiles as indicated in the following table.

If device implementations support VP9 codec and a hardware decoder:

[C-2-1] MUST support the HD decoding profiles as indicated in the following table.

If the height that is reported by the Display.getSupportedModes() method is equal to or greater than the video resolution, then:

[C-3-1] Device implementations MUST support at least one of VP9 or H.265 decoding of the 720, 1080 and UHD profiles.

	SD (Low quality)	SD (High quality)	HD 720p	HD 1080p	UHD
Video resolution	320 x 180 px	640 x 360 px	1280 x 720 px	1920 x 1080 px	3840 x 2160 px
Video frame rate	30 fps	30 fps	30 fps	30 fps (60 fps^{Television with VP9 hardware decoding})	60 fps
Video bitrate	600 Kbps	1.6 Mbps	4 Mbps	5 Mbps	20 Mbps

If device implementations claim to support VP9Profile2 or VP9Profile3 through the 'CodecProfileLevel' media APIs:

Support for 12-bit format is OPTIONAL.

If device implementations claim to support an HDR Profile (VP9Profile2HDR, VP9Profile2HDR10Plus, VP9Profile3HDR, VP9Profile3HDR10Plus) through the media APIs:

[C-4-1] Device implementations MUST accept the required HDR metadata (KEY_HDR_STATIC_INFO for all HDR profiles, as well as 'KEY_HDR10_PLUS_INFO' for HDR10Plus profiles) from the application. They also MUST support extracting and outputting the required HDR metadata from the bitstream and/or container.
[C-4-2] Device implementations MUST properly display HDR content on the device screen or on a standard video output port (e.g., HDMI).

5.3.8. Dolby Vision

If device implementations declare support for the Dolby Vision decoder through HDR_TYPE_DOLBY_VISION, they:

[C-1-1] MUST provide a Dolby Vision-capable extractor.
[C-1-2] MUST properly display Dolby Vision content either on the device screen or on an external display attached via a standard video output port (such as HDMI).
[C-1-3] MUST set the track ID of backward-compatible base-layer(s) (if present) to be the same as the combined Dolby Vision layer's track ID.

5.3.9. AV1

If device implementations support AV1 codec and make it available to third-party applications, they:

[C-1-1] MUST support Main Profile including 8-bit and 10-bit content.

If device implementations provide support for AV1 codec with a hardware accelerated decoder then they:

[C-2-1] MUST be able to decode at least HD 720p video decoding profiles from the table below when the height reported by Display.getSupportedModes() method is equal or greater than 720p.
[C-2-2] MUST be able to decode at least HD 1080p video decoding profiles from the table below when the height reported by Display.getSupportedModes() method is equal or greater than 1080p.

	SD	HD 720p	HD 1080p	UHD
Video resolution	720 x 480 px	1280 x 720 px	1920 x 1080 px	3840 x 2160 px
Video frame rate	30 fps	30 fps	30 fps	30 fps
Video bitrate	5 Mbps	8 Mbps	16 Mbps	50 Mbps

If device implementations support HDR Profile through the Media APIs, then they:

[C-3-1] MUST support extracting and outputting HDR metadata from the bitstream and/or container.
[C-3-2] MUST properly display HDR content on the device screen or on a standard video output port (for example, HDMI).

5.4. Audio Recording

While some of the requirements outlined in this section are listed as SHOULD since Android 4.3, the Compatibility Definition for future versions are planned to change these to MUST. Existing and new Android devices are STRONGLY RECOMMENDED to meet these requirements that are listed as SHOULD, or they will not be able to attain Android compatibility when upgraded to the future version.

5.4.1. Raw Audio Capture and Microphone Information

If device implementations declare android.hardware.microphone, they:

[C-1-1] MUST allow capture of raw audio content for any AudioRecord or AAudio INPUT stream that is opened successfully. At a minimum, the following characteristics MUST be supported:
- Format: Linear PCM, 16-bit
- Sampling rates: 8000, 11025, 16000, 44100, 48000 Hz
- Channels: Mono
- Audio Sources: DEFAULT, MIC, CAMCORDER, VOICE_RECOGNITION, VOICE_COMMUNICATION, UNPROCESSED, or VOICE_PERFORMANCE. This also applies to the equivalent Input Presets in AAudio, for example, AAUDIO_INPUT_PRESET_CAMCORDER.
SHOULD allow capture of raw audio content with the following characteristics:
- Format: Linear PCM, 16-bit and 24-bit
- Sampling rates: 8000, 11025, 16000, 22050, 24000, 32000, 44100, 48000 Hz
- Channels: As many channels as the number of microphones on the device
[C-1-2] MUST capture at above sample rates without up-sampling.
[C-1-3] MUST include an appropriate anti-aliasing filter when the sample rates given above are captured with down-sampling.
SHOULD allow AM radio and DVD quality capture of raw audio content, which means the following characteristics:
- Format: Linear PCM, 16-bit
- Sampling rates: 22050, 48000 Hz
- Channels: Stereo
[C-1-4] MUST honor the MicrophoneInfo API and properly fill in information for the available microphones on device accessible to the third-party applications via the AudioManager.getMicrophones() API, for active AudioRecord using MediaRecorder.AudioSources DEFAULT, MIC, CAMCORDER, VOICE_RECOGNITION, VOICE_COMMUNICATION, UNPROCESSED, or VOICE_PERFORMANCE. If device implementations allow AM radio and DVD quality capture of raw audio content, they:
[C-2-1] MUST capture without up-sampling at any ratio higher than 16000:22050 or 44100:48000.
[C-2-2] MUST include an appropriate anti-aliasing filter for any up-sampling or down-sampling.

5.4.2. Capture for Voice Recognition

If device implementations declare android.hardware.microphone, they:

[C-1-1] MUST capture android.media.MediaRecorder.AudioSource.VOICE_RECOGNITION audio source at one of the sampling rates, 44100 and 48000.
[C-1-2] MUST, by default, disable any noise reduction audio processing when recording an audio stream from the AudioSource.VOICE_RECOGNITION audio source.
[C-1-3] MUST, by default, disable any automatic gain control when recording an audio stream from the AudioSource.VOICE_RECOGNITION audio source.
SHOULD exhibit approximately flat amplitude-versus-frequency characteristics in the mid-frequency range: specifically ±3dB from 100 Hz to 4000 Hz for each and every microphone used to record the voice recognition audio source.
[C-SR-1] are STRONGLY RECOMMENDED to exhibit amplitude levels in the low frequency range: specifically from ±20 dB from 30 Hz to 100 Hz compared to the mid-frequency range for each and every microphone used to record the voice recognition audio source.
[C-SR-2] are STRONGLY RECOMMENDED to exhibit amplitude levels in the high frequency range: specifically from ±30 dB from 4000 Hz to 22 KHz compared to the mid-frequency range for each and every microphone used to record the voice recognition audio source.
SHOULD set audio input sensitivity such that a 1000 Hz sinusoidal tone source played at 90 dB Sound Pressure Level (SPL) (measured next to the microphone) yields an ideal response of RMS 2500 within a range of 1770 and 3530 for 16 bit-samples (or -22.35 db ±3dB Full Scale for floating point/double precision samples) for each and every microphone used to record the voice recognition audio source.
SHOULD record the voice recognition audio stream so that the PCM amplitude levels linearly track input SPL changes over at least a 30 dB range from -18 dB to +12 dB re 90 dB SPL at the microphone.
SHOULD record the voice recognition audio stream with total harmonic distortion (THD) less than 1% for 1 kHz at 90 dB SPL input level at the microphone.

If device implementations declare android.hardware.microphone and noise suppression (reduction) technologies tuned for speech recognition, they:

[C-2-1] MUST allow this audio effect to be controllable with the android.media.audiofx.NoiseSuppressor API.
[C-2-2] MUST uniquely identify each noise suppression technology implementation via the AudioEffect.Descriptor.uuid field.

5.4.3. Capture for Rerouting of Playback

The android.media.MediaRecorder.AudioSource class includes the REMOTE_SUBMIX audio source.

If device implementations declare both android.hardware.audio.output and android.hardware.microphone, they:

[C-1-1] MUST properly implement the REMOTE_SUBMIX audio source so that when an application uses the android.media.AudioRecord API to record from this audio source, it captures a mix of all audio streams except for the following:
- AudioManager.STREAM_RING
- AudioManager.STREAM_ALARM
- AudioManager.STREAM_NOTIFICATION

5.4.4. Acoustic Echo Canceler

If device implementations declare android.hardware.microphone, they:

SHOULD implement an Acoustic Echo Canceler (AEC) technology tuned for voice communication and applied to the capture path when capturing using AudioSource.VOICE_COMMUNICATION.

If device implementations provides an Acoustic Echo Canceler which is inserted in the capture audio path when AudioSource.VOICE_COMMUNICATION is selected, they:

[C-SR-1] are STRONGLY_RECOMMENDED to declare this via AcousticEchoCanceler API method AcousticEchoCanceler.isAvailable()
[C-SR-2] are STRONGLY_RECOMMENDED to allow this audio effect to be controllable with the AcousticEchoCanceler API.
[C-SR-3] are STRONGLY_RECOMMENDED to uniquely identify each AEC technology implementation via the AudioEffect.Descriptor.uuid field.

5.4.5. Concurrent Capture

If device implementations declare android.hardware.microphone, they MUST implement concurrent capture as described in this document. Specifically:

[C-1-1] MUST allow concurrent access to microphone by an accessibility service capturing with AudioSource.VOICE_RECOGNITION and at least one application capturing with any AudioSource.
[C-1-2] MUST allow concurrent access to microphone by a pre-installed application that holds an Assistant role and at least one application capturing with any AudioSource except for AudioSource.VOICE_COMMUNICATION or AudioSource.CAMCORDER.
[C-1-3] MUST silence the audio capture for any other application, except for an accessibility service, while an application is capturing with AudioSource.VOICE_COMMUNICATION or AudioSource.CAMCORDER. However, when an app is capturing via AudioSource.VOICE_COMMUNICATION then another app can capture the voice call if it is a privileged (pre-installed) app with permission CAPTURE_AUDIO_OUTPUT.
[C-1-4] If two or more applications are capturing concurrently and if neither app has an UI on top, the one that started capture the most recently receives audio.

5.5. Audio Playback

Android includes the support to allow apps to playback audio through the audio output peripheral as defined in section 7.8.2.

5.5.1. Raw Audio Playback

If device implementations declare android.hardware.audio.output, they:

[C-1-1] MUST allow playback of raw audio content with the following characteristics:
- Source formats: Linear PCM, 16-bit, 8-bit, float
- Channels: Mono, Stereo, valid multichannel configurations with up to 8 channels
- Sampling rates (in Hz):
  - 8000, 11025, 16000, 22050, 24000, 32000, 44100, 48000 at the channel configurations listed above
  - 96000 in mono and stereo

5.5.2. Audio Effects

Android provides an API for audio effects for device implementations.

If device implementations declare the feature android.hardware.audio.output, they:

[C-1-1] MUST support the EFFECT_TYPE_EQUALIZER and EFFECT_TYPE_LOUDNESS_ENHANCER implementations controllable through the AudioEffect subclasses Equalizer and LoudnessEnhancer.
[C-1-2] MUST support the visualizer API implementation, controllable through the Visualizer class.
[C-1-3] MUST support the EFFECT_TYPE_DYNAMICS_PROCESSING implementation controllable through the AudioEffect subclass DynamicsProcessing.
[C-1-4] MUST support audio effects with floating-point input and output, when the effect results are returned to the framework audio pipeline. This refers to typical insert or aux effects such as the equalizer. Equivalent behavior is strongly recommended when the effect results aren't visible by the framework audio pipeline, such as post-processing or offloaded effects.
[C-1-5] MUST make sure that audio effects support multiple channels up to the mixer channel count also known as FCC_LIMIT, when the effect results are returned to the framework audio pipeline. This refers to typical insert or aux effects, but excludes special effects such as downmix, upmix, or spatialization effects which change the channel count. Equivalent behavior is recommended when the effects aren't visible by the framework audio pipeline, such as post-processing or offloaded effects.
SHOULD support the EFFECT_TYPE_BASS_BOOST, EFFECT_TYPE_ENV_REVERB, EFFECT_TYPE_PRESET_REVERB, and EFFECT_TYPE_VIRTUALIZER implementations controllable through the AudioEffect sub-classes BassBoost, EnvironmentalReverb, PresetReverb, and Virtualizer.
[C-SR-1] Are STRONGLY RECOMMENDED to support effects in floating-point and multichannel.

5.5.3. Audio Output Volume

Automotive device implementations:

SHOULD allow adjusting audio volume separately per each audio stream using the content type or usage as defined by AudioAttributes and car audio usage as publicly defined in android.car.CarAudioManager.

5.5.4. Audio Offload

If device implementations support audio offload playback, they:

[C-SR-1] Are STRONGLY RECOMMENDED to trim the played gapless audio content between two clips with the same format when specified by the AudioTrack gapless API and the media container for MediaPlayer.

[C-SR-2] Are STRONGLY RECOMMENDED to implement offload playback for AAC, MP3, OPUS, and PCM formats.

5.6. Audio Latency

Audio latency is the time delay as an audio signal passes through a system. Many classes of applications rely on short latencies, to achieve real-time sound effects.

For the purposes of this section, use the following definitions:

output latency. The interval between when an application writes a frame of PCM-coded data and when the corresponding sound is presented to the environment at an on-device transducer or the signal leaves the device via a port and can be observed externally.
cold output latency. The time between starting an output stream and the presentation time of the first frame based on timestamps, when the audio output system has been idle and powered down prior to the request.
continuous output latency. The output latency for subsequent frames, after the device is playing audio.
input latency. The interval between when a sound is presented by environment to device at an on-device transducer or signal enters the device via a port and when an application reads the corresponding frame of PCM-coded data.
lost input. The initial portion of an input signal that is unusable or unavailable.
cold input latency. The time between starting the stream and when the first valid frame is received, when the audio input system has been idle and powered down prior to the request.
continuous input latency. The input latency for subsequent frames, while the device is capturing audio.
continuous round-trip latency. The sum of continuous input latency plus continuous output latency plus one buffer period. The buffer period allows time for the app to process the signal and time for the app to mitigate phase difference between input and output streams.
OpenSL ES PCM buffer queue API. The set of PCM-related OpenSL ES APIs within Android NDK.
AAudio native audio API. The set of AAudio APIs within Android NDK.
Timestamp. A pair consisting of a relative frame position within a stream and the estimated time when that frame enters or leaves the audio processing pipeline on the associated endpoint. See also AudioTimestamp.
glitch. A temporary interruption or incorrect sample value in the audio signal, typically caused by a buffer underrun for output, buffer overrun for input, or any other source of digital or analog noise.
mean absolute deviation (MAD). The average of the absolute value of the deviations from the mean for a set of values.
tap-to-tone latency (TTL), as measured by CTS Verifier, is the time between when the screen is tapped and when a tone generated as a result of that tap is heard on the speaker. This is averaged over 5 measurements using the AAudio native audio API for output.
round-trip latency (RTL), as measured by the CTS Verifier, is the Mean Continuous latency over 5 measurements, measured over a loopback path that feeds the output back to the input, using the AAudio native audio API.

The loopback paths are:
- Speaker/mic: Built-in speaker to built-in microphone.
- Analog: 3.5mm analog jack and a loopback adapter.
- USB: USB to 3.5mm adapter and a loopback adapter or a USB audio interface and loopback cables.
FEATURE_AUDIO_LOW_LATENCY. The android.hardware.audio.low_latency feature is declared.
FEATURE_AUDIO_PRO. The android.hardware.audio.pro feature is declared.
MPC. Media Performance Class.
head-tracking latency. The time it takes from the head motion captured by the inertial measurement unit (IMU) to the headphone transducers' detection of the change in sound caused by this motion.

If device implementations declare android.hardware.audio.output, they MUST meet or exceed the following requirements:

[C-1-2] Cold output latency of 500 milliseconds or less.
[C-1-3] Opening an output stream using AAudioStreamBuilder_openStream() MUST take less than 1000 milliseconds.
[C-1-4] The calculated round-trip latencies based on input and output timestamps returned by AAudioStream_getTimestamp MUST be within 200 msec of the measured round trip latency for AAUDIO_PERFORMANCE_MODE_NONEandAAUDIO_PERFORMANCE_MODE_LOW_LATENCY` for speakers, wired headsets, and wireless headsets.

If device implementations include android.hardware.microphone, they MUST meet these input audio requirements:

[C-3-2] Cold input latency of 500 milliseconds or less.
[C-3-3] Opening an input stream using AAudioStreamBuilder_openStream() MUST take less than 1000 milliseconds.

The following table defines the requirements for RTL for Handheld device implementations as defined in 2.2.1 that declare android.hardware.audio.output and android.hardware.microphone.

Device and Declarations	RTL (ms)	MAD (ms)	Loopback Paths
Handheld	~~250~~ 200	30 25	speaker/mic, analog 3.5mm (if supported), USB (if supported)
>= MPC_T (13)	80	15	at least one path
FEATURE_AUDIO_LOW_LATENCY	50	10	at least one path
FEATURE_AUDIO_PRO	25	5	at least one path
FEATURE_AUDIO_PRO	20	5	analog (if supported)
FEATURE_AUDIO_PRO	25	5	USB (if analog not supported)

The following table defines the requirements for TTL for Handheld device implementations as defined in 2.2.1 that declare android.hardware.audio.output and android.hardware.microphone.

Device and Declarations	TTL (ms)
Handheld	250
>= MPC_T (13)	80
MPC_S (12)	100
FEATURE_AUDIO_PRO	80

If device implementations include support for spatial audio with head tracking and declare the PackageManager.FEATURE_AUDIO_SPATIAL_HEADTRACKING_LOW_LATENCY flag, they:

[C-4-1] MUST exhibit a maximum head-tracking to audio-update latency of 300 ms.

5.7. Network Protocols

Device implementations MUST support the media network protocols for audio and video playback as specified in the Android SDK documentation.

For each codec and container format that a device implementation is required to support, the device implementation:

[C-1-1] MUST support that codec or container over HTTP and HTTPS.
[C-1-2] MUST support the corresponding media segment formats as shown in the media segment formats table below over HTTP Live Streaming draft protocol, Version 7.
[C-1-3] MUST support the corresponding RTSP payload formats as shown in the RTSP table below. For exceptions please see the table footnotes in section 5.1.

Media Segment Formats

Segment formats	Reference(s)	Required codec support
MPEG-2 Transport Stream	ISO 13818	Video codecs: H264 AVC MPEG-4 SP MPEG-2 See section 5.1.8 for details on H264 AVC, MPEG2-4 SP, and MPEG-2. Audio codecs: AAC See section 5.1.3 for details on AAC and its variants.
AAC with ADTS framing and ID3 tags	ISO 13818-7	See section 5.1.1 for details on AAC and its variants
WebVTT	WebVTT

Segment formats

Reference(s)

Required codec support

MPEG-2 Transport Stream

ISO 13818

Video codecs:

H264 AVC
MPEG-4 SP
MPEG-2

See section 5.1.8 for details on H264 AVC, MPEG2-4 SP,
and MPEG-2.

Audio codecs:

See section 5.1.3 for details on AAC and its variants.

AAC with ADTS framing and ID3 tags

ISO 13818-7

See section 5.1.1 for details on AAC and its variants

WebVTT

RTSP (RTP, SDP)

Profile name	Reference(s)	Required codec support
H264 AVC	RFC 6184	See section 5.1.8 for details on H264 AVC
MP4A-LATM	RFC 6416	See section 5.1.3 for details on AAC and its variants
H263-1998	RFC 3551 RFC 4629 RFC 2190	See section 5.1.8 for details on H263
H263-2000	RFC 4629	See section 5.1.8 for details on H263
AMR	RFC 4867	See section 5.1.3 for details on AMR-NB
AMR-WB	RFC 4867	See section 5.1.3 for details on AMR-WB
MP4V-ES	RFC 6416	See section 5.1.8 for details on MPEG-4 SP
mpeg4-generic	RFC 3640	See section 5.1.3 for details on AAC and its variants
MP2T	RFC 2250	See MPEG-2 Transport Stream underneath HTTP Live Streaming for details

5.8. Secure Media

If device implementations support secure video output and are capable of supporting secure surfaces, they:

[C-1-1] MUST declare support for Display.FLAG_SECURE.

If device implementations declare support for Display.FLAG_SECURE and support wireless display protocol, they:

[C-2-1] MUST secure the link with a cryptographically strong mechanism such as HDCP 2.x or higher for the displays connected through wireless protocols such as Miracast.

If device implementations declare support for Display.FLAG_SECURE and support wired external display, they:

[C-3-1] MUST support HDCP 1.2 or higher for all external displays connected via a user-accessible wired port.

5.9. Musical Instrument Digital Interface (MIDI)

If device implementations report support for feature android.software.midi via the android.content.pm.PackageManager class, they:

[C-1-1] MUST support MIDI over all MIDI-capable hardware transports for which they provide generic non-MIDI connectivity, where such transports are:
- USB host mode, section 7.7
- MIDI over Bluetooth LE acting in central role, section 7.4.3
[C-1-2] MUST support the inter-app MIDI software transport (virtual MIDI devices)
[C-1-3] MUST include libamidi.so (native MIDI support)
SHOULD support MIDI over USB peripheral mode, section 7.7

5.10. Professional Audio

If device implementations report support for feature android.hardware.audio.pro via the android.content.pm.PackageManager class, they:

[C-1-1] MUST report support for feature android.hardware.audio.low_latency.
[C-1-2] MUST meet the latency requirements for FEATURE_AUDIO_PRO as defined in section 5.6 Audio Latency .
[C-1-3] MUST include a USB port(s) supporting USB host mode and USB peripheral mode.
[C-1-4] MUST report support for feature android.software.midi.
[C-1-5] MUST meet USB audio latency requirements using the AAudio native audio API and AAUDIO_PERFORMANCE_MODE_LOW_LATENCY.
[C-1-6] MUST have Cold output latency of 200 milliseconds or less.
[C-1-7] MUST have Cold input latency of 200 milliseconds or less.

If device implementations include a 4 conductor 3.5mm audio jack, they:

[C-2-2] MUST comply with section Mobile device (jack) specifications of the Wired Audio Headset Specification (v1.1).

If device implementations omit a 4 conductor 3.5mm audio jack and include a USB port(s) supporting USB host mode, they:

[C-3-1] MUST implement the USB audio class.

5.11. Capture for Unprocessed

Android includes support for recording of unprocessed audio via the android.media.MediaRecorder.AudioSource.UNPROCESSED audio source. In OpenSL ES, it can be accessed with the record preset SL_ANDROID_RECORDING_PRESET_UNPROCESSED.

If device implementations intent to support unprocessed audio source and make it available to third-party apps, they:

[C-1-1] MUST report the support through the android.media.AudioManager property PROPERTY_SUPPORT_AUDIO_SOURCE_UNPROCESSED.
[C-1-2] MUST exhibit approximately flat amplitude-versus-frequency characteristics in the mid-frequency range: specifically ±10 dB from 100 Hz to 7000 Hz for each and every microphone used to record the unprocessed audio source.
[C-1-3] MUST exhibit amplitude levels in the low frequency range: specifically from ±20 dB from 5 z to 100 Hz compared to the mid-frequency range for each and every microphone used to record the unprocessed audio source.
[C-1-4] MUST exhibit amplitude levels in the high frequency range: specifically from ±30 dB from 7000 Hz to 22 KHz compared to the mid-frequency range for each and every microphone used to record the unprocessed audio source.
[C-1-5] MUST set audio input sensitivity such that a 1000 Hz sinusoidal tone source played at 94 dB Sound Pressure Level (SPL) yields a response with RMS of 520 for 16 bit-samples (or -36 dB Full Scale for floating point/double precision samples) for each and every microphone used to record the unprocessed audio source.
[C-1-6] MUST have a signal-to-noise ratio (SNR) at 60 dB or higher for each and every microphone used to record the unprocessed audio source. (whereas the SNR is measured as the difference between 94 dB SPL and equivalent SPL of self noise, A-weighted).
[C-1-7] MUST have a total harmonic distortion (THD) less than be less than 1% for 1 kHZ at 90 dB SPL input level at each and every microphone used to record the unprocessed audio source.
[C-1-8] MUST not have any other signal processing (e.g. Automatic Gain Control, High Pass Filter, or Echo cancellation) in the path other than a level multiplier to bring the level to desired range. In other words:
- [C-1-9] If any signal processing is present in the architecture for any reason, it MUST be disabled and effectively introduce zero delay or extra latency to the signal path.
- [C-1-10] The level multiplier, while allowed to be on the path, MUST NOT introduce delay or latency to the signal path.

All SPL measurements are made directly next to the microphone under test. For multiple microphone configurations, these requirements apply to each microphone.

If device implementations declare android.hardware.microphone but do not support unprocessed audio source, they:

[C-2-1] MUST return null for the AudioManager.getProperty(PROPERTY_SUPPORT_AUDIO_SOURCE_UNPROCESSED) API method, to properly indicate the lack of support.
[C-SR-1] are still STRONGLY RECOMMENDED to satisfy as many of the requirements for the signal path for the unprocessed recording source.

5.12. HDR Video

Android 13 supports the HDR technologies as described in an upcoming document.

Pixel Format

If a video decoder advertises support for COLOR_FormatYUVP010, then:

[C-1-1] MUST support the P010 format for CPU-read (ImageReader, MediaImage, ByteBuffer). In Android 13, P010 is relaxed to allow arbitrary stride for the Y and UV planes.
[C-1-2] The P010 output buffer MUST be able to be sampled by the GPU (when allocated with GPU_SAMPLING usage). This enables GPU composition and custom tone mapping by apps.

If a video decoder advertises support for COLOR_Format32bitABGR2101010, it:

[C-2-1] MUST support the RGBA_1010102 format for output surface and CPU-readable (ByteBuffer output).

If a video encoder advertises support for COLOR_FormatYUVP010, it:

[C-3-1] MUST support the P010 format for input surface and CPU-writeable (ImageWriter, MediaImage, ByteBuffer) input.

If a video encoder advertises support for COLOR_Format32bitABGR2101010, it:

[C-4-1] MUST support RGBA_1010102 format for input surface and CPU-writeable (ImageWriter, ByteBuffer) input. Note: Converting between various transfer curves is NOT required for encoders.

HDR Capture Requirements

For all video encoders that support HDR profiles, device implementations:

[C-5-1] MUST NOT assume that the HDR metadata is precise. For example, the encoded frame could have pixels beyond the peak luminance level, or the histogram might not be representative of the frame.
SHOULD aggregate HDR dynamic metadata to generate appropriate HDR static metadata for encoded streams, and they should output it at the end of each encoding session.

If device implementations support HDR capture using the CamcorderProfile APIs then they:

[C-6-1] MUST support HDR capture through the Camera2 APIs as well.
[C-6-2] MUST support at least one hardware-accelerated video encoder for each HDR technology supported.
[C-6-3] MUST support (at the minimum) HLG capture.
[C-6-4] MUST support writing the HDR metadata (if applicable to the HDR technology) into the captured video file. For AV1, HEVC, and DolbyVision this means including the metadata into the encoded bitstream.
[C-6-5] MUST support P010 and COLOR_FormatYUVP010.
[C-6-6] MUST support HDR to SDR tone mapping in the default hardware-accelerated decoder for the captured profile. In other words, if a device can capture HDR10+ HEVC, the default HEVC decoder MUST be able to decode the captured stream in SDR.

HDR Editing Requirements

If device implementations include video encoders that support HDR editing, then they:

SHOULD use minimal latency for generating the HDR metadata when not present, and SHOULD gracefully handle situations where the metadata is present for some frames and not for others. This metadata SHOULD be precise (for example, represent the actual peak luminance and histogram of the frame).

If device implementation includes codecs that support FEATURE_HdrEditing, then those codecs:

[C-7-1] MUST support at least one HDR profile.
[C-7-2] MUST support FEATURE_HdrEditing for all HDR profiles advertised by that codec. In other words, they MUST support generating HDR metadata when not present for all HDR profiles supported that use HDR metadata.
[C-7-3] MUST support the following video encoder input formats that fully preserve the HDR decoded signal:
- RGBA_1010102 (already in the target transfer curve) for both input surface and ByteBuffer and MUST advertise support for COLOR_Format32bitABGR2101010.

If device implementation includes codecs that support FEATURE_HdrEditing, then the device:

[C-7-4] MUST advertise support for EXT_YUV_target OpenGL extension.

HDR Display Requirements

If device implementations receive buffer content encoded with ADATASPACE_TRANSFER_HLG, and that content is sent to the display through SurfaceControl.Transaction#setBuffer, they:

[C-8-1] MUST follow the graphics white recommendation in BT. 2408-7, and only display that content to be at most greater than 4.926 times of SDR content.

6. Developer Tools and Options Compatibility

6.1. Developer Tools

Device implementations:

[C-0-1] MUST support the Android Developer Tools provided in the Android SDK.
Android Debug Bridge (adb)
[C-0-2] MUST support adb as documented in the Android SDK and the shell commands provided in the AOSP, which can be used by app developers, including dumpsys, cmd stats, and Simpleperf.
[C-0-11] MUST support the shell command cmd testharness. Upgrading device implementations from an earlier Android version without a persistent data block MAY be exempted from C-0-11.
[C-0-3] MUST NOT alter the format or the contents of device system events (batterystats, diskstats, fingerprint, graphicsstats, netstats, notification, procstats) logged via the dumpsys command.

[C-0-10] MUST record, without omission, and make the following events accessible and available to the cmd stats shell command and the StatsManager System API class.
- ActivityForegroundStateChanged
- AnomalyDetected
- AppBreadcrumbReported
- AppCrashOccurred
- AppStartOccurred
- BatteryLevelChanged
- BatterySaverModeStateChanged
- BleScanResultReceived
- BleScanStateChanged
- ChargingStateChanged
- DeviceIdleModeStateChanged
- ForegroundServiceStateChanged
- GpsScanStateChanged
- InputDeviceUsageReported
- JobStateChanged
- KeyboardConfigured
- KeyboardSystemsEventReported
- PluggedStateChanged
- PressureStallInformation
- ScheduledJobStateChanged
- ScreenStateChanged
- SyncStateChanged
- SystemElapsedRealtime
- TouchpadUsage
- UidProcessStateChanged
- WakelockStateChanged
- WakeupAlarmOccurred
- WifiLockStateChanged
- WifiMulticastLockStateChanged
- WifiScanStateChanged

[C-0-4] MUST have the device-side adb daemon be inactive by default and there MUST be a user-accessible mechanism to turn on the Android Debug Bridge.
[C-0-5] MUST support secure adb. Android includes support for secure adb. Secure adb enables adb on known authenticated hosts.
[C-0-6] MUST provide a mechanism allowing adb to be connected from a host machine. Specifically:

If device implementations without a USB port support peripheral mode, they:

[C-3-1] MUST implement adb via local-area network (such as Ethernet or Wi-Fi).
[C-3-2] MUST provide drivers for Windows 7, 8 and 10, allowing developers to connect to the device using the adb protocol.

If device implementations support adb connections to a host machine via Wi-Fi or Ethernet, they:

[C-4-1] MUST have the AdbManager#isAdbWifiSupported() method return true.

If device implementations support adb connections to a host machine via Wi-Fi or Ethernet, and includes at least one camera, they:

[C-5-1] MUST have the AdbManager#isAdbWifiQrSupported() method return true.
Dalvik Debug Monitor Service (ddms)
- [C-0-7] MUST support all ddms features as documented in the Android SDK. As ddms uses adb, support for ddms SHOULD be inactive by default, but MUST be supported whenever the user has activated the Android Debug Bridge, as above.
SysTrace
- [C-0-9] MUST support the systrace tool as documented in the Android SDK. Systrace must be inactive by default and there MUST be a user-accessible mechanism to turn on Systrace.
Perfetto
- [C-SR-1] Are STRONGLY RECOMMENDED to expose a /system/bin/perfetto binary to the shell user which cmdline complies with the perfetto documentation.
- [C-SR-2] The perfetto binary is STRONGLY RECOMMENDED to accept as input a protobuf config that complies with the schema defined in the perfetto documentation.
- [C-SR-3] The perfetto binary is STRONGLY RECOMMENDED to write as output a protobuf trace that complies with the schema defined in the perfetto documentation.
- [C-SR-4] Are STRONGLY RECOMMENDED to provide, through the perfetto binary, at least the data sources described in the perfetto documentation.
Low Memory Killer
- [C-0-12] MUST write a LMK_KILL_OCCURRED_FIELD_NUMBER Atom to the statsd log when an app is terminated by the Low Memory Killer.
Test Harness Mode If device implementations support the shell command cmd testharness and run cmd testharness enable, they:
- [C-2-1] MUST return true for ActivityManager.isRunningInUserTestHarness()
- [C-2-2] MUST implement Test Harness Mode as described in Test Harness Mode documentation.
GPU work information

Device implementations:
- [C-0-13] MUST implement the shell command dumpsys gpu --gpuwork to display the aggregated GPU work data returned by the power/gpu_work_period kernel tracepoint, or display no data if the tracepoint is not supported. The AOSP implementation is frameworks/native/services/gpuservice/gpuwork/.

If device implementations report the support of Vulkan 1.0 or higher via the android.hardware.vulkan.version feature flags, they:

[C-1-1] MUST provide an affordance for the app developer to enable/disable GPU debug layers.
[C-1-2] MUST, when the GPU debug layers are enabled, enumerate layers in libraries provided by external tools (i.e. not part of the platform or application package) found in debuggable applications' base directory to support vkEnumerateInstanceLayerProperties() and vkCreateInstance() API methods.

6.2. Developer Options

Android includes support for developers to configure application development-related settings.

Device implementations MUST provide a consistent experience for Developer Options, they:

[C-0-1] MUST honor the android.settings.APPLICATION_DEVELOPMENT_SETTINGS intent to show application development-related settings. The upstream Android implementation hides the Developer Options menu by default and enables users to launch Developer Options after pressing seven (7) times on the Settings > About Device > Build Number menu item.
[C-0-2] MUST hide Developer Options by default.
[C-0-3] MUST provide a clear mechanism that does not give preferential treatment to one third-party app as opposed to another to enable Developer Options. MUST provide a public visible document or website that describes how to enable Developer Options. This document or website MUST be linkable from the Android SDK documents.
SHOULD have an ongoing visual notification to the user when Developer Options is enabled and the safety of the user is of concern.
MAY temporarily limit access to the Developer Options menu, by visually hiding or disabling the menu, to prevent distraction for scenarios where the safety of the user is of concern.

7. Hardware Compatibility

If a device includes a particular hardware component that has a corresponding API for third-party developers:

[C-0-1] The device implementation MUST implement that API as described in the Android SDK documentation.

If an API in the SDK interacts with a hardware component that is stated to be optional and the device implementation does not possess that component:

[C-0-2] Complete class definitions (as documented by the SDK) for the component APIs MUST still be presented.
[C-0-3] The API's behaviors MUST be implemented as no-ops in some reasonable fashion.
[C-0-4] API methods MUST return null values where permitted by the SDK documentation.
[C-0-5] API methods MUST return no-op implementations of classes where null values are not permitted by the SDK documentation.
[C-0-6] API methods MUST NOT throw exceptions not documented by the SDK documentation.
[C-0-7] Device implementations MUST consistently report accurate hardware configuration information via the getSystemAvailableFeatures() and hasSystemFeature(String) methods on the android.content.pm.PackageManager class for the same build fingerprint.

A typical example of a scenario where these requirements apply is the telephony API: Even on non-phone devices, these APIs must be implemented as reasonable no-ops.

7.1. Display and Graphics

Android includes facilities that automatically adjust application assets and UI layouts appropriately for the device to ensure that third-party applications run well on a variety of hardware displays and configurations. An Android-compatible display is a display screen that implements all of the behaviors and APIs described in Android Developers - Screen compatibility overview, this section (7.1) and its subsections, as well as any additional device-type specific behaviors documented in section 2 of this CDD.

Device implementations:

[C-0-1] MUST, by default, render third party applications only onto Android-compatible displays.

The units referenced by the requirements in this section are defined as follows:

physical diagonal size. The distance in inches between two opposing corners of the illuminated portion of the display.
density. The number of pixels encompassed by a linear horizontal or vertical span of 1", expressed as pixels per inch (ppi or dpi). Where ppi and dpi values are listed, both horizontal and vertical dpi must fall within the listed range.
aspect ratio. The ratio of the pixels of the longer dimension to the shorter dimension of the screen. For example, a display of 480x854 pixels would be 854/480 = 1.779, or roughly "16:9".
density-independent pixel (dp). A virtual pixel unit normalized to a screen density of 160. For some density d, and a number of pixels p, the number of density-independent pixels dp, is calculated as: dp = (160 / d) * p.

7.1.1. Screen Configuration

7.1.1.1. Screen Size and Shape

The Android UI framework supports a variety of different logical screen layout sizes, and allows applications to query the current configuration's screen layout size via Configuration.screenLayout with the SCREENLAYOUT_SIZE_MASK and Configuration.smallestScreenWidthDp.

Device implementations:

[C-0-1] MUST report the correct layout size for the Configuration.screenLayout as defined in the Android SDK documentation. Specifically, device implementations MUST report the correct logical density-independent pixel (dp) screen dimensions as below:
- Devices with the Configuration.uiMode set as any value other than UI_MODE_TYPE_WATCH, and reporting a small size for the Configuration.screenLayout, MUST have at least 426 dp x 320 dp.
- Devices reporting a normal size for the Configuration.screenLayout, MUST have at least 480 dp x 320 dp.
- Devices reporting a large size for the Configuration.screenLayout, MUST have at least 640 dp x 480 dp.
- Devices reporting a xlarge size for the Configuration.screenLayout, MUST have at least 960 dp x 720 dp.
[C-0-2] MUST correctly honor applications' stated support for screen sizes through the <supports-screens> attribute in the AndroidManifest.xml, as described in the Android SDK documentation.
MAY have the Android-compatible display(s) with rounded corners.

If device implementations support screens capable of the UI_MODE_TYPE_NORMAL size configuration and use physical display(s) with rounded corners to render these screens, they:

[C-1-1] MUST ensure that at least one of the following requirements is met for each such display:
- The radius of the rounded corners is less than or equal to 38 dp.
- When an 18 dp by 18 dp box is anchored at each corner of the logical display, at least one pixel of each box is visible on the screen.
SHOULD include user affordance to switch to the display mode with the rectangular corners.

If device implementations are only capable of NO_KEYS keyboard configuration, and intend to report support for the UI_MODE_TYPE_NORMAL ui mode configuration, they:

[C-4-1] MUST have a layout size, excluding any display cutouts, of at least 596 dp x 384 dp or greater.

For details on correctly implementing the sidecar or extension APIs refer to the public documentation of Window Manager Jetpack.

7.1.1.2. Screen Aspect Ratio

This section was deleted in Android 14.

7.1.1.3. Screen Density

The Android UI framework defines a set of standard logical densities to help application developers target application resources.

Device Implementations:

[C-0-1] MUST report one of the Android framework densities that are listed on DisplayMetrics through the DENSITY_DEVICE_STABLE API and this value must be a static value for each physical display. However the device MAY report a different DisplayMetrics.density according to the display configuration changes made by the user (for example, display size) set after initial boot.
SHOULD define the standard Android framework density that is numerically closest to the physical density of the screen, or a value that would map to the same equivalent angular field-of-view measurements of a handheld device.

If device implementations provide an affordance to change the display size of the device, they:

[C-1-1] MUST NOT scale the display larger than 1.5 times DENSITY_DEVICE_STABLE or produce an effective minimum screen dimension smaller than 320dp (equivalent to resource qualifier sw320dp), whichever comes first.
[C-1-2] MUST NOT scale the display smaller than 0.85 times the DENSITY_DEVICE_STABLE.
To ensure good usability and consistent font sizes, it is RECOMMENDED that the following scaling of Native Display options be provided (while complying with the limits specified above)
- Small: 0.85x
- Default: 1x (Native display scale)
- Large: 1.15x
- Larger: 1.3x
- Largest 1.45x

7.1.2. Display Metrics

If device implementations include the Android-compatible display(s) or video output to the Android-compatible display screen(s), they:

[C-1-1] MUST report correct values for all Android-compatible display metrics defined in the android.util.DisplayMetrics API.

If device implementations does not include an embedded screen or video output, they:

[C-2-1] MUST report correct values of the Android-compatible display as defined in the android.util.DisplayMetrics API for the emulated default view.Display.

7.1.3. Screen Orientation

Device implementations:

[C-0-1] MUST report which screen orientations they support (android.hardware.screen.portrait and/or android.hardware.screen.landscape) and MUST report at least one supported orientation. For example, a device with a fixed orientation landscape screen, such as a television or laptop, SHOULD only report android.hardware.screen.landscape.
[C-0-2] MUST report the correct value for the device's current orientation, whenever queried via theß android.content.res.Configuration.orientation, android.view.Display.getOrientation(), or other APIs.

If device implementations support both screen orientations, they:

[C-1-1] MUST support dynamic orientation by applications to either portrait or landscape screen orientation. That is, the device must respect the application's request for a specific screen orientation.

[C-1-2] MUST NOT change the reported screen size or density when changing orientation.
MAY select either portrait or landscape orientation as the default.

7.1.4. 2D and 3D Graphics Acceleration

7.1.4.1. OpenGL ES

Device implementations:

[C-0-1] MUST correctly identify the supported OpenGL ES versions (1.1, 2.0, 3.0, 3.1, 3.2) through the managed APIs (such as via the GLES10.getString() method) and the native APIs.
[C-0-2] MUST include the support for all the corresponding managed APIs and native APIs for every OpenGL ES versions they identified to support.

If device implementations include a screen or video output, they:

[C-1-1] MUST support OpenGL ES 1.1, 2.0, 3.0, and 3.1, as embodied and detailed in the Android SDK documentation.
SHOULD support OpenGL ES 3.2.

The OpenGL ES dEQP tests are partitioned into a number of test lists, each with an associated date/version number. These are in the Android source tree at external/deqp/android/cts/main/glesXX-master-YYYY-MM-DD.txt. A device that supports OpenGL ES at a self-reported level indicates that it can pass the dEQP tests in all test lists from this level and earlier.

If device implementations support any of the OpenGL ES versions, they:

[C-2-1] MUST report via the OpenGL ES managed APIs and native APIs any other OpenGL ES extensions they have implemented, and conversely MUST NOT report extension strings that they do not support.
[C-2-2] MUST support the EGL_KHR_image, EGL_KHR_image_base, EGL_ANDROID_image_native_buffer, EGL_ANDROID_get_native_client_buffer, EGL_KHR_wait_sync, EGL_KHR_get_all_proc_addresses, EGL_ANDROID_presentation_time, EGL_KHR_swap_buffers_with_damage, EGL_ANDROID_recordable, and EGL_ANDROID_GLES_layers extensions.
[C-2-3] MUST report the maximum version of the OpenGL ES dEQP tests supported via the android.software.opengles.deqp.level feature flag.
[C-2-4] MUST at least support version 132383489 (from Mar 1st, 2020) as reported in the android.software.opengles.deqp.level feature flag.
[C-2-5] MUST pass all OpenGL ES dEQP Tests in the test lists between version 132383489 and the version specified in the android.software.opengles.deqp.level feature flag, for each supported OpenGL ES version.
[C-SR-2] Are STRONGLY RECOMMENDED to support the EGL_KHR_partial_update and OES_EGL_image_external extensions.
SHOULD accurately report via the getString() method, any texture compression format that they support, which is typically vendor-specific.
SHOULD support the EGL_IMG_context_priority and EGL_EXT_protected_content extensions.

If device implementations declare support for OpenGL ES 3.0, 3.1, or 3.2, they:

[C-3-1] MUST export the corresponding function symbols for these version in addition to the OpenGL ES 2.0 function symbols in the libGLESv2.so library.
[C-SR-3] Are STRONGLY RECOMMENDED to support the OES_EGL_image_external_essl3 extension.

If device implementations support OpenGL ES 3.2, they:

[C-4-1] MUST support the OpenGL ES Android Extension Pack in its entirety.

If device implementations support the OpenGL ES Android Extension Pack in its entirety, they:

[C-5-1] MUST identify the support through the android.hardware.opengles.aep feature flag.

If device implementations expose support for the EGL_KHR_mutable_render_buffer extension, they:

[C-6-1] MUST also support the EGL_ANDROID_front_buffer_auto_refresh extension.

7.1.4.2. Vulkan

Android includes support for Vulkan, a low-overhead, cross-platform API for high-performance 3D graphics.

If device implementations support OpenGL ES 3.1, they:

[C-SR-1] Are STRONGLY RECOMMENDED to include support for Vulkan 1.3.
[C-4-1] MUST NOT support a Vulkan variant version (i.e. the variant part of the Vulkan core version MUST be zero).

If device implementations include a screen or video output, they:

[C-SR-2] Are STRONGLY RECOMMENDED to include support for Vulkan 1.3.

The Vulkan dEQP tests are partitioned into a number of test lists, each with an associated date/version. These are in the Android source tree at external/deqp/android/cts/main/vk-master-YYYY-MM-DD.txt. A device that supports Vulkan at a self-reported level indicates that it can pass the dEQP tests in all test lists from this level and earlier.

If device implementations include support for Vulkan, they:

[C-1-1] MUST report the correct integer value with the android.hardware.vulkan.level and android.hardware.vulkan.version feature flags.
[C-1-2] MUST enumerate, at least one VkPhysicalDevice for the Vulkan native API vkEnumeratePhysicalDevices().
[C-1-3] MUST fully implement the Vulkan 1.1 APIs for each enumerated VkPhysicalDevice.
[C-1-4] MUST enumerate layers, contained in native libraries named as libVkLayer*.so in the application package's native library directory, through the Vulkan native APIs vkEnumerateInstanceLayerProperties() and vkEnumerateDeviceLayerProperties().
[C-1-5] MUST NOT enumerate layers provided by libraries outside of the application package, or provide other ways of tracing or intercepting the Vulkan API, unless the application has the android:debuggable attribute set as true or the metadata com.android.graphics.injectLayers.enable set to true.
[C-1-6] MUST report all extension strings that they do support via the Vulkan native APIs , and conversely MUST NOT report extension strings that they do not correctly support.
[C-1-7] MUST support the VK_KHR_surface, VK_KHR_android_surface, VK_KHR_swapchain, and VK_KHR_incremental_present extensions.
[C-1-8] MUST report the maximum version of the Vulkan dEQP Tests supported via the android.software.vulkan.deqp.level feature flag.
[C-1-9] MUST at least support version 132317953 (from Mar 1st, 2019) as reported in the android.software.vulkan.deqp.level feature flag.
[C-1-10] MUST pass all Vulkan dEQP Tests in the test lists between version 132317953 and the version specified in the android.software.vulkan.deqp.level feature flag.
[C-1-11] MUST NOT enumerate support for the VK_KHR_video_queue, VK_KHR_video_decode_queue, or VK_KHR_video_encode_queue extensions.
[C-SR-3] Are STRONGLY RECOMMENDED to support the VK_KHR_driver_properties and VK_GOOGLE_display_timing extensions.
[C-1-12] MUST NOT enumerate support for the VK_KHR_performance_query extension.
[C-SR-4] Are STRONGLY RECOMMENDED to satisfy the requirements specified by the Android Baseline 2022 profile.
[C-SR-5] Are STRONGLY RECOMMENDED to support VkPhysicalDeviceProtectedMemoryFeatures.protectedMemory and VK_EXT_global_priority.
[C-SR-6] Are STRONGLY RECOMMENDED to use SkiaVk with HWUI.

If device implementations include support for Vulkan, then they:

[C-SR-8] Are STRONGLY RECOMMENDED to not modify the Vulkan loader.
[C-1-14] MUST NOT enumerate Vulkan Device extensions of type "KHR", "GOOGLE", or "ANDROID" unless these extensions are included in the android.software.vulkan.deqp.level feature flag.

If device implementations do not include support for Vulkan 1.0, they:

[C-2-1] MUST NOT declare any of the Vulkan feature flags (e.g. android.hardware.vulkan.level, android.hardware.vulkan.version).
[C-2-2] MUST NOT enumerate any VkPhysicalDevice for the Vulkan native API vkEnumeratePhysicalDevices().

If device implementations include support for Vulkan 1.1 and declare any of the Vulkan feature flags described here, they:

[C-3-1] MUST expose support for the SYNC_FD external semaphore and handle types and the VK_ANDROID_external_memory_android_hardware_buffer extension.
[C-SR-7] Are STRONGLY RECOMMENDED to make the VK_KHR_external_fence_fd extension available to third-party applications and enable the application to export fence payload to and import fence payload from POSIX file descriptors as described here.

7.1.4.3. RenderScript

Device implementations:

[C-0-1] MUST support Android RenderScript, as detailed in the Android SDK documentation.

7.1.4.4. 2D Graphics Acceleration

Android includes a mechanism for applications to declare that they want to enable hardware acceleration for 2D graphics at the Application, Activity, Window, or View level through the use of a manifest tag android:hardwareAccelerated or direct API calls.

Device implementations:

[C-0-1] MUST enable hardware acceleration by default, and MUST disable hardware acceleration if the developer so requests by setting android:hardwareAccelerated="false" or disabling hardware acceleration directly through the Android View APIs.
[C-0-2] MUST exhibit behavior consistent with the Android SDK documentation on hardware acceleration.

Android includes a TextureView object that lets developers directly integrate hardware-accelerated OpenGL ES textures as rendering targets in a UI hierarchy.

Device implementations:

[C-0-3] MUST support the TextureView API, and MUST exhibit consistent behavior with the upstream Android implementation.

7.1.4.5. Wide-gamut Displays

If device implementations claim support for wide-gamut displays through Configuration.isScreenWideColorGamut(), they:

[C-1-1] MUST have a color-calibrated display.
[C-1-2] MUST have a display whose gamut covers the sRGB color gamut entirely in CIE 1931 xyY space.
[C-1-3] MUST have a display whose gamut has an area of at least 90% of DCI-P3 in CIE 1931 xyY space.
[C-1-4] MUST support OpenGL ES 3.1 or 3.2 and report it properly.
[C-1-5] MUST advertise support for the EGL_KHR_no_config_context, EGL_EXT_pixel_format_float, EGL_KHR_gl_colorspace, EGL_EXT_gl_colorspace_scrgb, EGL_EXT_gl_colorspace_scrgb_linear, EGL_EXT_gl_colorspace_display_p3, EGL_EXT_gl_colorspace_display_p3_linear, and EGL_EXT_gl_colorspace_display_p3_passthrough extensions.
[C-SR-1] Are STRONGLY RECOMMENDED to support GL_EXT_sRGB.

Conversely, if device implementations do not support wide-gamut displays, they:

[C-2-1] SHOULD cover 100% or more of sRGB in CIE 1931 xyY space, although the screen color gamut is undefined.

7.1.5. Legacy Application Compatibility Mode

Android specifies a "compatibility mode" in which the framework operates in a 'normal' screen size equivalent (320dp width) mode for the benefit of legacy applications not developed for old versions of Android that pre-date screen-size independence.

7.1.6. Screen Technology

The Android platform includes APIs that allow applications to render rich graphics to an Android-compatible display. Devices MUST support all of these APIs as defined by the Android SDK unless specifically allowed in this document.

All of a device implementation's Android-compatible displays:

[C-0-1] MUST be capable of rendering 16-bit color graphics.
SHOULD support displays capable of 24-bit color graphics.
[C-0-2] MUST be capable of rendering animations.
[C-0-3] MUST have a pixel aspect ratio (PAR) between 0.9 and 1.15. That is, the pixel aspect ratio MUST be near square (1.0) with a 10 ~ 15% tolerance.

7.1.7. Secondary Displays

Android includes support for secondary Android-compatible displays to enable media sharing capabilities and developer APIs for accessing external displays.

If device implementations support an external display either via a wired, wireless, or an embedded additional display connection, they:

[C-1-1] MUST implement the DisplayManager system service and API as described in the Android SDK documentation.

7.2. Input Devices

Device implementations:

[C-0-1] MUST include an input mechanism, such as a touchscreen or non-touch navigation, to navigate between the UI elements.

7.2.1. Keyboard

If device implementations include support for third-party Input Method Editor (IME) applications, they:

[C-1-1] MUST declare the android.software.input_methods feature flag.
[C-1-2] MUST implement fully Input Management Framework
[C-1-3] MUST have a preinstalled software keyboard.

Device implementations:

[C-0-1] MUST NOT include a hardware keyboard that does not match one of the formats specified in android.content.res.Configuration.keyboard (QWERTY or 12-key).
SHOULD include additional soft keyboard implementations.
MAY include a hardware keyboard.

7.2.2. Non-touch Navigation

Android includes support for d-pad, trackball, and wheel as mechanisms for non-touch navigation.

Device implementations:

[C-0-1] MUST report the correct value for android.content.res.Configuration.navigation.

If device implementations lack non-touch navigations, they:

[C-1-1] MUST provide a reasonable alternative user interface mechanism for the selection and editing of text, compatible with Input Management Engines. The upstream Android open source implementation includes a selection mechanism suitable for use with devices that lack non-touch navigation inputs.

7.2.3. Navigation Keys

The Home, Recents, and Back functions typically provided via an interaction with a dedicated physical button or a distinct portion of the touch screen, are essential to the Android navigation paradigm and therefore, device implementations:

[C-0-1] MUST provide a user affordance to launch installed applications that have an activity with the <intent-filter> set with ACTION=MAIN and CATEGORY=LAUNCHER or CATEGORY=LEANBACK_LAUNCHER for Television device implementations. The Home function SHOULD be the mechanism for this user affordance.
SHOULD provide buttons for the Recents and Back function.

If the Home, Recents, or Back functions are provided, they:

[C-1-1] MUST be accessible with a single action (e.g. tap, double-click or gesture) when any of them are accessible.
[C-1-2] MUST provide a clear indication of which single action would trigger each function. Having a visible icon imprinted on the button, showing a software icon on the navigation bar portion of the screen, or walking the user through a guided step-by-step demo flow during the out-of-box setup experience are examples of such an indication.

Device implementations:

[C-SR-1] are STRONGLY RECOMMENDED to not provide the input mechanism for the Menu function as it is deprecated in favor of action bar since Android 4.0.
[C-SR-2] Are STRONGLY RECOMMENDED to provide all navigation functions as cancellable. 'Cancellable' is defined as the user's ability to prevent the navigation function from executing (e.g. going home, going back, etc.) if the swipe is not released past a certain threshold.

If device implementations provide the Menu function, they:

[C-2-1] MUST display the action overflow button whenever the action overflow menu popup is not empty and the action bar is visible.
[C-2-2] MUST NOT modify the position of the action overflow popup displayed by selecting the overflow button in the action bar, but MAY render the action overflow popup at a modified position on the screen when it is displayed by selecting the Menu function.

If device implementations do not provide the Menu function, for backwards compatibility, they:

[C-3-1] MUST make the Menu function available to applications when targetSdkVersion is less than 10, either by a physical button, a software key, or gestures. This Menu function should be accessible unless hidden together with other navigation functions.

If device implementations provide the Assist function, they:

[C-4-1] MUST make the Assist function accessible with a single action (e.g. tap, double-click or gesture) when other navigation keys are accessible.
[C-SR-3] STRONGLY RECOMMENDED to use long press on HOME function as this designated interaction.

If device implementations use a distinct portion of the screen to display the navigation keys, they:

[C-5-1] Navigation keys MUST use a distinct portion of the screen, not available to applications, and MUST NOT obscure or otherwise interfere with the portion of the screen available to applications.
[C-5-2] MUST make available a portion of the display to applications that meets the requirements defined in section 7.1.1.
[C-5-3] MUST honor the flags set by the app through the View.setSystemUiVisibility() API method, so that this distinct portion of the screen (a.k.a. the navigation bar) is properly hidden away as documented in the SDK.

If the navigation function is provided as an on-screen, gesture-based action:

[C-6-1] WindowInsets#getMandatorySystemGestureInsets() MUST only be used to report the Home gesture recognition area.
[C-6-2] Gestures that start within an exclusion rect as provided by the foreground application via View#setSystemGestureExclusionRects(), but outside of WindowInsets#getMandatorySystemGestureInsets(), MUST NOT be intercepted for the navigation function as long as the exclusion rect is allowed within the max exclusion limit as specified in the documentation for View#setSystemGestureExclusionRects().
[C-6-3] MUST send the foreground app a MotionEvent.ACTION_CANCEL event once touches start being intercepted for a system gesture, if the foreground app was previously sent an MotionEvent.ACTION_DOWN event.
[C-6-4] MUST provide a user affordance to switch to an on-screen, button-based navigation (for example, in Settings).
SHOULD provide Home function as a swipe up from the bottom edge of the current orientation of the screen.
SHOULD provide Recents function as a swipe up and hold before release, from the same area as the Home gesture.
Gestures that start within WindowInsets#getMandatorySystemGestureInsets() SHOULD NOT be affected by exclusion rects provided by the foreground application via View#setSystemGestureExclusionRects().

If a navigation function is provided from anywhere on the left and right edges of the current orientation of the screen:

[C-7-1] The navigation function MUST be Back and provided as a swipe from both left and right edges of the current orientation of the screen.
[C-7-2] If custom swipeable system panels are provided on the left or right edges, they MUST be placed within the top 1/3rd of the screen with a clear, persistent visual indication that dragging in would invoke the aforementioned panels, and hence not Back. A system panel MAY be configured by a user such that it lands below the top 1/3rd of the screen edge(s) but the system panel MUST NOT use longer than 1/3rd of the edge(s).
[C-7-3] When the foreground app has either the View.SYSTEM_UI_FLAG_IMMERSIVE, View.SYSTEM_UI_FLAG_IMMERSIVE_STICKY, WindowInsetsController.BEHAVIOR_DEFAULT, or WindowInsetsController.BEHAVIOR_SHOW_TRANSIENT_BARS_BY_SWIPE flags set, swiping from the edges MUST behave as implemented in AOSP, which is documented in the SDK.
[C-7-4] When the foreground app has either the View.SYSTEM_UI_FLAG_IMMERSIVE, View.SYSTEM_UI_FLAG_IMMERSIVE_STICKY, WindowInsetsController.BEHAVIOR_DEFAULT, or WindowInsetsController.BEHAVIOR_SHOW_TRANSIENT_BARS_BY_SWIPE flags set, custom swipeable system panels MUST be hidden until the user brings in or un-dims the system bars (a.k.a. navigation and status bar) as implemented in AOSP.

If the back navigation function is provided and the user cancels the Back gesture, then:

[C-8-1] OnBackInvokedCallback.onBackCancelled() MUST be called.
[C-8-2] OnBackInvokedCallback.onBackInvoked() MUST NOT be called.
[C-8-3] KEYCODE_BACK event MUST NOT be dispatched.

If the back navigation function is provided but the foreground application does NOT have an OnBackInvokedCallback registered, then:

The system SHOULD provide an animation for the foreground application that suggests that the user is going back, as provided in AOSP.

If device implementations provide support for the system API setNavBarMode to allow any system app with android.permission.STATUS_BAR permission to set the navigation bar mode, then they:

[C-9-1] MUST provide support for kid-friendly icons or button-based navigation as provided in the AOSP code.

7.2.4. Touchscreen Input

Android includes support for a variety of pointer input systems, such as touchscreens, touch pads, and fake touch input devices. Touchscreen-based device implementations are associated with a display such that the user has the impression of directly manipulating items on screen. Since the user is directly touching the screen, the system does not require any additional affordances to indicate the objects being manipulated.

Device implementations:

SHOULD have a pointer input system of some kind (either mouse-like or touch).
SHOULD support fully independently tracked pointers.

If device implementations include a touchscreen (single-touch or better) on a primary Android-compatible display, they:

[C-1-1] MUST report TOUCHSCREEN_FINGER for the Configuration.touchscreen API field.
[C-1-2] MUST report the android.hardware.touchscreen and android.hardware.faketouch feature flags.

If device implementations include a touchscreen that can track more than a single touch on a primary Android-compatible display, they:

[C-2-1] MUST report the appropriate feature flags android.hardware.touchscreen.multitouch, android.hardware.touchscreen.multitouch.distinct, android.hardware.touchscreen.multitouch.jazzhand corresponding to the type of the specific touchscreen on the device.

If device implementations rely on an external input device such as mouse or trackball (i.e. not directly touching the screen) for input on a primary Android-compatible display and meet the fake touch requirements in section 7.2.5, they:

[C-3-1] MUST NOT report any feature flag starting with android.hardware.touchscreen.
[C-3-2] MUST report only android.hardware.faketouch.
[C-3-3] MUST report TOUCHSCREEN_NOTOUCH for the Configuration.touchscreen API field.

7.2.5. Fake Touch Input

Fake touch interface provides a user input system that approximates a subset of touchscreen capabilities. For example, a mouse or remote control that drives an on-screen cursor approximates touch, but requires the user to first point or focus then click. Numerous input devices like the mouse, trackpad, gyro-based air mouse, gyro-pointer, joystick, and multi-touch trackpad can support fake touch interactions. Android includes the feature constant android.hardware.faketouch, which corresponds to a high-fidelity non-touch (pointer-based) input device such as a mouse or trackpad that can adequately emulate touch-based input (including basic gesture support), and indicates that the device supports an emulated subset of touchscreen functionality.

If device implementations do not include a touchscreen but include another pointer input system which they want to make available, they:

SHOULD declare support for the android.hardware.faketouch feature flag.

If device implementations declare support for android.hardware.faketouch, they:

[C-1-1] MUST report the absolute X and Y screen positions of the pointer location and display a visual pointer on the screen.
[C-1-2] MUST report touch event with the action code that specifies the state change that occurs on the pointer going down or up on the screen.
[C-1-3] MUST support pointer down and up on an object on the screen, which allows users to emulate tap on an object on the screen.
[C-1-4] MUST support pointer down, pointer up, pointer down then pointer up in the same place on an object on the screen within a time threshold, which allows users to emulate double tap on an object on the screen.
[C-1-5] MUST support pointer down on an arbitrary point on the screen, pointer move to any other arbitrary point on the screen, followed by a pointer up, which allows users to emulate a touch drag.
[C-1-6] MUST support pointer down then allow users to quickly move the object to a different position on the screen and then pointer up on the screen, which allows users to fling an object on the screen.

If device implementations declare support for android.hardware.faketouch.multitouch.distinct, they:

[C-2-1] MUST declare support for android.hardware.faketouch.
[C-2-2] MUST support distinct tracking of two or more independent pointer inputs.

If device implementations declare support for android.hardware.faketouch.multitouch.jazzhand, they:

[C-3-1] MUST declare support for android.hardware.faketouch.
[C-3-2] MUST support distinct tracking of 5 (tracking a hand of fingers) or more pointer inputs fully independently.

7.2.6. Game Controller Support

7.2.6.1. Button Mappings

Device implementations:

[C-1-1] MUST be capable to map HID events to the corresponding InputEvent constants as listed in the below tables. The upstream Android implementation satisfies this requirement.

If device implementations embed a controller or ship with a separate controller in the box that would provide means to input all the events listed in the below tables, they:

[C-2-1] MUST declare the feature flag android.hardware.gamepad

Button	HID Usage²	Android Button
A¹	0x09 0x0001	KEYCODE_BUTTON_A (96)
B¹	0x09 0x0002	KEYCODE_BUTTON_B (97)
X¹	0x09 0x0004	KEYCODE_BUTTON_X (99)
Y¹	0x09 0x0005	KEYCODE_BUTTON_Y (100)
D-pad up¹ D-pad down¹	0x01 0x0039³	AXIS_HAT_Y⁴

Android 16 Compatibility Definition Stay organized with collections Save and categorize content based on your preferences.

1. Introduction

1.1 Document Structure

1.1.1. Requirements by Device Type

1.1.2. Requirement ID

1.1.3. Requirement ID in Section 2

2. Device Types

2.1 Device Configurations

2.2. Handheld Requirements

2.2.1. Hardware

2.2.2. Multimedia

2.2.3. Software

2.2.4. Performance and Power

2.2.5. Security Model

Restricted settings

2.2.6. Developer Tools and Options Compatibility

2.2.7. Handheld Media Performance Class

2.2.7.1. Media

2.2.7.2. Camera

2.2.7.3. Hardware

2.2.7.4. Performance

2.2.7.5. Graphics

2.3. Television Requirements

2.3.1. Hardware

2.3.2. Multimedia

2.3.3. Software

2.3.4. Performance and Power

2.3.5. Security Model

2.3.6. Developer Tools and Options Compatibility

2.4. Watch Requirements

2.4.1. Hardware

2.4.2. Multimedia

2.4.3. Software

2.4.4. Performance and Power

2.4.5. Security Model

2.5. Automotive Requirements

2.5.1. Hardware

2.5.2. Multimedia

2.5.3. Software

2.5.4. Performance and Power

2.5.5. Security Model

2.5.6. Developer Tools and Options Compatibility

2.6. Tablet Requirements

2.6.1. Hardware

2.6.2. Security Model

2.6.2. Software

3. Software

3.1. Managed API Compatibility

3.1.1. Android Extensions

3.1.2. Android Library

3.2. Soft API Compatibility

3.2.1. Permissions

3.2.2. Build Parameters

3.2.3. Intent Compatibility

3.2.3.1. Common Application Intents

3.2.3.2. Intent Resolution

3.2.3.3. Intent Namespaces

3.2.3.4. Broadcast Intents

3.2.3.5. Conditional Application Intents

3.2.4. Activities on secondary/multiple displays

3.3. Native API Compatibility

3.3.1. Application Binary Interfaces

3.3.2. 32-bit ARM Native Code Compatibility

3.4. Web Compatibility

3.4.1. WebView Compatibility

3.4.2. Browser Compatibility

3.5. API Behavioral Compatibility

3.5.1. Application Restriction

3.5.2. Application Hibernation

3.6. API Namespaces

3.7. Runtime Compatibility

3.8. User Interface Compatibility

3.8.1. Launcher (Home Screen)

3.8.2. Widgets

3.8.3. Notifications

3.8.3.1. Presentation of Notifications

3.8.3.2. Notification Listener Service

3.8.3.3. DND (Do not Disturb) / Priority Mode

3.8.3.4. Sensitive Notification Protection

3.8.4. Assist APIs

Android 16 Compatibility Definition