Cherry-picked from http://ag/25163335.
Trigger fsck on mount of /data if the value of ro.preventative_fsck is
not equal to the contents of /metadata/vold/preventative_fsck, then set
the file to the property to prevent future runs
See b/305658663 for context
Bug: 305658663
Test: Make sure fsck run after first boot and not after second
Change-Id: I1263d2d55fe22d994ae8c8654b1e75ad9e4ddafe
Change-Id: Ie6b9fc94752d91e77e8fc48979216917c1fd9ec3
Merged-In: Ie6b9fc94752d91e77e8fc48979216917c1fd9ec3
Signed-off-by: Jaegeuk Kim <jaegeuk@google.com>
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
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
The original performance number may not able to meet from CTS since
cpu scheduling is changed in P23 for power saving. We align hevc/h264
encoder lower bound performance as P22's result to get the stable test
result for CTS.
Bug: 291689152
Test: run cts -m CtsVideoTestCases -t android.video.cts.VideoEncoderDecoderTest
Change-Id: I17a7f832c421d873a68a87eea0131d141afdc108
* changes:
zuma: use android.hardware.boot aidl interface
zuma: update manifest HAL android.hardware.boot from hidl 1.2 to aidl
zuma:interfaces:boot: add aidl interface support
bootctrl aidl interface is based on hidl 1.2 interface implementation
code and migrate to aidl interface
Bug: 282670401
Test:
- boot to home
- OTA successfully in Recovery mode
- OTA successfully in OS mode
Change-Id: I5221ddc997d06dc24e46816885d617f4cf193502
Signed-off-by: Jason Chiu <jasoncschiu@google.com>
Compile ArmNN shim over the support library.
Remove SELinux permissions and settings for the old HIDL backend.
The AIDL settings will be in the gs-common folder.
Test: Local run of CtsNNAPITestCases
Test: Local run of VtsHalNeuralnetworksTargetTest
Test: Local run of MLTS Benchmark
Bug: 283724775
Merged-In: I57f807934ca219460a4e589b899f933115718a70
Change-Id: Ica6a25f270a499670f23ba5452903c4904f37d48
We advertise 4k@120 for meet Performance class U requirements.
However, to compliant with performance class T requirements,
We need advertise at least performace point to 180 FPS for 1080p resolution.
Bug: 290220438
Test: run cts -m CtsMediaMiscTestCases
Test: run cts -m CtsMediaPerformanceClassTestCases
Change-Id: I1eeee5f166ecc4f4416777b321a3d74d651029f2
Restore uclamp_min and use preferred_idle_mask and group util to
optimize about 200ms boot time performance.
Bug: 284039815
Test: pts-tradefed run singleCommand pts -m PtsPerformanceTestCases -t com.google.android.perf.pts.BootPerformanceTest
Change-Id: I3a77fb0270c1afdc3983710c90a4369a813c7f2c
- set lmkd's swap_free_low_percentage to 100
- decrease swappiness to 60
Test: boots with correct settings
Bug: 288432219
Change-Id: Ie9fc39b03b25ee231190e12e312485794d0f8686
