/
COVESA AOSP Emulator Weekly

Get Involved

◎ COVESA Community Calendar
◎ COVESA Getting Started
◎ Understanding and Engaging in COVESA
◎ Project Launch Process

Groups and Projects

Groups and Projects continued...

◎ Vehicle Signal Specification (VSS)
◎ AOSP App Framework
◎ Commercial Vehicle and Fleet Group
◎ Generative AI Group
◎ Central Data Service Playground

◎ Vehicle Data Model
◎ Cyberecurity Group
◎ In-Vehicle Payments Group
◎ Connected Safety
◎ All Groups and Projects

Resources

◎ COVESA Events
◎ Industry Events 2025
◎ Antitrust and Open Statement
◎ Member Visibility

Join/Sign Up

◎ Join COVESA
◎ Sign Up for Member Newsletter
◎ Request Wiki Account
◎ Request Access to Slack

COVESA AOSP Emulator Weekly

Jul 07, 2025

Contents:

AOSP home page:

Automotive AOSP App Framework Standardization Expert Group

please see also (sub-pages):

General Information

Welcome to the COVESA Automotive AOSP Emulator Workstream Meeting!

Weekly Meeting: Monday, 5:30-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

Leads:

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

No further separate meetings.

Cancelled 2025-04-21 (Easter Monday)

  • Public Holiday in many European countries.

Meeting notes 2025-04-14

Meeting notes 2025-04-07

Meeting notes 2025-03-31

  • Participants: COVESA, Forvia, Appning by Forvia, GM, FORD, Spotify, ParadoxCat, Elektrobit, RemotiveLabs, Allianz, BMW

  • Update activities Paradox Cat for AOSP emulator:

    • ARM, X86 Android 12, with boot animation

      instrument cluster – with some placeholder in it (instead of maps?)

    •  

      issues with Android Studio Meerkat, you see the screen only with a workaround

Meeting notes 2025-03-24

  • Participants: COVESA, Forvia, Appning by Forvia, GM, FORD, Bosch, ParadoxCat, Elektrobit, RemotiveLabs, Allianz, Valtech Mobility, BMW

  • Update activities Paradox Cat for AOSP emulator

    • The repositories are updated, boot animation is now implemented, first prebuilt version is to be distributed via S3 by Paradox Cat.

    • GitHub actions are to be set up by Paradox Cat, testing with AWS needs to be done to decide on operation mode which would not incur too much cost.

  • Update planning App Host extension → Prep Board meeting on April 9.

    • First draft from Paradox Cat: 

Meeting notes 2025-03-17

Meeting notes 2025-03-10

  • Participants: COVESA, Paradox Cat, Antonio Roa-Valverde, Chris Simmonds, Remotive Labs, Bosch, FORD, GM, Endava, Valtech Mobility, Allianz, BMW.

  • Proposal in regards to Automotive Template Host from Paradox Cat:
     

Meeting Recording: https://us06web.zoom.us/rec/share/G90n0CFEzUPdPvLOeWHFkauMTCx3qOHBQCKEKzCuSDSk9Zixa8hqRH0j8PMRpiPs.LYKHKny0hCRuY_DZ

invite Chris: The aosp-devs automotive chanel: go to the main landing page: https://aosp-devs.org/ and follow the link at the top under "Come chat with us"

Meeting notes 2025-03-03

  • Participants: Valtech Mobility, Appning by FORVIA, Ford, Forvia, BMW, GM, Elektrobit, Tietoevery, RemotiveLab, Paradox Cat

  • Discussed plan for setup (Paradox Cat)

  • Templated host

    • Paradox Cat will share their vision and propose something in the next meeting

  • Boot animation

    • Use a static image from marketing resources link 

Meeting notes 2025-02-24

  • Participants: Forvia, Allianz, 2net, RemotiveLabs, ParadoxCat, Elektrobeat, GM, Gracenote, Appning by Forvia, Mavi, Valtech Mobility, Tietoevry, Paradox Cat, Bosch, Ford, Endava, BMW

    • Hosting

      • Approximate breakdown of monthly costs for setting up the Android Automotive OS emulator project on AWS, from Nick, COVESA'S IT manager.

      • Being reviewed by Paradox Cat (Viktor)

        • EC2 Instance (r5.large):
          Approximately $0.126 per hour; for 24/7 operation, this equates to roughly $91 per month.

        • EBS Storage (500 GB on gp3):
          $0.08 per GB per month, totaling $40 for 500 GB.

        • S3 Storage for Artifacts:
          Assuming 100 GB usage, at $0.023 per GB per month, this would cost about $2.30.

        • Data Transfer Costs:
          AWS provides 1 GB per month of free data transfer out to the internet. Beyond that, prices are approximately $0.09 per GB. The cost will depend on your actual usage.

        • Additional Costs:
          Other potential costs include network usage, snapshots, and any specific AWS services like CloudWatch for monitoring, which starts at $0.30 per metric.

    • Boot animation

      • Richard to follow up with Paul to see what's available

      • Static is ok to start with

    • Presentation from Nuno (Appning) about gaps between the AOSP Host & GAS

      • Need to get feedback from Google on dependency on GAS from the Android for Car library

    • Template Host:

    • Not done: gather feedback from participants on white paper, see Meeting notes 2025-02-17
      and decide on where to give feedback (google docs, co-working document?)

