GATT CONN TIMEOUT

[mijiale]

Hi all

nrf52840 Development board,sdk is nRF5_SDK_15.2.0_9412b96,PC is windows 10

When I run the demo of ble_app_hrs on my development board,I use nrf connect app to connect my devcie,the connecting will disconnect.

From the nrf conenct we can see that the error is "GATT CONN TIMEOUT" and I print the log of the error code is 34 that express BLE_HCI_STATUS_CODE_LMP_RESPONSE_TIMEOUT

There is another point to pazzle me is that this situation only happens when I use the phone of HuaWei,other phones just like XiaoMi and HTC will not happen this situation.

[Simonr]

Hi

Error 133 is a known compatability error for a lot of Android phones, although we have mostly patched this problem, there still are some phones who gets this error. What Huawei model is it that you're using? I suggest you just use a phone that doesn't have this issue as there is no guaranteed fix. You could try adding some delays (buffers) after connection, to try and prevent this timeout, but this is not guaranteed to work.

Best regards,

Simon

[MikeT]

We are seeing this on Huawei p10 lite as well
we previously used:
nrf51822 (softdevice: S110, v7.1.0)

and now we use:
nrf52832 (softdevice: S132, v3.0.0)
nrf52840 (softdevice: S140, v6.0.0)

The behavior is worse with the newer nrf52 chipset.

The android NRF tool hardly finds the BLE device and if it finally (after restarting ble, wifi, etc) discovers it, it returns 133 during connection.


Is there any configuration or something similar we have to do and we might have missed?


I know Huawei is horrible, but nevertheless we have lots of users using that phones, and we want to provide them the best experience possible.

Cheers,
Mike

[Simonr]

Hey Mike

Please open a separate post on this if you want additional support, as we try to keep one thread per subject. You can try updating the SoftDevice of your nRF52 devices, but seeing as you struggle discovering the BLE device this very well can be another problem.

Best regards,

Simon