Versions Compared

Old Version 13

changes.mady.by.user Suhasini Raghuram

Saved on

compared with

New Version 14

changes.mady.by.user Unknown User (wassim.filali)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

(AM) 9:00-9:30


Report30

Android Automotive SIG #2 - Audio HAL
"Status Report"

  • introduction what we want to do

    • 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 
  • what we have achieved and what we want to add in the future
  • demo architecture and demo itself

Presenter: Piotr Krawczyk (Tieto) Pre-recorded?

Supporting presentation material: Wassim Filali

9:30-9:45Break15Sponsors' Videos
9:45-11:15Working Session90Android Automotive SIG #2 - Audio HAL

Moderators: Raghuram, Suhasini / Filali, Wassim

Abstract: 

Audio management is one important aspect and constraint for the utilization of Android Automotive for the IVI unit. During Q2 2020, the AASIG AUDIO HAL project team has undertaken the design and implementation of a proof-of-concept demonstrator focusing on the routing and control of external data streams. 
The AASIG AUDIO HAL project team will present a status report of the proof-of-concept implementation
and explain the design choices made. The following next steps will be then comprehensively debated:

  • Proof of concept : Assessment of proof-of-concept demo implementation TRL (Technical Readiness Level)
    • Assumption (to confirm with Piotr) that demo is presented before starting with this section


  • Topics priorities : Update of the list of prioritized topics for audio management and identification of other proof-of-concepts implementation based on this list


  • Contact with Google : Ensure project participants have opened, or are planning, a discussion to achieve synchronization of activities with Google's Android team
    • might be subject to misunderstanding as ongoing work is connected to the daily Android development (directly or indirectly)
    • neutral question about interaction channels
      • interaction with Google's events (Bootcamps,..)
      • contributions to AOSP
      • features request
11:15-11:30Break15Sponsors' Videos
11:30-13:00Working Session90Android Automotive SIG #2 - Audio HAL

Moderator: Raghuram, Suhasini / Filali, Wassim

Abstract: 

continuation of the working session

...

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

...

Timed Agenda

Session 1 (90 min)

(30 mn) Role of Android in Audio System (Car Audio System)

    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 control master - master controller that controls the overall audio system.
    * Mention of an alternative and question if anyone would consider usage of android as a source only ?*

(30 mn) Use cases to be covered with Android

  • what are the most prominent use cases for infotainment headunit and how does android help/ hinder that as compared to linux / QNX / custom OS?
    • What are the applications ?
      • Telephony
      • Voice assistance
      • Multichannel video streaming
    • Importance of Audio zones (is it important or possible to play two music at the same time on cabin speakers, or are zones rather for headphones, or rather only to restrict to telephony in one zone)
    • what if two androids are working in the system? ( how do we sync between the two?)

(30 mn) Audio transport in the car network

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 - - how android would handle this?

    • transporting protocols (AVB, A2B, MOST )

    • 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)

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

    • Communication between host and guest ( hypervisor or container?)
    • What works best? - shared Performance vs practicality ? Shared memory ? TCPIP ? 
    • VirtIOSVirtIO? ( Android 11 is pointing to this)
    • Depends on system design - do we really need to virtualize?
    (10m)
    • Audio transport and communicating between containers / vms ?
    • if a virtualized Ethernet supports AVB ?

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

      • Partitioning of Audio HAL and vendor development
      • Preference over virtualization
      • Transport mechanism
      • How to control effects?
    • using different OS, one for infotainment and one for safety
  • ((10-15m) Latency & performance

    • Latency
      Audio latency is quite an important aspect for some advanced applications/ processing in audio (Telephony, Speech).
      * How is latency measured today (Testing ITU).
      * How can we support low latency applications with Android? (AAudio,...)

    • CPU offloading
    • Low latency framework ? the framework is not directly one layer above HW. What do we do when there are many other layers above HW?  (Gaming, AAudio)
    • << need diagrams on slide >>

  • (30m) Should we be looking at using some AGL Linux components with Android?
    * (AGL, Linux Audio Manager)

    • Example : use Audio control from Android and audio routing transport libraries from AGL
      • Any designs that can be adapted, (if possible to add design picture to explain the intention)
    • counter example (bad example) : mixing two audio managements concepts in the same system, one in Android and one in Linux
      • integration complexities

    • Are there any features in

    AGL (

    • Linux  which is already adapted to automotive

    usecases)

    • use cases 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 -20m15m) Use case supports -

    • (10m)Bluetooth device control and support
      ( more research )

      • bluetooth control to android makes most sense now. 
      • << Present our analysis and get feedback >>

    • (5 - 10m) Safety implementation in Audio?<<taken from list of prioritized topics page>>

      • interaction of Android with external safety signals (or in general with external sources)

      • assumptions : 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)

  • (15 min) Testing ? 
    • Stephen can present 10-15 minutes (including Q&A) on the Lava Test Farm status
  • (15m) Open questions to what Android did not solve yet (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 statushow to improve interactions and feedback to AOSP and future versions of Android


    ...

    ...