Set `avb_keys=no_such_key` for the vendor_dlkm dynamic kernel partition
to allow booting unlocked devices with a custom kernel. This allows a
few things:
1) Dogfooders can flash a custom kernel without wiping their device.
This can help developers track down hard-to-reproduce bugs without
rolling out a patch to the whole dogfooder population.
2) Developers can uprev their device's kernel without wiping their
device or packaging the kernel with an Android platform build.
Note: we are using "no_such_key" to ensure an AVB keys file doesn't
accidentally get created.
Test: Flash CI build. Then flash custom kernel on top.
Bug: 274825778
Change-Id: Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b
This is to avoid unnecessary ext4 behavior
Bug: 289631992
Test: boot to home
Change-Id: I5efdb979e9c738964350b221b9f5fffea19c721d
Signed-off-by: Randall Huang <huangrandall@google.com>
This reverts commit 58893b442f.
Reason for revert: OTA failues observed during S -> T
Bug: 228927535
Test: Full and Incremental OTA's.
Change-Id: Iec9e15d60dab92213494c9e679de6702f8d56e37
Set flags to enable system_dlkm dynamic partition
for GKI Modules for gs101 devices.
Partition will be empty as of now but this adds
enough support to pass the vts for the feature.
Bug: 222334390
Test: TH, manual build, flash and verification on 6Pro
Full OTA Update test from S to T as below:
1. go/flash: git_sc-v2-release - SP2A.220405.004 (8233519)
2. Full ota build from tm-dev
3. Manual push full ota update and verify boot
4. Verify system_dlkm partition is present & mounted
Signed-off-by: Ramji Jiyani <ramjiyani@google.com>
Change-Id: I0b4038b100add965737527b72a8d5f905907e23e
Move zram settings to pixel common mm folder
Bug: 200899926
Test: check swap size
Signed-off-by: Martin Liu <liumartin@google.com>
Change-Id: Ic81e26d706459e14029f611c03df4a14d4184277
Add a file "fstab.gs101-fips" alongside the existing "fstab.gs101" in
order to specify different encryption settings in FIPS mode.
"androidboot.fstab_suffix=gs101-fips" on the kernel command line will be
used to select the FIPS fstab when needed.
As the two fstabs should be otherwise identical, generate them from a
template file so that they will stay in sync.
Note that generating the fstabs requires that they be installed as build
system modules rather than via PRODUCT_COPY_FILES, which results in the
vendor_ramdisk copy of the fstabs being installed to system/etc rather
than /. This shouldn't cause any problem, now that Android has been
updated to look for the fstab in this location too.
Bug: 191417025
Change-Id: I1d115e014df8ba2fb83046ac0b9b791597364846
