Missing the A2DP profile and defaults to low quality

The fix is:

https://github.com/bluez/bluez/commit/62e591578e3f948e187aacf44ede4286fad37ad7

@vanvugt Thank you very much for opening this bug and everyone else for the quick fix!

Also we shouldn't target jammy until someone is assigned to it.

But now it looks like a fix is released, no? Sorry, I'm still new to launchpad and not everything is obvious to me yet.

Yes you are right that it looks confusing, but this is how Launchpad works. A bug that is fixed in any release is closed. :/

Adding a task to fix it in 22.04 will reopen the bug just for 22.04 but generally we don't do that until someone is assigned to actually do the work.

To request that a fix be considered in 22.04 you add the 'rls-jj-incoming' tag which has already been done in comment #1.

Thanks for clarifying, that makes sense now.

Actually I just wanted to thank you, if there would be reactions to comments that would be great for that. But as I'm writing this comment now I got one other question: In the sidebar I see many people being listed under "May be notified". And I'm very sorry if all people listed there now receive an email because of this comment, I'm already feeling a bit guilty writing it just because I wanted to thank Daniel. But what does "May be notified" mean? Are there going emails out to everyone there?

Edit: Is there maybe a "Getting Started with Launchpad", maybe even specific to Ubuntu?

"May be notified" generally means people will be receiving some comments as emails, like when a bug is closed or changes status. Only "Notified of all changes" will be receiving all comments but even then expect those people to have email filters set up so they don't have to read everything.

Usually very few people are listening :)

Thanks, good to know :) At least you are listening :P

Do you know about any updates on this topic?

Also added this to our internal tracker so we don't forget to patch jammy.

Hey @vanvugt, is there maybe any ETA?

This work is not currently scheduled. It's just on the backlog queue.

Looks like a simple patch though. Given how simple it is I might try to do it in the coming weeks.

Oh, I forgot I don't own Sony WH-1000XM4 anymore but hopefully the bug reproduces with other headphones.

Debdiff for jammy

Patch attached above, but can anyone help with a reliable test plan? (edit the top of this page)

Rafael, I can't seem to find a way to reproduce the bug with the headphones I do have. Can you outline the steps (and the model of headphones) you are using?

Hmm, currently when connecting it via blueman it automatically connects with the last used profile.
I just saw it says "High Fidelity Playback (A2DP sink, codec SBC-XQ)". So it seems to have A2DP there.
But as soon as I change my Mic Input Device to my headphones it changes to "Headset Head Unit (HSP/HFP codec mSBC)". If try to change the profile back to the A2DP sink my input device is also switched back to my internal Laptop Mic.

I'm not sure anymore if the A2DP sink was always there or if came back with a recent OS update (Linux Mint 21.1) - I'm also not sure if bluez 5.65 can fix this behavior.
Is there a more or less easy way I can test this on my machine? Maybe just clone it from the GitHub repo, checkout 5.65, compile and install it? Or do I need additional steps?

IIRC I tried to install it from source back then, but had missing build dependencies (or versions) which were not in the package repositories. I could be wrong, though.

OK so you may or may not be commenting on the right bug. Assuming you are, we'll just ask you to test the proposed fix when it is built...

I just removed my WF-1000XM4 from my device list and paired them again.
Now I have "High Fidelity Playback (A2DP Sink, codec LDAC)" and it was selected by default.

I have no idea what changed. bluez is still 5.64 since 2022-08-28. Maybe it's related to the blueman update from 2.3.4 to 2.3.5 on 2023-01-19 or some pipewire update on 2023-01-12.

These are my current bluez related packages:
bluez-alsa-utils/jammy 3.0.0-2 amd64
bluez-btsco/jammy 1:0.50-0ubuntu7 amd64
bluez-cups/jammy,now 5.64-0ubuntu1 amd64 [installed]
bluez-firmware/jammy,jammy 1.2-7 all
bluez-hcidump/jammy 5.64-0ubuntu1 amd64
bluez-hcidump/jammy 5.64-0ubuntu1 i386
bluez-meshd/jammy 5.64-0ubuntu1 amd64
bluez-meshd/jammy 5.64-0ubuntu1 i386
bluez-obexd/jammy,now 5.64-0ubuntu1 amd64 [installed]
bluez-obexd/jammy 5.64-0ubuntu1 i386
bluez-tests/jammy 5.64-0ubuntu1 amd64
bluez-tests/jammy 5.64-0ubuntu1 i386
bluez-tools/jammy,now 2.0~20170911.0.7cb788c-4 amd64 [installed]
bluez/jammy,now 5.64-0ubuntu1 amd64 [installed]
bluez/jammy 5.64-0ubuntu1 i386
libasound2-plugin-bluez/jammy 3.0.0-2 amd64
libkf5bluezqt-data/jammy,jammy 5.92.0-0ubuntu1 all
libkf5bluezqt-dev/jammy 5.92.0-0ubuntu1 amd64
libkf5bluezqt-doc/jammy,jammy 5.92.0-0ubuntu1 all
libkf5bluezqt6/jammy 5.92.0-0ubuntu1 amd64
python3-bluez/jammy 0.23-4build1 amd64
qml-module-org-kde-bluezqt/jammy 5.92.0-0ubuntu1 amd64

So it seems it's somehow unrelated to bluez 5.65

Alright, there's no need to wait for a fix here. Mainly because there's no one to verify a fix anymore.