Flag: EXEMPT gated by overlay
Bug: 373594936
Test: Manuel test, trigger SSR and won't create bugreport automatically
Change-Id: I3b236cee06bd792355551c21cf888261bedbfa95
Preparing for deviation of gs101 UMD from other devices.
This change has no on-device functional behavior impact. The change only picks
the UMD source from a new location, the actual driver should be the same
as earlier.
Flag: EXEMPT for switching where the UMD source is picked up.
Bug: 360830887
Test: Local build
Change-Id: I033c7553c94bed67fa6b6fc2d407b48e8b6d1a3e
LDAF sensor device filename changed after kernel upgrade
from v5.10 to v6.1 in some of our in-market devices.
We need to update the device filename to access the LDAF
with this new kernel version.
Bug: 378045567
Test: Open camera, and observe available LDAF sensor in logs
Flag: EXEMPT bugfix
Change-Id: I4bed0358263910d1312238a8e109afb75517d8c2
Revert submission 30066446-goodix-ext-service-aidl
Reason for revert: Droidmonitor created revert due to b/376465180. Will be verifying through ABTD before submission.
Reverted changes: /q/submissionid:30066446-goodix-ext-service-aidl
Change-Id: I720eb17fbdf9961ba5505ef83e2b5b53f95e9639
Set the full module path of libacryl_hdr_plugin and the include dir for
lobacryl conversion to soong. It will take effect after aosp/3286932 and
aosp/3287183 merged.
Bug: 370414334
Test: lunch aosp_riole-trunk_staging-userdebug ; m libacryl_hdr_plugin libacryl
Change-Id: I67339b5420d523d9a61e0457d77a1412ae6b3582
Disable cgroup kernel memory accounting to avoid unnecessary overhead
similar change ag/22891292 but now back-port to gs101
Flag: NONE kernel config
Bug: 373232814
Test: pts-tradefed run commandAndExit pts -m PtsPerfWbsTestCases
-t com.google.android.perfwbs.pts.KernelModuleTest
and alternative tests on forrest.
Change-Id: I4ab5d20a2d74c023c6fca26b32c8acc67fcd2582
Signed-off-by: Robin Hsu <robinhsu@google.com>
This patch prevents a Null Pointer Exception in
queryMoistureDetectionStatus() when getPortStatusHelper() fails to open
the /sys/class/typec file. The failure results in an empty
currentPortStatus vector, causing the NPE when accessing its first
element.
Bug: 361097811
Flag: EXEMPT bugfix
Test: NPE does not occur when getPortStatusHelper() fails
Change-Id: Id6886283d6f2f9179b3a9c5d535646874e9f277b
Signed-off-by: Kuen-Han Tsai <khtsai@google.com>
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
