Tying LauncherAppState lifecycle with LauncherProvider

The content provider is the first component started with the main process,
which makes it ideal for initiating LauncherAppState

Change-Id: I03db82a8949ad1376af53a0033592f421dbf0b15
This commit is contained in:
Sunny Goyal committed 2015-11-24 12:06:42 -08:00
1 parent 4ee66259eb
commit 7bce5f7988
5 files changed
+5 -6

No files matched your search

@@ -171,7 +171,6 @@ public class InstallShortcutReceiver extends BroadcastReceiver {
private static void queuePendingShortcutInfo(PendingInstallShortcutInfo info, Context context) {
// Queue the item up for adding if launcher has not loaded properly yet
LauncherAppState.setApplicationContext(context.getApplicationContext());
LauncherAppState app = LauncherAppState.getInstance();
boolean launcherNotLoaded = app.getModel().getCallback() == null;