8f7df0b49f
With the deprecation of `BT_LE_ADV_OPT_USE_NAME` and `BT_LE_ADV_OPT_FORCE_NAME_IN_AD` samples were updated to not use the macro adding the device name in the advertising/scan response data anymore. Instead the name was explicitly added to the scan response data in `periodic_adv` sample. But because it was using an extended advertiser and was already adding data in the AD, the name should have been put in the advertising data and not the scan response data. Update the sample to add the device name in the advertising data. Signed-off-by: Théo Battrel <theo.battrel@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| src | ||
| CMakeLists.txt | ||
| prj.conf | ||
| README.rst | ||
| sample.yaml | ||
.. _bluetooth-periodic-advertising-sample: Bluetooth: Periodic Advertising ############################### Overview ******** A simple application demonstrating the BLE Periodic Advertising functionality. Requirements ************ * A board with BLE support Building and Running ******************** This sample can be found under :zephyr_file:`samples/bluetooth/periodic_adv` in the Zephyr tree. Use the sample found under :zephyr_file:`samples/bluetooth/periodic_sync` in the Zephyr tree that will scan and establish a periodic advertising synchronization to this sample. See :ref:`bluetooth samples section <bluetooth-samples>` for details.