[align=center]The Activity-LifeCycle

since SDK v0.9 the neming of the "states" is a bit different, however the overall 'way' is the same
@Source

If you have problems understanding or other questions, post right below...

[/align]

Regards,
plusminus

Could someone elaborate a little bit with examples of how these might get used? This kind of lifecycle is a little bit new to me...and having 8 stages complicates things a little bit (onStart and onStop would be straightforward...onCreate onStart onResume etc. starts to get a little hairy...)

Could someone give some examples in which all of these get used? Or just a few examples that collectively use all of them? I'm just trying to wrap my brain around what questions I need to ask myself when writing an Android app to implement the lifecycle. Thanks in advance!

Hi
I suggest you might implement all callback functions of life cycle:

onCreate(), onStart(), onResume(), onFreeze(), onPause(), onStop() and onDestroy().

Set breakpoint for each callback functions and start the activity with eclipse debugger.
Then you could operate some actions on that activity, see how state life state goes.

I wrote new article (+ tutorial) about an essence of Activity. There's an explanation of return some value from Activity in the tutotial. Article wrote on russian language Here you can look it and download source code of tutorial - http://www.maximyudin.com/?p=12

Thanks mr. plusmius for ur digram, it help me alot ^^

Ghalya wrote:Thanks mr. plusmius for ur digram, it help me alot ^^

Its the original one from Google but obviously seems a bit hidden .)

Regards,
plusminus

hi all,
picking up on the lifecycle question, can anybody explain to me when onSaveInstanceState is called?

i have a test activity that implements onSaveInstanceState, but it is never called, and consequently the bundle in oncreate is always null.

what i do is:

start application
- onCreate
- onStart
- onResume

press back
- onPause
- onStop
- onDestroy

(no onSaveInstanceState called)

start again
- onCreate
- onStart
- onResume

press home
- onPause
- onStop

(no onSaveInstanceState called)

if onSaveInstanceState is not called in any of these instances, when is it called?

onSaveInstanceState() is called when a configuration change happens. That means: "Unless you specify otherwise, a configuration change (such as a change in screen orientation, language, input devices, etc) will cause your current activity to be destroyed, going through the normal activity lifecycle process of onPause(), onStop(), and onDestroy() as appropriate. If the activity had been in the foreground or visible to the user, once onDestroy() is called in that instance then a new instance of the activity will be created, with whatever savedInstanceState the previous instance had generated from onSaveInstanceState(Bundle)." (From the docs).

Hi all,

here is video illustrator about life cycle of andorid apps, you can get source code by svn:
http://blip.tv/file/958450/

more detail:
http://sleepydroid.blogspot.com/

Regard,

thnxs

CAn anyone explain,who manages the lifecycle of Activity,
as in J2me AMS is there,
once we run the activity,
who calls the instance of activity and how it initializes the Activity

there is a tutorial illustrate the life cycle in activity from developer.android.com

see this:http://developer.android.com/resources/tutorials/notepad/index.html

Here is the official explanation from Google. Most of this information is already posted, but here is the link http://developer.android.com/reference/ ... ivity.html

Thank you for all videos and pictures! I've just started and now i've finally understood lifecycles!!

If I do not take care to clean up properly, is it possible that my code will create multiple instances of certain objects? I'm having a problem where the application will progressively get slower each time you run it.