Calls Are Quiet but Media Works: Compare Earpiece, Speakerphone and Headset

Call audio and media playback can use different paths, so a browser speaker test is only one part of the picture.

Name the failing path

Note whether you cannot hear the other person or they cannot hear you. Those are different directions of audio. Then note whether the issue occurs on normal calls, speakerphone, a headset, or one internet-calling app. This short description prevents a microphone problem from being treated as a speaker-cleaning problem.

Use browser tools for a limited comparison

Sound Check can confirm ordinary browser playback through your current output. Microphone Test can confirm the input the browser selected. Neither tool can force access to a dedicated call earpiece or certify the voice-call path. Do not treat a passing browser test as proof that every call component works.

Compare ordinary usage

If practical, compare another call or app using the same setup, then an alternate output at a comfortable level. If only one calling app has trouble, check its input/output and permission settings. Google’s microphone troubleshooting guidance distinguishes recording checks from call behavior and includes Bluetooth checks. Use the corresponding guide for your device.

Escalate with the right observations

Tell support which direction fails, which output you used, and whether media and local recording work. Avoid publishing a recording of someone else’s call. Persistent problems after ordinary settings checks belong with your carrier, app support, or device manufacturer depending on which path fails. Repeated water-eject cycles are not a general solution to call quality.

Official reference

Google: when others cannot hear you

TNAPK editorial note: This guide combines official support information with practical comparison steps. It is not a device inspection or a guarantee of repair. Settings and model-specific care instructions can change.