Xiaomi Redmi Note 8 64Gb+6Gb Dual LTE [59/132] Video decoding

If device implementations support VP9 codec, they:

SHOULD support writing Matroska WebM files.

5.3. Video Decoding

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

[C-1-1] MUST support dynamic video resolution and frame rate switching through the

standard Android APIs within the same stream for all VP8, VP9, H.264, and H.265 codecs

in real time and up to the maximum resolution supported by each codec on the device.

If device implementations declare support for the Dolby Vision decoder through

HDR_TYPE_DOLBY_VISION , they:

[C-2-1] MUST provide a Dolby Vision-capable extractor.

[C-2-2] MUST properly display Dolby Vision content on the device screen or on a standard

video output port (e.g., HDMI).

[C-2-3] MUST set the track index of backward-compatible base-layer(s) (if present) to be

the same as the combined Dolby Vision layer's track index.

5.3.1. MPEG-2

If device implementations support MPEG-2 decoders, they:

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

5.3.2. H.263

If device implementations support H.263 decoders, they:

[C-1-1] MUST support Baseline Profile Level 30 and Level 45.

5.3.3. MPEG-4

If device implementations with MPEG-4 decoders, they:

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

5.3.4. H.264

If device implementations support H.264 decoders, they:

[C-1-1] MUST support Main Profile Level 3.1 and Baseline Profile. Support for ASO

(Arbitrary Slice Ordering), FMO (Flexible Macroblock Ordering) and RS (Redundant Slices)

is OPTIONAL.

[C-1-2] MUST be capable of decoding videos with the SD (Standard Definition) profiles

listed in the following table and encoded with the Baseline Profile and Main Profile Level

3.1 (including 720p30).

SHOULD be capable of decoding videos with the HD (High Definition) profiles as indicated

in the following table.

If the height that is reported by the Display.getSupportedModes() method is equal or greater than the video

Page 59 of 132