-
Notifications
You must be signed in to change notification settings - Fork 21
Bluetooth: Classic: CLCC report NULL when finish. #103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
Conversation
zhangyuan376
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add rootcause for commit
19e6d08 to
75b54ba
Compare
Done |
a62a4f2 to
8fcf88b
Compare
8fcf88b to
e2987db
Compare
| clear_call_without_clcc(hf); | ||
| } | ||
|
|
||
| if (atomic_test_bit(hf->flags, BT_HFP_HF_FLAG_USR_CLCC_CMD) && |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what is the procedure of barrot or Android Stack?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
barrot reports a call with index 0.
Android reports ok in bta if client_cb->send_at_reply is set
e2987db to
de7546b
Compare
bug: v/78002 Rootcause: The CLCC API does not report when it finishes, app cannot know whether the CLCC procedure has ended. Signed-off-by: liyuheng <[email protected]>
de7546b to
6a1d4c6
Compare
bug: v/78002