PowerManager

ACQUIRE_CAUSES_WAKEUP

static val ACQUIRE_CAUSES_WAKEUP: Int

Wake lock flag: Turn the screen on when the wake lock is acquired.

Normally wake locks don't actually wake the device, they just cause the screen to remain on once it's already on. Think of the video player application as the normal behavior. Notifications that pop up and want the device to be on are the exception; use this flag to be like them.

Cannot be used with PARTIAL_WAKE_LOCK.

Value: 268435456

ACTION_DEVICE_IDLE_MODE_CHANGED

static val ACTION_DEVICE_IDLE_MODE_CHANGED: String

Intent that is broadcast when the state of isDeviceIdleMode() changes. This broadcast is only sent to registered receivers.

Value: "android.os.action.DEVICE_IDLE_MODE_CHANGED"

ACTION_POWER_SAVE_MODE_CHANGED

static val ACTION_POWER_SAVE_MODE_CHANGED: String

Intent that is broadcast when the state of isPowerSaveMode() changes. This broadcast is only sent to registered receivers.

Value: "android.os.action.POWER_SAVE_MODE_CHANGED"

FULL_WAKE_LOCK

static val FULL_WAKE_LOCK: Int

Deprecated: Most applications should use android.view.WindowManager.LayoutParams#FLAG_KEEP_SCREEN_ON instead of this type of wake lock, as it will be correctly managed by the platform as the user moves between applications and doesn't require a special permission.

Wake lock level: Ensures that the screen and keyboard backlight are on at full brightness.

If the user presses the power button, then the FULL_WAKE_LOCK will be implicitly released by the system, causing both the screen and the CPU to be turned off. Contrast with PARTIAL_WAKE_LOCK.

Value: 26

LOCATION_MODE_ALL_DISABLED_WHEN_SCREEN_OFF

static val LOCATION_MODE_ALL_DISABLED_WHEN_SCREEN_OFF: Int

All location providers should be disabled when battery saver is on and the device is non-interactive.

Value: 2

LOCATION_MODE_FOREGROUND_ONLY

static val LOCATION_MODE_FOREGROUND_ONLY: Int

In this mode, all the location providers will be kept available, but location fixes should only be provided to foreground apps.

Value: 3

LOCATION_MODE_GPS_DISABLED_WHEN_SCREEN_OFF

static val LOCATION_MODE_GPS_DISABLED_WHEN_SCREEN_OFF: Int

In this mode, the GPS based location provider should be disabled when battery saver is on and the device is non-interactive.

Value: 1

LOCATION_MODE_NO_CHANGE

static val LOCATION_MODE_NO_CHANGE: Int

Either the location providers shouldn't be affected by battery saver, or battery saver is off.

Value: 0

LOCATION_MODE_THROTTLE_REQUESTS_WHEN_SCREEN_OFF

static val LOCATION_MODE_THROTTLE_REQUESTS_WHEN_SCREEN_OFF: Int

In this mode, location will not be turned off, but LocationManager will throttle all requests to providers when the device is non-interactive.

Value: 4

ON_AFTER_RELEASE

static val ON_AFTER_RELEASE: Int

Wake lock flag: When this wake lock is released, poke the user activity timer so the screen stays on for a little longer.

Will not turn the screen on if it is not already on. See ACQUIRE_CAUSES_WAKEUP if you want that.

Cannot be used with PARTIAL_WAKE_LOCK.

Value: 536870912

PARTIAL_WAKE_LOCK

static val PARTIAL_WAKE_LOCK: Int

Wake lock level: Ensures that the CPU is running; the screen and keyboard backlight will be allowed to go off.

If the user presses the power button, then the screen will be turned off but the CPU will be kept on until all partial wake locks have been released.

Value: 1

PROXIMITY_SCREEN_OFF_WAKE_LOCK

static val PROXIMITY_SCREEN_OFF_WAKE_LOCK: Int

