Boot otas for 16kb developer option are failing on builds signed with release keys are failing due verification issues. Turning off the incremental otas
Test: atest Enable16KbTest
Bug: 339658378
Change-Id: Idfc3efc796b599de66ddc52cbee37ca3d74d11b6
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
Remove irrelevant copy and paste content. None of the zuma
devices ever included these services and these sockets are
not doing anything.
Bug: 234559097
Test: presubmit
Flag: EXEMPT dead code removal
Change-Id: I8664262708b89016227d7df076e7c8d70a53de07
This change is to allow the CPU Idle Histogram Stats to be dumped in
bugreports so that there is more insight into the idle behavior of
devices in the field.
Test: Build/Flash
Test: adb bugreport
Bug: 344908619
Flag: EXEMPT bugfix
Change-Id: I9c31b4fbaf8adb35df27f4d19a7bf87ac33b05d3
Signed-off-by: Vishvam Mazumdar <vmazumdar@google.com>
am skip reason: Merged-In Iad74cae0d6ad6887d79d705dc8478f1b44532503 with SHA-1 12f2e55257 is already in history
Original change: https://android-review.googlesource.com/c/device/google/zuma/+/3164638
Change-Id: Id46e979b5ca60952cadf16b596ed5227325339a4
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
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: 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: Ibd060eae8f4e97ae8ff800f765e2310c984e5796
This reverts commit 721a8358c6.
Reason for revert: 24Q3 has been cut, relanding the original commit ef68e9b578.
Change-Id: I7882ebafd66d126df9ccbe2124617fbf4ed73eb5
Bug: 347272991
We're copying from a live r/w image, so the picture we get may be a bit
distorted. Running fsck over the image first should help with
reliability, but f2fs does some fixes on mount as well, so we mount and
unmount the image before running dump.f2fs.
Change-Id: Ibb15388c55b6f909a1d1b849f9760f248644d9e9
Signed-off-by: Daniel Rosenberg <drosen@google.com>
Bug: 349120101
Test: atest CopyEfsTest
Flag: TEST_ONLY
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
This will allow to run the tests out of the pixel tests set rather than the super large device-tests set. Which will save build resources.
Flag: TEST_ONLY
Change-Id: I7d902662dff05dfdc88808c5647793ff5bde6107
Test: presubmit
Bug: 342232954
4k mode devices no longer set up redirection, so the old test would fail
now. Instead, this tests that the contents of the copied partitions will
match. Since the partitions are mounted and could change, we work off of
a copy.
Change-Id: Ia98517bb4ede9cb3416132e815da9b87728423a6
Signed-off-by: Daniel Rosenberg <drosen@google.com>
Flag: TEST_ONLY
Bug: 347744178
Test: atest CopyEfsTest
The graphics hal might need to access /persist early in the boot
process. So mount persist early for 4K devices.
Test: boot 4K device
Bug: 338504890
Change-Id: I4b2a0a61ebaff5d85a4daac445d81ae3d21aa9c3
am skip reason: Merged-In I38eef1dff949c4275bf0b355582238678a6894a7 with SHA-1 120974a4b1 is already in history
Original change: https://googleplex-android-review.googlesource.com/c/device/google/zuma/+/27908527
Change-Id: I7c7aba2e51fdcb33140f33d5e648a238e5b2988a
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
treehugger does not have any test suite setup for zuma target,
and CopyEfsTest should only be run on zuma targets. So remove
from test mapping to unbreak tests.
Test: th
Bug: 347396961
Change-Id: I079d24cae4808d3370c3821412640f7fef1d0cc7
