Evolution-X-Tensor/device_google_zuma
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

[conflict] DO NOT MERGE - Run fsck to resolve possible data corruption am: 19eb98145d

Browse source 
Original change: https://googleplex-android-review.googlesource.com/c/device/google/zuma/+/25175376

Bug: 305658663
Change-Id: Icc611e53d39734b7f6ce9c70ca601d61ec4d4e33
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
This commit is contained in:
Jaegeuk Kim 2023-10-26 20:04:00 +00:00
commit 707c8849e5
1 changed files with 4 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

4
device-common.mk
View file

@ -47,6 +47,10 @@ PRODUCT_PRODUCT_PROPERTIES += \
# Set the max page size to 4096 (b/300367402)
PRODUCT_MAX_PAGE_SIZE_SUPPORTED := 4096
# Trigger fsck on upgrade (305658663)
PRODUCT_PRODUCT_PROPERTIES += \
ro.preventative_fsck = 1
# Indicate that the bootloader supports the MTE developer option switch
# (MISC_MEMTAG_MODE_MEMTAG_ONCE), with the exception of _fullmte products that
# force enable MTE.