It also seems like the issue can be triggered by moving away from the computer. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. The dongle is rather hot when it disconnects. There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Then the computer fails to enable the sound device (visible in the preference manager f.ex.) It may take 5–10 minutes and up to several hours before it disconnects. Then at some random point it start to lag noticeably (sound becomes scratchy)Īnd suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) When I listen to sound from a movie with A2DP I have also used other dongles, but it seems like all of them has the same chipset. To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. They will probably be replaced when I have time to rebuild everything. It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment.

(Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) I'm now running Ubuntu 19.10 and Gnome 3.34.2. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. Both of them have run both Ubuntu and Windows. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on.

Bcm20702a0