title: Android Activity Lifecycle: restoring app after kill - design problem
body: <p>atm I try to get my app working around "onSaveInstanceState" and "onRestoreInstanceState", but  the deeper I dig, the the more problems occur.</p>
  
  <p>So, for example, I just realized, that restoring one activity via those two functions is pretty useless. Because, if I press the back button and return to the activity before, this one doesn't get its "savedInstanceState" bundle and instead gets recreated completely.</p>
  
  <p>Is there a way to restore the whole application instead of just a single activity? Or is this just a weird design and I shouldn't even bother with restoring one activity?</p>
  
  <p>Kind regards, 
  jellyfish</p>
  
  <p><strong>Edit:</strong> ok, stupid me...</p>
  
  <p>the bundle my main activity got was not null, but only in "onRestore...". In "onCreate" it was null indeed, but this was true all the time. (No matter if I came back from another activity after kill or not, for example)</p>
  
  <p>So now I'm confused in another way: I have tested this before in another activity, and there, the savedInstanceState bundle of "onCreate" and "OnRestoreInstanceState" where the same! Is this just random or something special of the main activity? (Tried different launch modes as well, but they had no impact).</p>