-
Notifications
You must be signed in to change notification settings - Fork 7.3k
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
IDF V4.3.1 examples a2dp-source no audio transmitted (IDFGH-5862) #7561
Labels
Comments
github-actions
bot
changed the title
IDF V4.3.1 examples a2dp-source no audio transmitted
IDF V4.3.1 examples a2dp-source no audio transmitted (IDFGH-5862)
Sep 15, 2021
esp_bt_gap_cancel_discovery function does not work properly on ESP-IDF V4.4.
|
Hi @nopnop2002, Thanks for your reporting! About the wrong behavior of
Thanks! |
espressif-bot
added
Status: In Progress
Work is in progress
and removed
Status: Opened
Issue is new
labels
Sep 23, 2021
espressif-bot
added
Resolution: NA
Issue resolution is unavailable
Status: Done
Issue is done internally
Resolution: Done
Issue is done internally
and removed
Status: In Progress
Work is in progress
Resolution: NA
Issue resolution is unavailable
labels
Oct 8, 2021
espressif-bot
pushed a commit
that referenced
this issue
Oct 12, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Using esp-v4.3.1 examples/ bluetooth/bluedroid/classic_bt/a2dp_source No audio is transmitted to the audio sink.
I had changed main.c so device name for ESP_SPEAKER test is ignored, and any BT device is used.
I have tested using 4.1.1 and this works correctly transmits the random noise.
With v4.3.1 I there is no audio.
so, with identical code 4.1.1 works, 4.3.1 fails.
(I'm using the example as test, I am having this problem on my production code after changing esp-idf version).
The v4.3.1 console log:
I (31233) BT_AV: bt_app_av_sm_hdlr state 1, evt 0xff00
I (35373) BT_AV: Scanned device: 00:23:02:32:14:f7
I (35383) BT_AV: --Class of Device: 0x240404
I (35383) BT_AV: --RSSI: -64
I (35383) BT_AV: Found a target device, address 00:23:02:32:14:f7, name MA650 Wireless
I (35393) BT_AV: Cancel device discovery ...
I (35393) BT_AV: Device discovery stopped.
I (35403) BT_AV: a2dp connecting to peer: MA650 Wireless
W (35403) BT_APPL: reset flags
I (35413) BT_AV: bt_app_av_sm_hdlr state 4, evt 0x0
E (37203) BT_APPL: bta_av_rc_create ACP handle exist for shdl:0
W (37493) BT_APPL: new conn_srvc id:18, app_id:0
I (37493) BT_AV: bt_app_av_sm_hdlr state 4, evt 0x0
I (37493) BT_AV: a2dp connected
I (39303) RCCT: AVRC conn_state evt: state 1, [00:23:02:32:14:f7]
I (39303) RCCT: AVRC remote features 24b, TG features 2
I (39313) RCCT: remote rn_cap: count 1, bitmask 0x2000
I (41233) BT_AV: bt_app_av_sm_hdlr state 5, evt 0xff00
I (41233) BT_AV: a2dp media ready checking ...
I (41233) BT_AV: bt_app_av_sm_hdlr state 5, evt 0x3
I (41233) BT_AV: a2dp media ready, starting ...
W (41243) BT_APPL: new conn_srvc id:18, app_id:1
I (41283) BT_LOG: bta_av_link_role_ok hndl:x41 role:0 conn_audio:x1 bits:1 features:x824b
I (41283) BT_AV: bt_app_av_sm_hdlr state 5, evt 0x3
I (41283) BT_AV: a2dp media start successfully.
I (41283) BT_AV: bt_app_av_sm_hdlr state 5, evt 0x1
I (51233) BT_AV: bt_app_av_sm_hdlr state 5, evt 0xff00
The text was updated successfully, but these errors were encountered: