activity lifecycle

I have a single activity app with four EditText fields. To enhance the user experience the content of each view (and cursor position) must be preserved every time the app goes to the background or terminates. Easy enough I thought.... use KVS to save and reload the fields every time the app...

I need to create an external class for storing activity data during the activity lifecycle. Here is the envisioned Sequence: The Activity is quite complex. Having sophisticated custom elements. So I need to be able to carry the state across from activity destruction to activity...