set custom GAP name failing due wrong max name lengthhttps://devzone.nordicsemi.com/f/nordic-q-a/862/set-custom-gap-name-failing-due-wrong-max-name-lengthI am using the code err_code = sd_ble_gap_device_name_set(&amp;sec_mode, (const uint8_t *)deviceName, nameLen); I have made sure that nameLen is less than BLE_GAP_DEVNAME_MAX_LEN and that deviceName is null terminated at BLE_GAP_DEVNAME_MAX_LEN buten-USTelligent Community 13Mon, 11 Nov 2013 10:30:00 GMTRE: set custom GAP name failing due wrong max name lengthhttps://devzone.nordicsemi.com/thread/4217?ContentTypeID=1Mon, 11 Nov 2013 10:30:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:ca74001f-a4cd-4eed-a4c0-0ed7262dbab4Stefan Birnir Sverrisson<p>If there is not space in your advertising packet for your long device name you could choose to insert it into the scan response packet, which contains additional 31 bytes</p><div style="clear:both;"></div>RE: set custom GAP name failing due wrong max name lengthhttps://devzone.nordicsemi.com/thread/4216?ContentTypeID=1Fri, 08 Nov 2013 23:26:16 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c094b290-86f2-4bd5-8a01-28b30f41c543Frank Zhao<p>I think the UUIDs of three services (a custom one, DIS, and BAS) are packed in there. From the code, I don&#39;t think anything else is in there, except for one more 8 bits worth of flag bits.</p> <p>Why would BLE_GAP_DEVNAME_MAX_LEN be 31 if the maximum for the advertising packet is also 31?</p><div style="clear:both;"></div>RE: set custom GAP name failing due wrong max name lengthhttps://devzone.nordicsemi.com/thread/4215?ContentTypeID=1Fri, 08 Nov 2013 22:40:32 GMT137ad170-7792-4731-bb38-c0d22fbe4515:0e6e14db-2bb4-419b-a0b6-6f69aacd3c4dStefan Birnir Sverrisson<p>My suspicion is that this is a limitation in the length of the advertising packet, which is maximum 31 bytes. What other data is in your advertising packet? Try to reduce other data in your advertising packet and then increase your device name length.</p><div style="clear:both;"></div>