Connection parameters update failed, LMP TIMEOUT

RE: Connection parameters update failed, LMP TIMEOUT

sridharnaidu — Fri, 05 Jul 2019 12:19:05 GMT

I am also facing similar issue with old android devices

"The phone first sends a LL_VERSION_IND and then it sends a LL_FEATURE_REQ before the peripheral has sent its LL_VERSION_IND. In other words, the phone initiates a seconds LL Control Procedure before the first is finished, and this is a clear violation of the Bluetooth specification. The SoftDevice will disconnect at this point".

Is it really violation of specification?. If so why Nordic fixed it from s132v4.0.2 ?. Is there any part in specification which mention this?. In my case i using s132v3, so how can i fix this in my case?

RE: Connection parameters update failed, LMP TIMEOUT

arthare — Thu, 20 Jun 2019 21:20:25 GMT

I fixed this problem in my firmware by responding to the BLE_GAP_EVT_PHY_UPDATE_REQUEST message sent to my on_ble_evt handler.

      case BLE_GAP_EVT_PHY_UPDATE_REQUEST:
      {
          ble_gap_phys_t const phys =
          {
              .tx_phys = BLE_GAP_PHY_AUTO,
              .rx_phys = BLE_GAP_PHY_AUTO,
          };
          ret_code_t err = sd_ble_gap_phy_update(pEvent->evt.gap_evt.conn_handle, &phys);
          APP_ERROR_CHECK(err);
          break;
      }

I had a Google Pixel 3A XL running Android 9, and every 30 seconds it would time out with the same complaints yours had.

RE: Connection parameters update failed, LMP TIMEOUT

tianfei00 — Wed, 06 Mar 2019 07:44:58 GMT

I also encounter the 0x22 error(LMP Responese Timeout). But the answer above is not specific and I also can not resolve this problem.

RE: Connection parameters update failed, LMP TIMEOUT

Fabian Hauschild — Wed, 20 Feb 2019 15:35:08 GMT

Hi I'm having a simular problem with a Galaxy S7 with Android 8.0.0.

Could you please specify the contet of your gatt_evt_handler() and gatt_init() function.

RE: Connection parameters update failed, LMP TIMEOUT

Mttrinh — Fri, 06 Apr 2018 09:26:36 GMT

Hi,

Look at the answer above :)

RE: Connection parameters update failed, LMP TIMEOUT

Takeshi Goda — Mon, 26 Mar 2018 01:44:10 GMT

Hello how did you solve it and I encountered the same problem

RE: Connection parameters update failed, LMP TIMEOUT

Andreas123 — Tue, 13 Mar 2018 10:44:28 GMT

We fixed the issue by enabling the GATT module in sdk_config.h and adding a gatt_evt_handler() and gatt_init() to our main file.

RE: Connection parameters update failed, LMP TIMEOUT

Mttrinh — Tue, 06 Mar 2018 09:32:17 GMT

The thingy firmware is based on SDK13, and since your application is a mix of the thingy firmware and ble-examples from SDK14, there will be softdevice compatibility issues. According to the compatibility matrix, you can see that SDK13 is compatible with softdevice s132v4.0.x, and SDK14 is compatible with softdevice s132v5.0.0.

RE: Connection parameters update failed, LMP TIMEOUT

Andreas123 — Wed, 28 Feb 2018 13:02:42 GMT

Hi,

thank you for your suggestions. Yes i have tried to increase the connection interval. I also tried to use exactly the same connection settings as in the ble_app_hrs example.

Our application is a mix of the thingy firmware and the ble-examples of the SDK 14.0.0, where we use the motion service of the thingy and the ble settings of the SDK to transmit accelerometer values via Bluetooth.

From my understanding of the sniffer trace, the phone seems to send LL_FEATURE_REQ after both the phone and the peripheral have sent a LL_VERSION_IND (lines 120-124)

120	10.078095	Master_0x50655a6f	Slave_0x50655a6f	LE LL	32	Control Opcode: LL_VERSION_IND
121	10.078764	Slave_0x50655a6f	Master_0x50655a6f	LE LL	26	Empty PDU
122	10.079386	Master_0x50655a6f	Slave_0x50655a6f	LE LL	26	Empty PDU
123	10.079974	Slave_0x50655a6f	Master_0x50655a6f	LE LL	32	Control Opcode: LL_VERSION_IND
124	10.080565	Master_0x50655a6f	Slave_0x50655a6f	LE LL	35	Control Opcode: LL_FEATURE_REQ

Complete sniffer trace: devzone.nordicsemi.com/.../2555.km_5F00_log.pcapng

RE: Connection parameters update failed, LMP TIMEOUT

Mttrinh — Tue, 27 Feb 2018 15:02:10 GMT

Hi,

Have you tried to increase the connection interval?

Error 133 is a known error on some Android phones. I'm not sure in this case but the error occurs when the phone first sends a LL_VERSION_IND and then it sends a LL_FEATURE_REQ before the peripheral has sent its LL_VERSION_IND. In other words, the phone initiates a seconds LL Control Procedure before the first is finished, and this is a clear violation of the Bluetooth specification. The SoftDevice will disconnect at this point. Can you do a sniffer trace to confirm that this is the case?

EDIT: We added a Compatibility mode 2 in the Softdevice(s132v3.1.0), which let the phone connect to the device regardless of this.

To Enable Compatibility Mode 2, add this:

ble_opt_t ble_opt;

memset(&ble_opt, 0, sizeof(ble_opt));

ble_opt.gap_opt.compat_mode_2.enable = 1;

err_code = sd_ble_opt_set(BLE_GAP_OPT_COMPAT_MODE_2,&ble_opt); 

APP_ERROR_CHECK(err_code);

You say that the example ble_app_hrs from the SDK works with all devices. Which example are you testing with that gives you these issues? Have you modified anything?