<?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>Connection drop immediately in specific Android models</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/44933/connection-drop-immediately-in-specific-android-models</link><description>Device/SW Info: 
 Ubuntu 18.1 SDK : 15.0 SD 132 v 6.0 
 NRF52832 QFAAE1 
 
 The device once connected to the device is immediately dropping the connection upon going into discoverServices(), as seen in the logs. I am unable to understand the reason exactly</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 09 Apr 2019 11:23:09 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/44933/connection-drop-immediately-in-specific-android-models" /><item><title>RE: Connection drop immediately in specific Android models</title><link>https://devzone.nordicsemi.com/thread/181010?ContentTypeID=1</link><pubDate>Tue, 09 Apr 2019 11:23:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0c592e2c-3c0c-4306-b71d-09862964f47b</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Ok, so it looks like that the phone tried to change PHY (1Mbps or 2Mbps or&amp;nbsp;Long range)&amp;nbsp; and was waiting for the response from the NRF52 but received nothing, so it disconnected after awhile. It&amp;#39;s not &amp;quot;immediately dropped&amp;quot; , the connection remains 40 seconds after the request.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;So you would need check if you handle&amp;nbsp;BLE_GAP_EVT_PHY_UPDATE_REQUEST event in your&amp;nbsp;ble_evt_handler() in main.c or not (it&amp;#39;s by default handled there in our examples in the SDK) , you would need to call&amp;nbsp;sd_ble_gap_phy_update() to reply to the request, on which PHY you want to use.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Connection drop immediately in specific Android models</title><link>https://devzone.nordicsemi.com/thread/180904?ContentTypeID=1</link><pubDate>Tue, 09 Apr 2019 06:25:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:766fddf2-38bb-49ca-a145-3699f040f926</guid><dc:creator>Charadhar Rddy</dc:creator><description>&lt;p&gt;Hi Hung Bui,&lt;/p&gt;
&lt;p&gt;I have attached the logs above. Can you please check now to see if it makes things any clearer?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Connection drop immediately in specific Android models</title><link>https://devzone.nordicsemi.com/thread/176755?ContentTypeID=1</link><pubDate>Mon, 18 Mar 2019 14:28:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:744f5673-c845-4c33-83ba-517d7bc4bf34</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;LMP TIMEOUT is Link Manager Protocol Timeout. This happens when a link layer request didn&amp;#39;t get a response after (usually) 30 seconds. It would be much easier to know what exactly causing the issue if you can provide a sniffer trace.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>