iOS BLE cannot correctly read the model number.

[Leo Mo]

After updating from SDK V2.1.3 OTA to SDK V2.9.0, iOS cannot correctly read data such as the model number, but Android can read it normally.

Turn off Bluetooth in the system, turn it back on, and it can be read normally after connecting.

[Leo Mo]

Hi Simonr,

Thanks, after turning Bluetooth off/on in iOS settings, it can connect to devices and communicate normally.

I can see 'Service Changed' using an Android app.

BR,

Leo Mo

[Simonr]

Hi again Leo

Okay, then it sounds like the Service changed characteristic isn't set correctly. I'll ask one of our iOS experts if they have seen this before. it might help if you were able to get a sniffer trace of what is happening over the air here (both for an Android connection where Service Changed works as expected, and for iOS where it doesn't so we can see what differences there are.

Best regards,

Simon

[Leo Mo]

Hi Simonr,

I have already added the OTA feature to this example: Bluetooth: Peripheral ANCS client.

After upgrading from SDK v2.1.3 (peripheral-ancs-client) to SDK v2.9.0 (peripheral-ancs-client), the Mode Number String read using nRF Connect is still garbled.

Please see the attachment for the code and use the local pm_static file (nrf52840dk_nrf52840)

peripheral_ancs_client_sdk_v2.1.3.zip

peripheral_ancs_client_sdk_v2.9.0.zip

BR,

Leo Mo

[Leo Mo]

Hi Simonr

Sorry, there are many Bluetooth devices nearby and no shielded room, so it's hard to capture the complete communication process.

BR,

Leo Mo

[Simonr]

Hi Leo

Thank you for your patience here. We don't have a specific theory of what is happening here I'm afraid. With the nRF Sniffer for BLE (https://academy.nordicsemi.com/courses/bluetooth-low-energy-fundamentals/lessons/lesson-6-bluetooth-le-sniffer/topic/nrf-sniffer-for-bluetooth-le/) for example, you can select sniffing the address and operations of a specific device, so it should be possible to capture the communication of one specific device even in a busy environment. I think that would help us a lot.

For the information you shared, I haven't found anything obviously wrong with it yet, but I'm not done reviewing it. I will get back to you later this week with more information.

Best regards,

Simon