Calculated by the app
Most tiles show values straight from Android or iPerf3. The app also derives these before display and logging:
| Derived value | What it means | How we work it out |
|---|---|---|
| RX power | Received RF power, in easier-to-read units | Converted from signal strength (dBm) into watts and scaled to W / mW / µW / nW / pW. It’s a restatement of signal strength, not a separate measurement. |
| Distance to tower | Rough range to the serving LTE cell | Estimated from the cell’s timing-advance value. A ballpark figure, LTE only, and often blank, because the phone only reports timing advance while actively connected. |
| Wi‑Fi throughput | Wi‑Fi download or upload speed | Inferred, not reported directly: Android gives total and mobile data usage, so we take the Wi‑Fi share as the difference. |
| Live Mbps | Real-time throughput on charts | Worked out from how many bytes moved between one-second samples. |
| Average C/N₀ | GNSS signal quality | The average signal-to-noise of the satellites actually used in the position fix. |
| Data age | How fresh a network scan is | How long ago the reading came from the hardware. |
| Chart trend lines | Smoothed trends and momentum on charts | Standard moving-average and momentum indicators, calculated on the device from recent history (app charts only). |
These appear in tiles or charts labelled with the underlying metric (e.g. Wi‑Fi DL is marked YANL in the Metrics reference because of the Total − Mobile step).
Derived values are estimates built on the raw readings, so they inherit the same freshness rules: when the underlying source is stale or unavailable, the derived tile blanks rather than showing an out-of-date figure. See Data quality & real-world behaviour.
Where the raw values come from
For the underlying modem and OS readings (before derivation), see Where the readings come from.
Last updated on