In Android R, the SurfaceFlinger calculate phase offsets
based on duration. Adopt the new way of specifying
phase offsets to SurfaceFlinger.
Bug: 158464992
Test: scrolling, app launching/closing, playing video
Change-Id: Ia717f5c0075b6adaedaf20dd6be689737edc1415
Signed-off-by: SamarV-121 <samarvispute121@gmail.com>
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>
The configstore will be not used in surfaceflinger. So surfaceflinger
will use the system properties instead of configstore.
For this, the system properties are added.
Bug: 112386364
Test: m -j && boot test
Change-Id: Ie3d2adccca06702217984cf2c9db986d852b7014
Signed-off-by: SamarV-121 <samarvispute121@gmail.com>
The property will be used to detect the framework type
at runtime.
Change-Id: Id5ede408641cd371d546ee5b35087c71781e380b
CRs-Fixed: 2379644
Signed-off-by: SamarV-121 <samarvispute121@gmail.com>
