nRF Connect not working on Poco F1

[EarthLord]

Hi everyone,

I've a nRF52810 based device that I am working with the Android based nRF Connect app on a Poco F1 (Oreo 8.1.0). The app scans the device properly but connection isn't being established, as you can see below. Note that at 12.14.34s when device.connectGatt happens on the app, the device also gets a callback that the connection is established. Please help us in debugging this. Thanks. 

[Kenneth]

Hi,

We need an on-air sniffer log, please download and install nrf-sniffer-v2 (follow user guide).
https://www.nordicsemi.com/eng/Products/Bluetooth-low-energy/nRF-Sniffer/(language)/eng-GB#Downloads 

As a wild guess can you comment out sd_ble_gattc_exchange_mtu_request() in on_connected_evt() in nrf_ble_gatt.c?

What SDK and softdevice are you running here? Is S112 defined? E.g. see nrf_ble_gatt_on_ble_evt() in nrf_ble_gatt.c if BLE_GAP_EVT_DATA_LENGTH_UPDATE and BLE_GAP_EVT_DATA_LENGTH_UPDATE_REQUEST is compiled.

Best regards,
Kenneth

[EarthLord]

static void ble_evt_handler(ble_evt_t * evt)
{
    uint32_t err_code;
    switch(evt->header.evt_id)
    {
    case BLE_GAP_EVT_CONNECTED:
        h_conn = evt->evt.gap_evt.conn_handle;
        break;
    case BLE_GAP_EVT_DISCONNECTED:
        h_conn = BLE_CONN_HANDLE_INVALID;
        break;
    case BLE_GATTS_EVT_WRITE:
    {
        sensepi_config_t * config =
                (sensepi_config_t *) evt->evt.gatts_evt.params.write.data;
        sensepi_config_t_update(config);
        break;
    }
    case BLE_GATTS_EVT_EXCHANGE_MTU_REQUEST:
    {
        uint16_t mtu_val = BLE_GATT_ATT_MTU_DEFAULT;
        err_code = sd_ble_gatts_exchange_mtu_reply(h_conn, mtu_val);
        APP_ERROR_CHECK(err_code);
        break;
    }
    }

    sensepi_ble_sd_evt(evt);
}

Thanks for the quick reply. We're using nRF52810 running S112 6.0.0. We're not using the SDK. The about function is all the SD related activities done with events.

We have not had any issue with any other phone, only this. So that's why the question is targeting the phone and the app .

Cheers, Prithvi

[Kenneth]

I suggest you print out evt->header.evt_id and check if there is an event occurring that is not handled (for instance compare working and non-working).

Best regards,
Kenneth

[EarthLord]

Thanks Kenneth. We were not handling the PHY update request. Once this is handled things got sorted.