We use cookies on this site to enhance your user experience. By using this site, you are giving your consent for us to set cookies.


Contents:

please see also:

General Information

Welcome to the COVESA Automotive AOSP App Framework Standardization Expert Group Meeting!

Weekly Meeting: Monday, 5-6pm CEST (Zoom Link) (Subscribe to Community Calendar to stay up to date)

Slack: https://covesacommunity.slack.com/archives/C05EB6A6J5R

GitHub: https://github.com/COVESA/aosp-app-framework-standardizatiion

Chairs:


Compliance statement:

Antitrust
Before we begin, we would like to make clear that COVESA is committed to compliance with the antitrust laws in all of its activities, and that it expects all participants to similarly comply with the antitrust laws.  We will not engage in--and members must refrain from--any discussion of, or understandings regarding competitively sensitive topics. If you have any doubts regarding whether a matter is appropriate for discussion, please consult with your antitrust counsel.

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-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):



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

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


  • next steps for potential next topics
  • onboarding for customers - discussion continued, if wanted.

Minutes 2025-06-23

  • Participants: COVESA, GM, BMW, Spotify, Paradox Cat, CARIAD SE, Remotive Labs, Allianz
  • Planning Droidcon, see call for papers https://sessionize.com/droidcon-berlin-2025/:
    • Paradox Cat is planning talks on Carchestra (appning App Challenge Winner), Covesa and more (Kotlin related).
    • The chairs & friends (welcome!) are preparing a talk.
    • Idea: Talk on how to get an app to the car. For all to understand. (appning? talk prepared by chairs & friends?)
  • Status App Host: Google plans an update on the AOSP Host API level 8 this year. Seems as if we need no project for that.
  • Invite Entertainment Meeting this Thursday, June 26 with BBC: 26.06.2025 Monthly
  • Discussion on potential next topics:
    • would another survey make sense?
    • general: how to solve the fragmentation problem we are facing.
    • multiscreen support e.g. can cause fragmentation in the long run.
    • onboarding for customers:
      • why: to get the activation rate higher, measure: as easy as CarPlay.
      • what: share best practises. (pre-install, trainings)
      • ideas: industry best practises, e.g. from LG and Samsung. what is best in class?
      • potential outcomes:
        • a white paper,
        • maybe even a standardized way of launching your first apps on a car,
        • walk-Through, car-setup wizard from AOSP, Google.
        • emulator contribution (showing out-of-box on emulator).

Minutes 2025-06-16

  • Participants: COVESA, GM, BMW, Spotify, Remotive Labs, FORD, Paradox Cat, Allianz.
  • Recap App Host → still waiting for feedback.  Aim is to offer 3rd partys to use the same Car App Library templates also for AOSP.
  • Google automotive bootcamp → videos open under NDA for all who are registered participants.
  • feedback AMM and learnings for next AMM
  • announcement next entertainment meeting on June, 26 with BBC: 26.06.2025 Monthly
  • AOSP data work stream -
    • how to move forward. → would need a core working group to work on the topic based on the presentations we had for the stream.
    • Google discussed extension of vehicle data in the bootcamp.
    • Paradox Cat provided a Kotlin wrapper for the dev workshop: https://github.com/Paradox-Cat-GmbH/KarPropertyManager
    • in the future, topic moved to this AOSP meeting, no extra thursday meetings for the time being.
    • Discussion - ideal would be if car properties would be as well in the Car App Library.

Cancelled Meeting 2025-06-09 (public holiday, e.g. Germany, Pentecost/Whitsun)

Agenda proposal 2025-06-02

Cancelled Meeting 2025-05-26 (public holiday)

Minutes 2025-05-19

  • Participants: COVESA, BMW, GM, Appning by FORVIA, CARIAD SE, FORD, Spotify, Elektrobit, Renesas, Paradox Cat
  • Recap COVESA AMM Berlin - thanks to all who contributed!
  • Recap COVESA Dev Workshop AMM Berlin
  • App Host revisited:
    • Project Proposal to the Board on April 09
      2025-04-09_COVESA-Board-AOSP-AppHost.pptx.pdf
    • Revisited at Board on Mai 12 → Board wants us to come back to them on who will be using it.
    • Status:

      Thanks to Paradox Cat, we could elaborate on the Projected Proposal to upgrade the AOSP App Host

      and to make it, step by step, to a real COVESA AOSP App Host.

      The COVESA Board has given the task to itself and to the AOSP Co-Chairs to come back

      to the board with an assurance that there are more than one OEM as well as app developers in the

      line to really use this COVESA AOSP App Host. Following this assurance, there can be a board decision

      to spend budget on the project.

      Given the fact that the adoption of the COVESA funded work on Push Notifications still is too slow,

      the best way forward is still being clarified between COVESA Board and Co-Chairs.

  • AOSP Vehicle Data next steps, next meeting.
  • next AOSP monday meeting on Monday, June 02.

