<?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>komoot repeatedly disconnected again(based on Android)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/50378/komoot-repeatedly-disconnected-again-based-on-android</link><description>When I connected the development board with komoot (based on Android), komoot repeatedly disconnected again. The chip platform is nRF52832, and the protocol stack version is S332. 
 The reason for disconnection is BLE_HCI_LOCAL_HOST_TERMINATED_CONNECTION</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 31 Jul 2019 03:31:55 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/50378/komoot-repeatedly-disconnected-again-based-on-android" /><item><title>RE: komoot repeatedly disconnected again(based on Android)</title><link>https://devzone.nordicsemi.com/thread/201387?ContentTypeID=1</link><pubDate>Wed, 31 Jul 2019 03:31:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0a21cfa2-4ce3-4c5b-9be6-22c579004e13</guid><dc:creator>Fridedrich</dc:creator><description>&lt;div class="result-shield-container tlid-copy-target"&gt;&lt;span class="tlid-translation translation" lang="en"&gt;&lt;span class="tlid-translation translation" lang="en"&gt;&lt;span class="tlid-translation translation" lang="en"&gt;&lt;span title=""&gt;Thank u for the reply,now &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="tlid-translation translation" lang="en"&gt;&lt;span title=""&gt;I grabbed the packet with a sniffer and found that it was komoot (based on Android) actively disconnected (reason:0x13), instead of the device actively disconnecting, at the same time, I found that komoot (based on Apple) and the device connection is stable.So, it&amp;#39;s very possible because some aspects of the Android machine optimized komoot, so I turned off the option for komoot optimization on my phone (one plus 3), but it still appears 0x13, but I use SAMSUNG GALAXYS In the S9 test, there is no disconnection (0x13 will appear if the battery optimization option is not turned off). So, probably because of the optimization of the Android battery.thank u,Have a nice day.&amp;nbsp;&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: komoot repeatedly disconnected again(based on Android)</title><link>https://devzone.nordicsemi.com/thread/201257?ContentTypeID=1</link><pubDate>Tue, 30 Jul 2019 13:07:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:97aba390-8dd7-42c2-8dd0-be2c6891bdbd</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;There is not enough information here to say anything about what is going on. Can you provide a sniffer trace, and perhaps also log from the nRF side? What is supposed to happen on the link, and how does this compare with what is actually happening (disconnect with reason 0x16)?&lt;/p&gt;
&lt;p&gt;Note that most of the BLE communication on the Android side is handled by the BLE stack, so it is probably not directly related to which app you are using (Komoot).&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>