To support this feature, the IHV’s Bluetooth controller or an IHV driver shall support these commands.
The hardware vendor here is probably the one who produced your combo Wi-Fi/Bluetooth PCIe card, which is certainly not Framework or AMD…
(It is unlikely that you will see much feedback on this issue, as it seems rather specific to a certain kind of only-unofficially-supported PCIe device.)
Thanks - I think the issue occurs not just because the QC driver doesn’t support HW offload but because the FW16 firmware never turns off the HW offload when the new HW isn’t configure for it.
Cut & Paste from my issue:
Why I think this happens: as I understand it, AMD’s BT Audio Offload is a platform feature — the audio coprocessor takes the Bluetooth stream directly rather than encoding A2DP on the CPU, to save power. That path is configured for the radio the OEM validated and shipped. Swap in a Qualcomm card and the offload path is still enabled, still expecting a radio that speaks its handoff protocol, and the Qualcomm doesn’t. Both drivers are arguably behaving correctly for hardware that isn’t present; the stream goes into the offload path and evaporates. Happy to be corrected on the mechanism — that’s inferred from the symptoms and the fix, not something I can verify from the outside.
The reason I’m asking Framework is that I know for certain that QC won’t give a rats about fixing this unless a big OEM asks but I’m hoping that Framework might be able to make a change to turn it off when they don’t detect supported HW.