Added in API level 1

ComponentCallbacks


interface ComponentCallbacks
android.content.ComponentCallbacks

The set of callback APIs that are common to all application components (android.app.Activity, android.app.Service, ContentProvider, and android.app.Application).

Note: You should also implement the ComponentCallbacks2 interface, which provides the android.content.ComponentCallbacks2#onTrimMemory callback to help your app manage its memory usage more effectively.

Summary

Public methods
abstract Unit

Called by the system when the device configuration changes while your component is running.

abstract Unit

This is called when the overall system is running low on memory, and actively running processes should trim their memory usage.

Public methods

onConfigurationChanged

Added in API level 1
abstract fun onConfigurationChanged(newConfig: Configuration): Unit

Called by the system when the device configuration changes while your component is running. Note that, unlike activities, other components are never restarted when a configuration changes: they must always deal with the results of the change, such as by re-retrieving resources.

At the time that this function has been called, your Resources object will have been updated to return resource values matching the new configuration.

For more information, read Handling Runtime Changes.

Parameters
newConfig Configuration: The new device configuration. This value cannot be null.

onLowMemory

Added in API level 1
Deprecated in API level 35
abstract fun onLowMemory(): Unit

Deprecated: Since API level 14 this is superseded by ComponentCallbacks2#onTrimMemory. Since API level 34 this is never called. Apps targeting API level 34 and above may provide an empty implementation.

This is called when the overall system is running low on memory, and actively running processes should trim their memory usage. While the exact point at which this will be called is not defined, generally it will happen when all background process have been killed. That is, before reaching the point of killing processes hosting service and foreground UI that we would like to avoid killing.