<?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>BLE stopped advertising and app timers slowed significantly</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/86047/ble-stopped-advertising-and-app-timers-slowed-significantly</link><description>Hi, 
 Im currently working with a custom PCB using the nRF52832 and soft device s132 with v5.1.0. 
 Sometimes the BLE stops advertising and becomes undetectable after a connection (and subsequent timed out disconnection) with a Mobile device. This happens</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 23 Mar 2022 09:14:15 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/86047/ble-stopped-advertising-and-app-timers-slowed-significantly" /><item><title>RE: BLE stopped advertising and app timers slowed significantly</title><link>https://devzone.nordicsemi.com/thread/359534?ContentTypeID=1</link><pubDate>Wed, 23 Mar 2022 09:14:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:63019f0e-e850-41ed-8c5f-d62e65864d31</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;All the known issues that were discovered after releasing S132v5.1.0 can be found if you look at bux fixes and known issues for all the releases in the release notes.&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/s132_5F00_nrf52_5F00_7.2.0_5F00_release_2D00_notes_2D00_update_2D00_2.pdf"&gt;devzone.nordicsemi.com/.../s132_5F00_nrf52_5F00_7.2.0_5F00_release_2D00_notes_2D00_update_2D00_2.pdf&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Based on your description it is hard for me to narrow down what the problem could be. Some logs or the context where it happens or the context into which the CPU goes after this happens will be helpful. It would be also good to know if there were any fault exceptions happened or if there was any spikes in the power source. We can take it from there with the information you provide.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Also please provide which chip version you are using (lazer markings on the nRF chip)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>