...
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 | |