Microsoft Teams Mobile Calls: Intermittent One-Way Audio on Samsung Android Devices

Grimmen, Dennis 10 Reputation points
2026-09-10T08:29:06.6866667+00:00

Hi everyone,

We're experiencing a strange issue with Microsoft Teams and are wondering if anyone else has seen something similar.

Users occasionally experience one-way audio during Teams-to-Teams calls. To clarify, these are not Direct Routing or PSTN calls, but standard Teams-to-Teams calls between users.

What we've observed so far:

  • The issue only occurs on Samsung Android phones

Multiple Samsung models are affected, so it does not appear to be device-specific

Teams calls on Windows PCs and laptops work without any issues

We initially suspected a Wi-Fi or corporate network problem, but the same behavior occurs when users are connected via mobile data (4G/5G)

The issue is intermittent and difficult to reproduce consistently

Typically, one participant can hear the other, while audio in the opposite direction is missing

We've already checked and tested:

Teams app updates

Android updates

Microphone permissions

Different networks (Wi-Fi and mobile data)

Multiple Samsung device models

Since the issue seems limited to Samsung Android devices and occurs across different networks, we're struggling to identify the root cause.

Has anyone experienced similar one-way audio problems with Teams on Samsung Android devices? Did you find a root cause, Microsoft advisory, or any workaround?

Any suggestions would be greatly appreciated. Thanks!Hi everyone,

We're experiencing a strange issue with Microsoft Teams and are wondering if anyone else has seen something similar.

Users occasionally experience one-way audio during Teams-to-Teams calls. To clarify, these are not Direct Routing or PSTN calls, but standard Teams-to-Teams calls between users.

What we've observed so far:

The issue only occurs on Samsung Android phones

Multiple Samsung models are affected, so it does not appear to be device-specific

Teams calls on Windows PCs and laptops work without any issues

We initially suspected a Wi-Fi or corporate network problem, but the same behavior occurs when users are connected via mobile data (4G/5G)

The issue is intermittent and difficult to reproduce consistently

Typically, one participant can hear the other, while audio in the opposite direction is missing

We've already checked and tested:

Teams app updates

Android updates

Microphone permissions

Different networks (Wi-Fi and mobile data)

Multiple Samsung device models

Since the issue seems limited to Samsung Android devices and occurs across different networks, we're struggling to identify the root cause.

Has anyone experienced similar one-way audio problems with Teams on Samsung Android devices? Did you find a root cause, Microsoft advisory, or any workaround?

Any suggestions would be greatly appreciated. Thanks!

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

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. bdiepold 0 Reputation points
    2026-09-18T07:18:07.2766667+00:00

    Hi, same problem for me. Only Samsung affected, iPhone is okay.

    Was this answer helpful?

  2. Helen Luu 3,300 Reputation points Independent Advisor
    2026-09-10T08:45:54.25+00:00

    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.

    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.