Earbuds produce stereo audio while call microphone remains phone mic. A partial failure matters: one capability still functions, while a closely related step does not. This guide focuses on isolating that difference in audio devices, not on indiscriminate resets. Use the known-good behavior as your control, change one variable at a time, and retest the original scenario after each intervention.
Practical six-point diagnosis
- Reproduce: Earbuds produce stereo audio while call microphone remains phone mic.
- Compare: Compare voice recorder microphone selection and phone call route.
- Check: Bluetooth call profile not negotiated, without adjusting unrelated settings.
- Check separately: Call app ignores microphone route.
- Correct: Choose earbuds as call audio device and re-establish permitted hands-free profile.
- Verify: Voice on both ends uses intended microphone and sound output.
Baseline test: Compare voice recorder microphone selection and phone call route. Record the current device model, OS or firmware version, and whether this occurs with one file, account, network or source. A reproducible contrast is more informative than a vague message such as “not working.” If the control fails too, stop treating this as a feature-specific problem and investigate the shared dependency first.
Possible explanations
| Hypothesis | Evidence worth checking | Next decision |
|---|---|---|
| Bluetooth call profile not negotiated | Inspect the permission, account or entitlement attached to this feature, without changing any other user profiles. | If the control still works, focus on the affected path rather than resetting the whole device. |
| Call app ignores microphone route | Compare the selected input/output route with a known-working local sound and verify the supported audio profile. | If this condition is not present, leave the associated setting unchanged. |
| Earbud permission or firmware mismatch | Record the installed firmware or app version, then compare behavior before and after a supported update or clean reopen. | Only escalate to this branch if the simpler comparison did not explain the failure. |
Choose the appropriate route
Route A — Correct the observable mismatch
Choose earbuds as call audio device and re-establish permitted hands-free profile. Start only after capturing the baseline. When the recommended control is not present on your model, look for its supported equivalent in the product documentation rather than following screenshots from another version.
Return immediately to the failing task and check whether the outcome changed. If it did, preserve the working setting and avoid piling on additional changes. If it did not, undo the change where appropriate before moving to deeper checks.
Route B — Test the underlying dependency
Test cellular call and one messaging app to isolate application routing. This advanced comparison is worthwhile only if the simple check did not resolve the problem. The first two possibilities to separate are Bluetooth call profile not negotiated and call app ignores microphone route. Do not interpret their presence as proof of a diagnosis; a compatible device and a partially failed service may coexist.
Route C — Handle a limitation or persistent fault
A third explanation is earbud permission or firmware mismatch. Check whether the feature requires particular hardware, account privileges, region settings or source formats. When a feature is unsupported, there may be no legitimate settings-only fix; use the vendor-documented alternative rather than an unsafe workaround.
Protect your setup: Do not make emergency calls to test device routing. Start with modest volume. Confirm which device is both the actual audio source and output; a paired Bluetooth device may still use another output path.
Step-by-Step Troubleshooting
Follow the Beginner steps first. Advanced steps are for isolating hardware, application or network-specific causes after a safe baseline test.
Confirm the boundary
Earbuds produce stereo audio while call microphone remains phone mic. Do not assume this is a complete outage. Compare voice recorder microphone selection and phone call route. Keep the account and connections unchanged between attempts.
Capture a useful baseline
Write down the affected model, software version, active input and when this started. Compare voice recorder microphone selection and phone call route. A working comparison tells you which part of the chain is still healthy.
Use the least disruptive correction
Choose earbuds as call audio device and re-establish permitted hands-free profile. Apply one supported change at a time; stop if your model uses a different setting or does not advertise the feature.
Confirm the expected outcome
Voice on both ends uses intended microphone and sound output. Try the original failing action again, not an unrelated easier test; retain the old setting until you know the change helped.
Test the first dependency
Investigate whether Bluetooth call profile not negotiated. Specifically, inspect the permission, account or entitlement attached to this feature, without changing any other user profiles. Compare the result with the working baseline from the beginner route.
Separate another possible cause
Assess whether call app ignores microphone route. For this branch, compare the selected input/output route with a known-working local sound and verify the supported audio profile. Do not change that configuration unless the evidence supports it.
Inspect the third branch
Test cellular call and one messaging app to isolate application routing. Also consider earbud permission or firmware mismatch. Record the exact point of failure and check product-specific support limits.
Validate and plan a rollback
Voice on both ends uses intended microphone and sound output. Do not make emergency calls to test device routing. If the last change made matters worse, restore it and request supported assistance with a redacted troubleshooting summary.
Verify the result
Success looks like this: Voice on both ends uses intended microphone and sound output. Run this check on the same device and account that originally failed. A different device passing is useful as a comparison, but it does not prove the original issue is fixed.
What to check if it still fails
Before contacting support, collect the exact model and version, the outcome of the baseline test, and whether the controlled correction changed anything. Keep passwords, private media, account identifiers, serial numbers and network keys out of screenshots or shared logs. Do not make emergency calls to test device routing.
Solution Checklist
Frequently asked questions
Should I reset the entire device?
Not at this stage. Compare voice recorder microphone selection and phone call route. A reset can erase useful state and is not justified when a specific path can still be isolated.
Which detail should I give support?
Report the exact symptom and the outcome of the targeted test: Voice on both ends uses intended microphone and sound output.