Signed-off-by: K A R T H I K <karthik.lal558@gmail.com>
Signed-off-by: chrisw444 <wandersonrodriguesf1@gmail.com>
Signed-off-by: clarencelol <clarencekuiek@icloud.com>
* +Adding some props also
When device is in Enforce mode, this happens:
---------------------------------------------
E init: Do not have permissions to set 'persist.radio.VT_CAM_INTERFACE' to '2' in property file '/vendor/build.prop': SELinux permission check failed
As example, so, moving those props to system/build.prop (from vendor/build.prop) fixes the issue.
Test: adb logcat -b all -d *:E > logcat-err.log and check for any init props related errors
Fix: Enforcing the Device Tree
These tell the ROM to use the correct Adreno drivers which fixes graphical artifacts.
Credit to Sultan for the triple buffers prop.
Credit to kdrag0n for noticing vulkan prop was missing.
Change-Id: I3481092f3aea2be2091c8c64ca04c426a244a696
Co-authored-by: Lunarixus <Nathan@lunarixus.party>
* As seen with December patch some system apps including user apps started to lag (like screen tearing).
* Enabling Vsync and disabling backpressure resolves the issue
Signed-off-by: Manish4586 <manish.n.manish45@gmail.com>
Change-Id: Ieea19e65020643353494336079104f3f53bd1e4c
* The values are kanged from hammerhead and may introduce
latency as it is not selected for any of our panels
and stock does not set these values in the first place.
Change-Id: Iee854ea77d1e8216c8f01aee2f71a178ffcfaf5c
* This is no-op when debug.sf.disable_backpressure=1
is set. Plus, it lags when it's set alone.
Just follow CAF here and remove this ricing.
This reverts commit ede4f5c879.
Change-Id: I74c5e4ba830ef23448e4f16822687d7a22746a3b
Define ro.charger.enable_suspend to true as charger no
longer uses BOARD_CHARGER_ENABLE_SUSPEND.
Bug: 153937817
Change-Id: Ic76bf3a66c5e21c74e49607f54d6c0358c31bbac
Signed-off-by: Redick Lin <redicklin@google.com>
* Fixes QR code scanning for WhatsApp web login
* Whatsapp video calls now support hal3, so hal1 is no longer required
Signed-off-by: OdSazib <odsazib@gmail.com>
Enable ro.lmk.use_minfree_levels flag to use minfree levels to decide
when lmkd should kill. This makes lmkd work the same way lowmemorykiller
kernel driver used to work.
Bug: 77299493
Bug: 75322373
Test: lmkd_unit_test
Change-Id: Ic29d7fd21af1cb6af3a7d2a175d210775a09987e
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Setting ro.lmk.medium to 800 to prevent important processes from being
killed at medium vmpressure levels.
Bug: 77299493
Test: lmkd_unit_test
Merged-In: I37e1651a0a2b148a852e5bde86501024d4f87bbf
Change-Id: I37e1651a0a2b148a852e5bde86501024d4f87bbf
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
(cherry picked from commit c954ec2eb318518cfa5c6f64a688fd8c809e91c5)
* When sys.use_fifo_ui is enabled, ActivityManager tracks the UI thread and RenderThread (the two most UI-critical threads) of the top application and makes those threads SCHED_FIFO instead of SCHED_OTHER. This effectively eliminates jitter from UI and RenderThreads; the traces that've gathered with this option enabled show runnable times on the order of microseconds instead of milliseconds.
* However, it should be enabled only when we have EAS i.e a capacity-aware RT scheduler because if RT load balancer is not capacity-aware, then there would be a 30% reduction in application startup performance.
Reference: https://source.android.com/devices/tech/debug/jank_jitter
Signed-off-by: Saurabh Charde <saurabhchardereal@gmail.com>
Signed-off-by: Aston-Martinn <advaithbhat9@gmail.com>
Change-Id: I8b55ad1899be985fc7357abaf06d68d6a130fb75
