Custom integration of DIS service fails on Android 16

RE: Custom integration of DIS service fails on Android 16

Fryderyk — Fri, 12 Dec 2025 10:09:18 GMT

We have tested this on two Android 16 devices using three different applications: nRF Connect, our own app, and another BLE application (BLE Scanner – Connect & Notify). On both devices, none of the applications were able to detect any services.

For reference, the build number for one of the Android 16 devices is BP4A.251205.006.

Currently, we do not have a minimal example project that reproduces this issue, but I will prepare one and share it with you as soon as possible.

RE: Custom integration of DIS service fails on Android 16

Einar Thorsrud — Fri, 12 Dec 2025 08:31:54 GMT

Hi,

I am sorry for the delay. We have not seen or heard about any such issue. My understanding is that you are testing with nRF Connect for Mobile, and not your own Android app. Is that correct? If so, there is something else that somehow trigger this, but I am not able to say what.

Which exact Android 16 version are you using now? And are there any Android 16 devices where you do not see this issue? Do you have firmware that can reproduce this on a DK so that we can see if we are able to reproduce with that?

RE: Custom integration of DIS service fails on Android 16

Fryderyk — Fri, 12 Dec 2025 06:38:05 GMT

Hi,
Just checking in — were you maybe able to find out anything from the Android team about the issue I mentioned earlier?

RE: Custom integration of DIS service fails on Android 16

Einar Thorsrud — Wed, 26 Nov 2025 13:30:38 GMT

Hi,

I am not able to explain this. I am checkign internally to see if any of our Android developers has come across this and will get back to you on that.

RE: Custom integration of DIS service fails on Android 16

Fryderyk — Tue, 25 Nov 2025 08:39:02 GMT

Hi,

I have uploaded the sniffer traces in the attached documents captured using Wireshark.

About the logs on the nRF side — I have attached two txt files in the first message, which contain the RTT logs from the nRF. In the prj.conf file I enabled belows kconfig, and I don’t see any errors coming from the nRF.

CONFIG_BT_ATT_LOG_LEVEL_DBG=y
CONFIG_BT_GATT_LOG_LEVEL_DBG=y
CONFIG_BT_SETTINGS_LOG_LEVEL_DBG=y

devzone.nordicsemi.com/.../Android-12.pcapng devzone.nordicsemi.com/.../desktop.pcapng devzone.nordicsemi.com/.../Android-16.pcapng devzone.nordicsemi.com/.../iphone-IOS18_5F00_5.pcapng

RE: Custom integration of DIS service fails on Android 16

Fryderyk — Mon, 24 Nov 2025 14:24:13 GMT

Hi,

Thanks for your response.

I can confirm that nRF Connect on iOS and nRF Connect for Desktop Bluetooth Low Energy Standalone v4.0.4 correctly discovers the DIS service.

Tomorrow, I will provide logs captured using Wireshark with:

Android 16 phone <-> my device , which is the device where we are experiencing the problem.
Older Android device <-> my device.
nRF Connect on iOS / nRF Connect for Desktop Bluetooth Low Energy Standalone v4.0.4 <-> my device.

RE: Custom integration of DIS service fails on Android 16

Einar Thorsrud — Mon, 24 Nov 2025 14:00:46 GMT

Hi,

DIS in it self should not cause any problems and is normally used by most devices. Do you have debug logging on the nRF side? Are there any errors indicated in the log?

Can you make a sniffer trace of both cases so that we see the exchange between the nRF and Android on air? Also, in the failing case with DIS, are the services discoverable using nRF Connect on iOS or Desktop? If so, can you make a sniffer trace of that as well?