Keep the metadata names intact
Android's MediaFormat reference exposes colour standard, transfer and range as separate properties. That structure reflects different information, not interchangeable names for resolution.
A diagnostic reporting one field does not establish the others. Keep unknowns visible instead of completing a specification from a brand or codec label.
Separate metadata from the rendered picture
The source can declare properties while the app, output conversion and display each affect presentation. A TV's received signal can differ from the source field.
Do not infer source accuracy from a colourful menu or a more vivid picture. Those observations may concern another rendering layer.
Use the same reference passage
Choose a permitted familiar scene and keep player, output and display processing consistent. Record the concrete symptom: lost shadow detail, bright clipping or altered neutral colour.
Do not change every colour control together. A result after several adjustments cannot identify which stage corrected or concealed the problem.
Ask the developer the narrow question
Provide the reported source fields and actual app/device versions. If another supported path differs, include that comparison with the same unchanged source.
A platform API field is developer information, not a universal consumer settings menu. Avoid inventing controls from the property names.
Keep the result conditional
A compatible output mode and attractive picture do not certify metadata accuracy for an entire catalogue. Keep source and output observations named separately.
No colour signal, display or IPTV source was measured here. This article explains documentation structure and a proposed support method, not calibration or a universal colour preset.
Preserve the distinction in screenshots
If sharing a diagnostic, retain enough context to show whether a field describes the input stream, decoder or output. A cropped image that leaves only one value can lose that meaning. Describe sensitive fields rather than sharing private addresses. The useful record combines field name, stage and observed picture symptom, allowing the developer to ask a focused question rather than treating every colour complaint as a generic HDR toggle issue. If the fields are absent from the user interface, ask the app developer what diagnostic evidence it supports. A developer API reference should not become an instruction for the viewer to locate an unverified hidden menu or alter undocumented values.
Sources and scope
Scope notes distinguish published documentation, supplied information and editorial methods. They do not report a hands-on service test.
- Android media format fields — Official current API excerpts: width/height, colour standard/transfer/range and AVIF MIME context. No app's metadata interpretation inspected.
- Android format tables — Official current excerpts distinguish still-image and video formats with version/profile qualifications; no universal device/app support inferred.
