Connection problem GATT_ERROR 133 (0x85)

RE: Connection problem GATT_ERROR 133 (0x85)

Bernard — Wed, 27 Feb 2019 23:17:31 GMT

I appreciate the response on such an old thread. You are correct that we did not see any issue recently but we had a tendency to put all the Tab A issues into a big bucket!

RE: Connection problem GATT_ERROR 133 (0x85)

Sigurd — Mon, 25 Feb 2019 13:40:49 GMT

Hi Bernard,

[quote userid="66559" url="~/f/nordic-q-a/19927/connection-problem-gatt_error-133-0x85/172619"]NRF51-based product[/quote]

I think the issue is fixed in the latest TAB A devices, but I don’t have any lists over the affected TAB A versions. That said, I think Samsung released a software update that fixes this issue, so if you see any devices with the issue, you should update the android firmware on the Tab A device.

RE: Connection problem GATT_ERROR 133 (0x85)

Bernard — Sat, 23 Feb 2019 17:28:47 GMT

I know this is an old thread, but is there a current list of the TAB A that have the problem? These devices are still sold in 2019 and we need to know which one we can support with our NRF51-based product

RE: Connection problem GATT_ERROR 133 (0x85)

Samuel Peter — Tue, 29 Aug 2017 09:04:57 GMT

This solved the issue for me.

RE: Connection problem GATT_ERROR 133 (0x85)

Sigurd — Mon, 21 Aug 2017 12:30:20 GMT

Hi energy,

It could be a problem with the device not supporting DLE. Take a look at this answer, and call the function found in the answer before you start advertising.

RE: Connection problem GATT_ERROR 133 (0x85)

energy — Mon, 21 Aug 2017 10:31:09 GMT

Hi Sigurd, I tried with sdk 12.2 + S132 v3.1.0 (verified 0.91 with nrf_go), connexion is ok with xperia Z2 compact, moto S2 but I got still reboot when using the 10' TAB A6 model. My client got the reset when connection since Nougat release of 10' A6 tablet. Could you provide a UART exemple hex build (12.2 + S132 V3.1.0) for 10040 board that work should work for 10' A6 tablet. Thanks

RE: Connection problem GATT_ERROR 133 (0x85)

Sigurd — Mon, 14 Aug 2017 08:04:43 GMT

Hi energy,

You need to call the option-set function after you have enabled the SoftDevice.

RE: Connection problem GATT_ERROR 133 (0x85)

energy — Fri, 11 Aug 2017 15:01:48 GMT

Thank you, at which moment of the init, option set should be called ? Just before enabling the softdevice ?

RE: Connection problem GATT_ERROR 133 (0x85)

Sigurd — Fri, 11 Aug 2017 13:46:19 GMT

When you download S132 V3.0.1 from here. You should replace the header files in the SDK(located in the folder SDK_folder\components\softdevice\s132\headers\) with the ones you download(located in folder s132_nrf52_3.1.0\s132_nrf52_3.1.0_API\include)

RE: Connection problem GATT_ERROR 133 (0x85)

energy — Fri, 11 Aug 2017 13:40:34 GMT

Does this mean I have to change the union to /@brief Option structure for GAP options. / typedef union { ble_gap_opt_ch_map_t ch_map; /< Parameters for the Channel Map option. */ ble_gap_opt_local_conn_latency_t local_conn_latency; /< Parameters for the Local connection latency option */ ble_gap_opt_passkey_t passkey; /< Parameters for the Passkey option./ ble_gap_opt_scan_req_report_t scan_req_report; /< Parameters for the scan request report option./ ble_gap_opt_compat_mode_1_t compat_mode_1; /< Parameters for the compatibility mode 1 option./ ble_gap_opt_compat_mode_2_t compat_mode_2; /< Parameters for the compatibility mode 2 option./ ble_gap_opt_auth_payload_timeout_t auth_payload_timeout; /< Parameters for the authenticated payload timeout option./ ble_gap_opt_preferred_phys_t preferred_phys; /< Parameters for the preferred PHYs option. / ble_gap_opt_slave_latency_disable_t slave_latency_disable; /< Parameters for the Disable slave latency option / } ble_gap_opt_t; /@} */ and add menu option and i will be ok ?

RE: Connection problem GATT_ERROR 133 (0x85)

energy — Fri, 11 Aug 2017 13:38:01 GMT

Thanks for your anwser but 12.2 don't have compatible ble_gap_opt_t structure type with and BLE_GAP_OPT_COMPAT_MODE_2 in option list

RE: Connection problem GATT_ERROR 133 (0x85)

Sigurd — Fri, 11 Aug 2017 13:07:14 GMT

Hi energy,

As shown in the compatibility matrix here. S132 v3.1.0 is compatible with SDK version 12.0, 12.1 and 12.3.

In fact all S132 v.3.x.x versions are compatible with SDK 12.x.

RE: Connection problem GATT_ERROR 133 (0x85)

energy — Fri, 11 Aug 2017 13:02:44 GMT

Hi, Sdk 12.2.0 and 12.3.0 are compatible with only S132 v3.0.0

infocenter.nordicsemi.com/.../index.html

Which SDK for 52832 is compatible with S132 v3.1.0 ?

Thanks

RE: Connection problem GATT_ERROR 133 (0x85)

Sigurd — Fri, 17 Mar 2017 12:20:26 GMT

Hi manuj,

As endnode pointed out there will not be a new major SoftDevice version for nRF51. Compatibility mode is therefore not support on nRF51. The actually problem here is that Samsung Galaxy TAB A6 is breaking/not following the Bluetooth specification. With S132 v.3.1.0 (for nRF52) we added something called compatibility mode that can be enabled to still be able to connect to some of these devices that are not following the Bluetooth Specification.

RE: Connection problem GATT_ERROR 133 (0x85)

endnode — Tue, 14 Mar 2017 20:17:30 GMT

Nordic said that S130 V2 is the last SD major version on nRF51, I'm afraid no help available.

RE: Connection problem GATT_ERROR 133 (0x85)

manuj — Tue, 14 Mar 2017 14:44:50 GMT

Hi , I have the same problem with my NRF51 (PCA10028) with my samsung galaxy TAB A6.

Is It possible to have the softdevice V3.1.0 for nrf51 ?

RE: Connection problem GATT_ERROR 133 (0x85)

Sigurd — Wed, 22 Feb 2017 13:58:12 GMT

Hi,

You could try to upgrade to S132 v3.1.0 and enable compatibility mode, and see if that solves the problem. See also this answer.

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

ble_opt.gap_opt.compat_mode_2.mode_2_enable = 1;

err_code = sd_ble_opt_set(BLE_GAP_OPT_COMPAT_MODE_2,&ble_opt); 
APP_ERROR_CHECK(err_code);