The nRF Toolbox cannot find services when I changed the application of PCA10028.

RE: The nRF Toolbox cannot find services when I changed the application of PCA10028.

J.Kwon — Tue, 01 Aug 2017 12:45:42 GMT

Thank you very much.

RE: The nRF Toolbox cannot find services when I changed the application of PCA10028.

Aleksander Nowakowski — Mon, 31 Jul 2017 15:20:24 GMT

Hi this is the cashing issue. Android always cashes services. The service says, that on non-bonded devices, if Service Changed characteristic is present, the services should not be kept, but it is much more common to reconnect to a non-bonded device having the same services as it had before, then connecting to it with new services (for example during developement or dfu) so they decided to store them in the cache despite that. That's why, every time you connect to your DK which has a different fw flashed, Android 'sees' the old services. Please, read more here: devzone.nordicsemi.com/.../

This is such by design. If you want to clear the cache in you app, you may do what the DFU lib is doing here: github.com/.../DfuBaseService.java

If you just want to try with nRF Toolbox, before you connect from the new profile, you have to open nRF Connect app, connect to your device, select Menu->Refresh services. It will clear the cache using the above method and do a new service discovery. Then you may disconnect, open nRF Toolbox (the new profile) and try again. This time the new services will be discovered.

BR, Aleksander

RE: The nRF Toolbox cannot find services when I changed the application of PCA10028.

J.Kwon — Sat, 29 Jul 2017 07:19:48 GMT

I tried re-pair already.. But the nRF app continue to recognize previous services.

RE: The nRF Toolbox cannot find services when I changed the application of PCA10028.

MartinBL — Fri, 28 Jul 2017 13:40:03 GMT

Can you try to go into your Bluetooth settings on your phone and see if there is a list of paired devices? If the list contains your device try unpairing it and start over again with nRF Toolbox.

RE: The nRF Toolbox cannot find services when I changed the application of PCA10028.

J.Kwon — Fri, 28 Jul 2017 07:37:56 GMT

No, subapp(HRS or HTS, ...) isn't important.

the message appear whenever the services of the server(PCA10028) change from HTS to HRS and vice versa.

I want to know method of handling Service Changed Characteristic..

RE: The nRF Toolbox cannot find services when I changed the application of PCA10028.

MartinBL — Fri, 28 Jul 2017 06:56:30 GMT

Ok, maybe I misunderstood your question. In your picture it looks like you are trying to connect to a HRS device using the HTM part of the nRF Toolbox app. That won't work. Try using the HRM part of the app instead.

RE: The nRF Toolbox cannot find services when I changed the application of PCA10028.

J.Kwon — Fri, 28 Jul 2017 03:55:47 GMT

But, nRF Toolbox cannot recognize changed service although I set SOFTDEVICE_GATTS_SRV_CHANGED in softdevice_handler.c to 1.

Do I need another code to handle the Service Changed Characteristic in GATT?

RE: The nRF Toolbox cannot find services when I changed the application of PCA10028.

MartinBL — Thu, 27 Jul 2017 07:21:32 GMT

Hi,

Your phone might be caching the attribute table with its characteristics and services in your peripheral. This is actually standard procedure according to the BLE specification. The next time the devices connect the phone assumes that nothing has changed. It does this to avoid wasting power by transferring the entire attribute table on each new connection. Usually it helps to either, disable and reenable BLE on your phone, close your current app, open a new Bluetooth app, and then go back to your first app, or reboot your phone. To notify the phone about a new attribute table you can also enable the Service Changed characteristic, though this should be enabled by default in the latest SDKs.