We're going to transition to using the kernel copy, not the HLOS copy.
Bug: 369686096
Test: build, flash, check /vendor_dlkm/etc/ (may or may not exist,
depending on kernel contents)
Flag: build.RELEASE_KERNEL_BLUEJAY_DIR
Flag: build.RELEASE_KERNEL_ORIOLE_DIR
Flag: build.RELEASE_KERNEL_RAVEN_DIR
Change-Id: I40649b59dc0e18e5a9dc160e58815929a7150226
Bug: 271887637
Test: Built and flashed on local device
Flag: build.RELEASE_SYSTEMUI_USE_SPEED_PROFILE
Change-Id: Idafe8f8e72a7b50bd3d0baea8b736dd853943a09
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
Change-Id: I77ae2cbd9fbe09e60db3ee89fc33f32cecb8bab6
Bug: 347122505
Test: check the priority and latency of input thread in Perffeto
Flag: NONE early device setting updates
Change-Id: I0c0a39e3fc03d8df4e9e87cf61fb8e1dafcfc996
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 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
vendor_boot.img is no longer built on 6.1 kernel codebase hence
vendor_boot.modules.load no longer exists. We can use modules.load
instead which is same as vendor_boot.modules.load but always exist.
Flag: EXEMPT build file update
Bug: 343042291
Test: build oriole-zvs1-userdebug
build oriole-trunk_pixel_kernel_61-userdebug
Change-Id: I7e5028ca4cc710367ddc5b161e006b8e7c25de80
Set the variable is true when USE_LASSEN_OEMHOOK is true and
BOARD_WITHOUT_RADIO is not true.
Flag: EXEMPT bugfix
Bug: 325857852
Test: m ConnectivityMonitor
Change-Id: I84e50ffeeec8aea8131cca07827324a2980ed9de
Pixel removed unnecessary allocation padding, and we now pass
dEQP with a maximum physical core index setting of 4, which allows
the driver to utilize 4 GPU cores (1111b) in the extreme tests.
Bug: 221255664
Test: O6 atest CtsDeqpTestCases -- --module-arg 'CtsDeqpTestCases:include-filter:dEQP-VK.protected_memory.*'
Flag: EXEMPT bugfix
Change-Id: I9de8d05f9de50c034ef20690a53705fe208fb47f
Remove irrelevant copy and paste content. None of the gs101
devices ever included these services and these sockets are
not doing anything.
Bug: 234559097
Test: presubmit
Flag: EXEMPT dead code removal
Change-Id: I6fdab1e2232f83c0286d5f33773aaa17f9da3f7a
am skip reason: Merged-In Iad74cae0d6ad6887d79d705dc8478f1b44532503 with SHA-1 2e1fd91321 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/3165100
Change-Id: I303e3e12e90bb1336a4fda4e76fbedae1f15d06e
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
