CODEWITHSUNDEEP
androidandroid-activityonresume
MayTheSchwartzBeWithYou
MayTheSchwartzBeWithYou

Reputation: 1177

Why is onResume() called when an activity starts?

I have an app where after sign in it throws you at the welcome screen. I put a Toast to see when the onResume fires, but it also fires after onCreate

protected void onResume(){
    super.onResume();
    Database openHelper = new Database(this);//create new Database to take advantage of the SQLiteOpenHelper class
    myDB2 = openHelper.getReadableDatabase(); // or getWritableDatabase();
    myDB2=SQLiteDatabase.openDatabase("data/data/com.example.login2/databases/aeglea", null, SQLiteDatabase.OPEN_READONLY);//set myDB to aeglea
         cur = fetchOption("SELECT * FROM user_login");//use above to execute SQL query
         msg.setText("Username: "+cur.getString(cur.getColumnIndex("username"))
                     +"\nFull name: "+cur.getString(cur.getColumnIndex("name"))+" "+cur.getString(cur.getColumnIndex("last"))
                     +"\ne-mail: "+cur.getString(cur.getColumnIndex("email"))
                     +"\nAeglea id:"+cur.getString(cur.getColumnIndex("uid")));

         Toast.makeText(getApplicationContext(), "RESUMED", Toast.LENGTH_SHORT).show();
}

It comes from:

 //create new intent
 Intent log = new Intent(getApplicationContext(), Welcome.class);
 // Close all views before launching logged
  log.addFlags(Intent.FLAG_ACTIVITY_CLEAR_TOP);
  startActivity(log);
   // Close Login Screen
   finish();

I am baffled. Please offer some experience here

Upvotes: 8

Views: 15451

Answers (4)

Jorge Aguilar
Jorge Aguilar

Reputation: 3450

Well, I do not understand very well what you are trying to ask or what is the question here, but I will recommend you to read the Android Activity LifeCycle and that will clear many of your doubts cause in Android is not the same as other languages or platforms.

enter image description here

Note: The OnResume is called each time the activity is "visible", so as many times as your activity becomes visible, the same number of times your method will be called. If you just want to call the method the first time, then OnCreate is what you looking for.

Upvotes: 21

GeneCode
GeneCode

Reputation: 7588

Just to add a way around for this. Declare a variablel int intResume = 0; Then implement the following onResume:

@Override
    public void onResume()
    {
        super.onResume();
        intResume++;
        // here put codes for after onCreate & "true resume"

        if (intResume>1) {
            intResume = 10;
            // here put codes for "true resume"
        }
    }

Upvotes: 0

zapl
zapl

Reputation: 63955

onResume after onCreate is the normal Activity Lifecycle

The reason you get onStart and onResume called even on the first launch is that it makes writing code easier.

You can assume that before you return to onResume you will get onPause called since there is no way to exit the "resumed" state without onPause. That behavior can be used to initialize things in onResume and to de-initialize them without further checking in onPause. If you can't be sure that onResume was called at the start that whole scheme breaks.

On a sidenote: Don't access your database from any of the onXYZ methods since that will block the UI thread which should rather draw the UI and handle touch events.

Upvotes: 2

Ivo
Ivo

Reputation: 1788

Please take a look at the activity lifecycle state chart.

This is the order the methods are being called:

  1. onCreate()
  2. onStart()
  3. onResume()
  4. -> activity is running

http://developer.android.com/reference/android/app/Activity.html#ProcessLifecycle

Upvotes: 7

Related Questions