Android measurement limits
Android serving and neighbour cell measurement limitations
Android can expose LTE and 5G cell information, but the available serving and neighbour values vary significantly by device, modem, OEM implementation, Android version, permissions and the network state.
What an Android app receives
Apps receive cellular information through Android telephony APIs, not direct protocol traces or unrestricted modem diagnostics. Android may provide registered and unregistered cell records. The registered record is the best starting point for serving context; unregistered records can be useful observations, but they are not a guaranteed complete neighbour list and their values may be unavailable.
Network Drive Test displays the radio measurements Android telephony APIs expose and logs available signal, quality, serving-cell and GPS context. It cannot force a handset, OEM or network to reveal a value that is not exposed.
Why two phones can report different data
| Factor | Practical implication |
|---|---|
| Modem and chipset | Cell reporting capability and timing can differ between devices. |
| OEM implementation and Android version | Android APIs provide a common interface, but device implementations can omit, delay or mark fields unavailable. |
| Permissions and location state | Access to cellular information is subject to Android permission and privacy rules; a missing permission can reduce what an app receives. |
| Network mode | LTE, NR NSA and NR SA do not present the same serving relationship or measurement context. |
| Network state | Mobility, idle/connected state and operator configuration influence which cells are reported at a given moment. |
Serving, neighbour, LTE and NR: read carefully
A serving cell is the cell Android identifies as registered for the current connection context. An unregistered LTE or NR record may be a detected cell, but it is not proof that every relevant neighbour, measurement event or handover candidate is available. LTE and NR records also have different identities and measurement fields; absent fields should be recorded as unavailable, not converted into zero or a diagnosis.
In NSA, LTE and NR can coexist in a dual-connectivity context. In SA, NR is the primary radio-access context. What Android exposes in either case remains device- and implementation-dependent. A screen that shows NR does not, by itself, prove the complete radio topology, carrier aggregation state or protocol-level handover cause.
Use the limitation as field context
- Record the exact device, Android version, app version, route and time window.
- Keep serving-cell information alongside the readings Android exposes.
- Mark missing or unavailable fields explicitly.
- Repeat a suspicious observation with the same method before comparing devices.
- Use operator tools or a professional platform when the task requires protocol traces, scanner data, chipset diagnostics or acceptance-grade multi-device benchmarking.