Added in API level 1

ComponentCallbacks


public interface ComponentCallbacks

android.content.ComponentCallbacks


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

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

Summary

Public methods

abstract void onConfigurationChanged(Configuration newConfig)

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

abstract void onLowMemory()

This method was deprecated in API level 35. 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.

Public methods

onConfigurationChanged

Added in API level 1
public abstract void onConfigurationChanged (Configuration newConfig)

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
public abstract void onLowMemory ()

This method was deprecated in API level 35.
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.