https://devzone.nordicsemi.com/f/nordic-q-a/2303/wake-up-time-from-system-off-to-start-advertisingHello, I have made some current and timing measurements on the nRF51822 Development Kit (connected to a nRFgo Starter Kit) running some of the example applications provided in the SDK (Power Profiling Application and Heart Rate application exampleen-USTelligent Community 13Fri, 25 Apr 2014 13:17:12 GMThttps://devzone.nordicsemi.com/thread/9551?ContentTypeID=1Fri, 25 Apr 2014 13:17:12 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a3db1e28-b491-4064-a1c0-15d6e1ffba83H&#229;kon Alseth<p>Hi,</p> <p>That&#39;s due to the external 32kHz startup (usually from 0.3 - 1 sec, depending on the xosc). Look at this thread on how to reduce this: <a href="https://devzone.nordicsemi.com/index.php/softdevice_handler_init-duration#reply-7194">devzone.nordicsemi.com/.../softdevice_handler_init-duration</a></p> <p>BR Håkon</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/9550?ContentTypeID=1Tue, 22 Apr 2014 15:03:09 GMT137ad170-7792-4731-bb38-c0d22fbe4515:1287f037-5024-4d15-a187-b9f064b3ba20Mario Amigot<p>I mean, comparing nRF51822 to other BLE SoC chips in the market, I find this 350 msec period too long and power consuming, especially taking into account that nRF51822 doesn&#39;t need to mirror/get the code from an OTP memory. So my questions are: what is exactly the &quot;sub-process&quot; (some kind of calibration or trimming?) which slows down the wake-up process from System OFF to start advertising? Can this &quot;sub-process&quot; time be reduced somehow?</p><div style="clear:both;"></div>