samples: bluetooth: fast_pair: locator_tag: add fw version read log

Added a firmware log to the Fast Pair Locator Tag sample to indicate
that the firmware version is being read. Improved the testing procedure
for Android update notifications by leveraging the new log information.

Ref: NCSDK-33211

Signed-off-by: Kamil Piszczek <[email protected]>

Author: kapi-no

doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst

@@ -277,6 +277,9 @@ Bluetooth Fast Pair samples
 
   * Added possibility to build and run the sample without the motion detector support (with the :kconfig:option:`CONFIG_BT_FAST_PAIR_FMDN_DULT_MOTION_DETECTOR` Kconfig option disabled).
 
+  * Updated the :ref:`fast_pair_locator_tag_testing_fw_update_notifications` section to improve the test procedure.
+    The application provides now an additional log message to indicate that the firmware version is being read.
+
 Cellular samples
 ----------------
 

samples/bluetooth/fast_pair/locator_tag/README.rst

@@ -1106,6 +1106,8 @@ Testing steps for the firmware update notification feature require the `nRF Conn
    * `Google Play Services`_ - ``v25.12.33``
    * `nRF Connect Device Manager`_ - ``v2.5.0``
 
+   Also, ensure that Android notifications are enabled for the `nRF Connect Device Manager`_ application.
+
 .. note::
    You can execute these testing steps in combination with the :ref:`fast_pair_locator_tag_testing_clock_sync` testing steps, as both test variants require you to wait for more than 24 hours.
 
@@ -1122,9 +1124,17 @@ To test this feature, complete the following steps:
       #. Power on the development kit.
       #. |connect_terminal_specific|
       #. Power on your test Android device and unlock it after the smartphone screen is turned on.
-      #. Wait for the Android device to connect to the development kit, read the local firmware version, and disconnect.
+      #. Wait for the device to automatically connect to the development kit and read the local firmware version in the background.
+      #. In the terminal, verify that a message confirming that the firmware version is being read appears::
+
+            DIS Firmware Revision characteristic is being read
+
       #. Observe that you get the Android notification about the new firmware update on your test Android device.
 
+         .. note::
+            Notification delivery on Android may be delayed due to system conditions or background processing.
+            It is recommended to wait up to five minutes before concluding that this test step has failed.
+
          .. figure:: /images/bt_fast_pair_locator_tag_android_fw_update_notification.png
             :scale: 80 %
             :alt: Firmware update notification in the Android notification center
@@ -1147,7 +1157,8 @@ To test this feature, complete the following steps:
       #. Power on the development kit.
       #. |connect_terminal_specific|
       #. Power on your test Android device and unlock it after the smartphone screen is turned on.
-      #. Wait for the Android device to connect to the development kit, read the local firmware version, and disconnect.
+      #. Wait for the device to automatically connect to the development kit and read the local firmware version in the background.
+      #. In the terminal, verify that a message confirming that the firmware version is being read appears.
       #. Observe that you no longer get the Android notification about the new firmware update on your test Android device.
 
    .. group-tab:: nRF54 DKs
@@ -1159,9 +1170,17 @@ To test this feature, complete the following steps:
       #. Power on the development kit.
       #. |connect_terminal_specific|
       #. Power on your test Android device and unlock it after the smartphone screen is turned on.
-      #. Wait for the Android device to connect to the development kit, read the local firmware version, and disconnect.
+      #. Wait for the device to automatically connect to the development kit and read the local firmware version in the background.
+      #. In the terminal, verify that a message confirming that the firmware version is being read appears::
+
+            DIS Firmware Revision characteristic is being read
+
       #. Observe that you get the Android notification about the new firmware update on your test Android device.
 
+         .. note::
+            Notification delivery on Android may be delayed due to system conditions or background processing.
+            It is recommended to wait up to five minutes before concluding that this test step has failed.
+
          .. figure:: /images/bt_fast_pair_locator_tag_android_fw_update_notification.png
             :scale: 80 %
             :alt: Firmware update notification in the Android notification center
@@ -1184,7 +1203,8 @@ To test this feature, complete the following steps:
       #. Power on the development kit.
       #. |connect_terminal_specific|
       #. Power on your test Android device and unlock it after the smartphone screen is turned on.
-      #. Wait for the Android device to connect to the development kit, read the local firmware version, and disconnect.
+      #. Wait for the device to automatically connect to the development kit and read the local firmware version in the background.
+      #. In the terminal, verify that a message confirming that the firmware version is being read appears.
       #. Observe that you no longer get the Android notification about the new firmware update on your test Android device.
 
 Disabling the locator tag

samples/bluetooth/fast_pair/locator_tag/src/main.c

@@ -230,6 +230,15 @@ static bool identifying_info_allow(struct bt_conn *conn, const struct bt_uuid *u
 	return false;
 }
 
+static void gatt_authorized_operation_indicate(struct bt_conn *conn,
+					       const struct bt_gatt_attr *attr)
+{
+	/* This function can be used to indicate important GATT operations to the user. */
+	if (!bt_uuid_cmp(attr->uuid, BT_UUID_DIS_FIRMWARE_REVISION)) {
+		LOG_INF("DIS Firmware Revision characteristic is being read");
+	}
+}
+
 static bool gatt_authorize(struct bt_conn *conn, const struct bt_gatt_attr *attr)
 {
 	bool authorized = true;
@@ -245,6 +254,10 @@ static bool gatt_authorize(struct bt_conn *conn, const struct bt_gatt_attr *attr
 
 	authorized = authorized && identifying_info_allow(conn, attr->uuid);
 
+	if (authorized) {
+		gatt_authorized_operation_indicate(conn, attr);
+	}
+
 	return authorized;
 }