<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Error(0x85):GATT ERROR</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/27074/error-0x85-gatt-error</link><description>Hi guys, 
 I&amp;#39;m investigating on a problem we found in our system. It seems not related to our custom pcb or firmware, you can replicate it with the following setup. 
 Setup: 
 
 pcb - PCA10028 
 softdevice - nRF_SoftDevice_S110 8.0.1 
 device app</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sun, 19 Nov 2017 13:50:13 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/27074/error-0x85-gatt-error" /><item><title>RE: Error(0x85):GATT ERROR</title><link>https://devzone.nordicsemi.com/thread/106436?ContentTypeID=1</link><pubDate>Sun, 19 Nov 2017 13:50:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1feced62-9d0b-45f4-b739-ce9e1f5e66d0</guid><dc:creator>Fanis</dc:creator><description>&lt;p&gt;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&amp;#39;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)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Error(0x85):GATT ERROR</title><link>https://devzone.nordicsemi.com/thread/106435?ContentTypeID=1</link><pubDate>Tue, 05 Sep 2017 14:40:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c8eed6e2-17b3-4fab-96bd-b655006613c2</guid><dc:creator>michaeld</dc:creator><description>&lt;p&gt;Did you manage to solve the issue Ankush?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Error(0x85):GATT ERROR</title><link>https://devzone.nordicsemi.com/thread/106434?ContentTypeID=1</link><pubDate>Fri, 24 Mar 2017 06:47:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:67b7fc0e-f3b0-45a3-9a21-7d0ddaea35c8</guid><dc:creator>Ankush</dc:creator><description>&lt;p&gt;In my code I have changed the values for connection interval from 7.5 to 11.25. I am having Android 6 smart phone. Still I am facing the same 133 issue.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Error(0x85):GATT ERROR</title><link>https://devzone.nordicsemi.com/thread/106432?ContentTypeID=1</link><pubDate>Tue, 21 Mar 2017 19:36:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b3762d41-eab1-466e-a917-8f5efa12dd2b</guid><dc:creator>gennaro82</dc:creator><description>&lt;p&gt;Asap I will post the log from nrf connect but it&amp;#39;s quitesimple&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Error(0x85):GATT ERROR</title><link>https://devzone.nordicsemi.com/thread/106431?ContentTypeID=1</link><pubDate>Tue, 21 Mar 2017 12:12:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ed1a4d50-75dd-4fc0-8a50-27d31c3468d3</guid><dc:creator>Aleksander Nowakowski</dc:creator><description>&lt;p&gt;Could you post the logs from nRF Connect to your question? It would help us understand what&amp;#39;s going on.
If the issue does not appear on Android 7+ then it was an Android bug. Initiating a connection and then cancelling it wasn&amp;#39;t in fact cancelling, so the phone stayed connected. How about reopening nRF Connect wiht GATT Server configured to anything else than Disabled. Is the connection showing up there? How about when you click Disconnect button then?&lt;/p&gt;
&lt;p&gt;@Ankush, the minimum connection interval for Android 5+ is 11.25 ms. Before it was 7.5 ms.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Error(0x85):GATT ERROR</title><link>https://devzone.nordicsemi.com/thread/106430?ContentTypeID=1</link><pubDate>Mon, 20 Mar 2017 12:00:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0940f629-7a78-4e1f-8328-ce91e9ed3b00</guid><dc:creator>gennaro82</dc:creator><description>&lt;p&gt;The error doesn&amp;#39;t pop up with android 7 and ios 10&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Error(0x85):GATT ERROR</title><link>https://devzone.nordicsemi.com/thread/106433?ContentTypeID=1</link><pubDate>Sat, 18 Mar 2017 04:59:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e6e78d8b-4bfd-4446-865c-1d1e396a5a41</guid><dc:creator>Ankush</dc:creator><description>&lt;p&gt;Even I am also facing the same issue. Sometimes App does not connect to device and if I try to connect it multiple times  133 error appears in app error log. For me connection parameters are 7.5, 7.5, 0, 32000 respectively. Does some has any idea regarding this?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>