Full desktop apps won’t burn the battery
Qualcomm and Microsoft’s partnership to bring Windows 10 to Qualcomm Snapdragon-powered laptops has promised always-connected laptops and day-long battery lives – but the worry was that would come at a price to longevity.
However, Qualcomm has now revealed that running standard Windows 10 desktop programs shouldn’t affect that impressive battery life too much.
(Update: Qualcomm got back to us explaining more about how Win32 apps will be handled, and why they won’t significantly impact battery life.)
We were previously led to believe that to benefit from the 20 or more hours’ battery life, owners of Windows 10 on Snapdragon (also known as Windows on ARM) devices would need to stick to UWP (Universal Windows Platform) apps.
These are apps downloaded from the Microsoft Store, and Windows 10 S, which Windows on Snapdragon devices run by default, is a locked-down version of Windows 10 that can only run those apps.
While some standard Windows 10 programs have UWP versions, many more do not, which meant some people worried that you would either be stuck without some of the desktop applications you rely on, or suffer from worse battery life.
Full apps, full battery
However, in a report published on Neowin, PJ Jacobowitz, a representative from Qualcomm, suggested that performance and battery life impact would be the same as if it was running on a PC with an Intel processor.
Neowin doesn’t supply the exact quote, so we’re not entirely clear what this means. However, many are interpreting it to mean that there won’t be a significant impact on battery life if you run full desktop programs – also known as Win32 applications.
Because Win32 applications require more power (and will be run with emulation in Windows 10 S) many thought they would further impact battery life with Windows on Snapdragon systems.
The report seems to dispute that, but the wording is ambiguous. It suggests Win32 applications will run as well as if they were running on a standard Intel machine, and will use the same amount of power.
So, these applications will still deplete the battery life faster than a UWP app might, but due to emulation not being an issue, the impact shouldn’t be as much as we feared.
We contacted Qualcomm to get clarification and we were told that “there’s a combination of things that allow Win32 apps to not significantly impact battery life. One of the major contributors is our efficient Adreno graphics core.
“Being a native GPU, we actually need less cycles/time in the same workloads as opposed to running on X86. Also in the case of running apps that don’t need much CPU, because of the ARM big.LITTLE architecture, we can light up the smaller cores for those workloads. [It] also helps that we’ve tight integration across our SoC, so we can distribute workloads across CPU/GPU/DSP/ISP”.
The big.LITTLE architecture Qualcomm refers to is the ability of a multi-core processor to be able to switch between slower, and more energy efficient (and therefore less battery intensive) cores (LITTLE), with faster and more powerful cores (big) depending on the workload. This clever switching between cores can help keep the impact on the battery down while running Win32 apps.