Connected standby basic test scenarios

Stabilize basic connected standby functionality before progressing to more advanced test scenarios, such as those that have an active Wi-Fi connection. First, validate entry to and exit from connected standby. Then validate airplane mode and audio playback.

Basic entry and exit testing

You should begin all testing by making sure that the system can reliably enter connected standby, and then exit connected standby after some interval of variable duration. To initiate entry to connected 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 to the system and turn the display on.

The connected standby entry and exit scenarios are enumerated in the following table. All connected standby systems should be tested for expected behavior in each scenario.

  • Test area: Entry to and exit from connected standby.
  • Purpose: Ensure system can reliably and quickly enter and exit connected standby.
  • System configuration:
    • Factory image is installed on the system.
    • All drivers are loaded in Device Manager.
    • Factory Windows Store apps are installed.
    • System is on battery power.
Test scenarioExpected resultTroubleshooting notes

The system can enter connected standby using the following methods:

  • Press the power button.
  • Select Sleep from the operating system settings.
  • Close the lid (if applicable).

The system instantly transitions into connected standby (display powers off).

No audio noises are generated.

If the system does not enter connected standby, a trace should be taken to diagnose the problem. See Capture and View a WPA Trace for Connected Standby Diagnostics for instructions on how to capture a trace and analyze the information.
The system can exit connected standby using the following methods:
  • Press the power button.
  • Open the lid (if applicable).
  • Use a USB mouse or keyboard.

The system instantly transitions out of connected standby (display powers on).

No audio noises are generated.

Most failure cases in this category are the result of the system being unable to resume from connected standby.

To debug, you must 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 Certification Kit (HCK) includes connected standby tests that exercise entering and exiting connected standby on a system. Running the following tests will further validate the readiness of the system:

  • Connected standby exit latency test
  • Connected standby duration test
  • Connected standby stress with I/O

Basic airplane mode testing

After you have verified that the system can reliably enter and exit connected standby, you can validate system behavior during connected standby.

Connected 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 be happening during connected 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 connected standby session with airplane mode enabled. After resuming the system from connected 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 factory image and apps installed.
  • System configuration:
    • Factory image is installed on the system.
    • All drivers are loaded in Device Manager.
    • Factory Windows Store apps are installed.
    • System is on battery power.
    • System is put into airplane mode.
Test scenarioExpected resultTroubleshooting notes
Stay in connected 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 97 percent of the time.Using SleepStudy, you can see which software or device component(s) is active, which prevents 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, we recommend that you wait at least 90 seconds after system boot before you start testing. As a general guideline, all connected standby testing should be performed on a system that is running on DC power to so that the power impact can be measured.

Basic audio playback testing

Audio playback during connected standby enables the system to play music while the display is powered off. The system is expected to consume less power when playing music in connected standby than playing music when the display is powered on. The goal of audio playback testing is to make sure that the system can play sound through the internal speakers and headphones, and that the user can adjust the volume by using the volume buttons during connected 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 connected 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. You should also try to plug in a headphone to make sure that the sound gets transferred from the internal speakers to the headphones.

Note  USB, Bluetooth, HDMI and other external devices are not supported for low-power audio. Audio playback will continue after the power button is pressed for USB, Bluetooth, and HDMI output, but at an increased power consumption compared to output through the system power jack or the built-in speakers.

  • Test area: Screen-off audio playback operation and power.
  • Purpose: Ensure that audio playback continues without interruption when the power button is pressed during low power consumption.
  • System configuration:
    • Factory image is installed on the system.
    • All drivers are loaded in Device Manager.
    • Factory Windows Store apps are installed.
    • System is on battery power.
    • Headphones are available to test output from headphone jack.
Test scenarioExpected resultTroubleshooting notes

The system can play audio during connected standby, and sound plays from:

  • Internal speakers
  • Headphones

The system continues to play sound through the speakers/headphones and the volume can be adjusted by using the volume buttons while the screen is powered off.

Ensure that system is consuming the power expected for low-power audio. Consult with your 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 Connected 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. For more information about this API, see Writing a power savvy background media app.

 

Testing for low-power audio playback must be done on a system that is running on battery power so that the power impact can be accurately measured.

 

 

Send comments about this topic to Microsoft

Afficher:
© 2014 Microsoft