Reconnect failure Android 9, sd132, SDK16

[dr9]

Hi,

I've come across a situation where when paired to Android 9 devices, the reconnect event that follows waking the peripheral fails.  Connection parameters are

#define MIN_CONN_INTERVAL                   MSEC_TO_UNITS(7.5, UNIT_1_25_MS)           /**< Minimum connection interval (7.5 ms) */
#define MAX_CONN_INTERVAL                   MSEC_TO_UNITS(30, UNIT_1_25_MS)            /**< Maximum connection interval (30 ms). */
#define SLAVE_LATENCY                       6                                          /**< Slave latency. */
#define CONN_SUP_TIMEOUT                    MSEC_TO_UNITS(430, UNIT_10_MS)             /**< Connection supervisory timeout (430 ms). */

The application is based on the BLE Keyboard example in SDK 16.

Behavior with iOS devices is fine, as well as with Android 10 and 11.  I've come across threads addressing this for older versions of Android, but not this particular combination.

Thanks

[Sigurd]

Hi,

What type of Android 9 device is this? model? brand?

Do you have a sniffer log that shows the issue ?

https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Sniffer-for-Bluetooth-LE

[dr9]

Sigurd,

Its on Samsung S9 and S9+ phones.  I don't have the central in front of me; the issue is being reported by a colleague who is helping test the functionality on other platforms.  It might take me a couple days to get a sniffer trace.

If the device lists are cleared on both central and peripheral, the peripheral has no problem connecting, pairing and functioning as expected.  After a period of inactivity, the app puts the peripheral to sleep.  When woken up, the peripheral attempts to reestablish the connection to the central, but is unsuccessful. 

In digging through the devzone, I have come across a couple of other tickets regarding Samsung centrals that all appear similar in nature, but don't offer a resolution that I can apply to my situation:

• https://devzone.nordicsemi.com/f/nordic-q-a/66107/samsung-a-series-not-detecting-nrf52832
• https://devzone.nordicsemi.com/f/nordic-q-a/53914/pairing-issue-0x3d-mic-failure-error/218460#218460
• https://devzone.nordicsemi.com/f/nordic-q-a/34623/unable-to-reconnect-after-disconnection-in-samsung-devices

If it makes a difference, I'm using the internal RC oscillator and SoftDevice s132 v7.0.1

Thanks,

[Sigurd]

dr9 said:

It might take me a couple days to get a sniffer trace.

 Ok, let me know when you have the log, and I will take a look at it. It will also be useful to get logs from the phone( e.g. by using nRF Conenct for mobile app), and logs from the nRF5 device(output from nrf_log, e.g. logs from peer manger, disconnect reasons, etc).