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.gs101
Flag: EXEMPT, refactor to fix build failure
Change-Id: Ia66a69a9375971223b712d695f5ea5f2c1e26c19
am skip reason: Merged-In Ibf7dda6c4c13d6513e2f08239c95c6b2778a98ec with SHA-1 ebddc4ff3f is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/3258552
Change-Id: I1b246ca1c53bc974ad957bc388a1934bc6a6ad3d
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I91df897d8ae7d8e4b1b49a7eb20f6bb5fe99755c with SHA-1 855cd95dce is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101-sepolicy/+/3257961
Change-Id: I6a625d82b030104366c2380f2d8b3b2726976bb8
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I91df897d8ae7d8e4b1b49a7eb20f6bb5fe99755c with SHA-1 855cd95dce is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101-sepolicy/+/3257961
Change-Id: I76119471c70db0083446d9a9b0d8bd59ff1a400d
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Ibf7dda6c4c13d6513e2f08239c95c6b2778a98ec with SHA-1 ebddc4ff3f is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/3258552
Change-Id: I4d1500a8ac8dc543fade1661c965bde24f52d6a4
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
This variable doesn't do anything for devices launching with
API level 26 or later, and the initial gs101 devices (Pixel 6)
launched with API level 31.
Bug: 307369186
Test: presubmit
Flag: EXEMPT trivial build cleanup
Change-Id: I3e3ef17f4a1d7101bbfdeb47c3072d0ede4af6e9
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: I9433d73e7ed4bfd5e72a0f8318e959373e76202e
Signed-off-by: Ocean Chen <oceanchen@google.com>
system/core/init/init.cpp SetUsbController picks the first udc device if
there're multiple udc devices present on the system to populate
sys.usb.controller system property.
CONFIG_USB_DUMMY_HCD enabled in kernel-5.10 GKI would introduce a
dummy udc device named "dummy_udc.0". Depends on timing, the dummy
device might be picked up by the init process and incorrectly populate
sys.usb.controller.
This issue only applies to devices on kernel-5.10 GKI, the WAR is to
overwrite the sysprop if it's incorrectly populated by the dummy udc.
Bug: 333778731
Test: tested on Cheetah
Flag: EXEMPT bugfix
Change-Id: Idefd1a5d8154a51792c6cb52ee6d11cbb7f6df78
This reverts commit c5b3375835.
Reason for revert: It's not need anymore for kunit testing
Change-Id: I8606bfb3cc375e97d78ff52cd4fe8b596c86d6fd
Bug: 337797668
Revert submission 28762313
Reason for revert: Droidmonitor created revert due to b/360059249.
Reverted changes: /q/submissionid:28762313
Change-Id: I4ffb476a64b32a4e725c894f8014070121848cc0
