On Oct 7, 1:51 pm, Rmac <[EMAIL PROTECTED]> wrote: > My testing shows starting an external activity and then returning via > the back key only calls onResume, not onCreate. The screen > orientation change calls both onCreate and onResume on the originating > activity. It seems odd (maybe a design flaw, grin) that starting > another activity which in essence leaves my app causes less disruption > to the original activity than a process that rotates the screen while > I am STILL in my app.
No, it is behaving exactly as desired, the previous activity does not need to be re-created unless its process has to be killed while it is in the background in order to use its memory elsewhere. This is a fundamental part of the activity/application lifecycle on Android: http://code.google.com/android/intro/lifecycle.html --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
