nRF Connect for android disconnects with Error 22: 'gatt conn terminate local host'

RE: nRF Connect for android disconnects with Error 22: 'gatt conn terminate local host'

tesc — Mon, 02 Nov 2020 15:13:33 GMT

Hi,

To sum up, the issue is that the smartphone app has a GATT server, and it sends indications to the nRF device, even if the nRF device has changed application to something not expecting indications?

Note that the nRF device, by default, will always use the same BLE address. So it might be the smartphone remembering from a previous session that the device of that address had enabled indications. However, from what I understand that should not happen unless the device is bonded... So if that is indeed what is happening then there is something wrong either in the app or in the BLE stack of the smartphone. It would still be worth trying the workaround from a previous answer in this thread:

[quote user="ivnn"]to solve this issue go to Android Settings->Bluetooth->Paired devices-> and unpair your dev[/quote]

Regards,
Terje

RE: nRF Connect for android disconnects with Error 22: 'gatt conn terminate local host'

Noon — Tue, 22 Sep 2020 18:46:56 GMT

Hi, i have the same problem. And i'm really curious to know the answer to the previous question: "I'm not sure how is it possible to receive Indications if i'm not enabling any client feature in my device" ?

Thx

RE: nRF Connect for android disconnects with Error 22: 'gatt conn terminate local host'

Sravanakumar — Thu, 16 Jul 2020 20:03:39 GMT

Hi liuked,

I have disabled the indication for example GATT service, even though I am facing the same issue.

RE: nRF Connect for android disconnects with Error 22: 'gatt conn terminate local host'

liuked — Mon, 22 Jun 2020 00:01:45 GMT

For anyone who ends up in this thread because of the nRF Connect "ERROR 22" issue, I just spent 2 h trying to figure out the reson in my case.

So, just to recap the details of the issue:

my device (NRF52832QFAAE0) is a BLE peripheral serving as GATT Server, using SoftDevice s132 v7.0.1, SDK16.0.0.
NRF_SDH_BLE_CENTRAL_LINK_COUNT = 0
NRF_SDH_BLE_PERIPHERAL_LINK_COUNT = 1
my device was not showing any known or unknown or assertion fail
my device was correctly advertising and accepting connection (without bonding)
after 30 seconds from each connection, my smartphone (OnePlus 5T, android 9) is dropping the connection with error 22 (0x16)
I was using nRF Connect version 4.24.1

The 30 second timeout of my phone lead me to think that my device was probably not replying to a GATT query from my phone.
After dumping all the BLE events, I noticed that I was receiving a HVX event of type INDICATION.

At first I solved it with a simple call to:

sd_ble_gattc_hv_confirm(p_ble_evt->evt.gap_evt.conn_handle, p_ble_evt->evt.gattc_evt.params.hvx.handle);

A second inspection brought me to find out that my NRF app was configured with an example of GATT service and apparently was sending indication to my device. Disabling it solved my issue.

Please, nRF Team, look into this, and maybe put a warning in the app if the server example is enabled by default.
Still, I'm nos sure how is it possible to receive Indications if i'm not enabling any client feature in my device.

RE: nRF Connect for android disconnects with Error 22: 'gatt conn terminate local host'

ivnn — Sun, 23 Sep 2018 20:19:47 GMT

hi, "error 22" happened when you trying to reconnect to already paired device

to solve this issue go to Android Settings->Bluetooth->Paired devices-> and unpair your dev

tested on Andr 8.1.0 xiaomi mia2 ble5.0

RE: nRF Connect for android disconnects with Error 22: 'gatt conn terminate local host'

Keton — Wed, 07 Mar 2018 12:19:33 GMT

I'm setting up recording of sniffer trace right now. I had to change the phone too as Mi2 switches to BLE 5.0 2Mbps mode automatically and sniffer looses track of the connection. I'll record trace of connection with Xiaomi Redmi 4X

RE: nRF Connect for android disconnects with Error 22: 'gatt conn terminate local host'

tesc — Wed, 07 Mar 2018 12:01:03 GMT

Have you tried with another phone now, and/or gotten a sniffer trace?

Any information that would let us get further in figuring out what is happening?

RE: nRF Connect for android disconnects with Error 22: 'gatt conn terminate local host'

Keton — Fri, 23 Feb 2018 15:34:46 GMT

The phone was connected to the charger. I'm pretty confident that this is not doze related issue because nRFConnect is added to power saving exceptions and as far as I can tell the app wasn't killed (unless this works differently in Android 8.0). I'll try different phone next week just to be sure.

This setup doesn't use bonding. As for reconnecting there will be auto reconnect procedure in the app but point of this exercise is to detect if nRF52 reboots or hangs. Early versions of this firmware had tendency to disappear from BLE after several weeks (no connection, no advertising).

I'll try to record sniffer trace of the disconnection, maybe this will tell us more.

RE: nRF Connect for android disconnects with Error 22: 'gatt conn terminate local host'

Aleksander Nowakowski — Fri, 23 Feb 2018 14:36:24 GMT

Hi, did you try with a different phone? Was your phone connected to power during the test? Could it be the Doze mode?

Are you using bonding? If so, you could advertise directly when it gets disconnected and Android should reconnect, I guess.

nRF Connect doesn't disconnect. It just displays events that it receives from the system...