All checks were successful
Sync To /home/ubuntu/gfps / sync (push) Successful in 2s
Change-Id: I71e676b997159a141ca07d16f82a73b45f4b2410
2.7 KiB
2.7 KiB
附耳配对失败 cause Numeric Comparison Failed 0x050C
\
原因是gfps_handle_char_additional_passkey 解密 additional passkey 失败了
| 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 0008067 12-30#14:08:38.005 200 0598426.097 [PATCH] patch_hw_aes_operate_imp: error code: 0x0 0008068 12-30#14:08:38.005 201 0598426.132 [APP] !!!gfps_handle_char_additional_passkey: message type error 240 0008069 12-30#14:08:38.005 202 0598426.162 [APP] !**gfps_attr_write_cb: pending, attr_index 17, cause 0xd04 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 |
|---|
gfps_handle_char_additional_passkey 解密:
怀疑 gfps→aes_key 被改了
//这边有一次异常断线,异常断线之后 我们有reset aes_key 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 |
|---|
因为Google spec 是说 shall discard aes key and pairing mode if this LE link disconnects,所以优先要请 lowerstack 帮忙查看disc_cause 0x108
目前的workaround 是:不清楚会不会引入新的问题:


