RN00227

Android Automotive Release Notes

Rev. automotive-14.0.0_2.1.0 — Release notes
7 November 2024

Document information
Information Content
Keywords Android, i.MX, Automotive, automotive-14.0.0_2.1.0, RN00227
Abstract The i.MX Android automotive-14.0.0_2.1.0 release is an Android Automotive GA (RFP) release on
NXP's i.MX 8QuadXPlus/8QuadMax MEK board and platform and Alpha (EAR) release on NXP's
i.MX 95 EVK board and platform. The release is based on Android 14.
NXP Semiconductors
RN00227
Android Automotive Release Notes

1 Release Description
The i.MX Android automotive-14.0.0_2.1.0 release is an Android Automotive GA (RFP) release on NXP's i.MX
8QuadXPlus/8QuadMax MEK board and platform and also an Alpha (EAR) release on NXP's i.MX 95 EVK
board and platform. The release is based on Android 14. It supports the device type in-vehicle infotainment
defined in https://source.android.com/devices/automotive/.
i.MX Android automotive-14.0.0_2.1.0 release includes all necessary code, documents, and tools to assist
users in building and running Android Automotive on the i.MX 8QuadXPlus/8QuadMax MEK board and i.MX 95
EVK board from scratch. Pre-built images are also included for a quick trial on the following platforms:
• i.MX 8QuadXPlus/8QuadMax MEK Board and Platform
• i.MX 95 EVK Board and Platform
This release includes all portings and enhancements based on the Android open source code.
Most of the deliveries in this release are provided in the source code except for some proprietary modules/
libraries from third parties.

2 Supported Hardware SoC/Boards

The supported hardware system-on-chip (SoCs)/boards are listed as follows:
• i.MX 8QuadMax (Silicon Revision B0) MEK Board and Platform
• i.MX 8QuadXPlus (Silicon Revision B0, C0) MEK Board and Platform
• i.MX 95 (Silicon 19x19 Revision A1) EVK Board and Platform

3 Release Package Contents

The automotive-14.0.0_2.1.0 release package includes the following software and documents.

Table 1. Release package contents

i.MX Android proprietary source • imx-automotive-14.0.0_2.1.0.tar.gz: i.MX Android Automotive proprietary
code package source code package to enable Android Automotive on i.MX boards. For example,
Hardware Abstraction Layer implementation, and hardware codec acceleration.
Documents The following documents are included in android_automotive-14.0.0_2.1.0_
docs.zip:
• Android Automotive Release Notes (RN00227): A document that introduces key
updates and known issues in this release.
• Android Automotive User's Guide (UG10176): A document describing procedures for
configuring and building this release package.
• Android Automotive Quick Start Guide (UG10177): A document that explains how to
run Android Automotive on an i.MX board using prebuilt images.
• i.MX Android Extended Codec Release Notes (RN00202): A document that provides
the extended codec information.
• i.MX Android Security User's Guide (UG10158): A document that describes how to do
customization work on security features supported by i.MX Android software.
• i.MX Graphics User's Guide (UG10159): A document that describes graphics APIs,
Tools, Memory, and Application programming guidelines.
Prebuilt images You can test Android Automotive with a prebuilt image on the i.MX reference board
before building any code:
• automotive-14.0.0_2.1.0_image_8qmek_car.tar.gz:
Prebuilt-image for i.MX 8QuadXPlus/8QuadMax MEK board with the Exterior View
System (EVS) function enabled in the ARM Cortex-M4 CPU core during Android OS
RN00227 All information provided in this document is subject to legal disclaimers. © 2024 NXP B.V. All rights reserved.

Release notes Rev. automotive-14.0.0_2.1.0 — 7 November 2024 Document feedback

2 / 11
NXP Semiconductors
RN00227
Android Automotive Release Notes

Table 1. Release package contents...continued

