Peer Manager disconnect after connection with NRF52 and Android 7.0

RE: Peer Manager disconnect after connection with NRF52 and Android 7.0

Greg Nowak — Fri, 28 Jul 2017 18:19:22 GMT

Nick, I started with the "ble_app_template" project (examples\ble_peripheral\ble_app_template). That uses "peer manager". I look at that as a starting place and merged that into my Nordic Uart Service application, since my application is a single peripheral connected to a single central device and talking over the Nordic Uart Service.

RE: Peer Manager disconnect after connection with NRF52 and Android 7.0

Nick Bentzen — Fri, 28 Jul 2017 17:59:46 GMT

Greg, what do you mean by the Template? I am struggling to finish a very similar application (peripheral connects to one central, whitelists it and then only talks to that one device unless the user chooses to attach it to a new central). I have tried adapting the peer management code from the examples but find it confusing, and it also doesn't work.

RE: Peer Manager disconnect after connection with NRF52 and Android 7.0

Greg Nowak — Thu, 20 Jul 2017 15:15:28 GMT

I'm not sure why, but the nRF Connect App works perfectly, including the Bonding. It must just be the generic Android Bluetooth interface (Bluetooth -> click on Device -> click "pair") doesn't work. Looks like I'll just use the nRF Connect App for now!
Thanks!

RE: Peer Manager disconnect after connection with NRF52 and Android 7.0

Petter Myhre — Thu, 20 Jul 2017 14:22:46 GMT

I see. Sounds like a cache problem. Delete unknown paired devices from the list, restart the smart phone, restart Bluetooth, and delete bond information on the nrf as well. Also try to connect with nRF Connect app instead.

RE: Peer Manager disconnect after connection with NRF52 and Android 7.0

Greg Nowak — Thu, 20 Jul 2017 14:02:38 GMT

In the HCI Log i'm getting a successful connection, pairing, encryption, etc... but I'm getting "Bluetooth Attribute Protocol error, Attribute Not Found for Nordic Uart Service (blah blah)" I'm using the generic application on my phone to do the pairing, not something that that would support the Nordic Uart Service. Shouldn't Android simply be able to bond with the device and show me the services it found?

RE: Peer Manager disconnect after connection with NRF52 and Android 7.0

Greg Nowak — Thu, 20 Jul 2017 13:18:53 GMT

I'm using SDK 13.0.0 with s132 nrf52 4.0.3 Soft Device. Unfortunately there is too much proprietary firmware in my project at the moment for me to share the complete project. I'll see if I can get the HCI dump from my phone and see if it gives me any more hints.

RE: Peer Manager disconnect after connection with NRF52 and Android 7.0

Petter Myhre — Thu, 20 Jul 2017 08:32:55 GMT

Seems like the phone for some reason disconnects. Could you provide a sniffer trace? Or maybe you can upload your complete project so I can test it here? Which SDK and SoftDevice version are you using?