No description
Sometimes SW_VSNC of DispSync comes 1ms earlier than signal_retire_fence(or HW_VSYNC) It means VSYNC-sf only 5ms behind signal_retire_fence. And VSYNC-sf will be 5.5ms earlier when applying early_sf_phase. (the phase-sf changes from 6ms to 0.5ms) Therefore, VSYNC-sf comes 0.5ms earlier than signal_retire_fence when applying early_sf_phase for transaction and cause frame missed. Add more 1ms to early_sf_phase then it will come 0.5 later than signal_retire_fence in this case. Bug: 118606025 Test: Open/close apps, observe no jank Test: -Launch app, stay the same picture on screen at least 30s -Tap home key, observe no jank when doing app animation Change-Id: Iec83aef719b830aed612b47bbda910508406d196 Signed-off-by: SamarV-121 <samarvispute121@gmail.com> |
||
---|---|---|
bluetooth | ||
configs | ||
Gcam | ||
keylayout | ||
libhidl | ||
light | ||
overlay | ||
overlay-pe | ||
parts | ||
power-libperfmgr | ||
powerstats | ||
prebuilt | ||
rootdir | ||
sepolicy/private | ||
usb | ||
wifi | ||
Android.bp | ||
Android.mk | ||
AndroidProducts.mk | ||
aosp.dependencies | ||
aosp_kunlun2.mk | ||
BoardConfig.mk | ||
config.fs | ||
device.mk | ||
extract-files.sh | ||
framework_manifest.xml | ||
manifest.xml | ||
product_prop.mk | ||
proprietary-files.txt | ||
releasetools.py | ||
setup-makefiles.sh | ||
update-sha1sums.sh |