Page History

...

• Philippe: what was discussed with Sriram. I think it's an important conversation. Gunnar's concerns as well.
  • Wassim: what exactly should we discuss?
  • Philippe: sharing the minutes of the virtual summit.
  • Concern: why are we not just using Android. Are there features that Android does not support?
• Wassim: What is the background of Sriram?
  • One of the architect of GENIVI, now manager at a company that uses GENIVI products and solutions used in production already
• Wassim: The base questions was: why do we need the proxy? Why can't we do everything with the Android Audio HAL
  • I think this is the question that we need to answer as it's the base of Sriram's question
  • We cannot answer it now, we need to check if Android Audio HAL fulfills all the requirements
  • Piotr: The proxy is (as agreed in the virtual summit) a placeholder for now
• Any functionality that Android Audio HAL cannot fulfill are done by this placeholder
• Philippe: maybe we need to document the features that we would like to try
  • We need to try to do something outside of Android and check if it makes sense
  • Wassim: we can answer the question of Sriram when we have a working PoC and try out specific use cases to check
• Philippe: we need to come up with more detailed work plan and we need to identify several stages and add topics to it. An example work plan would look like this:
  
  1. What do we do to handle the low latency? List our solutions
     
  2. Experiments to check our solutions with the PoC
     
  3. Answer the question: Can this be handled from within Android or do we need outside dependencies
  4. Not sure however if the low latency problem has anything to do with the audio manger. Maybe it should be dealt alone.
• Gunnar: there are some topics such as low latency, the ability of the application to control where the audio is going, the safety control audio, these are some of the topics that can be added outside the android platform
  • Nadim: is this work plan within the milestones?
  • Philippe: yes exactly we need to expand on these milestones and detail the work to be done
• Philippe: maybe we can create some sort of a WBS to start with it
  • Unknown User (wassim.filali) : create a confluence page for thisto place the ideas and the WBS
    
  • Unknown User (wassim.filali) : communicate with Piotr Krawczyk and Unknown User (bartoszbialek)  and others to get the ideas for the next steps before the milestones → Initiate the WBS creation
    
• Nadim: what about the milestones are they still the same
  • Philippe: well we cannot change the dates for sure
    
  • Wassim: the milestones will not contradict each others so let's keep them as they are
    

Discussion about hardware

• So the two milestones to create a software, then create hardware, these can be interchanged, which one to do first?Wassim: Do we create the PoC using software simulation only or do we need a real real HW? (Unknown User (wassim.filali) : please correct me on this question)
  
  • if we try on emulator but no without a real hardware then it's not really a proof
  • If we start at hardware we might get stuck with some hardware issues
  • Piotr: Maybe we can get the input of Sriram here as well
  • @PhilippePhilippe Robin : can we get the input of Sriram on this? Wassim:Please wait for Wassim to better clarify the question.
    
  • Gunnar: can 't we do both?
• @NadimUnknown User (niskandar) : Add path to the proof of concept (in the other page) https:code https://github.com/GENIVI/android-external-audio-mixing
• @PiotrPiotr Krawczyk : could you please add to the read me note, how to compile on virtual server
• Gunnar: We have several suggestions but if you need as a company a certain hardware then we can select it
  • It's more about who is writing the software because if you want providing the software to support your board then you can port it to your board. More about what software is on the board that we can use.we are doing
    
  • Piotr: Qualcom is out of scope, it would be very nice cause it needs minimal efforts to have nice solutions but their support is rather minimal for us. They are more mobile oriented.
  • Henric: preference is Renesas
  • Suhasini: no preferences for the hardware
  • Nadim: no preferences for the hardware
  • Hikey is low cost with support
  • As a vote: Renesas seems to be the first choice and Hikey as the second choice
• Wassim: how will the hardware be accessible?
  • Philippe: it makes sense if each member would have a board on the desk if you want to listen to the audio
  • Gunnar: there will be a global testing center with Renesas' support where we can do some testing on it, but if we want to listen to something a hardware board is better
  • Gunnar Andersson : what exactly which HW from Renesas to order? Please write it in the new page that Wassim is creating
  • We can also directly ask Steven

Gathered Todo's:

•  Unknown User (wassim.filali) : create a confluence page to place the ideas and the WBS
  
•  Unknown User (wassim.filali) : communicate with Piotr Krawczyk and Unknown User (bartoszbialek)  and others to get the ideas for the next steps → Initiate the WBS creation
•  Philippe Robin : can we get the input of Sriram on this?
•  Unknown User (niskandar) : Add path to the proof of concept code https://github.com/GENIVI/android-external-audio-mixing
•  Piotr Krawczyk : could you please add to the read me note, how to compile on a virtual server
•  Gunnar Andersson : which HW from Renesas to order?
  

Anchor
AUDIO_HAL_CW2019 AUDIO_HAL_CW2019

Thursday 7 May - 11:30am CET (AUDIO_HAL_CW19)

...