• State Verified Answer
  • Replies 14 replies
  • Subscribers 62 subscribers
  • Views 8214 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 118170
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

No disconnect event after bond on Android

Mindaugas

Hello,

To reproduce this problem I use these steps:

  1. Bond to NRF51822 using Android 6.0.1 and latest nRF Connect version;
  2. After successful bond, connect to NRF51822;
  3. Use "DISCONNECT" button in nRF Connect application;

After these steps my application does not get BLE_GAP_EVT_DISCONNECTED event. As a consequence it does not advertise.

I am using custom board with NRF51822, S130 v2.0.1, SDK v12.1.0. My application has a custom profile. Note: problem is also reproducible with ble_app_hrs_freertos example.

Some insights:

  1. If I repeat connect/disconnect action from nRF Connect for few times I eventually get BLE_GAP_EVT_DISCONNECTED with reason BLE_HCI_LOCAL_HOST_TERMINATED_CONNECTION. After that I get disconnect events in application on every disconnect from android.
  2. If I turn off bluetooth on mobile phone or reset NRF51822 after bond, I receive disconnect event later on;
  3. This behaviour does not reproduce with S110 and SDK v10;
  4. This behavior does not reproduce with android version 5.0;
Parents
  • 0

    Hi, as far as I know the first disconnection after Edit: OOB (Out Of Band) bonding will not work when Disconnect sent from the Android side. After reconnecting it should work properly every time.

    The fix for that is already on AOSP but will not be included in N release. I'll try to get a link to a commit. Edit: found it: android-review.googlesource.com/

    Disconnecting after pairing from Settings should work normally, but as you see above some phones may have problems (however, I have never had such issue).

    As a workaround you would have to disconnect from the peripheral side, perhaps just after bonding? After that phone could connect again.

Reply
  • 0

    Hi, as far as I know the first disconnection after Edit: OOB (Out Of Band) bonding will not work when Disconnect sent from the Android side. After reconnecting it should work properly every time.

    The fix for that is already on AOSP but will not be included in N release. I'll try to get a link to a commit. Edit: found it: android-review.googlesource.com/

    Disconnecting after pairing from Settings should work normally, but as you see above some phones may have problems (however, I have never had such issue).

    As a workaround you would have to disconnect from the peripheral side, perhaps just after bonding? After that phone could connect again.

Children
Related