Noble bluetooth issues

[jojumaxx]

I have experienced issues on my Quintus:

The bluetooth gui does not see my headsets when searching for devices. But I can directly pair them using bluetoothctl and their hardware identifier.
After having done this, they seem to stay saved in the list of paired devices, since they auto connect from then on.
Yet, the quintus does never show the headsets in the GUI (one are Volla buds, the other is no name).
The Pinetime in contrary works without issues and is always visible in the list.

I can't remember having these issues before which makes me think that is connected to Noble.
My phone is running UT natively, no dual boot.

Maybe this can be added to observations made on Noble that might be addresed at some point.

[PhAndersson]

@jojumaxx I have a similar issue, maybe not absolutely identical:

I had to fiddle a lot to get my new Volla Quintus paired with my Linux laptop (tried several times, turned BT on and off on the phone), then eventually they accepted to pair.

Now, a few days later, the laptop is still listed as a paired device, but I can't get the phone to reconnect to it (I've not activated the auto-connect feature as that's not desired). I haven't tried bluetoothctl either, but I'll do and report back.

The Quintus is on 24.04-1.3, also no dual boot.

[PhAndersson]

I tried connecting the phone to the laptop using bluetoothctl: same outcome (it fails).

The laptop (kermit) is still considered a paired device:

[bluetooth]# devices Paired
Device xx:xx:xx:xx:xx:xx kermit

Attempting to connect to it yields the following error message after a while:

[bluetooth]# Failed to connect: org.bluez.Error.Failed le-connection-abort-by-local

'journal' doesn't seem to contain any further information.