...
review of the backlog for audio HAL
- epic: audio HAL analysisaudio HAM implementation - BT
Jira server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key AASIG-75 Jira server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key AASIG-76 - we look at the diagram attached
- Piotr: native mechanism to connect to a BT device is shown on the diagram
- Potr: a second option is to connect the BT device to the platform directly and use the BT infrastructure and pass the audio data to Android
- there is a need to update the diagram
- discussion on the options
- discussion on accessing the hw
- accessing the dsp through 2 different VMs ?
- either you own the dsp on one machine only and you do not have a virtualization problem
- or you run the dsp as a service like a networked device
- Piotr mentions the work done by Opensynergy and Qualcomm with Google on virtualizing Android Automotive
- TODO Wassim and Piotr will capture the discussion on a tech note
- Piotr: added offline (in a email) the questions he raised during the call
- BT headset handling should be realized by Android stack or host OS - virtualized/containerized environment, I guess we agreed here that such case should be handled by Android and its BT stack
- how to properly utilize DSP for BT headset, especially in virtualized environment, DSP as a service?
- Google is introducing GKI (Generic Kernel Image) concept - how this could affect DSP and ECNR usage?
- ECNR for BT headset - how this should be handled, should it be?
- Jira ticket commented
...