Error 22 (0x16): GATT_CONN_TERMINATE_LOCAL_HOST only on Samsung XCover device

RE: Error 22 (0x16): GATT_CONN_TERMINATE_LOCAL_HOST only on Samsung XCover device

Dinesh Harjani — Tue, 16 Jun 2020 00:08:51 GMT

If you flash the Eddystone sample into a dev-kit after having previously paired/bonded with it with another image, you need to go into Settings in your Android phone and forget it 'by hand'; otherwise error 22 will arise when attempting to connect to it.

RE: Error 22 (0x16): GATT_CONN_TERMINATE_LOCAL_HOST only on Samsung XCover device

Sigurd — Wed, 12 Jun 2019 08:01:14 GMT

Hi George R,

Please create a new ticket for this.

RE: Error 22 (0x16): GATT_CONN_TERMINATE_LOCAL_HOST only on Samsung XCover device

George R — Wed, 12 Jun 2019 04:50:27 GMT

Hi Sigurd, we encounter the same problem with a Samsung Galaxy Tab A (2016) (ERR_22). We are using our sensors and Polidea RxBle to connect to sensors.

Can you please suggest a solution for us too? I do not know how to and where to implement the above mentioned solution provided.

RE: Error 22 (0x16): GATT_CONN_TERMINATE_LOCAL_HOST only on Samsung XCover device

Sigurd — Tue, 07 Mar 2017 17:37:27 GMT

Yes, that is correct.

RE: Error 22 (0x16): GATT_CONN_TERMINATE_LOCAL_HOST only on Samsung XCover device

Benjamin Füldner — Tue, 07 Mar 2017 16:12:46 GMT

Thank you for this hint! The connection with the Samsung XCover3 now works as expected, also with the S132 SoftDevice version 3.0.0. As I understand the problem, the Samsung device is not fully Bluetooth 4.2 compatible, right?

RE: Error 22 (0x16): GATT_CONN_TERMINATE_LOCAL_HOST only on Samsung XCover device

Sigurd — Mon, 06 Mar 2017 12:48:15 GMT

The sniffer is not up-to-date with the newest LL packets, so the name of the newest packets are shown as unknown in the sniffer. The first “unknown” packet has opcode 0x14, if you look at the Bluetooth Specifications (Core version 4.2 or 5.0) this is a LL_LENGTH_REQ packet send from the nRF52 to the Xcover, in order to enable Data length extension (DLE)/ longer on-air data packets. According to the specifications, if the Xcover supported DLE, it should have responded with a LL_LENGTH_RSP packet, and if Xcover didn’t support DLE it should have sent a LL_UNKNOWN_RSP packet. None of these packets are sent by the Xcover.

I suggest to use the default payload size of 27, so that the DLE procedure is not initiated (LL_LENGTH_REQ will not be sent). Call this function before you start advertising:

void data_len_ext_set(void)
{
    ret_code_t err_code;
    ble_opt_t  opt;

    memset(&opt, 0x00, sizeof(opt));

    opt.gap_opt.ext_len.rxtx_max_pdu_payload_size = 0;

    err_code = sd_ble_opt_set(BLE_GAP_OPT_EXT_LEN, &opt);
    APP_ERROR_CHECK(err_code);
}

RE: Error 22 (0x16): GATT_CONN_TERMINATE_LOCAL_HOST only on Samsung XCover device

Benjamin Füldner — Thu, 02 Mar 2017 14:37:49 GMT

I did the test with S132 version 3.1.0, but I got the same error results.

With the PCA10000 eval board I catched the two loggs attached to the question. The trace of the Samsung device is really weired: It is full of unknown LL Control PDUs. What does this mean?

RE: Error 22 (0x16): GATT_CONN_TERMINATE_LOCAL_HOST only on Samsung XCover device

Sigurd — Tue, 07 Feb 2017 10:35:05 GMT

Error 22 is not very common. Could you test with the S132 version 3.1.0 SoftDevice? Download it here, and replace the headers in the folder SDK_Folder\components\softdevice\s132. Try to enable compatibility mode, and see it this solves the issue. Put this after ble_stack_init():

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);

If this doesn't solve the issue, a sniffer trace should be performed.

RE: Error 22 (0x16): GATT_CONN_TERMINATE_LOCAL_HOST only on Samsung XCover device

Benjamin Füldner — Tue, 07 Feb 2017 09:48:05 GMT

I did a complete factory reset on the Samsung device (wipe /data, /cache, ...): Same behaviour. Also enabling debug output of the example did not lead to any error faults.

Interesting fakt: With the old SDK 11.0.0 and softdevice 2.0.0 the Samsung device works, but there we had problems with Apple devices :(

RE: Error 22 (0x16): GATT_CONN_TERMINATE_LOCAL_HOST only on Samsung XCover device

Sigurd — Mon, 06 Feb 2017 14:09:06 GMT

Hi,

This could be caused by an old gatt table with services that you previously bonded with. Try to go into Bluetooth settings on your phone, forget all bluetooth services/devices that you have listed there (paired with) and perhaps disable Bluetooth and enable it again. Then try again and see if it works.

If this doesn’t work, try to find any error codes reported by the nRF52(any reasons for the disconnect). See e.g. this answer on how to debug. A sniffer trace could also reveal what the problem is.