Softdevice crashes/disappears after connection speed test

[schef]

Hi guys, i was testing the connection speed from android in conjunction with advertisement time to see what will work better in my production code.

The result were:

• ~3s on 100ms adv time
• ~7s on 300ms adv time

I have some other sensor readings, adc, flash and timer. I was monitoring firmware status over RTT and what happend was:

after 100 connections the device was unvisible but the code on RTT side was further executing. No reboot or any sign of crash.

This happend multiple times. Do you have any suggestions? Is there somekind of watchdog for Softdevice? Or am i totaly looking at the wrong rabbits hole?

Thanks

[FormerMember]

From what I understand, you are measuring the time it takes to connect when a device is advertising.

1) The longer a connection interval is, the longer time it will take for a scanner to pick up the signals. Especially if the scanner is not scanning continuously. It is hard to know if Android is scanning continuously. To create a continuous scanner, you can for example use pc-ble-driver.

2) How does the production code work? Does it disconnect immediately after a connect? And after 100 connections, the devices stop to advertise?

[FormerMember]

I need to summarize what I have understood:

• The problems happens when android phone connects and disconnects but nRF52 doesn't get the disconnect event: In this case there should be a BLE_GAP_EVT_TIMEOUT event in the nRF52. Could you double check the behavior using our sniffer?
• Airplane mode works also but not disable bluetooth: Does the problem not occur when using airplane mode with Bluetooth enabled?
• It disconnects 7 seconds right after turning airplane mode on. It looks like normal disconnect event: In this case the nRF52 should understand that there has been a disconnect through the BLE_GAP_EVT_TIMEOUT event.