Pauli Virtanen

One way to reproduce seems to be to run the stack in qemu and forward the AX210 USB device there. This setup appears susceptible to delays in the USB subsystem,...

Still observed with `Firmware Version: 88-13.25`, `Firmware timestamp 2025.13 buildtype 1 build 82008`

Try to get logs that are not truncated to 80 columns. Usual cause for A2DP connection looking ok in btmon but not appering as sound output, is that you are...

> Pipewire ver: 1.2.3 > Pipewire ver: 1.0.5 Pipewire 1.0 used to have two SBC endpoints (with different capabilities). Pipewire 1.2 has only one, to keep the endpoint count low...

If this failure is not due to an Apple Accelerate bug, and a reproducible test case is found, probably can be forwarded to Arpack maintainers: https://github.com/opencollab/arpack-ng/issues

Trusted devices are allowed to do things like connect and use bluetooth services exposed by the local host, without requiring explicit confirmation from user (technically the confirmations go through org.bluez.Agent1...

No, I'm saying trusting generally allows the device to use local services (without going through org.bluez.Agent1), and that according to the snippet quoted above also whether the remote device is...

BlueZ asks for authorization when connecting services (apparently, for some services like a2dp it does ask, but this is not done in all of the services), trusted means it will...

> arrays with large enough numbers in them, it just stops working for some reason Please give an example (ie. Python code that prints stuff the wrong way), so that...

It probably worked before if sound server exposes multiple endpoints, eg. different codecs, and pipewire earlier used to expose different SBC configurations as separate endpoints, nowadays it's just one ep...