Meeting notes 2025-02-17

  • Participants: GM, FORVIA, Appning by FORVIA, BMW, Bosch, FORD, CARIAD, Elektrobit, Endava, Paradox Cat.

  • White paper as project charter; Initial draft - please give your feedback!

  • first steps possible after infrastructure has been clarified (repo in github, github actions, build host, artifacts and binary storage) → news expected next week.

  • Automotive App Host gaps → analysis probably next week, see change log https://developer.android.com/jetpack/androidx/releases/car-app

  • App Host Experience (Paradox Cat, Appning):

    • App Host is open source lib with regular updates.

    • updates include

      • e.g. more number of buttons now (4 instead of 2)

      • some new types of templates, e.g. tab view with each tab having a grid.

    • one update which would be needed also for AOSP is the map rendering possibility:.

      • status was formerly: navi maps render on their own, POI apps use maps rendered by the App Host.

      • if we update to V1.7, apps would be able to render on their own.

      • Appning is using open street maps OSM.

      • ability to run different maps depends on availability of keys, questionable if this would really plug & play.

      • question is if OSM or even different maps could be added to AOSP.

      • maybe a further layer of abstraction would be possible: OSM plus lib which renders OSM.

      • seems as if App Host can be updated and built separate from the platform (as a system app).
        From OEM perspective this feature then would need to be supported.

Meeting notes 2025-02-10

  • Participants: COVESA, csimmonds, GM, RemotiveLabs, BMW, FORVIA, Ford, Appning by FORVIA, Endava, Valtech Mobility, Allianz, Tietoevry, Paradox Cat, Renesas, mavi.io

  • Review COVESA AOSP Emulator Requirements - thanks to Viktor and José!

  • Discussions:

    • add white paper from José as project charter.

    • smaller group to take this forward as proposed in Requirements

    • Viktor could start to build repos, then switch to COVESA

    • first priority: repos, infrastructure. Paul will be talking to Steve and connecting to Viktor regarding machines that are needed.

    • automate the first build, then build on top of it, e.g. adding push notifications

    • Side track not immediately to be solved: automotive host.

      • Option 1: bridge the gap GAS and AOSP automotive host on COVESA

      • Option 2: limit API level which can be used. Up to level 4

      • Option 3: wait for Google.

      • First step: document the gap. José offers first feedback on that within 2 weeks.

    • different emulator images that will be needed:

      • Android version 10-14, two architectures ARM/X86.
        proposal: Start with Android 12 && ARM/X86 ?

      • might also need Android 9.

      • might also need emulators with/without additional services

      • be careful, too many flavours will end us up in too much space/compute power that is needed.

Meeting notes 2025-02-03

  • Participants: BMW, COVESA, Bosch, RemotiveLabs, FORVIA, FORD, Appning by FORVIA, Tietoevry, General Motors, Elektrobit, Endava, Allianz, Paradox Cat

  • Topics:

     

 

Meeting notes 2025-01-27

  • Participants: BMW, FORVIA/Appning by FORVIA, General Motors, FORD, COVESA, UnifiedPush, RemotiveLabs, Elektrobit, Tietoevry, Paradox Cat

  • Emulator Kickoff - requirements (José Freitas, appning by FORVIA):

    • Push notifications

    • SDK

    • Automotive host:

      • explanation: for templated apps that can be used while driving, there is a Car app library for e.g. Point of Interest apps. the automotive host on IVI renders the apps.

      • challenge at the moment: mismatch AOSP vs. GAS release.
        for the gap, see release notes: https://developer.android.com/jetpack/androidx/releases/car-app

      • solutions to solve the challenge could be

        • update from Google

        • restrain API level for developers

        • build add-ons on top of AOSP host.

    • Add open source map like open street map, as Automotive host doesn't render maps

    • Data workstream requirements like authentication, system service.

    • From COVESA: building and hosting the images of the emulator,
      ideas:

    • next Steps:

      • check with Crave

      • document what is needed (→ new space with this confluence)

      • meet again next week.