Android 14 Compatibility Definition

1. Introduction

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

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 14. A "device implementation" or "implementation" is the hardware/software solution so developed.

To be considered compatible with Android 14, 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 3.3 inches (or 2.5 inches for device implementations which shipped on API level 29 or earlier) 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 meets all requirements described on this document. 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.

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.
• [7.4.3/H] SHOULD include support for Bluetooth and Bluetooth LE.

If devices support WiFi 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 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 supporting 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
			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
			Input: Long press Output: Reject call
		Ongoing call	Input: Short press Output: End 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.

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

• [5.6/H-1-1] MUST have a Mean Continuous Round-Trip latency of 300 milliseconds or less over 5 measurements, with a Mean Absolute Deviation less than 30ms, over the following data paths: "speaker to microphone", 3.5 mm loopback adapter (if supported), USB loopback (if supported).

• [5.6/H-1-2] MUST have an average Tap-to-tone latency of 300 milliseconds or less over at least 5 measurements over the speaker to microphone data path.

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 move the haptic actuator in the X-axis (left-right) of the device’s natural portrait 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() API's.

• [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

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

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 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.

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.

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 in the Settings menu 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. and the ability to stop an app that is running a foreground service or a user-initiated job.with the ability to stop an app that is running a foreground service and display all apps that have active foreground services and the duration of each of these services since it started as described in the SDK document.
  • Some apps MAY be exempted from being stopped or being listed in such a user affordance as described in the SDK document.

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.

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, SHA1, 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 shared across large enough number of devices to prevent the keys from being used as device identifiers. One way of meeting this requirement is to share the same attestation key unless at least 100,000 units of a given SKU are produced. If more than 100,000 units of an SKU are produced, a different key MAY be used for each 100,000 units.

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 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.

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 to be transmitted out of the hotword detection service on each successful hotword result except for audio data passed through HotwordAudioStream.
• [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-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 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.

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.

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 (* Not applicable for Tablet):

• 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.T for android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS, then they:

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

2.2.7.2. Camera

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

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

2.2.7.3. Hardware

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

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

2.2.7.4. Performance

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

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

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

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.

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

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

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. MUST set the HDMI output mode to select the maximum resolution that can be supported with either a 50Hz or 60Hz refresh rate.
• [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.

Television device implementations:

• [3.12/T-0-1] MUST support TV Input Framework.

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, SHA1, 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 shared across large enough number of devices to prevent the keys from being used as device identifiers. One way of meeting this requirement is to share the same attestation key unless at least 100,000 units of a given SKU are produced. If more than 100,000 units of an SKU are produced, a different key MAY be used for each 100,000 units.

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.

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.

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.

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.
• [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.

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 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).

• [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.

Automotive device implementations:

• [7.6.1/A-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/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.

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 816MB if any of the following densities are used:

  • 280dpi 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 944MB 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 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

• [7.6.1/A-2-4] The memory available to the kernel and userspace MUST be at least 1824MB if any of the following densities are used:

  • 560dpi or higher on small/normal screens
  • 400dpi or higher on large screens
  • xhdpi or higher on extra large screens

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.

Automotive device implementations:

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

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.

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

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.

• [