Most of the time a phone that won't vibrate has a setting turned off, not a broken motor: silent mode, Do Not Disturb, or vibration switched off in sound settings. On Android you can check the motor directly with our vibration test, which buzzes it in four patterns. On an iPhone you can't do that from any web page, but Settings can. Here's how to tell a setting from a hardware fault.
Each button sends a fixed on-off pattern in milliseconds. Here's what you should feel:
| Button | Pattern sent (ms, on/off) | Buzzes | Motor on | Pauses | Total |
|---|---|---|---|---|---|
| Short buzz | 100 | 1 | 100 ms | 0 ms | 100 ms |
| Long buzz | 500 | 1 | 500 ms | 0 ms | 500 ms |
| Pulse pattern | 100, 100, 100, 100, 100 | 3 | 300 ms | 200 ms | 500 ms |
| Ramp | 50, 150, 100, 150, 200, 150, 400 | 4 | 750 ms | 450 ms | 1,200 ms |
If you feel all four, with clear gaps in the pulse and ramp, the motor works. If the long buzz works and the short one doesn't, the motor may be slow to start, which can point to wear.
One thing a web page can't do is set the strength. The browser only switches the motor on and off for set times. The ramp feels stronger as it goes because each pulse runs longer, not because the page turned the power up.
Because some browsers accept the request and then do nothing. MDN's compatibility data says Firefox for Android disabled vibration from version 79: the call "returns true, but no vibration takes place (regardless of hardware support)". Desktop Chrome does the same for a different reason. The method exists, but a laptop has no motor to drive. The W3C spec allows this: when a device can't vibrate, the call still reports success.
| Browser | Can a web page vibrate the phone? | What our test shows |
|---|---|---|
| Chrome for Android | Yes (since version 32; needs a tap first) | Supported |
| Samsung Internet, Edge, Opera on Android | Yes, same engine as Chrome | Supported |
| Firefox for Android | No. The call is accepted but vibration is switched off | Supported, but nothing happens |
| Safari on iPhone and iPad (and every iOS browser) | No, never supported | Not supported |
| Chrome or Edge on a computer | The call works, but there's no motor | Supported, but nothing happens |
| Firefox on a computer | No, removed in version 129 | Not supported |
So before you blame the hardware, make sure you're in Chrome or Samsung Internet on Android. That's the only combination where "nothing happened" really tells you something.
Work down this list. Most fixes take seconds:
| What happens | Likely cause | What to try |
|---|---|---|
| Nothing on any button, in Firefox | Firefox for Android has vibration turned off | Open the test in Chrome or Samsung Internet |
| Nothing in Chrome, but the phone buzzes for calls | Silent mode, Do Not Disturb, or touch vibration turned off | Turn off Do Not Disturb, search Settings for "vibration" and switch it on, retest |
| Nothing in Chrome, and no buzz for calls either | Vibration off everywhere, or a failed motor | Check the settings; if they're on, restart and test again |
| Short buzz is missing, Long buzz works | Possibly a worn motor that's slow to start | Compare with another phone; plan a repair |
| Buzz rattles or buzzes against something | Loose case, loose part, or something in the case | Take the case off and test again |
MDN warns that some devices may not vibrate in silent or Do Not Disturb mode, so turn both off before you test. Settings menus differ between makers and Android versions, so the quickest way to the switch is to search Settings for "vibration" or "haptics".
Keep the test page on screen while it runs. The spec tells browsers to refuse vibration from a page that isn't visible, and to stop a pattern if you switch away. The page also has to have been tapped first. Chrome has required that since version 60, which is why nothing buzzes until you press a button.
Not from a website. Safari has never supported the Vibration API, and nearly every iPhone browser runs on Safari's engine, so the vibration test shows "not supported" on iOS. WebKit, the team behind that engine, has published a position against the spec.
Use Settings instead. Apple's iPhone User Guide gives the path: open Settings, tap Sounds & Haptics, tap Ringtone (or a sound such as Text Tone), then tap Haptics and choose a pattern. Create New Vibration lets you tap out a pattern of your own, which is a handy way to feel short and long buzzes one after another.
If nothing buzzes there, restart the phone and try again. A phone that won't buzz for calls after a restart, with every setting on, needs a repair.
A software problem usually affects everything at once and goes away with a restart or a settings change. A motor problem tends to show up as a weak buzz, a buzz that starts late, or a rattle. It often follows a drop or water exposure, and it doesn't change when you change settings.
A good test is to compare. If a friend's phone gives a crisp short buzz on the same test and yours gives a mushy one or none, and both are in Chrome with the same settings, the motor is the likely cause.
While you're checking the phone, the touch screen test finds dead zones in the display, and the battery test shows live charge and drain. Our battery health guide explains how to read wear figures.
On Android, open the vibration test in Chrome or Samsung Internet and tap Short buzz, Long buzz, Pulse and Ramp while holding the phone. On an iPhone, go to Settings, Sounds & Haptics, pick a sound, then Haptics, and choose a pattern.
Firefox for Android turned vibration off from version 79. The browser still reports success, but no vibration takes place. Use Chrome or Samsung Internet instead.
No. Safari has never supported the Vibration API, and nearly all iPhone browsers use Safari's engine. Test haptics from the Sounds & Haptics menu in Settings instead.
Check silent mode and Do Not Disturb first, then search Settings for "vibration" to make sure it's switched on for calls. If every setting is on and nothing buzzes after a restart, the motor may need replacing.
No. The Vibration API only sets how long the motor runs and pauses, in milliseconds. Longer pulses can feel stronger, but the strength itself is set by the phone.