boot process when the EVS function is switched to the Cortex-A CPU core, which
includes NXP extended features.
• automotive-14.0.0_2.1.0_image_8qmek_car2.tar.gz:
Prebuilt-image for i.MX 8QuadMax/8QuadXPlus MEK board with the EVS function
enabled in the Arm Cortex-A CPU core only (EVS function is available after starting
the Android OS from Cortex-A core), which includes NXP extended features.
• automotive-14.0.0_2.1.0_image_95evk_car.tar.gz, automotive-14.0.
0_2.1.0_image_95evk_car2.tar.gz:
Prebuilt-image for i.MX 95 EVK board with the EVS function enabled in the Arm
Cortex-A CPU core only (EVS function is available after starting Android OS from
Cortex-A core), which includes NXP extended features.
All prebuilt images are in a separate package. See the Android Automotive User's
Guide (UG10176) and Android Automotive Quick Start Guide (UG10177) to choose the
appropriate image.

4 Features
This section describes the features in this package.

Table 2. Features
Feature i.MX 8QuadXPlus/ i.MX 95 EVK Remarks
8QuadMax MEK
Google Android 14 release Y Y Based on android-14.0.0_r34 release.
Linux 6.6.30 kernel (merged Y Y Based on Linux OS BSP LF6.6.23_2.0.0 release.
with the AOSP kernel)
Generic Kernel Image (6.6. Y Y Based on AOSP android15-6.6
30)
U-Boot Y Y v2024.04
Trusty OS Y Y -
Graphics-HW Y Y VeriSilicon GC7000L GPU for i.MX 8QuadXPlus,
GC7000XSVX GPU for i.MX 8QuadMax with 6.4.11.
p2 driver, Mali-G310 GPU with r47p0-01eac0 driver
for i.MX 95.
Graphics-HW 3D Y Y OpenGL ES 1.1/2.0/3.1 through GC7000L for i.MX
acceleration 8QuadXPlus, OpenGL ES 1.1/2.0/3.1/3.2 through
GC7000XSVX for i.MX 8QuadMax, OpenGL ES1.1/2.
0/3.2 through Mali-G310 for i.MX 95.
Graphics-HW accelerated UI Y Y OpenGL ES 3.1 through GC7000L for i.MX 8Quad
surface composition XPlus, OpenGL ES 3.2 through GC7000XSVX for
i.MX 8QuadMax, OpenGL ES3.2 through Mali-G310
for i.MX 95.
SCFW Y N Version 1.16.0
SECO firmware Y N Version 3.8.5 for i.MX 8QuadMax B0, i.MX 8Quad
XPlus B0, and i.MX 8QuadXPlus C0.
Boot source eMMC eMMC -
Splash Screen Y Y Supports USB mouse.
UI (input) Y Y -
UI (display) HDMI display Y Supports LVDS-to-HDMI display.

RN00227 All information provided in this document is subject to legal disclaimers. © 2024 NXP B.V. All rights reserved.

Release notes Rev. automotive-14.0.0_2.1.0 — 7 November 2024 Document feedback

3 / 11
NXP Semiconductors
RN00227
Android Automotive Release Notes

Table 2. Features...continued
Feature i.MX 8QuadXPlus/ i.MX 95 EVK Remarks
8QuadMax MEK
UI (brightness control) N N -
Storage - External Media Y Y -
Connectivity - Ethernet Y Y Atheros AR8031
Connectivity - Bluetooth Y Y PCIE9098 (Murata LBEE5ZZ1XL) for i.MX 8QuadMax
wireless technology and 8QuadXPlus. PCIE9098 (U-Blox JODY-W3) for
i.MX 95.
Profiles: A2DP Sink, AVRCP, BLE Host, HFP,
PBAPClient, MAPMCE, PAN.
Connectivity - Wi-Fi Y Y PCIE9098 (Murata LBEE5ZZ1XL) for i.MX 8QuadMax
and 8QuadXPlus. PCIE9098 (U-Blox JODY-W3) for
i.MX 95.
Features: STA mode, AP mode, AP/STA Concurrency.
Connectivity - USB Tethering Y Y Supports Wi-Fi as upstream.
Power - CPU Freq Y Y -
Power - Bus Freq Y Y -
Media - Music Play Y Y i.MX 8/95: SAI+WM8960 or WM8962.
i.MX 8: ESAI+CS42888 (no support for multichannel)
i.MX 95: SAI+CS42888 (no support for multichannel)
Media - HDMI audio output N N -
Misc - ADB over USB Y Y -
Misc - Fastboot utility Y Y -
Misc - SW update and Y Y -
factory reset
File-based Encryption Y Y -
webGL Y Y -
Vulkan Y Y -
USB TYPEC PD Y Y -
OTA for A/B Y Y -
TEE backed Keymaster HAL Y Y This is based on the i.MX Trusty OS TEE firmware.
TEE backed AVB Y Y This is based on the i.MX Trusty OS TEE firmware
and secure storage of eMMC chip. In this release, the
RPMB part needs to be initialized manually.
Media rearview camera Y Y MAX9286 camera.
Car Audio Policy Y Y All sounds are played from the audio jack on the CPU
board. Rear zone audio is played to an extended
audio board (CS42888 codec). Rear zone audio is an
optional audio path.

