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
Keyboard TestPress keys and verify that the browser receives the expected keyboard events.
→NKRO Keyboard TestCheck how many simultaneous key presses your browser receives.
→Keyboard Ghosting TestTest key combinations for missed or phantom keyboard events.
→Keyboard Chatter TestLook for duplicate key presses that may indicate switch chatter.
→First sequence
Do the high-signal checks before risky changes
- 1
Test the problem key in DeviceOK
- 2
Compare the same key in another app
- 3
Check layout/profile/game binding only after a browser pass
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
- Observe standard keyboard events
- Compare simultaneous key combinations
- Detect repeated browser key events
Browser cannot prove
- Read every vendor macro layer
- Measure switch electrical resistance
- Flash keyboard firmware
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