Versions Compared

Old Version 279

changes.mady.by.user Sabine Hofschen

Saved on

compared with

New Version Current

changes.mady.by.user Sabine Hofschen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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-

...

08-

...

04

  • Participants:
  • Droidcon submission for COVESA AOSP Group:
    Image Removed
    Speakers: Sabine Hofschen, BMW. Gabriel Gautron, Forvia. Chris Simmonds.
  • COVESA Fall 2025 AMM planning (Ann Arbor, MI event on 22-23 October.):
  • AOSP Host update and discussion on how to proceed.
  • Image Added
    Image Added


Agenda 2025-07-28

  • Participants:
  • Entertainment App Back button
  • Info on question to Google on AOSP App Host, AOSP Emulator and CARMA.
  • Feedback vehicle data meeting Thursday, July 24 and Technical Steering Team on July 28:
    2025-07-24 AOSP Vehicle Data next steps meeting
  • next topic from backlog. (or just CARMA revisited, if needed).

Minutes 2025-07-21

  • 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?
  • see below potential next topics. → every week one topic.

Minutes 2025-07-14

  • Participants: COVESA, GM, Appning by Forvia, Ford, BMW, Paradox Cat, Allianz
  • Fall AMM planning
    • 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.
  • 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) (Jan). → for that, a COVESA SDK would be needed.
    • → follow-ups together with ParadoxCat and Elektrobit.
  • not discussed:
    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:
    Image Added
    Speakers: Sabine Hofschen, BMW. Gabriel Gautron, Forvia. Chris Simmonds.
  • COVESA Fall 2025 AMM planning (Ann Arbor, MI event on 22-23 October.):
  • 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
    AOSP Next topics - discussion
      • .

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. 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 (smile) 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..

...