android - onsaveInsanceState never gets called fragment -

A lot of information and followed by Goggle, I have tried many things onsaveState to work when a user has a different piece Navigates to and then back to the previous section by using the back key.

I have two pieces A and B, which are stored in a container xml layout kept by a normal activity and used it. A single activation

Here I am adding a piece in the slice manager and my container xml

  about FragmentA = new piece (); Fragment Transaction Feet = FM BBT transactions (); Ft.replace (About R.id.mainViewContainer,) .addToBackStack (TAG_ABOUT_PAGE); Ft.commit ();  

Here is the onswest status on Fragment A

  Override public null at @SaveInstanceState (bundle outstate) {super.onSaveInstanceState (outstate); // Something save. Input level (KEY_CENTER_POINT, mlatLong); Log D. ("Jezezie", "onsite personasset");     
 Fragment Transaction Feet = FM BBT transactions (); Ft.replace (R.id.mainViewContainer, fragmentB) .addToBackStack (TAG_ABOUT_PAGE); Ft.commit ();  

When the user presses the back key, the whole life cycle of the piece is called in the attache, secret, openview etc. and the pieces are displayed, but they are not saved. Because it is not called onsite insteststate

Any ideas?

I can hardcoded and can represent a value that a singleton wants to store and load it with only the optical view but it is not ideal and this is the last resort.

Thanks