FMDN upstream part 8: Fast Pair Integration guide update with the FMDN content #15688
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kapi-no
requested review from
alstrzebonski,
divipillai,
annwoj and
mkapala-nordic
github-actions
bot
added
doc-required
Test specificationCI/Jenkins/NRF
CI/Jenkins/integration
Note: This message is automatically posted and updated by the CI |
alstrzebonski
approved these changes
Jun 4, 2024
mkapala-nordic
approved these changes
Jun 4, 2024
|
You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds. Note: This comment is automatically posted by the Documentation Publishing GitHub Action. |
divipillai
reviewed
Jun 4, 2024
| FMDN extension | ||
| ============== | ||
|
|
||
| The FMDN extension leverages the Find My Device network, which is a crowdsourced network consisting of millions of Android devices that use Bluetooth® LE to detect missing devices and report their approximate locations back to their owners. |
There was a problem hiding this comment.
Suggested change
| The FMDN extension leverages the Find My Device network, which is a crowdsourced network consisting of millions of Android devices that use Bluetooth® LE to detect missing devices and report their approximate locations back to their owners. | |
| The FMDN extension leverages the Find My Device network, which is a crowdsourced network consisting of millions of Android devices that use Bluetooth LE to detect missing devices and report their approximate locations back to their owners. |
Trademark already mentioned in the docs.
Comment on lines
+260
to
+262
| * The :c:func:`bt_fast_pair_fmdn_info_cb_register` function (optional) | ||
| * The :c:func:`bt_fast_pair_fmdn_ring_cb_register` function (mandatory with the Kconfig configuration for at least one ringing component) | ||
| * The :c:func:`bt_fast_pair_fmdn_read_mode_cb_register` function (optional) |
There was a problem hiding this comment.
These functions don't link. Is the reason that the related header files has not yet been merged?
There was a problem hiding this comment.
Discussed on Teams. We plan to merge the FMDN documentation in the follow-up PR
There was a problem hiding this comment.
These links now work in the follow-up PR:
#15729
https://developer.nordicsemi.com/nRF_Connect_SDK_dev/doc/PR-15729/nrf/external_comp/bt_fast_pair.html
Extended the Fast Pair user guide to cover the Find My Device Network extension. Ref: NCSDK-20552 Signed-off-by: Kamil Piszczek <[email protected]>
kapi-no
force-pushed
the
fmdn_upstream_part8_fp_ug_fdmn_update
branch
from
1ac8007
to
1295904
Compare
divipillai
approved these changes
Jun 5, 2024
kapi-no
removed
the
changelog-entry-required
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow-up upstreaming activity for the documentation content after the following PR (DULT documentation):
#15643