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

Hi NatashaGoode, You may try the other options below. Hope that one of the solutions will solve the issue. 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" 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.

Amen - this finally worked! You should pull down all the other wrong answers on MSFT's site though, as this is the correct one. Thank you!

i tried uninstall and reinstall then bluetooth works again Seems the pronlem was triggered by "transfer" function when i tried to switch the meeting from phone to PC. PC audio was down at the same time.

Oh, good point! it started to magically work again with my car, although i hadn't made any settings in weeks. no idea why. Still will not work with my hearing aids (i've had them about a month). Still won't work for anything else that i've tried. I don't use headphones anymore because....hearing aids. and if that's microsoft's answer, they can walk on legos. keep us posted on the ADA factor! i'm as curious as i am frustrated. I also have a Samsung S22

This issue was never truly fixed as others are suggesting. I work on audio for smartphones and I looked at how the audio stacks are accessed. There are 3 issues that remain unfixed or super unreliable: Teams for Android uses Nearby function to scan for RF or ultrasonic beacons related to other audio devices, i.e., office conference room units or Teams Room devices. If you don't grant the app Nearby access, then it won't even bother to look at normal paired Bluetooth devices. This is silly. With so many people WFH or doing hybrid work, most of us aren't near these enterprise-class conference device to even want to project the call into these devices. Even if you grant it Nearby access, Teams seem to have an issue query for active Bluetooth devices. Team also doesn't respond to OS broadcast of new device arrival either. This explains why even you turn on a paired Bluetooth device and it's connected to your phone, it doesn't always appear in the audio device list when you try to select something besides the handset or speakerphone endpoints. The audio device discovery logic doesn't seem to respond to these OS broadcasts. Teams seems to lack Bluetooth state awareness. Depend on the VoIP app, it can either access Bluetooth through handset/telephony mode, or multimedia mode via decoupled speaker (A2DP) and microphone. If you have conducted a prior call on another app, i.e., Skype, Zoom, WebEx, etc, there is a good chance Teams doesn't know what to do with that Bluetooth device or the state it was left at. I am shocked how inept Microsoft is on this particular issue - there is no other VoIP collaboration app that have soooooo many issues with Bluetooth audio devices. I am on these apps all day long and Teams is the only one giving me this level of headache.

Can't connect Bluetooth headset to Android Teams

Anonymous

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

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

Hi NatashaGoode,

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

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"

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.

0 comments

60 additional answers

Anonymous

2023-05-17T13:11:53+00:00

Amen - this finally worked! You should pull down all the other wrong answers on MSFT's site though, as this is the correct one. Thank you!
Was this answer helpful?

0 comments No comments
Anonymous

2023-05-11T03:05:44+00:00

i tried uninstall and reinstall then bluetooth works again Seems the pronlem was triggered by "transfer" function when i tried to switch the meeting from phone to PC. PC audio was down at the same time.
Was this answer helpful?

0 comments No comments
Anonymous

2023-05-09T13:18:07+00:00

Oh, good point!

it started to magically work again with my car, although i hadn't made any settings in weeks. no idea why. Still will not work with my hearing aids (i've had them about a month). Still won't work for anything else that i've tried. I don't use headphones anymore because....hearing aids. and if that's microsoft's answer, they can walk on legos.

keep us posted on the ADA factor! i'm as curious as i am frustrated.

I also have a Samsung S22
Was this answer helpful?

0 comments No comments
Anonymous

2023-04-17T18:45:23+00:00
This issue was never truly fixed as others are suggesting. I work on audio for smartphones and I looked at how the audio stacks are accessed. There are 3 issues that remain unfixed or super unreliable:
1. Teams for Android uses Nearby function to scan for RF or ultrasonic beacons related to other audio devices, i.e., office conference room units or Teams Room devices. If you don't grant the app Nearby access, then it won't even bother to look at normal paired Bluetooth devices. This is silly. With so many people WFH or doing hybrid work, most of us aren't near these enterprise-class conference device to even want to project the call into these devices.
2. Even if you grant it Nearby access, Teams seem to have an issue query for active Bluetooth devices. Team also doesn't respond to OS broadcast of new device arrival either. This explains why even you turn on a paired Bluetooth device and it's connected to your phone, it doesn't always appear in the audio device list when you try to select something besides the handset or speakerphone endpoints. The audio device discovery logic doesn't seem to respond to these OS broadcasts.
3. Teams seems to lack Bluetooth state awareness. Depend on the VoIP app, it can either access Bluetooth through handset/telephony mode, or multimedia mode via decoupled speaker (A2DP) and microphone. If you have conducted a prior call on another app, i.e., Skype, Zoom, WebEx, etc, there is a good chance Teams doesn't know what to do with that Bluetooth device or the state it was left at.
I am shocked how inept Microsoft is on this particular issue - there is no other VoIP collaboration app that have soooooo many issues with Bluetooth audio devices. I am on these apps all day long and Teams is the only one giving me this level of headache.
Was this answer helpful?

0 comments No comments