5 Multimedia Codecs
For multimedia codecs and features, see the i.MX Android Extended Codec Release Notes (RN00202).
RN00227 All information provided in this document is subject to legal disclaimers. © 2024 NXP B.V. All rights reserved.

Release notes Rev. automotive-14.0.0_2.1.0 — 7 November 2024 Document feedback

4 / 11
NXP Semiconductors
RN00227
Android Automotive Release Notes

6 Change Logs
Compared to the automotive-14.0.0_1.1.0 release, automotive-14.0.0_2.1.0 has the following major changes:
• Upgraded the Android code base from android-14.0.0_r17 to android-14.0.0_r34.
• Upgraded the GKI kernel from android14-6.1-2024-01_r4 to android15-6.6.
• Upgraded U-Boot from 2023.04 to 2024.04.
• Upgraded ATF from v2.8 to v2.10.

Compared to the automotive-14.0.0_2.1.0-imx95-er release, automotive-14.0.0_2.1.0 has the following major

changes:
• Upgraded the Android code base from android-14.0.0_r30 to android-14.0.0_r34.
• Upgrade of the i.MX kernel from v6.6.23 to v6.6.30.
• Added GKI support based on AOSP android15-6.6.
• Upgraded U-Boot from 2023.04 to 2024.04.
• Upgraded ATF from v2.8 to v2.10.
• Added experimental support of the i.MX 95 Toradex Verdin board.
• Enabled WideVine L1 on i.MX 95 EVK.

7 Known Issues and Limitations

The known issues about the hardware and hardware rework instructions are not included in this document.
Read all the hardware-related reference materials and ensure that the necessary hardware modifications have
been made before using the software.

Table 3. Known issues and limitations

Issue description Remarks
For i.MX 8QuadXPlus silicon revision B0 In the default settings, the UUU script burns the boot image into the eMMC Boot
chip, it fails to boot from some types of Partition with 32 KB offset. Although it works properly on the MEK board, it fails
eMMC. to read the boot image on some types of eMMC.
There are two possible solutions:
• Download flash.bin in the eMMC Boot Partition + 0 KB offset + eMMC
fastboot enabled in fuse.
• Download flash.bin in the eMMC User Partition + 32 KB offset (eMMC
fastboot can be either enabled or disabled in fuse).
For more information, see https://community.nxp.com/docs/DOC-342877.
The camera may freeze if only one This issue will be fixed in a future release.
camera is connected to the MAX9286
board.
Sound Open Firmware (SOF) is not This issue is related to the image flashed using the -d sof option (dtbo-
working with i.MX 8QuadXPlus. imx8qxp-sof.img). When the SOF dtbo image is used, the media audio is
routed to i.MX 8QuadXPlus DSP (running SOF) but the SOF is crashing during
boot (DSP crash observed in kernel log). This affects the media audio, in which
case the CS42888 codec audio is not working.
Kernel panic when copying a file through The file is not copied to the target. The copy operation freezes. The issue is
MTP (file transfer mode) with the caused by “ERR050149: USB3: TRB OUT endpoits transfer blockage and
disabled ADB. performance delays”.

RN00227 All information provided in this document is subject to legal disclaimers. © 2024 NXP B.V. All rights reserved.

Release notes Rev. automotive-14.0.0_2.1.0 — 7 November 2024 Document feedback

5 / 11
NXP Semiconductors
RN00227
Android Automotive Release Notes

Table 3. Known issues and limitations...continued

