Kepong bench
A crash that exists only on a mid-range Xiaomi will not appear on the Pixel in your drawer. Reproduction here means putting the same skin on the desk in Kepong and walking the steps until the process dies or it does not.
Malaysian Android traffic is heavy on Samsung, Xiaomi, Oppo, Vivo, and Realme. Office test racks still skew toward whatever was on promotion at a carrier store in Singapore or a Pixel bought for development. The gap is where “cannot reproduce” lives.
A bench day is for a named fault. If you do not yet know the signature, start with a crash stability audit so we are not wandering the app hoping something dies.
Engineers who already have a crash signature or a tester video, but cannot reproduce it on office flagships — especially Xiaomi HyperOS, Oppo ColorOS, or older Samsung One UI builds common in Malaysian retail.
Reproduction notes: device, API level, skin build, steps that hold, logcat or tombstone excerpt, and whether the fault is absent on a control unit.
One named signature or tester scenario per bench day. Extra signatures are extra days or a quoted block.
We check whether the Kepong bench has the OEM, API level, and roughly the skin generation you need.
We follow your steps, then adjacent paths if the first sequence does not fire.
Notes and excerpts go back the same day when the fault appears, or we say it did not appear on the units we hold.
The APK or Play internal track link, mapping file, exact signature or video, and any account credentials required to reach the crashing screen.
The bench is finite. If we do not hold the exact model, we say so before you book the day. We will not pretend a nearby model is the same skin build.