Files
gfps/1+Reason_+could+not+connected.md
danni_dong bdbb2527e6
All checks were successful
Sync To /home/ubuntu/gfps / sync (push) Successful in 2s
gfps: 添加认证测试和FAQ 20260505
Change-Id: I71e676b997159a141ca07d16f82a73b45f4b2410
2026-05-05 19:24:08 +08:00

5.4 KiB
Raw Blame History

1 Reason: could not connected

如果测试遇到该问题,麻烦贴一下上面的截图,并且请帮忙指出上图红色框里面对应的信息:

1.Found by EID at xxxxxx xxxxx对应的地址是什么

2.手机端显示connecting对应的时间点

3.手机端显示Test finished对应的时间点

\

log分析

截图位置1

"Found by AK at 48:48:6A:60:5A:F7"

截图位置2

"Scaning by EID"

"Found by EID at 7B:F8:BE:9E:64:E0"

截图位置3

手机尝试connecting 7B:F8:BE:9E:64:E0

但是此时耳机端因为 48:48:6A:60:5A:F7 这条link还没有断掉

手机再尝试连7B:F8:BE:9E:64:E0的时候

耳机端会认为link已经存在直接拒绝这次连线

导致手机端测试显示 "Could not connect"

这个问题不是必现的

\

想请问是不是可以先断开48:48:6A:60:5A:F7这条link确保手机和耳机的link断开之后, 再尝试执行截图位置2以及之后的操作

不然的话,

如果在48:48:6A:60:5A:F7这条link 断开之后, 再scan 到7B:F8:BE:9E:64:E0 并且尝试创建BLE link 是没有问题的。

如果在48:48:6A:60:5A:F7这条link 尚未断开之前 就scan 到7B:F8:BE:9E:64:E0 并且尝试创建BLE link 就会遇到上面描述的问题。

\

log:

0006294 03-28#14:18:17.958 199 0034334.679 [HCI] hci_if_confirm: buf 0x0020de33
0006295 03-28#14:18:17.958 200 0034334.980 [HCI] !!!hci_le_conn_cmpl_evt: handle 0x0015, peer_addr 75 F2 05 93 E8 62 connection already exist
0006296 03-28#14:18:17.958 201 0034335.049 [HCI] !**hci_cmd_disconnect: handle 0x0015, cause 0x13
0006297 03-28#14:18:17.958 202 0034335.183 [HCI] hci_if_write: buf 0x00407397, len 7
0006298 03-28#14:18:17.958 203 0034335.299 File[011], Line[0239] [MODULE_LOWERSTACK] [clk:0x0001acd2]-->HCI_CMD:opcode:0406 len:3, 15001300-00407440-00130011-000d0004-00800000
0006299 03-28#14:18:17.958 204 0034335.343 File[011], Line[0789] [MODULE_LOWERSTACK] DISCONNECT OPCODE
0006300 03-28#14:18:17.958 205 0034335.390 File[201], Line[2466] [MODULE_LOWERSTACK] [LL] Disconnect Cmd: conn_handle 21 entry 10 reason 13

COM3_btsnoop_2023-03-28_14-17-41.cfa

COM3_2023-03-28_14-17-31.log

air_log_could_not_connect.btt

bugreport-taimen-RP1A.201005.004.A1-2023-03-28-14-19-27.zip

这个问题需要咨询google

from google:

Thanks for reporting. I found a race condition which can lead to this result. I'll prepare a fix, but since it does not reproduce on devices that we have, and to save some time, I would like to share an APK with the fix with you to verify it resolves the issue.

Can you provide a Google account on which I can share the APK once it is ready?

google 提供的新的apk: validator_realtek_diag.apk

Alice Zhou(周丽) 麻烦用这个apk压测试试看是否还能复现到这个问题

\