Issue description Remarks
Dual Hotspots cannot be used Simultaneous usage of dual hotspots (AP+AP concurrency) with the Wi-Fi
simultaneously with the Wi-Fi station. station (board connected to the external network) is not supported (STA+AP+AP
concurrency is not supported).
Boot animation is not available when Boot animation is terminated earlier than starting the init process.
starting the Car image type.
Multi-display configuration shows nothing When using a multi-display configuration, the unused displays are black.
on the unused displays. Additional tasks can still be launched on them.
No sound can be heard from the On the first boot after installation or after creating and switching to a new driver
CS42888 codec. profile, no sound can be heard from CS42888.
EVS functionality degraded on the Car2 Camera output is available after starting the surface flinger.
image.
Screen recording from the front camera ISI.0 channel resource conflict. ISI.0 channel is using the front camera and VPU
is not available. encoder at the same time.
Changing the HVAC-Auto button value to The Auto button has to be interacted on the HVAC UI at least once. Then, the
OFF with the report or echo command report or echo command works. This issue will be fixed in a future release.
does not work by default after boot.
Power consumption increases when The current EVS AIDL HAL implementation contains two buffer types, camera
running the EVS application. and display. EVS AIDL copies bitmaps between the two buffers by the CPU.
This issue will be fixed in a future release.
For i.MX 95 EVK, the USB-Type C -
port vbus is connected to a 3.3v power
source. Once it is connected to the
host and successfully enumerated by
the host, the gadget stage is changed
to be configured, and the USB HAL
acquires its wakelock. Disconnection
from the host does not generate a
disconnection interrupt. The gadget state
keeps unchanged, and the USB HAL
does not release its wakelock.
cpuidle is not stable and disabled for -
i.MX 95.
The encrypted boot on i.MX 95 EVK is -
not enabled due to the ELE limitation.
For i.MX 8QuadMax, the 9098 Wi-Fi is It is a base board design issue. The M.2 slot on the base board does not
plugged in the PCIeB slot (base board). connect the #W_DISABLE1 and #SDIO_WAKE signals to the i.MX 8QuadMax
The 9098 Wi-Fi firmware loading failed chip. The Wi-Fi module 9098 requires to configure these PADs during the boot/
after the Android Automotive OS reboot. start process.
For the i.MX 95 EVK Car image type, Display drivers are not available in the vendor RAM disk, and the display output
the display is not working in Android is empty in Andorid recovery mode. This issue will be fixed in a future release.
recovery mode.
For i.MX 95 EVK Car/Car2 image The top bar menu can reappear after reconnecting touch or after reopening the
types, the Gallery application, top bar application.
menu, is not visible (but still works) after
interacting with pictures.
For i.MX 95 EVK Car/Car2 image types, The System Manager (SM) does not support this feature in the Android
the Android automotive OS cannot be automotive-14.0.0_2.1.0 version. This issue will be fixed in a future release.

RN00227 All information provided in this document is subject to legal disclaimers. © 2024 NXP B.V. All rights reserved.

Release notes Rev. automotive-14.0.0_2.1.0 — 7 November 2024 Document feedback

6 / 11
NXP Semiconductors
RN00227
Android Automotive Release Notes

Table 3. Known issues and limitations...continued

