BLE advertising data flags field and discovery

RE: BLE advertising data flags field and discovery

run_ar — Mon, 21 Aug 2017 13:07:14 GMT

I think these flags is meant as a help to the scanner to see which advertisements to prioritize. Basically all advertisements are visible to all scanners. But the scanners can assume that:

if the Limited discoverable mode is used the device will only advertise for a limited amount of time. e.g. the user has put the device in bondable mode or some other time limited mode.
If a scanner sees a "non discoverable" advertisement it can assume this device uses a whitelist or for some other reason is not connectable. So it can save power by not trying to connect.
But I'm afraid the behavior will depend on the implementation, as it's up to the developer to use these flags correctly. Unless you are implementing a sig define profile with given requirements for flags.

Regardless I don't think there is anything wrong with Android or iOS when allowing you to connect to these devices. Hopefully the flags is forwarded to the application (looks like both Android and iOS forwards a string with the content of the ad packet), so the application can choose what to do.

Not sure why you are talking about service discovery. That seems unrelated to me, and should be performed after connecting, at least when connecting to an unknown device.

RE: BLE advertising data flags field and discovery

Eliot Stock — Sat, 19 Aug 2017 15:14:33 GMT

Yes, it's related, but deserved a more general question. No, it's not just Android. iOS will also happily do service discovery even without the discoverability bit set in the flag byte. No, you're right, on closer inspection and a bit more testing, there's no reason for me not to just use BLE_GAP_ADV_FLAGS_LE_ONLY_LIMITED_DISC_MODE since that more correctly my intentions. But I'm asking because I want to understand the behaviour of the iOS and Android BLE stacks here, not just what the spec says.

RE: BLE advertising data flags field and discovery

RK — Sat, 19 Aug 2017 12:48:10 GMT

Does this go back to your thread from a few weeks ago you left unanswered after Hung Bui and I replied to it?

That byte doesn't mix two concepts, it expresses two concepts in different bits of a single byte because data is precious.

If you set no discoverability flags the peripheral is not supposed to be discoverable. If Android is broken enough to try discovering it then that's just Android. If (as in your previous thread) you're finding you get a connection attempt but no discovery, perhaps Android is only half broken and if it connects and discovers and the device responds, a lot of things are broken.

Is there a reason you don't just set the discoverability flags which represent your actual discoverability status. If that doesn't work, that's bad.

And the difference between general and limited discovery is that limited is like shouting loudly so you are seen first but can only be done for a short time.