Cute baby wallpaper, cute babies

Cute baby wallpaper, cute babies, cute babies wallpapers, cute babies wallpaper, cute baby pictures, cute baby wallpapers, baby wallpaper, babies wallpaper, cute babies pictures, baby cute wallpaper

• Tweet

Beach of hdwallpaper, hd beach wallpapers

Beach of hdwallpaper, hd beach wallpapers, free beach wallpaper, beach wallpaper hd, hd beach wallpaper, beach hd wallpaper, free computer wallpaper, free spring wallpaper, desktop wallpaper

• Tweet

Animated desktop wallpaper, animated wallpapers for desktop

Animated desktop wallpaper, animated wallpapers for desktop, free animated desktop wallpaper, animated desktop wallpapers, free animated desktop wallpapers, animated desktop background, desktop wallpaper free, free desktop wallpaper

• Tweet

Simulate kill activity to test onSaveInstanceState() / onCreate()

In order to test the lifecycle behaviour of our apps, we always have to leave our apps to move it to background, wait sometime for the system to kill it...and restart it.

It's a alternative to simulate "kill activity" by the Immediately destroy activities (or called Don't keep activities/Do not keep activities) selection Development Settings:

Select Developer options in Setting

According to the Android Developer document of Using the Dev Tools App:

Immediately destroy activities
Tells the system to destroy an activity as soon as it is stopped (as if Android had to reclaim memory). This is very useful for testing the onSaveInstanceState(Bundle) / onCreate(android.os.Bundle) code path, which would otherwise be difficult to force. Choosing this option will probably reveal a number of problems in your application due to not saving state. For more information about saving an activity's state, see the Activities document.

Notice: This setting for developers only, NOT for general user.

---

Related: The lifecycle in Activity Killed

• Tweet