Media diagnostics · Primary-source explanation; examples are illustrative. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Distinguish the two rendering layers
The Media3 surface guide explains that some Android TV devices run their UI below the full display resolution and upscale it. It identifies SurfaceView as necessary for full display resolution video on such devices, while TextureView follows a different rendering path. Therefore a diagnostic reporting the interface size cannot by itself establish the actual video surface output or the programme source resolution. Keep those measurements under separate names.
Use a layered example
For an original conceptual case, a television has a 4K display while its application interface is rendered at 1080p before scaling. A text label based only on the UI dimension could misdescribe the display or the video path. Record the actual display mode, surface configuration and media dimensions when the implementation exposes them. These invented conditions illustrate the documented distinction and are not a test result from any named television model.
Make surface changes a developer decision
The documentation lists tradeoffs involving power, timing, secure output and view lifecycle, with version specific behaviour. Do not present a surface switch as a universal viewer setting or guaranteed quality upgrade. An app developer should choose the supported surface for the design and test its real controls and transitions. This article explains why a UI size number is incomplete evidence; it does not prove native 4K source detail, actual UK IPTV support or identical behaviour on every Android TV device.