nRF Connect for Mobile (Android) Bluetooth 5.0 scan

[Lorenzo]

Hi everybody,

we're testing our device with nRF52840 and full Bluetooth 5.0 by sending some packets over coded PHY and receiving them via nRF Connect for Mobile on an Android smartphone (Huawei Mate 20).

We've noticed that the "advertising interval" detected by nRF Connect is much higher (sometimes even around 1 second) than the one set on the actual FW (250 ms).

Is this happening because the app is "switching" the physical support (1M/2M to coded and vice-versa) while scanning?

If yes, can you please confirm that this "switching" has to be implemented on FW side as well in order to receive both packets on 1M/2M PHY and packets on coded PHY?

Thank you!

[AndreasF]

Hi.

Sorry for the late reply.

I've talked to the development team about this, but the guy who's in charge of this Application is out of office this week.

I will come back to you as soon as I know something, if this is ok :-)

Best regards,

Andreas

[Lorenzo]

Thanks Andreas, 

I'll wait ;)

[AndreasF]

Hi again.

The developer is out of office this week as well, I have sent him an email and I'm waiting on a reply.

Best regards,

Andreas

[AndreasF]

Hi again.

Got an email from the developer:

Unknown said:

The nRF Connect app isn't switching anything. If anything, the phone may by doing some behind the screens logic, to scan on multiple channels and phys.
The app is just using standard Android API. It starts scanning and saves a timestamp of each packet received. Based on those it estimates the scanning interval. They can open device details (scan for some time, expand a device row and click MORE button). You'll have all the timestamps there with interval between each two.

Hope this helps you.

Best regards,

Andreas

[Lorenzo]

Thanks!