first commit

This commit is contained in:
魏风
2026-05-01 10:06:36 +08:00
commit e29d75e367
129 changed files with 1485 additions and 0 deletions

View File

@@ -0,0 +1,45 @@
# 1.1 Project 工程enable对应功能 {#project-工程enable对应功能}
::: {.Section1}
app_flags.h 里面找到 [CONFIG_REALTEK_GFPS_XXX 相关的宏并按照以下信息配置:]{style="color: rgb(166,38,164);"}
\#define CONFIG_REALTEK_GFPS_FEATURE_SUPPORT                         1\
\#define CONFIG_REALTEK_GFPS_LE_DEVICE_SUPPORT                      (0 && CONFIG_REALTEK_GFPS_FEATURE_SUPPORT)\
\#define CONFIG_REALTEK_GFPS_SASS_SUPPORT                              (0 && CONFIG_REALTEK_GFPS_FEATURE_SUPPORT)\
\#define CONFIG_REALTEK_GFPS_FINDER_SUPPORT                          (0 && CONFIG_REALTEK_GFPS_FEATURE_SUPPORT)
GFPS依赖的其他的模块
\#if CONFIG_REALTEK_GFPS_FEATURE_SUPPORT\
\#undef F_APP_RWS_BLE_USE_RPA_SUPPORT\
\#define F_APP_RWS_BLE_USE_RPA_SUPPORT                                   1
\#undef F_APP_SC_KEY_DERIVE_SUPPORT\
\#define F_APP_SC_KEY_DERIVE_SUPPORT                                        1\
\#endif
\
Note:
有的IC宏的名字是GFPS_XXX, [app_flags.h 里面找到 [GFPS_XXX 相关的宏并按照以下信息配置:]{style="color: rgb(166,38,164);"}]{style="color: rgb(152,104,1);"}
\#define GFPS_FEATURE_SUPPORT                                                   1\
\#define GFPS_LE_DEVICE_SUPPORT                                                (0 && GFPS_FEATURE_SUPPORT)\
\#define GFPS_SASS_SUPPORT                                                        (0 && GFPS_FEATURE_SUPPORT)\
\#define GFPS_FINDER_SUPPORT                                                    (0 && GFPS_FEATURE_SUPPORT)
GFPS依赖的其他的模块
\#if GFPS_FEATURE_SUPPORT\
\#undef F_APP_RWS_BLE_USE_RPA_SUPPORT\
\#define F_APP_RWS_BLE_USE_RPA_SUPPORT               1
\#undef F_APP_SC_KEY_DERIVE_SUPPORT\
\#define F_APP_SC_KEY_DERIVE_SUPPORT                   1\
\#endif
\
\
:::

View File

@@ -0,0 +1,4 @@
# 1.2 测试环境搭建 {#测试环境搭建}
::: {.Section1}
:::

View File

