Hi. So I have a Plugable-brand USB bluetooth audio transmitter. I’ve installed the necessary Broadcom firmware and the device works fine until I reboot. Following a reboot, dmesg shows the Plugable device is recognized but the audio device never shows up in sound settings. Near as I can tell, bluetoothd does not indicate that the endpoints have been registered. If, at this point, I remove and re-install the Bluetooth transmitter, bluetoothd gets notified, registers the device and the audio device appears in the sound settings.
Perhaps during boot the USB subsystem is scanning the USB bus before the Bluetooth subsystem is starting?
Has anybody run into this? Is there a workaround short of removing and re-installing the device?
I use a bluetooth rocket dongle to connect to my hearing aids and it works on reboot. Sometimes I do have to bring the menu down from the tray icon and reconect but not often, usually when I leave the area and come back.
Hi. Interesting that you asked if they’re paired. They are. In fact, the bluetooth receiver on the other side of the room has an LED that flashes when no paired devices are attached. It turns solid when a paired device is attached. As my system is rebooting, the receiver LED is flashing (which is expected behavior). By the time the GDM login screen is displayed, that LED is solid which suggests that the receiver and transmitter have linked-up even though the audio device does not appear in my sound settings. I’m not familiar enough with how bluetooth works to know if this is expected behavior. Once the devices have been paired once, will they automatically connect in the future without further software intervention?
Also, bluetooth is running on the machine at startup.
An interesting datapoint that I noticed a few minutes ago: As I described earlier, following a reboot, the BT audio device does not appear in my sound settings yet the remote BT receiver indicates that the devices have attached. If, at this point, I run “bluetoothctl list”, I do see “Amazon_Audio” as a connected controller. But, according to syslog, bluetoothd does not appear to actually register the endpoints unless I unplug and replug the USB transmitter. I think understanding what triggers bluetoothd to (not) register an endpoint is key to understanding my problem.
ok I have the same trouble but rarely and what I have to do is use the drop down menu from the tray icon and either disconnect and reconnect or just connect.
Bluetooth does act up at times.
you do have the icon in the sys tray correct?
It shows if your connected or not and has some configuration in a right click menu. A left click drops the connect menu and dis connect menu down. Sometimes it will cycle from connected to disconnected like it can’t lock on and a manual connect solves it.
So far I haven’t had to unplug and plug the dongle back in but in the past I have had to do just that. It has been at least 2 months since I have had to go the unplugging route.
The bluetooth integration is improving steadily.
It also helps to make sure the bluetooth device is listed as the main sound use or main source and priority in the sound config of system setting menu multimedia menu audio and video menu and check to make sure. If there is no bluetooth it falls back to the second choice or main audio device that is on board.
The one thing that drives me nuts is even when paired and connected it seems the link sleeps ( but is still paired and connected ) when theres no sound and starts to transmit sound only when something decides sound has been triggered or needs to be output… for example when watching a video in kaffeine the output is constant and smooth but when it;s a system sound it wakes up to transmit it seems and I only hear part of the output.