Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Stabilize basic functionality of Modern Standby before proceeding to more advanced test scenarios, such as those involving an active Wi-Fi connection. First, validate entry to and exit from Modern Standby. Then, validate airplane mode and audio playback.
Required System Configuration
Ensure the following configurations are correct before performing any of the tests below:
- Factory image is installed on the system.
- All drivers are loaded in Device Manager.
- Factory Microsoft Store apps are installed.
- System is running on battery power.
- All Windows updates are installed.
Basic Entry and Exit Testing
Begin all testing by ensuring that the system can reliably enter Modern Standby and then exit Modern Standby after a variable duration. To initiate entry to Modern Standby, press the power button, close the lid, or select Sleep from the power button in the Settings flyout. These actions should instantly power off the display. To wake up the system, simply press the power button or open the lid of the system. These actions should instantly power on the display.
If the system is connected to a USB mouse or keyboard, move the mouse or press any key to generate a wake event and turn on the display.
The following table enumerates the Modern Standby entry and exit scenarios. All Modern Standby systems should be tested for expected behavior in each scenario.
- Test area: Entry to and exit from Modern Standby.
- Purpose: Ensure the system can reliably and quickly enter and exit Modern Standby.
- Additional system configuration requirements:
- None
| Test scenario | Expected result | Troubleshooting notes |
|---|---|---|
The system can enter Modern Standby using the following methods:
|
The system instantly transitions into Modern Standby (display powers off). No audio noises are generated. | If the system does not enter Modern Standby, a trace should be taken to diagnose the problem. See Capture and View a WPA Trace for Modern Standby Diagnostics for instructions on how to capture a trace and analyze the information. |
The system can enter Modern Standby using the following method:
|
The system transitions into display powers off. The time this takes is the sleep timeout minus the display timeout settings. (Audio player may still playback with Screen Off until pressing power button). | If the system does not enter Modern Standby when user specifically press power button to sleep, a trace should be taken to diagnose the problem. See Capture and View a WPA Trace for Modern Standby Diagnostics for instructions on how to capture a trace and analyze the information. |
The system can exit Modern Standby using the following methods:
|
The system instantly transitions out of Modern Standby (display powers on). Most failure cases in this category are the result of the system being unable to resume from Modern Standby. To debug, enable both the kernel debugger and the hardware debugger on the system to catch software crashes and hardware hard hangs, which can prevent the system from resuming. |
The Windows Hardware Lab Kit (HLK) includes Modern Standby tests that exercise entering and exiting Modern Standby on a system. Running the following tests will further validate the readiness of the system:
- Modern Standby basic verification test on AC-power
- Modern Standby basic verification test on DC-power
Basic Airplane Mode Testing
After verifying that the system can reliably enter and exit Modern Standby, validate system behavior during Modern Standby.
Modern Standby battery life is directly impacted by hardware and software activity. The goal of basic airplane mode testing is to identify activities that should not occur during Modern Standby and resolve them. These activities might be a result of software in the OEM pre-installation or unexpected hardware interrupts.
Start airplane mode testing with a one-hour Modern Standby session with airplane mode enabled. After resuming the system from Modern Standby, use SleepStudy to review the activities during the session and the amount of time that the system was in a low-power state.
- Test area: Airplane mode low-power state time.
- Purpose: Ensure that the basic activity level of the system is minimal (less than three percent of active time) with the factory image and apps installed.
- Additional system configuration requirements:
- System is put into airplane mode.
| Test scenario | Expected result | Troubleshooting notes |
|---|---|---|
| Stay in Modern Standby in airplane mode for at least one hour. | Using SleepStudy, observe that the system is in the lowest power state equal to or greater than 80 percent of the time. | SleepStudy helps identify which software or device component(s) are active, preventing the system from entering the lowest power state. Contact the owner of the offending component for debugging tips and next steps. |
To eliminate noise from system resource loading on boot, wait at least 5 minutes after system boot before testing. As a general guideline, all Modern Standby testing should be performed on a system running on DC power so that the power impact can be measured.
Basic Audio Playback Testing
Caution
Starting from Windows 11 version 24H2, audio playback is not supported when standby is entered explicitly (power button press, lid close, or through the start menu). Audio playback is only supported when idling to screen off.
Audio playback during Modern Standby enables the system to play music while screen off. The system is expected to consume less power when playing music in Modern Standby than when playing music with the display powered on. The goal of audio playback testing is to verify that the system can play sound through the internal speakers and headphones, and that the user can adjust the volume using the volume buttons during Modern Standby in a low-power state.
Start with a system that is un-muted and use the inbox Music app to play a 256-kilobits/second .mp3 track. Put the system into Modern Standby by idling to standby. Make sure that the sound continues to play through the speakers and that the volume can be adjusted through the volume buttons while the screen is powered off. Also, try plugging in headphones to ensure that the sound is transferred from the internal speakers to the headphones.
Not all USB, Bluetooth, HDMI, and other external devices support low-power audio. Low-power audio playback depends on the hardware and software support of the audio device.
For audio devices that do not support low-power playback, audio playback will continue after the power button is pressed, but at an increased power consumption compared to output through audio devices that support low-power playback.
Support for low-power audio for USB audio was added in Windows Version 1903. Bluetooth A2DP low-power audio is available starting from Windows 11 version 21H2. In Windows 11 version 24H2 and later, audio is supported when idling to screen off and will not play when standby is entered explicitly (power button press, lid close, or through the start menu).
All audio devices are expected to be able to play during Modern Standby using supported apps. The power consumption will depend on the hardware and driver support.
| Test scenario | Expected result | Troubleshooting notes |
|---|---|---|
When idling to Modern Standby, the system can play audio, and sound plays from:
|
The system continues to play sound through the speakers/headphones, and the volume can be adjusted using the volume buttons while the screen is powered off. Ensure that the system is consuming the expected power for low-power audio. Consult with the System on a Chip (SoC) vendor for the expected power consumption for low-power audio. | If the system fails to enter a low-power state, a trace is needed to diagnose the problem. For information about how to capture a trace and analyze the information, see Capture and View a WPA Trace for Modern Standby Diagnostics. If the audio stops when the screen is powered off, this usually means the music app does not have the background transfer API implemented correctly. |
Testing for low-power audio playback must be done on a system running on battery power so that the power impact can be accurately measured.