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
Flag: EXEMPT trivially safe build cleanup
Change-Id: Id2934bc0dcbffb85a43ab020a8208fb85f51432a
Bug: 347122505
Test: check the priority and latency of input thread in Perffeto
Flag: NONE early device setting updates
Change-Id: Ib4f7efd03bb7118b32538b569a6587f4a786ca7b
[5.1/H-1-20] MUST support the Feature_HdrEditing feature for all
hardware AV1 and HEVC encoders present on the device at 4K
resolution or the largest Camera-supported resolution,
whichever is less.
Bug: 343146210
Bug: 343864145
Flag: EXEMPT resource only update
Test: run cts -m CtsMediaPerformanceClassTestCases -- --module-arg \
CtsMediaPerformanceClassTestCases:instrumentation-arg:media-performance-class:=35
Change-Id: I362b9b8cc349f58869aa51322d35930e29a8d2b8
[5.1/H-1-21] MUST support FEATURE_DynamicColorAspect for all
hardware video decoders (AVC, HEVC, VP9, AV1, or later).
Bug: 343864145
Flag: EXEMPT resource only update
Test: run cts -m CtsMediaPerformanceClassTestCases -- --module-arg \
CtsMediaPerformanceClassTestCases:instrumentation-arg:media-performance-class:=35
Test: run cts -m CtsMediaV2TestCases -t android.mediav2.cts.DecoderDynamicColorAspectTest
Test: run cts -m CtsMediaV2TestCases -t android.mediav2.cts.AdaptivePlaybackTest
Change-Id: I97c2e683f2290a91e40be77f595b1043c548db6d
If the enumeration is too long, it may trigger the watchdog mechanism
to cause device reset. Therefore, this patch will modify the timeout.
Ported from Change-Id: Ib54d8ff5a1e680fc86f2b89ee0d02d63ee5741d8
(usb: modify the initial_descriptor_timeout to 500ms)
Bug: 365715654
Test: verified `initial_descriptor_timeout` is set to 500
Flag: EXEMPT cherry-picked CLs from existing projects
Change-Id: I36c5a0ba0a766720cd7d6601cc56f3a883adac8a
Signed-off-by: Kuen-Han Tsai <khtsai@google.com>
For PDK build, the "vendor/arm" path doesn't exist. The modules will be
built from vendor/google_devices/zumapro/prebuilts/gpu.
Flag: EXEMPT bugfix
Bug: 364491703
Test: 1. lunch comet-trunk_staging-eng
2. m libGLES_mali vulkan.mali libOpenCL libgpudataproducer
Change-Id: Ie58b2707fb9774f4a3552561b809c3c15d3803ef
This reverts commit 7e10eefc25.
Reason for revert: Re-enable EHLD since kernel EHLD issue is fixed.
Bug: 354380599
Change-Id: I588c2b96a69cabb7be8d264c9591b61da80fb5e2
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.zumapro
Flag: EXEMPT, refactor to fix build failure
Change-Id: I96ab1eb2caf092008cc573949a1529c057ee4bb1
The 16kb kernels need to select the fstab that has this configurations:
- data partition: fstab
- metadata partition: ext4
Bug: 350101696
Test: Built zumapro target and checked mounted partitions
Flag: EXEMPT bugfix
Change-Id: I2fc82946cdbadee7af0b3f6fc026b846fa79a146
The f2fs block size has to be set up to 16384 for 16kb kernels.
Bug: 350101696
Test: Built zumapro device and checked mounted partitions
Flag: EXEMPT bugfix
Change-Id: Ie3bf17d78da62a20882b17363afeb3a3a8a984e0
The zumapro targets that only boot with 16kb kernels will
have this filesystem setup for data and metadata partitions:
- data partition: f2fs
- metadata partition: ext4
Important: For the HW file encryption to work in the data partition in 16kb kernels the `dusize_4k` parameter has to be set:
```
fileencryption=:aes-256-hctr2:inlinecrypt_optimized+wrappedkey_v0+dusize_4k
```
Bug: 350101696
Test: built pgagnostic target and checked the fs for mounted
partitions.
Flag: EXEMPT bugfix
Change-Id: I566618e6fa1db2ff4463e00e8d091e7226ba0399
Set task name and boost value for ExoPlayer:Place thread.
Bug: 357956265
Test: build pass
Flag: NONE init rc file change does not support flags
Change-Id: I09e79a16b7b6a0675de606b2f65dfbee154ec943
This variable doesn't do anything for devices launching with
API level 26 or later, and the initial zumapro devices (Pixel 9)
launched with API level 34.
Bug: 307369186
Test: presubmit
Flag: EXEMPT trivial build cleanup
Change-Id: If23568e7e1fc0dff05467e6b4fc97376c06c2233
For PDK build, the "vendor/unbundled_google" path doesn't exist.
"GoogleDialer" will be built from vendor/google_devices/zumapro/proprietary/GoogleDialer.
Flag: EXEMPT bugfix
Bug: 364510147
Test: export USES_GOOGLE_DIALER_CARRIER_SETTINGS=true; m GoogleDialer
Change-Id: I5c6796036627a5ae208dfda3ea19ead550a55c9a