Wake lock level: Turns the screen off when the proximity sensor activates.

If the proximity sensor detects that an object is nearby, the screen turns off immediately. Shortly after the object moves away, the screen turns on again.

A proximity wake lock does not prevent the device from falling asleep unlike FULL_WAKE_LOCK, SCREEN_BRIGHT_WAKE_LOCK and SCREEN_DIM_WAKE_LOCK. If there is no user activity and no other wake locks are held, then the device will fall asleep (and lock) as usual. However, the device will not fall asleep while the screen has been turned off by the proximity sensor because it effectively counts as ongoing user activity.

Since not all devices have proximity sensors, use isWakeLockLevelSupported to determine whether this wake lock level is supported.

Cannot be used with ACQUIRE_CAUSES_WAKEUP.

Value: 32

RELEASE_FLAG_WAIT_FOR_NO_PROXIMITY

static val RELEASE_FLAG_WAIT_FOR_NO_PROXIMITY: Int

Flag for WakeLock#release: Defer releasing a PROXIMITY_SCREEN_OFF_WAKE_LOCK wake lock until the proximity sensor indicates that an object is not in close proximity.

Value: 1

SCREEN_BRIGHT_WAKE_LOCK

static val SCREEN_BRIGHT_WAKE_LOCK: Int

Deprecated: Most applications should use android.view.WindowManager.LayoutParams#FLAG_KEEP_SCREEN_ON instead of this type of wake lock, as it will be correctly managed by the platform as the user moves between applications and doesn't require a special permission.

Wake lock level: Ensures that the screen is on at full brightness; the keyboard backlight will be allowed to go off.

If the user presses the power button, then the SCREEN_BRIGHT_WAKE_LOCK will be implicitly released by the system, causing both the screen and the CPU to be turned off. Contrast with PARTIAL_WAKE_LOCK.

Value: 10

SCREEN_DIM_WAKE_LOCK

static val SCREEN_DIM_WAKE_LOCK: Int

Deprecated: Most applications should use android.view.WindowManager.LayoutParams#FLAG_KEEP_SCREEN_ON instead of this type of wake lock, as it will be correctly managed by the platform as the user moves between applications and doesn't require a special permission.

Wake lock level: Ensures that the screen is on (but may be dimmed); the keyboard backlight will be allowed to go off.

If the user presses the power button, then the SCREEN_DIM_WAKE_LOCK will be implicitly released by the system, causing both the screen and the CPU to be turned off. Contrast with PARTIAL_WAKE_LOCK.

Value: 6

THERMAL_STATUS_CRITICAL

static val THERMAL_STATUS_CRITICAL: Int

Thermal status code: Platform has done everything to reduce power.

Value: 4

THERMAL_STATUS_EMERGENCY

static val THERMAL_STATUS_EMERGENCY: Int

Thermal status code: Key components in platform are shutting down due to thermal condition. Device functionalities will be limited.

Value: 5

THERMAL_STATUS_LIGHT

static val THERMAL_STATUS_LIGHT: Int

Thermal status code: Light throttling where UX is not impacted.

Value: 1

THERMAL_STATUS_MODERATE

static val THERMAL_STATUS_MODERATE: Int

Thermal status code: Moderate throttling where UX is not largely impacted.

Value: 2

THERMAL_STATUS_NONE

static val THERMAL_STATUS_NONE: Int

Thermal status code: Not under throttling.

Value: 0

THERMAL_STATUS_SEVERE

static val THERMAL_STATUS_SEVERE: Int

Thermal status code: Severe throttling where UX is largely impacted.

Value: 3

THERMAL_STATUS_SHUTDOWN

static val THERMAL_STATUS_SHUTDOWN: Int

Thermal status code: Need shutdown immediately.

Value: 6

addThermalStatusListener

fun addThermalStatusListener(listener: PowerManager.OnThermalStatusChangedListener): Unit

