Controller Diagnostics
Run both rumble motors on their own, try a few pulse patterns, and confirm by feel whether each one is actually working.
Checking for a controller…
No controller detected
Connect a controller by USB or Bluetooth, then press any button — most browsers won't notice it until you do.
Checking this controller…
Send a short pulse at a chosen strength to find the lowest level you can still feel.
These play a short sequence so you can tell a motor is actually responding to changing commands, not just buzzing at one fixed level.
Nearly every modern rumble controller has two separate motors, not one. The strong motor spins an off-centre weight slowly for a deep, heavy rumble, usually felt under your left hand. The weak motor spins a smaller weight quickly for a sharper, buzzier feel, usually under your right hand. They run independently, which is exactly why one can fail while the other keeps working perfectly.
A browser can confirm it successfully sent a vibration command, but it has no way to confirm the motor actually moved, so this page asks you directly. Press the controller against your hand or rest it on your leg rather than a hard desk, since a healthy motor can still be hard to notice through a loose grip or a solid surface.
A single buzz can be misleading: a motor running constantly at low power can feel similar to a healthy one firing briefly. Patterns like the double pulse and heartbeat change intensity and timing partway through, so you can tell the motor is genuinely responding to new commands rather than stuck at one level.
Some newer controllers add small motors inside the triggers themselves, separate from the two main grip motors, used for effects like a rifle's recoil or a car's brakes. Support for testing them from a browser is inconsistent. A "not supported" result here almost always means the browser or current connection doesn't expose that effect, not that the trigger motor is broken.
Plug in over USB, or pair over Bluetooth in your system settings first. Chrome and Edge currently offer the most complete vibration support; Firefox and Safari vary by controller.
Pair the controller in your device's Bluetooth settings, then open this page in Chrome. Vibration support on Android varies more by controller model than by phone.
Pair an MFi or Bluetooth controller in Settings, then open this page in Safari. Vibration support here is the least consistent of any platform, so a "not supported" result is common even with a controller that vibrates fine on a games console.
Plug in over USB or pair over Bluetooth, then use Chrome or Firefox. Some distros need a one-time udev rule for certain Bluetooth controllers to be recognised by the OS at all — if the controller isn't visible at the system level, vibration won't work here either.
Check the support line above first; if it reports no vibration actuator at all, the issue is almost certainly the browser or the connection rather than the controller. Try a wired USB connection if you're on Bluetooth, and try Chrome if you're testing in a different browser.
That's a genuinely useful result rather than a contradiction, since the two motors are wired and driven separately. Mark the working one as felt and the other as not, and treat it as a single failed motor rather than a wider fault.
Low battery is the most common and easiest explanation on wireless controllers, so try again on a fresh charge before assuming a motor is degrading. If it stays weak right after a full charge, run the intensity sweep and compare how low you can go before you stop feeling anything, and keep that number for future comparison.
Confirm your controller actually has motors built into the triggers; many controllers don't, and that's expected, not a fault. If you know yours does, the browser you're using most likely doesn't expose that specific effect yet.
If a result here doesn't match what you're feeling, or you'd like a second opinion before deciding whether a motor needs replacing, send over a description of what you tried and what you felt or didn't feel. We'll help you work out whether it's a setup issue or a hardware one.
info.gpadviewer@gmail.comSign in to your account