You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any advantage to using scan periods on devices that invoke callbacks for every advertisement? That is to say, if I'm not worried about power consumption. I've noticed the stack getting into an error state (can't find callback) and beacons are not getting discovered so I figure less frequently we toggle start/stop scanning less likely to encounter issues.
For example, Android Things on Intel Edison, the stack provides every callback. Technically, per Android API you can tell the stack you want all callbacks in your ScanSettings, but having developed with Android Bluetooth for a while I've learned better. It's the wild west and observed behavior frequently contradicts documentation official.
The text was updated successfully, but these errors were encountered:
Is there any advantage to using scan periods on devices that invoke callbacks for every advertisement? That is to say, if I'm not worried about power consumption. I've noticed the stack getting into an error state (can't find callback) and beacons are not getting discovered so I figure less frequently we toggle start/stop scanning less likely to encounter issues.
For example, Android Things on Intel Edison, the stack provides every callback. Technically, per Android API you can tell the stack you want all callbacks in your ScanSettings, but having developed with Android Bluetooth for a while I've learned better. It's the wild west and observed behavior frequently contradicts documentation official.
The text was updated successfully, but these errors were encountered: