gfps: 添加认证测试和FAQ 20260505
All checks were successful
Sync To /home/ubuntu/gfps / sync (push) Successful in 2s
All checks were successful
Sync To /home/ubuntu/gfps / sync (push) Successful in 2s
Change-Id: I71e676b997159a141ca07d16f82a73b45f4b2410
This commit is contained in:
danni_dong
126
手机不弹窗原因整理.md
Normal file
126
手机不弹窗原因整理.md
Normal file
@@ -0,0 +1,126 @@
|
||||
# 手机不弹窗原因整理
|
||||
|
||||
首先请参考 <a href="https://wiki.realtek.com/pages/viewpage.action?pageId=948641629" rel="nofollow">GFPS 认证测试 - BT_Market - WIKI</a> 确认环境配置
|
||||
|
||||
如果弹窗还不出现，以下整理了一些常见的手机不弹窗的原因：
|
||||
|
||||
1.如果手机端弹窗出现之后，一直不点击弹窗进行配对，弹窗的优先级就会降低，后面就有可能不会弹窗了，如果想要解决这个问题，只能是重启一下手机，来恢复弹窗的优先级。
|
||||
|
||||
\
|
||||
|
||||
2.正常情况下耳机进入pairing mode之后，手机会出现如下图所示的GFPS notification弹窗(弹窗图片可能不完全一样)
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
3.如果出现如下图所示的情况：
|
||||
|
||||
只弹出小图标，下拉打开通知中心，在通知中心可以看到GFPS Notification。
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
4.不弹窗还有可能是手机开启了勿扰模式，请把勿扰模式关闭。关闭方式如下图：
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
5.确保手机setting界面：位置信息-》使用位置信息已经打开
|
||||
|
||||
\
|
||||
|
||||
如果客户注册的model id 不弹窗，可以请QC换成场内测试model id试试看，如果场内测试model id可以弹窗， 那可能是客户注册的model id有问题， model id注册参考 [model_id 注册](/pages/viewpage.action?pageId=157379126)
|
||||
|
||||
**<span style="color: rgb(255,0,0);">Note:</span>**
|
||||
|
||||
20240101之后注册的model id 好像需要google设置成active 之后才可以使用，如果注册model id页面有如下提示：
|
||||
|
||||
<span class="fui-Flex ___o96bqp0 f22iagw f5wk2nc f10ra9hq"></span>
|
||||
|
||||
需要FAE帮助客户向 Realtek YT(YingTsung (YT) Lin) 提ticket， 提了ticket之后， google就会帮忙激活这个model id
|
||||
|
||||
\
|
||||
|
||||
6.如果始终不出现GFPS Notification弹窗。\
|
||||
可以将手机靠近耳机，如果靠近后出现GFPS Notification弹窗，说明GFPS Advertising Data中的TX Power Level设置的不对，需要重新调整(增大tx power 缩小被发现的距离，减小tx power 增大被发现的距离)。\
|
||||
如果调整mcu cfg tool 中的tx power之后仍然不起作用，请查看注册model id的时候是不是有设置tx power, 如果注册model id的时候有设置tx power, mcu cfg tool中设置的tx power就不会起作用。
|
||||
|
||||
|
||||
|
||||
\
|
||||
|
||||
7.如果手机靠近耳机后还是不出现GFPS Notification弹窗，可以用另外一只手机试一下。如果另外一只手机也没有出现，看一下是不是耳机的问题(耳机gfps adv是否正常广播，广播包的内容是否正确)。
|
||||
|
||||
7.1 initial pair(discoverable mode) adv data 格式如下：
|
||||
|
||||
gfps_gen_adv_data: adv mode 0, tx_power -19, popup_show_ui 1, adv data 02 01 19 02 0A <span style="color: rgb(0,0,0);">ED</span> 06 16<span style="color: rgb(255,0,0);"> 2C FE</span> <span style="color: rgb(51,153,102);">EC F4 AC</span>, len 13
|
||||
|
||||
红色位置是GFPS service UUID 0xFE2C
|
||||
|
||||
绿色位置是model id
|
||||
|
||||
7.2 subsequent pair(nondiscoverable mode) adv data 格式如下：
|
||||
|
||||
gfps_gen_adv_data: adv mode 1, tx_power -19, popup_show_ui 1, adv data 02 01 19 02 0A ED 0B 16 <span style="color: rgb(255,0,0);">2C FE</span> 00 <span style="color: rgb(51,153,102);">40</span> 18 04 88 80 11 72, len 18
|
||||
|
||||
红色位置是GFPS service UUID 0xFE2C
|
||||
|
||||
绿色位置是account key length 和 type: 0x<span style="color: rgb(0,0,0);">40是指length是4(对应一个account key), type是0(对应show ui)</span>
|
||||
|
||||
<span style="color: rgb(0,0,0);"> 以下是一个错误的log：</span>
|
||||
|
||||
gfps_gen_adv_data: adv mode 1, tx_power -19, popup_show_ui 1, adv data 02 01 19 02 0A ED 07 16 2C FE 00 **<span style="color: rgb(255,102,0);">00</span>** 11 C4, len 14
|
||||
|
||||
红色位置是account key length 和 type，**<span style="color: rgb(255,102,0);">00</span>**是指耳机端没有account key,**在没有account key的情况下做subsequent pair，这肯定是有问题的**。
|
||||
|
||||
\
|
||||
|
||||
8.如果弹框仍然不出现，可以手动点击一下，setting\>Google\>开发者 Firebase App Indexing 手动刷新一下里面的内容,然后重启手机。
|
||||
|
||||
\
|
||||
|
||||
9.如果subsequent pairing过程中弹窗没有出现，
|
||||
|
||||
9.1 除了上面列出的原因之外，请确认一下google的网络是不是可用，以及Settings\>Google\>Devices\>Saved devices界面下是否已经有同步的saved device,
|
||||
|
||||
如果没有saved device，手机肯定不会弹窗的，这个时候要确认一下Google网络是否正常
|
||||
|
||||
|
||||
|
||||
9.2 如果saved device里面有设备，但是依然没有弹窗，需要考虑是否account key filter 生成的有问题 ， 验证脚本：<a href="/download/attachments/137586699/verify_bloom_filter.py?version=1&modificationDate=1772841949233&api=v2" data-linked-resource-container-id="137586699" data-linked-resource-container-version="16" data-linked-resource-content-type="application/octet-stream" data-linked-resource-default-alias="verify_bloom_filter.py" data-linked-resource-id="1066107303" data-linked-resource-type="attachment" data-linked-resource-version="1">verify_bloom_filter.py</a> 验证文档 <a href="/download/attachments/137586699/Fast%20Pair%20Bloom%20Filter%20%E9%AA%8C%E8%AF%81%E5%B7%A5%E5%85%B7%20-%20README.md?version=1&modificationDate=1772841986423&api=v2" data-linked-resource-container-id="137586699" data-linked-resource-container-version="16" data-linked-resource-content-type="application/octet-stream" data-linked-resource-default-alias="Fast Pair Bloom Filter 验证工具 - README.md" data-linked-resource-id="1066107304" data-linked-resource-type="attachment" data-linked-resource-version="1">Fast Pair Bloom Filter 验证工具 - README.md</a>
|
||||
|
||||
Line 24586: 0004564 03-06#16:43:44.479 015 0033813.407 \[APP\] !\*\*gfps_gen_account_key_filter: key 04 1D 75 FB 16 47 B7 91 07 EB 69 50 D2 68 9A CD\
|
||||
Line 24587: 0004565 03-06#16:43:44.479 016 0033813.599 \[APP\] !\*\*gfps_gen_account_key_filter: key 04 1D 75 FB 16 47 B7 91 07 EB 69 50 D2 68 9A CD\
|
||||
Line 24588: 0004566 03-06#16:43:44.479 017 0033813.750 \[APP\] !\*\*gfps_gen_account_key_filter: key 04 1D 75 FB 16 47 B7 91 07 EB 69 50 D2 68 9A CD\
|
||||
Line 24589: 0004567 03-06#16:43:44.479 018 0033813.903 \[APP\] !\*\*gfps_gen_account_key_filter: key 04 1D 75 FB 16 47 B7 91 07 EB 69 50 D2 68 9A CD\
|
||||
Line 24590: 0004568 03-06#16:43:44.479 019 0033814.055 \[APP\] !\*\*gfps_gen_account_key_filter: key 04 1D 75 FB 16 47 B7 91 07 EB 69 50 D2 68 9A CD\
|
||||
Line 24591: 0004569 03-06#16:43:44.479 020 0033814.211 \[APP\] !\*\*gfps_gen_account_key_filter: filter 21 00 04 00 28 40 04 00 00
|
||||
|
||||
\
|
||||
|
||||
<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=159814449" rel="nofollow">6 用客户自己注册的model id不弹窗，用rtk认证过的model id就可以弹窗 - BT_Market - WIKI</a><a href="https://wiki.realtek.com/pages/viewpage.action?pageId=159814449" rel="nofollow">6 用客户自己注册的model id不弹窗，用rtk认证过的model id就可以弹窗 - BT_Market - WIKI</a>
|
||||
|
||||
<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=302940616" rel="nofollow">6 同一个手机搭配RTK耳机不会弹窗，搭配竞品耳机可以弹窗 - BT_Market - WIKI</a>
|
||||
|
||||
<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=288810427" rel="nofollow">6 弹窗功能测试时手机不弹窗 - BT_Market - WIKI</a>
|
||||
|
||||
<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=1034120023" rel="nofollow">21 android 13设备无GFPS弹窗 - BT_Market - WIKI</a>
|
||||
|
||||
<a href="https://wiki.realtek.com/pages/viewpage.action?pageId=1045539446" rel="nofollow">22 Android 12 GFPS不弹窗 - BT_Market - WIKI</a>
|
||||
|
||||
<span class="jira-issue resolved" jira-key="BBPRO2BUG-21347"> <a href="https://jira.realtek.com/browse/BBPRO2BUG-21347" class="jira-issue-key"><img src="https://jira.realtek.com/secure/viewavatar?size=xsmall&avatarId=10916&avatarType=issuetype" />BBPRO2BUG-21347</a> - <span class="summary">\[BBPro2\]\[RTL8773CO SDK\]\[沃莱特/飞利浦\]\[RHA\]GFPS 30cm 不弹框</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Closed</span> </span>
|
||||
|
||||
<span class="jira-issue resolved" jira-key="BB2BUG-7057"> <a href="https://jira.realtek.com/browse/BB2BUG-7057" class="jira-issue-key"><img src="https://jira.realtek.com/secure/viewavatar?size=xsmall&avatarId=10916&avatarType=issuetype" />BB2BUG-7057</a> - <span class="summary">\[BB2\]\[RTL8763EF/ROM\]\[GMI\]\[沃莱特\]\[Harman\]\[T520\]\[133\]: google手机不弹窗</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Closed</span> </span>
|
||||
|
||||
<span class="jira-issue resolved" jira-key="BB2BUG-5778"> <a href="https://jira.realtek.com/browse/BB2BUG-5778" class="jira-issue-key"><img src="https://jira.realtek.com/secure/viewavatar?size=xsmall&avatarId=10916&avatarType=issuetype" />BB2BUG-5778</a> - <span class="summary">\[BB2\]\[RTL8763EF/ROM\]\[GMI\]\[沃莱特\]\[Harman\]\[T520\]\[JBL1366\]: 谷歌6P和谷歌6手机登陆相同的账号，耳机多次开机进入配对与谷歌6P配对，谷歌6手机概率出现不弹窗</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Closed</span> </span>
|
||||
|
||||
<span class="jira-issue resolved" jira-key="BB2BUG-5654"> <a href="https://jira.realtek.com/browse/BB2BUG-5654" class="jira-issue-key"><img src="https://jira.realtek.com/secure/viewavatar?size=xsmall&avatarId=10916&avatarType=issuetype" />BB2BUG-5654</a> - <span class="summary">\[BB2\]\[RTL8763EF/ROM\]\[GMI\]\[沃莱特\]\[Harman\]\[T520\]\[127\]:谷歌快速配对，耳机开机进配对，靠近两个谷歌手机，只有一个手机能弹窗</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Closed</span> </span>
|
||||
|
||||
<span class="jira-issue resolved" jira-key="BB2BUG-5377"> <a href="https://jira.realtek.com/browse/BB2BUG-5377" class="jira-issue-key"><img src="https://jira.realtek.com/secure/viewavatar?size=xsmall&avatarId=10916&avatarType=issuetype" />BB2BUG-5377</a> - <span class="summary">\[BB2\]\[RTL8763EF/ROM\]\[GMI\]\[沃莱特\]\[Harman\]\[T520\]: google手机快速配对不弹窗的</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Closed</span> </span>
|
||||
|
||||
<span class="jira-issue resolved" jira-key="BUMBEEBUG-7880"> <a href="https://jira.realtek.com/browse/BUMBEEBUG-7880" class="jira-issue-key"><img src="https://jira.realtek.com/secure/viewavatar?size=xsmall&avatarId=10916&avatarType=issuetype" />BUMBEEBUG-7880</a> - <span class="summary">\[BBlite\]\[8753BFJ\]\[凯力威\]\[QCY\]\[TW02\]\[ v1.7.5.1\]: GFPS 第三次开机谷歌不弹出窗口了</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Closed</span> </span>
|
||||
|
||||
<span class="jira-issue resolved" jira-key="BB2RD-2200"> <a href="https://jira.realtek.com/browse/BB2RD-2200" class="jira-issue-key"><img src="https://jira.realtek.com/secure/viewavatar?size=xsmall&avatarId=10900&avatarType=issuetype" />BB2RD-2200</a> - <span class="summary">\[GFPS\]\[LEA\] subsequent pair 手机 nrf connect scan不到GFPS adv</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf">Closed</span> </span>
|
||||
Reference in New Issue
Block a user