Central Address Resolution?

RE: Central Address Resolution?

run_ar — Fri, 03 Mar 2017 15:39:53 GMT

I guess you could take a look at this. The change address "fix" also works for iOS as it will show as a new device.

RE: Central Address Resolution?

AndreaO — Fri, 03 Mar 2017 13:47:26 GMT

Is there any workaround at app level (iOS, Android) to permit the firmware update from the old soft device to the new one without asking the user to manually reset Bluetooth (to reset the BLE cache) in the middle of update procedure (just after SD+BL update and before application update)?

RE: Central Address Resolution?

run_ar — Fri, 03 Mar 2017 12:53:16 GMT

Not really, the central address resolution is part of the generic access service which is placed before the Generic attribute service (that contains the service changed indication characteristic) in the attribute table. This means the attribute handle of the service changed characteristic will also change after the DFU.

RE: Central Address Resolution?

AndreaO — Fri, 03 Mar 2017 12:46:01 GMT

Do you think is it possible to implement the Service Changed characteristic, to force a cache reconstruction just after the reconnection?

RE: Central Address Resolution?

run_ar — Fri, 03 Mar 2017 12:04:34 GMT

Unfortunately I cannot see any way to disable this, but I will check internally if there is anything we can do about it. For now I'm afraid you will have to manually reset the cache (This can be done programatically on android, but on iOS it requires user action, not sure about windows).