Page History

...

•  Alexander, Wassim, Charnjiv, Nadim, Gerald, Guru, Piotr, Stefan, Gunnar, Philippe
• guest: Richard
• apologies: Sachin, Blake

Minutes

Status reportIntroduction

• Richard introduces himself and explains his interest is in running multiple instances of Android Automotive inside a vehicle, he is in working on a proof-of-concept to investigate and identify whether some parts could be made common among the instances, for instance at the HAL level, our objective is to run the business logic on a virtual machine on a hypervisor
• Charnjiv: do you intend to have this certified ?
• Richard: no, it is not intended, it is proof-of-concept work

Status report

• Philippe introduces then the status report and hands over the presentation of the technical parts to Alex, Stefan and Wassim
• VHAL / Vehicle Data APIs
  • slide #3 - graphql

    • code is at: https://github.com/GENIVI/vss-graphql

    • Alex: shows the readme on graphql and the docket setup

    • Alex: example can be used on firefox and chrome and allow you to play around with the grammar

    • Alex: we need to scope down the number of signals for the propf-of-concept

    • Alex: IMHO we miss in VSS some concepts we have in graphql, we need to extend the VSS specification

    • Gunnar: asks Alex to provide details on what is missing in VSS

    • Alex: shows a wiki page comparing the syntax of types, lists, arrays, enumerations in VSS and graphql, the comparison will be provided offline

    • Gunnar: ITSM this relates to the tooling that makes the translation from (VSS) vspec to graphql, has the tool been published as well

    • Alex: I needs to ask Daniel and Adnan about publishing the tool

  • slide #4 - VSS feeder
    • code is at: https://github.com/GENIVI/vss-feeder
    • Stefan: explains the VSS feeder will receive inputs from a vehicle simulator
  • slide #4 - authentication service
    • code is at: https://github.com/stefanwysocki/aasig_dev_platform/tree/develop/vendor/genivi/modules/VssAuthenticationService
    • Stefan: explains the status of the implementation, the low-hanging fruit are identified as TODOs in the code
• Audio HAL
  
  • slide #5 - audio system level options
    • Wassim: explains that the "final" design will not be one of the two extreme options of having all audio control in or out Android Automotive (AA provides sources and sinks only or AA controls the complete audio system) , the solution will be somewhere in-between
  • slide #6 - raw streams management
    • Wassim: explains how we intend to manage raw streams in a proof-of-concept (as compared to what Android Automotive currently does)

31 March 2020 Meeting

• AASIG status report is here

...