Missing vibration is frustrating because games, browsers, and operating systems each expose rumble differently. Start with the Vibration Test on a desktop Chromium browser over USB. If the page reports no vibration actuator, that often means the web stack lacks access, not that the motors are dead.
Browser versus native rumble
Native Xbox, DualSense, and DualShock titles can use richer haptic channels than the basic Gamepad API dual-rumble model. Adaptive DualSense effects and some impulse triggers will not appear in a simple web pulse. A successful browser pulse only proves basic actuator access. A failed browser pulse needs a USB retest and a native game check before you replace hardware.
- Prefer USB for the first rumble experiment.
- Close exclusive apps that may lock the pad.
- Confirm detection on Controller Detection.
- Run a full input pass on the Controller Tester.
- Update official firmware tools from the manufacturer when available.
Bluetooth sometimes omits rumble in browsers even when games still shake the pad. That mismatch is a known web limitation. Document browser, connection type, and whether native games rumble before buying replacement motors.
When hardware is likely
If USB Chromium cannot pulse, native games also stay silent, and the OS sees the pad, then motors, drivers, or board power deserve attention. Fightsticks and some generic pads never expose vibrationActuator at all.
Continue with brand tools such as PS5 Vibration Test or Xbox Vibration Test when you already know the platform. For broader troubleshooting trees, open Troubleshooting and the blog.
Gamepad Tester Pro will not claim a motor is destroyed based on a single missing web actuator flag. Gather USB and native evidence, then decide on repair. That approach avoids false alarms and keeps your gamepad tester workflow aligned with how browsers actually work.
Also confirm buttons and sticks still report cleanly while you chase rumble. A pad that fails multiple systems may need deeper board work than a single motor swap. Keep a short log of each test so you do not repeat the same blind steps across browsers.