...

This info is to be moved in the repo readme, the current readme is not at the root of the repo to avoid aosp directory pollution, therefore this info will move once a new structure of repo is created with manifest and new readme

Brainstorming about breakdown rework

Use cases

1) external Amplifier, controlled by Android only (cross ECU itnerface used by headunit only)
2) interact of an Android Audio ECU with the rest of the audio system other ECUs (e.g. remote control - e.g. non Android system)
3) interact with the Audio System from a server

Relations to existing work in other SIG

CVII : Common Vehicle Interface Initiative
VSS : Vehicle Signal specification
VSC : Vehicle Service Catalogue (list of interfaces)

Audio and VSS, data interfaces,...

common model for data (call functions with params, services, interfaces, franca,...)

-no dealing with streaming data, rather simply connection points urls exchange
-can we define similar things to audio e.g. currently played track, volume,... ?
-requests to add media in VSS

-standardized interface for audio/media streaming, renewed interest by Hyundai
- complex question, OEM => standardize / Netflix => App custom standard

- if possible to add info in VSS
- different scope from cross ECU interfaces

-prevent fragmentation by collecting a survey about state of the art
- MPRIS dbus standard