Investigations

Named crash work, not a monitoring login.

Each investigation is a finite piece of desk time: exports in, a written pack or note out. The flagship is the fourteen-day crash stability audit. The others exist for weeks when that is more than you need.

Black Android phone resting on a pale wooden desk beside a notebook

Flagship investigation

Android Crash Stability Audit

A fourteen-day reading of one Android app’s crash and ANR clusters, drawn from Play Console, tombstones, and a small OEM bench in Kepong.

Person holding a smartphone with both hands against a soft interior background

Focused reading

ANR and Main-Thread Stall Review

A shorter pass that treats Application Not Responding traces as their own problem, not as leftover crash tickets.

Smartphone standing upright on a clean desk next to a plant

Before the production track

Pre-release Stability Gate

A fixed window of crash and ANR reading on a release candidate, so a staged rollout does not inherit last version’s unresolved clusters.

Two smartphones lying on linen beside a ceramic cup

Weekly desk time

Recurring Crash Triage

A standing weekly reading of new crash clusters after a rocky release, so signatures do not pile up unread between sprints.

Smartphone face-up on a dark surface with the screen illuminated

Kepong bench

OEM Device Reproduction

Hands-on reproduction of a named crash or freeze on Samsung, Xiaomi, Oppo, Vivo, and Realme units kept in Kepong, rather than on a Pixel that never showed the fault.