Cancelled Meeting 2025-05-12 (on our way to COVESA AMM in Berlin).

COVESA All Member Meeting ~ May 14-15, 2025

Minutes 2025-05-04

  • Participants: COVESA, FORVIA, Appning by FORVIA, GM, BMW, Paradox Cat, Mavi, CARIAD SE, Elektrobit, Spotify, Allianz
  • App Host revisited
  • AMM and DevWorkshop AMM - Preparation topics

Minutes 2025-04-28

  • Participants: COVESA, BMW, Paradox Cat, Bosch, CARIAD SE, Remotive Labs, Allianz

  • AMM and DevWorkshop AMM - Preparation topics, AMM agenda revisited.

  • for information: Dev Workshop at AMM is a pure Dev Workshop + breakout meetings on AOSP in the afternoon:
    AMM 20250525 Automotive AOSP App Framework Expert Group Workshop Agenda

  • Info on last AOSP Data meeting: 2025-04-24 AOSP Data Meeting notes
    Prep     Draft presentation AOSP Data for AMM Berlin

  • messages from Chris Simmonds:
    • there are plans to have a https://aosp-devs.org/ BoF meeting at AMM:

      Title: 1. Android Platform Builders Birds of a Feather (BoF)

      Description:

      Although Android is pretty common in Automotive, there are surprisingly few opportunities for us developers to come together.
      This BoF is such an opportunity. If you are working with Android at the platform level, or even if you just find this interesting, please come along. 
      Bring with you your experiences, tips, tricks and grumbles about developing Android Automotive. As a starter, here are some of the topics we might discuss:

        * The AOSP community and community portals
        * Working with Google
        * Porting to new hardware
        * System apps vs 3rd party apps

        * Issues around Android security - both where there is too much and also too little

    • Maybe you could bring this us at the AOSP SiG this afternoon:
      Droidcon Berlin are planning an Automotive Summit this year, 24 to 26 September

      https://berlin.droidcon.com/android-automotive-2025/

      I guess it will be similar to last year, which in my opinion was a great success.

Cancelled 2025-04-21 (Easter Monday)

  • Public Holiday in many European countries.
  • Participants: easter bunnies and easter eggs.

Meeting notes 2025-04-14

  • Participants: COVESA, Forvia, GM, BMW, Ford, ParadoxCat, spotify, RemotiveLabs, freelancers, source.dev, Valtech Mobility, Allianz

  • Info on Project proposal App Host - outcome COVESA Board meeting, April 9 and COVESA TST, April 14 
    2025-04-09_COVESA-Board-AOSP-AppHost.pptx.pdf
    and draft requirements as input to tender in Meeting notes 2025-03-24 by Paradox Cat.
    • this discussion was only possible via the analysis by Paradox Cat, Thank you!!!
    • Board: overall positive → get back to Board on
      • which COVESA members would apply it
      • solid timeline and
      • ways to bring the timeline forward (do we have to start from scratch or are there contributions on which we could build).
      • solid numbers on what is needed
      • talk to Google.
    • TST: → check all legal aspects. → connect to Hyundai

  • Entertainment meeting, April 9: 
    • slides will be provided on COVESA AOSP Entertainment Minutes
    • presentation from Hayu, worlds only DTC reality SVOD service (Direct-to-consumer, Subscription Video on Demand). 
    • Discussion on challenges automotive:
      • Standardised features known from smart TV would be needed.
      • Geo-Blocking standardisation (content based on geo-position. download possibilites)
      • What are the bare minimum requirements? DRM levels one to three.
      • Back button. Google has introduced it via tablet app to the car. For GAS already planned to get available. Android 14.
      • Voice assistant: Not an own engine for voice, rely on mobile phone or vehicle.
      • Seemless – continue watching. Would be handled from the app perspective.
      • simple registration with one link (status quo for Hayu).
      • to be discussed: Android APK for test purposes.

  • Emulator news (smile) thanks, Victor! 
  • any further inputs on our workshop at AMM ?
    AMM 20250525 Automotive AOSP App Framework Expert Group Workshop Agenda

  • Data meetings on Thursday → next meeting to take place on April 24.

  • fyi: "Google will stop restricting competition in connection with Google Automotive Services and Google Maps Platform"
    https://www.bundeskartellamt.de/SharedDocs/Meldung/EN/Pressemitteilungen/2025/04_09_2025_GAS_GMP.html

