Christopher Schramm

It's true for Pop!_OS 22.04. Ubuntu Budgie is going to switch in 22.10, so if you tested with 22.04 it was pulseaudio. I still don't think that Linux Mint switched...

`bluetoothd[894]: src/device.c:search_cb() BC:14:85:D3:XX:XX: error updating services: Input/output error (5)` is currently the root cause here. The error code comes from the kernel side. We had similar issues in #158. Most...

Basically yes. What's interesting is the moment of when you're trying to connect to the device (e.g. ~Aug 22 01:36:14). I'm wondering about those error messages about already registered profiles....

To my understanding what you need to get aptX out of pulseaudio (there are alternatives like PipeWire) is pulseaudio 15 with built-in GStreamer support and GStreamer 1.20. If you want...

Interesting. PipeWire seems to go a different way there and add the codecs to the list of profiles. I guess it does not even have the messaging API that pulseaudio...

Ah, alright, so PipeWire copied the pulseaudio-modules-bt workaround. That makes sense, given the timeline (PipeWire implemented codec support much earlier than pulseaudio, so there was nothing else it could have...

To be fair: They did not. PipeWire implemented codec support before pulseaudio did.

They are called (in that order and as visible in the tooltip) _Received Signal Strength_, _Link Quality_ and _Transmit Power Level_ and often pointless standard values. See #1620 regarding concepts...

There are multiple levels of on / off state. Most probably this is about powering the adapter (running `bluetoothctl power on` should do the trick then). BlueZ has you covered...

What you're looking for is a killswitch, not the power state of the adapter. Killswitches are usually persistent and the system typically has one for Bluetooth. You can check the...