Stats for Nerds, Support & Diagnostics
Troubleshooting is a first-class part of the app, because most IPTV problems are
provider-specific or device-specific and cannot be reproduced anywhere else.
Stats for Nerds New in Beta 19
Open it from Live TV Actions Bar › More › Stats for nerds.
It draws in the upper-left corner over video, refreshes about once a second, and hides
itself behind the Guide, menus and dialogs. It is a read-only display: it records nothing
and does not alter playback.
Fields are shown when the information is actually available, and omitted when it is not.
Beta 21 added a playback-diagnosis block: engine state, buffer depth and positions,
rebuffer count and duration, link estimate, how long it has been since data last arrived,
bitrate, load errors, the stream host (sanitized), the active buffer profile, recovery
state, and what background Guide work is doing right now. It is scoped to the player
actually on screen, so a background pre-buffer’s rebuffers never appear in it.
Playback information it can show
- Playback engine and mode
- Content classification — LIVE, CATCH-UP, VOD or RECORDING
- Player state, and the playback generation
- Video resolution and frame rate
- Video codec and MIME type
- The active video decoder
- Audio codec, channel layout and sample rate
- The active audio decoder
- Declared bitrate, when the stream provides one
- Buffer duration
- Live-edge offset, but only when the stream really has a live edge worth trusting
- Rendered and dropped frame counters
- App and native memory use, and memory pressure
- The last playback-recovery step
Display and output information it can show
- The current output resolution and refresh rate
- A summary of what the display reports it can do — maximum resolution and
maximum refresh rate, reported separately
- HDR capability
- HDR output state, where Android exposes it
- Wide colour gamut information
- HDCP level, where Android exposes it
- An HDMI connection indication, where it can be established reliably
Display and output rows are shown when Android and the device expose them,
and are not guaranteed on every device. Older Android versions expose less, and some
devices expose nothing at all — in which case the row is simply absent.
On HDMI accuracy.
PureFusionIPTV does not guess HDMI 2.0 versus HDMI 2.1. Android exposes no
trustworthy public API for the HDMI protocol version or the negotiated TMDS/FRL link on an
ordinary device. Therefore the HDMI version row is omitted when it is not
available, TMDS and FRL link state are never inferred, and a
display capable of 4K120 is not treated as proof of HDMI 2.1.
This is deliberate: accurate missing data is more useful in a support conversation than a
confident wrong number. The same rule applies to HDCP, HDR and output mode — reported
when the platform reports it, absent when it does not.
Nothing that identifies your television is read. The display descriptor is consulted only
for how the panel is attached; manufacturer, model, product name, year and serial are never
read, stored or shown.
Support & Diagnostics, and crash reporting
From the TV, open Settings › Features & Tools › Support &
Diagnostics.
- Copy Diagnostics, and a screenshot-friendly on-device summary
- Report a Problem, with your own description added
- A PF report ID to quote when you ask for help
- Release-safe redaction of provider passwords, authorization tokens, API keys, full
playlist and stream addresses, MAC addresses and SMB credentials
- A consent flow — automatic crash collection is off by default, and nothing is
uploaded unless you choose to send it
- Retained crash-session diagnostics that survive the crash itself
- Evidence for deaths Android does not hand to the app, including native crashes and
app-not-responding events
- Decoder lifecycle information, format changes and surface transitions
- Playback recovery evidence
Beta 19 significantly expands what a future crash report contains — particularly
what was playing and what was decoding at the moment of a native death.
This is richer diagnostics, not a fix. The intermittent native playback
problem reported on the onn 4K Pro is still under investigation and is
not claimed fixed.
Back to categories