This function adds a listener for thermal status change, listen call back will be enqueued tasks on the main thread

addThermalStatusListener

fun addThermalStatusListener(
    executor: Executor, 
    listener: PowerManager.OnThermalStatusChangedListener
): Unit

This function adds a listener for thermal status change.

getCurrentThermalStatus

fun getCurrentThermalStatus(): Int

This function returns the current thermal status of the device.

getLocationPowerSaveMode

fun getLocationPowerSaveMode(): Int

Returns how location features should behave when battery saver is on. When battery saver is off, this will always return LOCATION_MODE_NO_CHANGE.

This API is normally only useful for components that provide location features.

getThermalHeadroom

fun getThermalHeadroom(forecastSeconds: Int): Float

Provides an estimate of how much thermal headroom the device currently has before hitting severe throttling. Note that this only attempts to track the headroom of slow-moving sensors, such as the skin temperature sensor. This means that there is no benefit to calling this function more frequently than about once per second, and attempts to call significantly more frequently may result in the function returning NaN.

In addition, in order to be able to provide an accurate forecast, the system does not attempt to forecast until it has multiple temperature samples from which to extrapolate. This should only take a few seconds from the time of the first call, but during this time, no forecasting will occur, and the current headroom will be returned regardless of the value of forecastSeconds.

The value returned is a non-negative float that represents how much of the thermal envelope is in use (or is forecasted to be in use). A value of 1.0 indicates that the device is (or will be) throttled at THERMAL_STATUS_SEVERE. Such throttling can affect the CPU, GPU, and other subsystems. Values may exceed 1.0, but there is no implied mapping to specific thermal status levels beyond that point. This means that values greater than 1.0 may correspond to THERMAL_STATUS_SEVERE, but may also represent heavier throttling.

A value of 0.0 corresponds to a fixed distance from 1.0, but does not correspond to any particular thermal status or temperature. Values on (0.0, 1.0] may be expected to scale linearly with temperature, though temperature changes over time are typically not linear. Negative values will be clamped to 0.0 before returning.

isDeviceIdleMode

fun isDeviceIdleMode(): Boolean

Returns true if the device is currently in idle mode. This happens when a device has been sitting unused and unmoving for a sufficiently long period of time, so that it decides to go into a lower power-use state. This may involve things like turning off network access to apps. You can monitor for changes to this state with ACTION_DEVICE_IDLE_MODE_CHANGED.

isIgnoringBatteryOptimizations

fun isIgnoringBatteryOptimizations(packageName: String!): Boolean

Return whether the given application package name is on the device's power whitelist. Apps can be placed on the whitelist through the settings UI invoked by android.provider.Settings#ACTION_IGNORE_BATTERY_OPTIMIZATION_SETTINGS.

isInteractive

fun isInteractive(): Boolean

Returns true if the device is in an interactive state.

When this method returns true, the device is awake and ready to interact with the user (although this is not a guarantee that the user is actively interacting with the device just this moment). The main screen is usually turned on while in this state. Certain features, such as the proximity sensor, may temporarily turn off the screen while still leaving the device in an interactive state. Note in particular that the device is still considered to be interactive while dreaming (since dreams can be interactive) but not when it is dozing or asleep.

When this method returns false, the device is dozing or asleep and must be awoken before it will become ready to interact with the user again. The main screen is usually turned off while in this state. Certain features, such as "ambient mode" may cause the main screen to remain on (albeit in a low power state) to display system-provided content while the device dozes.

The system will send a screen on or screen off broadcast whenever the interactive state of the device changes. For historical reasons, the names of these broadcasts refer to the power state of the screen but they are actually sent in response to changes in the overall interactive state of the device, as described by this method.

Services may use the non-interactive state as a hint to conserve power since the user is not present.

isPowerSaveMode

fun isPowerSaveMode(): Boolean

