previous fragment taking too much time to load on back press

Question

I have an app that is mainly based on fragments. Each fragment involves it's own json parsing and image loading from json.Also to be noted that I have called addToBackStack(null) on ech fragment when it's getting replaced. As I switch between the fragments, and press the back button, it takes quite some time 4-5 secs to be exact to load the previous fragment. Is there any way that the load time can be minimized?

I have used async task to fetch the data,async task is performed in fragment's onAttach() method to prevent json parsing when back button is pressed.

Can you please share related code? – mertsimsek Jan 16 '17 at 07:30 — mertsimsek, Jan 16 '17 at 07:30

score 0 · Answer 1 · answered Jan 16 '17 at 07:14

0

This could easily be a simulator issue, but if not it could be because you are loading all of the information on the main thread instead of in an async task. Making an Async task loads the information in the background and updates the UI when finished

answered Jan 16 '17 at 07:14

touchofsarcasm

79
4

score 0 · Answer 2 · answered Jan 16 '17 at 07:23

   public void currentFragment(int position, Bundle bundle) {
        switch (position) {

            case 105:
                MainFragment workoutFragment = MainFragment.newInstance("", "");
                workoutFragment.setArguments(bundle);
                replaceFragment(workoutFragment, "front");
                break;

            case 108:

                break;
            default:
                replaceFragment(new MainFragment(), "Main");
                break;
        }
    }

    private void replaceFragment(Fragment fragment, String tag) {
        String backStateName = fragment.getClass().getName();
        try {
            boolean fragmentPopped = fm.popBackStackImmediate(backStateName, 0);
            if (!fragmentPopped && fm.findFragmentByTag(backStateName) == null) {
                //fragment not in back stack, create it.
                FragmentTransaction ft = fm.beginTransaction();
                ft.add(R.id.fragment_container, fragment, backStateName);
                ft.setTransition(FragmentTransaction.TRANSIT_FRAGMENT_OPEN);
                ft.addToBackStack(backStateName);
                ft.commitAllowingStateLoss();
                //ft.commit();
            }
        } catch (Exception e) {
            e.printStackTrace();
        }
    }

// inside  Backpress    @Override
   // public void onBackPressed()
//  if (fm.getBackStackEntryCount() == 1) {

//     super.onBackPressed();

// }

//  to add fragment call like this 

// currentFragment(101,null);

// what it do is popup from stack not add again and again that is best method to achiveve this if still getting problem then ask me again

if you dont want to change whole code remove ddToBackStack(null) method and on backpress implement what i suggested — SanjeevMogaBishnoi, Jan 16 '17 at 07:26
@Vlad Matvienko yes it is related to question it matter a lot whether you are creating a frament again or poping from backstack .if you addBackstakc to null then it will created again and again other wise it will poped out from back stack. try it it will work — SanjeevMogaBishnoi, Jan 16 '17 at 07:29
I mean that posting only a code is not an answer to a question. You should add some explanation/comments on this. It is not clear how to use your code — Vladyslav Matviienko, Jan 16 '17 at 07:34

score 0 · Answer 3 · answered Jan 16 '17 at 07:26

If you have no need to reload images in fragments on backpress ,then you can use this trick

in Each Fragment

  View mView; // declare it globally

    @Override
    public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) {
       if(mView == null){ // it will not reload image it will set first time view which is loaded. 
          mView = inflater.inflate(R.layout.fragment_dashboard, null);
        }
        return rootView;
    }

This will be load immediately . it will restore previous view on backpress

Hold on. Saving whole view could be a disaster. – Paresh P. Jan 16 '17 at 07:57 — Paresh P., Jan 16 '17 at 07:57

score 0 · Answer 4 · answered Jan 16 '17 at 07:56

One reason could be the amount of data that you're loading. To overcome situation, you can user Handler with Runnable.

// Declaration
private Handler layoutHandler = new Handler();
private Runnable mRunnable;

// Initialization
mRunnable = new Runnable() {
       @Override
       public void run() {
            hideProgress();
            // Perform an action such as binding your data
       }
};

Now make delay before loading a data... using

showProgress();
layoutHandler.postDelayed(mRunnable, 800);

I recommend to save your data using savedInstanceState rather then loading data everytime.

previous fragment taking too much time to load on back press

4 Answers4