Meeting notes 2025-04-07

Meeting notes 2025-03-31

  • Participants: COVESA, Forvia, Appning by Forvia, GM, FORD, Spotify, ParadoxCat, Elektrobit, RemotiveLabs, Allianz, BMW
  • AMM 20250525 Automotive AOSP App Framework Expert Group Workshop Agenda - thank you, Paul, discussion:
    • reorganize, focus on developer meeting → Florian, Sabine
    • developer onboarding together with Jose/Nuno. Car Lib vs. Media vs. Game.
    • trying some templated apps, walk-through different categories.
    • Data → overview.
    • ROOM CONNECTIVITY?
  • Input from Spotify - what would be needed from a app dev perspective:
    • Roadmap, Featureset that would be available for app devs, which Car App Library API etc. 
    • Consistency and emulator, not so many different versions & fragmentation
    • Personalisation for the passenger.

Meeting notes 2025-03-24

  • Participants: COVESA, Forvia, Appning by Forvia, GM, FORD, Bosch, ParadoxCat, Elektrobit, RemotiveLabs, Allianz, Valtech Mobility, BMW
  • AMM news from Paul:
    The registration form is up for the AOSP workshop in Berlin (on Thursday).  Please register.  Please let me know if you see problems, have questions, suggestions, etc…  https://forms.gle/EMLX4AtnEB27ffZ2A. FYI - Registration for the Workshop is separate from registration for the AMM.
  • Emulator workstream last week:
    • First emulator will be started by Paradox Cat, 
    • App Host discussion, aim: decision in board meeting April 9, next step: refinement by Paradox Cat.
  • Data workstream last week:

Meeting notes 2025-03-17

  • Participants: COVESA, Paradox Cat, Forvia, Appning by Forvia, Ford, GM, RemotiveLabs, Chris Simmonds, Allianz, BMW.
  • AMM news:
    • invite:
      Please register for the Spring All Member Meeting in Berlin. 
      The preliminary agenda has been posted with lots of interesting Tech and Business sessions. 
      Additional invite for workshop on Thursday coming soon.

    • info from Paul (slack):
      we have confirmation that  room has been secured for the entire day of May 15 for a workshop for the AOSP group. 
      Let’s make sure we invite those that we would like to join:  developers, content providers, OEMs, Tier 1s,…  Let’s add the topic to the Monday meeting.

  • Short first info on follow up hands on session from March 14. Details to follow
    with Quartett Mobile, Appning, Paradox Cat, BMW, Allianz, Valtech Mobility, Antonio:

    • Setup Test Distributor (Car, Testbench)

    • Integrate COVESA SDK
    • Implement & test some standard VHAL properties
    • Push Notifications first test
  • Work streams:

Meeting notes 2025-03-14 Dev session

Meeting notes 2025-03-10

Meeting notes 2025-03-03

  • Participants: Valtech Mobility, Appning by FORVIA, Ford, Forvia, BMW, Ford, GM, Elektrobit, Tietoevery, RemotiveLab, Paradox Cat
  • AMM agenda
    • Multiple proposals received for talks
    • Looking for live demos (push, emulator, ...)
  • Push notification
    • Pull request was merged link
    • Instructions in the readme, as well as sample app link
    • Live demo by Viktor Mukha @ Paradox Cat
  • Entertainment
    • HAYU (NBCUniversal’s reality TV streaming service)! invited thos Thursday March 6th 5PM-6pm CET ==> Join us!
    • Detail in COVESA's Slack link

