Table of Contents | ||
---|---|---|
|
Next "All-Hands" Meeting
Tuesday 25 August 2020 at 1700 CET / 1100 US EDT / 0800 US PDT
...
Active Meeting schedules are listed under each sub-project minute page: [VHAL] [Audio]
Agenda
- Next milestone readiness
- Vehicle HAL
- Audio HAL
- New projects opportunities
- AOB
Webex link
Dial by your location: find dial-in number here
All-hands meetings are not run regularly at the moment.
Please join the specific Audio-HAL and VHAL calls.
Progress reports will also be done at GENIVI All Member Meeting (May 4-7, 2021)
Project Charter
Info |
---|
For AASIG Vehicle HAL and Audio HAL next meeting schedule, see relevant minutes below |
...
AA SIG - Vehicle Data APIs / Vehicle HAL Meeting Minutes
AA SIG - Audio HAL Meeting Minutes
AA SIG "All-Hands" Meeting Minutes
AA SIG - Vehicle Data APIs /
...
VHAL Workshop - May 2021
please look at AA SIG - VHAL / Vehicle Data APIs - Meeting Minutes
AA SIG - Audio HAL Workshop - May 2021
...
please look at
AA SIG - Vehicle Data APIs / VHAL Workshop - May 2020
AA SIG - Audio HAL Workshop - May 2020
AA SIG - Vehicle HAL & Audio HAL F2F Meeting Minutes - February 2020
AA SIG - Vehicle HAL - Architectural Design Concepts - GENIVI Tech Summit - November 2019
Project Overview
Automotive OEMs are increasingly adopting Androidtm Automotive (embedded) as a solution for their IVI stack. This adoption has introduced a series of challenges around integrating the Android Automotive embedded solution into existing legacy software and into other systems present in the vehicle (security, vehicle data, etc.).
Through a GENIVI-hosted Android Automotive SIG project, OEMs, their suppliers, and the broader cockpit software ecosystem can discuss requirements, identify gaps and provide an aligned, community voice for discussion with the Google Android Automotive team.
AASIG Android Development Platform
The purpose of the "development platform" is not significantly different from any standard development people are used to (e.g. AOSP).
It only defines a well-defined version of Android for Automotive development that supports solutions developed in the SIG. A repository holds the scripts, configurations, and knowledge to make a common and repeatable build, including any modifications, new components, and also to integrate automotive-specific hardware settings, BSP files, etc.
More details here: Android development platform
Areas of Focus
The following list of topics
...
was adopted in the original project charter. Additional topics are likely to be added as the project proceeds:
Extensions required for Android in an automotive environment
Audio management
Lifecycle, diagnosis and health monitoring
Multi-display support
Cluster integration
Platform requirements
Security
Access to vehicle information
Non-OEM validated 3rd party applications downloaded to the vehicle
Responsibility for long-term maintenance
Defining boundaries where Tier 1s/OEMs must take primary responsibilities over Google Android Automotive team support
Keeping an automotive system updated to support new versions of Android
On software level (Treble)
On hardware level (“cartridge” concept)
.
Participating Organizations | ||
---|---|---|
BMW (Chris Brandt) | Renault Nissan Mitsubishi Alliance | Mobis |
Daimler/Mercedes-Benz R&D NA |
...
...
Harman (Sujal Shah) | Wind River |
Fiat Chrysler | Bosch |
...
Renesas | |
Siemens | Mitsubishi Electric |
...
Tieto | ||
Mobica | ADIT | EPAM |
Analog Devices | Inrix |
...
Point of Contact
...