Versions Compared

Key

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

...

  • tbc: first feedback from José, appning on documenting the gap between Automotive App Host GAS vs. AOSP

...

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
name2305_COVESA_Automotive_AOSP_Emulator_Draft.docx
height250
 

  • first steps
  • takenupdate on
  • possible after infrastructure possibilities from COVESA
  • emulator images revisited
  • AMM plans to offer emulators in working sessions ?
  • anything else ?
  • have been clarified.
  • APP Host Experience (Paradox Cat, Appning):
    • App Host is open source lib with regular updates.
    • one update which would be needed for AOSP is the rendering.
      • Appning is using open street maps. 
      • WIP
    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.

...