AMM Porto, April 22 - Workshop planning

9:30-9:55

Community Update

Co-Chairs

Status Update by CoChairs.

Info on Workshops

10:00-11:00

Workshop

OEM VHAL introduction

Kickoff for AOSP VHAL Proofs-of Concept based on open source VHAL showcase

Jan Kubovy, BMW
and Co-Chairs

1. Live Emulator Presentation AOSP VHAL Showcase - getting familiar with the open source code.

2. OEM Use Case Ideation and Agreement on Required VHAL Signals
   --> get it started in the afternoon for all, who can contribute.

3. Next Steps & Contributions (dynamic values, follow‑up work)

OEM-VHAL session outline

11:00-11:45

Workshop

Entertainment

Chris Goebel

• Why the Android Automotive App Ecosystem Isn’t Taking Off – and What We Can Do About It

11:50-12:30

Workshop

Future working model of the AOSP group - future topics and participation

Co-Chairs

• Future Topics, like e.g. Geocoding, iMAP updates, App Host, in-app updates

• Group Charta Next

• Who would actively participate and contribute in the future?

14:00-17:30

Dev Workshop

Showroom AOSP table

OEM-VHAL PoCs (Jan)

tbd App Devs (José)

• OEM VHAL PoCs coding as decided in the morning.

• tbd: Prototyping with Car.

9:30-9:55

Community Update

Co-Chairs

Status Update

Info on Workshops

10:00-11:00

OEM VHAL introduction

Jan and Co-Chairs

• OEM-VHAL session outline:

1. Introduction & OEM Value Framing

2. AOSP VHAL Showcase (Jan):
   Understand VHAL show case based on basic data points, VSS client and websockets on emulator (links to be provided upfront) (presented by Jan).

3. OEM Use Case Ideation: get ideas for use cases based on the show case.

4. Agreement on Required VHAL Signals
   agreement on VHAL values needed for these ideas.

5. Next Steps & Contributions (dynamic values, follow‑up work)
   tbd: dynamic values to feed the emulator (JS, could someone else provide pre-work for this?).
   
   

11:00-11:45

Entertainment

Chris Goebel

• Why the Android Automotive App Ecosystem Isn’t Taking Off – and What We Can Do About It

11:50-12:30

AOSP Group Charta and Backlog

Co-Chairs

• agreed upon Backlog including topics like e.g. Geocoding, iMAP updates, App Host….

• agreed upon update of Group Charta and next steps

• one of the topics:
  In-app updates: provide a standard mechanism to allow app developers to check for the availability of newer versions of their app in the current OEM store and redirect the user to the store to update the app in case needed.
  
  Google Play on Android Automotive OS  |  Android for Cars  |  Android Developers

  "The following libraries are not supported by cars with Google built-in:

  • In-app reviews

  • In-app updates"

14:00-17:30

tbd???

Dev Workshop

TBD and where.

? Sabine, Jan

?

• tbd if done at all????

• first draft code for 2 PoCs agreed upon. tbd static values or dynamic values. to be shown on emulator (not in car).

• tbd: additional topic.