Please enter your thoughts and ideas as to what problems or opportunities the AA-SIG might pursue next. We will discuss them in our April 27 - Android Opportunities and Problems session.
| Topic | Comments | Entered by | Date |
|---|---|---|---|
| Vehicle Properties is very limited. There is no standard way outside Vehicle Properties for a developer to obtain vehicle data on Android. | VSS related. VHAL wider set of information. Permissions. Everyone | Paul Boyes | April 18, 2022 |
| Share non-differentiating, non-competitive content outside of Google App Store | Paul Boyes | Aprili 18, 2022 | |
| Multi-display and multi-user: currently, you can have multiple driver users, with one active driver at a time. There is some code (since Android 10) that hints at a way to support passenger users and be able to assign a passenger to a display, e.g. left hand rear seat. It would be great if we had a working example showing how this is meant to work | More RSE from Google. Cinemo has proprietary solution. | Chris Simmonds | April 19, 2022 |
| Where Vehicle Properties are lacking in functionality, can we suggest extensions (Vendor Properties) that would fill the gaps? | Chris Simmonds | April 19, 2022 | |
| How to improve sharing of roadmap with customers: e.g. Multi-display, multi-user,... | Need a good forum where automotive community can interact with Android/Google. Perhaps forum through COVESA Google to share clearer roadmap Desire for Android to work closely with the complete community. Regulation and standards. Work with Google to share history from Automotive. Bluetooth for example Perhaps if we able to show enough volume/use/interaction through COVESA - Google may open to regular conversation | ||
| Bootcamp - How do you get an invite? NDA. 2020 videos online. | Perhaps partner engineering interaction | ||
| How do we engage with the AOSP Car/AAOS community? Very little information on how to build with AOSP? All B2B? Why so little effort into developer relations? | With Linux huge community to interact with? Much more open. No secret to roadmap? AAOS has nothing. | ||
| Google puts minimum amount of effort into AOSP And AAOS. | |||
| Summary: is there an appetite in COVESA to create a forum for sharing information about AAOS, and maybe also to create a cross party interface with the AAOS team in Google? | Perhaps | Chris Simmonds | April 19, 2022 |
| Sharing vehicle data with Google and other parties: what are the risks and opportunities? Should there be sharing at the level of Vehicle Properties? | Chris Simmonds | April 19, 2022 | |
What data points/metrics to OEMs and others want from vehicles? | Jeff Reid | ||
What different Telemetry will be needed from EVs vs. ICE vehicles? | Jeff Reid | ||
Thoughts on AAOS going beyond the IVI space to other ECUs in the vehicle? | Automotive SPICE level 2 - how will it be handled in the future? Meeting ISO 21434. As Android is only IVI some oems are saying no need, but for Tier1 may be responsible. Code that is unsafe? | Jeff Red | |
| Permissions for properties are implemented differently per oem. How to standardize | Have OEMs coalesce/discuss with google. Perhaps set regular sessions. Get on Google and OEM RADAR. | ||
| Github repo that captures documentation, instruction, code, tools, etc.. for building Google | |||
| Amazon with Stellantis - COVESA may want to get involved. FireOS - Amazon Smart Vehicles | |||