title: Android retain callback state after configuration change
body: <p>I understand pretty well about Android lifecycle. I post here because I've observed one weird behavior, anyway this is my own thought.</p>
  
  <p>My case is like this: One activity will use a simple layout with just a single <code>EditText</code>. In the activity <code>onCreate</code> method, i set some default text to the <code>EditText</code> and in later part of the method, assign a <code>TextWatcher</code> to the <code>EditText</code> so whenever user types in anything, i can response in my own way.</p>
  
  <p>Everything is alright until I rotate the screen. The <code>TextWatcher</code> callback starts to react against the code that initialize the <code>EditText</code>.</p>
  
  <p>According to the normal code flow, the <code>TextWatcher</code> is assigned later after initializing text value of the <code>EditText</code>. so it's not supposed to fire because of the text assignment in the <code>onCreate</code> method.</p>
  
  <p>Could anyone here explain this?</p>