title: Saving UI on orientation change - onSaveInstanceState not working as expected if retaining Fragment
body: <p>Using compat lib v1 (not using v2|3 because of certain bugs); a variation of <a href="https://stackoverflow.com/questions/7320785/onsaveinstancestate-is-not-saving-my-values-oncreate-input-bundle-is-always-nu">this question</a>.</p>
  
  <p>I have a fragment whose UI has various controls whose state I want to maintain on an orientation change.</p>
  
  <p>The parent activity is being destroyed on orientation change (PLEASE don't tell me about manifest changes to avoid activity recreation!!!!). </p>
  
  <p>The fragment calls <code>setRetainInstance(true)</code>.</p>
  
  <p>1) Now my understanding is that Views with unique IDs should retain some state on say an orientation change. Given this I would expect a non-null bundle into <code>onCreateView|onActivityCreated</code> but it is null.</p>
  
  <p>2) In any case if I save state in <code>onSaveInstanceState</code> (ensuring I call super) I still get a null bundle in 'onCreateView|onActivityCreated`</p>
  
  <p>3) If I don't call <code>setRetainInstance(true)</code> then I DO get a non-null bundle in <code>onCreateView|onActivityCreated</code> even if I don't have an `onSaveInstanceState' method.</p>
  
  <p>The questions I have is, is this working as expected and my understanding of the life-cycle is broken? Regardless, I'm guessing that the best way forward for me would be to retain the fragment and then maintain the state of the controls myself within the fragment.</p>
  
  <p>Thanks in advance. Peter.</p>