Fast Pair Certification FAQ

Validator app/self-test report

Hardware requirements for pre-certification readiness

Validator app/self-test report

I am having issues decrypting the message on the validator app, what can be done to fix this?
Verify whether there is an issue with the HW crypto block.
What is the process for passing certification to be on the list of supported chipsets?
There are two ways to get supported chipsets listed in our developer page. The SoC uses its dev-board to pass the certification or OEMs have products using the chipset and pass the certification. The chipset is then recognized as certified.

Here are actions you need to take before sending samples for certification:

  • Run the validator app on one phone (Pixel series suggested), and make sure that the calibration and end to end integration tests all pass, and then submit the result.
  • See the attached self-test guidelines, which are applicable for both pre-certification and post-certification, and the self-test template.
  • Pairing time measurement: Start counting from the tap to pair UI until the pairing successfully UI shows up on the phone side.
  • Before you start the self-test, verify that the account in the phone has been added to the test group. Click https://groups.google.com/g/fast-pair-partner-test to join the account to the test group.
After the product has been certified and there is a firmware update, what is the approval process?
After the product has been certified, for every firmware update, you must submit the self-test report for approval, and run the validator end-to-end integration test.
Where do I send the self-test report for firmware updates?
If the partner has a firmware update, they can send the self-test report for review to fp_partner_firmware_update@google.com.
Please reach out to your SI for details on the process if applicable.
How many reference phones must be run for initial pairing?
The phones listed in the self-test report are for your reference, and will be used for lab certification. You are not required to use the phones on the list, however you must use at least three different test phones covering different Android versions and brands for the self-test.
Are separate model ID applications required for devices of different color, SKU, etc.?
Yes, you must apply for different model IDs in this case.
If we have different colors for the same product, what is the process for the self-test?
If you have a product with comes in different colors, do a full self-test on one model, and run the validator app to verify that models in all other colors have passed.
Which testing/tabs in the report are required for speakers?
If it's a speaker, you can skip the battery notification and ring the device. Personalized name and retroactive pairing are mandatory.
Are self-test reports required for firmware updates?
Yes. After the product has been certified, all firmware changes require the self-test to be run to verify that Fast Pair remains intact.

Hardware requirements for pre-certification readiness

How many samples are required, and which location should we submit samples to?
Six samples are required in total. Three go to the lab and three to Google US.
What is the process for importing samples from the labs?
You must reach out to the lab separately for their process for importing the samples.
What is the requirement for the samples for testing and certification?
It should be DVT at least. If there are any firmware changes after certification has passed, you must run the self-test report and submit it to Google for review to ensure that there is no impact on Fast Pair before release.
Do we need to fill in any sample submission forms to specify the model ID, FW status, and align with pre-test result?
Please provide these details in the self-test report.
Please see the product marketing flow, and sign up for access to the Partner Marketing Hub if you haven’t already done so. Once you are granted access, you can view the guidelines and download the logos. Once you have designed your Fast Pair related packaging/ marketing materials, please go to ‘Asset Approval’ tab and submit to our marketing team for review
Do I need to take any action upon the issue ticket or quote the issue ID on the report when sending the sample for certification?
Please let us know which lab you will go to for certification. After confirming the lab for your product certification, reach out to the lab with this ticket number.
How do we specify different color versions for the same device going through certification?
You can decide by yourself. We identify via model ID. One type of naming is product name with a suffix indicating color.
For sample submission, do we need to have the same FW version as the self-test report and validator APP run?
The lab will certify the version you run for self-test and validator.
If we have multiple colors and SKUs but the same product name, same HW/FW, and same product image for GFP, how many devices must be added to the console, and for certification?
Add the number of devices from the device console directly. For certification, you can send one model ID for certification, and do the self-test for other model IDs
Where can the model ID anti-spoofing keys be found?
Ensure that your project is registered in the device console. The model ID and anti-spoofing keys can be found in the device console.