...

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

...

24 (tbc)

• Participants:
• learnings from last week on infrastructure (Paul, Viktor) 
• 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?).
• tbc: first feedback from José, appning on documenting the gap between Automotive App Host GAS vs. AOSP

...

• tbd: emulator requirements revisited

Meeting notes 2025-02-17

...

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

...

• update onwhite paper as project charter; Initial draft :- please give your feedback!

View file
name 2305_COVESA_Automotive_AOSP_Emulator_Draft.docx height 250

 

• first steps
taken
• update on infrastructure possibilities from COVESA
• emulator images revisited
• AMM plans to offer emulators in working sessions ?
• anything else ?
• 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.
  Structure rest of topics in Meeting notes 2025-02-03

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.

...