Android - Message
Download as PPTX, PDF0 likes430 views
1. The document discusses the Android application lifecycle and how activities can transition between different states like onCreate, onStart, onResume, onPause, onStop, and onDestroy. 2. It also covers the activity lifecycle methods and how they relate to different states, as well as how to save and restore activity instance states. 3. Additionally, it provides comparisons between the Android and Windows lifecycles and messaging systems, and introduces concepts like handlers, loopers, threads, and the context class in Android.
![Android –
Message
Yong Heui Cho @ Mokwon University
Some of slides are referred to:
[1] Nitin Ramchandani, Android OS, slideshare.](https://image.slidesharecdn.com/4-200205024819/85/Android-Message-1-320.jpg)
Android - Message
- 1. Android – Message Yong Heui Cho @ Mokwon University Some of slides are referred to: [1] Nitin Ramchandani, Android OS, slideshare.
- 3. 3 Application Lifecycle I. In Android, every application runs in their own process. II. Processes are started or stopped as needed to run application components. III. A process may be killed to reclaim resources. □ Courtesy to Nitin Ramchandani, Android OS, slideshare.
- 5. 5 • onCreate(Bundle): This is called when the activity first starts up. •onStart( ): This indicates the activity is about to be displayed to the user. • onResume( ): This is called when your activity can start interacting with the user. This is a good place to start animations and music. • onPause( ): This runs when the activity is about to go into the background, usually because another activity has been launched in front of it. This is where you should save your program’s persistent state, such as a database record being edited. Activity Lifecycle (II) □ Courtesy to Nitin Ramchandani, Android OS, slideshare.
- 6. 6 • onStop( ): This is called when your activity is no longer visible to the user and it won’t be needed for a while. If memory is tight, onStop( ) may never be called (the system may simply terminate your process). • onRestart( ): If this method is called, it indicates your activity is being redisplayed to the user from a stopped state. • onDestroy( ): This is called right before your activity is destroyed. If memory is tight, onDestroy( ) may never be called (the system may simply terminate your process). Activity Lifecycle (III) □ Courtesy to Nitin Ramchandani, Android OS, slideshare.
- 7. 7 •onSaveInstanceState(Bundle): Android will call this method to allow the activity to save per-instance state, such as a cursor position within a text field. Usually you won’t need to override it because the default implementation saves the state for all your user interface controls automatically. • onRestoreInstanceState(Bundle): This is called when the activity is being reinitialized from a state previously saved by the onSaveInstanceState( ) method. The default implementation restores the state of your user interface. Save & Restore □ Courtesy to Nitin Ramchandani, Android OS, slideshare.
- 8. 8 Lifecycle Comparison Run Terminate onCreate() onDestroy() onStart() onStop() onResume() onPause() onRestart() - onRestoreInstanceState() onSaveInstanceState()
- 10. 10 Android vs. Windows type Android Windows CPU optimal fast battery small power supply memory mobile DRAM small DRAM large message handler message (Message) or action (String) message (int) termination app lifecycle permanent function call call & proceed call & wait or call & proceed
- 12. 12 Android Msg Handler • Message: containing a description and arbitrary data object • Runnable: a command that can be executed • Handler: allows you to send and process Message and Runnable • Looper: used to run a message loop for a thread
- 14. 14 Android Rules • Do not block the UI thread (or main thread). • Do not access the Android UI toolkit from outside the UI thread.
- 15. 15 Context • Interface to global information about an application environment • Uses of context – Creating new objects – Accessing standard common resources – Accessing components implicitly Activity Context OS
- 16. 16 Access of Context • this – Activity extends Context • View.getContext() – Context for View (usually Activity Context) • Activity.getApplicationContext() – Permanent Application Context • ContextWrapper.getBaseContext() – Access to another Context