Managing sound and video settings during Teams meetings and calls
I'm not able to see the device in Teams at all.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have a pair of Bluetooth Skullcandy Hesh 3 Headphones, and they have 2 connections with my laptop.
1)Hesh 3 Stereo
2)Hesh 3 Hands-Free AG Audio
When I use Hands free AG Audio, there is some static disturbance. When watching videos, stereo option gives great sound quality but for some reason it doesn't give any sound during a meeting in teams. In device settings during a meeting, once I choose Hesh 3 Stereo, the voice just stops.
Managing sound and video settings during Teams meetings and calls
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.
I'm not able to see the device in Teams at all.
Did you go to settings and there "Devices"? There at the top I see section "Audio devices", where I can set my speaker and microphone. I've got 1.5.00.9163 Teams version.
Sadly a very strange behavior of Teams, probably also a reason why many companies always want to use Zoom. Had the same issue, thank you for sharing the solution. Found also this video, which shows and explains the fix. I hope to use BT devices soon as intended with Teams. ¯\_(ツ)_/¯
Yeah I have played around with it, and gotten it to work occasionally. But it then it suddenly stops working even though the config is unchanged. Very weird.
This worked for me...
- Unpair headset
- Right-click start menu and open Device Manager
- Expand Bluetooth
- Right-click Microsoft Bluetooth LE Enumerator and disable. It will give you a warning about devices not working. Unless you have devices that require Bluetooth low energy, it will be okay. Leave the other one (without LE) enabled.
- Pair your headset
- Enjoy
This did not work for me. FYI, it's also a problem with Webex on Windows 10 and 11. I believe this is a problem in Windows not Teams.