title: Managing activity state on orientation change (Android)
body: <p>I have a question. I'm learning about the activity lifecycles in Android
  at the moment. I had some trouble with the orientation change of the device.</p>
  
  <p>In my particular case I have an activity with a quite complex data-structure.
  As I don't like the retained fragment method to pass this object to the new
  created activity, I will use the deprecated <code>onRetainNonConfigurationInstance()</code>
  method, because I feel its more light weight. Is there a big disadvantage to use
  this?</p>
  
  <p>Another thing I did experience is, that when I have an activity and views, for example
  TextEdits defined (in the layout XML in my case) and I write something and then cause
  an orientation change, the TextEdits keeps its state (the text written in), even though I didn't care for it.
  How can that be explained?</p>