tag | 70afa58b6f21ea2cd531375609d08d5b1ec4ac4f | |
---|---|---|
tagger | The Android Open Source Project <initial-contribution@android.com> | Tue May 14 16:42:07 2024 -0700 |
object | aea197031af3deb10111433593f398af078617f9 |
Android 14.0.0 release 40
commit | aea197031af3deb10111433593f398af078617f9 | [log] [tgz] |
---|---|---|
author | Pranav Gupta <pranavgupta@google.com> | Wed Apr 26 02:04:17 2023 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Apr 26 02:04:17 2023 +0000 |
tree | 9eba7ed9de4a3d6dd474733722cf66d55ad5a6e7 | |
parent | 1fab4e462a239db7dd8fcc432dc83dca05c86024 [diff] | |
parent | e99b7707772edfceba41f13be61d477c57264146 [diff] |
Set MODULE_BUILD_FROM_SOURCE to true for GSI images am: e99b770777 Original change: https://googleplex-android-review.googlesource.com/c/device/generic/common/+/22830026 Change-Id: I99dfa006595e2e47c67478665fa63997df7a4d26 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
This document introduces special GSI settings for facilitating xTS-on-GSI with a single image.
[BoardConfigGsiCommon.mk] BOARD_USES_SYSTEM_DLKMIMAGE := true BOARD_SYSTEM_DLKMIMAGE_FILE_SYSTEM_TYPE := ext4 TARGET_COPY_OUT_SYSTEM_DLKM := system_dlkm [gsi_release.mk] PRODUCT_BUILD_SYSTEM_DLKM_IMAGE := false
Starting from Android 13, all devices must include a system_dlkm partition. GSI enables system_dlkm to support the devices with system_dlkm partition, and be compatible with old devices without a system_dlkm partition.
With these configurations, /system/system_dlkm
would not be created. Instead, a /system/lib/modules
-> /system_dlkm/lib/modules
symlink is created.
For device without system_dlkm partition, the symlink would be dangling. The dangling symlink shouldn‘t be followed anyway because the device doesn’t use system_dlkm.
For device with system_dlkm, they can load modules via that path normally like when they are using their original system image.
Some devices access the private android framework resource by @*android:
while overlaying their SystemUI setting status_bar_header_height_keyguard
. However, referencing private framework resource IDs from RRO packages in the vendor partition crashes on these devices when GSI is used. This is because private framework resource don't have a stable ID, and these vendor RRO packages would be referencing to dangling resource references after GSI is used (b/245806899).
In order to prevent SystemUI crash, GSI adds a runtime resource overlay in the system_ext partition, which have higher overlay precedence than RROs on vendor partition, so the problematic vendor RROs would be overridden.
Lifetime of this package: