When a clock with seconds tick is on the display, it switches back and
forth between high and low refresh rate if the timer is <=1000ms (1s).
Set it to 1.1s which is just slightly higher to avoid this issue.
This also matches stock value.
Signed-off-by: Arijit78 <sahaarijit2007@gmail.com>
Need to explicitly set auto_latch_unsignaled property to
disabled state to keep latch-unsignaled as the default
behavior.
* Also set debug.sf.latch_unsignaled to 1
Signed-off-by: Arijit78 <sahaarijit2007@gmail.com>
When blur is enabled,
There is severe lag in; Launcher3 while scrolling apps in App drawer, Scrolling through recents and occasionally on QS pull down.
Enabling or completely removing the prop here sm6150-davinci/device_xiaomi_sm6150-common@d6233e0 doesn't seem to make an effect.
Explicitly disabling the "Enable GL comp backpressure" prop seems to slove the issue.
Lag & janks are gone now, even with blur.
Signed-off-by: Arijit78 <sahaarijit2007@gmail.com>
If the device only have 60 and 120 Hz in the config group, 60 Hz won't be
used when watching a 24 fps video and instead 120 Hz will be used because
it is perfectly divisible by 24.
This is a publicly documented AOSP behavior [1], but it simply does not
make any practical sense and trades off significant amount of power for a
very-hard-to-notice jitter-free experience.
Set debug.sf.frame_rate_multiple_threshold to 60 by default to limit this
behavior to 60 or lower fps.
Extend buffer size for offload playback to reduce the frequency of CPU
wake up.
It makes ADSP to process more data one time and reduce the number of
times to wake up CPU.
Bug: 137973303
Test: MP3 playback
Change-Id: Ib0b2a8827647ed780bb20bd9dfa2a383153eb282
Signed-off-by: justinweng <justinweng@google.com>
Signed-off-by: xNombre <kartapolska@gmail.com>
Signed-off-by: Pascoato <viniciuspascoato@gmail.com>
Signed-off-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
Signed-off-by: Arijit78 <sahaarijit2007@gmail.com>
This is required on some devices with video mode panel, since the
scheduler sets refresh rate to 120 Hz _after_ turning screen off at
60 Hz (VRR idle) but the HWC ignores this and when the display is
turned back on SF thinks we are back at 120 Hz while HWC is still
rendering at 60 Hz. Defer setting refresh rate until the screen is
turned back on, to avoid this confusion.
The health AIDL HAL service provides functionalities of charger,
therefore system charger at /system/bin/charger is deprecated.
On top of that, QTI health AIDL HAL service enables suspend by
default, the equivalent of setting ro.charger.enable_suspend
for legacy charger.
