Latency & full test

How often the controller reports to the phone: the polling rate in Hz and the interval between reports in milliseconds. It is not end-to-end lag from your thumb to the picture — that also depends on the display, the game and the phone, and no app can measure it from the inside. What it is good for is comparing two pads, or the same pad on Bluetooth versus USB.

That is normal for most Bluetooth pads; USB and 2.4 GHz dongles usually report faster. The reading is also capped by how quickly Android delivers input events, so a high-rate pad can read lower here than on a PC. Tag the connection type before sampling and your saved sessions stay comparable.

It is how much the reporting interval varies. Two pads can share the same average interval while one reports evenly and the other in bursts — the uneven one feels worse, and jitter is what reveals it. The interval distribution chart and session comparison make it visible. (Pro)

Six steps: every button, stick range, stick circularity, trigger travel, resting drift and vibration. It walks you through them in order and gives a pass, check or fail for each, plus a report you can share. Around two minutes if you skip nothing.

Check usually means incomplete input rather than a fault: a stick that never reached every edge, or a trigger not pulled all the way, so that step is worth re-running. Fail on drift or vibration points at hardware — see “Can drift be fixed?” and “The vibration test doesn't do anything” for what to try. Skipped steps do not count towards the result.

Export renders the result as one long image and hands it to your phone's share sheet, so you can send it to a seller, a repair shop or a friend — the app uploads nothing. A free export asks you to watch a short video ad first; with Pro it exports without ads.