Christopher Schramm

According to https://wiki.ubuntuusers.de/sources.list/#Jammy everything should be in place and, as I said, you just need to uncomment. Otherwise just duplicate the main deb URI as a deb-src URI. Remember that...

https://git.kernel.org/cgit/bluetooth/bluez.git/tree/doc/gatt-api.txt

@lcorsini: Are you sure that object actually exists? Should be in `gdbus call -y -o / -d org.bluez -m org.freedesktop.DBus.ObjectManager.GetManagedObjects` then.

You're trying to use `char000c` but introspecting `char001c`.

Trying to wrap my head around this with the current status quo. I think there are three levels of disabling a Bluetooth adapter: Kernel driver, rfkill and BlueZ power state....

I just had issue with my adapter not responding and successfully fixed it with `fcntl.ioctl(open("/dev/bus/usb/003/008", "w"), ord('U')

`ord('U')

> I currently have no straightforward idea how to get to an adapter's device file. This is a blocker. Ideas welcome. To illustrate: When we know about an adapter, we...

Lol, you're right, blueman-manager provides a way. :sweat_smile:

This is out of blueman's scope and sounds like an issue with pulseaudio. I personally cannot provide any help here, sorry.