This change introduces "is APF enabled" system properties, and
uses them as trigger conditions for APF nodes / pre-APF nodes.
By default APF nodes are active, and pre-APF nodes are inactive,
which maintains the situation before this change.
A future experiment will flip "is APF enabled" system properties,
deactivating APF nodes and activating pre-APF nodes. For more
info see go/pixel-perf-apf-experiment.
Bug: 365855872
Test: set vendor.powerhal.apf_enabled=false, vendor.powerhal.apf_disabled=true, observe auto_prefer_fit
procfs value staying "false" and instead preferred_idle_mask_mid
changing to 0x1ff during app launches
Flag: NONE powerhint change does not support flags
Change-Id: I85b5dc812132f229c2cc8583aaadd31d7eedc178
Signed-off-by: Dmitry Skiba <dskiba@google.com>
Bug: 380369950
Test: PTE PQM-BT LE audio unicast test
Flag: EXEMPT The Samsung Galaxy Buds 3 pro users are able to disable LE audio in Settings app
Change-Id: I142d38d66e844aab35a72733e84374df72158042
This build flag is not used now.
Test: build
Bug: 376153497
Flag: EXEMPT only modify device config file
Change-Id: If8ac0328494e15ee4a18e9316f527d9867a129c0
This should be in experimental.
Bug: 352009226
Bug: 349571564
Flag: EXEMPT experimental code
Change-Id: I712caa712286c9625ca22983ba55395f08d7f22d
Signed-off-by: Mostafa Saleh <smostafa@google.com>
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
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
Bug: 258364350
Test: Verification at b/258364350.
Test: Function verification at b/258364350.
Test: Compile and verify the configuration is correct.
Change-Id: I7d6521bef3605dc725c9a9e34f27217ccae42d4e
Husky and shiba might use different kernels moving forward and
dev options should be controlled by separate flags on husky and
shiba.
Test: Build husky-trunk_staging-userdebug
Bug: 342011434
Change-Id: I8c855c95d99e4e4b3f2233179f368bcbb63a9720
