gfps/1.+手机端点击+ring+stop，耳机端并未停止响铃.md

1. 手机端点击 ring stop，耳机端并未停止响铃

BB2BUG-18476 - [BB2][8773ESL][v3.13.0.7][GFPS][LE Audio]Find device响铃时，有时候停止响铃失败 In Progress

手机端点击 ring stop，耳机端并未停止响铃

原因是：

手机端有尝试发送停止响铃的cmd 给耳机端，

但是因为我们耳机端没有发credit给手机，

导致手机端认为耳机端没有剩余的credit了，

进而手机端没办法发送停止响铃的cmd到耳机端，

\

From google：

hi tony:
11：27：45 pair
11：27：55 connect LE Audio
11：28：07 Ring Left，11：28：14 Mute Left，sucess
11：28：23 Ring Right，11：28：27 Mute Right，Mute 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 [CONTEXT service_id=265 ]

however in phone's hci log, 11：28：27 we do not see  mute right cmd

it seems that after 11:28:22.960783, FP cannot send any message via L2CAP.

LE L2cap channel is not disconnected in the log.

Can you help to see why the PSM cannot be found? thanks

\

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: b/158958522#comment12) when we worked with realtek on ringing through RFCOMM.

From wade_li@realsil.com.cn 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!

\

hi  tony:
The reason is Provider do not send credit to seeker, we have already fix this issue and test sucess.

we have another problem：some times seeker do not create LE L2CAP channel,  I will create another jira, thanks

\

\