diff options
| author | 2022-10-30 10:16:03 +0000 | |
|---|---|---|
| committer | 2022-11-17 16:36:24 +0000 | |
| commit | de3be8915d2d044998e34e0149aa2c3d1d59d954 (patch) | |
| tree | 8b920abb14fe55484b0c4d52563b78df9828a304 /api/api.go | |
| parent | 6e16fac514596b71b05ea6f3489f49578c8ba094 (diff) | |
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
Diffstat (limited to 'api/api.go')
0 files changed, 0 insertions, 0 deletions