-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
A2DP not working with Car Stereo (IDFGH-11166) #12334
Comments
Hi, `I (663) main_task: Calling app_main() W (1373) BT_BTC: A2DP Enable with AVRC |
@divyansh Thank you for your feedback. These warnings do exist for certain reasons, but theoretically they will not affect the establishment of the connection. Is it still not possible to connect to your device Using ESP-IDF A2DP_SOURCE? |
Hi, |
@divyansh Sorry for late reply. Please attach the whole logs on ESP32 side. Thanks! |
In If pin_type is ESP_BT_PIN_TYPE_VARIABLE, pin_code and pin_code_len will be ignored Does the code below solve the issue? Haven't tested this . I'm facing this issue as well . If the solution is something else would like an input on it. |
@Joel-Joseph-Raju It will do help if yuou attch the whole logs. |
Thanks for reporting, will close due to inactivity, feel free to reopen with more updates. |
Answers checklist.
IDF version.
Latest version installed with fresh Arduino installation
Espressif SoC revision.
VID: 0x1c04 PID 0xEA60
Operating System used.
Windows
How did you build your project?
Command line with Make
If you are using Windows, please specify command line type.
None
Development Kit.
ESP wroom 32
Power Supply used.
USB
What is the expected behavior?
As the A2DP example ESP32_A2DP_example_sender_8bit works perfectly fine with BT speakers which are not having any pin.
But Car stereo's which we call as Android Headup Display have a default pin "0000".
I am unable to connect the ESP32_A2DP_example_sender_8bit example project to the Android Head up Display.
My setup function and isValid funciton is as mentioned below rest is unchanged.
`bool isValid(const char* ssid, esp_bd_addr_t address, int rssi){
Serial.print("available SSID: ");
Serial.println(ssid);
return true;
}
void setup() {
Serial.begin(115200);
a2dp_source.set_ssid_callback(isValid);
a2dp_source.set_pin_code("0000",ESP_BT_PIN_TYPE_VARIABLE);
a2dp_source.set_ssp_enabled(1);
a2dp_source.set_auto_reconnect(false);
a2dp_source.start(get_data_frames);
a2dp_source.set_volume(30);`
What is the actual behavior?
Here I am explaining just what happens when we connect the Android Headup Display ( AHUD )with our Android Phone.
When the search for new bluetooth device is started, and the device (AHUD) is clicked upon a pop comes for entering password.
I am guessing this problem is coming.
In ESP32, I am unable to change the program to work with AHUD as it throws a pin pop on Android device whereas in ESP32 i am unaware of this function.
I have enable SSP in the code and set the pin but still it deosn;t connect.
Steps to reproduce.
a2dp_source.set_pin_code("0000",ESP_BT_PIN_TYPE_VARIABLE); a2dp_source.set_ssp_enabled(1);
...
Debug Logs.
More Information.
a2dp_source.set_pin_code("0000",ESP_BT_PIN_TYPE_VARIABLE); a2dp_source.set_ssp_enabled(1);
The text was updated successfully, but these errors were encountered: