The UVC gadget requires some setup in configfs before it can be used by
the gadget HAL. This CL adds that setup to usb specific init.rc file.
Currently, UVC is setup to advertise mjpeg streams at 720p and 1080p.
Bug: 242344221
Test: Manually tested that UVC is correctly set up on boot.
Merged-In: I71cf4727fb23744c5aef368c1750784a19ba8c5d
Change-Id: I71cf4727fb23744c5aef368c1750784a19ba8c5d
Signed-off-by: Jayant Chowdhary <jchowdhary@google.com>
UVC is a new USB function supported in Android. This CL adds UVC as a
valid function and gives it a new pid of 0x4ee[de]. UVC function is
guarded by the property `ro.usb.uvc.enabled`. When this property is set
to false, UVC won't be considered as a valid gadget function.
Bug: 242344221
Test: Manually tested that the UVC function is successfully configured
Merged-In: I5c2040a84ee8360b16c955403478d908fe109121
Change-Id: I5c2040a84ee8360b16c955403478d908fe109121
Signed-off-by: Jayant Chowdhary <jchowdhary@google.com>
Populates AltModeData within PortStatus with DisplayPort
Alt Mode statuses for pin assignment, hpd, link training
status, and port partner capability.
Test: manual test on device
Bug: 277466852
Change-Id: I52a56f7090ed6dbef6211f19d6350cecac58e4fa
Merged-In: I52a56f7090ed6dbef6211f19d6350cecac58e4fa
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
(cherry picked from commit 4c559d3334)
This is a no-op in regular builds. Impact is limited to a testing-only
_fullmte build.
Bug: 297266100
Test: chrome does not crash
Change-Id: Iba9b031fa9d2df0c093f0465ae2dd8e1b36133b9
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
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)
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
