I am using Zephyr 2.9.0 with the sdk-nrf repo v2.9-branch checked out. The locator_tag sample builds without issue and flashes to the nRF54L15-PDK without issue. I have a Moto G 5G that I am testing with, and have it set up in developer mode as well as having "include debug results" enabled. My google account is registered with the developer program.
When I boot the dev board with the locator_tag firmware, I get the half-screen "connect" dialog, and when I tap connect I see it interact with the dev board. The "use responsibly" dialog comes up, but I see that the dev kit has already been disconnected, and tapping "agree and continue" briefly shows something I cannot see because it is so fast, then the "issue connecting" dialog comes up saying "check your internet and Bluetooth connections, then try connecting to the Find My Device again." Trying again just waits forever.
On the devkit console I see the following. Note that *all* of this is printed before I tap on "agree and continue", and nothing is printed afterward. It seems like whatever fast pairing is happening is not getting written to the device, since a reboot of the devkit just does the same again.
What am I missing? I have tried several times, and also tried with an nRF52840 dev kit as well with the same results.
*** Booting NCS locator tag v2.9.0-eaae5ac184e9 *** *** Using nRF Connect SDK v2.9.0-eaae5ac184e9 *** *** Using Zephyr OS v3.7.99-1f8f3dc29142 *** I: Starting Bluetooth Fast Pair locator tag example I: DFU: Firmware version: 2.9.0+0 I: 7 Sectors of 4096 bytes I: alloc wra: 0, e60 I: data wra: 0, b0 I: SoftDevice Controller build revision: I: 79 a3 10 be e6 80 b7 e9 |y....... I: a3 ba cc a9 fc 08 66 12 |......f. I: 90 cf 45 a9 |..E. I: HW Platform: Nordic Semiconductor (0x0002) I: HW Variant: nRF54Lx (0x0005) I: Firmware: Standard Bluetooth controller (0x00) Version 121.4259 Build 3078678206 I: No ID address. App must call settings_load() I: Bluetooth initialized I: Identity[0]: E8:66:EE:5F:C6:47 (random) I: Identity[1]: F2:33:78:AF:BC:D0 (random) I: HCI: version 6.0 (0x0e) revision 0x309a, manufacturer 0x0059 I: LMP: version 6.0 (0x0e) subver 0x309a I: Settings loaded I: FMDN: setting battery level to 100 % I: FMDN level: Normal I: DULT level: Full I: Performing reset to factory settings... I: Factory Reset: resetting Bluetooth identity within the factory reset I: Reset to factory settings has completed D: FMDN State: TX power set to 0 [dBm] D: FMDN State: enabled D: Motion detector is not running: owner nearby I: DULT enabled D: Fast Pair is enabled I: Fast Pair: prepared the advertising set I: Fast Pair: fp_adv module enabled I: SI: Fast Pair: RPA expired I: Fast Pair: setting RPA timeout to 777 [s] ample has started I: FMDN: state changed to unprovisioned I: The device has been reset to factory settings I: Please press a button to put the device in the Fast Pair discoverable advertising mode I: Fast Pair: advertising request from trigger "ui": enable I: Fast Pair: advertising: enabling I: Fast Pair: advertising in the discoverable mode I: Connected D: Key-based Pairing write: res=80 conn=0x20002780 D: Account Key stored I: Fast Pair: Account Key write I: Fast Pair: advertising request from trigger "fmdn_provisioning": enable I: Fast Pair: advertising: enabling I: Fast Pair: automatically switched to non-discoverable advertising mode I: Fast Pair: advertising inactive due to an active connection D: Account Key write: res=16 conn=0x20002780 D: Beacon Actions GATT Read Request D: Beacon Actions: challenge-response enabled for the next write: D: ec bb 0e 43 12 2d 6b cc |...C.-k. D: Beacon Actions read: res=9 conn=0x20002780 I: Beacon Actions CCCD write, handle: 0, value: 0x0001 D: Beacon Actions GATT Write Request: D: 01 08 63 ed f0 7a 01 9e |..c..z.. D: 40 c1 |@. D: Beacon Actions: consuming random nonce read operation D: Beacon Actions response: D: 01 09 7e ab ee 8f 15 d6 |..~..... D: 0b 68 02 |.h. D: Beacon Actions write: res=10 conn=0x20002780 I: Beacon Actions CCCD write, handle: 0, value: 0x0000 I: Disconnected (reason 19) I: Fast Pair: advertising in the non-discoverable mode I: Connected D: Beacon Actions GATT Read Request D: Beacon Actions: challenge-response enabled for the next write: D: 8b 29 5c 01 10 0e 63 c2 |.)\...c. D: Beacon Actions read: res=9 conn=0x20002780 I: Beacon Actions CCCD write, handle: 0, value: 0x0001 D: Beacon Actions GATT Write Request: D: 01 08 6c 9f d9 ff bb f2 |..l..... D: 21 42 |!B D: Beacon Actions: consuming random nonce read operation D: Beacon Actions response: D: 01 09 1c 9d b5 7d b3 74 |.....}.t D: c3 37 02 |.7. D: Beacon Actions write: res=10 conn=0x20002780 I: Beacon Actions CCCD write, handle: 0, value: 0x0000 I: Disconnected (reason 19) I: Fast Pair: advertising in the non-discoverable mode
