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

[J.Kwon]

My android version is the Kitkat.

The nRF Toolbox cannot find services when I changed the application of PCA10028 for example from ble_app_hts to ble_app_hrs.

The message below appeared.

The result of observing with the Android message is that the android recognize previous services although the PCA10028 sent the information of changed services.

After rebooting the smartphone, it will work normally.

What is the problem?

[MartinBL]

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.

[J.Kwon]

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?

[MartinBL]

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.

[J.Kwon]

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..

[MartinBL]

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.