Record the source requirement
Obtain reliable metadata for the permitted reference: codec, profile, level where known, dimensions, frame rate and bit depth. Keep the fields identified by name. A marketing4K badge is not a substitute for a stream specification.
A source can change configuration between programmes or variants. If only one item fails, preserve that specific item rather than declaring the entire codec unsupported.
Understand the platform evidence
Android documents supported framework formats and provides codec capability APIs. Its VideoCapabilities API includes a check for a size-and-rate combination, while CodecCapabilities describes profile and level support. These are developer mechanisms.
A consumer cannot assume that installing an app changes the hardware's supported combinations. Nor does the existence of a framework API certify that a third-party player queries or handles every capability correctly.
Separate capability from observed performance
A stated supported configuration is not identical to a sustained benchmark in a particular thermal, power and workload condition. Keep ordinary device conditions stable when comparing references. Do not deliberately stress or overheat hardware to prove a point.
If a lower-complexity permitted reference works, record its full configuration. A lower resolution can differ in other fields too, so it is evidence rather than a uniquely identified cause.
Give the developer a usable report
Include the device model, Android version, app version and source configuration. State whether the app rejects the item, shows no picture, produces artefacts or begins and then drops frames. Those are different failures.
Ask the developer which decoder path is used and whether the supplied configuration is supported. Do not invent an advanced user menu from a developer API name.
Keep the conclusion bounded
A working test applies to the stated item and setup. It does not mean every HEVC stream, every10-bit profile or every high frame rate will behave the same way.
This guide follows official framework and API documentation. No device capability query or physical performance test was executed, and IPTV Canada service/player compatibility remains unverified.
Do not infer performance from the interface
An app menu can be responsive while a particular video configuration exceeds the chosen playback path. Conversely, a heavy catalogue interface can feel slow while a simple permitted reference plays normally. Record menu navigation and decoded motion as separate tasks. That helps the developer distinguish interface workload from configuration-specific decoding or presentation behaviour.
Sources and scope
Scope notes distinguish published documentation, supplied information and editorial methods. They do not report a hands-on service test.
- Android supported media formats — Official current documentation excerpts: container/codec and profile qualifications. No device-wide or IPTV player guarantee inferred from a framework table.
- Android codec capabilities — Official current API documentation excerpt: profile/level and format capability queries; developer mechanism, not a consumer menu or completed device test.
- Android video size and rate capabilities — Official current API excerpt: size/rate combinations and qualified performance information; no benchmark performed.
