I think I am not able to resolve this issue because I am missing understanding of new 5.35 architecture. So I have following doubt:ġ) Why there is new android package in blueZ stack? What's the development idea behind this?Ģ) Why SBC capabilities are initialized in android/hal-audio-sbc.c, how non-android device will access SBC capabilities?ģ) How in my embedded environment, I can use android/hal-audio-sbc.c to get SBC capabilities? My embedded device is RTOS based and I have nothing to do with android. In blueZ 5.35 there comes the new package android/hal-audio-sbc.c, in this package SBC coded capability are set. avdtp_media_codec_capability are set in endpoint_getcap_ind() function in AVDTP layer, which is as per my expectation. In 5.35, sbc_getcap_ind() function is not available. So this capability packet I can send back to Phone. In sbc_getcap_ind(), both sbc_codec_cap and avdtp_media_codec_capability are initialized. In Bluez 4.97 code, I am getting SBC codec capability from sbc_getcap_ind() function in AVDTP layer. In ideal case the capablity will look like figure 1. I am updating Bluez 4.97 to 5.35 in my embedded device.įor A2DP connection, we have to share SBC codec capabilities.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |