Microsoft Teams Android app poor outbound audio quality on Samsung Galaxy A36 over Wi‑Fi, but browser and Bluetooth are fine

Simon Laffoley 0 Reputation points
2026-10-13T13:04:31.04+00:00

We are investigating a Microsoft Teams audio issue on a Samsung Galaxy A36 and would like to know if this is a known issue or if anyone has seen similar behaviour.

Environment

  • Device: Samsung Galaxy A36
  • OS: Android 16 / One UI 8.5
  • Teams Version: 1416/2026.27.011
  • Multiple Wi‑Fi networks tested (office and home)
  • Issue occurs on different access points and internet connections

Problem** **Description

When making Teams calls using the Android Teams app and the phone's built-in microphone, the remote party reports that the user's voice is:

  • Crackly
  • Muffled
  • Low pitched
  • Difficult to understand

The user does not hear any issues themselves. The problem only affects the transmitted audio heard by the other participant.

Troubleshooting** **Performed

✅ Battery optimisation disabled for Teams

✅ Wi‑Fi power saving disabled

✅ Teams noise suppression disabled

✅ Teams cache cleared

✅ Teams Developer Preview enabled

✅ Tested on multiple Wi‑Fi networks (office and home)

✅ Tested on 2.4 GHz Wi‑Fi

✅ Reproduced on multiple outbound Teams calls

Results
Scenario Result
Teams app + Wi‑Fi + built-in microphone Poor audio
Teams app + Wi‑Fi + Bluetooth headset microphone Good audio
Teams app + Mobile Data + built-in microphone Good audio
Teams via Edge browser + Wi‑Fi + built-in microphone Good audio

Because the same device microphone works correctly in both the Edge browser and on mobile data, and a Bluetooth microphone works correctly within the Teams app, the issue appears to be specific to the Teams Android app when using the handset microphone over Wi‑Fi.

Questions

  1. Is this a known issue with Teams Android on Samsung Galaxy A36 devices?
  2. Has anyone seen similar behaviour with One UI 8.5 or Android 16?
  3. Are there any Teams media, audio-processing, codec, or Wi‑Fi-related settings that could explain why only the handset microphone path is affected?

Any suggestions would be appreciated.

Microsoft Teams | Microsoft Teams for business | Teams on mobile devices
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. bdiepold 0 Reputation points
    2026-10-14T08:39:04.9+00:00

    Hi @Simon Laffoley same problem in our company. We have heart that the next firmware update of Samsung should solve the problem. It was scheduled for this month, now it is postponed to January. And bad news it is not clear if the installed Android version will get the update in January. We either must look for new device for our company or we pray and hope that A36 and A27 will get the promised update.

    Was this answer helpful?

    0 comments
  2. Kristen Tran 2,445 Reputation points Independent Advisor
    2026-10-13T13:38:10.6066667+00:00

    Hi Simon,

    Thank you for providing such detailed test results. The comparison between the built-in microphone, Bluetooth headset, Wi-Fi, mobile data, and Teams in Edge is particularly helpful in narrowing down the issue.

    At this time, I could not find any official Microsoft documentation confirming this as a known issue specifically affecting the Samsung Galaxy A36, Android 16, or One UI 8.5. Therefore, I would not classify it as a known issue at this stage.

    Since the built-in microphone works correctly when using Teams through Edge over Wi-Fi and when using the Teams app over mobile data, the microphone itself does not appear to be the general cause. Based on your testing, the behavior seems to occur specifically when the Teams Android app uses the phone's built-in microphone over Wi-Fi.

    Since you have already completed extensive application and network troubleshooting, I would suggest trying the following:

    1. Make sure both the Teams app and your Samsung device software are fully up to date.
    2. Completely uninstall Teams, restart the phone, and then reinstall Teams from Google Play. This provides a cleaner test than clearing the app cache alone.
    3. If available on your device, temporarily disable Samsung audio-processing features such as Dolby Atmos, Adapt Sound, voice effects, or other microphone/audio enhancements, and test another Teams call.
    4. If the issue persists, I recommend asking your IT administrator to open a support request with Microsoft. When submitting the case, include the Teams version, Android and One UI versions, the time of an affected call, participant information, and the comparison results you provided above. This information may help Microsoft Support investigate the issue further. For more information, please refer to: Get support - Microsoft 365 admin

    In the meantime, based on your testing, using a Bluetooth headset, mobile data, or Teams through Edge may serve as practical workarounds.

    I hope this helps point you in the right direction. If you have any further questions or updates, please feel free to let me know.

    Best regards.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.