<?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>Android 6+ can´t (re)connect to nRF51822 in DIRECT ADVERTISE mode</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/36120/android-6-can-t-re-connect-to-nrf51822-in-direct-advertise-mode</link><description>Hi, 
 We are using nRF51822, SDK12.3, pca10028, S130 with &amp;quot;Red Bear BLE Nano V1.5&amp;quot; board. We try also in nRF51DK and our own board (designed by us) and the issue is the same. So we think the problem is not in module but in Android version or in code.</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 16 Jul 2018 15:20:52 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/36120/android-6-can-t-re-connect-to-nrf51822-in-direct-advertise-mode" /><item><title>RE: Android 6+ can´t (re)connect to nRF51822 in DIRECT ADVERTISE mode</title><link>https://devzone.nordicsemi.com/thread/140252?ContentTypeID=1</link><pubDate>Mon, 16 Jul 2018 15:20:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3de4a28f-ba9a-47dc-94e9-5087017bb93e</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;The LE Privacy feature was evolving around the time that Android 5-6 and S130 were released and it seems&amp;nbsp;to be some compatibility issues. Please refer to these articles for some background:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;a href="https://www.bluetooth.com/~/media/files/specification/bluetooth-low-energy-security.ashx"&gt;Bluetooth SIG Proprietary Information Security, Bluetooth Low Energ&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://blog.bluetooth.com/bluetooth-technology-protecting-your-privacy"&gt;Bluetooth Technology Protecting Your Privacy&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.electronicdesign.com/communications/ble-v42-creating-faster-more-secure-power-efficient-designs-part-2"&gt;BLE v4.2: Creating Faster, More Secure, Power-Efficient Designs—Part 2&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Most likely your Android&amp;nbsp;6+&amp;nbsp;devices don&amp;#39;t support the use of a random identity address during directed advertising. What you need to do is to generate a resolvable address (RPA) in your application and use that for directed advertising instead.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Before before using directed advertisement where the initiator address is set to an RPA t&lt;span&gt;he peripheral should also check if the peer device supports address resolution by reading the&amp;nbsp;&lt;a href="https://www.bluetooth.com/specifications/gatt/viewer?attributeXmlFile=org.bluetooth.characteristic.resolvable_private_address_only.xml"&gt;Resolvable Private Address Only&lt;/a&gt; and&amp;nbsp;&lt;a href="https://www.bluetooth.com/specifications/gatt/viewer?attributeXmlFile=org.bluetooth.characteristic.gap.central_address_resolution.xml"&gt;Central Address Resolution characteristic&lt;/a&gt;.&lt;/span&gt; &lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Android 6+ can´t (re)connect to nRF51822 in DIRECT ADVERTISE mode</title><link>https://devzone.nordicsemi.com/thread/140095?ContentTypeID=1</link><pubDate>Fri, 13 Jul 2018 16:16:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1fcabac0-edd2-40c0-aab9-68a17585746e</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Sorry for the slow response time. I have asked the Softdevice team for their opinion, but due to summer holidays a lot of key personnel is out of office and the progress is slow. Please give&amp;nbsp;us a couple of more days.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Android 6+ can´t (re)connect to nRF51822 in DIRECT ADVERTISE mode</title><link>https://devzone.nordicsemi.com/thread/139284?ContentTypeID=1</link><pubDate>Fri, 06 Jul 2018 14:14:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:32d48746-64f0-498c-b107-732175fcd35d</guid><dc:creator>TiagoST</dc:creator><description>&lt;p&gt;Yes, we use S130 v2.0.1&lt;/p&gt;
&lt;p&gt;I will send to you in private, the files.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Android 6+ can´t (re)connect to nRF51822 in DIRECT ADVERTISE mode</title><link>https://devzone.nordicsemi.com/thread/139240?ContentTypeID=1</link><pubDate>Fri, 06 Jul 2018 11:46:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9a80026a-4060-49a7-a1fe-a69ac9d40009</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Can you confirm that you are using S130 v2.0.1?&lt;/p&gt;
&lt;p&gt;Can you upload all your sniffer and HCI snoop log files?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>