Hi, I did a fresh install of fedora 30 recently and everything(for the most part) worked great. Unfortunately, my Bluetooth headphones(WH-1000XM2) stopped working today. I can hear audio with the Headset Head Unit config (mono). The High Fidelity config is listed as an option but I can just barely hear audio when selected. Volume is at max. The Hight Fidelity config still works using the internal speakers and the analog headphone jack
How do I troubleshoot this? DNF history shows I have done a few updates recently. Perhaps one of those caused the issue? I’m not sure where to start.
This should also work for Fedora using dnf package manager.
There seems to be a package conflict for instance.
But despite of this my Fedora 30 is collaborating with a bluetooth receiver a2dp. I can send sound out of Fedora 30 to a bluetooth receiver. It appears as new playback HiFi a2dp sink in Pulseaudio.
In case of troubles investigate on capabilites of controller and receiving device by mean of
bluetoothctl
dnf shell
install pulseaudio-module-bluetooth-freeworld
remove pulseaudio-module-bluetooth
run
This package contains: “Bluetooth audio (A2DP/HSP/HFP) support for the PulseAudio sound server. Includes support for LDAC, aptX and aptX-HD codecs.”
Enjoy!
EDIT: fix for conflicts with nonfreeworld package as reported by [awfed]
dnf install pulseaudio-module-bluetooth-freeworld
Letzte PrĂĽfung auf abgelaufene Metadaten: vor 0:32:44 am Fr 17 Mai 2019 17:32:41 CEST.
Fehler:
Problem: problem with installed package pulseaudio-module-bluetooth-12.2-3.fc30.x86_64
- package pulseaudio-module-bluetooth-freeworld-1.1-3.fc30.x86_64 conflicts with pulseaudio-module-bluetooth < 12.2-100 provided by pulseaudio-module-bluetooth-12.2-3.fc30.x86_64
- conflicting requests
- package pulseaudio-module-bluetooth-freeworld-1.1.99-2.fc30.x86_64 conflicts with pulseaudio-module-bluetooth < 12.2-100 provided by pulseaudio-module-bluetooth-12.2-3.fc30.x86_64
So, you are saying that the standard pulseaudio Bluetooth module does not work? Is this a bug, or expected behavior? And I would have to install this freeworld package just to play audio through a Bluetooth speaker?
I suspect I’m having the same problem. I have wasted the past hour diddling with Gnome Bluetooth and the bluetoothctl program, but nothing works. My speaker is seen and I can find the address, but when I run the pair subcommand, it always responds “Failed to pair: org.bluez.Error.ConnectionAttemptFailed”.
Ok, I broke down and replaced pulseaudio-module-bluetooth with pulseaudio-module-bluetooth-freeworld. Now, I can successfully pair with my speakers. However, I still cannot connect to them. The bluetoothctl connect command still fails immediately with “Failed to connect: org.bluez.Error.Failed”.
Hmm, so sadly this appears to be a pretty common issue; a quick google of the busy-related errors turned up quite a few results, with causes ranging from kernel bugs to linux-firmware, and solutions sometimes as simple as “unpair and re-pair the device”.
There have been quite a few linux-firmware issues with Intel chipsets in the past few months, and I know some are related to bluetooth. What is the model of your Bluetooth controller? (You can do sudo lspci | grep -i 'network\|bluetooth'.)
Here is what I can find: lsusb shows an Intel device 8087:0a2b. No label is given except “Intel”. An internet search shows that this device has something to do with Bluetooth.
Now, I find an Intel page that shows my Bluetooth driver is outdated and offers to automatically update it. That sounds incompatible with Fedora software management to me, though.
It says my driver is 20.20.0.5 and I should have 20.70.0.4
This device does indeed have an integrated bluetooth controller, were you trying to use a USB one instead?
Also, the 8265’s firmware was updated in the latest linux-firmware release, which was pushed to the repos just two days ago. Have you tried upgrading to see if it fixes anything?
I update daily. I just received many iwl firmware and linux-firmware updates this morning. I rebooted, then rechecked the Intel page that reveals the Bluetooth driver version; it still says it’s the same as before, 20.20.0.5
No, I have not added it as a USB device. I trashed the horrible Realtek 8723 wifi card that came in this PC and replaced it with an Intel 8265, which performs much better. That seems to be where my system is picking up its Bluetooth connectivity. It is an m2 form-factor card inside the notebook PC. I have no idea why it shows up as a USB device. Note that the wi-fi portion of the card was picked up by lspci, but the Bluetooth was picked up by lsusb.
A little more info from Intel: The current Bluetooth driver version is 21.30.0 dated Aug 13, 2019. Of course, they only provide it for MS Windows platforms.
Ok, I have resolved the problem, and I am an idiot. The problem was that there is a clearly identified Bluetooth button on the speakers, and that is what I have been using. I think it is what got me paired.
But there is another button for Connect. When I pressed it and ran command “connect ” in bluetoothctl, the connection was established, immediately.
I still have trouble with my speaker here—it has one of these “connect” buttons too and it connects to any devices in range etc.