Page History

...

• Participants: COVESA, GM, Forvia, BMW, FORD, Mavi, Elektrobit, Allianz, Paradox Cat, Cariad SE
  
  
• info discussion vehicle data on July, 17: 2025-07-17 AOSP Vehicle Data next steps meeting
  Teams link (or ask Sabine on slack), Thursday, July 24, 17:00-17:30 pm (CEST):
  

  Microsoft Teams Benötigen Sie Hilfe?

  Jetzt an der Besprechung teilnehmen

  Besprechungs-ID: 336 464 628 846 4

  Kennung: EH9Wy9ED
  
  

• COVESA AOSP blog
  
  
• AOSP App host. → how to get a timeline and contents (App Host only, Emulator as well?) from Google, Paul will reach out.
  additional question to Google after additional investigation: how can we include the CARMA-features (back button) and the compatibility mode to AOSP?
  

  https://developer.android.com/training/cars/platforms/automotive-os/compatibility-mode

  → draft mail to Google - set it up until/in next Monday.
  
  
• Droidcon planning → last year confirmation came about 2 weeks before.
  
  
• COVESA Fall All Member Meeting 2025
  October 22-23, 2025
  Ann Arbor, Michigan
• Fall AMM working sessions planning, proposal:
  • 20 min. community update. + 20 min. vehicle properties update + 20 min. topic update.
  • 2 hours: workshop evaluation of next topics → better might be to decide that before to have a proposal at AMM.
  • 2 hours: workshop vehicle properties.
  • 2 hours: workshop next topic no. 1 → details
  • 2 hours: workshop next topic no.2 → details
    
    
• Entertainment/CARMA discussion next steps - COVESA back button?
  • TOPICS:
    • in GAS / CARMA, there is a back button (overlay).

    • There are standardized features from smart TV that Content Providers would need, like Geo-Blocking,

    • DRM,

    • a back button & pause content instead of killing the app

    • a voice assistant,

    • seamless services and

    • simple registration.

  • Step 1: how is it done at GAS at the moment? part of the template host? how does the user perceive it? how is it implemented?
  • Step 2: show how it could be done in the emulator. "back button testing suite".
  • Step 3: find out which OEMs would support it.
  • Step 4: follow up to find out detailed possible standardized solutions.
  • see 

    https://wiki.covesa.global/display/WIK4/COVESA+AOSP+Entertainment+Minutes?preview=/103088310/133169278/2503-COVESA%20Entertainment-%20Meeting%20(06.03.2025).pdf

  • 
    

    CARMA maybe just a library or just a set of requirements? no requirement on the app side for apps in the right category.
    
    

  • https://developer.android.com/training/cars/platforms/automotive-os/compatibility-mode → 
    find out the concrete questions on that to Google, see above.
    
    

  • on August, 7 entertainment meeting → ask Tomek & collegues. or if they want to come to next monday meeting. Richard reaching out.
    
    
• see below potential next topics. → every week one topic.

...