Microphone Not Working on Android

Microphone Not Working on Android: Chrome Permission Fix Guide

On Android, microphone access is governed by both OS-level permissions and app-level permissions, with Chrome adding its own permission layer for browser-based audio access. Chrome on Android uses getUserMedia to request microphone access, which requires both the Chrome browser app to have microphone permission in Android settings and the specific website to be granted permission within Chrome. Both layers must be correct for browser-based audio tools to work.¹

Browser-based microphone testing on Android uses the same getUserMedia path that Google Meet, WhatsApp web, and other web-based voice applications use. If the Noise Floor Grade works in Chrome on Android here, the microphone is accessible to all Chrome-based web applications. If it fails, the permission issue affects all browser-based voice access, not just this tool.

Check the hardware first

Open Chrome on Android and navigate to this tool. Grant microphone permission when prompted. Run the Noise Floor Grade. If the test returns a grade, even if the number is poor, the microphone hardware, Android OS permission, and Chrome permission are all correctly configured. A successful test result proves that the signal path from the Android microphone capsule through the OS audio stack to the Chrome browser is fully functional, which means any web-based voice application on the same device should also be able to access the microphone.

Two independent permission layers block access

If the test fails with a permission error, the issue is in Chrome or Android permission settings. Android requires two independent permissions for browser-based microphone access: the Chrome app must have microphone permission at the OS level, and the specific website must have microphone permission within Chrome's site settings. Both must be granted for the Noise Floor Grade to work. If either layer is denied, the browser cannot access the microphone, and neither can any web application running in that browser.¹

What the test results mean

Noise Floor Grade returns any result: microphone access is working in Chrome, which means the Android OS permission and Chrome app permission are both correctly configured. The problem with your specific application may be in that app's own permission or configuration, since each Android app manages its own microphone permission independently.

Noise Floor Grade shows "Permission denied": go to Android Settings > Apps > Chrome > Permissions > Microphone > Allow, and check the per-site permission for the specific website. If Chrome has permission but specific sites do not, go to Chrome Site Settings (Chrome menu > Settings > Site settings > Microphone) and check the blocked list.

Platform-specific fix path

Stock Android: Settings > Privacy > Permission manager > Microphone > Chrome. Ensure it shows "Allow only while using the app." Samsung One UI: Settings > Privacy > Permission manager > Microphone > Chrome. MIUI (Xiaomi): Settings > Apps > Chrome > App permissions > Microphone > Allow. For specific websites in Chrome: tap the site info icon in the Chrome address bar > Microphone > set to Allow. Some Android OEMs add an additional OS-level microphone access layer in their privacy settings. These manufacturer-specific layers operate below the standard Android permission model and can block microphone access even when Chrome and individual websites appear to have all necessary permissions granted at the standard Android level.

Unlike a standard Android permission denial that shows an explicit error message, manufacturer privacy layers often block microphone access silently by returning an empty audio stream rather than throwing a permission error. This means the Noise Floor Grade may return a result that looks valid but actually represents digital silence rather than real room noise, making it appear as though the microphone is working when in fact no audio data is reaching the browser at all.²

Manufacturer permission layers on custom Android builds

Beyond the standard Android permission model, several major Android manufacturers add additional privacy controls that intercept microphone access before Chrome's own permission layer. These manufacturer overlays are separate from Android's standard Privacy Manager and can block microphone access even when both Chrome and individual websites appear to have permission granted. If the Noise Floor Grade fails in Chrome despite all standard permissions appearing correct, a manufacturer-specific permission layer may be the cause.³

HarmonyOS and Xiaomi MIUI additional permission layers

On Xiaomi MIUI devices, navigate to Settings > Apps > Chrome > App permissions > Microphone, but also check Security > Privacy protection > Permission management, which maintains a separate microphone access list. On Huawei devices running HarmonyOS, check Settings > Privacy > Permission manager > Microphone > Chrome, distinct from the standard Android path. Samsung One UI adds a Camera and Microphone Usage indicator in the status bar; if it shows blocked, check Settings > Privacy > Permission manager. After granting access through all applicable layers, reload this page and retry the Noise Floor Grade.

Run the Noise Floor Grade again only after every applicable permission layer has been granted, because a partially-granted state can return a silent or empty stream that looks like success while delivering no real audio. If the retry still shows digital silence, the missing layer is almost certainly one of the manufacturer overlays rather than the standard Android permission, and the device-specific privacy menu is the place to look next.

Testing across browsers to isolate Chrome-specific issues

If the Noise Floor Grade works in Firefox on Android but fails in Chrome, the issue is Chrome-specific rather than at the Android OS level. Chrome and Firefox maintain independent permission states. A microphone permission granted in Firefox does not satisfy Chrome's permission requirement for the same site.⁴ Testing in both browsers establishes which layer is responsible. OS-level failures affect all browsers simultaneously; Chrome-level failures affect only Chrome.

Device management policy as a root cause

On Android devices enrolled in corporate mobile device management (MDM), a management policy can restrict microphone access for specific applications, including Chrome. This restriction applies silently: Chrome requests microphone permission and the OS appears to grant it, but the MDM policy intercepts the audio stream before it reaches the app. If your device is managed by an organization and microphone access fails in Chrome despite all standard permissions appearing correct, trace the Android mic permission layers and then contact IT support. The fix requires a policy change that only the domain administrator can apply.⁵

When to use this

Use this test when voice features fail in Chrome on Android, such as voice messaging, Google Meet web, or AI voice assistants, to distinguish hardware failure from permission configuration issues.

Examples

Noise Floor Grade fails with permission error — Chrome's microphone permission was reset by Android update

Re-granted microphone permission in Android App Settings for Chrome — voice calls restored

Noise Floor Grade in Chrome fails. Native camera app works — Chrome-level permission was blocked

Allowed microphone for Chrome in Android permissions — Chrome-based tools now work