<?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>WiFi / BLE coexistence with shared antenna lead to BLE timeout on IOS</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/109246/wifi-ble-coexistence-with-shared-antenna-lead-to-ble-timeout-on-ios</link><description>Hello, 
 Working with nRF5340 and nRF7002, I wrote some code that initialise both WiFi stack and BLE stack and that perform network scan when receiving a BLE command. On Android it seems to work well but on IOS, the nRF Connect sometime disconnects the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 14 Mar 2024 13:38:23 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/109246/wifi-ble-coexistence-with-shared-antenna-lead-to-ble-timeout-on-ios" /><item><title>RE: WiFi / BLE coexistence with shared antenna lead to BLE timeout on IOS</title><link>https://devzone.nordicsemi.com/thread/473888?ContentTypeID=1</link><pubDate>Thu, 14 Mar 2024 13:38:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:16fe0ac3-1919-4ed3-969f-7f847b297399</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I assume the connection parameters usedon iOS and&amp;nbsp; Android driffer? With WiFi and BLE coexistance there will be soem missed connection events, and if the parameters are too tight, it could cause problems. Which parameters are used in the two cases (that can be seen from a sniffer trace)? Perhaps it would make sense to add some slack (like alonger superivsion timeout)?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>