https://devzone.nordicsemi.com/f/nordic-q-a/71725/how-to-save-services-and-characteristics-configuration-of-a-particular-ble-deviceHi, I&#39;m using the BLE_app_interactive example as a starting point for my prototype (with SDK_17.0.2 and SoftDevice s132 ). I am using nRF52DK to read and write data from/to BLE characteristics of some commercial devices based on nrf52832 micros, usingen-USTelligent Community 13Wed, 17 Feb 2021 15:45:12 GMThttps://devzone.nordicsemi.com/thread/294922?ContentTypeID=1Wed, 17 Feb 2021 15:45:12 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7497d558-7d2d-4c6f-89e6-e03f00caa7a9Edvin<p>Hello,</p> <p>You can of course hardcode many of these things, but you can try by turning down the connection interval settings in both your devices (remember that it is the central that has the final saying in connection parameters). By decreasing this, it will be quicker to send the packets back and forth to do the service discovery etc.</p> <p>Another thing you can try is to apply bonding in your project. This way, the peer manager will keep track of the services, characteristics and what characteristics that you turned on notifications/indications. If you want to really lower the time it takes, then maybe that is the way to go. Besides from that, it shouldn&#39;t really take that long (couple of seconds). Try the ble_app_uart and ble_app_uart_c example pair, and measure how long it takes before you can send notifications. I am not sure exactly how long it is, but it is not several seconds.</p> <p></p> <p>What is your connection interval, by the way? And from where does your central call&nbsp;ble_db_discovery_start()?</p> <p></p> <p>Best regards,</p> <p>Edvin</p><div style="clear:both;"></div>