Application lifecycle and Bundle savedInstanceState
<p>Can somebody clarify please why I have such a weird behavior. Up to documentation the <code>Bundle savedInstanceState</code> which is set in <code>onSaveInstanceState()</code> is alive as long as application alive, so when it it in foreground or background. After the application is being killed the <code>savedInstanceState</code> instance is killed as well. Here is what I have:</p>

<pre><code>@Override
    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.main);

        if (savedInstanceState != null) {
            Log.i("Dev", "not null");
        } else {
            Log.i("Dev", "null");
        }
    }
</code></pre>

<p>Here is how I set it:</p>

<pre><code>@Override
    protected void onSaveInstanceState(Bundle outState) {
        super.onSaveInstanceState(outState);
        outState.putBoolean("bool", true);
    }
</code></pre>

<p>Then, I'm starting the application in the emulator. After application is opened I click <code>home</code> button so the Launcher is visible. Then I kill the application's process using adb. After that I start the application from the list of recently used application expecting for "<strong>null</strong>" in the Logcat, but what I actually see is "<strong>not null</strong>", so my understanding is incorrect? </p>
