https://devzone.nordicsemi.com/f/nordic-q-a/16607/advertising-service-with-128-bit-uuidHello everyone, I have 2 chip; Bluegiga and nRF51-DK I can easily advertise my custom service in Bluegiga chip. As you can see, nRF Connect application shows my service so that i can scan peripherals with service and connect via IOS applicationen-USTelligent Community 13Mon, 26 Sep 2016 06:50:40 GMThttps://devzone.nordicsemi.com/thread/63531?ContentTypeID=1Mon, 26 Sep 2016 06:50:40 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c3915fd3-e396-4fd7-bf46-de8c55ec2343Hakan<p>Sorry for late answer.</p> <p>I found the solution in experimental_app_ble_blinky source code. I added UUID to the response data. Now I can scan and connect with IOS and Android using service UUID.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/63530?ContentTypeID=1Fri, 23 Sep 2016 10:09:20 GMT137ad170-7792-4731-bb38-c0d22fbe4515:62e73604-54dc-4445-a98f-b8db59ee8f9dOle Bauck<p>Do you want to advertise only the 128 UUID or also service data? The ble_app_uart example in the SDK shows how to advertise a 128bit UUID. It places it in the scan response packet, but you should be able to put it in the advertising packet in the same way if there is enough space (advertisement packet can have maximum 31 bytes of data).</p> <p>Actually it does not look like you have enough space in the advertisement packet. The size of your packet will be: 8 (device name) + 3 (flags) + 4 (16 bit uuids) + 18 (128 bit uuids) = 33 bytes. See <a href="https://devzone.nordicsemi.com/question/37952/setting-tx_power_level/?answer=37997#post-id-37997">here</a> for explanation. Do you try to put it all in one packet?</p><div style="clear:both;"></div>