Marijn Suijten

@gshpychka As per the above: Have you enabled BlueZ experimental features/interfaces?

@gshpychka Your best bet is to check and share _debug_ logs for both bluetoothd and pipewire right after connecting headphones. That usually gives some hints though I'm unfamiliar with PipeWire...

@gshpychka That sounds like `bluetoothd` wasn't properly restarted with `-E` (or `--experimental`) after all? You can check the status to see if it's indeed running with the desired flags: ```console...

@jamietanna Is PulseAudio or PipeWire running, and built from recent enough source to report this battery level to BlueZ in the first place? Perhaps their logs might clarify what is...

@jamietanna As [mentioned above](https://github.com/TheWeirdDev/Bluetooth_Headset_Battery_Level/issues/43#issuecomment-860492265) PulseAudio must be built with [this MR](https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/482) in order to have the feature; it'll only land in 16.0 which should ~be out~ go into feature freeze...

> * Regarding the difference between NV and KHR variants, I suggest doing only KHR first, and adding NV in a separate PR later. While I don't think Vulkano has...

https://github.com/gtk-rs/gir/pull/991 Modifies the current assumption about all `to_string` functions never returning null, that should be revisited when nullability can be trusted in both gtk and gstreamer.

@sdroege Are the examples in a different crate? Might need to add `--all`/`--workspace` too so that it builds all examples (`all-targets`) for every crate :)

Filling up this incomplete report: 1. This change was made in #292; 2. This behaviour was implied because of the implementation in https://cs.android.com/android/platform/superproject/+/master:frameworks/base/native/android/input.cpp;l=324;drc=3da1d20bcfb103f146ff67910d14b7b40f6f686f?q=AInputQueue_preDispatchEvent (why did "Quest 2" change system code?);...

For the record android-ndk-rs doesn't generate anything besides AndroidManifest.xml. The rest is C bindings (and safe wrappers) around the NDK, toolchain discovery and setting up the compiler/linker to target Android....