Prove supported 10-bit playback on Android TV #11

At a glance

Scope clarification

“10-bit decoding” may mean HEVC Main 10, VP9 Profile 2, AV1 10-bit, HDR10, or merely a file whose stream reports ten-bit depth. Support must be defined as a tested matrix, not a single checkbox.

Playback contract

• Prefer hardware decoding where the device reports a compatible decoder
• Define software fallback, thermal limits, and unsupported-device behavior
• Preserve HDR metadata only when the full output chain supports it
• Distinguish direct original playback from converted HLS or MP4

Acceptance criteria

• The accepted codec, profile, level, container, chroma, and HDR matrix is documented
• Capability checks select only decoders the device can actually sustain
• Unsupported sources fall back or fail with a clear explanation instead of a black screen
• Audio tracks, subtitles, seeking, resume, and frame-rate switching work on accepted fixtures
• Software decoding has explicit resolution, frame-rate, memory, and thermal bounds
• Telemetry distinguishes codec rejection, decoder initialization, dropped frames, and output incompatibility
• Representative Android TV and Fire TV hardware passes a sanitized 8-bit and 10-bit fixture matrix

Implementation notes

• Resolve the Media3, libVLC, or hybrid player boundary before promising broad 10-bit support
• Do not infer support from emulator playback or codec enumeration alone