Error(0x85):GATT ERROR

RE: Error(0x85):GATT ERROR

Fanis — Sun, 19 Nov 2017 13:50:29 GMT

It seems that playing with connection intervals and connection interval update times can solve the problem. I have had an issue in which i could connect with honor 9 to the main firmware and couldn't to dfu bootloader. Increasing conn parameter update delays seems to solve this problem (by default there was a 100ms after first connection and honor reports disconnect right after connect, or sometimes 0x85 error)

RE: Error(0x85):GATT ERROR

furnaceX — Wed, 16 Mar 2016 17:32:16 GMT

I didn't find a specific "bluetooth" only app. Just things like "Bluetooth MIDI Service", "bluetooth share", etc. Anyway, I forced close and cleared data on all of them. Didn't fix it.

I have 3 identical devices... On the samsung S7, one I can connect to all of the time, one some of the time, and the 3rd, I can connect to if I push the button on it, it will connect for a short time ~15 seconds (otherwise it fails to connect immediately, as I showed above). On a Moto X (Android 5.1) all 3 devices connect without anything special (i.e. no button clicks) and stay connect.

RE: Error(0x85):GATT ERROR

Hung Bui — Mon, 14 Mar 2016 13:52:37 GMT

@furnaceX: Next time please add your question in the comment section or create a new question. We found that this could be Android's issue. Could you try, on the phone, to go to Setting -> Application -> Application manager -> All app -> look for Bluetooth and click Force Close and Clear Data ? And test again.

RE: Error(0x85):GATT ERROR

Shubham Kumar Mishra — Mon, 14 Mar 2016 06:30:51 GMT

You are using your own customized BLE service or you are checking with the SIG service come with Nordic SDK?

Because this seems there is some mistakes with source code.

RE: Error(0x85):GATT ERROR

furnaceX — Mon, 14 Mar 2016 00:30:24 GMT

I'm having a similar problem. I can connect to the devices on an Android 5.1 Phone (MotoX), but on a new Samsung S7 on Android 6.0.1, I'm unable to connect. I don't even get as far as discovery. I can connect to other non-Nordic devices. And I can't connect using non-Nordic scanner apps on the S7.

Here's the log from your nRF Master Control app:

nRF Master Control Panel, 2016-03-13
Teddy_M100044 (F5:12:9E:28:22:7F)
V	18:02:34.233	Connecting to F5:12:9E:28:22:7F...
D	18:02:34.238	gatt = device.connectGatt(autoConnect = false)
D	18:02:35.501	[Callback] Connection state changed with status: 133 and new state: DISCONNECTED (0)
E	18:02:35.528	Error 133 (0x85): GATT ERROR
I	18:02:35.543	Disconnected
D	18:02:35.558	gatt.close()

And here's the adb debug output:

03-13 18:18:18.391 16014 16083 D BluetoothGatt: connect() - device: F5:12:9E:28:22:7F, auto: false
03-13 18:18:18.391 16014 16083 D BluetoothGatt: registerApp()
03-13 18:18:18.401 16014 16083 D BluetoothGatt: registerApp() - UUID=02c2672d-f730-428f-983b-6f9a91360cb9
03-13 18:18:18.441 16014 16025 D BluetoothGatt: onClientRegistered() - status=0 clientIf=7
03-13 18:18:19.971 16014 16026 D BluetoothGatt: onClientConnectionState() - status=133 clientIf=7 device=F5:12:9E:28:22:7F
03-13 18:18:19.971 16014 16026 E Peripheral: onConnectionStateChange. status = 133
03-13 18:18:19.971 16014 16026 E Peripheral: onConnectionStateChange. newState = 0
03-13 18:18:19.981 16014 16026 D BluetoothGatt: close()
03-13 18:18:19.981 16014 16026 D BluetoothGatt: unregisterApp() - mClientIf=7
03-13 18:18:19.991 16014 16014 D SystemWebChromeClient: file:///android_asset/www/js/bluetooth2.js: Line 266 : error in connect:ble.connect: {"name":"Teddy_M100044","id":"F5:12:9E:28:22:7F","advertising":{"CDVType":"ArrayBuffer","data":"DglUZWRkeV9NMTAwMDQ0AxlAAgIBBAcDBBgCGAMYAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA="},"rssi":-41}

RE: Error(0x85):GATT ERROR

Hung Bui — Mon, 02 Nov 2015 08:23:35 GMT

@vineeshvs: Please create another case with the link to this case and add description and a sniffer trace to your case.

RE: Error(0x85):GATT ERROR

vineeshvs — Sun, 01 Nov 2015 07:37:41 GMT

Tried turning on and off bluetooth. Same eror (Error 133) appears :(

RE: Error(0x85):GATT ERROR

Hung Bui — Mon, 29 Jun 2015 07:35:37 GMT

@Gigel: Did you bond with the device ? Could you try to unbond/unpair the device in Bluetooth setting ? Which nRF51 firmware did you use ? Have you tried with our SDK example ?

A sniffer firmware would be very useful to find what could be wrong.

RE: Error(0x85):GATT ERROR

Shubham Kumar Mishra — Fri, 26 Jun 2015 06:55:23 GMT

This mainly comes if service definition at client side and at central side in APP is not properly configured. So check your source code. Does the service you are using defined properly at both Peripheral and central end.

RE: Error(0x85):GATT ERROR

Gigel — Fri, 26 Jun 2015 03:13:24 GMT

I get the same error on reconnect. My setup uses a Nexus 5 running Android 5.1.1, build LMY48B, and my embedded device runs S110_nRF51822_7.0.0 (id:0x004f) and app based on SDK 6.1.0 (note: I can't use newer S110 and SDK due to the fact that my nRF51822 is a rev. 2 IC).

I can reproduce the issue from within nRF Master Control app ver 3.1.0. Restarting the Android device and my own nRF51822 device won't help much as the issue reappears.

The services and characteristics discovery works fine, but I get "Error 133 (0x85): GATT ERROR" right after performing a read on a characteristic, and it disconnects.

Any clues why this happens?

RE: Error(0x85):GATT ERROR

Hung Bui — Fri, 29 May 2015 15:28:59 GMT

@Error 133 is quite familiar with older version of Android (4.2, 4.3) Which Android device are you testing and running which version ? You can try to erase bond and turn off and on Bluetooth when the issue occurs.

RE: Error(0x85):GATT ERROR

Shubham Kumar Mishra — Fri, 29 May 2015 12:08:01 GMT

Yes this issue come only at the time of reconnect...... as on Mobile App from nordic nRF Master Control App I recieved this error ......... in log file gatt = device.connectGatt(autoConnect = false) [callback]Connection state changed with status 133 and new state :2 (CONNECTED) Error(0x85): GATT ERROR

RE: Error(0x85):GATT ERROR

Hung Bui — Fri, 13 Feb 2015 14:31:32 GMT

Hi Hucs,

Could you try to record a sniffer trace when the issue occurs ? Which phone are you using? and with which Android version ?

Do you have the issue after you turn off and on bluetooth ?