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>
This reverts commit 637fc9e8d727121276cf8dea2976ac52f8da8d15.
Reason for revert: Camera EBUF overflow observed after launching GCA.
Bug: 187760882
Change-Id: I2357d943f4b4d96ffa7a156671ac7c790640a5ed
uclamp value is calculated based on the full capacity 1024. Previously
camera-daemon uses 6 which would set the min to 61. This boosts the
camera thread util up and would have power penalty. Change the value
to 1 to have minimum boost.
Bug: 186564130
Test: cat /dev/cpuctl/camera-daemon/cpu.uclamp.min & check power
Change-Id: Ib8f5ae2091848da4ee98211aeae37612ae2b308a
With recently merged kernel change pa/1916082, down rate limit will be
adjusted dynamically. Without out this change, we would run into cases
that we too little down rate limit for little.
Bug: 186392111
Bug: 170511089
Test: boot and check rate limit
Signed-off-by: Wei Wang <wvw@google.com>
Change-Id: I78d9894301c9f4f888d33010c9fcca20d51d4b20
Use the environment variable USES_GOOGLE_DIALER_PARIS to decide to
replace AOSP Dialer by Google Dialer and enable PARIS.
The variable should be set in PDK release ROM and User could set it
locally as you want the AOSP build with them.
Bug: 187242540
Test: Loacal build. Google Dialer and Paris work
Change-Id: Ib823f5447db5fd593b9044c8cdb766165ce6cedf
Bug: 187302501
Bug: 186636898
Test: boot and wifi function is ok
Test: p2p connection and throughput tests.
Change-Id: I599763e8c583f9566833183d4dbec13db1d040bc
This reverts commit 788012640b
Reason for revert: Caused throughput issue in p2p b/187302501
Bug: 187302501
Bug: 186636898
Test: boot and wifi function is ok
Test: p2p connection and throughput tests.
Change-Id: I70f4015040f10452acff697ee504b02cfb3c1e27
Test: Forrest build with the commit and the libmetrics_logger.so is
present in the build.
Bug:151063663
Change-Id: Ib5b59acfb6bc929d24884740f593417afe392434
The following interfaces are deprecated for Target FCM version 5
android.hardware.drm@1.0::ICryptoFactory/default
android.hardware.drm@1.0::IDrmFactory/default
Test: $ m check-vintf-all
The device is bootable.
Bug: 186538652
Change-Id: I0babd05f17281406af10e4ea2435aca598910d36
Move AEC and NS to the liboffloadeffect
Bug: 187153996
Test: make -j128
Test: run cts --include-filter "CtsMediaTestCases android.media.cts.AudioPreProcessingTest"
Change-Id: Ida949d8ae3c06b4ab6743159cc952cdef3a73de7
For gs101 devices, we must detect whether a wireless charger exists at
runtime, otherwise we'd need to create separate Health.cpp for each
product in order to instantiate the wireless path correctly.
Test: Ensure battery defender triggers via wireless connection.
Ensure there are no warnings for devices that do not have a wireless
charger
Bug: 165954398
Change-Id: Ibba202293141c017d3048980b643a80b5fb57ca4
We should wait for the Android SC SDK finalization.
Remove the unnecessary "BUILD_BROKEN_VENDOR_PROPERTY_NAMESPACE".
Test: Build successfully and the device is bootable
CtsOsTestCases: android.os.cts.BuildTest#testSdkInt pass
Bug: 187023500
Change-Id: Ib9adbb7a7c913790994a06ae1a57f95eebf84a78
