Android onSaveInstanceState onRestoreInstanceState

Filed Under: Android

In this tutorial, we’ll be discussing the two vital methods for managing the state of the application, namely onSaveInstanceState and onRestoreInstanceState.
We’ll be developing a Counter Android Application in which we’ll handle the state of the application when the configuration changes.

Android Lifecycle

Following is the lifecycle of the Activities in our application:

android lifecycle

Whenever there is a configuration change, such as rotation or application going into multi-window mode, the activity is recreated.

In this recreation, the application gets restarted and may lose data in the views if not handled properly.

For this there are two methods that are triggered at different stages of the lifecycle:

  • onSaveInstanceState
  • onRestoreInstanceState

They are used to save and retrieve values. The values are stored in the form of a key-value pair.
Let’s look at each of them separately.


onSaveInstanceState method gets called typically before/after onStop() is called. This varies from Android version to version. In the older versions it used to get before onStop().

Inside this method, we save the important values in the Bundle in the form of key value pairs.

The onSaveInstanceState method looks like :

    public void onSaveInstanceState(Bundle outState) {

On the outState bundle instance we add the key value pairs. Following are the methods applicable:

android onsaveinstancestate methods

We can pass custom class instances by setting the class as Parcelable or Serializable.

Let’s look at an example using Parcelable since it is faster than Serializable.

Following is a custom class :

public class Model implements Parcelable {
        public long id;
        public String name;

        public Model(long id, String name) {
   = id;
   = name;

        protected Model(Parcel in) {
            id = in.readLong();
            name = in.readString();

        public final Creator<Model> CREATOR = new Creator() {
            public Model createFromParcel(Parcel in) {
                return new Model(in);

            public Model[] newArray(int size) {
                return new Model[size];

        public int describeContents() {
            return 0;

        public void writeToParcel(Parcel parcel, int i) {

writeToParcel method is where we set the class properties on the Parcelable instance.

Now create an instance of the Model and save it in onSaveInstanceState.

Model model = new Model(10, "Hello");

    public void onSaveInstanceState(Bundle outState) {
        outState.putParcelable("parcelable", model);

Now we can retrieve these saved values in the onRestoreInstanceState method.

Note: onSaveInstanceState gets called whenever you press the home button in your application as well.

Another note: Things like EditText can save and restore their content implicitly provided you’ve set an id on the View. Activity will automatically collect View’s State from every single View in the View hierarchy.


This method gets triggered only when something was saved in onSaveInstanceState method.
It gets called after onStart().

    protected void onRestoreInstanceState(Bundle savedInstanceState) {
        Model model = savedInstanceState.getParcelable("parcelable");

Following are the other method available:

android onrestoreinstancestate methods

The super method implementation restores the view hierarchy.

Generally, onRestoreInstanceState isn’t used to restore values often now. The same can be done from the Bundle in the onCreate method. Also since the onCreate method is always called before, it is a good practice to restore the saved instances there only.

In the following section, we’ll be creating a Counter Application in which we’ll save the state of the counter using the above methods.

Project Structure

android save restore instance project


The code for the activity_main.xml is given below:

<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android=""

        android:hint="Username" />

        android:hint="Phone number"
        android:inputType="phone" />

        android:textSize="32sp" />

        android:text="COUNT UP" />


In the above layout, the second EditText doesn’t have any id set. So when the device is rotated or any configuration happens that causes the activity to recreate, this EditText contents would be reset.

The code for the is given below:

package com.journaldev.androidsaverestoreinstance;

import android.os.Bundle;
import android.view.View;
import android.widget.Button;
import android.widget.TextView;
import android.widget.Toast;

public class MainActivity extends AppCompatActivity {

    Button button;
    TextView textView;
    int counter;

    protected void onCreate(Bundle savedInstanceState) {

        if (savedInstanceState != null) {
            String message = savedInstanceState.getString("message");
            Toast.makeText(this, message, Toast.LENGTH_LONG).show();

            counter = savedInstanceState.getInt("counter", 0);

        button = findViewById(;
        textView = findViewById(;

        button.setOnClickListener(new View.OnClickListener() {
            public void onClick(View view) {
                counter = Integer.valueOf(textView.getText().toString()) + 1;

    public void onSaveInstanceState(Bundle outState) {
        outState.putString("message", "This is a saved message");
        outState.putInt("counter", counter);

    protected void onRestoreInstanceState(Bundle savedInstanceState) {
        Toast.makeText(getApplicationContext(), "onRestoreInstanceState", Toast.LENGTH_SHORT).show();
        counter = savedInstanceState.getInt("counter", 0);



In this the save the integer value of the counter and then when the activity is recreated, the onCreate gets called again. Over there we check if the savedInstanceState Bundle is null or not. If it isn’t we restore the views with the data from the counter.

The output of the application in action is given below:

android save restore instance state

Notice that the Phone Number field goes empty when the orientation was changed.

This brings an end to this tutorial. You can download the project from the link below.


  1. David says:

    I have a Fragment which calls a service using StartService. When I use a FilePicker, naturally the Fragment is suspended and then must be restarted , but I don’t want to interrupt the service (its running a file sequence with static variables.) I am currently trying to rebind to the service without restarting it . Should I use onRestoreInstanceState to save the Service Intent instance handle ? In simple terms I want the Fragment to seamlessly re-engage with the service after it starts up again.
    Thanks, Anupam

  2. George says:

    Fantastic explanation! Thank you for such tutorials.

  3. Anik Kumar Bhushan says:

    Great tutorial on the use of onSaveInstanceState() and onRestoreInstanceState().
    It was very helpful.

  4. Rahul Nag says:

    The first edits text data has been saved although you have not used it inside the onSaveInstanceState and onRestoreInstanceState.
    is this due to that the first edit text has its id value but the second edit text don’t?

    1. sajal says:

      By default, Edittext save their own instance when changing orientation.

      Be sure that the 2 Edittexts have unique IDs and have the same IDs in both Layouts.

      That way, their state should be saved and you can let Android handle the orientation change.

      If you are using a fragment, be sure it has a unique ID also and you dont recreate it when recreating the Activity.

  5. lovely says:

    why dose the Phone Number field goes empty when the orientation was changed? please explain!!

Comments are closed.

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors