<?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 problems depending on the Smartphone with nrf52840</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/74287/connection-problems-depending-on-the-smartphone-with-nrf52840</link><description>Good afternoon, 
 We have developed a new equipment based on the nrf52840. We use sofldevice &amp;#39;s140_nrf52_6.1.0_softdevice&amp;#39; and we use bonding with static pin. 
 We have setup following parameters: 
 
 We also agreed with you (someone in this devzone)</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 22 Apr 2021 13:38:01 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/74287/connection-problems-depending-on-the-smartphone-with-nrf52840" /><item><title>RE: Connection problems depending on the Smartphone with nrf52840</title><link>https://devzone.nordicsemi.com/thread/306366?ContentTypeID=1</link><pubDate>Thu, 22 Apr 2021 13:38:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5a1ad6e9-86e1-4f07-bb2b-5348532314fc</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi Dani,&lt;/p&gt;
[quote user=""]- Depending on the Smartphone, we are not asked for the PIN when pairing/bonding the first time.[/quote]
&lt;p&gt;With iOS bonding is only initiated when needed, which is after being denied to read/write to a characteristic. Once that happens, the iOS BLE stack will initiate pairing/bonding. I suspect that is what you are seeing here.&lt;/p&gt;
[quote user=""]- In some smartphones, it takes a lot of time (even when already bonded) to stablish connection: maximum time should be 10&amp;quot; (advertising period) but sometimes, it takes more and more time.[/quote]
&lt;p&gt;Can you clarify what you mean by 10&amp;#39;&amp;#39;? (It does not match your&amp;nbsp;APP_ADV_INTERVAL value of 80 = 50 ms). Please elaborate.&lt;/p&gt;
[quote user=""]- When it takes a lot of time to connect, sometimes smartphone is able to connect when bluetooth is switched off and switched on again. But this is not happening with other devices, only with this one we have designed. Is it something related with parameters we have set up?[/quote]
&lt;p&gt;It is not clear to me exactly which advertising parameters you use (see above). But generally you can come into a situation where the phones scan window does not overlap with the peripherals advertisement packets for a long time if the scan interval and advertising interval re very similar (or advertising interval is a multiple of the scan interval). If they are not identical, they will drift to overlap at some point though. For this reason Apple has recommended some advertising intervals that work well in the &lt;a href="https://developer.apple.com/accessories/Accessory-Design-Guidelines.pdf"&gt;Accessory Design Guidelines for Apple Devices&lt;/a&gt;. Following those is generally a good idea. Also, some phones in some situations may have much less time for scanning, for instance if they allready have a lot of other BLE or other 2.4 GHz activity going on.&lt;/p&gt;
&lt;p&gt;Einar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>