Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: updated a draft of agenda

...

TODO

  • The Demonstration needs to be planned – set up a separate call with Piotr + interested people (Wassim, Suhasini, Nadim).  30 minutes may be enough. Gunnar

...

  • (30 min) The Demonstration
  • (10m?) Why AASIG does investigation into the Audio subsystem
    This is good to have. This is sort of an intro to what the aim of this group is. Should this come here, or before, in the status report?
    Would it be an abrupt flow, if we talk about who we are and what we do after demonstration?

    • Here is also where the marketing impact slide from Nadim will be useful 

  •  (30m) Audio systems in automotive and where android fits in.
    A small intro to what the audio system in cars is today might be useful to drive the discussion. We can then bring in the following options :
    * android as audio router - routing different streams?
    * android as a audio master (what is the term master referring to here?)
    * android as a source only ?
    * what are the most prominent use cases for infotainment headunit and how does android help/ hinder that as compared to linux / QNX / custom OS?

    This discussion will also serve as an intro to Networked audio devices ( which is a specific use case of when Android is just used for routing various streams throughout the network in the car. )

  • (20 m?) Supporting and controlling external audio devices -

    • trunk amp / Rear seat entertainment units 

    • encryption - decryption for content protected streams ( netflix / spotify streaming services)

    •  Also communicating between containers / vms ?



Session 2 (90 min)

  • (10m) Virtualization ( need to research more to get specific questions to drive discussion )


  • (10m) Containerization ( need to research more to get specific questions to drive discussion )


  • (10-15m) Latency :
    Audio latency is quite an important aspect for some advanced applications/ processing in audio.
    * How is latency measured today.
    * How can we support low latency applications with Android?

  • (30m) Should we be looking at using some AGL components with Android?
    * Are there any features in AGL ( which is already adapted to automotive usecases) that can be brought in directly into Android.
    * Any designs that can be adapted.
    * is there scope for maybe making this more similar in design to AGL ( for specific features)


  • (15 -20m) Use case supports -

    • (10m)Bluetooth device control and support
      ( Henric to give some inputs here)

    • (5 - 10m)Safety implementation in Audio?
      <<taken from list of prioritized topics page>>
      Android Audio subsystem is developed only for infotainment purposes. Safety-related features need to be implemented in another RTOS


      • Need to share the same hardware between 2 OSes
        Running Android as a virtual machine inside RTOS leads to problems with scheduling of audio processes

        Remark : This going towards the other extreme of making a system outside of Android to control safety-related features. It should be address in the POC as well.

        extracting raw streams helps with this point (handing over also relates to this)

  • (15m) What problems are we facing where just android is not sufficient?
    • <<need to brainstorm / prepare leading questions>>
  • (5m) Question audience to find out who are all involved with google and try to connect that with AA-SIG work and get them to drive things from within AA-SIG also
  • (15 min) Testing ? 
    • Stephen can present 10-15 minutes (including Q&A) on the Lava Test Farm status


...

...