You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Updates Personalized Name testing steps documentation, as the bug
on Android has been fixed for Android 16.
Jira: NCSDK-34507
Signed-off-by: Aleksander Strzebonski <[email protected]>
Copy file name to clipboardExpand all lines: samples/bluetooth/fast_pair/input_device/README.rst
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -458,12 +458,13 @@ Personalized Name extension
458
458
Testing Personalized Name extension is described in `Fast Pair Certification Guidelines for Personalized Name`_.
459
459
460
460
.. note::
461
-
To mitigate Android Personalized Name write issues, whenever you change the Personalized Name on an Android phone, perform the following:
461
+
For Android devices running Android 15 or lower, to mitigate Android Personalized Name write issues when you change the Personalized Name, perform the following:
462
462
463
-
* Write the new Personalized Name.
464
-
* Disconnect the phone from the Fast Pair Provider.
465
-
* Put the Fast Pair Provider in not discoverable advertising mode.
466
-
* The phone reconnects and sends new Personalized Name to the Fast Pair Provider.
463
+
1. Write the new Personalized Name.
464
+
#. Disconnect the phone from the Fast Pair Provider.
465
+
#. Put the Fast Pair Provider in not discoverable advertising mode.
466
+
#. The phone reconnects automatically or you need to reconnect it manually.
467
+
#. The phone sends new Personalized Name to the Fast Pair Provider.
0 commit comments