tree b9c07a8ffb37a3758f9fe59c1a17df10b924b949
parent df2e2eff9446c0220515fa7aab7857135e04e12e
author Christopher Tate <ctate@google.com> 1275960920 -0700
committer Christopher Tate <ctate@google.com> 1275960920 -0700

Don't bring up Launcher until after boot complete

The preboot upgrade handling was bringing up the acore process with a default
application object, then the normal "start the HOME app" code was bringing up
Launcher2 [hosted in acore] in anticipation of boot completion... but then it
saw that the host process was alive and continued with Launcher2's init.
Launcher2 depends on a custom application object, however, so it crashed
immediately.

This change ensures that the HOME app is not actually initted at that level
until after boot has completed, at which point its proper application class
can be instantiated.

Fixes bug #2732250

Change-Id: I1a15384e2c0d50e14300df0c0db236bd7b1a187c