onCreate

Note that this can be called while the fragment's activity is
still in the process of being created. As such, you can not rely
on things like the activity's content view hierarchy being initialized
at this point. If you want to do work once the activity itself is
created, see onActivityCreated(Bundle).

Any restored child fragments will be created before the base
Fragment.onCreate method returns.

Parameters

savedInstanceState

Bundle: If the fragment is being re-created from
a previous saved state, this is the state.

A default View can be returned by calling Fragment(int) in your
constructor. Otherwise, this method returns null.

It is recommended to only inflate the layout in this method and move
logic that operates on the returned View to onViewCreated(View, Bundle).

If you return a View from here, you will later be called in
onDestroyView() when the view is being released.

Parameters

inflater

LayoutInflater: The LayoutInflater object that can be used to inflate
any views in the fragment,

container

ViewGroup: If non-null, this is the parent view that the fragment's
UI should be attached to. The fragment should not add the view itself,
but this can be used to generate the LayoutParams of the view.

savedInstanceState

Bundle: If non-null, this fragment is being re-constructed
from a previous saved state as given here.

This corresponds to Activity.onSaveInstanceState(Bundle) and most of the discussion there
applies here as well. Note however: this method may be called
at any time before onDestroy(). There are many situations
where a fragment may be mostly torn down (such as when placed on the
back stack with no UI showing), but its state will not be saved until
its owning activity actually needs to save its state.

Parameters

outState

Bundle: Bundle in which to place your saved state.

onStart

public void onStart ()

Called when the Fragment is visible to the user. This is generally
tied to Activity.onStart of the containing
Activity's lifecycle.

onStop

public void onStop ()

Called when the Fragment is no longer started. This is generally
tied to Activity.onStop of the containing
Activity's lifecycle.

onViewCreated

Called immediately after onCreateView(LayoutInflater, ViewGroup, Bundle)
has returned, but before any saved state has been restored in to the view.
This gives subclasses a chance to initialize themselves once
they know their view hierarchy has been completely created. The fragment's
view hierarchy is not however attached to its parent at this point.