| commit | 6082ff24638bfca22210144cf600158fcf23ec3e | [log] [tgz] |
|---|---|---|
| author | SzuWei Lin <[email protected]> | Sun Feb 23 20:03:36 2025 -0800 |
| committer | Automerger Merge Worker <[email protected]> | Sun Feb 23 20:03:36 2025 -0800 |
| tree | 642a6312a8dba608839439e64c22cddb5a6e96d1 | |
| parent | dcaa3ccf9d61d41540f64917b1e1f7f79cb0934e [diff] | |
| parent | a3bb259540dc8cebeb8239faa68a6ccdeac6ab88 [diff] |
Merge "[owners] Remove [email protected] from OWNERS" into main am: a3bb259540 Original change: https://android-review.googlesource.com/c/device/generic/common/+/3504874 Change-Id: Ie7c4f30c4bd26c9b9f512d76f810e94944a48b94 Signed-off-by: Automerger Merge Worker <[email protected]>
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: