Headset model
Sony WH-1000-XM2 (tested with Jabra Elite 75t as well with same symptoms)
Bluetooth receiver
Ubit-AX200 802.11AX WiFi 6 using the drivers found here
Sound card
The onboard card in this motherboard is a GIGABYTE B550M DS3H and the drivers are from here (Realtek HD Audio Driver (Note) Win10 ver.2004 supported. -- [6.0.8945.1] -- 2020/05/08)
OS
Symptoms
I can pair the device like normal, no issues. Once paired, playing audio over something like Spotify works fine, playing games mostly works fine (Apex Legends has no audio at all -- not sure if this is related) UNLESS I enable the microphone. If the microphone is enabled, all sound stops (Spotify, games, whatever).
My simple test case is to play some music on Spotify then open sound settings (right-click the sound icon). This is what I see:
I think click Device properties and test microphone
. On the next screen if i click Start test
I can see the microphone receiving input but all music stops playing. It doesn't pause the music, Spotify continues to progress on the song it's on, just the audio output stops. No sound from the headphones.
This happens in online games. If I enable the microphone, game audio stops as well.
Back in the sound settings screen, if i switch the input to anything else, audio is fine as long as the mic is either disabled or a different mic is selected.
In the sound settings found via the Control Panel, I see this:
As in the image, if the Headphones entry is set as the default device, all the symptoms above occur. If i switch the default device to Headset, everything starts working as expected (audio and mic work simultaneously). The problem is that the Headset devices is limited to 1 channel, 16 bit, 16000 Hz (Tape Recorder Quality)
:
What I've tried
I've mostly tried re-installing drivers and using different combinations of default devices. Setting Headphones as the default device and Headset as the default communication device has no effect.
I don't have easy access to a wired headset with a microphone so I haven't been able to test that way to rule out/in bluetooth as the issue. I'll update if/when I am able to test this. It does happen with both bluetooth headsets that I have so I don't believe it's a headset specific issue.