Meeting notes 2025-02-24

  • Participants: Forvia, Allianz, 2net, RemotiveLabs, ParadoxCat, , GM, Gracenote, Appning by Forvia, Mavi, Valtech Mobility, Tietoevry, Paradox Cat, Bosch, Ford, Endava, BMW
  • Push notification
    • Marketing / blog post: need update
    • COVESA AOSP SDK
      • Pull request
        • Changes proposed by Appning were reviewed by Simon, that requested some changes
        • Will be reviewed this week by Appning,
      • Hosting:
        • Decision: Public, on Maven
      • Structure: one SDK / feature vs 1 SDK for all features
        • Decision: 1 SDK for all features in the short term (pro: BMW)
        • When adding more features, will be reconsidered (pro: Appning)
      • How to release
        • Decision: use Github action
        • Appning to create an issue to expose push notification as a jar
        • Owner: will ask Simon
        • Covesa SDK requirements:
      • Need input from Paul
      • Covesa SDK now mentioned on the aosp-dev.org website! => https://aosp-devs.org/code.html?mwg_rnd=8777906
  • Entertainment
    • Now a monthly meeting
    • Meetings notes need to be updated
    • Monthly meeting now
  • AMM: Presentation Appning x app challenge?
  • Start a discussion on requirements for a COVESA SDK in general?
    (e.g. on https://github.com/COVESA/covesa-aosp-sdk/discussions or on a subpage on this WIKI?)
    • ==> Need nput from Paul ?

Meeting notes 2025-02-17

  • Participants: GM, FORVIA, Appning by FORVIA, BMW, Bosch, FORD, Elektrobit, Endava, Paradox Cat.
  • AMM coming in May:
    • Update what we have done.
    • Feedback from different members.
    • Very open to inputs: business track. If executives want to talk, welcome.
    • Projects / next steps 40min-1h
    • Technical sessions (different work streams). & call for participants – welcome, mostly on 14th of May.
  • Push Notifications revisited
    • Some presentations about Push Notifications
      • PDF from workshop in April 2024 link 
    • Links for COVESA Push Notifications
      • The solution is based on Unified Push link
      • Distributor app built for COVESA: Sunup link
      • Covesa AOSP SDK link
        • Pull request for integrating push notifications link
      • The solution can use the Mozilla Autopush RS Server  link
      • Sample app for implementation example: developers can use this sample page link

    • changes have been proposed. PR fixes an issue https://github.com/p1gp1g/covesa-aosp-sdk/pulls
      appning is further investigating.

    • Decoupling push notifications from ambient light is possible – Each module or package can be addressed separately.
    • Discussion on COVESA SDK (forked from, discussions) –
      please leave comments on https://github.com/COVESA/covesa-aosp-sdk/discussions
    • Description best in readme on github, link out from there. Website of devs a good place as well.
    • Target date for merge request "asap".

Meeting notes 2025-02-10

Meeting notes 2025-02-03

Meeting notes 2025-01-27

Meeting notes 2025-01-13

  • Participants: BMW, FORVIA, General Motors, Elektrobit, Geotab, Mavi.io, Paradox Cat, RemotiveLabs, Tietoevry, UnifiedPush 
  • COVESA CES event was successful
  • Emulator
    • Paul reached out to Google and will debrief in next meeting
    • Richard will setup a meeting for next Monday 5:30PM CET
  • Data workstream
    • Paul will present the initiative in the VSS meeting to get involvement from OEMs
    • Suggestion to have someone present what was already done: 

      link link link

    • Presentation about VSS by BMW 

      link

  • Push notifications
    • Sunup
      • Delivered: new distributor => Sunup, 

        codeberg, izzysoft,

        and proposed on frdoid
      • Mentioned on the UP website

         link

      • Added support for Reddis for autopush, modif upstream not in fork
      • Added support for urgency
        • Server
    • Docker compose available to easily deploy the server
        • Call for testers !
    • Paradoxcat collaborated end of 2024
  • Communication:
    • Need to make an article / blog post about it
    • Simon will reference "Contributed by Covesa" on his website
  • Agenda for next meeting
    • Testing apps
    • Organize AMM live meeting (demo, …)
    • How to reach out to app developers and invite them to our activities
      • Such as uploading to stores

Charter 



  • No labels

Privacy Policy | Cookie Policy