There are power regression reports for low activity use cases on mids
and bigs. Disable util-awareness on mids and bigs for now until this is
better investigated and either use a slightly higher threshold or fix
any potential root cause that is causing unnecessary higher activities
on these cores.
Bug: 289293494
Signed-off-by: Qais Yousef <qyousef@google.com>
Change-Id: I7ab2dca998c749567c5e1908d57b2174313e8390
RCS has a low priority and will not be used in the future, remove it from the system image.
Bug: 295403727
Test: Make sure the TestRcsApp is removed from the system image.
Change-Id: I3a8f1f2363bb36418ea12ace6ee145e8114ae51c
am skip reason: Merged-In I429e01b68fa4a22473c0b57dbf63ee6f579c5f18 with SHA-1 4d8bc4d744 is already in history
Original change: https://googleplex-android-review.googlesource.com/c/device/google/zuma/+/24349103
Change-Id: Ic183b4bfc8a44f912c1626fff5105a20f77aff4a
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
Poll the sysfs attributes that represents usb device state in
either of the following states: not attached, powered, default,
addressed, configured.
The information is useful in detecting non compliant USB cable,
which will be supported in later patch sets. This patch lays
the ground work to monitor the sysfs attributes in both device
and host modes.
The thread to poll uevent is re-used to poll sysfs because this
serialize type-C port events and usb device state changes, hence
prevent potential races.
Added a thin abstration layer and a map to keep epoll data so
that it's easier to dynamically add/delete files to epoll, which
is needed for usb devices in host mode.
Bug: 285199434
Test: trigger usb device state changes in device and host mode
Change-Id: Ie5389d051deb28dbb486c2f27319b3cc9e89312f
am skip reason: Merged-In I3eb3f880671bea091ff6c798d8def2f559a5e291 with SHA-1 5d8da452cb is already in history
Original change: https://googleplex-android-review.googlesource.com/c/device/google/zuma/+/24325829
Change-Id: I64e706308a6129b6a7e61658e7719c65cce3378f
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In I3eb3f880671bea091ff6c798d8def2f559a5e291 with SHA-1 5d8da452cb is already in history
Original change: https://googleplex-android-review.googlesource.com/c/device/google/zuma/+/24325829
Change-Id: I6215c0283fcba595ff1b96716f6c68113ff90c66
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
Discontinue maintenance and active support of ArmNN on Pixel phones.
Bug: 294459623
Test: Local nnapi_info
Merged-In: I3eb3f880671bea091ff6c798d8def2f559a5e291
Change-Id: Ib6140584a724b5e1fd3634e414773092da49b41a
Bug: 279486693
Test: Verified the existence of atom and correctness of atom stats
adb shell
cmd stats print-logs && logcat -b all | grep -i 105043
Merged-In: I429e01b68fa4a22473c0b57dbf63ee6f579c5f18
Change-Id: I429e01b68fa4a22473c0b57dbf63ee6f579c5f18
Signed-off-by: Ziyi Cui <ziyic@google.com>
(cherry picked from commit 4d8bc4d744)
Bug: 279486693
Test: Verified the existence of atom and correctness of atom stats
adb shell
cmd stats print-logs && logcat -b all | grep -i 105043
Change-Id: I429e01b68fa4a22473c0b57dbf63ee6f579c5f18
Signed-off-by: Ziyi Cui <ziyic@google.com>
Discontinue maintenance and active support of ArmNN on Pixel phones.
Bug: 294459623
Test: Local nnapi_info
Test: Presubmit
Change-Id: I3eb3f880671bea091ff6c798d8def2f559a5e291
The change disables the dumpstate strict-run flag, which is enabled by default. Disabling this flag increases the timeout for capturing incident report to 120 seconds, from the default 20 seconds. This is done because 20s isn't enough to capture incident report proto in some cases, especially when device is throttling.
Bug: 283326935
Test: Booted both P23 devices along with other strict_run changes. Then manually thermal throttled the devices and captured bugreports. In some tests Incident report took lot more than 20s, and in all these cases it was succesfully captured.
Change-Id: Ie6e688ed7fb0218c1ace70d623f98378c7e6c1de
In the 'next' release configuration, we don't allow using unfrozen
versions of interfaces, so the previous version is served instead.
Once this interface is frozen, this previous version can be removed from
the FCM.
Test: lunch cheetah-next-userdebug && m
Bug: 290265210
Bug: 294130026
Change-Id: I662355264e4901f2f99bc0635779ab9b2f9756b9
In the 'next' release configuration, we don't allow using unfrozen
versions of interfaces, so the previous version is served instead.
Once this interface is frozen, this previous version can be removed from
the FCM.
Test: lunch cheetah-next-userdebug && m
Bug: 290265210
Bug: 294127698
Change-Id: Ia9f93c9235fea89eafa66c6b11aeac5497e483bf
