<?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>Constant Android Bluetooth Pairing Requests for ALREADY PAIRED device after new Android security update</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/76969/constant-android-bluetooth-pairing-requests-for-already-paired-device-after-new-android-security-update</link><description>Hi 
 Since a recent Android security update, I am experiencing issues with my &amp;#39;Just Works&amp;#39; device based on NRF52832. Prior to this Android update, once paired, I would receive no further &amp;#39;Pairing Requests&amp;#39; however, since the change (to Android), I get</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 03 Aug 2021 12:36:58 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/76969/constant-android-bluetooth-pairing-requests-for-already-paired-device-after-new-android-security-update" /><item><title>RE: Constant Android Bluetooth Pairing Requests for ALREADY PAIRED device after new Android security update</title><link>https://devzone.nordicsemi.com/thread/323100?ContentTypeID=1</link><pubDate>Tue, 03 Aug 2021 12:36:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:af9a3bff-6d0b-4ea8-b010-87d5011d1772</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Thanks for the information. We have not been able to reproduce this issue, though there is clearly something there. I suspect there must be something else needed to trigger this, in addition to Android 11 and just works pairing. Please let me know if you make any progress or if you can provide firmware for a DK that can be used to reproduce this issue with a specific Android device.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Constant Android Bluetooth Pairing Requests for ALREADY PAIRED device after new Android security update</title><link>https://devzone.nordicsemi.com/thread/321087?ContentTypeID=1</link><pubDate>Wed, 21 Jul 2021 10:43:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ada924d5-a48a-4596-bbec-a76d11138c64</guid><dc:creator>veletron</dc:creator><description>&lt;p&gt;Sorry, I got bogged down with other stuff. Issue occurs on Android 11 no matter whether the bonding was done b4 the 10--&amp;gt;11 update or otherwise. EG, fresh clean phone already running android 11, install app, pair with device, appears under &amp;#39;paired devices&amp;#39; but every time you leave and then come back into range you get another pairing request despite the identity&amp;nbsp; of the device not having changed and the keys exchanged during the initial pairing being identical to current. If I get time I&amp;#39;ll try adding MITM to the peripheral and see if that &amp;#39;fixes&amp;#39; it, seems that this is an ill-thought-out security fix in android to prevent tracking on &amp;#39;Just Works&amp;#39; Mode1 level 2 devices.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Constant Android Bluetooth Pairing Requests for ALREADY PAIRED device after new Android security update</title><link>https://devzone.nordicsemi.com/thread/318200?ContentTypeID=1</link><pubDate>Thu, 01 Jul 2021 12:17:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:12e9630f-376e-4848-8906-ecdbd9a11392</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi Karen,&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;/em&gt;I have not come across this issue before, but if someone else has on this forum it would good with some feedback.&lt;/p&gt;
&lt;p&gt;It would be good to understand what actually happens here. Is it possible for you to make a sniffer trace? Also, what is the behavior like if you delete the bond on both the nRF and Android, and then bond again? Does the issue reappear, or does it only apply to devices that were bonded before the Android phone was updated?&lt;/p&gt;
&lt;p&gt;Einar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>