Stay organized with collections
Save and categorize content based on your preferences.
Personalized Name
The Seeker can write a personalized name to the Provider during the first
pairing and when the user edits the name on the Seeker side. The Provider shall
allocate space, at least 64 bytes, to store the personalized name.
Writes to Additional Data characteristic with personalized
name may happen in 2 flows:
- After initial pairing, the Seeker may write a personalized name to the
Provider after writing the account key.
- After a user modifies the personalized name on the Seeker, the Seeker will
write the new name to the Provider:
- handshake from step 1 to step 4 in the above procedure to
identify each other and know which account key will be used for the
encryption and decryption of the name. In Table 1.2.2:
- Set Message type to 0x10
- Set Flag Bit 1 to 1 to indicate it will be followed by
Data characteristic.
- Set Data ID of Table 1.2.2 to 0x01 as personalized name.
- write the name to Data characteristic
FE2C1237-8366-4814-8EB0-01DE32100BEA
.
The Provider should notify to Additional Data characteristic
with personalized name when it is requested via Bit 2 in
Table 1.2.1.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-12 UTC.
[null,null,["Last updated 2025-08-12 UTC."],[[["\u003cp\u003eSeekers can personalize the name of their Provider device during initial pairing and anytime after.\u003c/p\u003e\n"],["\u003cp\u003eThe Provider device securely stores the personalized name, allocating at least 64 bytes for it.\u003c/p\u003e\n"],["\u003cp\u003eName updates are communicated via the Additional Data characteristic following a secure handshake process.\u003c/p\u003e\n"],["\u003cp\u003eProviders can be prompted to share the personalized name using a specific flag in the data exchange.\u003c/p\u003e\n"]]],[],null,["Personalized Name\n-----------------\n\nThe Seeker can write a personalized name to the Provider during the first\npairing and when the user edits the name on the Seeker side. The Provider shall\nallocate space, at least 64 bytes, to store the personalized name.\n\nWrites to [Additional Data characteristic](/nearby/fast-pair/specifications/characteristics#AdditionalData \"Characteristic: Addiitonal Data\") with personalized\nname may happen in 2 flows:\n\n1. After initial pairing, the Seeker may write a personalized name to the Provider after writing the account key.\n2. After a user modifies the personalized name on the Seeker, the Seeker will write the new name to the Provider:\n 1. handshake from step 1 to step 4 in the above [procedure](/nearby/fast-pair/specifications/service/gatt#procedure \"GATT Procedure\") to identify each other and know which account key will be used for the encryption and decryption of the name. In [Table 1.2.2](/nearby/fast-pair/specifications/characteristics#table1.2.2 \"Table 1.2.2\"):\n 1. Set Message type to 0x10\n 2. Set Flag Bit 1 to 1 to indicate it will be followed by Data characteristic.\n 3. Set Data ID of [Table 1.2.2](/nearby/fast-pair/specifications/characteristics#table1.2.2 \"Table 1.2.2\") to 0x01 as personalized name.\n 2. write the name to Data characteristic `FE2C1237-8366-4814-8EB0-01DE32100BEA`.\n\nThe Provider should notify to [Additional Data characteristic](/nearby/fast-pair/specifications/characteristics#AdditionalData \"Characteristic: Addiitonal Data\")\nwith personalized name when it is requested via Bit 2 in\n[Table 1.2.1](/nearby/fast-pair/specifications/characteristics#table1.2.1 \"Table 1.2.1\")."]]