<?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>Unable to talk to IOS11 phone</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/70147/unable-to-talk-to-ios11-phone</link><description>I have a startup sequenced (nRF52832 peripheral) based on the s132 (v7.0.1 BLE 5.1) NFC Pairing example where it advertises at 1Msps link rate, then uses the PHY UPDATE API to go to 2Msps. My peripheral node works correctly when using an nRF dev board</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 21 Jan 2021 15:16:38 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/70147/unable-to-talk-to-ios11-phone" /><item><title>RE: Unable to talk to IOS11 phone</title><link>https://devzone.nordicsemi.com/thread/290580?ContentTypeID=1</link><pubDate>Thu, 21 Jan 2021 15:16:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4da6acaa-9ec9-4048-b3dd-8b053632c387</guid><dc:creator>anealca</dc:creator><description>&lt;p&gt;It turns out that iOS10 and newer requires the use of an MTU size of 185. This is concerning since BLE certification&amp;nbsp;expects the normal MTU size.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to talk to IOS11 phone</title><link>https://devzone.nordicsemi.com/thread/287780?ContentTypeID=1</link><pubDate>Wed, 06 Jan 2021 15:52:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e4d24eaf-a709-489c-b517-98077e552e26</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;If you are using the latest nRF sniffer with an nRF52-DK you should be able to also sniff 2Mbps I believe:&lt;br /&gt;&lt;a href="https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Sniffer-for-Bluetooth-LE"&gt;https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Sniffer-for-Bluetooth-LE&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Is that what you are doing?&lt;/p&gt;
&lt;p&gt;Can you share the sniffer log before switching to 2Mbps?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to talk to IOS11 phone</title><link>https://devzone.nordicsemi.com/thread/287777?ContentTypeID=1</link><pubDate>Wed, 06 Jan 2021 15:35:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8a3608d7-f147-4014-ab4e-77a35dbfa19f</guid><dc:creator>anealca</dc:creator><description>&lt;p&gt;I know I am not&amp;nbsp;calling the update request ftn from the peripheral except in&amp;nbsp;that event...&lt;/p&gt;
&lt;p&gt;The problem with the sniffer logs is it doesn&amp;#39;t switch to 2Msps. So the sniffer stops recording as soon as they switch to the higher link speed.&amp;nbsp; I do not know how to get the sniffer to also switch to 2Msps.&amp;nbsp;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to talk to IOS11 phone</title><link>https://devzone.nordicsemi.com/thread/287738?ContentTypeID=1</link><pubDate>Wed, 06 Jan 2021 13:42:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7b67cfcf-9837-4156-8bdd-ee52df558017</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I suspect we need an on-air sniffer log (e.g. using nRF sniffer) to see what is actually occurring here. However if you suspect it is related to RF_PHY update, you can check if you may be calling&amp;nbsp;sd_ble_gap_phy_update() somewhere in the application on the peripheral outside of the&amp;nbsp;BLE_GAP_EVT_PHY_UPDATE_REQUEST event.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>