Flag: EXEMPT gated by overlay
Bug: 373594936
Test: Manuel test, trigger SSR and won't create bugreport automatically
Change-Id: I28af1c1400b90b302b3c9b86c1c377dcdfe6db2a
This build flag is not used now.
Test: build
Bug: 376153497
Flag: EXEMPT only modify device config file
Change-Id: If8ac0328494e15ee4a18e9316f527d9867a129c0
am skip reason: Merged-In I80cb3e9f4c4a1609ca668af554d930edb3b4c5a0 with SHA-1 2502760f89 is already in history
Original change: https://android-review.googlesource.com/c/device/google/shusky/+/3311724
Change-Id: I8e121634457f86f748c10d62d84b1cfd7da0151f
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Ic1da7f21b696f1659ef7d7b0b7089c3d2c03103e with SHA-1 d3ad2f99ce is already in history
Original change: https://android-review.googlesource.com/c/device/google/shusky/+/3311723
Change-Id: Ia49a05c3cfeb25328447e53191bc81131371b286
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Ia75c7f8cfca6d651777c730a3f86715a0991fbec with SHA-1 73c64fff21 is already in history
Original change: https://android-review.googlesource.com/c/device/google/shusky/+/3311722
Change-Id: Ie4e972e96ad18d1e0f88414df436e5ac6bb60656
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
The makefile logic in this file is identical to the logic required for
akita-trunk_staging-userdebug. Hence, this logic is moved to
device/google/zuma/BoardConfig-16k-common.mk to avoid duplicating the
file for akita.
Bug: 370842132
Bug: 349877551
Test: Built and booted up `aosp_shiba` and and `aosp_shiba-pgagnostic` targets
Flag: EXEMPT bugfix
Change-Id: I80cb3e9f4c4a1609ca668af554d930edb3b4c5a0
Merged-In: I80cb3e9f4c4a1609ca668af554d930edb3b4c5a0
TARGET_ build variables MUST NOT be set up in device*
files. In the device* files, the PRODUCT_ variables are not
defined properly and only after the build system finishes
parsing all the product files, we can set up TARGET_ vars
based on PRODUCT_ vars. During the parsing of the BoardConfig
files, the PRODUCT_ vars are defined and their values can
not be changed.
Test: Built and booted up `aosp_shiba` and and `aosp_shiba-pgagnostic` targets
Bug: 370842132
Bug: 350529323
Bug: 346868433
Flag: EXEMPT bugfix
Change-Id: Ic1da7f21b696f1659ef7d7b0b7089c3d2c03103e
Merged-In: Ic1da7f21b696f1659ef7d7b0b7089c3d2c03103e
The build flag PRODUCT_BOOTS_16K will be used to select
whether the shusky devices boot with 16kb kernel or 4kb kernel.
Bug: 370842132
Bug: 346868433
Test: Built and booted up the following targets:
aosp_shiba_pgagnostic-trunk_staging-userdebug
aosp_shiba-trunk_staging-userdebug
Flag: EXEMPT bugfix
Change-Id: Ia75c7f8cfca6d651777c730a3f86715a0991fbec
Merged-In: Ia75c7f8cfca6d651777c730a3f86715a0991fbec
These streams do not disable TA or FG prefer idle, so restore it.
Bug: 236868627
Flag: NONE powerhint change does not support flags
Test: build pass
Change-Id: Ia0f12911110856b82b858bed11fb5d120388285a
TARGET_RW_FILE_SYSTEM_TYPE is used to decide the fstab configuration to
use for RW files. It must be set to ext4 for targets that boot with 16k
page size kernels.
Test: $ get_build_var TARGET_RW_FILE_SYSTEM_TYPE
ext4
Also built & booted the targets successfully (on internal branch)
Bug: 358213765
Change-Id: Ia4e36e5a5e10ff10e4d43c1089f8a98a3ac601b5
Flag: EXEMPT bugfix
