Possible false scan requests.

RE: Possible false scan requests.

MartinBL — Fri, 31 Aug 2018 09:16:01 GMT

Hi,

I'm not sure I understand how it could be a bug in the Softdevice causing this. Anyway, I suppose a sniffer trace would could be useful. It would show exactly what advertising packet (and its content) the mobile responds to. If you have an extra Nordic dev kit to spare you can use our nRF Bluetooth Sniffer solution.

RE: Possible false scan requests.

Al Bundy — Fri, 24 Aug 2018 13:16:19 GMT

I know that's why I want to use Scan Request as an acknowledgement.

My beacon advertises with 4 seconds interval. If I get Scan Request I change the data and ADV with new data takes places 4 seconds later. I think that should be enough for mobile BLE stack to deliver data to my application.

RE: Possible false scan requests.

MartinBL — Fri, 24 Aug 2018 12:21:26 GMT

Hi,

The APIs in Android doesn't necessarily deliver each and every advertising event to your application instantly. It can be configured to deliver a batch of advertising reports every other second for example. In other words, it is not certain that the advertising event that the mobile is replying to is delivered to your application immediately. If, for example, during 2 seconds of scanning your phone receives 20 advertising packets from 4 different devices, it will pick one packet from each of the four devices and deliver only those. I'm not sure what happens if the content of your advertising packet changes while your phone collects advertising reports. Could this be relevant to your problem?

Also remember that there is no guarantee that your phone receives 100 % of the packets.