Home » Android » android – Prevent ViewPager from destroying off-screen views

android – Prevent ViewPager from destroying off-screen views

Posted by: admin March 11, 2020 Leave a comment


I have a ViewPager hooked up to a FragmentPagerAdapter that’s displaying three fragments. The ViewPager appears to destroy a hosted fragment’s view when it is more than one swipe away from the current position.

These views are all simple lists and this optimization is completely unnecessary, so I’d like to disable it. It’s causing some visual problems because the lists have layout animations applied to them and those animations are being replayed after they’ve been destroyed and recreated. It also shows the scrollbar intro animation each time (where the scrollbar is briefly visible to indicate that scrolling is possible) which can be distracting, and the user’s current scroll position is lost in the process.

It also doesn’t load the third fragment until the first swipe happens, which is problematic because each fragment handles its own service calls and I’d prefer to have all three fire off at the same time when the activity loads. Having the third service call delayed is less than ideal.

Is there any way to convince ViewPager to stop this behavior and just keep all my fragments in memory?

How to&Answers:

In revision 4 of the Support Package, a method was added to ViewPager which allows you to specify the number of offscreen pages to use, rather than the default which is 1.

In your case, you want to specify 2, so that when you are on the third page, the first one is not destroyed, and vice-versa.

mViewPager = (ViewPager)findViewById(R.id.pager);


By default, ViewPager recreates the fragments when you swipe the page. To prevent this, you can try one of two things:

1. In the onCreate() of your fragments, call setRetainInstance(true).

2. If the number of fragments is fixed & relatively small, then in your onCreate() add the following code:

ViewPager mViewPager = (ViewPager) findViewById(R.id.pager);

If I remember correctly, the second option is more promising. But I urge you to try both and see which of them work.


“Set the number of pages that should be retained to either side of the current page in the view hierarchy in an idle state. Pages beyond this limit will be recreated from the adapter when needed.”