commit | fdf499547f5aa24a5b1393fd63c962172b095adf | [log] [tgz] |
---|---|---|
author | Roman Kiryanov <rkir@google.com> | Fri Apr 21 11:12:39 2023 -0700 |
committer | Roman Kiryanov <rkir@google.com> | Sat Apr 22 17:13:09 2023 -0700 |
tree | c8c8e3e4be8339cedf3908c44432ea9c8a4fb572 | |
parent | 650482b6fbd639306a31e064a3077824cc779f76 [diff] |
Unset BOARD_X_FILE_SYSTEM_TYPE required if TARGET_COPY_OUT_X is 'system/xyz'. Bug: 111538404 Test: presubmit Change-Id: Icabc7d0deec82746fb7220bc16a0e4385f404a0d Signed-off-by: Roman Kiryanov <rkir@google.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: