<?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 problem after initial connection</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/8174/connection-problem-after-initial-connection</link><description>Hello everyone, 
 I have a strange issue with s110 + whitelisting + Device Manager + nrf51822 + GCC and hopefully you can help me with a good advice. It appears that the device filters correctly based on the whitelist. However, the problem is that after</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 21 Jul 2015 10:45:12 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/8174/connection-problem-after-initial-connection" /><item><title>RE: Connection problem after initial connection</title><link>https://devzone.nordicsemi.com/thread/29378?ContentTypeID=1</link><pubDate>Tue, 21 Jul 2015 10:45:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6631df03-6f94-4737-b80b-27c2442ead76</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@GT: I&amp;#39;m glad that it worked for you now. I guess the case can be closed.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Connection problem after initial connection</title><link>https://devzone.nordicsemi.com/thread/29377?ContentTypeID=1</link><pubDate>Tue, 21 Jul 2015 09:59:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:38c4e50e-af73-48b1-b43f-56702b4a767c</guid><dc:creator>GT</dc:creator><description>&lt;p&gt;Hello Hung,
Thank you for the reply. I&amp;#39;ve already managed to solve it. The source of the problem was how I was handling the advertising module and more specifically starting and restaring it. Now, the application keeps track of the module&amp;#39;s state and takes care to stop it before it request a start again. Works fine now.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Connection problem after initial connection</title><link>https://devzone.nordicsemi.com/thread/29376?ContentTypeID=1</link><pubDate>Wed, 15 Jul 2015 08:52:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c7c5e07b-e0f2-44f5-ae12-b593f5f55368</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@GT: I would need to have a &lt;a href="https://www.nordicsemi.com/eng/Products/Bluetooth-Smart-Bluetooth-low-energy/nRF-Sniffer/(language)/eng-GB"&gt;sniffer trace&lt;/a&gt; to check if the issue was with the whitelist (establishing connection) or with bonding (re-encrypting connection).&lt;/p&gt;
&lt;p&gt;Have you tried with our stock example ? the ble_app_proximity for example  ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>