List of prioritatized topics for the Audio HAL
Next Meeting - Thursday
...
23 January - 15:00 CET / 20:30 India / 6:00am US Pacific
Zoom dial-in
...
- review of the priorities of topics of interest for the Audio HAL project (continuation)
- discussion on additional extensions to Audio HAL that "would not change too many things"
- discussion on the part of the Audio HAL that could common for all SoC vendors
- AOB
...
- the Audio HAL project (continuation)
- Backlog
- discussion on additional extensions to Audio HAL that "would not change too many things"
- discussion on the part of the Audio HAL that could common for all SoC vendors
- AOB
19 December 2019
Participants
- Andrey, Suhasini, Piotr, Stephen Lawrence, Gunnar, Philippe
Minutes
upcoming F2F meeting for the Vehicle HAL project
- decision on the dates was made => 4-5 February, at BMW, Munich, Germany
- Philippe: we have an opportunity to coschedule (and colocate) a meeting for the Audio HAL project
- /TODO/ all fill in the participation table and indicate whether you would be available and interested by joining a meeting either F2F or via telco
Review of the list of prioritarized topics (continuation)
13- BT handsfree
Suhasini: it is rather a question of multisource management
Andrey: would agree it is related to multisource management
Gunnar: on the mobile phone, the BT role is the server role, the car is more the handsfree role
Andrey: we need to clarify the automotive use cases
the group should work on use cases but there are more fundamental questions to be solved on multi source management
14- Android does not implement all features required by customer.
Andrey: this is about multisource management, support of external devices, limited number of priorities, etc. the various bullet points can be distributed over the table
/TODO/ Andrey distribute the bullet points among the table
Piotr: what are the priorities you are talking about ?
Andrey: these are the priorities related to phone calls, I will clarify this when I do the split (phone calls vs. not phone calls)
15- Android Audio subsystem is developed only for infotainment purposes. Safety-related features need to be implemented in another RTOS
Andrey: thinks the safety-related audio features are not in the scope of this group
Piotr: we need to keep in mind that there is a higher priority audio functionnality in the system
Gunnar: it might be worth discussing how AA can use external components that manage the higher priority audio functionnality, these are system-level considerations
/TODO/ Gunnar add HERE what was discussed in this call about the system level architecture Thanks
Gunnar: do we look for solutions on AA side first or do we look also at the general system design for audio ? my recommendation is to start something concrete at the design level
16- Android way of extending its functionality is developing vendor extensions without modification of the framework
Piotr: we need to avoid changing the framework because there is a lot of manual work necessary to track the changes that need to be taken into account
Andrey: agreed
Andrey: we have a mechanism in Harman to follow up the changes in AOSP
Gunnar: we need to start the design work asap and as a general principle we do not change the framework
17- Google is still very “hand wavy” about solution
Gunnar: WR has a lot of work to implement the audio HAL by themselves
Piotr: people look at the code of android directly, I would like to get some tooling to cope with the fact the doc will not be provided by Google anyway
Piotr: tool can take care of the configuration setting, helping with work we do currently manually
Andrey: we need to adapt to the Google way, we cannot change this
Piotr: we can translate HIDL to Franca and provide a more flexible way of implementing things
Andrey: we are considering similar ideas within Harman
Gunnar: agreed, it is part of the discussion on how to use a common interface in multiple systems (with the remote interfaces, not only on AA), something like CommonAPI, there is a generic discussion to have there
18- Genivi ?
Gunnar: in my opinion this is a question about the role of GENIVI, we need to think about what could be the outcome of the group, as I said before, the question is rather to find solutions, it can be anything from a formal specification, to guidelines and even code
- category changed to "Deliverables"
- Philippe: IMHO this is also a question about the recycling of earlier work done by GENIVI, e.g. the audiio manager, we said we would organize a presentation of the GENIVI audio manager and the automotive use cases it supports
- /TODO/ Gunnar plan a presentation of the GENIVI audio manager in Q1, 2020
list of prioritarized topics
- /TODO/ all review the minutes of 12 & 19 December together with the list of prioritarized topics and identify any gap / missing points in the list
Next call
- Thursday 23 January, 15:00 CET / 20:30 India / 6am US Pacific
- agenda
- review comments for the list of prioritarized topics
12 December 2019
Participants
- Andrey, Suhasini, Piotr, Jimhyuk Jung (mobis), Patrick Carlisle (mobis), Stephen Lawrence, Giovanni, Gunnar, Philippe
- apologies: Wassim
...
- Philippe: the Vehicle HAL project intends to have a F2F meeting in early Q1/2020, BMW will host the meeting in Munich, Germany
- look at Vehicle HAL F2F Planning - January4-5 February 2020 - Organization
- Philippe: it might be an opportunity for the Audio HAL project to meet F2F at the same date & location
- /TODO/ all check about your availabilities and the clearance of travel expenses
...
- Vehicle HAL project will meet F2F at the end of January / beginning of February, this is an opportunity to colocate a F2F meeting for the Audio HAL project
- please look at Vehicle HAL F2F Planning - January4-5 February 2020 - Organization and fill it in (you may have to ask for credentials)
...