So I suspect there is a very simple answer to this, but a couple days of much reading and searching haven't led me to a very clear answer.
My setup: Galaxy S3 (Android 5.1.1) and nRF52 with S132 and a few things added to the BLE Template in the SDK examples to light up LEDs. The behavior described below happens with all examples in the SDK.
My Goal: I want the BLE device, in this case a smartphone, to connect to the nRF52 and then have the nRF52 monitor the RSSI of the connection, collect data on it, and light up some LEDs when the distance between the devices changes. The Proximity Profile doesn't quite provide all the functionality I'd like, so I plan to just write my own.
The Problem: Using Master Control Panel, the phone connects just fine with the nRF52 and behaves the way I'd expect (LEDs lighting up when I move toward or away from), but when I try to connect without MCP and just use the Android "Settings" menu, the device successfully pairs and then disconnects a few seconds later and the nRF52 starts advertising again. I am not sure which side is issuing the disconnect but I suspect it is the phone. I have also tried connecting to the nRF52 with my PC (Windows 8.1) and it also disconnects a few seconds after successfully pairing.
I think what is going on here is that the phone or PC is successfully pairing with the device, but after a few seconds realizes there is nothing to talk about so it disconnects, a timeout. I figure this means I just have to write some software for the android to manage the connection to keep it open.
Any other explanation as to what is going on or other solutions? The ideal would of course to not have to write an android program since all I want to do is monitor the RSSI, but I'm thinking I may have to.
