Treat a completed multi-sample window as evidence of the browser-delivered controller signal.
IP-CTL-01 / AXES / BUTTONS / TIME
Gamepad Vibration Test
Run strong/weak motor channels at low/high intensity with explicit Felt or Not felt confirmation.
Controller vibration is missing or feels asymmetric in games.
This focused entry uses the shared Controller protocol. The measurement logic and Evidence version remain identical to the complete lab.
Remove the easiest false alarms first.
01
Connect one controller, press a button and keep this tab visible.
02
Place the controller on a stable surface before any idle capture.
03
Test USB and Bluetooth as separate sessions instead of changing mid-run.
Run one repeatable protocol.
- 01
Connect and activate the controller.
- 02
Run each exposed strong/weak low/high step from a user gesture.
- 03
Confirm Felt or Not felt after every step, then compare connection modes.
Evidence the result should expose.
DIRECT / INFERREDActuator API
DIRECT / INFERREDPer-step request
DIRECT / INFERREDPer-step human response
Separate observed, review and inconclusive.
Repeat the same protocol twice with the same connection before escalating persistent drift, bounce or missed transitions.
No Gamepad API signal, an unsupported actuator or one release spike cannot prove a physical controller fault.
Start with the likely path, then retest.
01
Unsupported browser mapping
02
Disabled vibration
03
Connection mode