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>
* Extra padding for front facing camera cutout when camera is in use
* Remove flares on high brightness while using front camera
Change-Id: I68acb0deecbecd916be90de0a9043ea4703553df
Signed-off-by: Arijit78 <sahaarijit2007@gmail.com>
This not only saves a lot of build time when building with
TARGET_USERIMAGES_SPARSE_EXT_DISABLED and/or
TARGET_USERIMAGES_SPARSE_F2FS_DISABLED which is required
on A14, but also removes the need for the build system to
temporarily create a 40+GB userdata image.
Which means that less free space is required to start the
build.
Change-Id: Ibf48e7cdf566a4653e85352a79170b354d917234
Signed-off-by: Arijit78 <sahaarijit2007@gmail.com>
No longer needed now init listens for property changes on a
separate thread.
Bug: 186580823
Test: Cuttlefish boots successfully
Change-Id: Ief3a546d2154231d18957c2f703bd128966d7288
Signed-off-by: Arijit78 <sahaarijit2007@gmail.com>
Unable to determine UFFD GC flag for kernel version "5.4.268-qgki".
You can fix this by explicitly setting PRODUCT_ENABLE_UFFD_GC to "true" or
"false" based on the kernel version.
1. Set PRODUCT_ENABLE_UFFD_GC to "true" if the kernel supports userfaultfd(2)
and MREMAP_DONTUNMAP.
2. Set PRODUCT_ENABLE_UFFD_GC to "false" otherwise.
Change-Id: Ie77d9a86a7fe94e4cade1868ffea27194f724e03
Signed-off-by: Arijit78 <sahaarijit2007@gmail.com>
* It is started in the on init phase in /system/etc/init/hw/init.rc
Change-Id: Ie10e1d4c520329a76627a965ca139f9ad0f71875
Signed-off-by: Arijit78 <sahaarijit2007@gmail.com>
As one can see in cfq_arm_slice_timer(), the CFQ I/O scheduler supports
two parameters that can make it delay I/O: group_idle and slice_idle.
Restore I/O performance by setting both the group_idle and slice_idle
parameters to zero.
Bug: 213617178
Bug: 313578691
Change-Id: I02429876790a6456ca957ff7c38f0c8bf88127f9
Signed-off-by: Bart Van Assche <bvanassche@google.com>
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.
