4 Link Calculator 1.1 serial key or number

Type	Digital audio/video connector
Production history
Designer	VESA
Designed	May
Manufacturer	Various
Produced	–present
Superseded	DVI, VGA, SCART, RGB Component
Superseded by	None
General specifications
Length	Various
Hot pluggable	Yes
External	Yes
Audio signal	Optional; 1–8 channels, 16 or bit linear PCM; 32–&#;kHz sampling rate; maximum bitrate 36,&#;kbit/s (4,&#;kB/s)
Video signal	Optional, maximum resolution limited by available bandwidth
Pins	20 pins for external connectors on desktops, notebooks, graphics cards, monitors, etc. and 30/20 pins for internal connections between graphics engines and built-in flat panels.
Electrical
Signal	+&#;V
Max. voltage	&#;V
Max. current	&#;A
Data
Data signal	Yes
Bitrate	, , , , or 20&#;Gbit/s data rate per lane; 1, 2, or 4 lanes; (effective total , , , , or &#;Gbit/s for 4-lane link); 2 or &#;Mbit/s (effectively 1 or &#;Mbit/s) for the auxiliary channel.
Protocol	Micro-packet
Pin out
External connector (source-side) on PCB
Pin 1	ML_Lane&#;0&#;(p)[a]	Lane 0 (positive)
Pin 2	GND	Ground
Pin 3	ML_Lane&#;0&#;(n)[a]	Lane 0 (negative)
Pin 4	ML_Lane&#;1&#;(p)[a]	Lane 1 (positive)
Pin 5	GND	Ground
Pin 6	ML_Lane&#;1&#;(n)[a]	Lane 1 (negative)
Pin 7	ML_Lane&#;2&#;(p)[a]	Lane 2 (positive)
Pin 8	GND	Ground
Pin 9	ML_Lane&#;2&#;(n)[a]	Lane 2 (negative)
Pin 10	ML_Lane&#;3&#;(p)[a]	Lane 3 (positive)
Pin 11	GND	Ground
Pin 12	ML_Lane&#;3&#;(n)[a]	Lane 3 (negative)
Pin 13	CONFIG1	Connected to ground[b]
Pin 14	CONFIG2	Connected to ground[b]
Pin 15	AUX&#;CH&#;(p)	Auxiliary channel (positive)
Pin 16	GND	Ground
Pin 17	AUX&#;CH&#;(n)	Auxiliary channel (negative)
Pin 18	Hot&#;plug	Hot plug detect
Pin 19	Return	Return for power
Pin 20	DP_PWR	Power for connector (&#;V &#;mA)
^ abcdefghThis is the pinout for source-side connector, the sink-side connector pinout will have lanes 0–3 reversed in order; i.e., lane 3 will be on pin 1(n) and 3(p) while lane 0 will be on pin 10(n) and 12(p). ^ abPins 13 and 14 may either be directly connected to ground or connected to ground through a pulldown device.

A Mini DisplayPort receptacle (center), with a Thunderbolt 3 port (left) and power input (right)

DisplayPort (DP) is a digital display interface developed by a consortium of PC and chip manufacturers and standardized by the Video Electronics Standards Association (VESA). The interface is primarily used to connect a video source to a display device such as a computer monitor, and it can also carry audio, USB, and other forms of data.^[1]

DisplayPort was designed to replace VGA, FPD-Link, and Digital Visual Interface (DVI). The interface is backward compatible with other interfaces, such as HDMI and DVI, through the use of either active or passive adapters.

Overview[edit]

DisplayPort is the first display interface to rely on packetized data transmission, a form of digital communication found in technologies such as Ethernet, USB, and PCI Express. It permits the use of internal and external display connections, and unlike legacy standards that transmit a clock signal with each output, the DisplayPort protocol is based on small data packets known as micro packets, which can embed the clock signal within the data stream. This allows for higher resolution using fewer pins.^[2] The use of data packets also makes DisplayPort extensible, meaning additional features can be added over time without significant changes to the physical interface.^[3]

DisplayPort can be used to transmit audio and video simultaneously, although each is optional and can be transmitted without the other. The video signal path can range from six to sixteen bits per color channel, and the audio path can have up to eight channels of bit, &#;kHz PCM audio that is uncompressed.^[1] A bi-directional, half-duplex auxiliary channel carries device management and device control data for the Main Link, such as VESA EDID, MCCS, and DPMS standards. In addition, the interface is capable of carrying bi-directional USB signals.^[4]

The DisplayPort interface uses an LVDS signal protocol that is not compatible with DVI or HDMI. However, dual-mode DisplayPort ports are designed to transmit a single-link DVI or HDMI protocol (TMDS) across the interface through the use of an external passive adapter. This adapter enables compatibility mode and converts the signal from volts to 5 volts. For analog VGA/YPbPr and dual-link DVI, a powered active adapter is required for compatibility and does not rely on dual mode. Active VGA adapters are powered by the DisplayPort connector directly, while active dual-link DVI adapters typically rely on an external power source such as USB.^[5]

Versions[edit]

to [edit]

The first version, , was approved by VESA on 3 May ^[6] Version was ratified on 2 April ,^[7] and version a was ratified on 11 January ^[8]

DisplayPort –a allow a maximum bandwidth of &#;Gbit/s (&#;Gbit/s data rate) over a standard 4-lane main link. DisplayPort cables up to 2 meters in length are required to support the full &#;Gbit/s bandwidth.^[8] DisplayPort allows devices to implement alternative link layers such as fiber optic, allowing a much longer reach between source and display without signal degradation,^[9] although alternative implementations are not standardized. It also includes HDCP in addition to DisplayPort Content Protection (DPCP). The DisplayPort&#;a standard can be downloaded for free from the VESA website.^[10]

[edit]

DisplayPort version was introduced on 7 January ^[11] The most significant improvement of the new version is the doubling of the effective bandwidth to &#;Gbit/s in High Bit Rate 2 (HBR2) mode, which allows increased resolutions, higher refresh rates, and greater color depth. Other improvements include multiple independent video streams (daisy-chain connection with multiple monitors) called Multi-Stream Transport, facilities for stereoscopic 3D, increased AUX channel bandwidth (from 1&#;Mbit/s to &#;Mbit/s), more color spaces including xvYCC, scRGB and Adobe RGB , and Global Time Code (GTC) for sub 1&#;μs audio/video synchronisation. Also Apple Inc.'s Mini DisplayPort connector, which is much smaller and designed for laptop computers and other small devices, is compatible with the new standard.^{[1][12][13][14]}

a[edit]

DisplayPort version a was released in January ^[15] and may optionally include VESA's Adaptive Sync.^[16]AMD'sFreeSync uses the DisplayPort Adaptive-Sync feature for operation. FreeSync was first demonstrated at CES on a Toshiba Satellite laptop by making use of the Panel-Self-Refresh (PSR) feature from the Embedded DisplayPort standard,^[17] and after a proposal from AMD, VESA later adapted the Panel-Self-Refresh feature for use in standalone displays and added it as an optional feature of the main DisplayPort standard under the name "Adaptive-Sync" in version a.^[18] As it is an optional feature, support for Adaptive-Sync is not required for a display to be DisplayPort a-compliant.

[edit]

DisplayPort version was approved on 15 September ^[19] This standard increases overall transmission bandwidth to &#;Gbit/s with the new HBR3 mode featuring &#;Gbit/s per lane (up from &#;Gbit/s with HBR2 in version ), for a total data throughput of &#;Gbit/s after factoring in 8b/10b encoding overhead. This bandwidth is enough for a 4K UHD display ( × ) at &#;Hz with 24&#;bit/px RGB color, a 5K display ( × ) at 60&#;Hz with 30&#;bit/px RGB color, or an 8K UHD display ( × ) at 30&#;Hz with 24&#;bit/px RGB color. Using Multi-Stream Transport (MST), a DisplayPort port can drive two 4K UHD ( × ) displays at 60&#;Hz, or up to four WQXGA ( × ) displays at 60&#;Hz with 24&#;bit/px RGB color. The new standard includes mandatory Dual-mode for DVI and HDMI adapters, implementing the HDMI&#; standard and HDCP&#; content protection.^[20] The Thunderbolt 3 connection standard was originally to include DisplayPort&#; capability, but the final release ended up with only version The VESA's Adaptive Sync feature in DisplayPort version remains an optional part of the specification.^[21]

[edit]

DisplayPort version was published 1 March ^[22] No new transmission modes are defined, so HBR3 (&#;Gbit/s) as introduced in version still remains as the highest available mode. DisplayPort&#; adds support for Display Stream Compression (DSC), Forward Error Correction, HDR10 metadata defined in CTA, including static and dynamic metadata and the Rec. color space, for HDMI interoperability,^[23] and extends the maximum number of inline audio channels to ^[24]

DSC is a "visually lossless" encoding technique with up to a compression ratio.^[22] Using DSC with HBR3 transmission rates, DisplayPort&#; can support 8K UHD ( × ) at 60&#;Hz or 4K UHD ( × ) at &#;Hz with 30&#;bit/px RGB color and HDR. 4K at 60&#;Hz 30&#;bit/px RGB/HDR can be achieved without the need for DSC. On displays which do not support DSC, the maximum limits are unchanged from DisplayPort&#; (4K &#;Hz, 5K 60&#;Hz, 8K 30&#;Hz).^[25]

a[edit]

DisplayPort version a was published in April ^[26] VESA made no official press release for this version. It updated DisplayPort's DSC implementation from DSC to a.^[27]

[edit]

According to a roadmap published by VESA in September , a new version of DisplayPort was intended to be launched in "early ". It would have improved the link rate from to &#;Gbit/s, a 24% increase.^[28][29] This would have increased the total bandwidth from &#;Gbit/s to &#;Gbit/s.

However, no new version was released in , likely delayed to make further improvements after the HDMI Forum announced in January that their next standard (HDMI&#;) would offer up to 48&#;Gbit/s of bandwidth. According to a press release on 3 January , "VESA is also currently engaged with its members in the development of the next DisplayPort standard generation, with plans to increase the data rate enabled by DisplayPort by two-fold and beyond. VESA plans to publish this update within the next 18 months."^[30]

At CES , VESA announced that the new version would support 8K @ 60&#;Hz without compression and was expected to be released in the first half of ^[31]

On June 26, , VESA formally released the DisplayPort standard. VESA stated that DP is the first major update to the DisplayPort standard since March , and provides up to a ≈3× improvement in data rate (from to &#;Gbit/s) compared to the previous version of DisplayPort (a), as well as new capabilities to address the future performance requirements of traditional displays. These include beyond 8K resolutions, higher refresh rates and high dynamic range (HDR) support at higher resolutions, improved support for multiple display configurations, as well as improved user experience with augmented/virtual reality (AR/VR) displays, including support for 4K-and-beyond VR resolutions.

Products incorporating DP are not projected by VESA to appear on the market until late ^[32]

DP configuration examples[edit]

With the increased bandwidth enabled by DP , VESA offers a high degree of versatility and configurations for higher display resolutions and refresh rates. In addition to the above-mentioned 8K resolution at 60&#;Hz with HDR support, DP across the native DP connector or through USB-C as DisplayPort Alt Mode enables a variety of high-performance configurations:

• Single display resolutions
  • One 16K ( × ) display @ 60&#;Hz with 10&#;bpc (30&#;bit/px, HDR) RGB/Y′C_BC_R color (with DSC)
  • One 10K ( × ) display @ 60&#;Hz and 8&#;bpc (24&#;bit/px, SDR) RGB/Y′C_BC_R color (uncompressed)
• Dual display resolutions
  • Two 8K ( × ) displays @ &#;Hz and 10&#;bpc (30&#;bit/px, HDR) RGB/Y′C_BC_R color (with DSC)
  • Two 4K ( × ) displays @ &#;Hz and 8&#;bpc (24&#;bit/px, SDR) RGB/Y′C_BC_R color (uncompressed)
• Triple display resolutions
  • Three 10K ( × ) displays @ 60&#;Hz and 10&#;bpc (30&#;bit/px, HDR) RGB/Y′C_BC_R color (with DSC)
  • Three 4K ( × ) displays @ 90&#;Hz and 10&#;bpc (30&#;bit/px, HDR) RGB/Y′C_BC_R color (uncompressed)

When using only two lanes on the USB-C connector via DP Alt Mode to allow for simultaneous SuperSpeed USB data and video, DP can enable such configurations as:^[32]

• Three 4K ( × ) displays @ &#;Hz and 10&#;bpc (30&#;bit/px, HDR) RGB/Y′C_BC_R color (with DSC)
• Two 4K &#; 4K ( × ) displays (for AR/VR headsets) @ &#;Hz and 10&#;bpc (30&#;bit/px, HDR) RGB/Y′C_BC_R color (with DSC)
• Three QHD ( × ) @ &#;Hz and 8&#;bpc (24&#;bit/px, SDR) RGB/Y′C_BC_R color (uncompressed)
• One 8K ( × ) display @ 30&#;Hz and 10&#;bpc (30&#;bit/px, HDR) RGB/Y′C_BC_R color (uncompressed)

Specifications[edit]

Main specifications[edit]

Main link[edit]

The DisplayPort main link is used for transmission of video and audio. The main link consists of a number of unidirectional serial data channels which operate concurrently, called lanes. A standard DisplayPort connection has 4 lanes, though some applications of DisplayPort implement more, such as the Thunderbolt 3 interface which implements up to 8 lanes of DisplayPort.^[38](p4)

In a standard DisplayPort connection, each lane has a dedicated set of twisted-pair wires, and transmits data across it using differential signaling. This is a self-clocking system, so no dedicated clock signal channel is necessary.^[8](§) Unlike DVI and HDMI, which vary their transmission speed to the exact rate required for the specific video format, DisplayPort only operates at a few specific speeds; any excess bits in the transmission are filled with "stuffing symbols".^[8](§)

In DisplayPort versions –a, the data is encoded using ANSI 8b/10b encoding prior to transmission. With this scheme, only 8 out of every 10 transmitted bits represent data; the extra bits are used for DC balancing (ensuring a roughly equal number of 1s and 0s). As a result, the rate at which data can be transmitted is only 80% of the physical bitrate. The transmission speeds are also sometimes expressed in terms of the "Link Symbol Rate", which is the rate at which these 8b/10b-encoded symbols are transmitted (i.e. the rate at which groups of 10 bits are transmitted, 8 of which represent data). The following transmission modes are defined in version –a:

• RBR (Reduced Bit Rate): &#;Gbit/s bandwidth per lane (&#;MHz link symbol rate)
• HBR (High Bit Rate): &#;Gbit/s bandwidth per lane (&#;MHz link symbol rate)
• HBR2 (High Bit Rate 2): &#;Gbit/s bandwidth per lane (&#;MHz link symbol rate), introduced in DP&#;
• HBR3 (High Bit Rate 3): &#;Gbit/s bandwidth per lane (&#;MHz link symbol rate), introduced in DP&#;

DisplayPort uses b/b encoding; each group of transmitted bits represents bits of data. This scheme has an efficiency of %. In addition, forward error correction (FEC) consumes a small amount of the link bandwidth, resulting in an overall efficiency of ≈%.^[39] The following transmission modes are added in DP

• UHBR 10 (Ultra High Bit Rate 10): &#;Gbit/s bandwidth per lane
• UHBR (Ultra High Bit Rate ): &#;Gbit/s bandwidth per lane
• UHBR 20 (Ultra High Bit Rate 20): &#;Gbit/s bandwidth per lane

The total bandwidth of the main link in a standard 4-lane connection is the aggregate of all lanes:

• RBR: 04 &#; &#;Gbit/s = &#;Gbit/s bandwidth (data rate of &#;Gbit/s or &#;MB/s with 8b/10b encoding)
• HBR: 04 &#; &#;Gbit/s = &#;Gbit/s bandwidth (data rate of &#;Gbit/s or &#;GB/s)
• HBR2: 4 &#; &#;Gbit/s = &#;Gbit/s bandwidth (data rate of &#;Gbit/s or &#;GB/s)
• HBR3: 4 &#; &#;Gbit/s = &#;Gbit/s bandwidth (data rate of &#;Gbit/s or &#;GB/s)
• UHBR 10: 4 &#; &#;Gbit/s = &#;Gbit/s bandwidth (data rate of &#;Gbit/s or &#;GB/s with b/b encoding and FEC)
• UHBR : 4 &#; &#;Gbit/s = &#;Gbit/s bandwidth (data rate of &#;Gbit/s or &#;GB/s)
• UHBR 20: 4 &#; &#;Gbit/s = &#;Gbit/s bandwidth (data rate of &#;Gbit/s or &#;GB/s)

The transmission mode used by the DisplayPort main link is negotiated by the source and sink device when a connection is made, through a process called Link Training. This process determines the maximum possible speed of the connection. If the quality of the DisplayPort cable is insufficient to reliably handle HBR2 speeds for example, the DisplayPort devices will detect this and switch down to a lower mode to maintain a stable connection.^[8](§) The link can be re-negotiated at any time if a loss of synchronization is detected.^[8](§)

Audio data is transmitted across the main link during the video blanking intervals (short pauses between each line and frame of video data).^[8](§)

Auxiliary channel[edit]

The DisplayPort AUX channel is a half-duplex bidirectional data channel used for miscellaneous additional data beyond video and audio (such as I²C or CEC commands)^[8](§) at the device manufacturer's discretion. AUX signals are transmitted across a dedicated set of twisted-pair wires. DisplayPort&#; specified Manchester encoding with a 2&#;Mbaud signal rate (1&#;Mbit/s data rate).^[8](§) DisplayPort&#; introduced a second transmission mode called FAUX (Fast AUX), which operates at &#;Mbaud with 8b/10b encoding (&#;Mbit/s data rate).^[36](§) This can be used to implement additional transport protocols such as USB&#; (&#;Mbit/s) without the need for an additional cable, but has seen little practical use as of

Cables and connectors[edit]

Cables[edit]

Compatibility and feature support[edit]

All DisplayPort cables are compatible with all DisplayPort devices, regardless of the version of each device or the cable certification level.^[40]

All features of DisplayPort will function across any DisplayPort cable. DisplayPort does not have multiple cable designs; all DP cables have the same basic layout and wiring, and will support any feature including audio, daisy-chaining, G-Sync/FreeSync, HDR, and DSC.

DisplayPort cables differ in their transmission speed support. DisplayPort specifies four different transmission modes (RBR, HBR, HBR2, and HBR3) which support progressively higher bandwidths. Not all DisplayPort cables are capable of all four transmission modes. VESA offers certifications for each level of bandwidth. These certifications are optional, and not all DisplayPort cables are certified by VESA.

Cables with limited transmission speed are still compatible with all DisplayPort devices, but may place limits on the maximum resolution or refresh rate available.

DisplayPort cables are not classified by "version". Although cables are commonly labeled with version numbers, with HBR2 cables advertised as "DisplayPort&#; cables" for example, this notation is not permitted by VESA.^[40] The use of version numbers with cables can seem to imply that a DisplayPort&#; display requires a "DisplayPort&#; cable", or that features introduced in DP&#; such as HDR or DSC will not function with older "DP&#; cables", when in reality neither of these are true. DisplayPort cables are classified only by their bandwidth certification level (RBR, HBR, HBR2, HBR3), if they have been certified at all.

Cable bandwidth and certifications[edit]

Not all DisplayPort cables are capable of functioning at the highest levels of bandwidth. Cables may be submitted to VESA for an optional certification at various bandwidth levels. VESA offers three levels of cable certification: RBR, Standard, and DP8K. These certify DisplayPort cables for proper operation at the following speeds:

In April , VESA published an article stating that the DisplayPort cable certification did not have distinct tiers for HBR and HBR2 bandwidth, and that any certified standard DisplayPort cable—including those certified under DisplayPort&#;—would be able to handle the &#;Gbit/s bandwidth of HBR2 that was introduced with the DisplayPort standard.^[40] The DisplayPort&#; standard defines only a single specification for High Bit Rate cable assemblies, which is used for both HBR and HBR2 speeds, although the DP cable certification process is governed by the DisplayPort PHY Compliance Test Standard (CTS) and not the DisplayPort standard itself.^{[36](§, §)}

The DP8K certification was announced by VESA in January , and certifies cables for proper operation at HBR3 speeds (&#;Gbit/s per lane, &#;Gbit/s total).^[41]

In June , with the release of version of the DisplayPort Standard, VESA announced that the DP8K certification was also sufficient for the new UHBR 10 transmission mode. No new certifications were announced for the UHBR and UHBR 20 modes. VESA is encouraging displays to use tethered cables for these speeds, rather than releasing standalone cables onto the market.^[39]

It should also be noted that the use of Display Stream Compression (DSC), introduced in DisplayPort&#;, greatly reduces the bandwidth requirements for the cable. Formats which would normally be beyond the limits of DisplayPort&#;, such as 4K ( × ) at &#;Hz 8&#;bpc RGB/ (&#;Gbit/s data rate when uncompressed), can only be implemented by using DSC. This would reduce the physical bandwidth requirements by 2–3x, placing it well within the capabilities of an HBR2-rated cable.

This exemplifies why DisplayPort cables are not classified by "version"; although DSC was introduced in version , this does not mean it needs a so-called "DP&#; cable" (an HBR3-rated cable) to function. HBR3 cables are only required for applications which exceed HBR2-level bandwidth, not simply any application involving DisplayPort&#; If DSC is used to reduce the bandwidth requirements to HBR2 levels, then an HBR2-rated cable will be sufficient.

Cable length[edit]

The DisplayPort standard does not specify any maximum length for cables, though the DisplayPort standard does set a minimum requirement that all cables up to 2 meters in length must support HBR2 speeds (&#;Gbit/s), and all cables of any length must support RBR speeds (&#;Gbit/s).^{[36](§, §)} Cables longer than 2 meters may or may not support HBR/HBR2 speeds, and cables of any length may or may not support HBR3 speeds.

Connectors and pin configuration[edit]

DisplayPort output on a computer

DisplayPort cables and ports may have either a "full-size" connector or a "mini" connector. These connectors differ only in physical shape—the capabilities of DisplayPort are the same regardless of which connector is used. Using a Mini DisplayPort connector does not affect performance or feature support of the connection.

Full-size DisplayPort connector[edit]

The standard DisplayPort connector (now referred to as a "full-size" connector to distinguish it from the mini connector)^[36]

1. Introduction

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

The use of “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” is per the IETF standard defined in RFC

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

To be considered compatible with Android 11, 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.

Document Structure

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.

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

Each ID is defined as below:

• Device Type ID (see more in 2. Device Types)
  • C: Core (Requirements that are applied to any 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.

Requirement ID in Section 2

The Requirement ID in Section 2 starts with the corresponding 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. /A).

2. Device Types

While the Android Open Source Project provides a software stack that can be used for a variety of device types and form factors, 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.

Device Configurations

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

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 inches (or inches for devices which launched on an API level earlier than Android 11) to 8 inches.

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

Hardware

Handheld device implementations:

• [/H] MUST have at least one Android-compatible display that meets all requirements described on this document.
• [/H-SR] Are STRONGLY RECOMMENDED to provide users an affordance to change the display size (screen density).

If Handheld device implementations support software screen rotation, they:

• [/H]* MUST make the logical screen that is made available for third party applications be at least 2 inches on the short edge(s) and inches on the long edge(s). Devices which launched on an API level earlier than that of this document are exempted from this requirement.

If Handheld device implementations do not support software screen rotation, they:

• [/H]* MUST make the logical screen that is made available for third party applications be at least inches on the short edge(s). Devices which launched on an API level earlier than that of this document are exempted from this requirement.

If Handheld device implementations claim support for high dynamic range displays through , they:

• [/H] MUST advertise support for the , , , , and extensions.

Handheld device implementations:

• [/H] MUST report whether the device supports the GPU profiling capability via a system property .

If Handheld device implementations declare support via a system property , they:

Handheld device implementations:

• [/H] 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.
• [/H] MUST include support for third-party Input Method Editor (IME) applications.
• [/H] MUST provide the Home function on all the Android-compatible displays that provide the home screen.
• [/H] MUST provide the Back function on all the Android-compatible displays and the Recents function on at least one of the Android-compatible displays.
• [/H] MUST send both the normal and long press event of the Back function () 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).
• [/H] MUST support touchscreen input.
• [/H-SR] Are STRONGLY RECOMMENDED to launch the user-selected assist app, in other words the app that implements VoiceInteractionService, or an activity handling the on long-press of or if the foreground activity does not handle those long-press events.
• [/H-SR] Are STRONGLY RECOMMENDED to include a 3-axis accelerometer.

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

• [/H] MUST be able to report events up to a frequency of at least Hz.

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

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

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

• [/H] MUST be able to report events up to a frequency of at least Hz.
• [/H] MUST be capable of measuring orientation changes up to degrees per second.

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

• [/H] SHOULD include a proximity sensor.

Handheld device implementations:

• [/H-SR] Are RECOMMENDED to support pose sensor with 6 degrees of freedom.
• [/H] SHOULD include support for Bluetooth and Bluetooth LE.

If Handheld device implementations include a metered connection, they:

• [/H] MUST provide the data saver mode.

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

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

Handheld device implementations:

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

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

• [/H] The memory available to the kernel and userspace MUST be at least MB if the default display uses framebuffer resolutions up to qHD (e.g. FWVGA).

• [/H] The memory available to the kernel and userspace MUST be at least MB if the default display uses framebuffer resolutions up to HD+ (e.g. HD, WSVGA).

• [/H] The memory available to the kernel and userspace MUST be at least MB if the default display uses framebuffer resolutions up to FHD (e.g. WSXGA+).

• [/H] The memory available to the kernel and userspace MUST be at least MB if the default display uses framebuffer resolutions up to QHD (e.g. QWXGA).

If Handheld device implementations declare support of bit and bit ABIs:

• [/H] The memory available to the kernel and userspace MUST be at least MB if the default display uses framebuffer resolutions up to qHD (e.g. FWVGA).

• [/H] The memory available to the kernel and userspace MUST be at least MB if the default display uses framebuffer resolutions up to HD+ (e.g. HD, WSVGA).

• [/H] The memory available to the kernel and userspace MUST be at least MB if the default display uses framebuffer resolutions up to FHD (e.g. WSXGA+).

• [/H] The memory available to the kernel and userspace MUST be at least MB 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:

• [/H] MUST declare the feature flag .
• [/H] MUST have at least 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:

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

Handheld device implementations:

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

If handheld device implementations include a USB port supporting peripheral mode, they:

• [/H] MUST implement the Android Open Accessory (AOA) API.

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

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

Handheld device implementations:

• [/H] MUST include a microphone.
• [/H] MUST have an audio output and declare .

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

• [/H] MUST declare the feature flag.
• [/H] MUST include an application implementing that can be enabled by VR applications via .

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 , they:

• [/H] MUST provide the following software mapping of HID codes:

• [/H] 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 0x is detected, they:

• [/H] MUST broadcast Intent ACTION_HEADSET_PLUG with "microphone" extra set to 0.

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

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

When API manicapital.comices() is called while the USB peripheral is connected they:

• [/H] MUST list a device of type manicapital.com_USB_HEADSET and role isSink() if the USB audio terminal type field is 0x

• [/H] MUST list a device of type manicapital.com_USB_HEADSET and role isSink() if the USB audio terminal type field is 0x

• [/H] MUST list a device of type manicapital.com_USB_HEADSET and role isSource() if the USB audio terminal type field is 0x

• [/H] MUST list a device of type manicapital.com_USB_DEVICE and role isSink() if the USB audio terminal type field is 0x

• [/H] MUST list a device of type manicapital.com_USB_DEVICE and role isSource() if the USB audio terminal type field is 0x

• [/H] MUST list a device of type manicapital.com_USB_DEVICE and role isSink() if the USB audio terminal type field is 0x

• [/H] MUST list a device of type manicapital.com_USB_DEVICE and role isSource() if the USB audio terminal type field is 0x

• [/H-SR] 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 milliseconds.

If Handheld device implementations include at least one haptic actuator, they:

• [/H-SR]* Are STRONGLY RECOMMENDED NOT to use an eccentric rotating mass (ERM) haptic actuator(vibrator).
• [/H]* SHOULD position the placement of the actuator near the location where the device is typically held or touched by hands.
• [/H-SR]* Are STRONGLY RECOMMENDED to implement all public constants for clear haptics in manicapital.comFeedbackConstants namely (CLOCK_TICK, CONTEXT_CLICK, KEYBOARD_PRESS, KEYBOARD_RELEASE, KEYBOARD_TAP, LONG_PRESS, TEXT_HANDLE_MOVE, VIRTUAL_KEY, VIRTUAL_KEY_RELEASE, CONFIRM, REJECT, GESTURE_START and GESTURE_END).
• [/H-SR]* Are STRONGLY RECOMMENDED to implement all public constants for clear haptics in manicapital.comionEffect namely (EFFECT_TICK, EFFECT_CLICK, EFFECT_HEAVY_CLICK and EFFECT_DOUBLE_CLICK) and all public constants for rich haptics in manicapital.comition namely (PRIMITIVE_CLICK and PRIMITIVE_TICK).
• [/H-SR]* Are STRONGLY RECOMMENDED to use these linked haptic constants mappings.
• [/H-SR]* Are STRONGLY RECOMMENDED to follow quality assessment for createOneShot() and createWaveform() API's.
• [/H-SR]* Are STRONGLY RECOMMENDED to verify the capabilities for amplitude scalability by running manicapital.comlitudeControl().

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 linear resonant actuator, they:

• [/H]* SHOULD move the haptic actuator in the X-axis of portrait orientation.

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

• [/H-SR]* Are STRONGLY RECOMMENDED to have the resonant frequency of the X-axis LRA be under Hz.

If handheld device implementations follow haptic constants mapping, they:

Multimedia

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

• [/H] AMR-NB
• [/H] AMR-WB
• [/H] MPEG-4 AAC Profile (AAC LC)
• [/H] MPEG-4 HE AAC Profile (AAC+)
• [/H] AAC ELD (enhanced low delay AAC)

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

• [/H] H AVC
• [/H] VP8

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

• [/H] H AVC
• [/H] H HEVC
• [/H] MPEG-4 SP
• [/H] VP8
• [/H] VP9

Software

Handheld device implementations:

• [/H] MUST have an application that handles the , , , and intents as described in the SDK documents, and provide the user affordance to access the document provider data by using API.
• [/H]* 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.
• [/H-SR] 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.
• [/H] MUST provide a complete implementation of the API.
• [/H] MUST include a standalone Browser application for general user web browsing.
• [/H-SR] Are STRONGLY RECOMMENDED to implement a default launcher that supports in-app pinning of shortcuts, widgets and widgetFeatures.
• [/H-SR] 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.
• [/H-SR] Are STRONGLY RECOMMENDED to include a default launcher app that shows badges for the app icons.
• [/H-SR] Are STRONGLY RECOMMENDED to support third-party app widgets.
• [/H] MUST allow third-party apps to notify users of notable events through the and API classes.
• [/H] MUST support rich notifications.
• [/H] MUST support heads-up notifications.
• [/H] 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.
• [/H] MUST display the choices provided through in the notification shade.
• [/H-SR] Are STRONGLY RECOMMENDED to display the first choice provided through in the notification shade without additional user interaction.
• [/H-SR] Are STRONGLY RECOMMENDED to display all the choices provided through in the notification shade when the user expands all notifications in the notification shade.
• [/H-SR] Are STRONGLY RECOMMENDED to display actions for which is set as in-line with the replies displayed by .
• [/H-SR] Are STRONGLY RECOMMENDED to implement an assistant on the device to handle the Assist action.

If Handheld device implementations support Assist action, they:

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

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

• [/H]* 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:

• [/H] MUST display the Lock screen Notifications including the Media Notification Template.

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

• [/H] MUST implement the full range of device administration policies defined in the Android SDK documentation.
• [/H] MUST declare the support of managed profiles via the feature flag, except when the device is configured so that it would report itself as a low RAM device or so that it allocates internal (non-removable) storage as shared storage.

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

• [/H] MUST declare the feature flag and set it to .
• [/H] 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 and the APIs.
• [/H] MUST provide access to this user affordance within three interactions from a default Launcher.
• [/H] MUST accurately render in this user affordance the name and icon of each third-party app that provides controls via the API as well as any specified fields provided by the APIs.

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

Handheld device implementations:

• [/H] MUST support third-party accessibility services.
• [/H-SR] 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.
• [/H] MUST support installation of third-party TTS engines.
• [/H-SR] Are STRONGLY RECOMMENDED to include a TTS engine supporting the languages available on the device.
• [/H-SR] Are STRONGLY RECOMMENDED to include a Quick Settings UI component.

If Android handheld device implementations declare or support, they:

• [/H] MUST support the companion device pairing feature.

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

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

• [/H] 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.

Performance and Power

• [/H] 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.
• [/H] 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.
• [/H] 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:

• [/H] MUST ensure a sequential write performance of at least 5 MB/s.
• [/H] MUST ensure a random write performance of at least MB/s.
• [/H] MUST ensure a sequential read performance of at least 15 MB/s.
• [/H] MUST ensure a random read performance of at least 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:

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

Handheld device implementations:

• [/H] 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.
• [/H] MUST report all power consumption values in milliampere hours (mAh).
• [/H] MUST report CPU power consumption per each process's UID. The Android Open Source Project meets the requirement through the kernel module implementation.
• [/H] MUST make this power usage available via the shell command to the app developer.
• [/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:

Security Model

Handheld device implementations:

• [/H] MUST allow third-party apps to access the usage statistics via the permission and provide a user-accessible mechanism to grant or revoke access to such apps in response to the intent.

Handheld device implementations (* Not applicable for Tablet):

• [/H]* MUST back up the keystore implementation with an isolated execution environment.
• [/H]* 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.
• [/H]* 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.
• [/H]* 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 , units of a given SKU are produced. If more than , units of an SKU are produced, a different key MAY be used for each , 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 feature which requires a keystore backed by an isolated execution environment.

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

• [/H] 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.
• [/H] MUST provide user affordance to hide notifications and disable all forms of authentication except for the primary authentication described in Secure Lock Screen. The AOSP meets the requirement as lockdown mode.

Developer Tools and Options Compatibility

Handheld device implementations (* Not applicable for Tablet):

• [/H]* MUST support the shell command .

Handheld device implementations (* Not applicable for Tablet):

• Perfetto
  • [/H]* MUST expose a binary to the shell user which cmdline complies with the perfetto documentation.
  • [/H]* The perfetto binary MUST accept as input a protobuf config that complies with the schema defined in the perfetto documentation.
  • [/H]* The perfetto binary MUST write as output a protobuf trace that complies with the schema defined in the perfetto documentation.
  • [/H]* MUST provide, through the perfetto binary, at least the data sources described in the perfetto documentation.
  • [/H]* The perfetto traced daemon MUST be enabled by default (system property ).

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

Hardware

Television device implementations:

• [/T] MUST support D-pad.
• [/T] MUST provide the Home and Back functions.
• [/T] MUST send both the normal and long press event of the Back function () to the foreground application.
• [/T] MUST include support for game controllers and declare the feature flag.
• [/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:

• [/T] MUST be able to report events up to a frequency of at least Hz.
• [/T] MUST be capable of measuring orientation changes up to degrees per second.

Television device implementations:

• [/T] MUST support Bluetooth and Bluetooth LE.
• [/T] 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:

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

If TV device implementations are bit:

• [/T] The memory available to the kernel and userspace MUST be at least MB if any of the following densities are used:

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

If TV device implementations are bit:

• [/T] The memory available to the kernel and userspace MUST be at least MB if any of the following densities are used:

  • dpi 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:

• [/T] SHOULD include a microphone.
• [/T] MUST have an audio output and declare .

Multimedia

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

• [/T] MPEG-4 AAC Profile (AAC LC)
• [/T] MPEG-4 HE AAC Profile (AAC+)
• [/T] AAC ELD (enhanced low delay AAC)

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

• [/T] H
• [/T] VP8

Television device implementations:

• [/T-SR] Are STRONGLY RECOMMENDED to support H encoding of p and p 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:

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

• [/T] HD p at frames per second with Main Profile High Level.
• [/T] HD i at frames per second with Main Profile High Level. They MUST deinterlace interlaced MPEG-2 video to its progressive equivalent (e.g. from i at frames per second to p at frames per second) and make it available to third-party applications.

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

• [/T] HD p at 60 frames per second with Baseline Profile
• [/T] HD p at 60 frames per second with Main Profile
• [/T] HD p at 60 frames per second with High Profile Level

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

• [/T] HD p at 60 frames per second with Main Profile Level

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

• [/T] MUST support UHD p at 60 frames per second with Main10 Level 5 Main Tier profile

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

• [/T] HD p at 60 frames per second decoding profile

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

• [/T] HD p 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:

• [/T] MUST support UHD p at 60 frames per second with profile 0 (8 bit color depth).
• [/T] Are STRONGLY RECOMMENDED to support UHD p at 60 frames per second with profile 2 (10 bit color depth).

Television device implementations:

• [/T] 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:

• [/T] MUST set the HDMI output mode to select the maximum resolution that can be supported with either a 50Hz or 60Hz refresh rate.
• [/T-SR] Are STRONGLY RECOMMENDED to provide a user configurable HDMI refresh rate selector.
• [] 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:

• [/T] MUST support HDCP

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

• [/T] MUST support HDCP

Software

Television device implementations:

• [3/T] MUST declare the features and .
• [/T] 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.
• [/T] MUST provide a complete implementation of the API.

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

• [/T] MUST display the Lock screen Notifications including the Media Notification Template.

Television device implementations:

• [/T-SR] Are STRONGLY RECOMMENDED to support picture-in-picture (PIP) mode multi-window.
• [/T] MUST support third-party accessibility services.
• [/T-SR] 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 , they:

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

Television device implementations:

• [/T] MUST support TV Input Framework.

Performance and Power

• [/T] 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.
• [/T] MUST ensure a sequential write performance of at least 5MB/s.
• [/T] MUST ensure a random write performance of at least MB/s.
• [/T] MUST ensure a sequential read performance of at least 15MB/s.
• [/T] MUST ensure a random read performance of at least MB/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:

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

If Television device implementations do not have a battery they:

If Television device implementations have a battery they:

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

Television device implementations:

• [/T] 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.
• [/T] MUST report all power consumption values in milliampere hours (mAh).
• [/T] MUST report CPU power consumption per each process's UID. The Android Open Source Project meets the requirement through the kernel module implementation.
• [/T] SHOULD be attributed to the hardware component itself if unable to attribute hardware component power usage to an application.
• [/T] MUST make this power usage available via the shell command to the app developer.

Security Model

Television device implementations:

• [/T] MUST back up the keystore implementation with an isolated execution environment.
• [/T] 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.
• [/T] 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.
• [/T] 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 , units of a given SKU are produced. If more than , units of an SKU are produced, a different key MAY be used for each , 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 feature which requires a keystore backed by an isolated execution environment.

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

• [/T] 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.

Developer Tools and Options Compatibility

Television device implementations: