weefnn/gfps
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

gfps: 添加认证测试和FAQ 20260505
All checks were successful
Sync To /home/ubuntu/gfps / sync (push) Successful in 2s
Details

Browse Source 
Change-Id: I71e676b997159a141ca07d16f82a73b45f4b2410
This commit is contained in:
danni_dong
2026-05-05 19:24:08 +08:00
parent 2ed168dcf8
commit bdbb2527e6
1943 changed files with 10585 additions and 434 deletions
Download Patch File Download Diff File Expand all files Collapse all files

44
附耳配对失败+cause+Numeric+Comparison+Failed_0x050C.md Normal file
View File

@@ -0,0 +1,44 @@
# 附耳配对失败 cause Numeric Comparison Failed 0x050C
![](images/附耳配对失败+cause+Numeric+Comparison+Failed_0x050C_eb41fecc.jpg)
\
原因是gfps_handle_char_additional_passkey 解密 additional passkey 失败了
<table class="confluenceTable">
<tbody>
<tr>
<th class="confluenceTh" scope="col"> 0008066  12-30#14:08:38.005  199  0598425.808  [BTIFMSG]↗BTIF_MSG_GATT_ATTR_WRITE_REQ_IND(CMD:0x010A) link_id:0x0012 cid:0x0004 p_srv_handle:0x004204C8 attr_index:0x0011 attr_len:0x0010 handle:0x0000 write_offset:0x0000 gap:0x09 data:0x17 <br />
 0008067  12-30#14:08:38.005  200  0598426.097  [PATCH] patch_hw_aes_operate_imp: error code: 0x0<br />
 0008068  12-30#14:08:38.005  201  0598426.132  [APP] !!!gfps_handle_char_additional_passkey: message type error 240<br />
 0008069  12-30#14:08:38.005  202  0598426.162  [APP] !**gfps_attr_write_cb: pending, attr_index 17, cause 0xd04<br />
 0008070  12-30#14:08:38.005  203  0598426.187  [BTIFMSG]↙BTIF_MSG_GATT_ATTR_WRITE_REQ_CFM(CMD:0x010B) link_id:0x0012 cid:0x0004 p_srv_handle:0x004204C8 cause:0x0D04 attr_index:0x0011</th>
</tr>
&#10;</tbody>
</table>
gfps_handle_char_additional_passkey 解密：
![](images/附耳配对失败+cause+Numeric+Comparison+Failed_0x050C_c8c8bee7.jpg)
怀疑 gfps→aes_key 被改了
<table class="confluenceTable">
<tbody>
<tr>
<th class="confluenceTh" scope="col"><p>//这边有一次异常断线，异常断线之后 我们有reset  aes_key </p>
<p>0004136  12-30#14:08:28.521  142  0588963.226  [APP] app_gfps_le_disconnect_cb: conn_id 0, local_disc_cause 0, disc_cause 0x108<br />
 0004137  12-30#14:08:28.521  143  0588963.260  [APP] !!!app_gfps_le_disconnect_cb: plink connid 0, gfps link connid 0, gfps curr conn_id 0<br />
 0004138  12-30#14:08:28.521  144  0588963.324  [APP] !**gfps_reset_aeskey_and_pairing_status: aes_key 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00</p></th>
</tr>
&#10;</tbody>
</table>
因为Google spec 是说  <span style="color: rgb(23,43,77);"> shall discard aes key and pairing mode if this LE link disconnects，所以优先要请 lowerstack 帮忙查看disc_cause 0x108</span>
<span style="color: rgb(23,43,77);">目前的workaround 是：不清楚会不会引入新的问题：</span>
<span style="color: rgb(23,43,77);">![](images/附耳配对失败+cause+Numeric+Comparison+Failed_0x050C_02a03764.jpg)</span>
<span style="color: rgb(23,43,77);"><a href="https://jira.realtek.com/browse/BBPRO3BUG-27030" class="external-link" rel="nofollow">[BBPRO3BUG-27030] [BBPRO3][EVB][E Cut][PEGA_HA_v1.0.4_20251106][24110 testbin][GFPS][FastPair][LEA phone]Auto Subsequent Pairing... 测试fail（fail reason：creatbond failed，multiple components） - Jira</a></span>