Fast Pair - Locator Tag Example Failing

[Sri1998]

Hai,

I am trying the fast pair - locator tag example on my nRF52833. I am using SDK version 2.7.0. The code is compiled and flash properly. In the serial terminal getting the following error.

*** Booting nRF Connect SDK v2.7.0-5cb85570ca43 ***
*** Using Zephyr OS v3.6.99-100befc70c74 ***
I: Starting Bluetooth Fast Pair locator tag example
I: 2 Sectors of 4096 bytes
I: alloc wra: 0, fa0
I: data wra: 0, 64
I: SoftDevice Controller build revision: 
I: d6 da c7 ae 08 db 72 6f |......ro
I: 2a a3 26 49 2a 4d a8 b3 |*.&I*M..
I: 98 0e 07 7f             |....    
I: HW Platform: Nordic Semiconductor (0x0002)
I: HW Variant: nRF52x (0x0002)
I: Firmware: Standard Bluetooth controller (0x00) Version 214.51162 Build 1926957230
I: No ID address. App must call settings_load()
I: Bluetooth initialized
I: Identity[0]: C4:C2:C5:C4:0E:C8 (random)
I: Identity[1]: EE:52:78:75:F6:39 (random)
I: HCI: version 5.4 (0x0d) revision 0x11fb, manufacturer 0x0059
I: LMP: version 5.4 (0x0d) subver 0x11fb
I: Settings loaded
I: FMDN: setting battery level to 100 %
I:      FMDN level: Normal
I:      DULT level: Full
I: Fast Pair: RPA expired
I: Fast Pair: setting RPA timeout to 759 [s]
I: Fast Pair: prepared the advertising set
E: Invalid content of the Fast Pair partition
E: modules_init returned error -22
E: FMDN: bt_fast_pair_enable failed (err -22)
E: r0/a1:  0x00000004  r1/a2:  0xe000ed00  r2/a3:  0x20004fb8
E: r3/a4:  0x00000004 r12/ip:  0x00000000 r14/lr:  0x0002fe7b
E:  xpsr:  0x21000000
E: Faulting instruction address (r15/pc): 0x0001836c
E: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0
E: Current thread: 0x20004368 (unknown)
E: Halting system

Can you help me enable the Locator Tag example in nRF52833.

[KevinXu787]

Hello,

I have registered my google account with google and using a google pixel 7 to test with your product. So far with other market products and your fast pair input device example, the pop-up window shows up just fine. However, only with your locator tag example the phone failed to pop up a window to allow for connection. Is there anything in particular about the locator tag example connection process that I should be aware of? Is there a possible explanation, and even better, a solution to this problem? Thank you and do let me know what else you need to locate the problem.

[Edvin]

Hello,

Sorry for the late reply. 

To me, it looks like the fast pair is only used in synchronization mode, and not for the provisioning process. So the find my tag will not use the fast pair popup feature for setting it up.

Best regards,

Edvin

[KevinXu787]

Edvin said:

synchronization mode

Hello, I don't quite understand this. Could you elaborate more on this matter? The same example do trigger pop-ups with other model IDs but not Nordic's particular one 0x4A436B. I wonder what caused this issue? 

[Edvin]

Hello,

I see that you have your own ticket regarding this. I suggest we stick to that one to minimize doubling up the work.

Best regards,

Edvin

[samkris]

Hi,

Our people contacted Google told me that,

Google replied that they will review request  for new device registration only after Dec-2024
- Currently Google is not giving any approval for new devices(For FMDN)

Any thoughts...

Thanks,

Samkris

[Edvin]

This feature is all in hands of Android/Google. There is nothing special about the service/characterstic/advertisements, other than that it holds some key parameters/ID's/UUIDs that Android/Google keeps an eye out for. Whatever they do on their side is out of our control, so if they said that they will not approve new devices, there is not much we can do.

Best regards,

Edvin