Identify the media type
Android's documentation separates still-image and continuous-video support. Its MediaFormat reference describes AVIF still-image data using AV1 coding.
That relationship does not make a thumbnail or photograph a substitute for the intended video test. Keep image versus video identified when reading a table or diagnostic.
Read the version and profile qualification
Framework format tables include version and capability conditions. Do not copy a still-image row into a claim that every player on that Android version handles all AV1 video profiles.
A third-party application can use its own supported path. The existence of a platform API is not an inspection of that app's implementation.
Record the actual video requirement
For the permitted video reference, collect codec, profile, dimensions, frame rate and bit-depth information where available. A single still frame does not exercise sustained decoding or audio synchronization.
Keep output display requirements separate as well. A4K television accepting an image does not certify the entire video pipeline.
Use the relevant comparison
Test the intended supported player with authorised reference media and record opening, picture, sound and continued motion as separate results.
If a diagnostic rejects the configuration, give the developer its exact fields rather than claiming that a working AVIF image disproves the error.
Keep the conclusion bounded
A successful photo demonstrates that image path under stated conditions. A successful video applies to its particular configuration and device.
No image or video was tested here. This explanation follows official format distinctions and does not certify every AV1 source or IPTV Canada app.
Do not infer performance from a poster
A catalogue poster can load through a general image library while programme playback uses another parser, decoder and presentation path. The poster appearing is therefore an interface success, not evidence that the programme format is supported. If playback fails after the poster is visible, report that stage accurately. It helps support avoid investigating image loading when the actual failure begins at video launch or sustained decoding. If a poster appears but selecting Play produces an error, preserve that exact sequence. The image result and the video launch result belong to different stages and can be reported without inventing a single shared decoder requirement.
Sources and scope
Scope notes distinguish published documentation, supplied information and editorial methods. They do not report a hands-on service test.
- Android format tables — Official current excerpts distinguish still-image and video formats with version/profile qualifications; no universal device/app support inferred.
- Android media format fields — Official current API excerpts: width/height, colour standard/transfer/range and AVIF MIME context. No app's metadata interpretation inspected.
