commit de3be8915d2d044998e34e0149aa2c3d1d59d954
author Rupesh Bansal <brup@google.com> Sun Oct 30 10:16:03 2022 +0000
committer Rupesh Bansal <brup@google.com> Thu Nov 17 16:36:24 2022 +0000
tree 8b920abb14fe55484b0c4d52563b78df9828a304
parent 6e16fac514596b71b05ea6f3489f49578c8ba094

Fixed latency spike

A spike in the startup time of DisplayManagerService was observeed
because of a recent change where we are attempting read values from
DeviceConfig, which if missing fallsback to DisplayDeviceConfig. This
extra read attempt is unneeded because once the DisplayManagerService is
setup, we explicitly make a start call to DisplayModeDirector which
takes care of reloading values from DeviceConfig if present.

Bug: 254354520
Test: Manual
Change-Id: Iae7066b8c732d9b39e3fb76200ff24cb5aeb3d73