Issue description Remarks
powered On by the "Power" button on
the board after the software power-off.
For i.MX 8QuadMax, power consumption Linux BSP 6.6.23 RC2 has the same VCC_1V8 and VCC_MAIN increasement in
increases in suspend to RAM mode. suspend to RAM mode.
This issue will be fixed in a future release.
For i.MX 8QuadMax, the board stays This issue will be fixed in a future release.
offline (no ADB or fastboot connection)
during reboot stress test. The issue is
reproducible after 1000 iteration (around
12 hours).
Red Box takes place of Google Maps When switching between menus tabs (Home -> Apps -> Home), the Google
inside the Home Screen. Maps View is colored fully red. When the program goes from one tab to another,
the Activity of the switched tab vanished. Therefore, when the program goes
back from tab Apps to Home, the problem with data synchronization occurs.
Then, Google Maps View turns to red as the default color. When restarting the
Home tab (by clicking on it), the Maps is restarted properly.
ADB connection lost after "adb kill- This issue is possible to reproduce under the platform-tools version 35.0.0 and
server" or switching to USB tethering. above. The ADB device is available again after disconnecting and connecting
the USB cable to the USB host (PC).
For i.MX 95 EVK Car/Car2 image types, The network device unicast and multicast address lists should be protected by
NETC Linux driver can crash when netif_addr_lock_bh() when reading MACs from these lists. If there is no
the network interfaces of ENETC are lock protection, the currently read entry may be released by other threads, which
frequently up and down. may result in accessing a null pointer.
This issue will be fixed in a future release.
The command adb kill-server The connection is recovered only if the sudo is used in sudo adb start-
causes lose of ADB connection. server. This issue is available from the Android build tools version 35 and
above.
This issue will be fixed in a future release.
For i.MX 95 EVK Car/Car2 image types, The Linux kernel can crash during unmounting the Android file system on the
the Linux kernel can crash during the end Android reboot process. This issue will be fixed in a future release.
reboot of the Android Automotive OS.

8 Revision History
This table provides the revision history.

Table 4. Revision history

Document ID Release date Description
RN00227 v.automotive-14.0.0_2.1.0 7 November 2024 i.MX 8QuadXPlus/8QuadMax MEK (Silicon Revision B0, C0)
GA release, i.MX 95 EVK (Silicon Revision A1 19x19) Alpha
(EAR)
AARN_14.0.0_1.1.0 20 June 2024 i.MX 8QuadXPlus/8QuadMax MEK (Silicon Revision B0, C0)
GA release
automotive-13.0.0_2.3.0 4 January 2024 i.MX 8QuadXPlus/8QuadMax MEK (Silicon Revision B0, C0)
GA release
automotive-13.0.0_2.1.0 10/2023 i.MX 8QuadXPlus/8QuadMax MEK (Silicon Revision B0, C0)
GA release

RN00227 All information provided in this document is subject to legal disclaimers. © 2024 NXP B.V. All rights reserved.

Release notes Rev. automotive-14.0.0_2.1.0 — 7 November 2024 Document feedback

7 / 11
NXP Semiconductors
RN00227
Android Automotive Release Notes

Table 4. Revision history...continued

Document ID Release date Description
automotive-13.0.0_1.3.0 07/2023 i.MX 8QuadXPlus/8QuadMax MEK (Silicon Revision B0, C0)
GA release
automotive-13.0.0_1.1.0 05/2023 i.MX 8QuadXPlus/8QuadMax MEK (Silicon Revision B0, C0)
GA release
automotive-12.1.0_1.1.0 12/2022 i.MX 8QuadXPlus/8QuadMax MEK (Silicon Revision B0, C0)
GA release
automotive-12.0.0_2.1.0 09/2022 i.MX 8QuadXPlus/8QuadMax MEK (Silicon Revision B0, C0)
GA release
automotive-12.0.0_1.1.0 06/2022 i.MX 8QuadXPlus/8QuadMax MEK (Silicon Revision B0, C0)
GA release
automotive-11.0.0_2.5.0 03/2022 i.MX 8QuadXPlus/8QuadMax MEK (Silicon Revision B0, C0)
GA release
automotive-11.0.0_2.3.0 12/2021 i.MX 8QuadXPlus/8QuadMax MEK (Silicon Revision B0, C0)
GA release
automotive-11.0.0_2.1.0 11/2021 Added the examples for i.MX 8QuadXPlus and upgraded the
tool version
android-11.0.0_1.1.0-AUTO 01/2021 i.MX 8QuadXPlus/8QuadMax MEK GA release
android-10.0.0_2.4.0 07/2020 i.MX 8QuadMax MEK GA release
android-10.0.0_2.2.0-AUTO 06/2020 i.MX 8QuadXPlus/8QuadMax MEK GA release
automotive-10.0.0_1.1.0 03/2020 i.MX 8QuadXPlus/8QuadMax MEK (Silicon Revision B0) GA
release
P9.0.0_2.1.0-AUTO-ga 08/2019 Updated the location of the SCFW porting kit
P9.0.0_2.1.0-AUTO-ga 04/2019 i.MX 8QuadXPlus/8QuadMax Automotive GA release
P9.0.0_1.0.2-AUTO-beta 01/2019 i.MX 8QuadXPlus/8QuadMax Automotive Beta release
P9.0.0_1.0.2-AUTO-alpha 11/2018 i.MX 8QuadXPlus/8QuadMax Automotive Alpha release
O8.1.0_1.1.0_AUTO-beta 05/2018 i.MX 8QuadXPlus/8QuadMax Beta release
O8.1.0_1.1.0_AUTO-EAR 02/2018 Initial release

