I have used a version of a workaround -- though not adopting the code below, instead having an auto resetting of the headset mode which is a work around.
For the Pulseaudio developers -- I think the code that is causing this issue are around or between lines 1421 and 1503 of the below github code page for: module-bluez4-device.c
The work around in the code seems to be about using a timer a to sync everything back up when a disruption occurs -- but either the timer is not working as intended, or the thresholds for the re-syncing process need to be considered.
This is what I can gather but am interpreting as best I can.
This is a common topic in troubleshooting boards for Bluetooth on linux distros.
I have used a version of a workaround -- though not adopting the code below, instead having an auto resetting of the headset mode which is a work around.
For the Pulseaudio developers -- I think the code that is causing this issue are around or between lines 1421 and 1503 of the below github code page for: module- bluez4- device. c
pulseaudio/ src/modules/ bluetooth/ module- bluez5- device. c
https:/ /github. com/pulseaudio/ pulseaudio/ blob/2417305ae7 55cbb3a92ca43a0 58f550809069cd9 /src/modules/ bluetooth/ module- bluez5- device. c
The work around in the code seems to be about using a timer a to sync everything back up when a disruption occurs -- but either the timer is not working as intended, or the thresholds for the re-syncing process need to be considered.
This is what I can gather but am interpreting as best I can.
This is a common topic in troubleshooting boards for Bluetooth on linux distros.