Android Retain Callback State After Configuration Change

I understand pretty well about Android lifecycle. I post here because I've observed one weird behavior, anyway this is my own thought. My case is like this: One activity will use a

Solution 1:

Here is why you see this behavior:

1. When 'onCreate' method is called first time, it has no saved state. Which means BundlesavedInstanceState parameter is null.
2. When configuration changed, Android paths non-null value in savedInstanceState parameter.
3. After configuration is changed, and onCreate returns, Android calls onRestoreInstateState.
4. By default, all views that have id are trying to restore their state, EditText restores its state too (actually, that TextView who restores most of it).
5. At some place during state restoration (but after onCreate method is completed) your EditText control calls setText on himself in order to restore text that it had just before configuration changed.
6. Your newTextWatcher that you added in onCreate method is notified about this change.

---

Just to make this clear, your old TextWatcher, that you added on first call to onCreate, is not preserved! Its new TextWatcher, that was added on last call to onCreate, which receives the text change notification.

You can examine TextView.onRestoreInstanceState yourself.

Solution 2:

When ever you rotate the device the onCreate method of activity called again.if you want to prevent to call onCreate when rotating the device do the following code in the Manifest

android:configChanges="orientation|keyboardHidden"

and in your activity

public void onConfigurationChanged(Configuration newConfig)
{       
    super.onConfigurationChanged(newConfig);    

    if(newConfig.orientation==Configuration.ORIENTATION_LANDSCAPE)
    {

    }      
    else if(newConfig.orientation==Configuration.ORIENTATION_PORTRAIT)
    {

    }  
}