Forum Discussion
dwaghela
Dec 11, 2024Copper Contributor
Persistent Bluetooth Headset Issues in Microsoft Teams
Many users, including myself, have encountered persistent issues using Bluetooth headsets with Microsoft Teams, particularly in the desktop app. Common problems include:
- Audio Output Problems: Low audio quality or no audio at all.
- Microphone Issues: The microphone does not function consistently or at all.
- Connection Drops: Devices disconnect unexpectedly during or after breakout sessions.
- Specific Trigger Points: These issues are often limited to Teams and do not occur in other applications.
Notable Observations:
- Disabling the "Handsfree Telephony" service on the headset in Windows resolves many of these problems but renders the headset as a simple audio output device, necessitating an external microphone.
- The issues seem prevalent across various brands (e.g., Jabra, Poly Voyager, Sony, Bose)
These issues are frustrating, especially since they are less frequent in other apps like Zoom or on the Teams web app. It seems related to how Teams interacts with Bluetooth profiles (A2DP vs. HFP) and prioritizes them during meetings.
Action for the Community:
To help Microsoft prioritize this issue, I’ve submitted detailed feedback on the Microsoft Teams Feedback Portal. If you’re experiencing similar problems, I encourage you to upvote and comment on the feedback to bring more visibility to this matter.
4 Replies
Sort By
- HelloBenTeohBronze Contributor
It seems related to how Teams interacts with Bluetooth profiles (A2DP vs. HFP) and prioritizes them during meetings.
Yep, this is pretty much it. There's not a lot that can be done unless the Bluetooth technology changes.
- FiniteLooperOccasional Reader
I have found a fix for this! You have to disable the headset portion of the Bluetooth device so that it never switches to that.
https://answers.microsoft.com/en-us/windows/forum/all/how-to-permanently-disable-handsfree-telephony-for/c9e3c827-9409-48f1-9cca-531ad4a6d97d
- LawrencesproulCopper Contributor
I have a problem like this. It only occurs if Teams is running when I connect the headset
- Lawrence_SproulCopper Contributor
Wow I seem to finally have a fix that works for me.
There are many things that I have tried unsuccessfully to fix this, including everything suggested in this thread except re-installing drivers. It is a work computer so I can't install drivers and getting IT to do it is painful if not impossible.
Unfortunately, I dont know exactly how I did it.
Basically I disabled Telephony Service on the device, then re-enabled telephony.
The result is that my Headset is now recognized as two devices. A headset device and a headphones device.
I think that disabling the Telephony required assigning a new driver for the headphones, and re-enabling Telephony configured a second driver, so I now have two drivers configured for the one device.
In Teams, I selected "Headphones" for Output and "Headset" for Input.
My headset has been working properly for a couple days now.