...

Open and Royalty-Free
Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the COVESA Intellectual Property policy. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.

Meeting Notes 2025

Agenda 2025-07-14

• Participants:
• Fall AMM planning
• Ideas for a COVESA AOSP blog
• AOSP Host discussion.
• Vehicle data next steps discussion.
• How to find the next big topic for us, candidates (from AMM Berlin presentation):
  Image Added
  
  

Minutes 2025-07-07

• Participants: COVESA, GM, BMW, RemotiveLabs, ParadoxCat, Allianz

• Droidcon submission for COVESA AOSP Group:
  
  Speakers: Sabine Hofschen, BMW. Gabriel Gautron, Forvia. Chris Simmonds.
• COVESA Fall 2025 AMM planning (Ann Arbor, MI event on 22-23 October.):
  • COVESA Fall 2025 AMM Call for Participation → deadline end of July.
  • Discussion on how to organize Fall 2025 AMM for AOSP Group.
• AOSP Host update and discussion on how to proceed.AOSP Next topics - discussion:
  
  • Google released an alpha for the CAL: 1.8.0-alpha02
  • Status is that Google announced it will update the AOSP App Host up to CAL 1.8
  • Discussion on how to proceed:
    • Package one of the project proposal which is meant to integrate the App Host in the COVESA emulator will be needed anyhow.
    • Question is which map providers will be needed → does it make sense to find out which?
    • COVESA & AOSP Co-Chairs to address Google again on timeline and contents (is there e.g. an update planned on the AOSP Emulator as well?)
• COVESA SDK discussion
  • COVESA SDK only makes sense for features that need the SDK.
  • if we are close enough to Google, we might not need it.
  • For Push Notifications, it is enough to give the link to Unified Push.
  • Usage of Ambient Light → does it work out of the box? Vehicle property enabler still missing?
  • which feature would be needed → revisit topic survey.
  • Vehicle Data might make sense.
• Vehicle Data discussion
  • Feed the emulator thoughts:
    • simple concepts like increase/decrease speed over time in a standard way,
      user friendly way to set and test vehicle data.
    • better tooling helps to save dev time.
    • use VHAL setting API
    • use vss to vhal mapping.

    • Generate fake data for simulation.

    • Python code for adb commands.

    • see Bosch offering: digital.auto/use-cases which is based on vss, open source playground.

      
      

    • see remotive Labs offering with data.

Minutes 2025-06-30

• Participants: COVESA, Forvia, Appning by Forvia, BMW, Paradox Cat, Remotive Labs, FORD, Allianz
• Droidcon - our COVESA AOSP submission - status:

  Format: Lightning Talk (20 min) Speaker:
  one of the Co-Chairs of COVESA AOSP Group (Sabine Hofschen, Gabriel Gautron, José Freitas, Richard Fernandes)

  Track:  Android Automotive

  1. 1. Title: It's time to develop apps for Android cars: getting started with COVESA.
        
     2. Define (3 to 5) key takeaways and learning points:
        1. Android Automotive market overview.
        2. Android Automotive key challenges for developers - how do apps get into the car (→ note: including simply adopting apps from projection modes, dev once - deliver anywhere, also in non-GAS OEMs)
        3. Introduction to COVESA Automotive AOSP, its advantages and program. 
        4. Unified Push is getting a reality – Demo on how it works.
        5. Call for Participation: bring your ideas to COVESA, we will empower you.
• Droidcon - what else has been submitted - ParadoxCat, see last week.
  TechTalk, potentially + Workshop from appning.
  
  
• BBC was there in our AOSP Entertainment stream last thursday  26.06.2025 Monthly
  Key Takeaways: 
  • Different car makers present a challenge.
  • Interaction models in the car are different to mobile devices - no customer tolerance for friction.
    
  • UX in the car has to be crisp, tight, responsive and fluid as well as introduction and onboarding, login experience is crucial.
  • great apps + great store does not mean the job is done:
    apps need prominent visibility, as customers will not be looking for them in a car.
  • attribution - people have to know they are listening to BBC → logo.
  • today: pure radio still dominant. coming world: mobile devices, everybody brings what they want to listen. more personalisation according to occupancy in the car, e.g..

...