Choreographer VSync has some performance impact for CPU rendered apps
as the app has to wait for VSync to start a new frame draw. When the
frame draw time exceeds one VSync, this has a direct impact on the FPS.
"debug.cpurend.vsync" property controls the VSync for CPU rendered apps.
Disable VSync for CPU rendered app, by setting this property to false.
Change-Id: I93cfa7c588f1ab80803940c8059073075fd49506
Signed-off-by: Akash <akashniki@gmail.com>
Signed-off-by: DarkDampSquib <andrin.geiger1998@gmail.com>
This patch removed the old writeout policy tune which was never touched since
2009. In the meantime, most of Android devices are equipped with over 4GB DRAM
and very fast flash storages like UFS, which becomes more like desktop or
servers in 2009. So, it'd be worth to go back to use the default kernel configs.
Bug: 136483670
Bug: 137190999
Bug: 152936751
Test: check value output
Change-Id: I1ebbf9f1f27a921103db51e96a50aadd6ec0dde8
Signed-off-by: Jaegeuk Kim <jaegeuk@google.com>
Signed-off-by: Martin Liu <liumartin@google.com>
Scheduler will use pure CFS before boot complete, and change to
EAS after boot complete, so set capacity margin here.
Bug: 153216544
Test: capacity margin set as expected
Change-Id: I0f76cb1112a37475422eb5866960dbd3db64ebc3
Set SurfaceFlinger idle timer to 50ms.
Test: flashall the build and observe idle timer value
Bug: 126270036
Change-Id: I26a0b3f9f1efedd05f164cdda1d6a1bbd07ba7e5
* This is only available on Nexus/Pixel devices, and we have our own
implementation in livedisplay.
Change-Id: I8343e4986d7dd8413bd8d36dfad0309a4c08026e
Accessibility transforms require a specific color mode that is not
always available for the user to select.
Bug: 130376719
Test: atest com.google.android.config.pts
Change-Id: Ia3211d5aa6e117c5361dea44d944064b23260a81
Enable Adaptive color mode setting.
Bug: 143513730
Test: Boot test and measure the adaptive color value
Change-Id: I969ec6c3cb1d092a33c0e3a028ff38ad7115dfe2
-Switch to LZ4 for better overall performance
-Set max_comp_streams to num of cores since upstream also moves this to
percpu.
-Set page-cluster to 0 as the incremental cost of reading 1 page at a
time is negligible for zram
Bug: 38249616
Test: boot and run zram-perf showing better performance
Change-Id: I0b92b246d773db85aa03d033b2cecee54347cbd1
Reserving more than 1.5gb sharply decreases free inodes, resulting
in gapps install/restore issues.
Change-Id: I16c0c649b7e06aea6203e34a81d0d0350b80588c
GPU takes long time(>8ms) when app was launching and closing.
This may because GPU is handling some heavy task like color conversion.
By setting NegativeOffset as 5ms to allow SF have more time to handle
when doing animation transaction and shift back 5ms with
early_app_phase_offset_ns such that app still has the same amount of
time to handle each frame.
Test: 1. Open Chrome from homescreen
2. Swipe vertically to go back to home screen
3. Measure the gpu completion time and "FrameMissed" count from systrace result
Bug: 147339695
Change-Id: I157cb11e8ed8c1ca296fc65612752fbb3d985dcd
