-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
HFP-AG example not working as intended (IDFGH-6114) #7792
Comments
I am testing the same configuration as @MarcosHWconfig and I also have the same problem with the sinusoid. |
hi all, my colleague is handling this issue, could you @BetterJincheng please provide a patch here? Thanks! |
Hi all, This is the patch for this issue towards IDF_V4.3. Turn to us if any problems. |
Hello @BetterJincheng and @Wth-Esp, thanks for the patch. |
Hi @skateskate, Codec (code & decode) for HFP is mSBC with specific parameters. It transfers 240 Bytes every 7.5 ms. So in the demo we need to |
Environment
Problem Description
I flashed the
esp-idf\examples\bluetooth\bluedroid\classic_bt\hfp_ag
example in my LyraT after modifying the following parameters from the menuconfig:BR/EDR Sync(SCO/eSCO) max connections --> 1
BR/EDR Sync(SCO/eSCO) default data path --> HCI
audio(SCO) data path --> HCI
Wide band speech --> ON
From the example code I see that the AG sends a sinusoid to the connected client. I used several pairs of bluetooth headphones (fully functional) as clients but the only thing I hear is noise, definitely not a sinusoid. I have recorded the received signal, here is the plot:
Expected Behavior
Hear the sinusoid correctly from the client side.
Actual Behavior
I hear a strange noise from the client side, not a sinusoid.
Steps to reproduce
esp-idf\examples\bluetooth\bluedroid\classic_bt\hfp_ag
BR/EDR Sync(SCO/eSCO) max connections --> 1
,BR/EDR Sync(SCO/eSCO) default data path --> HCI
,audio(SCO) data path --> HCI
,Wide band speech --> ON
app_hf_msg_set.c
and set the MAC address of the clientcon
and after connection typecona
The text was updated successfully, but these errors were encountered: