Clean up updating bounds after config/display info change
We always update the display info before handling the configuration change. Thus, we remove this weird interleaving asynchronous beast of code and handle rotation and density in updateBoundsAfterConfigChange and everything else in updateDisplayInfo. Sending an asynchronous message to resize the stack only causes race condition and issues. Change-Id: Ifa86f62e816917822a8c1d42d13d4bf1ad9bc5bf Fixes: 28316517 Bug: 28184044
Loading
Please register or sign in to comment