Can't connect Bluetooth headset to Android Teams

Anonymous
2022-12-08T00:05:25+00:00

This seems to be an ongoing issue. I have a Samsung Galaxy S22 Ultra. Until recently I had no problems connecting my Bluetooth headphones. Now I cannot. My AKG, NuraTrue, Sony wh1000mx5. All fail. I cannot find any setting in my phone app that allows me to choose my headset like the pc application does.

This appears to be an issue with MS Teams, not user error, device connectivity, etc.

I have tried the following advice previously posted without success.

  • Clearing the cache of your Android phone's Teams app by signing out and closing the Teams App. Then go to Phone Settings > Apps & Notifications > Teams > Storage & Cache > Clear Storage and Clear Cache and confirm your action. After that, please re-open the Teams App and sign in again to see if it makes a difference.
  • Unpair the device from Bluetooth devices (Forget devices), then reconnect.
  • Updating to the latest version of Teams for Android phones should resolve the issue, and Bluetooth should work properly with both devices

Please provide advice on how I can fix this issue. It is critical for my work.

TIA

Microsoft Teams | Microsoft Teams for business | Meetings and calls | Audio and video

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2022-12-08T04:49:15+00:00

Hi NatashaGoode,

You may try the other options below. Hope that one of the solutions will solve the issue.

  1. Check also the apps permission on your phone like camera, microphone and also nearby devices.

Go to Settings -> Apps -> Teams -> Permissions -> Allow access to "Nearby devices"

  1. Try to connect with your bluetooth device first before you open the Teams.

Please let me know if this doesn't work or if you need further assistance.

Thank you.

Was this answer helpful?

600+ people found this answer helpful.
0 comments

60 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2023-03-03T12:47:18+00:00

    This was so useful! Fixed it for me! Thanks a lot!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-02-21T17:58:17+00:00

    I tried the above and it worked! Thank you!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2023-02-16T18:25:49+00:00

    skype.... I miss it. Teams is a poor substitute.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  4. Anonymous
    2023-02-16T18:09:33+00:00

    Your issue is partly your phone's. On later Android devices, the requirement of giving "Nearby devices" permission is explicitly popped. It started late last year when this requirement was added by Teams.

    Give it time... The issue will reappear. Enabling permission for "Nearby devices" does not solve the issue persistently. I am on Teams about 8 to 10 hours of a day, and this issue reappears randomly throughout the day. The solution mentioned to turn on BT accessory before the call also doesn't make technical sense - Android broadcast to all apps when new audio device is attached to the system... Also, not everyone has every BT accessory turned on, so you can turn it on after a call/meeting initiated, i.e., have multiple BT headsets and decided to change after call started. If "Option 2" works, it means it's an Teams app bug. If should respond to OS broadcast of new audio devices and re-enumerate its audio device/endpoint list.

    This is a Teams app issue - absolutely NO other app has this issue. I am talking about Zoom doesn't have it, Meet doesn't have it, WebEx doesn't have it, GotoMeeting doesn't have it. Heck, even Microsoft's own Skype doesn't have it.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments