Probably the Metro Apps are not x64 though I could be wrong so how do they play into this equation since x32 apps can be a no no if we want a successful experience with Connected Standby?
And if Connected Standby is shaky out of the gate would this maybe be something better disabled until it becomes stable? I know it isn't time to cross that bridge yet but just asking...
For the most part Connected Standby is just a fancy sleep where the main difference between Sleep (S3) and CS is that the latter keeps network connectivity ON in a very low power mode and has the ability to wake the system. The main (only?) reason it uses less power because the hardware is simply better and optimized for CS.One other piece everyone is ignoring the i3 is a Connected Standby SoC which increase battery life, run cooler and quieter.....
I have no way of verifying it, but I have every reason to believe if one were to test "Sleep" and "CS" on the *exact same hardware*, sleep would come out slightly ahead.The traditional Sleep (ACPI S3) state consumes 500 milliwatts or more of average power consumption to maintain memory in self-refresh and allow the platform to wake on user input. This gives the typical mobile system with a 45-watt-hour battery just under 100 hours of Sleep time on a full charge. However, Connected Standby systems use low-power memory and power-optimized embedded controllers to consume less than 150 milliwatts in most configurations. This allows the typical platform to remain in Sleep for 300 hours on a full battery charge—3 times longer than the traditional Sleep state.