https://devzone.nordicsemi.com/f/nordic-q-a/942/bondmanager-and-schedulerI took the ble_app_proximity as an example. Before I introduced the scheduler it worked ( not always but reasonably well). I added APP_SCHED_INIT(SCHED_MAX_EVENT_DATA_SIZE, SCHED_QUEUE_SIZE); to the main init. I added app_sched_execute(); to theen-USTelligent Community 13Wed, 20 Nov 2013 13:46:43 GMThttps://devzone.nordicsemi.com/thread/4518?ContentTypeID=1Wed, 20 Nov 2013 13:46:43 GMT137ad170-7792-4731-bb38-c0d22fbe4515:64dc7d7d-92ed-4d3f-8e9f-d350d7da2df8Ole Morten<p>The bond manager&#39;s event handler is not required to make things work.</p> <p>By default app_error_handler on top of main contains a reset, but I&#39;d recommend you to remove that for development and instead use an infinite loop (or ble_debug_assert_handler). This should make it possible for you to see what kind of error occurs, and better be able to debug the problem.</p> <p>If this does not help you, can you please supply the error code and line number/file the error handler points at (if any), and the full source code of your modified app?</p> <p>Edit: Clarified that it is the bond manager&#39;s event handler that&#39;s not required. You do need the bond manager to support bonding (unless you want to reimplement its functionality yourself, which I would strongly recommend you not to.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/4517?ContentTypeID=1Wed, 20 Nov 2013 10:58:40 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c356c8d8-bbff-4de7-b51c-f053eb4049faLeon Schmetz<p>I saw that the bondmanager init structure also has room for an event handler. This is not implemented in the proximity demo.</p> <p>Might this be the cause of the troubles?</p><div style="clear:both;"></div>