Many phone browsers and desktop environments do not provide usable vibration. This page checks the actual method, not the user-agent name. Keep security settings enabled; do not change flags to force a success. No audio or screen flash is substituted for a motor pulse.
Phone Vibration Test: Request One Short Pulse
Request one short pulse from your phone's body and record what you felt separately from the browser reply. Limited browser support: a reply does not certify the motor.
Also known as: vibration test, phone vibrator, phone vibration, vibrating phone. Free, online, and no download required.
No permission neededNothing uploaded
Press Test one short pulse for a single 200ms request. Nothing vibrates automatically; unsupported devices receive no sound or flashing substitute.
01
What the phone Vibration Test: Request One Short Pulse checks
| Check | How it is measured | Fails when |
|---|---|---|
| Browser request | Whether navigator.vibrate exists and whether the deliberate 200ms request returns true, false or throws an exception. | An unsupported method, a false return and an exception are distinct browser outcomes. None diagnoses the phone's vibration motor. |
| Physical observation | Only the observation you select: felt vibration, felt nothing or not checked. Its default remains not checked even when the API returns true. | You might not feel a short pulse because of browser support, the device, system settings or how you hold it. Felt nothing does not mean damaged hardware. |
| Cancellation | The separate API reply when Stop, Reset, Finish, tab hiding or leaving asks navigator.vibrate(0) to cancel a pending request. | False or an exception means the cancellation request did not return an accepted reply. The page removes its own timer but cannot certify a physical stop. |
How to run the phone Vibration Test: Request One Short Pulse
- Hold the device you intend to check, keep this page in the foreground, and press Test one short pulse. The button makes one 200ms navigator.vibrate request, not a sequence or a continuous vibration.
- Read Browser request result, then choose Felt vibration, Felt nothing or Not checked under Your observation. The browser's boolean reply is not the same thing as a physical sensation and never fills your observation automatically.
- Use Stop, Finish or Reset to request cancellation and clear the observation. Check the separate cancellation reply; false or an exception cannot establish a successful stop. Returning from another tab does not start a new pulse.
If something failed
True is the browser's request return, not a sensor reading. Check your own observation separately. Silent mode, DND, system settings or missing hardware may affect the sensation. This page neither inspects nor changes those settings and cannot identify the cause of a missing sensation.
Read the separate cancellation result. The original request is only 200ms and normally ends on its own, but this page does not assert that a motor stopped merely because its JavaScript timeout was removed. It does not retry automatically or build a queue of replacement pulses.
02
How to read the result
Browser reply and hand-held observation
The two columns answer different questions. The browser reports whether it accepted an API request. You report whether you felt the device move. Keeping those separate prevents a successful function call on a desktop from being presented as evidence that a phone motor works.
| API result | Your observation | What it establishes |
|---|---|---|
| true | Not checked | Request accepted; physical outcome remains unknown. |
| true | Felt nothing | Request accepted; you did not feel a pulse. No hardware-fault diagnosis. |
| true | Felt vibration | Request accepted and you reported a sensation for this attempt only. |
| false or Exception | Not checked | The request was not accepted or threw; do not manufacture a motor verdict. |
| Unsupported | Not checked | This browser cannot expose the requested function; a different browser or device is not assumed to work. |
One pulse rather than a repeating phone vibrator
This is a bounded check, not a continuous phone vibrator, alarm or intensity controller. A vibrating phone may be useful evidence for one attempt, but the tool does not measure acceleration, strength or frequency. The only positive-duration request used here is 200ms.
- During the short activity window the button is disabled, so rapid presses cannot queue later requests.
- One local timeout releases that button lock. The timeout does not call the vibration API or start another pulse.
- Stop, Finish, Reset, hiding the tab and leaving all clear that timeout and request duration zero. Nothing restarts when the page becomes visible again.
Repeat only when you choose to
If you want another phone vibration attempt, wait for the button to become available and click it yourself. A new request resets the observation to not checked so an earlier felt vibration cannot be silently carried into a later test. Keep the same device and browser if you compare attempts.
- Record a missing sensation honestly instead of picking Felt vibration because the API returned true.
- Consult your device's documented vibration behavior when a system feature is the original problem. A browser sample cannot certify that feature.
- For a connected game controller use the separate controller vibration test. Gamepad dual-motor output is not phone-body vibration.
Measurement limits
A web page cannot inspect the physical motor or certify its health through navigator.vibrate. Device and browser support vary, and a browser can return without causing a useful physical effect. This test does not classify your operating system from a user-agent string or infer installed hardware.
- No health percentage, Motor passed label, strength slider or weak/strong gamepad channel is assigned to a phone.
- The observation and replies stay in this page's current memory. They are not uploaded, saved to browser history storage or included in analytics.
- The API contract follows MDN Navigator.vibrate documentation, reviewed October 14, 2026: user activation matters, the call returns a boolean, and zero requests cancellation. Return to all tools for other checks; none substitutes for an unobserved motor response.
03
Phone Vibration Test: Request One Short Pulse questions
Does true mean my phone motor passed?
No. True is an accepted browser request, not a motor measurement. Keep Your observation at Not checked until you actually checked the sensation. Even Felt vibration records only your report for this attempt, not overall health, strength or reliability.
Can this phone vibration test work on iOS or a desktop?
It tests the actual exposed function rather than assuming support from the platform name. Many environments cannot provide useful vibration. An API available on a desktop does not establish that desktop hardware includes a motor; cross-platform physical support remains unverified.
Why might a short pulse be accepted without a sensation?
The browser return does not observe movement. Browser support, missing device hardware and system settings can affect the effect. Silent mode or DND may matter on a particular device, but this page does not inspect those settings or tell you a failed motor is the cause.
Will repeated clicks keep my phone vibrating?
No pulse sequence or automatic restart exists here. The active button lock prevents queued requests during the 200ms window, and a new request needs another deliberate click afterward. The tool offers no duration pattern, continuous mode or intensity control.
What does the phone cancellation result mean?
It is the return of the separate navigator.vibrate(0) call. False or an exception stays visible instead of becoming Stopped successfully. Finish, Reset and background cleanup also clear local state and the unlock timeout; that JavaScript cleanup is not a sensor confirmation of physical stopping.