Skip to main content
TestingPhone
Menu

Audio

Browser-based

Phone Speaker and Audio Test

Play an original voice sample, a controlled tone sweep, and a repeating sound to listen for clear playback, rattling, or distortion.

What this result means
  • Browser observedThe page records a signal or capability the browser received.
  • You confirmedYou decide whether the physical response looks, sounds, or works as expected.
  • Browser cannot verifyComplete hardware health, hidden or intermittent faults, or manufacturer certification.

Start with your phone volume low. Keep the speakers away from your ears.

Raise the phone's media volume gradually. If no sound plays, check whether Silent Mode, Do Not Disturb, Bluetooth, AirPlay, headphones, casting, or another audio route may be affecting playback.

Sound stopped

1. Voice clarity

Listen to a spoken check

Listen for understandable speech without buzzing, crackling, or distortion.

How did the voice sound?

2. Tone sweep

Listen across a range of tones

Listen for buzzing, crackling, rattling, distortion, or missing audio. Changes in loudness across the sweep can be normal. This is a listening inspection, not a calibrated frequency-response measurement.

How did the sweep sound?

3. Physical volume buttons

Check several comfortable volume levels

Use the phone's physical volume buttons while replaying the voice or sweep. The browser cannot read or control the hardware volume. You do not need to use 100% volume.

Keep the phone away from your ear while testing at higher volume.

4. Physical cover inspection

Notice whether covered areas affect playback

Start the repeating sound, then cover each area gently. Do not press objects into an opening.

A. Cover the bottom speaker openings gently. Did the sound noticeably change?
B. Cover the top / earpiece speaker area gently. Did the sound noticeably change?

A change in sound can indicate that the covered area contributes to current media playback. No change does not prove that a speaker is faulty or unused. Phones and browsers may route audio differently.

Save your listening result

Choose a voice and tone-sweep observation first. The browser can start audio, but only you can report what the physical output sounded like.

Privacy: This test requests no microphone access, records nothing, and uploads no audio or listening data. Only your selected observations are stored locally.

Limitations: Bluetooth, headphones, AirPlay, or another route may receive the sound. This functional listening test cannot identify a defective physical speaker or measure calibrated loudness, frequency response, or distortion percentage.

Interactive helper

What did the speaker sound like?

Choose one symptom. Nothing plays automatically, and this helper never turns a listening result into a hardware diagnosis.

No sound played

Raise media volume gradually and disconnect Bluetooth, headphones, AirPlay, USB audio, or casting before repeating.

Repeat speaker test
Buzzing, crackling, or rattling

Compare the voice sample and tone sweep at moderate volume. A repeatable sound matters more than one noisy moment.

Open speaker guide
Muffled after fresh water

A short tone may help droplets near the grille, but it cannot dry the phone or verify internal liquid is gone.

Open Water Eject

Test guidance

How to interpret a phone speaker test

Browse all testing guides →
01

No sound at all

Confirm the media volume is raised and disconnect Bluetooth, USB, or other external audio routes. Browser playback alone cannot identify which physical speaker or audio path is responsible.

02

Rattling or distortion

Start at low volume and increase it gradually. Repeat more than one sample; distortion that returns at the same volume is more useful evidence than a single noisy moment.

03

One speaker seems quiet

Phone models route calls, media, and stereo channels differently. Compare normal calls and media playback, and do not insert tools into a speaker opening during inspection.

A browser test is one part of a phone inspection. Repeat an unexpected result and combine it with ordinary real-world use before deciding that hardware needs repair.