RN00227 All information provided in this document is subject to legal disclaimers. © 2024 NXP B.V. All rights reserved.

Release notes Rev. automotive-14.0.0_2.1.0 — 7 November 2024 Document feedback

8 / 11
NXP Semiconductors
RN00227
Android Automotive Release Notes

Legal information
Definitions Suitability for use in automotive applications — This NXP product has
been qualified for use in automotive applications. If this product is used
by customer in the development of, or for incorporation into, products or
Draft — A draft status on a document indicates that the content is still services (a) used in safety critical applications or (b) in which failure could
under internal review and subject to formal approval, which may result lead to death, personal injury, or severe physical or environmental damage
in modifications or additions. NXP Semiconductors does not give any (such products and services hereinafter referred to as “Critical Applications”),
representations or warranties as to the accuracy or completeness of then customer makes the ultimate design decisions regarding its products
information included in a draft version of a document and shall have no and is solely responsible for compliance with all legal, regulatory, safety,
liability for the consequences of use of such information. and security related requirements concerning its products, regardless of
any information or support that may be provided by NXP. As such, customer
assumes all risk related to use of any products in Critical Applications and
Disclaimers NXP and its suppliers shall not be liable for any such use by customer.
Accordingly, customer will indemnify and hold NXP harmless from any
claims, liabilities, damages and associated costs and expenses (including
Limited warranty and liability — Information in this document is believed
attorneys’ fees) that NXP may incur related to customer’s incorporation of
to be accurate and reliable. However, NXP Semiconductors does not give
any product in a Critical Application.
any representations or warranties, expressed or implied, as to the accuracy
or completeness of such information and shall have no liability for the
Export control — This document as well as the item(s) described herein
consequences of use of such information. NXP Semiconductors takes no
may be subject to export control regulations. Export might require a prior
responsibility for the content in this document if provided by an information
authorization from competent authorities.
source outside of NXP Semiconductors.
In no event shall NXP Semiconductors be liable for any indirect, incidental,
HTML publications — An HTML version, if available, of this document is
punitive, special or consequential damages (including - without limitation -
provided as a courtesy. Definitive information is contained in the applicable
lost profits, lost savings, business interruption, costs related to the removal
document in PDF format. If there is a discrepancy between the HTML
or replacement of any products or rework charges) whether or not such
document and the PDF document, the PDF document has priority.
damages are based on tort (including negligence), warranty, breach of
contract or any other legal theory.
Translations — A non-English (translated) version of a document, including
Notwithstanding any damages that customer might incur for any reason the legal information in that document, is for reference only. The English
whatsoever, NXP Semiconductors’ aggregate and cumulative liability version shall prevail in case of any discrepancy between the translated and
towards customer for the products described herein shall be limited in English versions.
accordance with the Terms and conditions of commercial sale of NXP
Semiconductors.
Security — Customer understands that all NXP products may be subject to
unidentified vulnerabilities or may support established security standards or
Right to make changes — NXP Semiconductors reserves the right to specifications with known limitations. Customer is responsible for the design
make changes to information published in this document, including without and operation of its applications and products throughout their lifecycles
limitation specifications and product descriptions, at any time and without to reduce the effect of these vulnerabilities on customer’s applications
notice. This document supersedes and replaces all information supplied prior and products. Customer’s responsibility also extends to other open and/or
to the publication hereof. proprietary technologies supported by NXP products for use in customer’s
applications. NXP accepts no liability for any vulnerability. Customer should
Applications — Applications that are described herein for any of these regularly check security updates from NXP and follow up appropriately.
products are for illustrative purposes only. NXP Semiconductors makes no
Customer shall select products with security features that best meet rules,
representation or warranty that such applications will be suitable for the
regulations, and standards of the intended application and make the
specified use without further testing or modification.
ultimate design decisions regarding its products and is solely responsible
Customers are responsible for the design and operation of their for compliance with all legal, regulatory, and security related requirements
applications and products using NXP Semiconductors products, and NXP concerning its products, regardless of any information or support that may be
Semiconductors accepts no liability for any assistance with applications or provided by NXP.
customer product design. It is customer’s sole responsibility to determine
NXP has a Product Security Incident Response Team (PSIRT) (reachable
whether the NXP Semiconductors product is suitable and fit for the
at [email protected]) that manages the investigation, reporting, and solution
customer’s applications and products planned, as well as for the planned
release to security vulnerabilities of NXP products.
application and use of customer’s third party customer(s). Customers should
provide appropriate design and operating safeguards to minimize the risks
associated with their applications and products. NXP B.V. — NXP B.V. is not an operating company and it does not distribute
or sell products.
NXP Semiconductors does not accept any liability related to any default,
damage, costs or problem which is based on any weakness or default
in the customer’s applications or products, or the application or use by
customer’s third party customer(s). Customer is responsible for doing all Trademarks
necessary testing for the customer’s applications and products using NXP
Semiconductors products in order to avoid a default of the applications Notice: All referenced brands, product names, service names, and
and the products or of the application or use by customer’s third party trademarks are the property of their respective owners.
customer(s). NXP does not accept any liability in this respect.
NXP — wordmark and logo are trademarks of NXP B.V.
Terms and conditions of commercial sale — NXP Semiconductors AMBA, Arm, Arm7, Arm7TDMI, Arm9, Arm11, Artisan, big.LITTLE,
products are sold subject to the general terms and conditions of commercial Cordio, CoreLink, CoreSight, Cortex, DesignStart, DynamIQ, Jazelle,
sale, as published at https://www.nxp.com/profile/terms, unless otherwise Keil, Mali, Mbed, Mbed Enabled, NEON, POP, RealView, SecurCore,
agreed in a valid written individual agreement. In case an individual Socrates, Thumb, TrustZone, ULINK, ULINK2, ULINK-ME, ULINK-
agreement is concluded only the terms and conditions of the respective PLUS, ULINKpro, μVision, Versatile — are trademarks and/or registered
agreement shall apply. NXP Semiconductors hereby expressly objects to trademarks of Arm Limited (or its subsidiaries or affiliates) in the US and/or
applying the customer’s general terms and conditions with regard to the elsewhere. The related technology may be protected by any or all of patents,
purchase of NXP Semiconductors products by customer. copyrights, designs and trade secrets. All rights reserved.
Bluetooth — the Bluetooth wordmark and logos are registered trademarks
owned by Bluetooth SIG, Inc. and any use of such marks by NXP
Semiconductors is under license.

