* so this isnt being done for the intended reason this is being done to
make sure a rr switch happens when we unlock, sometimes when the device
wakes up its stuck at 30fps and isnt fixed till a rr change happens
this is basically a way to force it to happen
Signed-off-by: Arijit78 <sahaarijit2007@gmail.com>
By putting them on the bigger cores, they can be processed quicker,
resulting in improved responsiveness.
Signed-off-by: Arijit78 <sahaarijit2007@gmail.com>
log spam goes brrrt
W libperfmgr: Failed to write to node: /dev/cpuctl/foreground/cpu.uclamp.min with value: 159, fd: 8
W libperfmgr: Failed to write to node: /dev/cpuctl/top-app/cpu.uclamp.min with value: 692, fd: 9
Signed-off-by: Arijit78 <sahaarijit2007@gmail.com>
These are critical for display performance and should not be balanced
in order to improve latency and responsiveness.
Signed-off-by: Arijit78 <sahaarijit2007@gmail.com>
Since Ext4 doesn't implement "-o sync", it commits metadata at every 5 secs.
This may cause /metadata corruption.
Bug: 162883014
Signed-off-by: Arijit78 <sahaarijit2007@gmail.com>
W libperfmgr: Failed to write to node: /proc/sys/kernel/sched_prefer_spread with value: 0, fd: -1
W libperfmgr: Failed to write to node: /proc/sys/kernel/sched_busy_hyst_ns with value: 3000000, fd: -1
W libperfmgr: Failed to write to node: /proc/sys/kernel/sched_busy_hysteresis_enable_cpus with value: 15, fd: -1
W libperfmgr: Failed to write to node: /proc/sys/kernel/sched_min_task_util_for_boost with value: 51, fd: -1
W libperfmgr: Failed to write to node: /proc/sys/kernel/sched_min_task_util_for_colocation with value: 35, fd: -1
Signed-off-by: Arijit78 <sahaarijit2007@gmail.com>
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>
- This flag turns off GPU/CPU intensive UI effects and
reduces the RAM footprint.
- Using this is a better compromise than the 'low_ram' flag
as this does not disable features in the rom but still
reduces RAM usage and gives better smoothness in the UI.
Signed-off-by: Arijit78 <sahaarijit2007@gmail.com>
