JOIN/SIGN UP
Already a Member? |
GET INVOLVED
Understanding and Engaging in COVESA Expert Groups & Projects |
COLLABORATIVE PROJECTS
HISTORICAL
SDV Telemetry Project |
We use cookies on this site to enhance your user experience. By using this site, you are giving your consent for us to set cookies. |
Active Meeting schedules are listed under each sub-project minute page: [VHAL] [Audio]
All-hands is not run regularly at the moment.
Please join the specific Audio-HAL and VHAL calls.
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.
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:
Participating Organizations