RN00227 All information provided in this document is subject to legal disclaimers. © 2024 NXP B.V. All rights reserved.

Release notes Rev. automotive-14.0.0_2.1.0 — 7 November 2024 Document feedback

9 / 11
NXP Semiconductors
RN00227
Android Automotive Release Notes

TensorFlow, the TensorFlow logo and any related marks — are

trademarks of Google Inc.

RN00227 All information provided in this document is subject to legal disclaimers. © 2024 NXP B.V. All rights reserved.

Release notes Rev. automotive-14.0.0_2.1.0 — 7 November 2024 Document feedback

10 / 11
NXP Semiconductors
RN00227
Android Automotive Release Notes

Contents
1 Release Description ........................................ 2
2 Supported Hardware SoC/Boards .................. 2
3 Release Package Contents ............................. 2
4 Features ............................................................ 3
5 Multimedia Codecs .......................................... 4
6 Change Logs ....................................................5
7 Known Issues and Limitations ....................... 5
8 Revision History .............................................. 7
Legal information .............................................9

Please be aware that important notices concerning this document and the product(s)
described herein, have been included in section 'Legal information'.

© 2024 NXP B.V. All rights reserved.

For more information, please visit: https://www.nxp.com Document feedback
Date of release: 7 November 2024
Document identifier: RN00227