Bluetooth Headset cannot be used as both headphones and speakers

Hi!

I hope I could bring more light to this issue to the developers working on this fix.

I had problems with crackling sound in Kodi, they said it was a sound drivers issue.

The sound started crackling after 10-15 minutes into a video when played with Kodi, but when played with Media Player Classic there was no issue. When it started crackling it got worse gradually and was unmanageable after a few seconds, I had to stop the video and resume.

Now among the automatic updates to Win10, one update fixed this issue. Hurray!

There is still a single very short crackling sound every 10-15 minutes, but I can hear the sound automatically fix itself, so the issue is definitely fixed.

And now after that sound update, I have the same issue as others here on this thread (but only in RDP!).

The thing is it was working great before, but after this update, I started hearing very faint crackling in my headset when the music starts playing and then no more crackling, only at the start of each music/voice (at initialization). Maybe this faint initialization crackling was there before, I just didn't notice it (it's almost silent - nonissue).

Now the weird part. On my desktop, my Bluetooth Sony Headset works great in Teams and other programs, but when using remote audio in RDP it stopped working, it was working prior to this update (update was around December/November 2020).

To test it (on host RDP machine):

Start playing sound on Youtube (sometimes it works, sometimes it does not), then go to Sound Settings and audio always stops working, no microphone bar responds (prior to update it worked), now go to Device properties under Input, and press Start test, audio stops working, microphone bar responds to my voice, press Stop test and now I can hear the audio playing in Youtube, but the microphone does not respond. I can press the Start/Stop button multiple times, but the audio and microphone will never work simultaneously together as it did before the mysterious Win10 update.

I have to mention that no drivers were manually installed and no settings were changed.

I also extensively tested all fixes and options and everything is set as it should be, remember it worked before and it still does, just not on the host machine in Remote Desktop.

Same here, multiple devices tested

The only thing that worked on calls is setting the speaker to "Headphones" and the Mic to the laptop's one

Any other settings sometime works but mostly doesn't

It could be, but not positive i have the same problem, that the computers bluetooth receiver cant output and input at the same time as it may be a cheap receiver or one which does not have that functionality therefore audio and mic input wouldn't work together. could be a hardware issue rather than software.

any news for help?

i has same issue 

2020 still not fixed this?

Thank you. I do have it working completely wire free with the H19 IPO headset, the 'upgraded' 059 headset is not really an upgrade as it is at least 3yrs old since 1st manufacture.   

The only issue i now have with H19 IPO is that the battery icon always shows 100% in Windows.   But I have come to accept that M$ don't give a rats **** and it will never get fixed. sigh.  No wonder they are losing market share to Apple and Android/Linux!

I wish Windows wasn't so stupid. My iPhone works great and easily switches between listening to music and making calls. Windows with Skype sometimes works perfectly - I can listen to music and when I take a Skype call the music is ducked under the call but still audible, just not intrusive.

The problem I have is any headset - Jabra, Bose both tested - sound great on Windows until you use it in communications mode. After that it stays stuck in this mode with crappy mono tinny audio until the next reboot. **** Microsoft? Why do this at all? Why not just duck the other audio signals? And why force the audio into crappy tinny mono - these days Zoom calls (sorry Teams) have great audio and can even have stereo audio. At least make this a "feature" I can disable.

Maybe the answer is to have two drivers - one for the mic and one for the headphone - so that Windows doesn't recognize it as a comms device.