Arch Linux

D3rise

Member

Registered: 2021-06-21

Posts: 2

[SOLVED] No A2DP profile on WF-1000XM3 using PipeWire and BlueZ

I've tried to connect my Sony WF-1000XM3 to Arch Linux using PipeWire and BlueZ (through gnome bluetooth settings and also through bluetoothctl, nothing changes), but I found that it can't recognize it as A2DP device, only showing HSP/HFP profiles.
https://i.imgur.com/ZHMUWtT.png

By the way, if use Fedora in GNOME Boxes, it works as intended: connects, recognizes it as A2DP device and shows different codecs this headphones support (SBC and AAC).
https://i.imgur.com/WHhYzBp.png

Here's my configs and outputs of some commands that may be useful:
/etc/pipewire/media-session.d/bluez-monitor.conf (original files are taken from /usr/share/pipewire, then edited and put in /etc/pipewire)
pactl list
pactl info

Mod Edit - Replaced oversized images with links.
CoC - Pasting pictures and code

Last edited by D3rise (2021-06-22 03:02:24)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,743

Re: [SOLVED] No A2DP profile on WF-1000XM3 using PipeWire and BlueZ

Known issue with the current bluez, either downgrade to 5.58 or upgrade via bluez-git and remove /var/lib/bluetooth before re-pairing.

D3rise

Member

Registered: 2021-06-21

Posts: 2

Re: [SOLVED] No A2DP profile on WF-1000XM3 using PipeWire and BlueZ

Known issue with the current bluez, either downgrade to 5.58 or upgrade via bluez-git and remove /var/lib/bluetooth before re-pairing.

Updated to bluez-git. Now it works perfectly as intended, thanks!

grail69

Member

Registered: 2021-09-12

Posts: 11

Re: [SOLVED] No A2DP profile on WF-1000XM3 using PipeWire and BlueZ

Hi D3rise

First timer here where I have just built a new system and installed pipewire whilst having the same bluetooth headset and for the life of me I cannot get it to connect.
I am running the latest version of bluez and even copied your conf file but still no joy.

Did you have to add yourself to a particular group or something to make them work?

Mainframed1

Member

Registered: 2020-08-17

Posts: 6

Re: [SOLVED] No A2DP profile on WF-1000XM3 using PipeWire and BlueZ

Hi grail69,

I think the issue exists for bluez versions >=5.59.

The solution with bluez-git worked, since it was actually older (still 5.58) when V1del and D3rise commented, than the bluez package in extra.
But bluez-git was updated on 2021-07-28 to 5.60.

To solve the problem, you have to downgrade bluez to 5.58.
I did not find that package in the Arch Linux Archive.
Hence, I cloned the AUR repository of bluez-git, checked out the second-to-last commit (with version 5.58) and made the package. I think I had to do some rewriting in the PKGBUILD, such that it did not check out the newest version.
And then, don't forget to ignore updates for the package in pacman.conf.

grail69

Member

Registered: 2021-09-12

Posts: 11

Re: [SOLVED] No A2DP profile on WF-1000XM3 using PipeWire and BlueZ

Hi Mainframed1

Thanks for the reply, but I have an existing system (which is to be replaced by new one) which has the following:

$ pacman -Qs bluez
local/bluez 5.61-1
    Daemons for the bluetooth protocol stack
local/bluez-libs 5.61-1
    Deprecated libraries for the bluetooth protocol stack
local/bluez-utils 5.61-1
    Development and debugging utilities for the bluetooth protocol stack

The difference on the old machine is I am using a dongle to connect to the headset and on the new one the bluetooth is on the MB ( i wouldn't have thought this would make a difference)

Additionally the old box is using pulseaudio and the new is using pipewire, but I am guessing this is an issue after I connect.

Please let me know if there is any output I can provide to assist in someone helping?

Last edited by grail69 (2021-09-14 17:19:43)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,743

Re: [SOLVED] No A2DP profile on WF-1000XM3 using PipeWire and BlueZ

The current bluez has the issue in the original post fixed. if you have something else, please open a new thread with details on how you are trying to connect and what kind of error messages you see.

Closing.