During streaming high fps mode, the BW is high and lead to CPU memory
high latency. This hint tries to avoid raising the CPU clock
at the condition when CPU is waiting for data access.
Bug: 184583714
Test:
4k60: 59+fps
1080p60fps: 58fps (b/186806120, disable eis can get 60fps)
Power benefit 80-100mW
Signed-off-by: Peter Liu <pingchienliu@google.com>
Change-Id: I3849dfd170085f7e10b5c53d27af353026a4093a
edgetpu_service was splitted into two in previous change:
edgetpu_service and edgetpu_vendor_service, where the new
vendor service for vendor clients, and the old service keeps
serving app clients.
This change renamed the edgetpu_service into edgetpu_app_service
in the device.mk to make the naming clearer.
Bug: 188463446
Test: Oriole + GCA
Change-Id: I969e264a82a4ebc77407a0eee45fe6be6a3a2ba8
Bug: 188110823
Test: Ensure that Dwell-Defend can trigger with 'setprop
vendor.battery.defender.threshold 61'
Change-Id: I4782e2c387b147fc48cf4134d27af8675964dc44
Bug: 187248983
Test: lshal debug android.hardware.sensors@2.0::ISensors/default
See b/187248983#comment2 for the output.
Signed-off-by: Rick Chen <rickctchen@google.com>
Change-Id: I174af99b6f1318c7420e8e6c5d4ed745c2328cf0
set 2 to prevent limit battery level in unexpected testing situation
Bug: 180511460
Signed-off-by: Jenny Ho <hsiufangho@google.com>
Change-Id: I9f0e66cf92b26c6946af162003378dcf0fd749f9
This changes PowerHAL to use a sysfs node created
specifically for use by PowerHAL when influencing
GPU clocks.
Bug: 188404581
Bug: 188034128
Signed-off-by: Sidath Senanayake <sidaths@google.com>
Change-Id: Icf120454ff908776c8717826689a0528aebf2f64
Only dump the latest dump files so that bugreport
size won't be increased by too much.
Test: build and capture bugreport
Bug: 178737594
Change-Id: I699ee76997c9107dad13419688f3c6c04551313b
SystemUI should always be speed-preopted on these devices.
Test: flashed, SysUI is preopted
Bug: 188465988
Change-Id: I990ce9d7d8c08b8e80fe4ca0b73c9eb339f065f3
Enable Page Pinner.
Bug: 187552095
Test: adb bugreport <zip> and confirmed it contains page_pinner
information at dumpstate_board.txt
Signed-off-by: Minchan Kim <minchan@google.com>
Change-Id: I509c5a825a798d8f1851cb65c5dd28dbddf11d33
Update manifest_64.xml for the following changes that were made to
manifest.xml:
I0babd05f17281406af10e4ea2435aca598910d36 Remove android.hardware.drm@1.0 HAL services
Iaafd526fc5a601f7e8189ec764399d99c660beb0 Replace the HIDL with AIDL for "android.hardware.memtrack"
I3f0d35647c0748d360b12d3be078d514f99d23d5 Update dumpstate HAL to V1.1
I9ba18473132f4bfa37a9fe2bbae4bb3dc015cc0e gs101: Remove sensor HAL 1.0 config
Bug: 188239794
Test: m out/target/product/oriole/obj/PACKAGING/check_vintf_all_intermediates/check_vintf_compatible.log
Change-Id: I92c313f7f31df7193ca8c67f56cd9f1317290948
Use bugreport flag to keep waking up the touch driver instead of
force active flag to prevent the kernel driver from blocking CPU
enter the suspend mode.
Bug: 183466375
Test: touch driver won't block system suspend.
Signed-off-by: davidycchen <davidycchen@google.com>
Change-Id: I586173485bd41deac891b7edb366b51a99977434
This hint is set to indicate that the framework is likely to provide
a new frame soon. Therefore HWC has additional time to exit power
collapse. Set display_update_imminent_timeout_ms align to DPU
hibernation timeout.
Bug: 164411401
Test: systrace, testLayoutCacheLowHitrateFling
Change-Id: Idac388ac8700ed92e9620445a5038af54683df53
Bug: 188078957
Test: Verified using temporary log messages to confirm
file paths are formed correctly as otherwise to test queryMoistureDetectionStatus()
requires some mock circuits.
Signed-off-by: Manish Varma <varmam@google.com>
Change-Id: If5402d5999c77bf5a3431c70d800e50570b87c88
Bug: 187237947
Test: Verified basic sensor sampling function.
run atest VtsHalSensorsV2_1TargetTest and result is passed.
Signed-off-by: Rick Chen <rickctchen@google.com>
Change-Id: If081e8afbfb71b5f9276c5ef023a41e7b8590419
GCH toggle was modified from disable_lazy_hal to use_lazy_hal,
so the explicit assignment is no longer needed - the camera HAL
is eager by default.
Bug: 186175754
Test: build, camera preview
Change-Id: I5e4bede5083c5b0793f1b816a10ba9ae1d7bafc2
To prevent early presentation, SF does not allow to skip validate
if it is called more than one vsync period before the target present
time (ag/14508376). If we wake up SF too early, then skip validate
would be disabled and we would end up with 2 binder calls to composer
(validate + present) instead of just one (presentOrValidate)
Change-Id: I0ff779db088b27a9bf18e4ede459fca722eb944c
Test: run bouncy ball and collect systraces
Bug: 161945010
Bug: 187871031
Since cfs_rq clamp feature uses tg's value, align it with the
vendor_group setting.
Bug: 170508405
Test: build pass
Signed-off-by: Wei Wang <wvw@google.com>
Change-Id: Ie0c896de2022f435be5ea53ae3cecf5d80d2c067
This is to avoid camera crash on factory builds.
Because disabling LTM could improve camera stability before, we can consider disable it again for factory builds once b/187900993 is clarified.
Test: build pass, capture/recording with Octopus
Bug: 187900993
Change-Id: I00407aa6c7da8b54b009b11c897689e7e003fc2d
1) Enable prefer_high_cap of camera vendor group
2) Set high_capacity_start_cpu to 4
3) Set prefer_idle of camera vendor group to 0
4) Set MemFreq floor
5) Change camera-daemon/cpu.uclamp.latency_sensitive owner to root
Bug: 186564130
Test: Boot & check setting values
Change-Id: Ief0cae2aa9e4f84bed93f7de0bfb765e8a27009b
With vendor kernel support of getting rq cfs util in group base,
we could limit uclamp.max of background group to get more power benefit.
Bug: 170508405
Test: build pass
Change-Id: I997e653eb2790f5e3be4fbf3c8b1de356d787377
Right now we have many groups due to uclamp setup, and this would
potentially create interesting fairness between groups.
Ultimately we want only a system group and a background group for
cpu.shares, which would achieve after b/182509410 resolved.
Test: boot and check setting
Bug: 171740453
Change-Id: I8fa23268aa7ed02dcccc527abcec8556009aa9a7
Follow the previous Pixel settings, add a product FCM to describe the
requirements of device-specific HALs.
TO-DO: (1) Check if we need to replace the product config with
Android.bp module like ag/14052744
(2) Check if we need to split the FCM for system_ext/product
Test: m check-vintf-all
The device is bootable.
Bug: 184714406
Change-Id: Icacace16863cfe1415e3dc4454e8763b8a30b425
PRODUCT_SHIPPING_API_LEVEL is 30 (Rvc) now.
Upgrade the Target FCM version to match the shipping api level.
TO-DO: Upgrade PRODUCT_SHIPPING_API_LEVEL to 31
Upgrade the Target FCM version to 6
Test: $ m check-vintf-all
The device is bootable.
Bug: 184714406
Change-Id: I72c7f490e9cb38d94f98071b302a4f465bf3281b
This changes the owner of specific logbuffer device node
dev/logbuffer_btlpm and dev/logbuffer_tty16 to Bluetooth,
so Bluetooth HAL is able to access them in userdebug rom
Bug: 177794127
Test: Manually Test
Change-Id: I17db3e3b8df521946d4358d191695c09ac2c2c3a
Set ro.audio.offload_wakelock to false to release the wakelock in
AudioFlinger so that the CPU is allowed to sleep to save power during
oflload playback.
Bug: 178789331
Test: build pass
Change-Id: I9cc3fe6db17060c7de2b2df8a49befdbe2aecf29
Signed-off-by: JJ Lee <leejj@google.com>
