If you want to stop the destroy/create issue that is the default in android because of an orientation change and lock in one orientation then you need to add code and xml In your activites code (notes about the xml) // When an android device changes orientation usually the activity is destroyed and recreated with … Read more
The ViewPager comes with the OnPageChangeListener interface. By setting some flags for the previous and currently shown pages, you can emulate this behavior.
When a fragment is moved to the backstack, it isn’t destroyed. All the instance variables remain there. So this is the place to save your data. In onActivityCreated you check the following conditions: Is the bundle != null? If yes, that’s where the data is saved (probably orientation change). Is there data saved in instance … Read more
i can’t really answer WHY exactly this happens, but if you delay the setCurrentItem call for a few milliseconds it should work. My guess is that because during onResume there hasn’t been a rendering pass yet, and the ViewPager needs one or something like that. private ViewPager viewPager; @Override public void onResume() { final int … Read more
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.
See it in Activity Lifecycle (at Android Developers). onCreate(): Called when the activity is first created. This is where you should do all of your normal static set up: create views, bind data to lists, etc. This method also provides you with a Bundle containing the activity’s previously frozen state, if there was one. Always … Read more