Returns true if the device is currently in power save mode. When in this mode, applications should reduce their functionality in order to conserve battery as much as possible. You can monitor for changes to this state with ACTION_POWER_SAVE_MODE_CHANGED.

isRebootingUserspaceSupported

fun isRebootingUserspaceSupported(): Boolean

Returns true if this device supports rebooting userspace.

isScreenOn

fun isScreenOn(): Boolean

Deprecated: Use isInteractive instead.

Returns true if the device is in an interactive state.

For historical reasons, the name of this method refers to the power state of the screen but it actually describes the overall interactive state of the device. This method has been replaced by isInteractive.

The value returned by this method only indicates whether the device is in an interactive state which may have nothing to do with the screen being on or off. To determine the actual state of the screen, use android.view.Display#getState.

isSustainedPerformanceModeSupported

fun isSustainedPerformanceModeSupported(): Boolean

This function checks if the device has implemented Sustained Performance Mode. This needs to be checked only once and is constant for a particular device/release. Sustained Performance Mode is intended to provide a consistent level of performance for prolonged amount of time. Applications should check if the device supports this mode, before using android.view.Window#setSustainedPerformanceMode.

isWakeLockLevelSupported

fun isWakeLockLevelSupported(level: Int): Boolean

Returns true if the specified wake lock level is supported.

newWakeLock

fun newWakeLock(
    levelAndFlags: Int, 
    tag: String!
): PowerManager.WakeLock!

Creates a new wake lock with the specified level and flags.

The levelAndFlags parameter specifies a wake lock level and optional flags combined using the logical OR operator.

The wake lock levels are: PARTIAL_WAKE_LOCK, FULL_WAKE_LOCK, SCREEN_DIM_WAKE_LOCK and SCREEN_BRIGHT_WAKE_LOCK. Exactly one wake lock level must be specified as part of the levelAndFlags parameter.

The wake lock flags are: ACQUIRE_CAUSES_WAKEUP and ON_AFTER_RELEASE. Multiple flags can be combined as part of the levelAndFlags parameters.

Call WakeLock#acquire() on the object to acquire the wake lock, and WakeLock#release when you are done.

{@samplecode * PowerManager pm = (PowerManager)mContext.getSystemService( * Context.POWER_SERVICE); * PowerManager.WakeLock wl = pm.newWakeLock( * PowerManager.SCREEN_DIM_WAKE_LOCK * | PowerManager.ON_AFTER_RELEASE, * TAG); * wl.acquire(); * // ... do work... * wl.release(); * }

Although a wake lock can be created without special permissions, the android.Manifest.permission#WAKE_LOCK permission is required to actually acquire or release the wake lock that is returned.

If using this to keep the screen on, you should strongly consider using android.view.WindowManager.LayoutParams#FLAG_KEEP_SCREEN_ON instead. This window flag will be correctly managed by the platform as the user moves between applications and doesn't require a special permission.

Recommended naming conventions for tags to make debugging easier:

• use a unique prefix delimited by a colon for your app/library (e.g. gmail:mytag) to make it easier to understand where the wake locks comes from. This namespace will also avoid collision for tags inside your app coming from different libraries which will make debugging easier.
• use constants (e.g. do not include timestamps in the tag) to make it easier for tools to aggregate similar wake locks. When collecting debugging data, the platform only monitors a finite number of tags, using constants will help tools to provide better debugging data.
• avoid using Class#getName() or similar method since this class name can be transformed by java optimizer and obfuscator tools.
• avoid wrapping the tag or a prefix to avoid collision with wake lock tags from the platform (e.g. *alarm*).
• never include personnally identifiable information for privacy reasons.

reboot

fun reboot(reason: String?): Unit

Reboot the device. Will not return if the reboot is successful.

Requires the android.Manifest.permission#REBOOT permission.

removeThermalStatusListener

fun removeThermalStatusListener(listener: PowerManager.OnThermalStatusChangedListener): Unit

This function removes a listener for thermal status change