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
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
Enable EGL image memory tracking on SurfaceFlinger to catch
memory leaks.
Bug: 137514000
Test: launch few apps and switch between them
Test: adb shell dumpsys SurfaceFlinger
Change-Id: I621231f36b5317e3487d5c9a93320584974b7af1
Window animations now have rounded corners, meaning that
the shader that we use is more expensive than it used to be.
Because of this, we need to adjust the SF offsets, to make sure
that we'll have enough time to finish the GPU composition without
dropping frames.
Change-Id: I8173e12b006bc1cab6b4cb0b3a5db9f9b3489819
We support IMS features on carriers not listed in the CarrierConfig,
so let's use the props to enable it everywhere.
Change-Id: Id3ad71d522a22048f7ad86d89695ad262361632d
* AOSP defaults to true but 10 QC telephony extension sets it to false.
* Restore AOSP behavior by enabling it with a system property which has
higher priority over global system settings which is used by QCOM w/o
modifying the jar.
Change-Id: I45854b91bb8cfafabfe811777cda9f1e1840febf
