Advertising BLE FOTA service and custom service with Zephyr

RE: Advertising BLE FOTA service and custom service with Zephyr

Einar Thorsrud — Tue, 25 May 2021 08:16:48 GMT

Hi,

Based on what you write this seems to be an issue on the Android side, so you should look more into that. You should always be able to discover all services when doing service discovery.

RE: Advertising BLE FOTA service and custom service with Zephyr

yayembedded — Fri, 21 May 2021 17:51:45 GMT

Hello Einar,

Yes, exactly, the response was -EINVAL when putting both 128 bit UUIDs in the advertising array. If you say there is no need to advertise all UUIDs then maybe I am looking at the wrong place for a solution.

(Edited) This is my actual problem after some digging:

When I run my Android test app (which uses the Nordic BLE SDK), on my Android 9 device there is no issue, but on my Android 7 device, the app fails to retrieve the custom service that is not advertised. It seems that the service discovery is not working

I ran nrfConnect on the Android 7 device and I noticed it also had issues with not being able to discover services on my devices.

Same APK, different result. These devices are commercial OEM tablets. Perhaps there is something wrong with the Android implementation?

RE: Advertising BLE FOTA service and custom service with Zephyr

Einar Thorsrud — Fri, 21 May 2021 12:21:25 GMT

Hi,

Did you check the return value from bt_le_adv_start()? I would expect it was -EINVAL, as the advertising packet will be too big in this case. So you either need to put e.g. the 128 bit UUID in the scan response packet instead, or decide not to advertise all the UUIDs (there is typically no need to advertise all service UUIDs).