With the mobile world, people have come to expect instant-on, always connected devices. First it was smartphones, and then tablets based off of mobile operating systems which offered the ability to have the device in a deep sleep state, but still able to connect out to various services for notifications and app events.

With Windows 8, Microsoft brought this same always-on model to devices running Windows. It was a big change from the traditional ACPI Sleep states of S3 (Sleep) and S4 (Hibernate) which power down most of the system. Initially Connected Standby was only available on ARM based devices, but shortly after the launch of Windows 8 in October 2012, Clover Trail based tablets began to emerge which also supported this new sleep state. Connected Standby provides one big change over the traditional sleep and hibernate modes – it keeps networking devices powered on in a low power mode and allows apps and services to run in a restrained mode in order to run background tasks and process push notifications.

Clover Trail was a 32 bit CPU, so it wasn’t surprising that Connected Standby was limited to 32 bit installs of Windows, but since that launch a lot has happened in the x86 CPU landscape. First came Haswell, with a better efficiency than Ivy Bridge which it replaced, but more importantly for the tablet market, Bay Trail was launched. This was a big step up in performance for the Atom line, and Bay Trail is a 64 bit CPU. All tablets launched with Bay Trail came with a 32 bit install of Windows to enable Connected Standby. The 64 bit support was not there for any platform – Haswell or Bay Trail – and it has been a reason to hold tablets back with the 32 bit version of Windows.

In order to support Connected Standby, the entire system needs to be developed with the support in mind, as the following system requirements must be met:

Connected Standby System Requirements
  Requirements Motivation Responsibility
ACPI Flag The system ACPI firmware must set the ACPI_S0_LOW_POWER_IDLE FADT flag. Indicates the platform hardware supports the low-power idle mode for Connected Standby. System firmware developer
Core silicon / SoC must be capable of low-power idle.
ACPI namespace The system ACPI firmware must not provide an S3 object in the root of the namespace. Windows supports a platform that exposes either the S3 object or the ACPI_S0_LOW_POWER_IDLE FADT flag, but not both at the same time. System firmware developer
SoC The core silicon or SoC manufacturer must provide a Power Engine Plug-in (PEP). The PEP coordinates device state and processor idle state dependencies. A minimal PEP is required to communicate to Windows when the device power state dependencies have been achieved for the lowest SoC idle power mode. Core silicon / SoC provider
Windows 8.1 includes the PEP for Intel-based platforms.
Hibernate x86/x64-based Connected Standby PCs must also support Hibernate. Hibernate is used to save the state of desktop / Win32 applications when critical-low battery capacity is reached. System firmware developer
Network Stack All Built-In Networking Devices must be compatible with NDIS 6.3, specifically WoL Patterns, Protocol Offloads, and D0 Packet Coalescing. Enables the SoC to enter low-power modes while the networking device maintains connectivity. System designer (OEM/ODM)
Storage The primary storage volume must be solid-state and have a 0-millisecond seek penalty. Ensures that Windows can safely access the storage device any time during Connected Standby. System designer (OEM/ODM)

Today, we can confirm that Connected Standby is now available in 64 bit installs of Windows 8.1. Anand has confirmed that it is working in the new Surface Pro 3, and Intel has also confirmed to us that the drivers and firmware are complete to allow Connected Standby on Bay Trail-T processors. There has been some questions about the lack of support with some tablets such as the Lenovo ThinkPad 10 now offering a 64 bit install option, but assuming Lenovo has added all of the required pieces for Connected Standby, it should be available. The final result is still dependent on the OEM to choose the correct pieces, and ensure all necessary flags are set. Intel has confirmed that the HP ElitePad 1000 G2 is running Bay Trail-T x64 and has Connected Standby enabled.

With these developments, Intel based tablets can now offer the instant-on capabilities of smartphones, even with the 64 bit OS. AMD currently has no plans to support Connected Standby.

Source: Intel, Microsoft

POST A COMMENT

27 Comments

View All Comments

  • jhoff80 - Wednesday, May 21, 2014 - link

    As I mentioned above, the Pro 2 has a TPM 1.2 chip, which means that it can't get an update to use Connected Standby. Reply
  • Myrandex - Wednesday, May 21, 2014 - link

    My thoughts too. I would have thought that it would get that ability eventually. I also hoped that my Surface Pro 1 would get it eventually too, but probably not. Reply
  • bkev - Wednesday, May 21, 2014 - link

    This sounds conceptually similar to Apple's Power Nap. How different is the implementation from that technology? Reply
  • Brett Howse - Wednesday, May 21, 2014 - link

    Definitely similar, but Power Nap is restricted to certain functions that Apple has approved. And to get updates in Mail and Notes, they have to be left running when you put your system to sleep.

    Conceptually they are similar, but the implementations are quite different. Connected Standby gives instant resume, with Wi-Fi already connected. And the background tasks are not limited to system tasks, or 1st part tasks, because any app written in WinRT can support background tasks. Also background tasks can respond to a specific network event, which is why the networking stack is part of the system requirements. If not responding to a specific network event directed towards an app, the app gets CPU time no more than every 15 minutes.

    Apps on the lock screen are allowed extra time.

    So definitely similar in concept, but dissimilar in execution.
    Reply
  • Medallish - Wednesday, May 21, 2014 - link

    AMD afaik supports Connected standby in Mullins and Beema. Reply
  • Brett Howse - Wednesday, May 21, 2014 - link

    I linked to Anand's preview of Beema/Mullins and he said: "AMD sees no value in supporting Microsoft's Connected Standby standard at this point" Reply
  • MrSpadge - Wednesday, May 21, 2014 - link

    They could support it nevertheless ;) Reply
  • juhatus - Wednesday, May 21, 2014 - link

    On Sony Vaio Pro 13 (Haswell, I7-4500U, win 8.1 x64, no-lan, Intel 7260ac-wifi) I think this should qualify, but checking "powercfg /availablepowerstates" shows Standby (S3).
    Standby (Connected) - Firmware does not support.

    Was the support removed? I remember there being a Connected Standby - driver or such on Sony Updates.. Any way to enable?
    Reply
  • Klug4Pres - Wednesday, May 21, 2014 - link

    Connected Standby doesn't seem to be very well implemented in general. There are a lot of complaints about excessive battery drain, resulting in devices dying while asleep.

    Also, it is unfortunate that in Windows [8, 8.1], Connected Standby cannot co-exist with "legacy" sleep modes, e.g. Suspend-to-RAM aka ACPI S3, hibernation (ACPI S4), or hybrid sleep (combined S3 and backup S4). Some (but not all) machines have a "BIOS" switch that can signal to Windows whether you want to boot with the traditional sleep options or boot only with Connected Standby. I think it would be great to be able to choose as a standard feature and also without a reboot.
    Reply
  • eddman - Wednesday, May 21, 2014 - link

    Did you read the table?

    "x86/x64-based Connected Standby PCs must also support Hibernate."

    Also, from the SP3 preview article:

    http://images.anandtech.com/doci/8037/connectedsta...
    Reply

Log in

Don't have an account? Sign up now