a browser vibration request is unavailable or produces no felt vibration
This symptom concerns the system path. Start with a neutral DeviceOK test where available so the next step is based on evidence rather than a generic reset sequence.
Do not jump to the most invasive fix
Avoid destructive resets, unofficial driver packages, firmware flashing, or replacing hardware before the simpler detection, permission, connection and configuration checks are exhausted.
Retest the same condition
After every meaningful change, repeat the same test under the same conditions and compare the result.
Rule out the simple causes
- 1
Run DeviceOK Vibration Test on the phone itself.
- 2
Make sure the device is not in a mode that suppresses haptics/vibration.
- 3
Check whether the browser supports the Vibration API at all.
Work through the problem in order
- 1
If the browser accepts the request but you feel nothing, compare a native system vibration/haptic action.
- 2
If native haptics work but browser vibration does not, treat it as browser/platform support rather than hardware failure.
- 3
Do not use this browser test as proof that a vibration motor is physically defective.
If the matching DeviceOK test succeeds, prioritize the affected app, browser policy, operating-system setting, or configuration before assuming complete hardware failure.
If the same capability also fails in DeviceOK and another trusted diagnostic path, broaden the investigation to connection, operating-system/device state, official driver or firmware support, and finally hardware.