Disable SKIN thermal throttling to avoid any side effect until we
receive the device which has the normal HW thermal solution.
Because the Tj thermal throttling is still workable, so there should be
no overheating risk.
Bug: 221077673
Test: no thermalHAL crash found
Change-Id: I88c23527b5add9e6b07a2ea4ab824ea4f699261c
Disable the powerhint for F2FS gc_urgent mode, since we are going to
replace this with the smart idle maintenance service.
Test: turn on/off the screen & check /sys/fs/f2fs/dm-*/gc_urgent
Bug: 214430685
Signed-off-by: Daeho Jeong <daehojeong@google.com>
Change-Id: I9774ae52765527f77f9c78af75fd6e29cd4ea572
We already have the settings for Wireless charger HAL for gs201
Test: m check-vintf-all
run vts -m vts_treble_vintf_vendor_test
Bug: 207076973
Change-Id: I74abd1de7004edce3e711d60b87f8849839f35e4
P21 has been using GPU power hold during app launch to mitigate jank
from GPU power on latency.
However this same mechanism seems causing instability (may be related
to the new inter-frame power optimization). While the root cause is
being investigated, disable the boost.
Bug: 223828284
Test: Build
Signed-off-by: Wei Wang <wvw@google.com>
Change-Id: Id04a1d09ebd5b36c1c7c55824da34bffb6435cab
based on pipit 93e38fbd070b55875d9c23e214dff6d26ac0cdf9
based on cheetah cdc1dc5379faf6bb60cf4f8b4b967ae87992b2ed
Bug: 206057564
Change-Id: I68ca7715cf7fd96066d8d517bc4daf236512f501
Fork the powerhint.json from gs201 and align the config with cheetah
Bug: 207573241
Test: build and boot pass
Change-Id: I6d3ad4661a030464d33b706d8eb7f67c5e8fd835
The calibration script will be copied higher level device uwb.mk
Bug: 219611318
Test: builds
Signed-off-by: Victor Liu <victorliu@google.com>
Change-Id: I62bc262603f8b5b58d9e3b1c92dc9b62789d82b2
Use device specific script to select which factory calibration
values to use.
Bug: 218719905
Test: build
Signed-off-by: Victor Liu <victorliu@google.com>
Change-Id: I1750cb6c17de69dc3a86ce01fa1e023194591358
This CL updates resource overlay of
rounded_corner_content_padding
so that the same device-specific value can be seen from both the
Framework code and the SysUI.
With my previous CL [1], the SysUI continues to see the same value
even after this migration.
[1]: I0c3717c0bdfc928167c6eba06247b37caabf33b9
24d6b891f572f7be419d3acc9793ca68d062cf35
Bug: 215554582
Test: presubmit
Change-Id: I7564a8d3f587ce735b74fbda6b4ea066f266d486
based on pipit 68a0b4b411e8d23dfd966d24a5c35ea4ffb9d5f1
and cheetah 9acaa7507c23ffc7ca5f82a9579dd3a7c56af809
Bug: 206057564
Change-Id: Id59ed48d2a39c9a5a811c41157732914f3568d51
