Bug 2321690

Created attachment 2053658 [details]
Video demonstration

Bluetooth module name - CSR8510 A10

This looks very much like https://bugzilla.redhat.com/show_bug.cgi?id=2319597

Please update to latest updates and confirm if it's still an issue.

Is this still a problem? If so please report:
* kernel version
* linux-firmware version
* bluez version
* type of bluetooth controller (lsusb| grep -i blue)
* the bluetooth devices (make and model) that you are trying to pair

(In reply to Peter Robinson from comment #2)
> This looks very much like https://bugzilla.redhat.com/show_bug.cgi?id=2319597
> 
> Please update to latest updates and confirm if it's still an issue.
It is.

And in this thread 
https://bugzilla.redhat.com/show_bug.cgi?id=2319597

You literally asked me to file a new bug because you thought it's different from what other people faced and it turned into a blocker.
But my main issue was always with pairing bluetooth devices.

Bluez version 5.78.1
Kernel 6.11.5
Bluetooth controller - Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bluetooth devices - Realme brick bluetooth speaker, Oneplus Nord buds

> You literally asked me to file a new bug because you thought it's different
> from what other people faced and it turned into a blocker.

I deal with *LOTS* of bugs so I don't always remember every bit of context.

And the reason I asked is you didn't include all the details like versions on the bug.

> Bluetooth devices - Realme brick bluetooth speaker, Oneplus Nord buds

What audio mode do they operate in? There's been reports of some AVRCP devices having issues.

Have the same problem with bluetooth speaker, cannot connect via gnome gui, but if i connect it manually in bluetoothctl it works and connect it. Strange behaviour, no errors, nothing. Before, some recent update everything was worked fine.

It's probably bug 2321690, please put details there and answer the questions asked there.

(In reply to Peter Robinson from comment #6)
> It's probably bug 2321690, please put details there and answer the questions
> asked there.

Bah, ignore that, too many bugs

(In reply to ConEst from comment #3)
> (In reply to Peter Robinson from comment #2)
> > This looks very much like https://bugzilla.redhat.com/show_bug.cgi?id=2319597
> > 
> > Please update to latest updates and confirm if it's still an issue.
> It is.
> 
> And in this thread 
> https://bugzilla.redhat.com/show_bug.cgi?id=2319597
> 
> You literally asked me to file a new bug because you thought it's different
> from what other people faced and it turned into a blocker.
> But my main issue was always with pairing bluetooth devices.
> 
> Bluez version 5.78.1
> Kernel 6.11.5
> Bluetooth controller - Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI
> mode)
> Bluetooth devices - Realme brick bluetooth speaker, Oneplus Nord buds

Do you have problems connecting after pairing? Or is your issue only with the initial pairing process and then everything works fine after that?
For example, after pairing, can you successfully disconnect and reconnect to your BT device?

(In reply to Chester from comment #8)

> For example, after pairing, can you successfully disconnect and reconnect to
> your BT device?

Yes everything works fine after that. I'm able to connect to my bt devices with gui.
One thing - auto connect does not work properly.

I have simmalar issues with Fedora 41 Gnome and Sony WF-1000XM5 earbuds. 

Kernel: 6.11.6-300.fc41.x86_64
Device: Sony WF-1000XM5	
Bluethooth controller: Bus 003 Device 005: ID 8087:0033 Intel Corp. AX211 Bluetooth


I tried both pairing/connecting/trusting via bluetoothctl and fedora 41 gnome bluethooth settings.

P.S I managed once to pair and use earphones last week , it worked but with only bluethoothctl ( gnome is bugged ) , but still auto connect was not working.

Now i need just to pair it, i do not care about auto connect :(

*** Bug 2323852 has been marked as a duplicate of this bug. ***

*** Bug 2324809 has been marked as a duplicate of this bug. ***

> > Bluetooth devices - Realme brick bluetooth speaker, Oneplus Nord buds
> 
> What audio mode do they operate in? There's been reports of some AVRCP
> devices having issues.

Can people answer this for me? Are their devices AVRCP (Audio/Video Remote Control Profile) devices?

(In reply to Peter Robinson from comment #13)
> > > Bluetooth devices - Realme brick bluetooth speaker, Oneplus Nord buds
> > 
> > What audio mode do they operate in? There's been reports of some AVRCP
> > devices having issues.
> 
> Can people answer this for me? Are their devices AVRCP (Audio/Video Remote
> Control Profile) devices?

Yes, in my case.

	Name: WH-1000XM5
	Alias: WH-1000XM5
	Class: 0x00240404 (2360324)
	Icon: audio-headset
	Paired: yes
	Bonded: yes
	Trusted: yes
	Blocked: no
	Connected: yes
	WakeAllowed: yes
	LegacyPairing: no
	UUID: Vendor specific           (00000000-deca-fade-deca-deafdecacaff)
	UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Cont.. (0000110f-0000-1000-8000-00805f9b34fb)
	UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
	UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
	UUID: Headset HS                (00001131-0000-1000-8000-00805f9b34fb)
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	UUID: Vendor specific           (45c93e07-d90d-4b93-a9db-91e5dd734e35)
	UUID: Vendor specific           (764cbf0d-bbcb-438f-a8bb-6b92759d6053)
	UUID: Vendor specific           (81c2e72a-0591-443e-a1ff-05f988593351)
	UUID: Vendor specific           (8901dfa8-5c7e-4d8f-9f0c-c2b70683f5f0)
	UUID: Vendor specific           (931c7e8a-540f-4686-b798-e8df0a2ad9f7)
	UUID: Vendor specific           (956c7b26-d49a-4ba8-b03f-b17d393cb6e2)
	UUID: Vendor specific           (9b26d8c0-a8ed-440b-95b0-c4714a518bcc)
	UUID: Vendor specific           (df21fe2c-2515-4fdb-8886-f12c4d67927c)
	UUID: Vendor specific           (f76acb00-7cab-495f-bb1a-e664598fd77f)
	UUID: Vendor specific           (f7a96061-a1b3-40de-aff0-e78ec45a151e)
	UUID: Vendor specific           (f8d1fbe4-7966-4334-8024-ff96c9330e15)
	Modalias: usb:v054Cp0DF0d0231
	Battery Percentage: 0x64 (100)

Update on my case:

As I stated I am using Sony WF-1000XM5 and found solution for successful pairing and good connection of Laptop (Fedora41) and earbuds. I am using Samsung S24 as a mobile device, I Connected to my earbuds with mobile ( i have installed Sony official application "Sound Connect" ), In this application I toggled off every feature. This was important because i think something was interfaring with linux bluetooth to pair my earbuds. 

I restarted bluetoothctl and checked if my earbuds was connected "info MAC_ADDRESS" and found out that is was still connected ( not paired tho ) used command "remove MAC_ADDRESS", and than restarted using "sudo systemctl restart bluetooth" after it i check with that bluetooth was up "sudo systemctl status bluetooth", entered in "bluetoothctl" and use command "scan on". 
After  this I activated as usual pairing mode for earbuds , and it was shown in bluetoothctl, I used "pair MAC_ADDRESS" and it paired successfully, after this I used "connect MAC_ADDRESS" and it connected successfully (no issue of playback or microphone, everything is cool). For extra, i just added in trusted "trust MAC_ADDRESS" and that is all.

After doing this all, I re-enabled everything from "Sound Connect" mobile app and everything is good for now.

P.S unfortunately i do not have time to deep dive and find out which setting was messing with bluetooth of my laptop (Dell Latitude 3540). I hope you can find this useful.

So I believe this has been fixed with the kernel-6.11.10-300.fc41 update, the fedora-release-41-28 release may also aide in improving the situations for AVRCP headsets (Which I think the Sony one is).

(In reply to Peter Robinson from comment #16)
> So I believe this has been fixed with the kernel-6.11.10-300.fc41 update,
> the fedora-release-41-28 release may also aide in improving the situations
> for AVRCP headsets (Which I think the Sony one is).

Can confirm.. Bluetooth is working perfectly now.

Thanks a lot, Team Fedora!