.. _nrf_bm_release_notes_2099: Changelog for |BMlong| v2.0.99 ############################## This changelog reflects the most relevant changes from the latest official release. Changelog ********* The following sections provide detailed lists of changes by component. SDK installation ================ No changes since the latest nRF Connect SDK Bare Metal release. S115 SoftDevice =============== No changes since the latest nRF Connect SDK Bare Metal release. S145 SoftDevice =============== No changes since the latest nRF Connect SDK Bare Metal release. SoftDevice Handler ================== No changes since the latest nRF Connect SDK Bare Metal release. Boards ====== No changes since the latest nRF Connect SDK Bare Metal release. Build system ============ No changes since the latest nRF Connect SDK Bare Metal release. Interrupts ========== No changes since the latest nRF Connect SDK Bare Metal release. Logging ======= No changes since the latest nRF Connect SDK Bare Metal release. Drivers ======= No changes since the latest nRF Connect SDK Bare Metal release. Subsystems ========== Storage ------- No changes since the latest nRF Connect SDK Bare Metal release. Filesystem ---------- No changes since the latest nRF Connect SDK Bare Metal release. Libraries ========= * :ref:`lib_ble_conn_params`: * Added: * Support for selecting more than one PHY mode (1M, 2M, and Coded) when setting the PHY mode preference with Kconfig. * Support for the :c:macro:`BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST` SoftDevice event. * Updated the :c:func:`ble_conn_params_phy_radio_mode_set` function to return :c:macro:`NRF_ERROR_INVALID_PARAM` if the ``phy_pref`` parameter contains PHY modes not supported by the SoftDevice. * Updated the :c:func:`ble_conn_params_override` function to allow runtime overrides of the acceptable connection parameter window used when validating peripheral requests to change the connection parameters. Previously, this window was set statically by Kconfig options and was not possible to override at runtime. * Fixed: * An issue where the :c:func:`ble_conn_params_phy_radio_mode_get` function would incorrectly return the PHY mode mask of a pending update rather than the currently active PHY mode if a PHY update initiated by the :c:func:`ble_conn_params_phy_radio_mode_set` function was still in progress. * An issue where the SoftDevice define :c:macro:`BLE_GAP_PHYS_SUPPORTED` was used instead of the PHY preferences set with Kconfig when initiating or responding to a PHY update procedure. * :ref:`lib_ble_adv` library: * Added the :c:func:`ble_adv_data_manufacturer_data_find` function to locate manufacturer-specific data in an advertising payload and prefix-match it against a target value. * :ref:`lib_ble_scan` library: * Added: * Support for filtering by manufacturer-specific data using the :c:macro:`BLE_SCAN_MANUFACTURER_DATA_FILTER` filter type. * The :kconfig:option:`CONFIG_BLE_SCAN_MANUFACTURER_DATA_COUNT` and :kconfig:option:`CONFIG_BLE_SCAN_MANUFACTURER_DATA_MAX_LEN` Kconfig options to configure the manufacturer data filter capacity and maximum payload length. Bluetooth LE Services --------------------- * :ref:`lib_ble_scan` * Changed :c:member:`ble_scan_filter_data.addr_filter.addr` and :c:member:`ble_scan_filter_data.name_filter.name` to ``const`` in the :c:struct:`ble_scan_filter_data` structure. Libraries for NFC ----------------- No changes since the latest nRF Connect SDK Bare Metal release. Utils ----- No changes since the latest nRF Connect SDK Bare Metal release. Samples ======= Peripheral samples ------------------ * Added the :ref:`radio_test` sample. Bluetooth LE samples -------------------- * Updated the following samples and applications that do not support pairing to call the :c:func:`sd_ble_gatts_sys_attr_set` function only in response to the :c:macro:`BLE_GATTS_EVT_SYS_ATTR_MISSING` event and not as a response to a :c:macro:`BLE_GAP_EVT_CONNECTED` event: * :ref:`ug_dfu_firmware_loader` (Bluetooth LE) * :ref:`ble_lbs_sample` * :ref:`ble_nus_sample` * :ref:`ble_mcuboot_recovery_entry_sample` * Removed the authentication status logging from the following samples and applications that do not support pairing (do not use the :ref:`lib_peer_manager` library): * :ref:`ug_dfu_firmware_loader` (Bluetooth LE) * :ref:`ble_lbs_sample` * :ref:`ble_nus_sample` * :ref:`ble_pwr_profiling_sample` * :ref:`ble_mcuboot_recovery_entry_sample` * :ref:`ble_cgms_sample` sample: * Removed the call to the :c:func:`sd_ble_gatts_sys_attr_set` function from the main source file. The :ref:`lib_peer_manager` library takes care of calling this function when :ref:`lib_peer_manager` is used. * :ref:`ble_hrs_sample` sample: * Removed redundant logging of authentication status from the main source file. Authentication status is logged by :ref:`lib_peer_manager` library. * :ref:`ble_nus_central_sample` sample: * Fixed the disconnect button handler to only disconnect on button press, and not on button release. * :ref:`ble_hrs_central_sample` sample: * Fixed: * The disconnect button handler to only disconnect on button press, and not on button release. * The allow list disabling button to only trigger on button press, and not on button release. NFC samples ----------- No changes since the latest nRF Connect SDK Bare Metal release. Peripheral samples ------------------ No changes since the latest nRF Connect SDK Bare Metal release. DFU samples ----------- No changes since the latest nRF Connect SDK Bare Metal release. Subsystem samples ----------------- No changes since the latest nRF Connect SDK Bare Metal release. Known issues and limitations ============================ No changes since the latest nRF Connect SDK Bare Metal release. Documentation ============= No changes since the latest nRF Connect SDK Bare Metal release.