Loading
Compute size range before setting DisplayInfoOverride
The original logic didn't adjust the size range within the DisplayInfo before setting it to DisplayManager, which caused apps would get the previous size ranges which might be incorrect. Bug: 132678244 Test: atest DisplaySizeTest Change-Id: Iaf08ae8a16d4d95516d9c8ae316b6efcd7240751