Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Why should I need to use setRetainInstance() or onSaveInstance() to save state and I can use android:configChanges="keyboard|orientation|screenLayout" and get the samething “saving state non-UI state”? I mean with less headache.
Don’t use
android:configChanges. It will break things in subtle ways and will prevent Android from getting the proper layout/theme/dimensions, etc. for the current configuration.onSaveInstanceState()is completely orthogonal to this: you need to save state so you can restore it if Android kills your process to save memory.configChagnesonly prevents it from re-creating the activity on rotation, keyboard state changes, etc.setRetainInstance()is for fragments that you don’t want re-created on device rotation, etc. If you don’t call it, Android will serialize their state in a Bundle, and re-create them along with the parent activity.In short, while
configChangesappears to be a ‘shortcut’ it is not. Don’t rely on it and save/restore state as necessary using the proper tools for each case.