A BLE_GAP_EVT_DISCONNECTED event has occurred after pairing with my phone. & I can not pair with Android app.

RE: A BLE_GAP_EVT_DISCONNECTED event has occurred after pairing with my phone. & I can not pair with Android app.

Edvin — Tue, 31 Jul 2018 09:27:55 GMT

Hello,

The advertisement timeout is what triggers the BLE_ADV_EVT_IDLE event, and not the other way around. So the advertisement will time out even though you remove sleep_mode_enter();

If you want to keep advertising "forever", you must do the two following steps:

Near the top of main.c, you will find the "#define APP_ADV_DURATION 18000". Change this to "#define APP_ADV_DURATION 0"

Next, in advertising_init() in main.c, you must change the advdata flag:

init.advdata.flags = BLE_GAP_ADV_FLAGS_LE_ONLY_LIMITED_DISC_MODE;

init.advdata.flags = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;

Then it should not stop advertising.

Best regards,

Edvin

RE: A BLE_GAP_EVT_DISCONNECTED event has occurred after pairing with my phone. & I can not pair with Android app.

powerup — Sat, 21 Jul 2018 11:40:38 GMT

Hi.

I want to get rid of the 180 second ad timeout.

So I made the following changes.

static void on_adv_evt(ble_adv_evt_t ble_adv_evt)
{
    uint32_t err_code;

    switch (ble_adv_evt)
    {
        case BLE_ADV_EVT_FAST:
            err_code = bsp_indication_set(BSP_INDICATE_ADVERTISING);
            APP_ERROR_CHECK(err_code);
            break;
        case BLE_ADV_EVT_IDLE: 
            //sleep_mode_enter();
            break;
        default:
            break;
    }
}

However, after 180 seconds, nRF52832 will not enter sleep mode, but your ads will end.

What should I do to keep my ads going?

Thank you.

RE: A BLE_GAP_EVT_DISCONNECTED event has occurred after pairing with my phone. & I can not pair with Android app.

Edvin — Mon, 16 Jul 2018 14:06:39 GMT

Hello,

Regarding the BLE_GAP_EVT_DISCONNECT event, 180 seconds, and BLE_ADV_EVT_IDLE sequence, this is expected, as most of our examples have 180 seconds advertising timeout. If it isn't connected within this time, it will go to system off mode, to save power. It is possible to disable this, if you want to, so that the device will keep advertising.

Disconnection reason 0x13 is BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION (see the file ble_hci.h in the SDK).

It sounds like one of your devices (either phone or nRF) has stored the bonding information, while the other has not. Can you try to delete the bonding information on both of your devices? On the phone, this is usually done in the bluetooth settings. On the nRF, since you might haven't added the delete bond functionality in your application yet, the easiest way is to erase the DK/chip, reprogram the softdevice and your application, and try to bond again. If it succeeds, you can turn on and off your phone and nRF, and they should remember the bonding information.

Bonding is an optional step. You can read a short description on connection, pairing, bonding and whitelisting here.

If you are interrested, you can try the ble_app_hids_keyboard example from the SDK:

SDK\examples\ble_peripheral\ble_app_hids_keyboard\...

which will reconnect automatically after a power cycle on the nRF.

Best regards,

Edvin