Android Automotive bekommt großes Update auf Version 12 spendiert

Renault Android Automotive Header

Android Automotive ist die native Version von Android für Autos, die unter anderem Volvo und Polestar derzeit nutzen. In Zukunft werden da aber noch deutlich mehr Marken dabei sein und selbst die Volkswagen AG greift teilweise darauf zurück.

Android Automotive 12 Update

Das erste Auto mit Android Automotive war der Polestar 2, der mit Version 10 auf den Markt kam, die auf Android 10 basierte. Android 11 hat man übersprungen, mit Android 12 werden wir dann ab 2022 aber auch Android Automotive 12 sehen.

Google hat bisher noch nicht verraten, ab wann das Update auf Version 12 verteilt wird, aber das dürfte dann auch eher die Entscheidung von Polestar und Co. sein.

Android Automotive Version 12

Android Automotive 12 mit zwei Spalten

Was ist neu? Die Benutzeroberfläche wurde optimiert, es gibt eine native App für Nachrichten, einen neuen Launcher, zwei Reihen bei breiten Displays und viele kleine Optimierungen, die sich mit Dingen wie Bluetooth und mehr beschäftigen.

Die Autohersteller haben viele Freiheiten bei Android Automotive, wir haben hier zwar ein paar Screenshots aus dem Emulator, aber die Benutzeroberfläche von Polestar und Co. wird anders aussehen. Nach den Screenshots haben wir auch noch den kompletten Changelog für euch, der sich aber eher an Entwickler richtet.

Ich bin mal gespannt, wie die Update-Politik bei Android Automotive aussehen wird und wie schnell und häufig die Autohersteller eine neue Version verteilen werden.

Android Automotive 12 Screenshots

Android Automotive Screen2 Android Automotive Screen1 Android Automotive Screen3 Android Automotive Screen4 Android Automotive Screen5 Android Automotive Screen6

Android Automotive 12 Changelog

Platform: System power, performance, and cluster

  • Understanding 64-Bit Builds. Learn about the 64-bit only Android system.
  • Power Policy. Provide an API (native service) to define power states and policy. This feature enables OEMs to customize ON states.
  • Cluster stack II. Improve the cluster stack to reduce OEM side work.

System user interface and improvements to core apps

  • Rotary Controller. Front-end AAOS experiences, including system apps such as Dialer, Media, and Settings can now be fully navigated with a Rotary controller that supports four-way nudge, clockwise and counter clockwise rotation, and selection.
  • Additional IME integration is now also available given an OEM-provided, Rotary-focused IME.
  • Short Message Service (SMS) v2. A reference SMS 2 app with message history and a UI to a compose a message is provided.
  • Heads-Up Notifications (HUN). By default, HUNs are ordered by time. However, since some HUNs are more important or urgent than others (for example, a car emergency is more important than a message), this feature enables HUNs to be prioritized.
  • User interface (UI):
    • Replace the AOSP reference launcher with launcher 2.
    • System UI proofing.
  • Privacy:
    • Transparency for the user on the microphone with a microphone indicator.
    • Apps visible more than 90 days are automatically designating as hibernating.
    • Enable microphone toggle notifications when an app attempts to access the microphone. Upon interacting with the indicator, a Recently Used dialog shows the most recent app that accessed the microphone.
  • Settings app redesign. Improve usability and scalability with a configurable two-column structure for larger and wider screens. Incorporated a revamped information architecture to ensure key settings can be easily accessed and discovered.
  • Toasts API. Only system apps can access the Toasts API.

User management

  • Remote user management. New APIs are available to create and delete Android users for remote management use cases. These APIs are integrated with the AAOS UX restriction engine, such that if these actions are remotely executed (for example, on the web or in a phone app), the drive-state of the vehicle is respected. For remote user locking, we integrate the existing [DevicePolicyManager APIs](

    developer.android.com

    ){external} with the UX restriction engine.

Bluetooth

  • Improved Bluetooth reconnection performance. Automatically connect to devices more often, under the right circumstances. For example, initiate reconnection on a VHAL event, such as driver-in-seat.
  • Messaging database. Added support for using a messaging database through MAP to provide more flexibility to messaging apps that rely on Bluetooth.

Connectivity

  • Per-Application Network Selection (PANS). Allow for the creation and enforcement of a dynamic network policy that determines which applications can use OEM_PAID networks.
  • Dual STA. Concurrently enable the In-Vehicle Infotainment (IVI) system to connect to a restricted Wi-Fi network for OEM purposes as well as with another connection to a Wi-Fi network.

Audio

  • Audio ducking signal. Provides the Hardware Abstraction Layer (HAL) with audio focus state and information on what output devices to duck.
  • Volume improvements. Allow for the finer control of volume, including providing API to get active volume groups.
  • Mute per volume group. Allow per volume group muting and enhance HAL and UI communication as to the mute states.

Camera

  • CarEvsManager. Enable OEMs to implement an Android Activity that shows the preview from automotive camera services.
  • Externded View System (EVS) statistics. : Collect EVS service usages and performance statistics.
  • Surround View GPU acceleration/ Improved performance for Surround View stitching by making the best of the GPU.
  • Surround View online calibration. Aligns Surround View images on-the-fly to accommodate shifts in camera positions over time, retaining the stitched image quality for the life span of the car.

Security

  • Vehicle Bound Encryption. Android storage encryption can now be configured to store some key encryption parameters on an external ECU. This prevents the harvesting of data by removing the head unit from the car (which can occur due to theft or demolition).
  • Secure Developer Options. Android developer options and ADB can be remotely enabled exclusively by an OEM. Reference implementation provides crypto token access mechanisms and remote web service.

Sensors

  • Automatic Time Detection Read time from Global Navigation Satellite Systems (GNSS) when other sources are unavailable. This way, a car has a time source when offline.
  • Enable sensor replay and playback on an emulator.

Telemetry

  • Edge-based analytics capability. Enables the ability to perform more edge-based metrics processing on Android Automotive devices. Android infotainment and vehicle property metrics can be configured in scripts written in the [Lua](

    www.lua.org/

    ){external} language and processed on-device and sent to the back-end determined by an OEM.

Vehicle integration

  • Temperature control. New attributes, including HVAC_TEMPERATURE_VALUE_SUGGESTION, enable HVAC temperature rounding and units.
  • Vehicle Property Updates. Added APIs to streamline the development flow by providing a way to get and set multiple vehicle properties at one time.
  • Freeze the vehicle HAL interface.

Display and input

  • OEM custom input. Add or customize different inputs for OEM cars.

Settings app update

  • UI and information architecture update. Updated the Settings app to version 2.

Additional updates

  • Deprecated PERMISSION_CONTROL_CAR_OCCUPANT_AWARENESS_SYSTEM.
  • Setup Wizard is now listed in Google Play.

Audi A4 e-tron soll 2024 kommen

Audi A6 Etron Konzept Front

Audi gehört zu den Autoherstellern, die zahlreiche Elektroautos in den letzten Monaten auf den Markt gebracht haben. Doch schaut man sich das Portfolio mal genau an, dann gibt es da […]7. Dezember 2021 JETZT LESEN →


Fehler meldenKommentare

   

Deine E-Mail bleibt vertraulich. Durch Kommentieren stimmst du der Datenschutzerklärung zu.

Du bist hier:
mobiFlip.de / Mobilität / ...