...
- GENIVI Audio Manager - Q&A after review of the docs as discussed in last week's call
- PoCs architectural design
- backlog update
- AOB
Thursday 5 March - 11:30am CET
Participants
- Wassim, Ruslan (EPAM, automotive systems) Gunnar, Philippe
- apologies: Nadim, Bartosz, Piotr
Agenda
- GENIVI Audio Manager - Q&A after review of the docs as discussed in last week's call
- PoCs architectural design
- backlog update
Minutes
Roundtable
- Ruslan represents Andrii in today's call
GENIVI Audio Manager
recap on the decision made by the team last week to get awareness on the GENIVI Audio Manager
Gunnar: the code might not be reusable as such in an Android Autmotive context, but it is worth understanding the archictectural design of the Audio Manager
Gunnar: Android is lacking the flexibilty audio systems have in a car, this project intends to enhance this
Wassim: there are deployed systems using the linux based GENIVI Audio Manager or using Android Automotive, who should take care of the audio management in the Android context ?
Gunnar: there 2 tracks one is to find out the audio management requirements in the Android Automotive context, track #2 is to achieve this with the appropriate technologies, we need to decide first what we want
Wassim: we need to define the common problem statement the Audio HAL wants to solve
Q&A after review of the GENIVI Audio Manager docs is shitfted to next week's call
Discussion on the Audio HAL project workplan
- Wassim: Audio effects are critical because they fall into the domain of custom interfaces in Android Automotive
- Wassim: the networked audio systems exemplify why a car is different from a smart phone
- Wassim: my vision is that with the networked audio systems Android Automotive will become an OS for distributed systems
- Gunnar: GENIVI is now focusing on system-level integration
- Gunnar: for the VHAL our objective is not only to provide more vehicle data (than the Google vehicle properties), it is also to dig into the Android Automotive based head unit and integrate with the rest of the vehicle systems
- Wassim: Android Automotive uses a wrapup around Alsa, we do not need to change this, what we should look at rather is how to solve the custom interfaces in a general way as the VHAL is doing for the access to vehicle data
- Wassim: what about graphics ?
- Gunnar: graphics came as a side track in the GSHA project, we look for instance at the combination of the Wayland (linux) stack and the Android Automotive stack, this was not in the AASIG actually, there is one company working on an implementation for this
- browsing through the collaborative tools for AASIG: wiki structure and jira project
- Philippe: explains the way we structure the work in the SIG from the identification of problems to solve, the brainstorming on architectural design options and possible prood-of-concepts to validate the architecture concepts and the definition of work breakdown structure for the PoC implementation
Thursday 27 February - 11:30am CET
Participants
- Nadim, Bartosz Cichosz, Gunnar, Andrii, Bartosz Bialek, Piotr, Stephen, Wassim, Suhasini, HenricHenric
- apologies: Philippe
Agenda
- Networked audio devices
- PoCs planning
Minutes
Networked audio devices
Gunnar: Le'ts start with the networked audio devices overview. It can be good input information before discussing PoC details
Suhasini presents her slide deck (link)
...
- Suhasini (Analog Devices), Henric (Bosch), Nadim (Mobis), Bartoz (Tieto), Philippe
Agenda
- Overview of last week's F2F outcome
- Call for participation
- AOB
...