Start with a clean baseline
Use raw browser input to separate a physical control/event problem from game/app mapping. Test the exact failing key, button, axis or wheel action rather than a generic connected/not-connected state.
Live evidence
Relevant checks
Gamepad Controller TestTest browser-detected controller buttons and analog axes.
→Controller Stick Drift TestMeasure resting stick offset to identify possible stick drift.
→Controller Dead Zone TestInspect how far a stick moves before input appears.
→Controller Trigger TestInspect trigger minimum, maximum, and analog range.
→First sequence
Do the high-signal checks before risky changes
- 1
Connect controller and run Gamepad Test
- 2
Check stick center before changing game dead zones
- 3
Compare USB and Bluetooth if both are supported
Decision points
What the result should change
If raw events are correct herePrioritize app/game bindings, profiles, sensitivity or remapping.
If duplicates/drift reproduce hereThe symptom is independent of the affected app; compare connection mode and official calibration.
If the entire device freezes intermittentlyPrioritize receiver/cable/power/interference before a single switch or stick component.
Browser can help check
- Read browser-exposed gamepad buttons and axes
- Measure resting stick offset
- Visualize trigger/stick ranges
Browser cannot prove
- Calibrate every controller firmware
- Read console-only diagnostics
- Prove mechanical wear source from input values alone
Repair boundary
Know when to stop browser troubleshooting
- Do not flash unofficial firmware to fix an input symptom.
- Browser polling estimates are not kernel-level USB analyzers.
- Cleaning/disassembly methods vary by manufacturer and switch design.
Used-device inspection
What to verify before paying or signing off a repair
- Every key/button and repeated-press behavior
- Stick/axis center, full range and dead zones where applicable
- Wireless receiver/Bluetooth plus wired mode if supported