Bluetooth init procedure with BT_SETTINGS is not reliable #14833

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.

Sign up for GitHub

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

Jump to bottom

Closed

jhedberg opened this issue Mar 22, 2019 · 0 comments · Fixed by #14834

Assignees

Labels

area: Bluetooth bug priority: medium

Milestone

Member

jhedberg commented Mar 22, 2019 •

edited

Loading

There are several issues with the current init procedure and BT_SETTINGS, which have become apparent from several independent developer reports:

It is not clear enough that the application needs to call settings_load()
The stack could potentially try to start passive scanning in central role even when it doesn't (yet) have an identity address
Several APIs are missing appropriate checks for the BT_DEV_READY flag

The text was updated successfully, but these errors were encountered:

jhedberg added bug priority: medium area: Bluetooth labels

jhedberg added this to the v1.14.0 milestone

jhedberg self-assigned this

jhedberg mentioned this issue

Bluetooth: Fix several issues related to initialization with BT_SETTINGS #14834

Merged

jhedberg closed this as completed in #14834

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment