commit | a7e0009116eb6c41f26b33e11a6aa41b7827d2a8 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <[email protected]> | Fri Jul 07 04:35:40 2023 +0000 |
committer | Android Build Coastguard Worker <[email protected]> | Fri Jul 07 04:35:40 2023 +0000 |
tree | 9eba7ed9de4a3d6dd474733722cf66d55ad5a6e7 | |
parent | afff79c8641d51e53e49f564ce79993b474b6c8c [diff] | |
parent | 3c5896d68f8d264272e01af4c3c82a9ffaa64864 [diff] |
Snap for 10453563 from 3c5896d68f8d264272e01af4c3c82a9ffaa64864 to mainline-art-release Change-Id: I6da1f654398879db66cd681f8cd3b967189bfa00
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: