New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
offload support failed #286
Comments
I'm still assuming this was caused by the upgrade of bluez. I managed to get it working to downgrade my system (which was in need of an updated), the know good versions:
|
I was encountering the same issue (this message being spammmed + BT audio not working at all). Just downgrading the kernel to the version you mentioned restored audio even when keeping pipewire and bluez-git (19448b9) at latest. It's still spamming |
With the older kernel and older bluez I still had the profile issue though? I might try to upgrade everything but the kernel to see if it is still functional after that the coming week. |
I just tried this with my old laptop. did a full update:
|
mainly after starting the blueberry. The error is still coming from bluetoothd, so I think it's still an issue within bluez rather then blueberry. |
Can confirm: after updating kernel to |
If advertising manager is not enabled don't log any error on btd_adapter_update_found_device, also change btd_adv_monitor_offload_supported to btd_adv_monitor_offload_enabled since that is checking if the features has been enabled rather than it is just supported. Fixes: bluez#286
If advertising manager is not enabled don't log any error on btd_adapter_update_found_device, also change btd_adv_monitor_offload_supported to btd_adv_monitor_offload_enabled since that is checking if the features has been enabled rather than it is just supported. Fixes: bluez#286
If advertising manager is not enabled don't log any error on btd_adapter_update_found_device, also change btd_adv_monitor_offload_supported to btd_adv_monitor_offload_enabled since that is checking if the features has been enabled rather than it is just supported. Fixes: bluez/bluez#286
If advertising manager is not enabled don't log any error on btd_adapter_update_found_device, also change btd_adv_monitor_offload_supported to btd_adv_monitor_offload_enabled since that is checking if the features has been enabled rather than it is just supported. Fixes: bluez/bluez#286
If advertising manager is not enabled don't log any error on btd_adapter_update_found_device, also change btd_adv_monitor_offload_supported to btd_adv_monitor_offload_enabled since that is checking if the features has been enabled rather than it is just supported. Fixes: bluez/bluez#286
If advertising manager is not enabled don't log any error on btd_adapter_update_found_device, also change btd_adv_monitor_offload_supported to btd_adv_monitor_offload_enabled since that is checking if the features has been enabled rather than it is just supported. Fixes: bluez#286
If advertising manager is not enabled don't log any error on btd_adapter_update_found_device, also change btd_adv_monitor_offload_supported to btd_adv_monitor_offload_enabled since that is checking if the features has been enabled rather than it is just supported. Fixes: bluez/bluez#286
I have updated bluez recently, and this caused constant disconnect/connect cycles. After trying to resolve this I have no working bluetooth at all. Connections just fail
This might be the main issue, as this is constantly being logged while connecting:
src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Eventually:
Versions:
I tried completely removing the device and reconnecting as well.
After downgrading to 5.60-1 the error was gone, but now I'm back at missing a2dp profiles.
The text was updated successfully, but these errors were encountered: