Accessing and using Microsoft Teams on smartphones and tablets across platforms
Hi,
The testing you have already completed makes an issue confined to one Samsung model or one Wi-Fi network less likely. However, it does not yet confirm a Samsung-wide Teams defect or identify the root cause.
First, please determine the direction of the failure in each affected call:
- The Samsung user can hear the other participant but cannot be heard: investigate the Samsung device’s outbound audio/capture path.
- The Samsung user can be heard but cannot hear the other participant: investigate its inbound audio/render path.
For one affected call, record the exact date, time and time zone, both participants, Samsung model, Android/One UI version, Teams version, and the audio route being used. Do not post user addresses or call identifiers publicly.
An administrator with an appropriate Teams role can then check:
Teams admin center > Manage users > select the affected user > Meetings & calls > Completed meetings and calls
P2P calls are included in this view. Telemetry can take approximately 30 minutes to two hours to appear. Open the participant details and review the available Audio (Inbound), Audio (Outbound), device, media, and network information. The available fields can vary by session and license. See Monitor and troubleshoot Teams meetings and calls.
For controlled testing, try:
- A call with Bluetooth completely disabled and no connected headset.
- Switching between the earpiece and speaker, or muting and unmuting, when the issue occurs. Note whether this restores audio; it is an isolation test, not a confirmed fix.
- Force-stopping Teams, clearing the Teams app cache, and restarting the phone. If the problem continues, reinstall Teams on one test device.
- If available, testing the same affected account on a non-Samsung Android phone.
- If the organization uses an always-on VPN, Android work profile, or mobile security software, have the administrator compare an approved test without that specific variable. Moving from Wi-Fi to mobile data does not necessarily bypass an always-on VPN.
I could not identify a publicly documented Microsoft advisory specifically matching this Samsung Android pattern. This does not rule out an advisory shown only for your organization. Because this is intermittent and limited to the mobile client, the administrator should open a Microsoft 365 support request if the call telemetry does not reveal the cause. The affected user can also submit Teams mobile > Settings > Help & feedback > Send feedback > Report a problem, if that option is enabled, and include the occurrence time and device/app versions: Manage user feedback in Teams.