From bbece869eb9d84c669340e69f9ebbe9edbe0fdfc Mon Sep 17 00:00:00 2001
From: Sunny Goyal <sunnygoyal@google.com>
Date: Fri, 1 Mar 2019 13:13:52 -0800
Subject: [PATCH] Reapply the current state after onCreate

In case of normal restart we were never applying the NORMAL state and
so various state properties didn't start with correct default values.
We generally get insets after start which reapplies the state and
fixes this issue but that is not always the case.

Bug: 126416861
Bug: 118441555
Change-Id: Iaa178556618f8a49197187d0820d8b8afdc73378
---
 src/com/android/launcher3/Launcher.java | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/com/android/launcher3/Launcher.java b/src/com/android/launcher3/Launcher.java
index f571aa30e9..d65fe763fa 100644
--- a/src/com/android/launcher3/Launcher.java
+++ b/src/com/android/launcher3/Launcher.java
@@ -319,6 +319,7 @@ public class Launcher extends BaseDraggingActivity implements LauncherExterns,
             }
         }
         restoreState(savedInstanceState);
+        mStateManager.reapplyState();
 
         // We only load the page synchronously if the user rotates (or triggers a
         // configuration change) while launcher is in the foreground