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

DRAFT minutes (Sabine working on it.....) 2025-02-03 (Proposal, tbc)

• Participants:
• Topics from last week revisited - structure the topics (tasks / timing / roadmap).
• tools are limiting factor at the moment.
• Sabine: Just a proposal for discussion how we could structure it:

  
  

  Category	Task	Description	contributors	until when
  Specification	Requirements	gather and document requirements on this WIKI → José and analyse tasks regarding automotive host
  Ressources	build & host critical path.	where?  Crave for building → Viktor? → Viktor to provide requirements, done monthly? on every pull request? CI needed. COVESA → hosting? → gerrit instance on virtual machine. Viktor to specify. How do we collaborate → go to every repo we are hosting - bundling automatically not easy on Github. → for bundling gerrit better. second option: manually. make the emulator available in the SDK.
  Component	Push Notifications	be able to use Push Notifications in the emulator → part of the requirements. pre-installed apk.
  Component	Vehicle Data access	Vision: Be able to use vehicle data in the emulator & description on how to do it (e.g. via adb shell commands). Authentication system service. needed: → simulating the data and data streams. → get back to the data stream working group. google has some (python) scripts to feed the emulator. see VISS tooling →  Swen would address it in the data group VSS/VISS. → managing access & permissions.
  Component	Open Source map	emulator extension to render maps in open source map
  Component	SDK	emulator extensions for all (future) SDK parts
  ...	Automotive host decision	as input to emulator.

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:
    • https://crave.io/ allows for open source instances
    • Gerrit instance?
  • next Steps:
    • check with Crave
    • document what is needed (→ new space with this confluence)
    • meet again next week.