You are not logged in.
Using bluez-git also solved this problem for me with my Bose QC35ii's. Thanks
Offline
bluez 5.60 has been released and should contain the fix, so if anyone wants to, they can go back to using bluez instead of bluez-git
Offline
bluez 5.60 has been released and should contain the fix, so if anyone wants to, they can go back to using bluez instead of bluez-git
this upgrade indeed fixed the A2DP problem, but i'm finding that my MX Vertical needs a repairing after each reboot (and this issue persists if i switch to the bluez-git package), guess i'm staying at bluez 5.58
Offline
knovoselic wrote:bluez 5.60 has been released and should contain the fix, so if anyone wants to, they can go back to using bluez instead of bluez-git
this upgrade indeed fixed the A2DP problem, but i'm finding that my MX Vertical needs a repairing after each reboot (and this issue persists if i switch to the bluez-git package), guess i'm staying at bluez 5.58
Did you nuke /var/lib/bluetooth ?
Offline
Bzzz_56 wrote:knovoselic wrote:bluez 5.60 has been released and should contain the fix, so if anyone wants to, they can go back to using bluez instead of bluez-git
this upgrade indeed fixed the A2DP problem, but i'm finding that my MX Vertical needs a repairing after each reboot (and this issue persists if i switch to the bluez-git package), guess i'm staying at bluez 5.58
Did you nuke /var/lib/bluetooth ?
Yep, and i've seen early posts that have the very same issue.
Offline
Yep, and i've seen early posts that have the very same issue.
Maybe you should file a bug report on 5.60?
"ONLY THOSE WHO ATTEMPT THE IMPOSSIBLE WILL ACHIEVE THE ABSURD"
- Oceania Association of Autonomous Astronauts
Offline
Bzzz_56 wrote:Yep, and i've seen early posts that have the very same issue.
Maybe you should file a bug report on 5.60?
It seems that i've found the workaround to my problem, as suggested in the archwiki page Problems with all BLE devices on kernel 5.9+, and it works in my case!
Offline
bluez 5.60 has been released and should contain the fix, so if anyone wants to, they can go back to using bluez instead of bluez-git
I can confirm this. Although I had already downgraded to 5.58 and deleted `/var/lib/bluetooth/`, upgrading to 5.60 and restarting bluetooth service still hasn't broken anything. I'm able to enjoy A2DP and even aptX now! wohoo!
Thanks for figuring out the workaround though knovoselic
Offline
Updated to the new bluez-5.60-1 and removed the pulseaudio-modules-bt-git and replaced with pulseaudio-bluetooth (to get back to a more standard setup), removed the contents of /var/lib/bluetooth/ and then ran a systemctl restart bluetooth -- re-paired my WH-1000XM4 and now they finally work with a2dp.
Offline
Confirm the steps above worked for me after running bluez-git while this was being resolved.
I know the community revels in reading the manual etc but I hadn't done this kind of conflicting upgrade yet, so learned a couple of new pacman steps which I'll add here:
Attempting to remove bluez-git:
> $ sudo pacman -Rs bluez-git
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing bluez-git breaks dependency 'bluez-libs' required by networkmanager
:: removing bluez-git breaks dependency 'bluez' required by pulseaudio-bluetooth
:: removing bluez-git breaks dependency 'bluez-libs' required by pulseaudio-bluetooth
Ah, it provides those:
> $ pacman -Qi bluez
Name : bluez-git
Version : 1:5.59.r10.g864d03727-1
Provides : libbluetooth.so=3-64 bluez=5.59-1 bluez-utils=5.59-1 bluez-libs=5.59-1 bluez-cups=5.59-1 bluez-hid2hci=5.59-1 bluez-plugins=5.59-1
Required By : networkmanager pulseaudio-bluetooth
Conflicts With : bluez bluez-utils bluez-libs bluez-cups bluez-hid2hci bluez-plugins bluez-hcidump obexd-client obexd-server
...
Read the man page on this one:
> $ pacman -Rdd bluez-git
And finally reinstate the dependencies:
> $ pacman -Rdd bluez-git
> $ pacman -S bluez bluez-libs
Probably time to mark the thread as solved?
Last edited by marksievers (2021-07-15 22:38:34)
Offline