Current CAM uclamp min is beyond MID clusters capacity when
CAM2 energy model is used. This causes most of camera HAL threads
scheduled on big cluster only with CAM2 EM profile.
Lowering CAM uclamp min so it is within MID clusters capacity for
both energe model
Flag: EXEMPT tuning changes
Test: check camera trace with proper uclamp value
Bug: 350629738
Change-Id: I40ce59d0a0d99ea6ba016a24245f44713485bc52
This is a clone of the default files, only GAME scenarios
has some order changed to prioritize 48k gaming without source.
Bug: 331490291
Test: Check file location
Flag: NONE system property change only
Change-Id: Ib367e638fc25bd1c8e8be16d5b062ece59354b99
Enable ExitOnComFailure so gpsd will call exit() instead of
calling abort() when com failed due to system performance degradation.
Test: on device
Bug: 341508348
Change-Id: I7994d65f5ac8441f8ed69fb256de9d3afff7919c
Bug: 344685639
Test: Checked the trace file running on the device.
Flag: NONE powerhal doesn't have a flag yet
Change-Id: I8b3918ee11a34315155561bfd0b0a7e9a8f9f32d
Bug: 351981809
Bug: 352658713
Test: AU drop/IFS/RvR/CTS/VTS/Manual Test, JP SAP indoor channel test
Change-Id: If2d46e2bbd7612e6cc6f80bc74c7870dea17e08d
Signed-off-by: Hana Huang <hanahuang@google.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: 349877551
Test: $ lunch shiba-trunk_staging-userdebug
$ get_build_var TARGET_KERNEL_DIR_16K
device/google/shusky-kernels/5.15/trunk-12022168/16kb
$ get_build_var BOARD_KERNEL_PATH_16K
device/google/shusky-kernels/5.15/trunk-12022168/16kb/Image.lz4
$ get_build_var BOARD_16K_OTA_USE_INCREMENTAL
true
$ get_build_var BOARD_16K_OTA_MOVE_VENDOR
true
Flag: EXEMPT bugfix
Change-Id: 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 tested husky-next and husky-pgagnostic targets
$ source build/envsetup.sh
$ lunch husky-trunk_staging-userdebug
$ get_build_var PRODUCT_16K_DEVELOPER_OPTION
true
$ get_build_var TARGET_BOOTS_16K
$ get_build_var TARGET_USERDATAIMAGE_FILE_SYSTEM_TYPE
$ get_build_var TARGET_KERNEL_DIR
device/google/shusky-kernels/6.1/trunk-12034122
$ get_build_var BOARD_KERNEL_PATH_16K
device/google/shusky-kernels/6.1/trunk-12034122/16kb/Image.lz4
$ get_build_var TARGET_KERNEL_DIR_16K
device/google/shusky-kernels/6.1/trunk-12034122/16kb
$ get_build_var ADDITIONAL_PRODUCT_PROPERTIES | grep 16k
ro.product.build.16k_page.enabled=true
$ get_build_var PRODUCT_COPY_FILES | grep efs
device/google/zuma/conf/init.efs.16k.rc:vendor/etc/init/init.efs.rc
$ get_build_var PRODUCT_SOONG_NAMESPACES | grep insmod
device/google/gs-common/insmod/4k
Bug: 350529323
Bug: 346868433
Flag: EXEMPT bugfix
Change-Id: Ic1da7f21b696f1659ef7d7b0b7089c3d2c03103e
Some 16KB kernels have a different device tree(stored on DTBO
partition). Hence add DTBO partition to dev option OTA
Test: th
Bug: 349590107
Change-Id: I1e54dd18a8bbcb82b1fc3b07b29f229b3d5366e5
Bug: 258364350
Test: Verification at b/258364350.
Test: Function verification at b/258364350.
Test: Compile and verify the configuration is correct.
Change-Id: I7d6521bef3605dc725c9a9e34f27217ccae42d4e
am skip reason: Merged-In Id7135d0505aa936207c761f04fb60c1017c125a9 with SHA-1 54ca980874 is already in history
Original change: https://android-review.googlesource.com/c/device/google/shusky/+/3131977
Change-Id: I0c10cb3630f02e1591de8a4ad897dd9cd335c67e
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
