Kai Krakow

There's also an issue with establishing an encrypted connection between the controller and the Linux Bluetooth stack. The first problem is (from my tests) often a missing link key. This...

I'm seeing a similar problem after upgrading to latest 5.4.y: firmware was already up to date for me but I had a lot of connection dropouts and establishing connection is...

@richardtatum ``` [CHG] Device 5C:BA:37:D6:DE:E9 ServicesResolved: yes [CHG] Device 5C:BA:37:D6:DE:E9 Paired: yes Pairing successful [CHG] Device 5C:BA:37:D6:DE:E9 ServicesResolved: no [CHG] Device 5C:BA:37:D6:DE:E9 Connected: no ``` Yeah there's something happening that...

## HEADS UP Kernel 5.4.72 brought some patches regarding Bluetooth pairing. All chronology later kernels (5.8.16, 5.9.1) should have the same patches. For my controller, this doesn't make any difference...

Scan usually doesn't show your device if it is already known. Use `devices` in `bluetoothctl` to find the MAC address to remove, then use `remove `. Now, with `scan on`...

@schmitmd I cannot confirm this for 5.4.72. But the actual commits tell that this pairing problem only came apparent after some Bluetooth changes introduced with 5.9. So older kernels may...

The kernel Bluetooth stack solved a bug for BLE devices in privacy mode: https://bugzilla.kernel.org/show_bug.cgi?id=209745, seen since 5.9, solved since 5.10.4, not sure if it has been backported yet. Updated topmost...

> Confirming. My XBES2 controller was suffering from the 20s delay on initial connect. Since updating to kernel v5.9.1, connection is now basically instantaneous. I can confirm the same for...

To all participants of this thread: Do you still see issues with kernel 5.10.4 or later?

Yes, it's important to pair the controller to a different machine and remove it from the Bluetooth stack. Otherwise one partner may fall back to a partially broken and old...