This reverts commit 4a1f9459e5.
The Chrome issue has been fixed upstread and this workaround is no
longer needed; in fact, it triggers another issue where conflicting MTE
mode settings make newer Chrome versions crash at startup.
Bug: 297266100
Bug: 305005339
Bug: https://crbug.com/1515053
Test: chrome still does not crash; debuggerd shows MTE is enabled (grep
for TCF_MTE)
Change-Id: Iee2b704c4ea39b5809193c1ceed3b8f41618dd40
The state count requirement is very specific to the case where the
signal integrity is the culprit of flaky connection. However,
there could be other cases such as bad receptacles causing data pins
to disconnect randomly.
Remove the state count requirement to cover more cases.
Bug: 296119135
Test: manually trigger the warnings
Change-Id: Ic2ae376ad6062d9930614381503f44e4a5ac760f
(cherry picked from commit 5e14ba01be9acc31d3df0f506b4287eea0bf9583)
Support flagging enum failure and flaky connection in device mode,
flagging enum failure and missing data lines in host mode.
No warning would be flagged until 5 secs after the data session
starts to give ample time for the connection to stabilize, a timer
is added to support it.
Bug: 296119135
Test: manually trigger the warnings
Change-Id: I25f08657e328913946add192b5ecb9ee50c3a1a8
(cherry picked from commit 42020dc4585442bd7ca88f183ba29a18834af197)
am skip reason: Merged-In If106f81c0dd2bd81a48e156e1cc75dba4a885aca with SHA-1 dc330b5e88 is already in history
Original change: https://googleplex-android-review.googlesource.com/c/device/google/zuma/+/25704537
Change-Id: Icaf771cd1500a31df49dd844132f1f23687d77d1
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I688f2559698c7553a7f585cab2693d09d70731f4 with SHA-1 f08b6e4d84 is already in history
Original change: https://googleplex-android-review.googlesource.com/c/device/google/zuma/+/25689420
Change-Id: I9727815f1b677fb77c0403c4b0e35bd66dd994fe
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
Since LMKD introduced aggressive kill for cached apps, we can change the
swap_free_low_percentage back to 10.
Bug: 300660611
Change-Id: I688f2559698c7553a7f585cab2693d09d70731f4
Merged-In: I688f2559698c7553a7f585cab2693d09d70731f4
Signed-off-by: Minchan Kim <minchan@google.com>
ACPM has an issue b/315079424 that reports incorrect TPU DVFS
residency. So change the data source from ACPM to TPU kernel.
Bug: 310094590
Test: vts-tradefed run vts -m VtsHalPowerStatsTargetTest
Change-Id: If4bdaeea510b1a8e72d057a7fbb0dc03f6a6c665
Signed-off-by: Darren Hsu <darrenhsu@google.com>
After USB enumeration, some SD card readers do not send signals to the
device when the SD card is inserted or removed.
To support SD card hotplugging, this patch enables in-kernel
media-presence polling, which will check the SD card status every 2
seconds after a SD card reader is attached.
Bug: 186479576
Test: SD card insertion/removal and data copy (see b/301566595)
Change-Id: I044aeffd9386c0bee6138402e5130c39e1adbc9f
Signed-off-by: Kuen-Han Tsai <khtsai@google.com>
am skip reason: Merged-In I12add8918fb1922029cbbee130be33a3a36e44a4 with SHA-1 8dadca19cf is already in history
Original change: https://android-review.googlesource.com/c/device/google/zuma/+/2866342
Change-Id: I8535f81cadead59df772a39ca12c7e67c321b5bb
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
On port-partner remove, write to drm's usbc_cable_disconnect
node if setupDisplayPortPoll() had run previously in the
connection, flagged by mPartnerSupportsDisplayPort.
Test: manual test on device
Bug: 303820069
Change-Id: I3478f2f027540972647044716a1a3e832ae1b152
Signed-off-by: RD Babiera <rdbabiera@google.com>
am skip reason: Merged-In I12add8918fb1922029cbbee130be33a3a36e44a4 with SHA-1 8dadca19cf is already in history
Original change: https://android-review.googlesource.com/c/device/google/zuma/+/2866342
Change-Id: Ib0634058959d578b4362dc2740c6532e55b39f6f
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I12add8918fb1922029cbbee130be33a3a36e44a4 with SHA-1 8dadca19cf is already in history
Original change: https://android-review.googlesource.com/c/device/google/zuma/+/2866342
Change-Id: I7554252880002165eead6431b0b4ef12c2ee9756
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
The versions were originally not specified in the device manifest and
compatibility matrices. This is changed here to fix the broken vts
tests.
Bug: 310109332
Test: atest vts_treble_vintf_vendor_test -- --abi arm64-v8a
Change-Id: I58653ed6f284b091995c93e9bf44a65023f380db
am skip reason: skipped by user willmcvicker
Original change: https://android-review.googlesource.com/c/device/google/zuma/+/2795415
Change-Id: I3b5dcd4e5723fa87ed648d772fa0879ae1d6ef1d
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: skipped by user willmcvicker
Original change: https://android-review.googlesource.com/c/device/google/zuma/+/2795415
Change-Id: I2715ce19c1eec0768919fe8362ad4e6a85a77869
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: skipped by user willmcvicker
Original change: https://android-review.googlesource.com/c/device/google/zuma/+/2795415
Change-Id: I07980e0ed1770697e0ed10aeb35978a8136bb8a2
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
