| tag | 2bd1b2e923200890ce2bef3ffaeca39b5b83d6f9 | |
|---|---|---|
| tagger | The Android Open Source Project <initial-contribution@android.com> | Wed Apr 24 20:12:25 2024 -0700 |
| object | 4a489c19d4eb6839de83f4ab23769d23f5c8578a |
aml_cbr_341610000 (11387106,com.google.android.cellbroadcast)
| commit | 4a489c19d4eb6839de83f4ab23769d23f5c8578a | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Fri Jul 07 00:55:27 2023 +0000 |
| committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Fri Jul 07 00:55:27 2023 +0000 |
| tree | 9eba7ed9de4a3d6dd474733722cf66d55ad5a6e7 | |
| parent | cde28891e2e4234d9442fe2415a0b7212906fd4d [diff] | |
| parent | 3c5896d68f8d264272e01af4c3c82a9ffaa64864 [diff] |
Snap for 10447354 from 3c5896d68f8d264272e01af4c3c82a9ffaa64864 to mainline-cellbroadcast-release Change-Id: I6ddb93f79b94bb51847b268a14b45f7f0f3b57e7
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: