The fragments onResume() or onPause() will be called only when the Activities onResume() or onPause() is called. They are tightly coupled to the Activity. Read the Handling the Fragment Lifecycle section of this article.
If you return to a fragment from the back stack it does not re-create the fragment but re-uses the same instance and starts with onCreateView() in the fragment lifecycle, see Fragment lifecycle. So if you want to store state you should use instance variables and not rely on onSaveInstanceState().
Explanation: on what’s going on here? If we keep in mind that .replace() is equal with .remove().add() that we know by the documentation: Replace an existing fragment that was added to a container. This is essentially the same as calling remove(Fragment) for all currently added fragments that were added with the same containerViewId and then … Read more
Add this to onCreate and you should be good to go: // Possible work around for market launches. See https://issuetracker.google.com/issues/36907463 // for more details. Essentially, the market launches the main activity on top of other activities. // we never want this to happen. Instead, we check if we are the root and if not, we … Read more
Look at the getFragmentManager().popBackStack() methods (there are several to choose from) http://developer.android.com/reference/android/app/FragmentManager.html#popBackStack()
In API level 11 a new Intent Flag was added just for this: Intent.FLAG_ACTIVITY_CLEAR_TASK Just to clarify, use this: Java intent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK | Intent.FLAG_ACTIVITY_CLEAR_TASK); Kotlin intent.flags = Intent.FLAG_ACTIVITY_NEW_TASK or Intent.FLAG_ACTIVITY_CLEAR_TASK Unfortunately for API lvl <= 10, I haven’t yet found a clean solution to this. The “DontHackAndroidLikeThis” solution is indeed pure hackery. You should not do … Read more
Reading the documentation, there is a way to pop the back stack based on either the transaction name or the id provided by commit. Using the name may be easier since it shouldn’t require keeping track of a number that may change and reinforces the “unique back stack entry” logic. Since you want only one … Read more