https://devzone.nordicsemi.com/f/nordic-q-a/35006/advertising-and-disconnection-issues-after-portingHi, I have recently ported from SDK12 to SDK14.2. We have a custom android app which connects to nRF52832. The correct sequence of events in BLE should be - Fast advertisement - Slow Advertisement(if not connected for 2 mins) - Connection en-USTelligent Community 13Mon, 04 Jun 2018 14:37:00 GMThttps://devzone.nordicsemi.com/thread/134598?ContentTypeID=1Mon, 04 Jun 2018 14:37:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:faf1da69-d1a7-427b-ae3d-38ab718e3379arai<p>ok I will try this and let you know. Thanks</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/134487?ContentTypeID=1Mon, 04 Jun 2018 08:59:39 GMT137ad170-7792-4731-bb38-c0d22fbe4515:62ea4a9f-1010-4ed5-9348-1bf9098e79a2Einar Thorsrud<p>Hi,</p> <p>I would be surprised if it starts advertising before it has disconnected if your application is similar to the SDK example (though it would be possible). Do you see the order of events from the central device, a sniffer or the nRF? If not from the nRF, can you enable logging on the nRF side and log the BLE events there? What is the disconnect reason seen from the nRF?</p> <p>What is the state of the nRF when you write that the system hangs? Can you check with a debugger? Enabling logging could be useful to understand this as well.</p><div style="clear:both;"></div>