Android Automotive SIG

AASIG - All Member Meeting Planning - April 2022 - Leipzig, Germany

AA-SIG Vehicle HAL subproject

Zoom link:  https://zoom.us/j/99373652562?pwd=Mnl3K1pxSUxXVFZma2xkL2tsb3ZDZz09
For time slot, please see the COVESA Common Meeting Schedule

All-hands is not run regularly at the moment.

Audio track has been completed/suspended, end of 2021.

Vehicle HAL call, a sub-project of the CVII, meets every week.

• please look at AA SIG - VHAL / Vehicle Data APIs - Meeting Minutes

• please look at AA SIG - Audio HAL - Meeting Minutes

Automotive OEMs are increasingly adopting Android^tm 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.

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

The following list of topics were 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 over project lifetime

• BMW (Chris Brandt
  
  

• Daimler/Mercedes-Benz R&D NA

• Fiat Chrysler

• Renault Nissan Mitsubuishi Alliance 

• Harman (Sujal Shah)

• Bosch 

• Mentor

• Mitsubishi Electric

• Mobis

• Wind River

• Renesas

• Tieto

• Mobica

• ADIT

• EPAM

• Analog Devices

• Inrix.

• Philippe Robin (GENIVI PMO)

• Gunnar Andersson (GENIVI Technical Lead)