Attachments (0)
Nordic Case Info
  • Case ID: 342983
Options
Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs

fast pair connects but fails to add to find my device

andrew-identita

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.

Parents
  • 0

    Hi andrew-identita,

    I am using Zephyr 2.9.0 with the sdk-nrf repo v2.9-branch checked out.

    This is a little strange description of an SDK. How did you install this?

    Since this is about an unmodified sample, I would like to reproduce and test this myself, but I am missing some prerequisites. Could you please try again with a specific release of the nRF Connect SDK? There are a few ways to install it, described here: Installation.

    Hieu

  • 0 in reply to Hieu

    This was a standard installation ... literally following the instructions you listed. when I say I am using the v2.9-branch, it just means that I'm using that specific branch (checking out the specific branch as described in the instructions).

    Building the firmware and flashing it was literally just navigating to nrf/samples/bluetooth/fast_pair/locator_tag and then running west zephyr-export, west build -b nrf52840dk/nrf52840 (or west build -b nrf54l15dk/nrf54l15/cpuapp for the nRF54L15 dev board) and then west flash. 

    I'm pretty sure I'm not doing anything weird to build the code.

  • 0 in reply to andrew-identita

    It was a little odd to me that you are using the v2.9-branch instead of a fixed release. However, I checked the difference and there shouldn't be any impactful change between v2.9.1 and the current v2.9-branch head.

    I will try to reproduce and follow up with you in 1-2 working days.

Reply
  • 0 in reply to andrew-identita

    It was a little odd to me that you are using the v2.9-branch instead of a fixed release. However, I checked the difference and there shouldn't be any impactful change between v2.9.1 and the current v2.9-branch head.

    I will try to reproduce and follow up with you in 1-2 working days.

Children
  • 0 in reply to Hieu

    Unfortunately, I cannot reproduce the issue with NCS v2.9.1. At the bottom is my log where the device can be added to my phone successfully, and I also tested the play sound feature successfully.

    We are unfortunately out of clue now. Can I ask you to test with NCS v2.9.1, and if that still failed, test with another phone?

Terms of service