Files
gfps/1.+手机端点击+ring+stop,耳机端并未停止响铃.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

74 lines
3.3 KiB
Markdown
Raw Blame History

This file contains invisible Unicode characters
This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# 1. 手机端点击 ring stop耳机端并未停止响铃
<span class="jira-issue" jira-key="BB2BUG-18476"> <a href="https://jira.realtek.com/browse/BB2BUG-18476" class="jira-issue-key"><img src="https://jira.realtek.com/secure/viewavatar?size=xsmall&amp;avatarId=10916&amp;avatarType=issuetype" />BB2BUG-18476</a> - <span class="summary">\[BB2\]\[8773ESL\]\[v3.13.0.7\]\[GFPS\]\[LE Audio\]Find device响铃时有时候停止响铃失败</span> <span class="aui-lozenge aui-lozenge-subtle aui-lozenge-current jira-macro-single-issue-export-pdf">In Progress</span> </span>
<span style="color: rgb(32,33,36);">手机端点击 ring stop耳机端并未停止响铃</span>
<span style="color: rgb(32,33,36);">原因是:</span>
<span style="color: rgb(32,33,36);">手机端有尝试发送停止响铃的cmd 给耳机端,</span>
但是因为我们耳机端没有发credit给手机
导致手机端认为耳机端没有剩余的credit了
进而手机端没办法发送停止响铃的cmd到耳机端
\
From google
\
hi tony:\
112745 pair\
112755 connect LE Audio\
112807 Ring Left112814 Mute Leftsucess\
112823 Ring Right112827 Mute RightMute Right fail
Line 135172: 07-13 11:28:26.957 10166  8442  8442 I FastPair: FindDevice: Sending ring event, pre left false, pre right true
\
//it seems fast pair has already send mute right cmd\
Line 135173: 07-13 11:28:26.957 10166  8442  8442 I FastPair: FindDevice: Sending ring event, left false, right false\
Line 135174: 07-13 11:28:26.958 10166  2946  4749 I NearbyDiscovery: FastPair: send ring, device=XX:XX:XX:XX:65:0C <span class="error">\[CONTEXT service_id=265 \]</span>
however in phone's hci log, 112827 we do not see  mute right cmd
it seems that after 11:28:22.960783, FP cannot send any message via L2CAP.
<span style="color: rgb(23,43,77);">LE L2cap channel is not disconnected in the log. </span>
<span style="color: rgb(23,43,77);">Can you help to see why the PSM cannot be found? thanks</span>
\
Hey Danni,
I filter the HCI with btl2cap.psm == 0x0080, Seeker can receive the battery info from the L2cap event stream,
but the problem here is Seeker cannot send message to the Provider.
\
It looks like a similar issue (google internal ticket: <a href="https://issuetracker.google.com/issues/158958522#comment12" class="external-link" rel="nofollow">b/158958522#comment12</a>) when we worked with realtek on ringing through RFCOMM.
From <span class="nobr"><a href="mailto:wade_li@realsil.com.cn" class="external-link" rel="nofollow">wade_li@realsil.com.cn<sup><img src="images/1.+手机端点击+ring+stop耳机端并未停止响铃_1f96683b.gif" /></sup></a></span> on Jul 2020.
> I check the differences with the HCI snoop log again. And find that phone has no RFC credits continue to send command.
>
> Actually, I will try to send credits after received RFC data.
Could you help to see if the issue can be fixed when Provider handles the credit correctly?
Thanks!
\
<span style="color: rgb(32,33,36);">hi  tony:</span>\
<span style="color: rgb(32,33,36);">The reason is Provider do not send credit to seeker, we have already fix this issue and test sucess.</span>\
\
<span style="color: rgb(32,33,36);">we have another problemsome times seeker do not create LE L2CAP channel,  I will create another jira, thanks</span>
\
\