Android: onCreate() getting called multiple times (and not by me)

There is something I don't quite understand right now.

My main activity class creates a Service, which creates a new thread that waits for a TCP connection. Once one comes in, it will start a new activity:

Intent dialogIntent = new Intent(getBaseContext(), VoIPCall.class);
dialogIntent.putExtra("inetAddress", clientSocket.getInetAddress());
dialogIntent.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
getApplication().startActivity(dialogIntent);

After that, the onCreate() method of that class gets run. It will create 2 threads: one records and send data, the other one receive a开发者_Python百科nd plays data. Those threads have a forever while loop.

For some reason, I notice that the onCreate() of that last class gets called again, which makes my program crash. I do not understand why it is called again as only the 2 threads are running, there is no user interaction. The documentation says: "Called when the activity is first created.". The activity is already running and I am not trying to create it.

Could someone please explain me this behavior?

Android will recreate your activity after certain "device configuration changes". One such example is orientation. You can read more here... http://developer.android.com/guide/topics/resources/runtime-changes.html

Perhaps something in your threads is doing something which is considered a configuration change?

If that's the case you might find it useful to extend the Application class instead and do your initialization there. See this post... Activity restart on rotation Android

HTH

I was experiencing an Activity called twice on some Samsung devices. I solved it adding android:launchMode = "singleInstance" on the Activity tag on Manifest. I hope this can help.

Similar to this question where orientation change is causing the device to reconfigure:

Activity restart on rotation Android

My preferred answer:

https://stackoverflow.com/a/11811999/3739540

Instead of trying to stop the onCreate() from being fired altogether, maybe try checking the Bundle savedInstanceState being passed into the event to see if it is null or not.

For instance, if I have some logic that should be run when the Activity is truly created, not on every orientation change, I only run that logic in the onCreate() only if the savedInstanceState is null.

Otherwise, I still want the layout to redraw properly for the orientation.

public void onCreate(Bundle savedInstanceState) {

    super.onCreate(savedInstanceState);

    setContentView(R.layout.activity_game_list);

    if(savedInstanceState == null){
        setupCloudMessaging();
    }
}

This happened to me once when I used "Don't save actions" in the app section of the developer options. Be sure you have turned this off.

I have observed this issue when you are trying start an activity with values in the intent.

Below is an example where Activity_A calls Activity_B and passes values in the intent to be collected in Activity_B:

Intent intent = new Intent(this, activityB.class);
intent.putExtra("val1", someValue1);
intent.putExtra("val2", someValue2);
intent.putExtra("val3", someValue3);
this.StartActivity(intent);

In this case, you can set the android:launchMode="singleInstance" or android:launchModel="singleTop" in your AndroidManifest.xml and Activity_B will only launch once. Hope this helps.