https://devzone.nordicsemi.com/f/nordic-q-a/53775/timer-dislabled-after-using-ble-radio-solvedHello, I have a problem with app_timer. My program need to use BLE UART for about 15 second then switch for just RADIO after. To do so, I enable the ble stack as the ble_app_uart example in the ble_peripheral folder, and set an app_timer asen-USTelligent Community 13Tue, 29 Oct 2019 16:24:28 GMThttps://devzone.nordicsemi.com/thread/217383?ContentTypeID=1Tue, 29 Oct 2019 16:24:28 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c4fcda2f-7cea-41d8-8c01-94db2d22eb7cYann<div>Thanks for your quick response.</div> <div></div> <div>The call to<b><span>&nbsp;</span>nrf_drv_clock_lfclk_request()</b><span>&nbsp;</span>solved the problem. I was indeed using the clock initialized by the soft device.</div> <div></div> <div>The program now work as intended.</div><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/217358?ContentTypeID=1Tue, 29 Oct 2019 14:30:29 GMT137ad170-7792-4731-bb38-c0d22fbe4515:0c3e7cad-9730-4dd6-8412-34b19eff564aVidar Berg<p>Hello,</p> <p>Are you using the clock driver in your code? The clock driver will release the 32K clock source used by the RTC/app timer&nbsp;when it receives a Softdevice disable request and if the Softdevice only requested the clock source. In that case, you can fix this by calling&nbsp;nrf_drv_clock_lfclk_request(). That&nbsp;informs&nbsp;the driver that&#39;s not only the Softdevice that relies on this clock source.&nbsp;</p><div style="clear:both;"></div>