https://devzone.nordicsemi.com/f/nordic-q-a/17532/add-remove-gatt-service-or-characts-with-bonded-deviceHello, I asked a question after this old one : old one and I read other posts on the subject. I wonder whether explained constraints may have changed or not since I am using SD130 2.0 - SDK11- nRF51422. My point is that I want my GATT server toen-USTelligent Community 13Mon, 14 Nov 2016 09:34:46 GMThttps://devzone.nordicsemi.com/thread/67405?ContentTypeID=1Mon, 14 Nov 2016 09:34:46 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a26c5cf2-b0c6-4de1-8f6c-0380fc527eb2jfDEVmoto<p>I don&#39;t really understand what do you mean with old instances</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/67406?ContentTypeID=1Mon, 14 Nov 2016 07:51:49 GMT137ad170-7792-4731-bb38-c0d22fbe4515:683c56aa-de44-4490-9f9b-38330fc441d2FormerMember<p>To make sure that the allocated flash area never gets full, you can make sure to delete old instances after the service changed.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/67404?ContentTypeID=1Tue, 08 Nov 2016 14:06:58 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7f1d943e-acb1-4c1e-a3b1-692a8cfe821cjfDEVmoto<p>Thanks, I am trying to implement this so I might have further questions on this topic in the future. Today, my concern is about the flash memory. When I indicate the service change in order to force the client to refresh services discovery with bonded device, will this trigger flash memory update on the server side using device manager ? I am concerned about this because my device should have a quite long life and quality of service that might lead to a high number of such refreshes, aproaching flash memory max cycle life.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/67403?ContentTypeID=1Mon, 07 Nov 2016 12:33:23 GMT137ad170-7792-4731-bb38-c0d22fbe4515:10077872-79b2-4e72-b89d-f49a0e4b4915FormerMember<p>As @jfDEVmoto says, service changed should be used indicate to the client that one or more services has been changed.</p> <p>When bonding to a device, the client will typically cache the services on the server side. It will therefore not normally do a service discovery upon a re-connection. When the client and server devices are bonded, and the server has changed one or more services, the service changed indication should be transmitted upon a re-connection, and the client should perform a service discovery procedure.</p> <p>Service changed is described in the Bluetooth Core Specification v. 4.2, Vol 3, Part G, chapter 7.1.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/67402?ContentTypeID=1Fri, 04 Nov 2016 23:37:28 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b351b91c-e6d2-49c0-b211-8e1039fb40e8jfDEVmoto<p>and this :<a href="https://code.google.com/p/android/issues/detail?id=81130">code.google.com/.../detail</a> It looks like the generic attribute service may implement a service changed characteristic to help bonded central to refresh its cache. !!!</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/67401?ContentTypeID=1Fri, 04 Nov 2016 23:32:34 GMT137ad170-7792-4731-bb38-c0d22fbe4515:83bdccdc-7f69-4b29-8fab-9a4ccaef50f6jfDEVmoto<p>I have to check something like that... <a href="http://stackoverflow.com/questions/22596951/how-to-programmatically-force-bluetooth-low-energy-service-discovery-on-android">stackoverflow.com/.../how-to-programmatically-force-bluetooth-low-energy-service-discovery-on-android</a></p><div style="clear:both;"></div>