back-stack

This question already has an answer here: Lifecycle of a replaced ViewPager and BackStack? 1 answer I'm using a TabLayout in one of my fragments with a viewPager to switch between two fragments below the tabs. When I click the FAB inside one of the lower fragments, I load a new fragment (for input). However- when I press the BACK button, the TabLayout shows up but WITHOUT either of the lower fragments (represented by the pages). So what am I doing wrong? and is there a better way to be swapping fragments ? and is there a way to press the back button and get back to the viewPager Page that was

I have implemented Navigation Drawer which is a subclass of Activity. I have many fragments in my application. My question goes here Imagine there are 3 fragments : Fragment_1 : Fragment_2 : Fragment_3 When I start my application, Fragment_1 is loaded When I click on some components on Fragment_1, I'm navigated to Fragment_2 and so on.. So it's like Fragment_1 > Fragment_2 > Fragment_3 When I press back key from Fragment_2, I'm navigated back to Fragment_1 But when I press back key from Fragment_3, I'm navigated back to Fragment_1 (instead of Fragment_2) I want something like this in my

How Do I Prevent Accidental App Exit w/in Android? IE: When the he/she presses the back button and reaches the last activity in the BackStack, show a toast to ask if the user wants to exit using the onBackPressed() method. Also, It needs to function with backStacks for fragments. This functionality can easily be implemented by overriding main activity's onBackPressed() method. In this example when user presses back button then the app will display a toast for 4 seconds on which time a new back press terminates the app immediately. ref You can put it in a BaseActivity that extends Activity like

I don't want my application to show few Activity (say SplashScreenActivity ) when pressing back button. So I've used noHistory=true in my Manifest.xml for that Activity as show below: <activity android:name="com.gokul.SplashScreenActivity" android:noHistory="true" > </activity> Instead of setting noHistory , I can also call finish() in my SplashActivity.onPause() method or wherever I want, as shown below: @Override protected void onPause() { super.onPause(); finish(); } Both does the job perfectly. But which one is better to use, to use noHistory or call finish() ? onPause() is not at all a

I am getting a strange problem, while using Fragments and popping back them out. I have one Fragment Activity: Step1: I am attaching one Fragment in the onCreate of that Activity in the Starting named Fragment A as: This is the onCreate of Fragment Activity @Override protected void onCreate(Bundle savedBundleState) { super.onCreate(savedBundleState); setContentView(R.layout.activity_base_new); Fragement_Home home = new Fragement_Home(); FragmentManager manager = getSupportFragmentManager(); manager.beginTransaction().add(R.id.frameContent, home).addToBackStack("home").commit(); } Step:2 After

Can I use savedInstanceState() to save the state when removing a fragment, then restore the state when I pop the fragment off the back stack? When I restore the fragment from the back stack, savedInstanceState bundle is always null. Right now, the app flow is: fragment created -> fragment removed (added to back stack) -> fragment restored from back stack (savedInstanceState bundle is null). Here is the relevant code: public void onActivityCreated(Bundle savedInstanceState) { super.onCreate(savedInstanceState); Bundle bundle = getArguments(); Long playlistId = bundle.getLong(Constants.PLAYLIST