Vibration API
Last pattern: —
📱 Hold the phone in your hand when you tap. If nothing moves on any pattern but the chip above says "supported", the vibration motor may be worn or disconnected.
Check your phone's vibration motor — buzz, patterns and ramp
This page uses the browser's navigator.vibrate() API, which lets a web page drive the phone's vibration motor directly — no app install needed. The four tests cover the patterns you'd notice in daily use: a short notification buzz, a long incoming-call buzz, a pulse pattern (the API alternates vibrate/pause durations in a single array), and a ramp that escalates from 50 ms to 400 ms so you can feel whether the motor is weaker at low intensities than at high ones — an early sign of a worn eccentric-rotor motor.
Because each button shows a bar preview of its pattern, you can compare what you feel against what the browser sent. A pattern that feels cut short, jittery, or missing pauses usually means the motor's counterweight is sticking, not that the software misfired.
Why doesn't it work on iPhone? Apple has never implemented the Vibration API in iOS Safari — it's the one major platform without support. iPhone users can verify haptics instead via Settings → Sounds & Haptics, or with a dedicated app from the App Store.
It says "supported" but nothing vibrates. Check that vibration isn't muted system-wide (silent mode on some Android skins, or a "vibrate on touch" accessibility setting), then retest with the screen unlocked and the page in the foreground — Android suspends vibration from background tabs. If every pattern is silent while the phone is set to vibrate, the motor itself is the likely fault and a repair is needed.