Pairing pop-up appears twice on Android using the HRS example

RE: Pairing pop-up appears twice on Android using the HRS example

Kazi Afroza Sultana — Wed, 14 Jun 2023 13:53:52 GMT

Have you found the popping up message twice issue after implementing this?

RE: Pairing pop-up appears twice on Android using the HRS example

Marten — Mon, 12 Jun 2023 12:06:10 GMT

Hi,

Thanks for looking into this issue. Glad you can reproduce the issue.

To be clear, the issue is that there are 2 pop-up messages (when bonding for the first time).

This is an issue, there should only be 1 pop-up message, not twice the same.

RE: Pairing pop-up appears twice on Android using the HRS example

Kazi Afroza Sultana — Mon, 12 Jun 2023 12:01:00 GMT

Hello,

I can not see anything different what I said before. When trying to pair the central and peripheral first time, the pairing message pops up twice. Later, while doing the same process from the beginning, there is no message popped up. It gets bonded connection.

RE: Pairing pop-up appears twice on Android using the HRS example

Marten — Mon, 22 May 2023 11:14:02 GMT

Here the content of nRF5_SDK_17.1.0_ddde560\examples\ble_peripheral\ble_app_hrs.

As said, I did not change the code, the hex file from the example in the sdk also has the issue(ble_app_hrs_pca10040_s132.hex).
You can download it from https://www.nordicsemi.com/Products/Development-software/nRF5-SDK/Download#infotabs and select sdk 17.1.0.
devzone.nordicsemi.com/.../4721.ble_5F00_app_5F00_hrs.zip

RE: Pairing pop-up appears twice on Android using the HRS example

Kazi Afroza Sultana — Tue, 16 May 2023 18:04:29 GMT

Can you please send us the example folder so I can try to look at thoroughly and reproduce the issue?

RE: Pairing pop-up appears twice on Android using the HRS example

Marten — Tue, 16 May 2023 12:33:55 GMT

Hi,

Thanks for looking into this issue. However I was unable to fix the issue.

Small note, the code above does not compile, the pm_handler_secure_on_connection() has to be added in ble_evt_handler(), it needs a ble_evt_t* type, so not in pm_evt_handler().
So I added pm_handler_secure_on_connection in ble_evt_handler() and removed pm_conn_secure, as it was already done in other examples (ble_app_bms) and set the delay to 200ms, but no change.

I also changed all the characteristics securities to SEC_JUST_WORKS, again no change.
As test I increased the delay to 10000ms, again 2 pop-ups, only it takes 10s to get the first.

RE: Pairing pop-up appears twice on Android using the HRS example

Kazi Afroza Sultana — Mon, 15 May 2023 14:16:21 GMT

Hello,

We have few suggestion.

In pm_evt_handler(), you need to add pm_handler_secure_on_connection(p_evt)

static void pm_evt_handler(pm_evt_t const * p_evt)
{
    pm_handler_on_pm_evt(p_evt);
    pm_handler_disconnect_on_sec_failure(p_evt);
    pm_handler_flash_clean(p_evt);
    pm_handler_secure_on_connection(p_evt);

    switch (p_evt->evt_id)
    {
        case PM_EVT_PEERS_DELETE_SUCCEEDED:
            advertising_start(false);
            break;

        default:
            break;
    }
}

and set PM_HANDLER_SEC_DELAY_MS in sdk_config.h for example 200.

and remove call to pm_conn_secure() in ble_evt_handler()

static void ble_evt_handler(ble_evt_t const * p_ble_evt, void * p_context)
{
    ret_code_t err_code;

    switch (p_ble_evt->header.evt_id)
    {
        case BLE_GAP_EVT_CONNECTED:
            NRF_LOG_INFO("Connected.");
            err_code = bsp_indication_set(BSP_INDICATE_CONNECTED);
            APP_ERROR_CHECK(err_code);
            m_conn_handle = p_ble_evt->evt.gap_evt.conn_handle;
            err_code = nrf_ble_qwr_conn_handle_assign(&m_qwr, m_conn_handle);
            APP_ERROR_CHECK(err_code);
            
            if (err_code != NRF_ERROR_BUSY)
            {
                APP_ERROR_CHECK(err_code);
            }
            break;
            ...
    }
    
    ...
    
}

This will add a delay before starting security.

If this does not work, you can try workaround here in this case https://devzone.nordicsemi.com/f/nordic-q-a/81227/android-pairing-pop-up-appears-twice/344424, setting characteristics read and write access to ''SEC_JUST_WORKS''.

Another report here that the delay does not work, https://devzone.nordicsemi.com/f/nordic-q-a/77116/double-pairing-request-with-android you can look at.

RE: Pairing pop-up appears twice on Android using the HRS example

Marten — Tue, 02 May 2023 16:03:11 GMT

Hi,

No, as said, the issue can be reproduced with ble_app_hrs, there just works is being used.

Also io capabilities is set to BLE_GAP_IO_CAPS_NONE.

So the 2 pop-ups are the same.

RE: Pairing pop-up appears twice on Android using the HRS example

Kazi Afroza Sultana — Tue, 02 May 2023 15:55:56 GMT

Hello Marten,

In principle, it is possible to pair/bond several times if there is a need to increase the security level.

Do you need to enter a pass key or do numeric comparison or similar on the second attempt? or could it be like first pairing and then bonding?

RE: Pairing pop-up appears twice on Android using the HRS example

Marten — Thu, 27 Apr 2023 15:38:01 GMT

Hi Kazi,

Could you reproduce the issue of the 2 pop-ups while bonding with a phone ?

Thanks,
Marten

RE: Pairing pop-up appears twice on Android using the HRS example

Marten — Wed, 26 Apr 2023 13:19:32 GMT

Indeed the Bluetooth Low Energy app in nRF Connect for desktop I used too for testing.

RE: Pairing pop-up appears twice on Android using the HRS example

Kazi Afroza Sultana — Wed, 26 Apr 2023 13:12:11 GMT

Hello Marten,

I have run the example and I had bonded connection here.

''There is no issue when using nRF Connect for Desktop, so enabling Le Secure connection and bonding.''. do you mean that you use BLE app on nRF Connect for Destop?

Thanks.

Kazi