Page History

...

Agenda 2025-07-14

• Participants: COVESA, GM, Appning by Forvia, Ford, BMW, Paradox Cat, Allianz
• Fall AMM planning
  • Ideas for a COVESA AOSP blog
  • AOSP Host discussion.
  • • technical call for papers coming soon.
    • status update in the beginning, working sessions then.
    • to be discussed: hybrid meetings.
    • working session doesnt need to have a tech talk included.
    • ask Forvia who are having a close subsidiary, for support / discussion on what could be organized,
      in a vehicle?
    • demo what is already possible, show apps downloaded from the app store → to enable devs in the end:
      idea: COVESA data playground for data points we agree upon before. Use case specific overlays like for fleet.
      challenge: OEM offering of data points + see below Vehicle data.
  • Ideas for a COVESA AOSP blog
  • AOSP Host discussion.
  • Vehicle data next steps discussion.
    • looking for an open - source solution, e.g. VSS/VHAL mapping.
    • as of today, only speed and a few others are available → devs cannot ideate on anything.
    • find the use cases on which to open up for devs.
    • idea: This would be a great opportunity to make vss available to apps directly, then we can define our own permissions.
    • idea: this group to do a joint specification on the data side which goes through list of properties, their specifics. then develop alongside this. 
    • work in progress (mapper, permission model)
    Vehicle data next steps discussion
    • .
  • How to find the next big topic for us, candidates (from AMM Berlin presentation):
    • 
      Image Modified
      
      

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

  ...