Android mirroring has video but no sound: check capture, transport and playback

An audio-enabled message is not proof of audible playback. Check browser restrictions, Android capture conditions and the remote audio path separately.

If mirroring has a picture but no sound, do not start by reconnecting repeatedly. Working video validates the video path. For sound, check whether the phone produces capturable audio, whether the receiver gets it, and whether the browser actually plays it. An “audio enabled” message is not evidence for all three.

This general guide draws on documentation checked on September 15, 2026. It is not a new hands-on test of a mirroring product, and it does not assume all tools use the same Android capture method.

Run a small comparison before changing everything

Use a short piece of media you are entitled to play and know contains sound. Test one device at a time.

  1. Confirm playback on the phone. Avoid calls, voice chat and uncertain source material for the first comparison.
  2. Play known-good audio locally on the computer. Check the output device, system volume and whether the browser tab is muted.
  3. Return to the mirroring page and click its audio or play control. Record whether that changes the result.
  4. If only one app is silent, compare it with another player that permits capture. Do not change the network, browser and phone at the same time.

These are diagnostic suggestions, not guaranteed fixes. “Only one app is silent” is substantially more useful to support than “mirroring has no sound.”

The browser may still be waiting to start playback

In Chrome, a Web Audio page may have an AudioContext in the suspended state. Chrome documents that a context created before user interaction may need resuming after interaction. Developers should check that state rather than merely change a button label. Chrome autoplay documentation

For media elements, play() returns a Promise. Playback restrictions can produce NotAllowedError; an unsupported media source can produce NotSupportedError. These point to different investigations. A server acknowledging an enable request does not establish that browser playback started. MDN play() reference

Try the page's explicit playback control first. If it fails, retain the error name rather than disabling browser security. Even a running player still warrants checking which speaker or headset receives the computer's output.

A recent Android version is not permission to capture every app

For ordinary apps using standard AudioPlaybackCapture, Android specifies conditions including user approval and a shared user profile. Audio usage and capture policy also matter. Platform support therefore does not mean every source app permits capture. Android capture requirements

Do not generalize those rules to every system component, debugging service or customized ROM. Ask which implementation the tool uses before applying a restriction to it; do not modify another app to bypass its capture policy.

Collect audio-specific evidence for remote sessions

If the software already offers local and remote access, compare the same phone and media through both. Remote-only silence makes the remote audio path worth investigating first, but does not prove a server or port fault.

Developers can record three checkpoints:

Stage Useful evidence
Capture Startup result, selected source, errors and whether non-silent samples exist
Transport and decoding Audio-specific packets or bytes, plus decoding results—not aggregate traffic
Playback Promise result or AudioContext state, mute settings and actual output device

Growing audio traffic can still contain silence. It does not automatically implicate the speakers. Share timestamps, versions and error names without private recordings, access tokens or connection addresses.

If audio and video are both delayed rather than silent, read why network RTT differs from perceived mirroring latency. That is a separate investigation; lowering video FPS is not a universal remedy for missing sound.

参考来源