Vibration Test: Check Your Phone's Vibration Motor Properly

Vibration is easy to ignore until it stops working. Then missed calls, silent alarms and unnoticed notifications reveal how much daily life depends on a tiny motor spinning an off-centre weight inside the phone. Vibration faults are also easy to misdiagnose, because the same symptom — "my phone doesn't vibrate" — can come from a setting, a mode, a software bug, or a genuinely failed motor. A systematic vibration test separates those causes in minutes, so you fix a setting when the problem is a setting, and seek repair only when the problem is hardware.

The Vibration Test is a browser-based test: it triggers vibration patterns on your own device through the browser, letting you feel whether the motor runs, how strong it feels, and whether patterns play consistently. It runs on your device, installs nothing, and needs no account. Because it is a device test, the results describe the phone in your hand right now, not a server or a website. For the test to work, the browser must support vibration, which most mobile browsers do, and the device must not be in a state that suppresses vibration, which is exactly what the preparation steps below check first.

Before testing, rule out the simple causes. Check that vibration is enabled in system settings, that the phone is not in a do-not-disturb or silent mode that suppresses it, and that the specific app or alert type you care about — calls, messages, alarms — has vibration enabled individually, because many phones control these separately. Remove any thick case that might muffle the motor, and test on a hard surface where vibration is easy to feel, as well as in your hand, because a soft surface can mask a weak motor. Note recent history too: a drop, water exposure, or a repair can all affect the motor, and that history matters when interpreting results.

Testing patterns, strength and consistency

Start with a simple pattern: a single short buzz. Confirm that it happens at all, and note its strength: strong and clear, faint but present, or barely perceptible. Then test a longer buzz, and a repeating pattern such as three short buzzes with pauses. Patterns matter because some faults affect only certain durations: a motor that manages short buzzes but fails on long ones may be weakening, while a motor that buzzes continuously without stopping points at a control or software problem rather than a motor failure. Repeat each pattern several times, because an intermittent fault — working three times, failing the fourth — is a different diagnosis from a total failure, and it is the pattern most often missed by a single quick test.

Strength deserves a comparison, not just an impression. If you have access to the same or a similar phone model, compare the two side by side on the same surface; a motor that is dramatically weaker than its twin is failing even if it still vibrates. Without a twin, compare with your memory of the phone when new, and with how vibration feels in different positions: a motor that feels normal in the hand but silent on a table, or vice versa, may be loose rather than dead, and looseness can worsen with drops. Also test while the phone is charging and while it is not, because charging-related electrical issues occasionally affect vibration, and a fault that appears only while charging points at the charger or port rather than the motor.

Listen as well as feel. A healthy motor produces a smooth, even buzz. A rattling, grinding or buzzing sound that changes pitch suggests a loose motor, a damaged weight, or debris inside the phone, and it is worth noting even if vibration still works, because mechanical damage tends to worsen. A motor that clicks without vibrating, or that starts and stops erratically, is also signalling a mechanical or connection problem. Record these observations in plain words — "rattles on long buzzes, smooth on short ones" — because a repairer can use that description to diagnose faster than a vague "vibration broken".

Worked example: a phone that stopped buzzing for calls

Suppose a phone owner notices missed calls: the phone rings visually but never vibrates, so calls in a pocket go unnoticed. She checks settings first and finds vibration enabled for calls, and do-not-disturb off. She runs the vibration test: short buzzes work, long buzzes feel weak and rattly, and repeating patterns sometimes skip a buzz. The pattern points away from settings — settings would block all vibration equally — and towards a weakening or loose motor. She tests without the case and on a hard table, with the same result, and notes that the phone was dropped a month earlier, after which vibration felt slightly different but was never tested.

Her next step is a repair assessment, not a settings hunt. She backs up the phone, checks warranty status, and takes the test observations to a repairer: short buzzes present, long buzzes weak and rattly, intermittent skips on patterns, fault unchanged without the case. The repairer confirms a loose motor mount from the drop and fixes it, after which a repeat test shows strong, consistent patterns. The total cost was a repair that was genuinely needed, and the test prevented two wrong turns: resetting the phone for a hardware problem, which would have wasted time and risked data, and ignoring the problem until an important call was missed.

Contrast that with a settings case: had the test shown no vibration at all while a settings check revealed vibration disabled for calls specifically, the fix would have been a single toggle, and the test would have confirmed the fix immediately afterwards. The test's value lies in making that distinction quickly, before either a needless reset or a needless repair.

When to repair, reset or replace

A motor fault that survives settings checks, restarts and software updates is a hardware problem, and software resets will not fix it. Before a repair, back up the phone, check warranty, and compare the repair quote with the phone's value, because motor replacement on some models is cheap while on others it requires significant disassembly. A phone under warranty should go to the manufacturer or seller with the test observations as evidence. After any repair, re-run the test before leaving the shop: a repaired motor should produce strong, consistent patterns, and checking on the spot avoids a second visit.

Software causes deserve one careful attempt before repair: restart the phone, check for system updates, and test again. If a recent update coincided with the fault, check whether other users report the same issue, because a software regression sometimes affects many devices at once and is fixed by a later update. Only consider a factory reset as a last resort, after a full backup, and only when the evidence points at software rather than hardware — for example, when vibration fails across all patterns but the motor previously worked and there is no drop or damage history. A reset for a rattling, intermittent motor wastes time and risks data for a problem it cannot solve.

For related device checks, the Multi-Touch Test covers screen touch input, and the A2Z Device Health Check gives a broader device overview. For an overall device-checking method, see A2Z Device Health Check Guide.

FAQs

Why does vibration work for alarms but not for calls? Because many phones control vibration separately per alert type and per mode. Check call vibration, message vibration and alarm vibration individually, and check do-not-disturb rules, before concluding the motor is faulty.

Can a browser test damage the motor? No. The test triggers the same vibration the phone produces for ordinary notifications, in short patterns. It does not overdrive the motor, and stopping the test stops the vibration.

Does a weak vibration always mean repair? Not always. A thick case, a soft surface, a low vibration-intensity setting, or a battery-saving mode can all weaken perceived vibration. Rule those out, compare patterns, and only then treat weakness as a hardware fault.