gaspersic/freeCodeCamp
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

This method also cleanup the resources such as threads so that application runs smooth. (#32340)

Browse Source
This commit is contained in:
CodeStrike
2019-05-12 22:13:47 +05:30
committed by Christopher McCormack
parent 0308cd3f9c
commit 42f565dd04
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
guide/english/android-development/core-components/index.md
View File

@ -45,14 +45,18 @@ An activity facilitates the following key interactions between system and app:
> Called when an activity is no longer visible to the user. You will next receive either onRestart(), onDestroy(), or nothing, depending on subsequent user activity.
>Note that this method may never be called, in low memory situations where the system does not have enough memory to keep your activity's process running after its onPause() method is called.
> Note that this method may never be called, in low memory situations where the system does not have enough memory to keep your activity's process running after its onPause() method is called.
* onDestroy():
> The final call you receive before your activity is destroyed. This can happen either because the activity is finishing (someone called finish() on it), or because the system is temporarily destroying this instance of the activity to save space. You can distinguish between these two scenarios with the isFinishing() method.
This call is often used when the user hits the back button, or closes the instance of the app.
Interestingly, when app display changes orientation (e.g., from landscape to portrait or the other way around), `onDestroy()` and `onCreate()` are called. This means that the Activity is recreated. This comes in handy in applications with different defined rules for landscape and portrait modes, or with different views defined for tablets and phones in these modes.
This method also cleanup the resources such as threads so that application runs smooth.
#### Sample code to understand Activity Lifecycle
You can print in log console using Log.d() method.