Task Killer not resetting stack
<p>My application has a main Activity A and that does a StartActivity on Activity B.  If somebody uses a Task Killer (e.g., Advanced Task Killer), the application is killed but when they run the app again I see the Application object is being built (onCreate called) and then it goes right into Activity B not Activity A.  The Manifest has A being the Launcher Activity.</p>

<p>I also see the scenario if I run A, then Activity B, bring down notification list and run Task Killer to kill my app, and press the Back key, it creates the Application object and then Activity B object.</p>

<p>Any ideas on how to prevent this behavior?  Activity B assumes that Activity A has already run.  I am able to kludge this but have a boolean in the Application object which is set on Activity A.  In Activity B onCreate, if that global flag is not set, I do a finish().  Must be a better way to handle this since I have quite a few activities that would experience the same behavior.</p>
