In Android documentation <http://www.bagualu.net/android/guide/components/tasks-and-back-stack.html#ActivityState>: " When the system stops one of your activities (such as when a new activity starts or the task moves to the background), the system might destroy that activity completely if it needs to recover system memory. When this happens, information about the activity state is lost. If this happens, the system still knows that the activity has a place in the back stack, but when the activity is brought to the top of the stack the system must recreate it (rather than resume it)..."
And question: whether or not Fragment with setRetainInstance(true) will stay alive when system destroy it parent activity (process is not destroy) and then this activity goes to foreground? (sorry for my Endlish) -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. To post to this group, send email to android-developers@googlegroups.com. Visit this group at https://groups.google.com/group/android-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/android-developers/8ff00029-d76a-426c-863a-1a8f8673bf88%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
