Network events
Things that happened during the session, as opposed to readings taken every second: call and data failures, plus the graded transitions described in Health grades. Every event carries the reading that caused it and appears in the events log, as markers on charts, and on the map, so you can jump straight to the moment that mattered.
| Metric | What it means | Unit | How to read | Source | Learn more |
|---|---|---|---|---|---|
Call Failsevents.call_drops | Count of detected voice call failures during the session. | Fails | Lower is better | YANL | Reference |
Data Failsevents.data_drops | Count of detected data connectivity failures during the session. | Drops | Lower is better | YANL | Reference |
Network Events Logevents.recent | Recent network-related events (handover, RAT change, etc.). | — | — | YANL | Reference |
Event types
Every event is written to the session log. What you see on screen is a separate choice: the categories below can be switched on and off in Settings on the phone, and under Events shown in the web viewer. Switching a category off hides its markers, and never removes anything from the recording.
| Category | Events | Shown by default |
|---|---|---|
| GPS accuracy | GPS accuracy degraded, poor, recovered | No, they are very frequent |
| Cell changes | Cell change | No, frequent while moving |
| Network mobility | RAT change, Band change, Tracking area change, Handover | Yes |
| Service state | No service, Emergency only, Radio off, Service restored | Yes |
| Data connection | Data Connected, Data Lost, Data Unavailable, Data path changed | Yes |
| Calls | Call Started, Call Ended, Call Ringing, Call Failed/Dropped | Yes |
| Power and radio state | Device idle, Device active, Power save on, Power save off, Radio dormant, Radio active | No, see below |
| Signal health | Cellular and Wi-Fi signal degraded, poor, recovered | Yes |
| Notes | Your own notes | Always shown |
Power and radio state
These mark the moments when the device or its radio changed how it behaves:
- Device idle / Device active: Android put the phone into deep doze, which suspends background network access, or brought it back out. Deep doze needs the phone to be still, unplugged and screen-off for a sustained period, so it rarely appears during hands-on testing.
- Power save on / off: battery saver was switched on or off, which throttles background work.
- Radio dormant / active: the mobile data connection stayed up while the radio link itself was released to save power, then came back. The next packet after a dormant spell has to wake the radio, which is why a first request can be slower than the ones that follow it. Brief flickers are ignored, so an event means the state actually held.
They are hidden by default because they are context for analysis rather than problems in their own right. Switch the category on when you are working out why something was slow while the phone was idle, and read them alongside the doze, battery saver and data activity readings on Device performance and Cellular radio.