Table of contents
TOC
Collapse the table of content
Expand the table of content

Prepare software for modern standby

Last Updated: 1/24/2017

On entry to modern standby, apps and system software must be made ready for the transition to low-power operation. Powering down the display is the first activity when entering standby. The display is turned off in response to the user pressing the power button, closing the lid, or selecting Sleep from the power button in the Settings charm.

Software preparation phases

After the display is powered off, Windows transitions through a set of phases to prepare apps and system software for achieving low power. The phases are sequential—each phase is a set of activities that must be performed before the phase can be completed and the next phase entered.

The purpose of these phases is to stop or reduce as much software activity on the system as possible. This reduction in activity gives more opportunity for the hardware to enter low-power modes, thereby extending overall modern connected standby battery life.

The following table describes each phase of preparing software for modern standby.

TopicsDescriptionTasks performedExited when...Typical duration (seconds)

No-CS phase

Note This is also the phase where the device waits for the sleep timeout to elapse.

The system is powered on and the screen is turned on. The system is not in standby.

No standby preparation tasks are being performed.

The screen is powered down.

N/A

Connection phase

The system is checking for remote desktop connections.

  • Determine if remote desktop session(s) exist.
  • Begin tracking outstanding power requests.

There are no remote desktop sessions connected.

  • Zero seconds if no remote desktop sessions are connected.
  • Phase will last until all remote desktop sessions are disconnected or have timed out.

Presence phase

This phase is currently not used by Windows 8 or Windows 8.1.

Process Lifetime Manager (PLM) phase

The system suspends Windows Store apps that are in the foreground.

  • Suspend all foreground Windows Store apps.
  • Check for ongoing non-offloaded audio playback or communications app activity.

All foreground Windows Store apps have been suspended and no non-offloaded audio playback is occurring.

  • Typically, less than five seconds.
  • If non-offloaded audio playback is ongoing, this phase will block until audio playback stops.
  • Audio playback may be part of a music or communications app.

Maintenance phase

The system executes maintenance tasks.

Wait for maintenance tasks to complete if running (most common on AC power).

No system maintenance tasks are running.

  • Typically, less than one second.
  • The system is most likely to block on maintenance phase on AC power.

Desktop Activity Moderator (DAM) phase

The system pauses desktop applications to reduce their power consumption during standby.

  • Check for outstanding power requests (PowerRequestExecutionRequired).
  • Wait for outstanding power requests to be dropped by the application, or enforce a maximum time-out on battery power (five minutes).

All outstanding power requests have been cleared by applications or the maximum time-out has been reached.

  • Typically, zero seconds.
  • If the system is on battery power, outstanding power requests will cause this phase to block for a maximum of five minutes. The applications with power requests can be inspected by running Powercfg.exe with the /requests option.
  • If the system is on AC power, outstanding power requests will cause this phase to block indefinitely or until the power request is cleared by the application.

Low-power phase

The system notifies registered subscribers that the power manager is entering a low-power, long-resume-latency phase. This is used by some devices as a hint to power down.

Notify registered subscribers.

All registered subscribers have been notified.

Typically, five seconds.

Resiliency notification phase

The network subsystem is notified to enter a low-power mode.

Notify the network subsystem. Network adapters that do not support modern connected standby are turned off (D3).

The network subsystem has been notified.

Typically, less than one second.

Resiliency phase

The system is ready for the SoC to enter the lowest power mode and remain idle.

  • PDC resiliency clients are notified that the system is in resiliency phase.
  • Session-0 services are throttled by the DAM to no more than one second of activity every 30 seconds.
  • The power manager waits for activators to turn on their reference and cause the system to remain active.

  • The system exits standby due to user input or a power button press.
  • The system transitions to maintenance phase to run system maintenance.

The majority of time the system is in standby.

After Windows has entered the resiliency phase, software is considered to be fully prepared for low-power operation. As soon as all devices have entered their low-power modes, the SoC and core chipset will enter the lowest idle power mode, as described in Prepare Hardware for Modern Standby.

Note Currently, no means is available to system designers to change or influence the behavior of these phases—they are a core part of Windows behavior. The details are explained here to aid in system debugging and development.

Desktop activity moderator

The desktop activity moderator (DAM) is the Windows component that is used to pause all desktop applications and throttle the runtime of third-party system services. The purpose of the DAM is to enable basic software compatibility with existing applications and services, but mitigate their impact on battery life during standby.

Windows prevents desktop applications from running during any part of modern standby after completing the DAM phase. Windows allows third-party system services to execute in a throttled mode after completing the DAM phase.

© 2017 Microsoft