Since the TARGET_RECOVERY_UI_LIB for each device is not exactly the
same, and most of the modules in it contain `soong_namespace{}` to
avoid conflicts between different devices, after converting
`librecovery_ui_ext` from Android.mk to Android.bp, it needs to be
changed to a `fully qualified name` in order to correctly use the
corresponding module.
Flag: EXEMPT refactor
Bug: 339143524
Test: m -j librecovery_ui_ext
Merged-In: I2912cbc905ff0ee716c293021c29061e3b6d3dca
Change-Id: I2912cbc905ff0ee716c293021c29061e3b6d3dca
Set the full module path of libacryl_hdr_plugin and the include dir for
lobacryl conversion to soong. It will take effect after aosp/3286932 and
aosp/3287183 merged.
Bug: 370414334
Test: lunch aosp_shiba-trunk_staging-userdebug ; m libacryl_hdr_plugin libacryl
Change-Id: I253ce1254450385e83ecaa75acbee5e70df3a930
to avoid build breakage with test kernel prebuilts (e.g. ag/28525733)
that doesn't have 16kb artifacts in it.
Bug: 370842132
Bug: 349877551
Flag: EXEMPT bugfix
Change-Id: I2f6c1f3365f624502366b883dbcd1066ed166cdb
Merged-In: I2f6c1f3365f624502366b883dbcd1066ed166cdb
The makefile logic in device/google/shusky/BoardConfig-shusky-common.mk
is identical to the logic required for akita. 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: Ibd060eae8f4e97ae8ff800f765e2310c984e5796
Merged-In: Ibd060eae8f4e97ae8ff800f765e2310c984e5796
The build flag PRODUCT_BOOTS_16K will be used to select
the proper efs rc file and fstab:
- When PRODUCT_BOOTS_16K := true, 16k rc files and fstab will be used.
- When PRODUCT_BOOTS_16K := false, 4k rc files and fstab will be used.
Bug: 370842132
Bug: 346868433
Test: Built and booted up `aosp_shiba` and and `aosp_shiba-pgagnostic` targets
Flag: EXEMPT bugfix
Change-Id: I4dba20518925a176f1e1e66596e2bb1e8ade7c26
Merged-In: I4dba20518925a176f1e1e66596e2bb1e8ade7c26
These are used for testing, enable Secretkeeper on these devices.
Test: get_build_var SECRETKEEPER_ENABLED
Bug: 341708664
Change-Id: I0fd0e3d5a16cab352c79228e89f9d2fdd6f886b7
This variable only does something when it differs from
TARGET_CPU_VARIANT. Setting it to the same values doesn't do
anything.
Bug: 368635026
Test: presubmit
Change-Id: I1e16c5b9244eca4d69909bb1caefebfc17e54a70
std::vector<const T> uses std::allocator<const T>, which is an
undocumented libc++ extension to the C++ standard library. The extension
was removed in llvm.org/PR96319. Use an ordinary non-const T instead.
Bug: http://b/349681543
Test: m android.hardware.power.stats-impl.zuma
Flag: EXEMPT, refactor to fix build failure
Change-Id: I47d0b3a441ab4ec8dd2ad8e794ae84f184d0d40f
This variable doesn't do anything for devices launching with
API level 26 or later, and the initial zuma devices (Pixel 8)
launched with API level 34.
Bug: 307369186
Test: presubmit
Flag: EXEMPT trivial build cleanup
Change-Id: I181937f9e49d4b9e1088fc92df7681d1a39e3d26
Merged-In: I181937f9e49d4b9e1088fc92df7681d1a39e3d26
The AOSP builds do not have a compatible BL for Secretkeeper (24Q3+).
This leads the crashing of HAL since the backing trusty is not updated
with the TA.
Test: lunch aosp & non-aosp targets -> get_build_var SECRETKEEPER_ENABLED
Bug: 350482613
Change-Id: I49d30914bc7a4b2b752a6d9eb7db0e7959638d98
Add a log for the retry. Also define the sleep time in the header file.
Bug: 341996696
Change-Id: Ib3cc0c6ad576e7cda26b7f50cdc61d52e6349c78
Signed-off-by: Kyle Tso <kyletso@google.com>
pgagnotic targets might boot into 16KB directly(w/o dev options),
in which case it would need copy efs files support to be enabled.
Test: boot device with dev option disabled, check efs
Bug: 346275905
Change-Id: If18bfa0b0646da8008c6d92bec094b236273cbfc