Hi,
we are developing a single-link peripheral using nrf52840, which uses bonding and whitelisting. We have an app on both android and ios.
We have stumbled on an odd problem: sometimes, on some android phones, the auto-connection simply does not work.
When this happens, we've tried auto-connecting the the nRF Connect app as well, without success.
Active connect does work, from both our own app and nRF Connect.
When sniffing the bluetooth data using the nrf52840 dongle, one can see that our peripheral is successfully advertising: we have the expected ADV_IND packets, and the General Discoverable bit is 0 as we are using the white list. However, there are no CONNECT_INDs from the app at all.
When performing an active connection from the app, CONNECT_IND turns up from a random resolvable private address and the connection is performed successfully. From that we conclude that the peer manager data and IRKs and all that is correct.
I am wondering if you have seen this before, or have any other tips that could help us track this down? To me it is fairly obvious that this is not a firmware problem but a specific android thing, which we probably would have to work around.
Thanks! / Peter
