Reconnect failure Android 9, sd132, SDK16

RE: Reconnect failure Android 9, sd132, SDK16

Sigurd — Mon, 25 Jan 2021 09:16:06 GMT

[quote user="dr9"]It might take me a couple days to get a sniffer trace.[/quote]

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).

RE: Reconnect failure Android 9, sd132, SDK16

dr9 — Fri, 22 Jan 2021 16:48:20 GMT

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:

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

Thanks,

RE: Reconnect failure Android 9, sd132, SDK16

Sigurd — Fri, 22 Jan 2021 12:39:23 GMT

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