I am trying to figure out how this Android architecture will work. I would be grateful for any assistance you will provide on this. I have seen many discussions around which go in-depth however, bigger picture is not clear. So I am writing here to understand it
I am trying to work with Android ‘O’ and Bluetooth dongle. Currently we are working on the TI board to support it (TI doesn’t currently supporting BT in the new SDK release, earlier they have support for WLINK). I’ve seen discussion around TI /BT /WLINK here , Traditionally most of are using I2S instead of HCI and HCI is so discarded that latest google code is not supporting (broken) and TI has no support for HCI.
We are using the BT dongle through mini-USB cable, establish the interface over the HCI. Now, when we want to establish the Voice call we need SCO (SCO over HCI is broken) , so my concern here is how we should achieve the Voice call over the BT in this case. I am attaching a diagram of “MY” understanding and will appreciates any input or correction.
Specifically, I want to know the answers of the following questions:
- How we can do SCO in this case ( as we have USB no I2S)? Is HCI is the only way?
- With Android O,Fluoride latest code, do we need to set the A2DP Sink routing to work or it is working straight out of the box? I have seen some comments who agree it is working however I haven’t seen so far.
- If HCI is the only option then current Android O doesn’t support it , is there any alternative?
Please feel free to share your thoughts.