Why One UI ANRs show up in Malaysia before they show up on your office Samsung

The office unit is not the cohort

Play Console will happily show an ANR rate climbing while every Samsung in the drawer remains smooth. That drawer is usually an S-series or a recent A-series bought for development. Malaysian retail, especially below the RM 1,200 band, is full of older A-series and leftover One UI builds that still run the same application ID.

When we read ANR traces for Klang Valley grocery and logistics apps, the freeze often sits in a ContentResolver query or a broadcast during startup. On a flagship the query returns before input dispatch times out. On a warmer, slower unit the same query becomes the ANR that Play attributes to your process.

What the trace is actually saying

An ANR trace is not a crash stack. It is a snapshot of who held the main thread when the system gave up waiting. We look at the head of the main thread, then at binder calls, then at whether a ContentProvider or a Receiver is doing work that belongs off the main thread.

One UI overlays can add their own services into that picture. A media scan, a battery-learning job, or a Samsung-specific clipboard helper may appear in the trace without being “your bug” in the moral sense — but it is still your ANR in Play Console if your process was the one declared frozen.

What to send us if this is your week

Export the ANR cluster, not a screenshot of the vitals graph. Include the mapping file for that version code. Name the Samsung models your testers hold, even if they never froze. The gap between those models and the models in the cluster is usually the investigation.

Request an audit briefing if this is the cluster on your desk this week.