For zumapro it shares the same libacryl_plugins in zuma but for
libexynosdisplay it still has different version between zuma and
zumapro. In ag/30508311 it already split
hardware/google/graphics/zuma/libhwc2.1 to it's own soong_namespace
which need to add it to product config for zuma.
Bug: 357500180
Test: lunch aosp_husky-trunk_staging-userdebug; \
m libexynosdisplay
Flag: EXEMPT refactor
Change-Id: I8adc95085067456aa2a29822e89f9777ece241f3
Makefile contain the following sysprops
bluetooth.profile.bap.unicast.server.enabled
bluetooth.profile.tbs.server.enabled
bluetooth.profile.vc.server.enabled
However, CS indicates the above sysprops aren't defined anywhere
nor read anywhere? Given how the following LE Audio sysprops are
missing from the makefile, and the similarities in naming, we
suspect there was a typo?
bluetooth.profile.bap.unicast.client.enabled
bluetooth.profile.ccp.server.enabled
bluetooth.profile.vcp.controller.enabled
Bug: 372711861
Test: builds
Flag: EXEMPT bugfix
Change-Id: I3b1be96531ffa6639647e0240dfc0f07ad1843a3
These are used for testing, enable Secretkeeper on these devices.
Test: get_build_var SECRETKEEPER_ENABLED
Bug: 341708664
Change-Id: I0fd0e3d5a16cab352c79228e89f9d2fdd6f886b7
The mq-deadline I/O scheduler is more stable than BFQ. Additionally, the
boot time is shorter with the mq-deadline I/O scheduler. It only changes the scheduler on new kernel.
Bug: 186902601
Test: forrest build
Change-Id: I51605b32afb4340d416fe4923570bb3f4af24ab8
Signed-off-by: Ocean Chen <oceanchen@google.com>
For PDK build, the "vendor/unbundled_google" path doesn't exist.
"GoogleDialer" will be built from vendor/google_devices/zuma/proprietary/GoogleDialer.
Flag: EXEMPT bugfix
Bug: 358012156
Test: export USES_GOOGLE_DIALER_CARRIER_SETTINGS=true; m GoogleDialer
Change-Id: If2aab058f23cebc5a25862c69deda508f5f9c37e
- power measurement result is on b/262803152#comment5
Bug: 355912013
Test: spatial audio
Flag: EXEMPT bugfix
Change-Id: I324288f219b2fecbc0ae4f3ce3c11ea6e93f4b2e
In case of always, we always enable hdcp regardless of drm status.
Bug: 359951297
Flag: EXEMPT bugfix
Change-Id: I04b5174be296d93a9f898929706785d50116d7a7
Signed-off-by: Ji Soo Shin <jisshin@google.com>
For PDK build, the "vendor/arm" path doesn't exist. The modules will be
built from vendor/google_devices/zuma/prebuilts/gpu.
Flag: EXEMPT bugfix
Bug: 357770476
Test: 1. lunch akita-trunk_staging-eng
2. m libGLES_mali vulkan.mali libOpenCL libgpudataproducer
Change-Id: I97631ffdc98b77b747f0abbc7e376d8fbe2a576d
Set the variable is true when USE_LASSEN_OEMHOOK is true and
BOARD_WITHOUT_RADIO is not true.
Flag: EXEMPT bugfix
Bug: 325857852
Test: lunch akita-trunk_staging-userdebug && m ConnectivityMonitor
Change-Id: I44df84ade1c8394a562b523264d5f3f08cb5b5b3
Pixel has removed unnecessary allocation padding, and we now pass
dEQP with a maximum physical core index setting of 4, which allows
the driver to utilize 2 GPU cores (1001b) in the extreme tests.
Bug: 221255664
Test: HK3 atest CtsDeqpTestCases -- --module-arg 'CtsDeqpTestCases:include-filter:dEQP-VK.protected_memory.*'
Flag: EXEMPT bugfix
Change-Id: I96a38a6070968100ce3adf01da7235a807bf31ab
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
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: 346868433
Test: Built Pixel 8 targets
$ source build/envsetup.sh
$ lunch husky_pgagnostic-trunk_staging-userdebug
$ get_build_var DEVICE_PAGE_AGNOSTIC
$ get_build_var TARGET_KERNEL_DIR
device/google/shusky-kernels/6.1/trunk-12010727/16kb
$ get_build_var TARGET_BOARD_KERNEL_HEADERS
device/google/shusky-kernels/6.1/trunk-12010727/kernel-headers
$ get_build_var PRODUCT_BOOTS_16K
true
$ get_build_var TARGET_RW_FILE_SYSTEM_TYPE
ext4
$ get_build_var TARGET_USERDATAIMAGE_FILE_SYSTEM_TYPE
ext4
Flag: EXEMPT bugfix
Change-Id: I4dba20518925a176f1e1e66596e2bb1e8ade7c26
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
