Android Mic Test: Free Online Microphone Test in Chrome
Overview
Android Mic Test. Run the Android Mic Test to confirm your phone's built-in microphone is actually picking up your voice — tap Enable Microphone, then read the live level meter, spectrum, and dominant frequency and peak level readouts as you speak. If Chrome hears you but another app doesn't, the Android-specific troubleshooting below explains the difference between Chrome's site permission and your phone's OS-level app permission. The microphone test tool gives you a clear answer instead of guessing.
Your phone can seem perfect to you and muffled to everyone else, and the only way to know is to measure it. This Android mic test runs in Chrome on any Android smartphone or tablet with no app and no registration, and in a few seconds it shows you a live waveform, your speaking level and a clear pass or fail result for the mic you are holding.
How This Android Mic Test Works in Your Browser
A browser microphone test uses the same Web Audio API that Google Meet and Zoom use in Chrome, so there is no software to install and no download to trust. That is the whole point of a free online Android mic test: no app from a store, no registration, just the browser you already have. Chrome calls getUserMedia(), Android hands over the digital stream from the mic, and the page measures it on the phone itself. The audio is processed locally and is never uploaded to a server, which keeps your privacy intact even when you test in public. Try the iphone mic test online for a quick, no-install way to check this yourself.
Allow Microphone Access When Chrome Asks
When you tap Start, Chrome shows a permission prompt at the top of the screen. Tap Allow. If you tapped Block by mistake, tap the lock icon in the address bar, open the site's permissions, set microphone access to Allow and tap the start button again to test my mic from scratch.
Speak and Watch the Real-Time Waveform
Talk at your normal call volume about 20 cm from the bottom of the phone. The visualizer draws an oscilloscope-style trace of the signal: talking makes tall, uneven bursts, a quiet room leaves a thin line. When you test your Android mic this way, the waveform reacts within a fraction of a second, so a dead input is obvious immediately.
Read the Pass/Fail Verdict
After a few seconds of talking the testing tool gives its verdict. A pass means your Android microphone delivered audio at a usable level. A fail usually means the stream stayed flat, which points to permissions, a muted input or a blocked port rather than a broken part.
Recording and Playback: Hear Yourself
- Record a 10-second clip, then use playback to hear exactly what a caller hears.
- Download the recording as MP3 for sharing or WAV for uncompressed detail.
- Live monitoring needs headphones, otherwise the speaker loops back into the mic and causes feedback.
- Keep the page in the foreground; if you lock the screen, Android pauses the audio stream.
What Each Microphone Reading Means
Every number on the screen comes from an AnalyserNode that samples the stream many times per second. Loudness is reported in decibels relative to the loudest value the system can store, and pitch is reported in hertz using an FFT. That makes this Android mic test a genuine microphone test online rather than a simple on/off check. The online midi check takes under a minute and needs nothing but your browser.
Volume Level and Peak Level in dBFS
The level reading converts the signal's amplitude (0 to 1) into decibels below full scale:
$$\text{Level (dB)} = 20 \times \log_{10}(\text{amplitude})$$
Worked example: you say a short sentence and the meter measures an average (RMS) amplitude of 0.0587 and a highest single sample of 0.389. The volume level is \(20 \times \log_{10}(0.0587) = -24.6\) dB and the peak level is \(20 \times \log_{10}(0.389) = -8.2\) dB. The 16.4 dB gap between them is normal for speech, and the peak still has 8.2 dB of headroom before it hits 0 dB. Halve the amplitude, for example by covering the port with a finger, and the average drops 6 dB to −30.6 dB.
| Average level (dBFS) | What it means | What to do |
|---|---|---|
| Below −55 dB | Silent, no usable sound | Check permission, mute and the port |
| −55 to −36 dB | Too quiet for a clear call | Move closer, clear the opening |
| −36 to −16 dB | Healthy speaking level | Nothing, this is the target |
| −16 to −6 dB | Hot, loud peaks | Back off a few centimetres |
| Peaks at 0 dB | Clipping, words sound distorted | Lower gain or increase distance |
Dominant Frequency and the VU Meter
Frequency analysis splits each block of audio into bins. At a 48,000 Hz stream and a 2,048-point FFT, each bin is 48,000 ÷ 2,048 = 23.4 Hz wide and one block lasts 42.7 ms. If the strongest bin is bin 7, the dominant frequency is 7 × 23.4 = 164.1 Hz, typical for an adult talking. The VU meter shows the same bins as coloured bars, so a lopsided display reveals a muffled or tinny mic at a glance.
Sample Rate, Latency and Audio Channels
The sample rate is usually 48,000 Hz on current phones; some older models report 44,100 Hz. Latency is the delay between speaking and the screen reacting, a few tens of milliseconds on most devices. Phones expose one or two audio channels and a 16-bit sample size. Android also applies echo cancellation, noise suppression and automatic gain control before Chrome sees the stream. If your Android phone lists several microphone inputs, pick each from the device selector and test them one by one.
Checking a Used Phone Before Paying: A Microphone Test in Practice
I'm meeting a seller in a café to buy a second-hand Motorola for €145, and the one thing I can't judge by eye is the bottom microphone. The question is simple, and the test on this page has to answer it before I hand over any money: is this mic healthy, or am I paying for a fix? The answer, after four minutes: healthy, but the seller's case was costing it 5.5 dB. Run the microphone echo test tool to see exactly what's working and what isn't.
I open this Android mic test in Chrome on the seller's phone, tap Allow, hold it 20 cm away and read the same sentence each time so the runs are comparable. The page reports amplitude, and I convert each one with \(20 \times \log_{10}(a)\):
| Run | Average amplitude | Average level | Peak |
|---|---|---|---|
| Case on | 0.0213 | −33.4 dB | −17.0 dB |
| Case off | 0.0402 | −27.9 dB | −12.7 dB |
| Case off, pause between sentences | 0.00331 | −49.6 dB | – |
| Bottom port covered (top mic only) | 0.0124 | −38.1 dB | – |
Both runs pass, but the case-on average sits only 2.6 dB above the tool's too-quiet line at −36 dB, while the case-off average lands in the middle of its healthy band. As an outside cross-check, case-off is 1.9 dB short of the −26 dB nominal telephone level used in ITU-T telephony testing (an amplitude of 0.0501); case-on is 7.4 dB short. Re-checking one figure by hand, 20 × log10(0.0402) gives −27.92, matching the screen.
The number I'd watch here isn't the level, though. Android's automatic gain control can boost a half-dead part until its level looks normal, but it boosts the room too. So I compare the talking level with the pause level: −27.9 against −49.6 is a 21.7 dB gap. A blocked or damaged capsule pushed up by gain usually shows a gap closer to 10 dB, because the floor rises with the level. If the gap had been small, no level reading would have convinced me.
The top mic reading 10.2 dB below the bottom one is expected, since it faces away from my mouth; the point is that it responds at all.
Decision: I pay the €145 and skip the seller's case, whose cutout sits a few millimetres off the port. If you repeat this, test with and without the case, and trust the gap before the level.
Bottom, Top and Rear: Where Each Phone Mic Sits
Most handsets carry multiple microphones, and each Android microphone has its own job. A test reads the input Android chooses, so it helps to know which phone mic you are actually measuring.
Bottom Microphone for Phone Calls
The main mic sits beside the charging port. It handles phone calls, voice notes and most app audio, so test it first. A tiny mic opening here is easy to block with pocket debris.
Top Microphone and Noise Cancellation
The upper mic listens to the room. The phone subtracts what it hears from the main mic, a form of beam-forming that cuts traffic and chatter for the person on the other end. To check it, cover the bottom port and run the test again: the level should drop but keep moving.
Rear Microphone for Video Recording
Many Android flagships add a microphone near the camera so video recording captures the scene in front of you rather than your fingers. If Android exposes it, pick it from the device selector and compare its level with the bottom one.
MEMS Capsules and the Android Audio Path
Each mic is a MEMS capsule a millimetre or two across. Its signal passes through an ADC, then the phone's DSP, then the audio HAL that decides which input to route, before Chrome receives it through the Web Audio API. The hardware's frequency response comfortably covers everything you say, so a weak reading is more often a blockage or setting than a worn part.
Microphone Permission Steps for Samsung, Pixel, OnePlus and Xiaomi
If Chrome never shows a prompt, the system has already denied it. On Android 12 and later you can check permissions in Settings, but each Android brand hides them in a slightly different place, and the browser can only ask for the microphone once the system allows it.
Samsung One UI: App Permissions and Voice Focus
On Samsung, open Settings, Apps, Chrome, App permissions and set the microphone permission to Allow only while using the app. One UI's sound effects can also hide a weak input, so switch off Dolby Atmos and Voice Focus while testing, and turn off the Bixby wake word so it cannot hold the mic.
Pixel and Stock Android: Privacy Dashboard
On a Pixel or Motorola, open Settings, Security and privacy, Privacy dashboard, Microphone to see which apps used it recently. Pause Google Assistant's Voice Match while you test so the hotword listener is not competing for the input.
Xiaomi MIUI and OnePlus OxygenOS
Xiaomi phones on MIUI keep a second permission layer in the Security app; grant Chrome the microphone there as well. Turn off Battery Saver, which can suspend audio in the browser. If MIUI still blocks it, try Chrome's desktop mode. OxygenOS follows the standard Android flow, so the usual Settings path is enough there.
Best Browser for a Mic Test on Android
Every modern browser on the operating system can reach the mic, but they don't all expose the same readings. Edge matches Chrome because both share the same engine, while Firefox reaches the microphone but reports fewer details.
| Browser | Mic input | Detailed readings | Verdict |
|---|---|---|---|
| Chrome for Android | Full | Full | Best choice |
| Edge | Full | Full | Good alternative |
| Samsung Internet | Full | Partial | Fine if Chrome is missing |
| Opera | Full | Partial | Usable |
| Brave | With Shields off | Full | Usable |
| Firefox | Full | Limited | Basic checks only |
For a clean run, open an Incognito tab so old permission blocks and extensions are out of the way. If readings freeze, update Android System WebView and Chrome from the Play Store.
Android Microphone Not Working? Troubleshooting Steps
Work through these in order and re-run the test after each step, so you see which change brought your Android mic back. A wired headset that is still connected, a mute toggle in a call app's settings or outdated audio drivers on an older custom ROM can all reroute or silence the input.
No Signal or a Flat Waveform
- Reload the page and allow access again.
- Close another application that holds the mic, such as WhatsApp or the camera.
- Restart the phone if the input stays flat; a stuck routing lock clears on reboot.
Low Input Level and Background Noise
A low input level usually means the phone case covers the opening or lint and dust have packed into it. Clear the hole with a soft brush or a short burst of compressed air, never a pin. If the trace never settles, move away from fans and open windows; constant noise fills the quiet gaps between words.
Mic Works Here but Not in WhatsApp or Zoom
If the browser test passes, the mic is fine and the app is the problem. Open Settings, find WhatsApp or the call app, check its own permissions entry, clear its cache and update it. Teams and Google Meet video calls can also select a Bluetooth input you forgot was paired.
Water Damage and Hardware Failure
After water damage, let the phone dry for at least a day before testing. If the level stays below the silent band after 48 hours on every input, treat it as hardware failure and book a repair.
Tips to Improve Audio Quality from Your Built-In Mic
- Hold the Android phone 15 to 25 cm away and speak across the microphone opening, not into it, to avoid plosive pops; a foam cover works like a pop screen.
- Remove a bulky case before an important call and compare the sound quality.
- A Bluetooth headset compresses speech for calls; the built-in mic or wired earphones often sound clearer.
- For podcasts, a USB microphone through a USB-C adapter beats the microphone inside any Android phone, and the same test reads a USB input, so you can compare the two.
- Re-run the test after every system update, because updates can reset permissions.
Why Test Your Microphone Before Calls and Recordings
A quick mic test saves a failed interview, an inaudible podcast take or a streaming session nobody can hear. This online mic test is the fastest way to check microphone online before video conferencing or sending voice notes, and it doubles as an Android microphone test after a repair. Because it is a free online Android mic test with no app to download, you can run it in the browser on a borrowed phone or tablet just as easily as on your own Android microphone. If you want to test microphone performance against a second phone, run the same microphone check on both and compare the readings.
Frequently Asked Questions
- Do I need to install an app to test my Android microphone?
- No. The test runs in Chrome on your phone or tablet. Tap Start, allow microphone access when Chrome asks, and speak for a few seconds. Nothing is installed and you don't need an account.
- Which browser should I use on Android?
- Chrome gives the most complete readings, and Edge is a close second. Samsung Internet and Opera work but may show fewer details. Firefox reaches the mic but reports less, and some manufacturer browsers block microphone access entirely.
- Why does Chrome ask for microphone permission?
- Every website that uses your microphone needs your consent first, the same as Google Meet or Zoom in the browser. You can withdraw it at any time from the lock icon in the address bar.
- Is my audio recorded or uploaded during the test?
- No. The audio is analysed inside the browser on your phone. Nothing is sent to a server, and the stream stops when you stop the test or close the tab.
- My phone has several microphones. Which one is tested?
- Chrome uses the input Android chooses by default, usually the bottom microphone. If your phone lists more inputs, pick each one from the device selector and run the test again.
- The test passes but people can't hear me on WhatsApp. Why?
- If the browser test passes, the microphone works. Check that WhatsApp has its own microphone permission, clear its cache, update the app and restart the phone. Also ask the other person to check their speaker.
- Why is my result Weak or Fail?
- The level stayed too low for too long. Check the permission, remove a case that covers the mic hole, clean lint out of the opening, close other apps that use the mic and speak closer to the bottom edge of the phone.