No pop-up on Android when testing Nordic Find My Device example with nRF52DK (nRF52832)

[Daniel Pazzini]

Environment:

• nRF Connect SDK Version: v3.0.2

• nRF Connect Toolchain: v3.0.2

• Board: nRF52DK – nRF52832

• Operating System: Windows 11 Pro – 24H2

• Android Phones:

  • Samsung A55 – Android 15

  • Samsung S20 FE – Android 13
    
    

Device Logs:

*** Booting NCS locator tag v3.0.2-89ba1294ac9b ***
*** Using nRF Connect SDK v3.0.2-89ba1294ac9b ***
*** Using Zephyr OS v4.0.99-f791c49f492c ***
I: Starting Bluetooth Fast Pair locator tag sample
I: 2 Sectors of 4096 bytes
I: alloc wra: 0, f88
I: data wra: 0, 78
I: SoftDevice Controller build revision:
I: 89 9a 50 8a 95 01 9c 58 |..P....X
I: fc 39 d2 c1 10 04 ee 02 |.9......
I: 64 ce 25 be |d.%.
I: HW Platform: Nordic Semiconductor (0x0002)
I: HW Variant: nRF52x (0x0002)
I: Firmware: Standard Bluetooth controller (0x00) Version 137.20634 Build 2617349514
I: No ID address. App must call settings_load()
I: Bluetooth initialized
I: Identity[0]: C9:E0:51:35:57:75 (random)
I: Identity[1]: E0:51:44:C3:F6:18 (random)
I: HCI: version 6.0 (0x0e) revision 0x10f3, manufacturer 0x0059
I: LMP: version 6.0 (0x0e) subver 0x10f3
I: Settings loaded
I: FMDN: setting battery level to 100 %
I: FMDN level: Normal
I: DULT level: Full
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: RPA expired
I: Fast Pair: RPA rotation in the inactive advertising state
I: Fast Pair: setting RPA timeout to 764 [s]
I: Fast Pair: fp_adv module enabled
I: Fast Pair: advertising request from trigger "ui": enable
I: Fast Pair: advertising: enabling
I: Fast Pair: advertising in the discoverable mode
I: Sample has started

Description:
I am currently testing the Find My Device example provided by Nordic. After flashing the device, no pop-up appears on my Android devices when the tag is brought close. The tag is visible in the Bluetooth device list, but the expected Fast Pair UI is not triggered.

Expected Behavior:
When bringing the Android device close to the tag, a pop-up should appear to initiate the pairing or detection process.

Actual Behavior:
No pop-up appears on any of my Android devices, even though the tag shows up in the Bluetooth device list.

Steps to Reproduce:

1. Build the Nordic Find My Device example.

2. Flash it to the board.

3. Power on the board and bring an Android device close to it.

Questions:

• Am I performing the build process incorrectly?

• If the build is correct, what could be causing this behavior?

Build Command:

west build --build-dir c:/ncs/v3.0.2/nrf/samples/bluetooth/fast_pair/locator_tag/build \ c:/ncs/v3.0.2/nrf/samples/bluetooth/fast_pair/locator_tag --pristine \ --board nrf52dk/nrf52832 --sysbuild -- -DNCS_TOOLCHAIN_VERSION=NONE

[Daniel Pazzini]

... In addiction

Installed Find hub app version : 3.1.348-3

[Amanda Hsieh]

Hi, 

Did you register your development email account by completing Google’s device proposal form to enable the FMDN feature on the phone?

See the note in the Testing:

Regards,
Amanda H.

[Daniel Pazzini]

Hi, Amanda.

The google e-mail registration is necessary even for a debug purpose ? 

I mean, At first, I just wanned to validate the demo Anti-Spoofing key and Model ID 

Daniel

[Amanda Hsieh]

Daniel Pazzini said:

The google e-mail registration is necessary even for a debug purpose ? 

Yes, it's required by Google to enable the FMDN feature on the phone.

[Daniel Pazzini]

All right...

Beeing more specifc, is this the doc for e-mail registration?

https://docs.google.com/forms/d/e/1FAIpQLSdAzrYyd-gFk90ghLsZdYkXTH4HkL1VNdgBEUqtaA9UST8lLg/viewform

It seems to be a complete new devie registration, not just a trivial e-mail registration. Just want to be sure that I'm following the correct procedure.