03 Diagnostic logger

Unraveller of All Reason

Diagnostic logger

Observe the system. Record the evidence.

by YubeGreen

SESSION24—08—31 / 02:16

  1. CPUawake
  2. APPbackground
  3. DOZEidle
  4. FCMreceived
  5. WAKEevidence

Luonnatar

changes.

Unraveller

observes.

A diagnostic tool should not keep the app alive or alter the test environment. Doing so would contaminate the evidence it is meant to collect.

Leave a trail that can be examined later.

The aim is not to guess why Android stopped a background process. It is to collect enough ordered evidence to make the next analysis grounded.

STATE

App enters background

importance · process state

SYSTEM

Device enters idle

doze · freeze · suspend

NETWORK

Connectivity changes

network · VPN · route

EVENT

Message and notification evidence

GMS · FCM · notification timing

Several signals. One ordered record.

01 / POWER

CPU & suspend

Wake-related evidence and device power transitions.

02 / IDLE

Doze & freeze

The states surrounding delayed background work.

03 / ROUTE

Network & VPN

Connectivity and route changes in the same timeline.

04 / MESSAGE

GMS, FCM & notification

Arrival, handling, and visible notification timing.

Observe without becoming the experiment.

Structured, timestamped, and intentionally quiet: a record for understanding background behavior after it happens.

PAIRLuonnatarChange the conditions
DOWNLOAD / 03

Unraveller of All Reason

Available on GitHub.