Connectivity android(bt 4.0) with nrf52832(sd s132v5).https://devzone.nordicsemi.com/f/nordic-q-a/26130/connectivity-android-bt-4-0-with-nrf52832-sd-s132v5Hello. I have some questions. Is it possible stabile work of android device , that has bluetooth 4.0 , with nordic device on base softdevice s132 v 5.0 ? What should i read, if i want to do it? My first experience is connection to nordic deviceen-USTelligent Community 13Mon, 23 Oct 2017 16:22:20 GMTRE: Connectivity android(bt 4.0) with nrf52832(sd s132v5).https://devzone.nordicsemi.com/thread/102966?ContentTypeID=1Mon, 23 Oct 2017 16:22:20 GMT137ad170-7792-4731-bb38-c0d22fbe4515:cafa7d94-2d80-47a6-9094-9b3d0e75a5efO1eg<p>Hi! Thank you! In my case, problem was on side of phone. It doesn&#39;t happen after research again of services in &quot;nrf connect&quot;. Best regards!</p><div style="clear:both;"></div>RE: Connectivity android(bt 4.0) with nrf52832(sd s132v5).https://devzone.nordicsemi.com/thread/102965?ContentTypeID=1Sun, 22 Oct 2017 11:53:09 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f3d4c809-71ea-4320-8c69-24ae3b55c908endnode<p>Sure, BLE is designed backward compatible so fact that you are using Nordic stack which has BT5 features doesn&#39;t mean it cannot work with legacy devices.</p> <p>When it comes to your GATT error(s) there will probably be other problems on that layer, either permissions have changed on Server side or one Client was authorized and second not. Indeed there might be even other rare issue under the hood (e.g. messing up GATT handles so Client might target wrong handle) but from your poor description nothing can be concluded. Get full trace from radio, read it, analyze steps on SM and GATT layer and you will probably find the root cause quickly.</p><div style="clear:both;"></div>