Bonding, Auto Connection, and App Disconnect Control

RE: Bonding, Auto Connection, and App Disconnect Control

Einar Thorsrud — Fri, 26 Feb 2016 07:14:18 GMT

You are probably not the only one. This is iOS behaviour. If you delete the peripheral from your iOS device, and connect via the nRF Toolbox app, you should see connection and disconnection function as expected. However, if you connect via iOS settings, you will see that iOS will automatically reconnect.

RE: Bonding, Auto Connection, and App Disconnect Control

MANGO — Fri, 26 Feb 2016 02:53:44 GMT

For instance, I merged HID keyboard and NUS together. I connected the peripheral with the nRF UART app.

Even though I press "Disconnect" from the NUS app and shows error number 0,

I still can send HID keyboard values to the phone.

What I want is that, when I press the "Disconnect" button of the nRF UART, MCP, or Toolbox App,

I want to make the bonded device to disconenct from HRS or HID together, not only the NUS.

Similar to this, the Toolbox app does not "completely" disconnects the peripheral.

Can you check this?

RE: Bonding, Auto Connection, and App Disconnect Control

MANGO — Fri, 26 Feb 2016 02:50:00 GMT

Thanks Einar. I have to take closer look about " Core Bluetooth Background Processing for iOS Apps".

About number 1, I check that, as you mentioned, the central sends LL_TERMINATE_IND PDU. I checked it with wireshark.

However, am I the only user observing that the picture above

(Bluetooth mark shown connected and settings menu still shows Norid_HRM)?

Even though the app has disconnected and doesn't receive any heart rate data,

the iOS still has connection as shown in the picture.

I want to make the central to totally disconnect.

What I mean is that the settings menus should display the Nordic_HRM as disconnected.

RE: Bonding, Auto Connection, and App Disconnect Control

Einar Thorsrud — Thu, 25 Feb 2016 13:16:27 GMT

In what way does disconnect not work well with HRM? Using a sniffer I can see that my iOS device with nRF Toolbox sends an LL_TERMINATE_IND PDU.
This is something that has to be implemented on the central side (iOS). You can implement this in your custom iOS app. Your app can scan for known peripherals and connect. This can be done as a background task. Refer to the Core Bluetooth Background Processing for iOS Apps chapter of the Core Bluetooth Programming Guide.