@@ -0,0 +1,230 @@
# 1.2.1 设备端环境搭建 {#设备端环境搭建}
:::: {.Section1}
`<style type="text/css">/**/
div.rbtoc1777598888652 {padding: 0px;}
div.rbtoc1777598888652 ul {margin-left: 0px;}
div.rbtoc1777598888652 li {margin-left: 0px;padding-left: 0px;}
/**/</style>`{=html}
::: {.toc-macro .rbtoc1777598888652}
- [1 MCUConfigTool 配置](#id-1.2.1设备端环境搭建-1MCUConfigTool配置)
- [1.1 General 页面 : 不勾选 Enable auto power off, 不勾选 Enable pairing timeout](#id-1.2.1设备端环境搭建-1.1General页面:不勾选Enableautopoweroff,不勾选Enablepairingtimeout)
- [1.2 General 页面 : Discoverable in standby mode 设置成disable。强制要求必须修改](#id-1.2.1设备端环境搭建-1.2General页面:Discoverableinstandbymode设置成disable。强制要求必须修改)
- [1.3 General 页面: 勾选 Non-discoverable when linkback 强制要求必须修改](#id-1.2.1设备端环境搭建-1.3General页面:勾选Non-discoverablewhenlinkback强制要求必须修改)
- [1.4 勾选Multi-link support, 并且不要勾选 Enter pairing state while only available device is connected 强制要求必须修改](#id-1.2.1设备端环境搭建-1.4勾选Multi-linksupport,并且不要勾选Enterpairingstatewhileonlyavailabledeviceisconnected强制要求必须修改)
- [1.5 Third Party页面配置GFPS参数](#id-1.2.1设备端环境搭建-1.5ThirdParty页面配置GFPS参数)
- [1.6 配置GFPS findme voice prompt tone](#id-1.2.1设备端环境搭建-1.6配置GFPSfindmevoiceprompttone)
- [1.7 保存新生成的 APP UI Parameter File 和 System Config File](#id-1.2.1设备端环境搭建-1.7保存新生成的APPUIParameterFile和SystemConfigFile)
- [1.8 Note](#id-1.2.1设备端环境搭建-1.8Note)
- [1.建议把BD Address和Device Name也改一下](#id-1.2.1设备端环境搭建-1.建议把BDAddress和DeviceName也改一下)
- [2.建议Export 生成rcfg之前先导入正确的flash_map.ini](#id-1.2.1设备端环境搭建-2.建议Export生成rcfg之前先导入正确的flash_map.ini)
- [3.因为设备不支援LEA LEA相关的配置要务必关掉](#id-1.2.1设备端环境搭建-3.因为设备不支援LEALEA相关的配置要务必关掉)
- [2 TWS 耳机 GFPS battery feature测试环境搭建(只有TWS耳机需要做GFPS battery测试single mode 不需要测试)](#id-1.2.1设备端环境搭建-2TWS耳机GFPSbatteryfeature测试环境搭建(只有TWS耳机需要做GFPSbattery测试singlemode不需要测试))
- [2.1.mcu config tool 配置:](#id-1.2.1设备端环境搭建-2.1.mcuconfigtool配置)
- [2.1.1 HW Feature 模块](#id-1.2.1设备端环境搭建-2.1.1HWFeature模块)
- [2.1.2 charger 模块勾选battery detection support](#id-1.2.1设备端环境搭建-2.1.2charger模块勾选batterydetectionsupport)
- [2.1.3 general 模块](#id-1.2.1设备端环境搭建-2.1.3general模块)
- [2.2.充电盒配置:](#id-1.2.1设备端环境搭建-2.2.充电盒配置:)
- [2.2.1 接线设置](#id-1.2.1设备端环境搭建-2.2.1接线设置)
- [2.2.2 充电盒操作](#id-1.2.1设备端环境搭建-2.2.2充电盒操作)
- [2.3 Note](#id-1.2.1设备端环境搭建-2.3Note)
- [2.3.1 开关盒操作步骤](#id-1.2.1设备端环境搭建-2.3.1开关盒操作步骤)
- [2.3.2 HUN显示测试](#id-1.2.1设备端环境搭建-2.3.2HUN显示测试)
- [2.3.3 demo rcfg 里面有model id信息不可以直接开给客户](#id-1.2.1设备端环境搭建-2.3.3demorcfg里面有modelid信息不可以直接开给客户)
:::
### 1  MCUConfigTool 配置 {#id-1.2.1设备端环境搭建-1MCUConfigTool配置}
#### 1.1 General 页面 : 不勾选 Enable auto power off, 不勾选 Enable pairing timeout {#id-1.2.1设备端环境搭建-1.1General页面:不勾选Enableautopoweroff,不勾选Enablepairingtimeout}
**Note**:
修改为了便于GFPS测试GFPS 测试的时候或者是过认证的时候需要修改, **量产时可以考虑不修改。**
![](media/1.2.1+设备端环境搭建/a75da87126dabd34a9c54e26b5008fd5.png)
#### 1.2 General 页面 : Discoverable in standby mode 设置成disable。**强制要求必须修改** {#id-1.2.1设备端环境搭建-1.2General页面:Discoverableinstandbymode设置成disable。强制要求必须修改}
**Note**:
GFPS 耳机第一次和一只手机配对成功之后(initial pairing 成功),就会进入 subsequent pairing mode。
所以initial pairing 成功之后不管耳机是进入idle mode 还是进入connectable mode(multilink 支持)都不应该再设置成discoverable。
![](media/1.2.1+设备端环境搭建/a73ebf874561ef037ea7cc0e0eec3c1a.png)
#### 1.3  General 页面: 勾选 Non-discoverable when linkback **强制要求必须修改** {#id-1.2.1设备端环境搭建-1.3General页面:勾选Non-discoverablewhenlinkback强制要求必须修改}
linkback模式下DUT不应该discoverable不然手机端会一直弹配对窗口。   
\
![](media/1.2.1+设备端环境搭建/bd1aae2090097e031e53873968a1d6f4.png)
#### 1.4 勾选Multi-link support, 并且不要勾选 Enter pairing state while only available device is connected  **强制要求必须修改** {#id-1.2.1设备端环境搭建-1.4勾选Multi-linksupport,并且不要勾选Enterpairingstatewhileonlyavailabledeviceisconnected强制要求必须修改}
下面红框里的**不可以勾选  **不然battery HUN测试可能测不过 ** [[BBPRO2BUG-21515](https://jira.realtek.com/browse/BBPRO2BUG-21515){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BBPRO2BUG-21515" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641792_2c9082e76519d09101657ff5cfb3003b"}**
![](media/1.2.1+设备端环境搭建/deb4e2f66d2e71d13625d9a84e02f4a9.png)
#### 1.5 Third Party页面配置GFPS参数 {#id-1.2.1设备端环境搭建-1.5ThirdParty页面配置GFPS参数}
在Third Party页面配置GFPS参数详细信息参考 [mcu cfg tool中 GFPS 各配置项的含义 - BT_Market - WIKI](https://wiki.realtek.com/pages/viewpage.action?pageId=158870786){rel="nofollow"}
![](media/1.2.1+设备端环境搭建/1184039875b1b2e3119c18c9f50f7a86.png)
下面是RTK已通过认证的Module ID
[认证结果及认证通过的model_id 和key](/pages/viewpage.action?pageId=204620689)
#### 1.6 配置GFPS findme voice prompt tone {#id-1.2.1设备端环境搭建-1.6配置GFPSfindmevoiceprompttone}
[gfps_findme.wav](#){.unresolved}
自行选择wav文件作为findme vp tone
wav文件名称可以自行修改放入MCU config tool vp目录
建议findme的wav文件可以播放久一些这样才能达到提示的效果。
如下图所示:
![](media/1.2.1+设备端环境搭建/376350bb02b315be95274cec1b03fa1d.png)
打开MCU config tool开始配置findme tone
首先refresh一下让tool能够识别新的wav文件
然后就可以选择vp tone了
如下图所示:
![](media/1.2.1+设备端环境搭建/c564ca9d4cb3db32c6a593bdda5b3617.png)
![](media/1.2.1+设备端环境搭建/38d2923796490cb846076477f7aa2e6a.png)
#### 1.7 保存新生成的 APP UI Parameter File 和 System Config File {#id-1.2.1设备端环境搭建-1.7保存新生成的APPUIParameterFile和SystemConfigFile}
#### **1.8 Note** {#id-1.2.1设备端环境搭建-1.8Note}
##### 1.建议把BD Address和Device Name也改一下 {#id-1.2.1设备端环境搭建-1.建议把BDAddress和DeviceName也改一下}
##### 2.建议Export 生成rcfg之前先导入正确的flash_map.ini {#id-1.2.1设备端环境搭建-2.建议Export生成rcfg之前先导入正确的flash_map.ini}
![](media/1.2.1+设备端环境搭建/f7cf5e80b139e58c372ee7bd3b58734d.png)
##### 3.因为设备不支援LEA LEA相关的配置要务必关掉 {#id-1.2.1设备端环境搭建-3.因为设备不支援LEALEA相关的配置要务必关掉}
![](media/1.2.1+设备端环境搭建/80bd69652553556fad57c0794099a55d.png)
![](media/1.2.1+设备端环境搭建/4fbd46cb906e3341fd72fa298fa820cf.png)
![](media/1.2.1+设备端环境搭建/51a0e41fdd5cb323f5cd8e5266bbb005.png)
### 2 TWS 耳机 GFPS battery feature测试环境搭建(只有TWS耳机需要做GFPS battery测试single mode 不需要测试) {#id-1.2.1设备端环境搭建-2TWS耳机GFPSbatteryfeature测试环境搭建(只有TWS耳机需要做GFPSbattery测试singlemode不需要测试)}
Note
测试battery的时候需要搭配充电盒
#### 2.1.mcu config tool 配置: {#id-1.2.1设备端环境搭建-2.1.mcuconfigtool配置}
##### 2.1.1 HW Feature 模块 {#id-1.2.1设备端环境搭建-2.1.1HWFeature模块}
       勾选Charger功能
![](media/1.2.1+设备端环境搭建/ea1bba5a0188d660a7843b301bd45575.png)
勾选支持充电盒功能注意如果充电盒image烧录的是20ms,下面红色框中的40ms也要改成20ms,这个要和充电盒image匹配的。
如果充电盒image 烧录的是40ms
![](media/1.2.1+设备端环境搭建/4bf5ee1adce5f42f2850af333c894b14.png)
如果充电盒image烧录的是20ms:\
![](media/1.2.1+设备端环境搭建/89818e83841c7886e8954c77c415deec.png)
勾选power off immediately when chose case和do not auto power off when case not close
![](media/1.2.1+设备端环境搭建/60edd7696c5c11c06f000f97097a3acb.png)
##### 2.1.2 charger 模块勾选battery detection support {#id-1.2.1设备端环境搭建-2.1.2charger模块勾选batterydetectionsupport}
![](media/1.2.1+设备端环境搭建/ec289f7c9f337a00ff4eed1b2731265c.png)
![](media/1.2.1+设备端环境搭建/b5ca29b78d55f32174c569e6d26e9a0b.png)
![](media/1.2.1+设备端环境搭建/500bc6e0f02e7d9c0c068090d4d90310.png)
##### 2.1.3 general 模块 {#id-1.2.1设备端环境搭建-2.1.3general模块}
![](media/1.2.1+设备端环境搭建/2341c78f84b2b1be53683ee2fe88e7cf.png)
2.1.4 third party 模块 enable battery 功能
![](media/1.2.1+设备端环境搭建/524208b2e6abc1f6646aeba14bd59d65.png)
#### 2.2.充电盒配置: {#id-1.2.1设备端环境搭建-2.2.充电盒配置:}
##### 2.2.1 接线设置 {#id-1.2.1设备端环境搭建-2.2.1接线设置}
![](media/1.2.1+设备端环境搭建/2995cee295e29c60b1d5b454ce57ebd0.png)
##### 2.2.2 充电盒操作 {#id-1.2.1设备端环境搭建-2.2.2充电盒操作}
![](media/1.2.1+设备端环境搭建/95b03ee961d34cf393b9e32ceb54e1cd.png)
#### **2.3 Note** {#id-1.2.1设备端环境搭建-2.3Note}
##### 2.3.1 开关盒操作步骤 {#id-1.2.1设备端环境搭建-2.3.1开关盒操作步骤}
1.左右耳factory reset 之后,先按下出盒入盒按钮(确保两个按钮同时按下,代表左右耳机入盒),耳机入盒之后,再按下开盒关盒按钮(按键弹起是开盒)耳机端可以听到power on的提示音说明开盒成功。有时候开盒成功但是没有提示音此时可以看一下log
app_adp_handle_msg +++++ AD2B_CMD_POWER_ON =3如果有AD2B_CMD_POWER_ON的log说明开盒成功
2.按下开盒关盒按钮按键按下是关盒耳机端可以听到power off的提示音说明关盒成功。有时候关盒成功但是没有提示音此时可以看一下log
app_adp_handle_msg +++++ AD2B_CMD_POWER_OFF =4如果有AD2B_CMD_POWER_OFF的log说明关盒成功
3.如果重新烧录app的bin. 烧录完成之后要先按一下reset按键然后按开盒关盒按钮进行操作。
**4.关盒之后3s关机关机之后 3s会 watch dog reset故关盒之后建议等10s才可以再次开盒否则开机流程可能会不正常**
相关代码修改(仅用于GFPS认证)
关盒之后3s关机
\#define ADP_CLOSE_CASE_TIMEOUT_MS                       3000
关机之后打开power off的提示音(目前没有打开,可以不需要修改,使用默认配置就好)
![](media/1.2.1+设备端环境搭建/08271864e4343f90c4a3c604c18353f4.png)
watch dog reset的时间改成6s,目前没有设置成6s,使用默认设置3s目前测试看是ok的所以这个也可以不用修改
![](media/1.2.1+设备端环境搭建/bf3b347414521efeed1e046f0f2a279c.png)
##### 2.3.2 HUN显示测试 {#id-1.2.1设备端环境搭建-2.3.2HUN显示测试}
HUN(Heads up notification)显示图如下:
![](media/1.2.1+设备端环境搭建/12993266da101944d424e1511aee4fc6.png)
一次HUN显示成功之后需要先把上次的显示信息清掉,再执行下一次操作:
![](media/1.2.1+设备端环境搭建/65276f35c42f7a8bfcb298a26c2e6f8d.png)
\
##### 2.3.3 demo rcfg 里面有model id信息不可以直接开给客户 {#id-1.2.1设备端环境搭建-2.3.3demorcfg里面有modelid信息不可以直接开给客户}
[GFPS_Left.rcfg](/download/attachments/139180496/GFPS_Left.rcfg?version=1&modificationDate=1636711808317&api=v2){linked-resource-id="205658521" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="GFPS_Left.rcfg" linked-resource-content-type="application/octet-stream" linked-resource-container-id="139180496" linked-resource-container-version="20"}
[GFPS_Right.rcfg](/download/attachments/139180496/GFPS_Right.rcfg?version=1&modificationDate=1636711808877&api=v2){linked-resource-id="205658522" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="GFPS_Right.rcfg" linked-resource-content-type="application/octet-stream" linked-resource-container-id="139180496" linked-resource-container-version="20"}
\
\
::::

View File

@@ -0,0 +1,154 @@
# 1.2.2 手机端环境搭建 {#手机端环境搭建}
:::: {.Section1}
`<style type="text/css">/**/
div.rbtoc1777598900336 {padding: 0px;}
div.rbtoc1777598900336 ul {margin-left: 0px;}
div.rbtoc1777598900336 li {margin-left: 0px;padding-left: 0px;}
/**/</style>`{=html}
::: {.toc-macro .rbtoc1777598900336}
- [1.手机需要连接google网络](#id-1.2.2手机端环境搭建-1.手机需要连接google网络)
- [2.手机不可以打开勿扰模式,不然可能看不到弹窗](#id-1.2.2手机端环境搭建-2.手机不可以打开勿扰模式,不然可能看不到弹窗)
- [3.检查手机是否打开Google Play服务通知](#id-1.2.2手机端环境搭建-3.检查手机是否打开GooglePlay服务通知)
- [4.检查google play 服务是否更新到最新的版本](#id-1.2.2手机端环境搭建-4.检查googleplay服务是否更新到最新的版本)
- [5.登陆google账号](#id-1.2.2手机端环境搭建-5.登陆google账号)
- [6 打开自动同步数据功能](#id-1.2.2手机端环境搭建-6打开自动同步数据功能)
- [7.检查Show notification是否打开](#id-1.2.2手机端环境搭建-7.检查Shownotification是否打开)
- [8.Setting界面打开蓝牙以及位置信息。](#id-1.2.2手机端环境搭建-8.Setting界面打开蓝牙以及位置信息。)
- [9.Enable debug mode ID](#id-1.2.2手机端环境搭建-9.EnabledebugmodeID)
- [10.Check Google Play Service version](#id-1.2.2手机端环境搭建-10.CheckGooglePlayServiceversion)
- [11.注册成为google beta tester内部测试账号已经注册过了这一步不需要如果是客户自己注册的Google账号需要提醒客户check](#id-1.2.2手机端环境搭建-11.注册成为googlebetatester内部测试账号已经注册过了这一步不需要如果是客户自己注册的Google账号需要提醒客户check)
:::
\
该测试至少要准备两只手机。测试手机建议使用Google pixel手机 Pixel 5+ is recommended. 请**务必确保**手机端有打开开发者选项 [https://developer.android.com/studio/debug/dev-options?hl=zh-cn](https://developer.android.com/studio/debug/dev-options?hl=zh-cn){.external-link rel="nofollow"} 
\
#### 1.手机需要连接google网络 {#id-1.2.2手机端环境搭建-1.手机需要连接google网络}
该网络必须可以登陆google的网站在测试前请先测试一下是否可以登录google的网站(**建议试试能不能打开youtube之类的**)。
#### 2.手机不可以打开勿扰模式,不然可能看不到弹窗 {#id-1.2.2手机端环境搭建-2.手机不可以打开勿扰模式,不然可能看不到弹窗}
![](media/1.2.2+手机端环境搭建/8961bf5217e5264df9f43b1e5dc19472.png)
#### 3.检查手机是否打开Google Play服务通知 {#id-1.2.2手机端环境搭建-3.检查手机是否打开GooglePlay服务通知}
Setting-\>(Apps&notification  or   Apps)应用和通知-\> See all apps -\>Google Play服务-\>通知-\>All Google Play services notifications, 开启(显示通知)
![](media/1.2.2+手机端环境搭建/0adfe8650d8c0daefd5a769e26f3d0b1.png)
\
#### 4.检查google play 服务是否更新到最新的版本 {#id-1.2.2手机端环境搭建-4.检查googleplay服务是否更新到最新的版本}
setting-\>(Apps&notification    or   Apps)应用和通知-\>See all apps-\>Google Play 服务-\>高级-\>商店, 点击 App details or google play界面会跳转到google play 商店,点击更新.
如果已经成为 beta tester, google play service可能会自动更新到最新的。
![](media/1.2.2+手机端环境搭建/4099155117e47e8fd6a2928139f023cf.png)
![](media/1.2.2+手机端环境搭建/02d69ad5e64edc68be395ec8424e3d77.png)
\
#### 5.登陆google账号 {#id-1.2.2手机端环境搭建-5.登陆google账号}
Settings\>Accounts   or  Seetings-\>Google(内部账号(不可给客户)
[[[[[Fast Pair Validator 测试 请使用 ]{style="color: rgb(0,0,0);"}]{style="color: rgb(23,43,77);"}]{style="color: rgb(255,0,0);"}]{style="color: rgb(0,0,0);"}]{style="color: rgb(255,0,0);"}[realsilbt8888@gmail.com](mailto:realsilbt8888@gmail.com){.external-link rel="nofollow"}[   ]{style="color: rgb(255,0,0);"}
[手动测试账号请参考 [[Google 账号 - BT_Market - WIKI (realtek.com)](https://wiki.realtek.com/pages/viewpage.action?pageId=394285307){rel="nofollow"} ]{style="color: rgb(23,43,77);"}]{style="color: rgb(255,0,0);"}
#### 6 打开自动同步数据功能 {#id-1.2.2手机端环境搭建-6打开自动同步数据功能}
由于GFPS的account key是存在google账号的云端的所以必须要登陆google账号并且需要打开自动同步数据功能
Settings\>Accounts
![](media/1.2.2+手机端环境搭建/804d309c95c25e78feb23f450d7755ca.png)
or
Seetings→Google:
![](media/1.2.2+手机端环境搭建/e93f5957349d40e509c2e561d161858d.png)![](media/1.2.2+手机端环境搭建/75f47b0f791e44a49a705a8576f20aee.png)![](media/1.2.2+手机端环境搭建/ea2aefeffbdf707acdd65a7a66083d1a.png)![](media/1.2.2+手机端环境搭建/307093c833475fc3c0876cd87a2d23a6.png)
#### 7.检查Show notification是否打开 {#id-1.2.2手机端环境搭建-7.检查Shownotification是否打开}
Settings\>Google\>(Devices & sharing)\>Devices(设置\>Google\>设备连接\>设备\>)
pixel 2xl:
![](media/1.2.2+手机端环境搭建/47fc85072a213d1ef683962c106e12a7.png)![](media/1.2.2+手机端环境搭建/04ad6633f70aaf5f2874183ab21105f2.png)
pixel 7:
![](media/1.2.2+手机端环境搭建/6145f25973da8c0950b116a685608f22.png)![](media/1.2.2+手机端环境搭建/acb641ca23621734850802d675256d78.png)![](media/1.2.2+手机端环境搭建/0afddbb13a88680ea12e60051fd70d3f.png)
\
#### 8.Setting界面打开蓝牙以及位置信息。 {#id-1.2.2手机端环境搭建-8.Setting界面打开蓝牙以及位置信息。}
\
#### 9.Enable debug mode ID {#id-1.2.2手机端环境搭建-9.EnabledebugmodeID}
The model ID provided to you is a debug mode ID. To enable it, go to Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable "Include debug results".
If the option "Include debug results" is missing in this page, please ensure Developer options in the phone is enabled.
or go to Settings \> Google \> Devices & sharing \> Devices \>"Include debug results" 
Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable "Include debug results"
![](media/1.2.2+手机端环境搭建/9e02ae63f1a480cd8aae5e995ec6292b.png)
or
Settings \> Google \> Devices & sharing \> Devices \>"Include debug results"
![](media/1.2.2+手机端环境搭建/a6eec7350b2c54e15ff34925a091b308.png)
[https://developer.android.com/studio/debug/dev-options?hl=zh-cn](https://developer.android.com/studio/debug/dev-options?hl=zh-cn){.external-link rel="nofollow"}
#### 10.Check Google Play Service version {#id-1.2.2手机端环境搭建-10.CheckGooglePlayServiceversion}
Purpose: To confirm we use right version of Fast Pair module for testing
Go to Settings \> Apps&notification  or Apps\>google play services \> advanced,  then check Google Play services version (It should be 20.XX.XX or higher).
![](media/1.2.2+手机端环境搭建/fdf003aa6f88c7bf2cfd73319f751c3f.png)
\
\
#### **11.注册成为google beta tester内部测试账号已经注册过了这一步不需要如果是客户自己注册的Google账号需要提醒客户check** {#id-1.2.2手机端环境搭建-11.注册成为googlebetatester内部测试账号已经注册过了这一步不需要如果是客户自己注册的Google账号需要提醒客户check}
[1. Google test group - BT_Market - WIKI](https://wiki.realtek.com/display/BTMKT/1.+Google+test+group){rel="nofollow"}
Sign up for the Google Play services beta program [https://play.google.com/apps/testing/com.google.android.gms](https://play.google.com/apps/testing/com.google.android.gms){.external-link rel="nofollow"}
join the Android Beta group at [https://www.google.com/android/beta](https://www.google.com/android/beta){.external-link rel="nofollow"} to get latest update via OTA
Finder/Find Hub testing program please Navigate to [https://play.google.com/apps/testing/com.google.android.apps.adm](https://play.google.com/apps/testing/com.google.android.apps.adm){.external-link rel="nofollow"}
\
可以登陆Google账号之后在以下链接查看是否有添加成功[我的群组](https://groups.google.com/my-groups){.external-link rel="nofollow"}
![](media/1.2.2+手机端环境搭建/cb73f9490ed6394cbc3076b4a20ab714.png)
需要注意的是:
![](media/1.2.2+手机端环境搭建/e2f389cdc0fd9e3536b611b068529f10.png)
如果没有权限添加FAE需要联系YingTsung (YT) Lin 请他发邮件给Google 让Google把客户注册的Google账号添加到Google的Test group。
\
::::

View File

@@ -0,0 +1,256 @@
# 1.2.3 Fast Pair Validator 环境搭建 {#fast-pair-validator-环境搭建}
:::: {.Section1}
`<style type="text/css">/**/
div.rbtoc1777598906641 {padding: 0px;}
div.rbtoc1777598906641 ul {margin-left: 0px;}
div.rbtoc1777598906641 li {margin-left: 0px;padding-left: 0px;}
/**/</style>`{=html}
::: {.toc-macro .rbtoc1777598906641}
- [1 搭建手机端的测试环境](#id-1.2.3FastPairValidator环境搭建-1搭建手机端的测试环境)
- [1.1 手机需要连接google网络](#id-1.2.3FastPairValidator环境搭建-1.1手机需要连接google网络)
- [1.2 手机不可以打开勿扰模式,不然可能看不到弹窗](#id-1.2.3FastPairValidator环境搭建-1.2手机不可以打开勿扰模式,不然可能看不到弹窗)
- [1.3 检查手机是否打开Google Play服务通知](#id-1.2.3FastPairValidator环境搭建-1.3检查手机是否打开GooglePlay服务通知)
- [1.4 检查google play 服务是否更新到最新的版本](#id-1.2.3FastPairValidator环境搭建-1.4检查googleplay服务是否更新到最新的版本)
- [1.5 登陆google账号](#id-1.2.3FastPairValidator环境搭建-1.5登陆google账号)
- [1.6 打开自动同步数据功能](#id-1.2.3FastPairValidator环境搭建-1.6打开自动同步数据功能)
- [1.7 检查Show notification是否打开](#id-1.2.3FastPairValidator环境搭建-1.7检查Shownotification是否打开)
- [1.8 Setting界面打开蓝牙以及位置信息。](#id-1.2.3FastPairValidator环境搭建-1.8Setting界面打开蓝牙,以及位置信息。)
- [1.9 Enable debug mode ID](#id-1.2.3FastPairValidator环境搭建-1.9EnabledebugmodeID)
- [1.10 Check Google Play Service version](#id-1.2.3FastPairValidator环境搭建-1.10CheckGooglePlayServiceversion)
- [1.11 注册成为google beta tester内部测试账号已经注册过了这一步不需要如果是客户自己注册的Google账号需要提醒客户check](#id-1.2.3FastPairValidator环境搭建-1.11注册成为googlebetatester内部测试账号已经注册过了这一步不需要如果是客户自己注册的Google账号需要提醒客户check)
- [2 Fast Pair Validator APP安装](#id-1.2.3FastPairValidator环境搭建-2FastPairValidatorAPP安装)
- [3 Enable fast pair validator app中的测项](#id-1.2.3FastPairValidator环境搭建-3Enablefastpairvalidatorapp中的测项)
- [3.1 安装adb:](#id-1.2.3FastPairValidator环境搭建-3.1安装adb:)
- [3.2 输入如下命令:](#id-1.2.3FastPairValidator环境搭建-3.2输入如下命令:)
- [4 uninstall amazon 相关app](#id-1.2.3FastPairValidator环境搭建-4uninstallamazon相关app)
- [5 测试账号和MODEL ID](#id-1.2.3FastPairValidator环境搭建-5测试账号和MODELID)
- [6 测试准备](#id-1.2.3FastPairValidator环境搭建-6测试准备)
:::
### 1 搭建手机端的测试环境 {#id-1.2.3FastPairValidator环境搭建-1搭建手机端的测试环境}
测试手机建议使用Google pixel手机请**务必确保**手机端有打开开发者选项 [https://developer.android.com/studio/debug/dev-options?hl=zh-cn](https://developer.android.com/studio/debug/dev-options?hl=zh-cn){.external-link rel="nofollow"} 
\
#### 1.1 手机需要连接google网络 {#id-1.2.3FastPairValidator环境搭建-1.1手机需要连接google网络}
该网络必须可以登陆google的网站在测试前请先测试一下是否可以登录google的网站(**建议试试能不能打开youtube之类的**)。
#### 1.2 手机不可以打开勿扰模式,不然可能看不到弹窗 {#id-1.2.3FastPairValidator环境搭建-1.2手机不可以打开勿扰模式,不然可能看不到弹窗}
![](media/1.2.3+Fast+Pair+Validator+环境搭建/94667834a280a4a9bbc13db5dbc554fc.png)
#### 1.3 检查手机是否打开Google Play服务通知 {#id-1.2.3FastPairValidator环境搭建-1.3检查手机是否打开GooglePlay服务通知}
Setting-\>(Apps&notification  or   Apps)应用和通知-\> See all apps -\>Google Play服务-\>通知-\>All Google Play services notifications, 开启(显示通知)
![](media/1.2.3+Fast+Pair+Validator+环境搭建/1e4f2c79976f21a9e067e2b7f94dc4d5.png)
#### 1.4 检查google play 服务是否更新到最新的版本 {#id-1.2.3FastPairValidator环境搭建-1.4检查googleplay服务是否更新到最新的版本}
setting-\>(Apps&notification    or   Apps)应用和通知-\>See all apps-\>Google Play 服务-\>高级-\>商店, 点击 App details or google play界面会跳转到google play 商店,点击更新.
如果已经成为 beta tester, google play service可能会自动更新到最新的。
![](media/1.2.3+Fast+Pair+Validator+环境搭建/f2fdc69e7658e7f5955988ca5f9280d5.png)
![](media/1.2.3+Fast+Pair+Validator+环境搭建/7313649e14e054046dc31eafc26a99a0.png)
\
#### 1.5 登陆google账号 {#id-1.2.3FastPairValidator环境搭建-1.5登陆google账号}
Settings\>Accounts   or  Seetings-\>Google(内部账号(不可给客户)
[[[[[Fast Pair Validator 测试 请使用 ]{style="color: rgb(0,0,0);"}]{style="color: rgb(23,43,77);"}]{style="color: rgb(255,0,0);"}]{style="color: rgb(0,0,0);"}]{style="color: rgb(255,0,0);"}[realsilbt8888@gmail.com](mailto:realsilbt8888@gmail.com){.external-link rel="nofollow"}[   ]{style="color: rgb(255,0,0);"}
[手动测试账号请参考 [[Google 账号 - BT_Market - WIKI (realtek.com)](https://wiki.realtek.com/pages/viewpage.action?pageId=394285307){rel="nofollow"} ]{style="color: rgb(23,43,77);"}]{style="color: rgb(255,0,0);"}
#### 1.6 打开自动同步数据功能 {#id-1.2.3FastPairValidator环境搭建-1.6打开自动同步数据功能}
由于GFPS的account key是存在google账号的云端的所以必须要登陆google账号并且需要打开自动同步数据功能
Settings\>Accounts
![](media/1.2.3+Fast+Pair+Validator+环境搭建/0b8ab45807f00be2a354fdb1f6568f26.png)
or
Seetings→Google:
![](media/1.2.3+Fast+Pair+Validator+环境搭建/824e58e4157c13a7a9ae26740fdc94fa.png)![](media/1.2.3+Fast+Pair+Validator+环境搭建/c53346bd740285ec3eff9a183d840538.png)![](media/1.2.3+Fast+Pair+Validator+环境搭建/8ec23fa1fcbeed94cd2fd9578f0002e5.png)![](media/1.2.3+Fast+Pair+Validator+环境搭建/9623d91573182c7f5b1493f12c4356e3.png)
#### 1.7 检查Show notification是否打开 {#id-1.2.3FastPairValidator环境搭建-1.7检查Shownotification是否打开}
Settings\>Google\>(Devices & sharing)\>Devices(设置\>Google\>设备连接\>设备\>)
pixel 2xl:
![](media/1.2.3+Fast+Pair+Validator+环境搭建/4e9dd6bc92d127639a4e5a538c9acc42.png)
pixel 7:
![](media/1.2.3+Fast+Pair+Validator+环境搭建/ebec7d388fb86d05aca3ba2165f5098e.png)![](media/1.2.3+Fast+Pair+Validator+环境搭建/80eb0310afca33931827d2287ded6836.png)
\
跑 Fast pair validator 测试之前关掉 Automatically save devices
**Note: 只有realsilbt8888的账号需要关掉 Automatically save devices 其他手动测试的账号Automatically save devices需要打开**
![](media/1.2.3+Fast+Pair+Validator+环境搭建/bb062e88ef90abe40f8398b64950b341.png)
#### 1.8 Setting界面打开蓝牙以及位置信息。 {#id-1.2.3FastPairValidator环境搭建-1.8Setting界面打开蓝牙,以及位置信息。}
\
#### 1.9 Enable debug mode ID {#id-1.2.3FastPairValidator环境搭建-1.9EnabledebugmodeID}
The model ID provided to you is a debug mode ID. To enable it, go to Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable "Include debug results".
If the option "Include debug results" is missing in this page, please ensure Developer options in the phone is enabled.
or go to Settings \> Google \> Devices & sharing \> Devices \>"Include debug results" 
Settings \> Google \> Devices & sharing \> Devices \> top right 3 dot menu to enable "Include debug results"
![](media/1.2.3+Fast+Pair+Validator+环境搭建/3f2cbf0fb83aedb623ce6a6af44aede9.png)
or
Settings \> Google \> Devices & sharing \> Devices \>"Include debug results"
![](media/1.2.3+Fast+Pair+Validator+环境搭建/3843e586b6e1f94639186b0584b86176.png)
[https://developer.android.com/studio/debug/dev-options?hl=zh-cn](https://developer.android.com/studio/debug/dev-options?hl=zh-cn){.external-link rel="nofollow"}
#### 1.10 Check Google Play Service version {#id-1.2.3FastPairValidator环境搭建-1.10CheckGooglePlayServiceversion}
Purpose: To confirm we use right version of Fast Pair module for testing
Go to Settings \> Apps&notification  or Apps\>google play services \> advanced,  then check Google Play services version (It should be 20.XX.XX or higher).
![](media/1.2.3+Fast+Pair+Validator+环境搭建/eb0dd21fa08cde04a9b83381d4884e1e.png)
\
\
#### **1.11 注册成为google beta tester内部测试账号已经注册过了这一步不需要如果是客户自己注册的Google账号需要提醒客户check** {#id-1.2.3FastPairValidator环境搭建-1.11注册成为googlebetatester内部测试账号已经注册过了这一步不需要如果是客户自己注册的Google账号需要提醒客户check}
Sign up for the Google Play services beta program [https://play.google.com/apps/testing/com.google.android.gms](https://play.google.com/apps/testing/com.google.android.gms){.external-link rel="nofollow"}
join the Android Beta group at [https://www.google.com/android/beta](https://www.google.com/android/beta){.external-link rel="nofollow"} to get latest update via OTA
Finder/Find Hub testing program please Navigate to [https://play.google.com/apps/testing/com.google.android.apps.adm](https://play.google.com/apps/testing/com.google.android.apps.adm){.external-link rel="nofollow"}
\
可以登陆Google账号之后在以下链接查看是否有添加成功[我的群组](https://groups.google.com/my-groups){.external-link rel="nofollow"}
![](media/1.2.3+Fast+Pair+Validator+环境搭建/6e51bd1141ca846e4af0bb2e93e17334.png)
需要注意的是:
![](media/1.2.3+Fast+Pair+Validator+环境搭建/0bab20060f6b2f3bfb155b88a05828b1.png)
如果没有权限添加FAE需要联系YingTsung (YT) Lin 请他发邮件给Google 让Google把客户注册的Google账号添加到Google的Test group。
\
### **2 Fast Pair Validator APP安装** {#id-1.2.3FastPairValidator环境搭建-2FastPairValidatorAPP安装}
确认手机是否安装 Fast Pair Validator APP
Fast pair validator app 图标如下图:
[![](media/1.2.3+Fast+Pair+Validator+环境搭建/0ba213fcc09099ab41c8e0221e4928f5.png)]{style="color: rgb(153,51,0);"}
如果没有安装:
去 Play Store/应用商店 下载 Fast Pair Validator APP并且安装。
如果已经安装:
确认安装的是否是最新版。不是最新版,请手动升级到最新版。确认步骤如下:
长按 Fast Pair Validator 图标会看到App info
![](media/1.2.3+Fast+Pair+Validator+环境搭建/bbdfcb16c991936618508c182350d221.png)
点击App info,会看到App details
![](media/1.2.3+Fast+Pair+Validator+环境搭建/c1a5e093b0c30a6ec18f3a502923afd7.png)
点击App details,会看到以下页面如果有新版本请手动更新到最新的版本。如果是beta版本则不需要更新系统会自动帮忙更新。
![](media/1.2.3+Fast+Pair+Validator+环境搭建/6f2e8db9a220e705bf4d48b3aaf9c482.png)
### 3 Enable fast pair validator app中的测项 {#id-1.2.3FastPairValidator环境搭建-3Enablefastpairvalidatorapp中的测项}
#### [3.1 安装adb:]{style="color: rgb(32,33,36);"} {#id-1.2.3FastPairValidator环境搭建-3.1安装adb:}
[[adb安装及使用方法](https://wiki.realtek.com/pages/viewpage.action?pageId=87464469){rel="nofollow"} 该wiki上提供的adb版本太旧会出现device offline的问题下载最新的[https://adbshell.com/downloads](https://adbshell.com/downloads){.external-link rel="nofollow"}]{style="color: rgb(32,33,36);"}
安装adb之后找到adb.exe所在的目录在该目录下打开cmd命令行
#### 3.2 输入如下命令: {#id-1.2.3FastPairValidator环境搭建-3.2输入如下命令:}
adb shell am broadcast -a com.google.location.nearby.apps.fastpair.validator.FLAG_OVERRIDE \--es flag enable_features_for_v3 \--es value true \--es type boolean com.google.location.nearby.apps.fastpair.validator
[![](media/1.2.3+Fast+Pair+Validator+环境搭建/5040df7f9e4af787dd63c45576f1d7f2.png)]{.confluence-embedded-file-wrapper .confluence-embedded-manual-size}
按enter执行命令。
命令执行成功之后,
打开fast pair validator 能看到新的feature
\
### 4 uninstall amazon 相关app {#id-1.2.3FastPairValidator环境搭建-4uninstallamazon相关app}
Alexa (com.amazon.dee.app) 和com.amazon.wellness app 会影响到Validator的测试需要Uninstall。
The Alexa (com.amazon.dee.app) took too much time on handling the ACL_CONNECTED intent, which impacts the Validator\'s flow.
There is still another **app,com.amazon.wellness** app, who handled ACL_CONNECTED for 20+ seconds.Please uninstall it as well.
现象 End-to-end integration测试出现Pairing timeout
操作方式: 
adb uninstall com.amazon.wellness
adb uninstall com.amazon.dee.app
\
### 5 测试账号和MODEL ID {#id-1.2.3FastPairValidator环境搭建-5测试账号和MODELID}
使用Fast Pair Validator测试需要先登陆Google账号测试设备使用的Model ID,public key, private key 必须是该google账号注册的Device。
场内测试账号:[realsilbt8888@gmail.com](mailto:realsilbt8888@gmail.com){.external-link rel="nofollow"}
**Note**
fast pair validator app使用的model id 要和DUT开发板配置的model id一致。
![](media/1.2.3+Fast+Pair+Validator+环境搭建/940b91547f4e49233ceaaf7092386c29.png)![](media/1.2.3+Fast+Pair+Validator+环境搭建/389cce5910af360b6867f26f36c1b9a3.png)
### **6 测试准备** {#id-1.2.3FastPairValidator环境搭建-6测试准备}
测试过程中需要注意
手机端弹出配对提示框时不要手动点击fast pair validator app会自己触发配对.
开始测试前,需要确认是否已经和待测试耳机配对过,需要删除配对信息。 最后最好在开始测试前,开关一下飞行模式。
点击GOT IT开始测试时耳机端一定要处于Pairable mode否则会scan不到设备, scan 到设备后点击Test开始测试。
![](media/1.2.3+Fast+Pair+Validator+环境搭建/6fa8e8c938098fc1362ca8cadcd5f68f.png)
::::

23
1.3+测试.md Normal file
View File

@@ -0,0 +1,23 @@
# 1.3 测试 {#测试}
::: {.Section1}
测试完成之后要填写测试报告, 测试报告从以下位置获取:
[Test Case of the Third Party - BT Test - WIKI](https://wiki.realtek.com/display/BT/Test+Case+of+the+Third+Party){rel="nofollow"}
![](media/1.3+测试/0683707db76fff45c025b6472bd589cd.png)
\
因为设备不支援find hub(类似于苹果的findmy功能) 所以测试报告中:
Find My Device 那一页不需要测试:
![](media/1.3+测试/6d6c19d4cd32e603d5dee783c1c52050.png)
\
Fast Pair Validator那一页 EDDYSTONE 下面的测项不需要测试:
![](media/1.3+测试/60166fa4da7468639014c496e6182937.png)
:::

View File

@@ -0,0 +1,13 @@
# 1.3.1 Fast Pair Validator测试 {#fast-pair-validator测试}
::: {.Section1}
[1.3.1.1 FAST PAIR](https://wiki.realtek.com/display/BTMKT/1.3.1.1+FAST+PAIR?src=contextnavpagetreemode){rel="nofollow"} 
这个测项客户自测并且提交测试结果到Google云端认证实验室暂时不会测试。
目前来看只要有一次测试成功并且有提交成功的测试结果到Google云端就可以即使偶尔失败了如果确定不是我们设备端的bug, 也没关系的
[https://partnerissuetracker.corp.google.com/u/0/issues/473688165](https://partnerissuetracker.corp.google.com/u/0/issues/473688165){.external-link rel="nofollow"}
[![](media/1.3.1+Fast+Pair+Validator测试/314cb995ea0ae6c488df07b4811c6a76.png)]{.plugin_pagetree_children_span}
:::

704
1.3.1.1+FAST+PAIR.md Normal file
View File

@@ -0,0 +1,704 @@
# 1.3.1.1 FAST PAIR {#fast-pair}
:::: {.Section1}
`<style type="text/css">/**/
div.rbtoc1777599001982 {padding: 0px;}
div.rbtoc1777599001982 ul {margin-left: 0px;}
div.rbtoc1777599001982 li {margin-left: 0px;padding-left: 0px;}
/**/</style>`{=html}
::: {.toc-macro .rbtoc1777599001982}
- [Note](#id-1.3.1.1FASTPAIR-Note)
- [1 以下关于mcu cfg tool 的修改仅仅是为了通过fast pair validator测试待测试通过之后需要将相应的修改恢复默认值。否则GFPS功能没法正常使用。](#id-1.3.1.1FASTPAIR-1以下关于mcucfgtool的修改仅仅是为了通过fastpairvalidator测试待测试通过之后需要将相应的修改恢复默认值。否则GFPS功能没法正常使用。)
- [2 测试过程中GFPS 弹窗出来之后请不要点击弹窗!!!](#id-1.3.1.1FASTPAIR-2测试过程中GFPS弹窗出来之后请不要点击弹窗)
- [3 GFPS Fast pair validator 测试走的Legacy flow, 通过gfps配对 legacy BREDR.](#id-1.3.1.1FASTPAIR-3GFPSFastpairvalidator测试走的Legacyflow,通过gfps配对legacyBREDR.)
- [4 mcu cfg tool 中 可以配置按键key1进入legacy Pairing mode(MMI 0x6C)有些测试会需要短按key1进入Pairing mode](#id-1.3.1.1FASTPAIR-4mcucfgtool中可以配置按键key1进入legacyPairingmode(MMI0x6C)有些测试会需要短按key1进入Pairingmode)
- [5 手机提示信息解读:](#id-1.3.1.1FASTPAIR-5手机提示信息解读)
- [Upair the device耳机做factory reset清掉配对信息](#id-1.3.1.1FASTPAIR-Upairthedevice耳机做factoryreset清掉配对信息)
- [place the device back into pairing mode耳机进入pairing mode](#id-1.3.1.1FASTPAIR-placethedevicebackintopairingmode耳机进入pairingmode)
- [6 测试准备](#id-1.3.1.1FASTPAIR-6测试准备)
- [打开Fast Pair Validator app](#id-1.3.1.1FASTPAIR-打开FastPairValidatorapp)
- [通过model id找到待测试设备](#id-1.3.1.1FASTPAIR-通过modelid找到待测试设备)
- [选择FAST PAIR进行测试](#id-1.3.1.1FASTPAIR-选择FASTPAIR进行测试)
- [不要Enable LE spec test](#id-1.3.1.1FASTPAIR-不要EnableLEspectest)
- [Calibration 测试](#id-1.3.1.1FASTPAIR-Calibration测试)
- [End-to-end integration 测试](#id-1.3.1.1FASTPAIR-End-to-endintegration测试)
- [Auto pairing 测试](#id-1.3.1.1FASTPAIR-Autopairing测试)
- [Auto Subsequent Pairing 测试](#id-1.3.1.1FASTPAIR-AutoSubsequentPairing测试)
- [Cross Seekers Auto Subsequent Pairing Test 测试](#id-1.3.1.1FASTPAIR-CrossSeekersAutoSubsequentPairingTest测试)
- [Public Key Based Pairing Request in Non Discoverable Mode 测试](#id-1.3.1.1FASTPAIR-PublicKeyBasedPairingRequestinNonDiscoverableMode测试)
- [Public Key Based Pairing Request After Retroactive Pair 测试](#id-1.3.1.1FASTPAIR-PublicKeyBasedPairingRequestAfterRetroactivePair测试)
- [Account key Broadcasting & Rotation of RPA测试](#id-1.3.1.1FASTPAIR-AccountkeyBroadcasting&RotationofRPA测试)
- [Key Based Request Flags Reserved Bit Verification 测试](#id-1.3.1.1FASTPAIR-KeyBasedRequestFlagsReservedBitVerification测试)
- [Distance 0.3 Meter 测试](#id-1.3.1.1FASTPAIR-Distance0.3Meter测试)
- [](#id-1.3.1.1FASTPAIR-)
- [Distance 1.2 Meter 测试](#id-1.3.1.1FASTPAIR-Distance1.2Meter测试)
- [Distance 2 Meter 测试](#id-1.3.1.1FASTPAIR-Distance2Meter测试)
- [Battery Notification Verification 测试](#id-1.3.1.1FASTPAIR-BatteryNotificationVerification测试)
- [Battery Suppress Notification Verification 测试](#id-1.3.1.1FASTPAIR-BatterySuppressNotificationVerification测试)
- [Battery Level Update Verification 测试](#id-1.3.1.1FASTPAIR-BatteryLevelUpdateVerification测试)
- [Personalized Name Update 测试](#id-1.3.1.1FASTPAIR-PersonalizedNameUpdate测试)
- [Personalized Name with Provider First Time Pairing 测试](#id-1.3.1.1FASTPAIR-PersonalizedNamewithProviderFirstTimePairing测试)
- [Ring a Device 测试](#id-1.3.1.1FASTPAIR-RingaDevice测试)
- [Retroactive Pair 测试](#id-1.3.1.1FASTPAIR-RetroactivePair测试)
- [Active Noise Control Verification 测试](#id-1.3.1.1FASTPAIR-ActiveNoiseControlVerification测试)
- [Active Noise Control Disable 测试](#id-1.3.1.1FASTPAIR-ActiveNoiseControlDisable测试)
- [Firmware Version 测试](#id-1.3.1.1FASTPAIR-FirmwareVersion测试)
- [Dynamic Buffer Size测试](#id-1.3.1.1FASTPAIR-DynamicBufferSize测试)
- [10.测试结果上报](#id-1.3.1.1FASTPAIR-10.测试结果上报)
:::
### **Note** {#id-1.3.1.1FASTPAIR-Note}
#### 1 以下关于mcu cfg tool 的修改仅仅是为了通过fast pair validator测试待测试通过之后需要将相应的修改恢复默认值。否则GFPS功能没法正常使用。 {#id-1.3.1.1FASTPAIR-1以下关于mcucfgtool的修改仅仅是为了通过fastpairvalidator测试待测试通过之后需要将相应的修改恢复默认值。否则GFPS功能没法正常使用。}
    也就是说以下修改只能搭配fast pair validator app使用请不要将对应的修改提交到正式release版本。
#### 2 测试过程中GFPS 弹窗出来之后请不要点击弹窗!!! {#id-1.3.1.1FASTPAIR-2测试过程中GFPS弹窗出来之后请不要点击弹窗}
#### 3 GFPS Fast pair validator 测试走的Legacy flow, 通过gfps配对 legacy BREDR. {#id-1.3.1.1FASTPAIR-3GFPSFastpairvalidator测试走的Legacyflow,通过gfps配对legacyBREDR.}
#### 4 mcu cfg tool 中 可以配置按键key1进入legacy Pairing mode(MMI 0x6C)有些测试会需要短按key1进入Pairing mode {#id-1.3.1.1FASTPAIR-4mcucfgtool中可以配置按键key1进入legacyPairingmode(MMI0x6C)有些测试会需要短按key1进入Pairingmode}
![](media/1.3.1.1+FAST+PAIR/d7939a45f30ae3c7e67a65edf0cc28b8.png)
![](media/1.3.1.1+FAST+PAIR/52772a16ee0fcfa9700aff47528d8a24.png)
\
#### 5 手机提示信息解读: {#id-1.3.1.1FASTPAIR-5手机提示信息解读}
#####  Upair the device耳机做factory reset清掉配对信息 {#id-1.3.1.1FASTPAIR-Upairthedevice耳机做factoryreset清掉配对信息}
#####  place the device back into pairing mode耳机进入pairing mode  {#id-1.3.1.1FASTPAIR-placethedevicebackintopairingmode耳机进入pairingmode}
#### 6 测试准备 {#id-1.3.1.1FASTPAIR-6测试准备}
##### 打开Fast Pair Validator app {#id-1.3.1.1FASTPAIR-打开FastPairValidatorapp}
[![](media/1.3.1.1+FAST+PAIR/043f058384a293e73a53923bff772afc.png)]{style="color: rgb(153,51,0);"}
##### 通过model id找到待测试设备 {#id-1.3.1.1FASTPAIR-通过modelid找到待测试设备}
[![](media/1.3.1.1+FAST+PAIR/9e0eb1856a0898d3ed225d7049640661.png)]{style="color: rgb(153,51,0);"}
##### 选择FAST PAIR进行测试 {#id-1.3.1.1FASTPAIR-选择FASTPAIR进行测试}
[![](media/1.3.1.1+FAST+PAIR/03b5e8532bfbd9c5e78f3ca23df51c20.png)]{style="color: rgb(153,51,0);"}
##### 不要Enable LE spec test {#id-1.3.1.1FASTPAIR-不要EnableLEspectest}
[![](media/1.3.1.1+FAST+PAIR/ba5599cbe19710a0b8d35fa2cece0ea3.png)]{style="color: rgb(153,51,0);"}
### Calibration 测试 {#id-1.3.1.1FASTPAIR-Calibration测试}
Note: 
calibration 测试, discoverable adv interval需要足够小spec 规定 discoverable mode adv \<= 100msmcu cfg tool目前设为32(20 ms) 可以测试通过。
开机legacy进pairing mode后按键key1进入GFPS LEA 配对模式按app提示将手机放置离耳机 1m、3m、0.3m米处,等待测试完成。
Note:
GFPS 弹窗出来之后请**不要**点击弹窗!!!
如果1m测项测试失败Fast pair validator可以协助我们手动调整tx power值:
![](media/1.3.1.1+FAST+PAIR/dafdadb61405ace826c4efea73f32a58.png)![](media/1.3.1.1+FAST+PAIR/2401fff5f00ae7435cafdaf8752b722f.png)![](media/1.3.1.1+FAST+PAIR/f93dfe7bd322a3e78b7f4f8ca879f6a5.png)![](media/1.3.1.1+FAST+PAIR/50d033783387d97216c65a8114f87853.png)
详细文档可以参考:[tx power adjust user guide - BT_Market - WIKI](https://wiki.realtek.com/display/BTMKT/tx+power+adjust+user+guide){rel="nofollow"}
### End-to-end integration 测试 {#id-1.3.1.1FASTPAIR-End-to-endintegration测试}
Note:
spec 规定not discoverable mode adv interval \<= 250ms该测项中有verify 500ms frequency检查超过500 会fail目前设置成62.5ms可以通过测试。
\
MCU cfg tool 配置:
测试该测项的时候,手机清除配对信息(unpair device)DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
![](media/1.3.1.1+FAST+PAIR/800dcc6a460f70646d3ee1f58129b02f.png)
如果找不到 rws normal disconnect enter pairing mode 这个配置项 原因是这个配置项挪位置了请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
![](media/1.3.1.1+FAST+PAIR/c0e8b2bb4be8fc3ba806ebb6f2c53d39.png)
\
1手机提示 Next steps时控制耳机进入配对模式点击next等待手机 prescan-\> pair device -\> check account key != null -\> unpair device-\>verify account key --\> verify 500ms frequency -\> Check subsequent pairing tx power level  -\> repair device -\> un-repair device.。
2点击next。 注意一定要在"10.Un-Repair device"显示"Unpairing finished!"后才能点NEXT。
如此反复5遍。
![](media/1.3.1.1+FAST+PAIR/c476ea9a254033b107738a4399923a84.png)![](media/1.3.1.1+FAST+PAIR/c53c9297abe1a8e58e8a6bb451597cd9.png)
![](media/1.3.1.1+FAST+PAIR/392c064173faa2951c00cadd7dfdda3c.png)![](media/1.3.1.1+FAST+PAIR/bb33026d3bd31db5cae4fae209208ff4.png)
测试视频:
[End To End test.mp4](/download/attachments/948641808/End%20To%20End%20test.mp4?version=1&modificationDate=1759129643533&api=v2){linked-resource-id="948642410" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="End To End test.mp4" nice-type="Multimedia" linked-resource-content-type="video/mp4" linked-resource-container-id="948641808" linked-resource-container-version="19"}
### Auto pairing 测试 {#id-1.3.1.1FASTPAIR-Autopairing测试}
Mcu cfg tool配置
测试该测项的时候,手机清除配对信息(unpair device)DUT断线需要进入discoverable mode, 所以mcu config tool 中 RWS页面下 rws normal disconnect enter pairing mode[需要设置成enable(勾选)。]{style="color: rgb(0,0,0);"}\
app_cfg_const.rws_disconnect_enter_pairing
[![](media/1.3.1.1+FAST+PAIR/c6e4c5adda43f5ad0a784e16ad2cdf74.png)]{style="color: rgb(0,0,0);"}
如果找不到 rws normal disconnect enter pairing mode 这个配置项 原因是这个配置项挪位置了请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
![](media/1.3.1.1+FAST+PAIR/0935c3983a9f6b7fc73b396e06d78dc3.png)
[\
]{style="color: rgb(0,0,0);"}
设置每一轮测试持续时间以及重复进行多少轮测试([推荐使用APP中提供的默认值进行测试100次一次120s)然后点击test, ]{style="color: rgb(0,0,0);"}
测试时将手机setting-》显示-》屏幕超时设置成最大值。灭屏之后测试好像会stop所以屏幕要保持常亮的状态。
\
**Note:**
这个测试按照Google的测试spec是要求每轮测试之前都要强制进pairing mode的。
正常每轮测试结束后手机会主动断线为了方便测试我们soc端有设置只要soc收到手机主动断线的指令之后就会主动进入pairing mode,等待下一轮测试。
因为是跑测试我们soc端没办法预测所有的失败场景所以针对异常的情况soc端是没办法做到所有的失败场景下都能保证下一轮测试一定会正常进pairing mode 因为手机端并不会告诉soc 什么时候测试开始。
所以如果跑自动化测试遇到失败的情况,建议手动测试, 每一轮测试结束之后根据提示让设备主动进入pairing mode。
\
![](media/1.3.1.1+FAST+PAIR/63044559a7bb37335a34c3e82d547cb3.png)
### Auto Subsequent Pairing 测试 {#id-1.3.1.1FASTPAIR-AutoSubsequentPairing测试}
MCU cfg tool 配置:
测试该测项的时候,手机清除配对信息(unpair device)DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
![](media/1.3.1.1+FAST+PAIR/800dcc6a460f70646d3ee1f58129b02f.png)
如果找不到 rws normal disconnect enter pairing mode 这个配置项 原因是这个配置项挪位置了请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
![](media/1.3.1.1+FAST+PAIR/c0e8b2bb4be8fc3ba806ebb6f2c53d39.png)
\
**Note:**
这个测试按照Google的测试spec是要求每轮测试之前都要打nondiscoverable 广播的。
正常每轮测试结束后手机会主动断线为了方便测试我们soc端有设置只要soc收到手机主动断线的指令之后就会主动打nondiscoverable 广播,等待下一轮测试。
因为是跑测试,
我们soc端没办法预测所有的失败场景
所以针对异常的情况,
soc端是没办法做到所有的失败场景下都能保证下一轮测试一定会主动打nondiscoverable 广播(不在pairing mode才会打nondiscoverable 广播) 因为手机端并不会告诉soc 什么时候测试开始。
所以如果跑自动化测试遇到失败的情况,建议手动测试:
每一轮测试结束之后EVB按一下reset或者是关机再开机让设备端主动打nondiscoverable 广播(注意这个时候EVB一定不能做factory reset也不能进pairing mode, 因为这个时候是期望打 nondiscoverable 广播)
BLE advertisements don\'t contain fast pair account key while not in pairing mode 如果频繁遇到这个error 可以尝试手动测试试试看
\
测试信息设置:
![](media/1.3.1.1+FAST+PAIR/d1f4e69a1ecc7f68fa8e7eaae54ffeac.png)
手机端测试信息设置完成之后,
耳机先做factory reset之后耳机开机进pairing mode
之后手机端点击test 开始测试
![](media/1.3.1.1+FAST+PAIR/ba694c3d598f3288fe64317cb121bcc3.png)
\
\
### Cross Seekers Auto Subsequent Pairing Test 测试 {#id-1.3.1.1FASTPAIR-CrossSeekersAutoSubsequentPairingTest测试}
MCU cfg tool 配置:
测试该测项的时候,手机清除配对信息(unpair device)DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
![](media/1.3.1.1+FAST+PAIR/800dcc6a460f70646d3ee1f58129b02f.png)
如果找不到 rws normal disconnect enter pairing mode 这个配置项 原因是这个配置项挪位置了请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
![](media/1.3.1.1+FAST+PAIR/c0e8b2bb4be8fc3ba806ebb6f2c53d39.png)
\
\
测试信息设置:
![](media/1.3.1.1+FAST+PAIR/a34463886fa9bcdedf0635825d0616ab.png)
\
耳机先做factory reset手机端清掉配对信息[1 gfps/finder 如何清除配对信息 - BT_Market - WIKI](https://wiki.realtek.com/pages/viewpage.action?pageId=401291585){rel="nofollow"} 之后耳机开机进pairing mode之后手机端点击test 开始测试
\
测试视频:
[Cross Seekers Auto Subsequent Pairing Test.mp4](/download/attachments/948641808/Cross%20Seekers%20Auto%20Subsequent%20Pairing%20Test.mp4?version=1&modificationDate=1759224099177&api=v2){linked-resource-id="948651208" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="Cross Seekers Auto Subsequent Pairing Test.mp4" nice-type="Multimedia" linked-resource-content-type="video/mp4" linked-resource-container-id="948641808" linked-resource-container-version="19"}
测试log
[COM12_2025-09-30_16-56-51.log](/download/attachments/948641808/COM12_2025-09-30_16-56-51.log?version=1&modificationDate=1759223471600&api=v2){linked-resource-id="948651140" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="COM12_2025-09-30_16-56-51.log" nice-type="Text File" linked-resource-content-type="text/plain" linked-resource-container-id="948641808" linked-resource-container-version="19"}
[COM12_btsnoop_2025-09-30_16-51-45.cfa](/download/attachments/948641808/COM12_btsnoop_2025-09-30_16-51-45.cfa?version=1&modificationDate=1759223475897&api=v2){linked-resource-id="948651142" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="COM12_btsnoop_2025-09-30_16-51-45.cfa" linked-resource-content-type="application/octet-stream" linked-resource-container-id="948641808" linked-resource-container-version="19"}
[COM12_2025-09-30_16-51-39.log](/download/attachments/948641808/COM12_2025-09-30_16-51-39.log?version=1&modificationDate=1759223476397&api=v2){linked-resource-id="948651143" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="COM12_2025-09-30_16-51-39.log" nice-type="Text File" linked-resource-content-type="text/plain" linked-resource-container-id="948641808" linked-resource-container-version="19"}
[COM12_2025-09-26_14-19-00.log](/download/attachments/948641808/COM12_2025-09-26_14-19-00.log?version=1&modificationDate=1759223503080&api=v2){linked-resource-id="948651148" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="COM12_2025-09-26_14-19-00.log" nice-type="Text File" linked-resource-content-type="text/plain" linked-resource-container-id="948641808" linked-resource-container-version="19"}
![](media/1.3.1.1+FAST+PAIR/bcd9b3c76d386f326fdd45a144328dab.png)![](media/1.3.1.1+FAST+PAIR/2c887e8d44f0b7d6a9f8900d146329a4.png)![](media/1.3.1.1+FAST+PAIR/f12815534877e22c540fd6ad2314c46f.png)
![](media/1.3.1.1+FAST+PAIR/23d8f2c04f247380e20d168814631501.png)![](media/1.3.1.1+FAST+PAIR/9f55833bffc337406d8ad3183f14d339.png)
\
### Public Key Based Pairing Request in Non Discoverable Mode 测试 {#id-1.3.1.1FASTPAIR-PublicKeyBasedPairingRequestinNonDiscoverableMode测试}
MCU cfg tool 配置:
测试该测项的时候,手机清除配对信息(unpair device)DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
![](media/1.3.1.1+FAST+PAIR/800dcc6a460f70646d3ee1f58129b02f.png)
如果找不到 rws normal disconnect enter pairing mode 这个配置项 原因是这个配置项挪位置了请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
![](media/1.3.1.1+FAST+PAIR/c0e8b2bb4be8fc3ba806ebb6f2c53d39.png)
\
\
测试信息设置:
![](media/1.3.1.1+FAST+PAIR/90d99727d0c624cccc2b4a41e055b992.png)
\
耳机先做factory reset手机端清掉配对信息[1 gfps/finder 如何清除配对信息 - BT_Market - WIKI](https://wiki.realtek.com/pages/viewpage.action?pageId=401291585){rel="nofollow"} 之后耳机开机进pairing mode之后手机端点击test 开始测试
\
测试视频:
[public key based request in non discoverable mode-Non LEA.mp4](/download/attachments/948641808/public%20key%20based%20request%20in%20non%20discoverable%20mode-Non%20LEA.mp4?version=1&modificationDate=1759225238333&api=v2){linked-resource-id="948651368" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="public key based request in non discoverable mode-Non LEA.mp4" nice-type="Multimedia" linked-resource-content-type="video/mp4" linked-resource-container-id="948641808" linked-resource-container-version="19"}
测试log
[COM12_2025-09-30_17-33-58.log](/download/attachments/948641808/COM12_2025-09-30_17-33-58.log?version=1&modificationDate=1759225010223&api=v2){linked-resource-id="948651337" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="COM12_2025-09-30_17-33-58.log" nice-type="Text File" linked-resource-content-type="text/plain" linked-resource-container-id="948641808" linked-resource-container-version="19"}
[COM12_btsnoop_2025-09-30_17-29-41.cfa](/download/attachments/948641808/COM12_btsnoop_2025-09-30_17-29-41.cfa?version=1&modificationDate=1759225015190&api=v2){linked-resource-id="948651338" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="COM12_btsnoop_2025-09-30_17-29-41.cfa" linked-resource-content-type="application/octet-stream" linked-resource-container-id="948641808" linked-resource-container-version="19"}
[COM12_2025-09-30_17-29-39.log](/download/attachments/948641808/COM12_2025-09-30_17-29-39.log?version=1&modificationDate=1759225015860&api=v2){linked-resource-id="948651339" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="COM12_2025-09-30_17-29-39.log" nice-type="Text File" linked-resource-content-type="text/plain" linked-resource-container-id="948641808" linked-resource-container-version="19"}
![](media/1.3.1.1+FAST+PAIR/93a20032a164b156ca9e612505c55791.png)![](media/1.3.1.1+FAST+PAIR/cb3e902b64e0abf0063e4ac29d3935b0.png)![](media/1.3.1.1+FAST+PAIR/3c6dc775a227108e0bbba6b555aa32b3.png)![](media/1.3.1.1+FAST+PAIR/c58a228e1cdc75d452396a889556769c.png)
\
### Public Key Based Pairing Request  After Retroactive Pair 测试 {#id-1.3.1.1FASTPAIR-PublicKeyBasedPairingRequestAfterRetroactivePair测试}
MCU cfg tool 配置:
测试该测项的时候,手机清除配对信息(unpair device)DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
![](media/1.3.1.1+FAST+PAIR/800dcc6a460f70646d3ee1f58129b02f.png)
如果找不到 rws normal disconnect enter pairing mode 这个配置项 原因是这个配置项挪位置了请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
![](media/1.3.1.1+FAST+PAIR/c0e8b2bb4be8fc3ba806ebb6f2c53d39.png)
\
\
测试信息设置:
耳机先做factory reset手机端清掉配对信息[1 gfps/finder 如何清除配对信息 - BT_Market - WIKI](https://wiki.realtek.com/pages/viewpage.action?pageId=401291585){rel="nofollow"} 之后耳机开机进pairing mode之后手机端点击test 开始测试
\
测试视频:
如果测试过程中遇到 Get account key fail, 参考以下视频:
[Public key based pairing request after retroactive pair-nonLEA-Get account key fail.mp4](/download/attachments/948641808/Public%20key%20based%20pairing%20request%20after%20retroactive%20pair-nonLEA-Get%20account%20key%20fail.mp4?version=1&modificationDate=1759226451537&api=v2){linked-resource-id="948651473" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="Public key based pairing request after retroactive pair-nonLEA-Get account key fail.mp4" nice-type="Multimedia" linked-resource-content-type="video/mp4" linked-resource-container-id="948641808" linked-resource-container-version="19"}
测试成功视频:
[Public key based pairing request after retroactive pair-nonLEA.mp4](/download/attachments/948641808/Public%20key%20based%20pairing%20request%20after%20retroactive%20pair-nonLEA.mp4?version=1&modificationDate=1759226617723&api=v2){linked-resource-id="948651483" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="Public key based pairing request after retroactive pair-nonLEA.mp4" nice-type="Multimedia" linked-resource-content-type="video/mp4" linked-resource-container-id="948641808" linked-resource-container-version="19"}
\
测试log
![](media/1.3.1.1+FAST+PAIR/a644beb33819734765801b155f5f0bb4.png)![](media/1.3.1.1+FAST+PAIR/03187c9b096259e2fea8747010de6691.png)![](media/1.3.1.1+FAST+PAIR/2b63da6b1faeb6f3ea8fcfbc7ba4d96a.png)![](media/1.3.1.1+FAST+PAIR/87be26035280a85301524861a8ac0da9.png)
![](media/1.3.1.1+FAST+PAIR/57b199affa5c0c3a7559b0aad1c3724b.png)![](media/1.3.1.1+FAST+PAIR/1f657ae36b57a71a1d4c427773998fe2.png)![](media/1.3.1.1+FAST+PAIR/d19e2b3c4a860ab0b6310a6e81f7c058.png)![](media/1.3.1.1+FAST+PAIR/d2e262415c1e2f9d9528dfff6d83ed79.png)
[COM12_2025-10-13_13-47-37.log](/download/attachments/948641808/COM12_2025-10-13_13-47-37.log?version=1&modificationDate=1760336127463&api=v2){linked-resource-id="964439163" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="COM12_2025-10-13_13-47-37.log" nice-type="Text File" linked-resource-content-type="text/plain" linked-resource-container-id="948641808" linked-resource-container-version="19"}
[COM12_2025-10-13_13-51-37.log](/download/attachments/948641808/COM12_2025-10-13_13-51-37.log?version=1&modificationDate=1760336113757&api=v2){linked-resource-id="964439159" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="COM12_2025-10-13_13-51-37.log" nice-type="Text File" linked-resource-content-type="text/plain" linked-resource-container-id="948641808" linked-resource-container-version="19"}
[COM12_btsnoop_2025-10-13_13-48-53.cfa](/download/attachments/948641808/COM12_btsnoop_2025-10-13_13-48-53.cfa?version=1&modificationDate=1760336126687&api=v2){linked-resource-id="964439162" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="COM12_btsnoop_2025-10-13_13-48-53.cfa" linked-resource-content-type="application/octet-stream" linked-resource-container-id="948641808" linked-resource-container-version="19"}
[Public Key Based Pairing Request After Retroactive Pair测试pass.7z](/download/attachments/948641808/Public%20Key%20Based%20Pairing%20Request%20After%20Retroactive%20Pair%E6%B5%8B%E8%AF%95pass.7z?version=1&modificationDate=1763543863557&api=v2){linked-resource-id="998593044" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="Public Key Based Pairing Request After Retroactive Pair测试pass.7z" linked-resource-content-type="application/octet-stream" linked-resource-container-id="948641808" linked-resource-container-version="19"}
### Account key Broadcasting & Rotation of RPA测试 {#id-1.3.1.1FASTPAIR-AccountkeyBroadcasting&RotationofRPA测试}
MCU cfg tool 配置:
测试该测项的时候,手机清除配对信息(unpair device)DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
![](media/1.3.1.1+FAST+PAIR/800dcc6a460f70646d3ee1f58129b02f.png)
如果找不到 rws normal disconnect enter pairing mode 这个配置项 原因是这个配置项挪位置了请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
![](media/1.3.1.1+FAST+PAIR/c0e8b2bb4be8fc3ba806ebb6f2c53d39.png)
\
板子做factory reset之后开机进pairing mode点击test开始测试, 测试时间大概30min左右
![](/download/attachments/948641808/image-2023-12-14_10-47-1.png?version=1&modificationDate=1759127749783&api=v2)![](/download/attachments/948641808/image-2023-12-14_10-47-39.png?version=1&modificationDate=1759127749973&api=v2)
\
### Key Based Request Flags Reserved Bit Verification 测试 {#id-1.3.1.1FASTPAIR-KeyBasedRequestFlagsReservedBitVerification测试}
MCU cfg tool 配置:
测试该测项的时候,手机清除配对信息(unpair device)DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
![](media/1.3.1.1+FAST+PAIR/800dcc6a460f70646d3ee1f58129b02f.png)
如果找不到 rws normal disconnect enter pairing mode 这个配置项 原因是这个配置项挪位置了请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
![](media/1.3.1.1+FAST+PAIR/c0e8b2bb4be8fc3ba806ebb6f2c53d39.png)
\
板子做factory reset之后开机进pairing mode点击test开始测试
测试过程中看到\"Please places the headset to pairing mode\"的时候短按key1进入pairing mode 测试过程中不可以做factory reset
测试视频:
[Key Based Request Flags Reserved Bit Verification.mp4](/download/attachments/948641808/Key%20Based%20Request%20Flags%20Reserved%20Bit%20Verification.mp4?version=1&modificationDate=1760339352253&api=v2){linked-resource-id="964439764" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="Key Based Request Flags Reserved Bit Verification.mp4" nice-type="Multimedia" linked-resource-content-type="video/mp4" linked-resource-container-id="948641808" linked-resource-container-version="19"}
\
### Distance 0.3 Meter 测试 {#id-1.3.1.1FASTPAIR-Distance0.3Meter测试}
耳机开机,[按键key1进入GFPS LEA配对模式然后开始测试等待测试完成。]{style="color: rgb(153,51,0);"}
Note:
GFPS 弹窗出来之后不要点;
如果该测项测不过MCU cfg tool Thirdparty 页面需要适当减小tx power(比如从-10减小到-12);并重新跑   \"**Calibration 测试\"** 以及该测项  
\
### [![](/download/attachments/948641808/image-2025-3-12_16-48-5.png?version=1&modificationDate=1760339559983&api=v2)![](/download/attachments/948641808/image-2025-3-12_16-48-25.png?version=1&modificationDate=1760339560190&api=v2)![](/download/attachments/948641808/image-2025-3-12_16-48-39.png?version=1&modificationDate=1760339560347&api=v2)![](/download/attachments/948641808/image-2025-3-12_16-48-48.png?version=1&modificationDate=1760339560570&api=v2)![](/download/attachments/948641808/image-2025-3-12_16-49-1.png?version=1&modificationDate=1760339560757&api=v2)![](/download/attachments/948641808/image-2025-3-12_16-49-9.png?version=1&modificationDate=1760339560927&api=v2)]{style="color: rgb(153,51,0);"} {#id-1.3.1.1FASTPAIR-}
\
### Distance 1.2 Meter 测试 {#id-1.3.1.1FASTPAIR-Distance1.2Meter测试}
耳机开机,[按键key1进入GFPS LEA配对模式然后开始测试等待测试完成。]{style="color: rgb(153,51,0);"}
Note:
GFPS 弹窗出来之后不要点;
如果该测项测不过MCU cfg tool Thirdparty 页面需要适当增大tx power(比如从-12增大到-10并重新跑   \"**Calibration 测试\"** 以及该测项 
\
\
### Distance 2 Meter 测试 {#id-1.3.1.1FASTPAIR-Distance2Meter测试}
耳机开机,[按键key1进入GFPS LEA配对模式然后开始测试等待测试完成。]{style="color: rgb(153,51,0);"}
Note:
GFPS 弹窗出来之后不要点;
如果该测项测不过MCU cfg tool Thirdparty 页面需要适当增大tx power(比如从-12增大到-10并重新跑   \"**Calibration 测试\"** 以及该测项  
![](/download/attachments/948641808/image-2025-3-12_17-59-49.png?version=1&modificationDate=1760339561093&api=v2)![](/download/attachments/948641808/image-2025-3-12_18-0-14.png?version=1&modificationDate=1760339561310&api=v2)![](/download/attachments/948641808/image-2025-3-12_18-0-31.png?version=1&modificationDate=1760339561487&api=v2)![](/download/attachments/948641808/image-2025-3-12_18-0-52.png?version=1&modificationDate=1760339561663&api=v2)
\
\
\
### Battery Notification Verification 测试 {#id-1.3.1.1FASTPAIR-BatteryNotificationVerification测试}
Note:
该测项测试的时候需要接充电盒
MCU cfg tool 配置:
测试该测项的时候,手机清除配对信息(unpair device)DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
![](media/1.3.1.1+FAST+PAIR/800dcc6a460f70646d3ee1f58129b02f.png)
如果找不到 rws normal disconnect enter pairing mode 这个配置项 原因是这个配置项挪位置了请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
![](media/1.3.1.1+FAST+PAIR/c0e8b2bb4be8fc3ba806ebb6f2c53d39.png)
\
测试前板子先做factory reset之后再开机进pairing mode
  ![](/download/attachments/948641808/image2020-6-2%2017%3A12%3A57.png?version=1&modificationDate=1759127750137&api=v2)![](/download/attachments/948641808/image2020-6-2%2017%3A13%3A10.png?version=1&modificationDate=1759127750217&api=v2)
\
### Battery Suppress Notification Verification 测试 {#id-1.3.1.1FASTPAIR-BatterySuppressNotificationVerification测试}
Note:
该测项测试的时候需要接充电盒
MCU cfg tool 配置:
测试该测项的时候,手机清除配对信息(unpair device)DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
![](media/1.3.1.1+FAST+PAIR/800dcc6a460f70646d3ee1f58129b02f.png)
如果找不到 rws normal disconnect enter pairing mode 这个配置项 原因是这个配置项挪位置了请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
![](media/1.3.1.1+FAST+PAIR/c0e8b2bb4be8fc3ba806ebb6f2c53d39.png)
\
测试前板子先做factory reset之后再开机进pairing mode
\
### Battery Level Update Verification 测试 {#id-1.3.1.1FASTPAIR-BatteryLevelUpdateVerification测试}
Note:
该测项测试的时候需要接充电盒
MCU cfg tool 配置:
测试该测项的时候,手机清除配对信息(unpair device)DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
![](media/1.3.1.1+FAST+PAIR/800dcc6a460f70646d3ee1f58129b02f.png)
如果找不到 rws normal disconnect enter pairing mode 这个配置项 原因是这个配置项挪位置了请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
![](media/1.3.1.1+FAST+PAIR/c0e8b2bb4be8fc3ba806ebb6f2c53d39.png)
\
测试前板子先做factory reset之后再开机进pairing mode
\
### Personalized Name Update 测试 {#id-1.3.1.1FASTPAIR-PersonalizedNameUpdate测试}
MCU cfg tool 配置:
测试该测项的时候,手机清除配对信息(unpair device)DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
![](media/1.3.1.1+FAST+PAIR/800dcc6a460f70646d3ee1f58129b02f.png)
如果找不到 rws normal disconnect enter pairing mode 这个配置项 原因是这个配置项挪位置了请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
![](media/1.3.1.1+FAST+PAIR/c0e8b2bb4be8fc3ba806ebb6f2c53d39.png)
\
\
\
测试注意事项:
测试之前板子先做factory reset 然后开机进pairing mode, 开始测试
测试过程中看到\"Please places the headset to pairing mode\"的时候短按key1进入pairing mode 测试过程中不可以做factory reset
![](/download/attachments/948641808/image2020-6-2%2017%3A12%3A26.png?version=1&modificationDate=1759127750300&api=v2)
\
测试log:
![](/download/attachments/948641808/image-2023-12-14_11-22-54.png?version=1&modificationDate=1759127750400&api=v2)![](/download/attachments/948641808/image-2023-12-14_11-23-12.png?version=1&modificationDate=1759127750597&api=v2)
测试视频:
[Personalized name update.mp4](/download/attachments/948641808/Personalized%20name%20update.mp4?version=1&modificationDate=1759129788767&api=v2){linked-resource-id="948642419" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="Personalized name update.mp4" nice-type="Multimedia" linked-resource-content-type="video/mp4" linked-resource-container-id="948641808" linked-resource-container-version="19"}
### Personalized Name with Provider First Time Pairing 测试 {#id-1.3.1.1FASTPAIR-PersonalizedNamewithProviderFirstTimePairing测试}
MCU cfg tool 配置:
测试该测项的时候,手机清除配对信息(unpair device)DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
![](media/1.3.1.1+FAST+PAIR/800dcc6a460f70646d3ee1f58129b02f.png)
如果找不到 rws normal disconnect enter pairing mode 这个配置项 原因是这个配置项挪位置了请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
![](media/1.3.1.1+FAST+PAIR/c0e8b2bb4be8fc3ba806ebb6f2c53d39.png)
\
\
测试注意事项:
测试之前板子做factory reset然后再开机进pairing mode,然后开始测试
看到\"Please places the headset to pairing mode\"的时候短按key1让耳机进入 pairing mode
测试log:
![](/download/attachments/948641808/image-2023-12-14_17-13-42.png?version=1&modificationDate=1759127750740&api=v2)
测试视频:
\
### Ring a Device 测试 {#id-1.3.1.1FASTPAIR-RingaDevice测试}
MCU cfg tool 配置:
测试该测项的时候,手机清除配对信息(unpair device)DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
![](media/1.3.1.1+FAST+PAIR/800dcc6a460f70646d3ee1f58129b02f.png)
如果找不到 rws normal disconnect enter pairing mode 这个配置项 原因是这个配置项挪位置了请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
![](media/1.3.1.1+FAST+PAIR/c0e8b2bb4be8fc3ba806ebb6f2c53d39.png)
\
配置ring tone
![](/download/attachments/948641808/image-2023-12-14_17-57-33.png?version=1&modificationDate=1759127750920&api=v2)
\
测试注意事项:
测试之前板子做factory reset然后再开机进pairing mode, 然后开始测试
看到\"Please places the headset to pairing mode\"的时候短按key1让耳机进入 pairing mode
测试log:
![](/download/attachments/948641808/image-2023-12-14_17-51-51.png?version=1&modificationDate=1759127751037&api=v2)
![](/download/attachments/948641808/image-2023-12-14_17-52-27.png?version=1&modificationDate=1759127751217&api=v2)
![](/download/attachments/948641808/image-2023-12-14_17-52-46.png?version=1&modificationDate=1759127751417&api=v2)
\
测试视频:
[Ring a Device.mp4](/download/attachments/948641808/Ring%20a%20Device.mp4?version=1&modificationDate=1759129874047&api=v2){linked-resource-id="948642430" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="Ring a Device.mp4" nice-type="Multimedia" linked-resource-content-type="video/mp4" linked-resource-container-id="948641808" linked-resource-container-version="19"}
### Retroactive Pair 测试 {#id-1.3.1.1FASTPAIR-RetroactivePair测试}
MCU cfg tool 配置:
测试该测项的时候,手机清除配对信息(unpair device)DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
![](media/1.3.1.1+FAST+PAIR/800dcc6a460f70646d3ee1f58129b02f.png)
如果找不到 rws normal disconnect enter pairing mode 这个配置项 原因是这个配置项挪位置了请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
![](media/1.3.1.1+FAST+PAIR/c0e8b2bb4be8fc3ba806ebb6f2c53d39.png)
\
\
在Available device点选要测试的设备
![](/download/attachments/948641808/image2020-6-2%2017%3A11%3A47.png?version=1&modificationDate=1759127751667&api=v2)![](/download/attachments/948641808/image2020-6-2%2017%3A12%3A5.png?version=1&modificationDate=1759127751797&api=v2)
测试视频:
[retroactive pair test.mp4](/download/attachments/948641808/retroactive%20pair%20test.mp4?version=1&modificationDate=1759129956680&api=v2){linked-resource-id="948642435" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="retroactive pair test.mp4" nice-type="Multimedia" linked-resource-content-type="video/mp4" linked-resource-container-id="948641808" linked-resource-container-version="19"}
测试log:
[Retroactive Pair测试pass.7z](/download/attachments/948641808/Retroactive%20Pair%E6%B5%8B%E8%AF%95pass.7z?version=1&modificationDate=1763543586347&api=v2){linked-resource-id="998593012" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="Retroactive Pair测试pass.7z" linked-resource-content-type="application/octet-stream" linked-resource-container-id="948641808" linked-resource-container-version="19"}
### Active Noise Control Verification 测试 {#id-1.3.1.1FASTPAIR-ActiveNoiseControlVerification测试}
目前还不清楚怎么测试,如果不支援可以不测
### Active Noise Control Disable 测试 {#id-1.3.1.1FASTPAIR-ActiveNoiseControlDisable测试}
目前还不清楚怎么测试,如果不支援可以不测
### Firmware Version 测试 {#id-1.3.1.1FASTPAIR-FirmwareVersion测试}
MCU cfg tool 配置:
测试该测项的时候,手机清除配对信息(unpair device)DUT断线需要进入non discoverable mode, 所以mcu config tool 中rws normal disconnect enter pairing mode需要设置成disable(不勾选)。
![](media/1.3.1.1+FAST+PAIR/800dcc6a460f70646d3ee1f58129b02f.png)
如果找不到 rws normal disconnect enter pairing mode 这个配置项 原因是这个配置项挪位置了请参考jira [[BTSOCTOOL-2822](https://jira.realtek.com/browse/BTSOCTOOL-2822){.jira-issue-key} - Getting issue details\... STATUS ]{.jira-issue jira-key="BTSOCTOOL-2822" client-id="SINGLE_2d885edc-676b-3349-9548-fe5648c9d8cd_948641808_2c9082e76519d09101657ff5cfb3003b"} 进行配置RWS normal disconnect enter pairing mode 改成Normal disconnect enter pairing mode
![](media/1.3.1.1+FAST+PAIR/c0e8b2bb4be8fc3ba806ebb6f2c53d39.png)
\
### Dynamic Buffer Size测试 {#id-1.3.1.1FASTPAIR-DynamicBufferSize测试}
目前还不清楚怎么测试,如果不支援 可以不测
\
### 10.测试结果上报 {#id-1.3.1.1FASTPAIR-10.测试结果上报}
测试成功后,除了 [目前还不清楚怎么测试 的测项之外的其他所有的测试结果都为PASS可以SUBMIT测试结果否则请不要提交测试结果]{style="color: rgb(255,0,0);"}
\
\
\
\
::::

7
1.3.2+手动测试.md Normal file
View File

@@ -0,0 +1,7 @@
# 1.3.2 手动测试 {#手动测试}
::: {.Section1}
手动测试完成之后需要提交self test report:
Fast Pair self-tests report can be found in the [BlueTooth Classic](https://developers.google.com/static/nearby/fast-pair/downloads/self-test-reports/Bluetooth_Classic_-_Google_Fast_Pair_Self_Test_Report_10142020.zip){.external-link style="" rel="nofollow"} 
:::

View File

@@ -0,0 +1,17 @@
# 1.3.2.1 Initial pair and subsequent pair {#initial-pair-and-subsequent-pair}
::: {.Section1}
google 官方测试文档:
[Fast Pair 3.2 & 3.3 Certification Guidelines  \|  Google for Developers](https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline#22_notification_popup_for_initial_pairing){.external-link rel="nofollow"}
Realtek内部整理文档
[1 Initial Pairing and Subsequent Pairing Test Guideline(中文文档) - BT_Market - WIKI](https://wiki.realtek.com/pages/viewpage.action?pageId=288810503){rel="nofollow"}
测试视频:
[initial_pairing.mp4](/download/attachments/948641817/initial_pairing.mp4?version=1&modificationDate=1759136017707&api=v2){linked-resource-id="948643166" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="initial_pairing.mp4" nice-type="Multimedia" linked-resource-content-type="video/mp4" linked-resource-container-id="948641817" linked-resource-container-version="3"}
\
:::

View File

@@ -0,0 +1,15 @@
# 1.3.2.2 extended feature {#extended-feature}
::: {.Section1}
Google 官方文档:
[https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline#4_feature_certification_criteria](https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline#4_feature_certification_criteria){.external-link rel="nofollow"}
Realtek 内部整理文档:
[1 Extension Feature Test Guideline(中文文档) - BT_Market - WIKI](https://wiki.realtek.com/pages/viewpage.action?pageId=374584696){rel="nofollow"}
\
\
:::

17
GFPS+认证测试.md Normal file
View File

@@ -0,0 +1,17 @@
# GFPS 认证测试
::: {.Section1}
手动测试视频: [认证Video.7z](/download/attachments/948641629/%E8%AE%A4%E8%AF%81Video.7z?version=1&modificationDate=1776678332627&api=v2){linked-resource-id="1097877256" linked-resource-version="1" linked-resource-type="attachment" linked-resource-default-alias="认证Video.7z" linked-resource-content-type="application/octet-stream" linked-resource-container-id="948641629" linked-resource-container-version="5"}
Note:
[ 1. realsilbt8888@gmail.com](mailto:realsilbt8888@gmail.com){.external-link rel="nofollow"} 这个账号只能用于 Fast Pair validator 测试,不可以用于手动测试
[realsilbt8888@gmail.com](mailto:realsilbt8888@gmail.com){.external-link style="color: rgb(255,0,0);" rel="nofollow"} 这个账号下面的 Automatically save devices要关掉
![](media/GFPS+认证测试/90b2adad442da11e1f20eee390eaaa82.png)
\
**除了[realsilbt8888@gmail.com](mailto:realsilbt8888@gmail.com){.external-link style="color: rgb(255,0,0);" rel="nofollow"}之外的其他账号 Automatically save devices要打开**
:::

Binary file not shown.

After

Width:  |  Height:  |  Size: 26 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 370 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 62 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.4 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 54 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 58 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 49 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 57 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 131 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 57 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 159 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 51 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 13 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 240 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 35 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 34 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 38 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 27 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 22 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 40 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 5.0 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.3 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 17 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 121 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 592 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 148 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 195 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 147 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 194 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 206 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 34 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 136 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 266 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 249 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 280 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 220 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 226 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 149 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 161 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 86 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 252 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 204 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 297 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 249 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 20 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 86 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 195 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 226 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 210 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 220 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 34 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 40 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 161 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 418 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 27 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 592 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 149 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 252 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 204 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 30 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 280 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 194 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 330 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 418 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 397 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 266 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 297 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 136 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 206 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 141 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 94 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 98 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 194 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 211 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 252 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 309 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 27 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 236 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 342 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 372 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 211 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 383 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 286 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 293 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 326 KiB

Some files were not shown because too many files have changed in this diff Show More