Linux Client only polls for audio devices on start up
When using the Teams Linux Client, the client only polls for audio devices on start up. If I connect my headset via bluetooth, I have to
restart the app. As an alternative, the client could just used the default device exposed my pulse audio.
Client version: 1.3.00.5153 64bit
OS: Fedora Linux 31
Steps to reproduce:
1) Start Teams
2) Connect Bluetooth headset
3) Go to Settings -> Devices
User would see Device listed under speaker and/or microphone
Device is not seen
1) Poll Pulse audio for new devices when going to devices
2) Use the default system devices as exposed by Pulse.
This is really a PITA when you want to switch from your default audio (e.g. Speakers and Webcam mic) to a BT headset.
I have the same problem. I have to restart teams to get it to see the bluetooth headset if I turn the headset off and on. This is extremely irritating. Please fix.
Robert Hancock commented
This is quite an annoying bug, which basically means I end up using Teams on the web through Chrome rather than the actual Linux app since I can't be sure that the audio is going to work when I make a call. I'm not sure why this works in Chrome but not in the app since I understand the app is basically a Chromium container.
In fact, at least sometimes, Teams does end up using the newly connected Bluetooth headset for audio, even though in the settings it doesn't even show up and it says it is using a different device entirely.
This is a pain point when a call is incoming and you want to use a Bluetooth headset. You have to tell people that you will call them back.
Average Joe commented
I need this, it's such a pain restarting the client all the time.
Jimmy Sjölund commented
I have the same issue, only solution is to close Teams and log in again.