Christopher Schramm

That could be a bug then. blueman-manager should only show devices bound to powered adapters. Please provide the basic information we ask for in the issue template and the output...

The blueman-manager log looks like BlueZ does not remove the devices and adapter. I'd expect that if no killswitch gets enabled. However, blueman-applet's Killswitch plugin should do exactly that. Unless...

Your system seems to behave differently than mine there. blueman does seem to set the killswitch states as expected, but BlueZ does not seem to remove the adapter. Quick cross-check:...

Got it. It's not the Bluetooth stack that removes the adapter for me but the driver or whatever. When I soft-block Bluetooth (`tpacpi_bluetooth_sw` in my case), I can see the...

I'm on 5.64 as well. To my understanding it's the ACPI hardward / thinkpad_acpi driver that physically unpowers the integrated adapter when `tpacpi_bluetooth_sw` gets blocked.

@birdie-github: Capable of what? Switching devices? It has `module-switch-on-connect` to switch the default device to a newly added one, yes.

blueman 2.2 supports the LE Battery Service. Your device might not provide one but instead provide battery information via the audio profiles. That is supported by recent versions of audio...

https://github.com/blueman-project/blueman/releases/tag/2.3.beta1 A debian package is only at mentors yet. You can build a binary package if you like. In short, something like: ``` apt-get build-dep blueman dget -u https://mentors.debian.net/debian/pool/main/b/blueman/blueman_2.3~beta1-1.dsc cd...

Does not seem like you did something like `apt-get build-dep blueman` from my snippet.

So you need to put (probably just uncomment) some deb-src URIs in your sources.list first.