https://devzone.nordicsemi.com/f/nordic-q-a/5352/missing-advertised-device-nameHello, I had to use sd_ble_gap_address_set() to make sure, that a bootloader running on the same device will not be cached on OS/X: static const ble_gap_addr_t gap_addr = { BLE_GAP_ADDR_TYPE_RANDOM_PRIVATE_RESOLVABLE }; check_error( sd_ble_gap_address_seten-USTelligent Community 13Wed, 04 Feb 2015 16:28:35 GMThttps://devzone.nordicsemi.com/thread/18694?ContentTypeID=1Wed, 04 Feb 2015 16:28:35 GMT137ad170-7792-4731-bb38-c0d22fbe4515:08d047be-dbcb-4cdd-88a2-8769370bbb31Torsten Robitzki<p>No, unfortunatelly I don&#39;t have access to an android or windows machine. I&#39;ve observed the same, missing name, when writing a native os/x central using the objectiv C api. But that could, of cause be an issue with the apple implementation of the BLE stack. I&#39;ve asked here in the forum because I&#39;m unsure, whom to blame ;-) Maybe some otheres could contribute similar observations.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/18693?ContentTypeID=1Wed, 04 Feb 2015 12:23:24 GMT137ad170-7792-4731-bb38-c0d22fbe4515:af47f6ba-e5d0-4d25-8d92-dae91f676982Petter Myhre<p>Have you tried this with other central devices? Windows or Android?</p> <p>If the issue only occurs in BLExplr it is diffucult to say what the problem could be, since this is a 3rd party product that we have limited knowledge about.</p><div style="clear:both;"></div>