Previously, `Liboemservice_proxy` was included as a part of DMD, and so
didn't need to be included on its own. However, since these two have
been decoupled, we need to explicitly include the build target here for
it to execute on device.
Test: Build and check logs to ensure service starts up on boot
Bug: 321867236
Change-Id: I9a03a5f7dffc91e4760472a79d510e23eacca564
This reverts commit a4a92ded54.
Reason for revert: move the conditional to bcl.mk and battery_mitigation to avoide haveing 2 versions of mk.
Change-Id: I87a0c7270960ccd4e4bb01ecf58e787defcc50b9
60257881ad
Reverting to comply with the Allocator VTS for 24Q1, do not merge to main.
Bug: 310046460
Test: VtsHalGraphicsAllocatorAidl_TargetTest
Change-Id: I47f69b046c798ea15eb48debdc55c3a7273ac007
Test: Various tests are done on zuma devices given which has been in
production for a while. Tests done on zumapro devices include:
- flashed a zumapro device and observed that the device boots up
successfully.
- Checking the bugreport and didn't see anything suspicious.
- Verify that there is not any sepolicy violation related to
the multiclient HAL.
Bug: 247124878
Change-Id: Iaae483761c8163a34aaeb86651e1b9f6f51dfb5a
Put build flag conditional inside bcl-aidl.mk
to handle new battery mitigation service.
Bug: 317869347
Change-Id: Ic2d781e5afbc1994fdf1a08528f4659fff929fed
Signed-off-by: samou <samou@google.com>
Revert submission 25697219-bm_enable_build_flag
Reason for revert: DroidMonitor: Potential culprit for Bug b/317869992
- verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.
Reverted changes: /q/submissionid:25697219-bm_enable_build_flag
Change-Id: Ic2be8f44e812b0486076eb2676bb2477eb065f34
init.zuma.soc.rc and init.zumapro.soc.rc only contain SOC related settings.
init.zumapro.board.rc contain board related settings
Bug: 311016628
Test: Build image and flash on KM4
Change-Id: I8f805a58a146009f301b9cb0da9d781c0f2245d9
zumapro inherited 'skiavkthreaded' when the config was initialized from
zuma, which had RE-SkiaVk enabled at the time. RE is currently reverted
back to SkiaGL on all other Pixel devices, so switching zumapro back
to SkiaGL for parity, since it's enabled by accident.
Bug: b/301846142
Change-Id: Ib07c7c7512c0a70de8831ed8afaaa4dfcd93d594
This is to prepare dev_type test earlier. It checks whether /dev nodes
have labeles with dev_type or not.
Bug: 303367345
Test: build
Change-Id: I4feb079d4a3badc6362127a09f8d458755d7d2d2
This is for supporting Softbank requirement OTR-CORE_GEN-000305,
UE shall delete the GUTI when performing software update.
Bug: 307247050
Test: build pass
Change-Id: I4a17676abb958ff24552ffab44771f25450fb08f
It looks like this device configuration was copied before ag/22597180
was applied.
Zuma Pro counterpart for the following patch:
zuma: Bump deqp conformance level to 2023
Git hash f1c32332c3488e9c42008367e044f241f3abc8a5
Test: atest VtsGpuTests:com.android.gpu.vts.VulkanTest#checkCpuVulkanRequirements
&& atest VtsGpuTests:com.android.gpu.vts.OpenGlEsTest#checkOpenGlEsDeqpLevelIsHighEnough
Bug: 303925354
Change-Id: I709e1951b1f65a28e9bda08387924afc84c1d5b0
