<?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>nRF5340 disconnection event is not triggered during OTA</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/129191/nrf5340-disconnection-event-is-not-triggered-during-ota</link><description>Hi, 
 We are using the nRF5340 and a Pixel phone for the nRF OTA update. We observed that the Pixel phone application disconnects after updating the connection parameters. However, this disconnection event is not being triggered or received by the application</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 17 Sep 2026 18:45:00 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/129191/nrf5340-disconnection-event-is-not-triggered-during-ota" /><item><title>RE: nRF5340 disconnection event is not triggered during OTA</title><link>https://devzone.nordicsemi.com/thread/571323?ContentTypeID=1</link><pubDate>Thu, 17 Sep 2026 18:45:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3eb09ed7-c7e8-4698-94ad-20e466c47c85</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;What mobile application are you using?&amp;nbsp;Could you try &lt;a href="https://www.nordicsemi.com/Products/Development-tools/nRF-Connect-Device-Manager"&gt;the nRF Device app&lt;/a&gt;? Do you get the same issue with&amp;nbsp;&lt;a href="https://www.nordicsemi.com/Products/Development-tools/nRF-Connect-Device-Manager"&gt;the nRF Device app&lt;/a&gt;?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF5340 disconnection event is not triggered during OTA</title><link>https://devzone.nordicsemi.com/thread/571283?ContentTypeID=1</link><pubDate>Thu, 17 Sep 2026 04:43:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9c5c6651-acfb-4b96-b3fd-1ebbf459dcfa</guid><dc:creator>AKV</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;We need to update both the Net Core and App Core. The issue occurs both when the Net Core is updated and when it is not updated.&lt;/p&gt;
&lt;p&gt;In the attached log, we are updating the same firmware again, which is why it shows the Net Core update as failed. However, the Net Core failure is reported in the application logs and is triggered by the disconnection that occurred before it.&lt;/p&gt;
&lt;p&gt;As per the HCI logs, the device did not respond to the phone for nearly 500 ms. Essentially, the radio was inactive for an extended period. Since the supervision timeout is 420 ms, an RF response gap of around 500 ms would trigger a disconnection event on the master side.&lt;/p&gt;
&lt;p&gt;So, please investigate why the radio remained inactive for approximately 500 ms and identify the root cause of this radio inactivity/disconnection.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF5340 disconnection event is not triggered during OTA</title><link>https://devzone.nordicsemi.com/thread/571270?ContentTypeID=1</link><pubDate>Wed, 16 Sep 2026 13:08:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d915a3c3-74c4-464b-995e-2b9498124fb1</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Do you really need to update the net code?&lt;/p&gt;
&lt;p&gt;In your log:&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/Screenshot-2026_2D00_09_2D00_16-080740.png" /&gt;&lt;/p&gt;
&lt;p&gt;If unchanged, do not upload image index 1 at all.&lt;/p&gt;
&lt;p&gt;This avoids the failure mode entirely for the common “app-only update” case, with no firmware change and no Pixel-specific hack.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF5340 disconnection event is not triggered during OTA</title><link>https://devzone.nordicsemi.com/thread/571250?ContentTypeID=1</link><pubDate>Wed, 16 Sep 2026 04:05:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9ad2bda8-987f-4b43-866f-ac906a387286</guid><dc:creator>AKV</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;We are using NCS 2.6.1 with &lt;code&gt;CONFIG_BT_HCI_ACL_FLOW_CONTROL=n&lt;/code&gt;. The issue occurs only with Pixel phones and is not reproducible with other phones.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;div&gt;&lt;/div&gt;
&lt;p&gt;These are the current Bluetooth buffer configuration settings:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;CONFIG_BT_BUF_ACL_TX_COUNT=30&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;CONFIG_BT_BUF_ACL_RX_COUNT=6&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;CONFIG_BT_CTLR_SDC_TX_PACKET_COUNT=21&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;CONFIG_BT_BUF_CMD_TX_COUNT=10&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;code&gt;&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Since the product is already in the market and we cannot make changes to the firmware/code, is there any workaround that can be implemented from the application side to address this issue?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF5340 disconnection event is not triggered during OTA</title><link>https://devzone.nordicsemi.com/thread/571244?ContentTypeID=1</link><pubDate>Tue, 15 Sep 2026 15:47:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:248e622f-15e0-4c42-8b81-efac5eb11cb9</guid><dc:creator>Amanda Hsieh</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;What NCS version are you using? Could you try the latest version, v3.4.0?&lt;/p&gt;
&lt;p&gt;There is a known issue:&amp;nbsp;&lt;span&gt;NCSDK-32999&lt;/span&gt;&amp;nbsp;&lt;br /&gt;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/Screenshot-2026_2D00_09_2D00_15-103959.png" /&gt;&lt;/p&gt;
&lt;p&gt;If you are using the affected version, please apply the workaround in your project. See &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/121986/ble-advertisement-issue-in-nrf-connect-sdk-v2-7-0-drgn-23231-any-cherry-pick-or-temporary-fix-available/538664"&gt;my colleague&amp;#39;s example in this post&lt;/a&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Amanda H.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>