While migrating a project from version 0.8.0 to 0.9.0, I noticed a change in the behavior of advertisement functionality on the Linux platform.
In version 0.8.0, sample projects functioned seamlessly, but in 0.9.0, I encountered issues on the hardware I was using. Specifically, I received the following error message:
panic: Failed to start advertisement: bluetooth: could not start advertisement: Failed to register advertisement
Upon investigation, I found that the default scanning mode for hci0 after reboot was set to PSCAN mode only. In version 0.8.0, the scanning mode could be set to PSCAN ISCAN when starting the advertisement. However, in version 0.9.0, this behavior no longer occurs, resulting in the failure to register the advertisement.
Manually setting the correct scanning mode resolves the issue: hciconfig -a hci0 piscan.
My question is whether this is something that should be addressed manually before using the library, or if it constitutes unexpected behavior.
While migrating a project from version 0.8.0 to 0.9.0, I noticed a change in the behavior of advertisement functionality on the Linux platform.
In version 0.8.0, sample projects functioned seamlessly, but in 0.9.0, I encountered issues on the hardware I was using. Specifically, I received the following error message:
Upon investigation, I found that the default scanning mode for
hci0
after reboot was set toPSCAN
mode only. In version 0.8.0, the scanning mode could be set toPSCAN ISCAN
when starting the advertisement. However, in version 0.9.0, this behavior no longer occurs, resulting in the failure to register the advertisement.Manually setting the correct scanning mode resolves the issue:
hciconfig -a hci0 piscan
.My question is whether this is something that should be addressed manually before using the library, or if it constitutes unexpected behavior.
For reference, here are the
Bluetoothd
logs:0.8.0
0.9.0