When the specs are the same, Windows Phone has better battery life than Android

Yesterday, HTC announced that they would begin selling a Windows Phone variant of their HTC One M8 smartphone. Seeing that the hardware is identical to that of Android version, the best test of performance is to see how long the battery will last when using the device.

Both devices have a 2600 mAh battery, the same 2.3 Ghz quad core processor, same display, same everything. What is different between the two devices is the battery life.

The Windows Phone version is stated to have talk time of 22 hrs and standby time of 528 hrs whereas the Android version is stated to have 20 hrs of talk time and 496 hours standby time. These figures were pulled from HTCs website (Windows Phone, Android); the Verizon website offered dramatically different stats for the Android that slanted the battery life much further towards Windows Phone but this could be a typing error.

That's about 10% better battery life by simply switching the operating system, and this shows that Windows Phone devices do get better battery life than their Android counterparts. It is worth pointing out that Windows Phone hardware is more restrictive than Android and therefore is optimized for the platforms that it runs on, where as Android is more flexible.

For those that love the hardware of the HTC One M8, the better battery life on the Windows Phone version may be enough to sway users to the platform. But, Android is still king of the market and crucially has a better app ecosystem.

Thanks for the tip Ginny!

Report a problem with article
Previous Story

For Microsoft, getting Diablo 3 to run at 1080P was a necessity to compete with PS4

Next Story

Microsoft overhauls Skype notifications, might actually make them work properly

130 Comments

Commenting is disabled on this article.

glen8 said,
ART
/thread

Well they had to get some benchmarks in right before Android blows WP away with L + Volta + ART. Mark my word, they'll be quoting these benchmarks years from now claiming that WP is has better battery life. But if they want to deceive themselves with non-stock vs stock benchmarks, I say let them. The rest of us know the real truth.

Won't be long before this ugly duckling known as Windows Phone die. With a reputation tarnished by Vista, Windows 8, Windows Phone, Kin, Zune, Bob; I wouldn't be surprised if people start to turn to other competitive platforms. And I hope they do, it's evident that Microsoft doesn't really know what it's doing for the last decade or so.

Pluribus said,
Won't be long before this ugly duckling known as Windows Phone die. With a reputation tarnished by Vista, Windows 8, Windows Phone, Kin, Zune, Bob; I wouldn't be surprised if people start to turn to other competitive platforms. And I hope they do, it's evident that Microsoft doesn't really know what it's doing for the last decade or so.

That's awfully nice of you! What company do you work for? I'll wish the same kind of fortune on your company as well.

TMYW said,

That's awfully nice of you! What company do you work for? I'll wish the same kind of fortune on your company as well.

Why thank you! Unfortunately my company doesn't keep shooting itself in the foot like Microsoft, so you will need to keep praying.

Disable some of the Sense services or better yet throw vanilla AOSP on the M8 and see who gets better battery life

Sonne said,
Disable some of the Sense services or better yet throw vanilla AOSP on the M8 and see who gets better battery life

Yeah, just cripple the device or install a gimped version of the OS to make the battery last longer. LOL. How the devices comes out the box is how the majority of users are going to experience the phone. Just accept that the bloated versions of Android are the only versions that people really buy and use.

If you disable every background service in Windows, you'd get the same battery life as a MacBook Air too, but that's not a realistic scenario.

TMYW said,

Yeah, just cripple the device or install a gimped version of the OS to make the battery last longer. LOL.

So when you buy a Windows laptop with pre-installed bloatware and its using a lot of resources so you uninstall/disable it then by your logic you are crippling the os and your laptop. Take two brand new HP laptops, one with Windows 8 and all of the HP and their partners bloatware pre-installed and the other with simply a clean install of Windows 8, obviously the one with a clean install would run faster and obviously it would give better battery life because less processes are running in the background. But to you its crippled?

AOSP is not crippled its simply Android untouched by OEM's and carriers. To most enthusiasts removing bloatware and disabling services is standard fare, we (enthusiasts) look at you with your bloatware running as using a crippled system, and we are right because you are.

Sonne said,

So when you buy a Windows laptop with pre-installed bloatware and its using a lot of resources so you uninstall/disable it then by your logic you are crippling the os and your laptop. Take two brand new HP laptops, one with Windows 8 and all of the HP and their partners bloatware pre-installed and the other with simply a clean install of Windows 8, obviously the one with a clean install would run faster and obviously it would give better battery life because less processes are running in the background. But to you its crippled?

AOSP is not crippled its simply Android untouched by OEM's and carriers. To most enthusiasts removing bloatware and disabling services is standard fare, we (enthusiasts) look at you with your bloatware running as using a crippled system, and we are right because you are.

I'm not talking about bloatware. I'm talking about services like Desktop Window Manager, Computer Browser, Cryptographic Services, Bitlocker Encryption Service, DHCP Client, User Profile Service, and whatever else that makes Windows function as an operating system.

AOSP doesn't include any of the Google Mobile Services. Running pure AOSP would be like running Windows with its most important services disabled.

Quit trying to sugar coat this. If you want a version of Android that's useable and not some shell of an OS, then it sucks up battery faster than WP does. #dealwithit

while i dont deny that wp might have better battery or be smoother, i still find it too restrictive for my taste.

my experience is based on lumia 800, so its been a while but one of the most annoying things for me was the fact i couldnt simply plug in the phone and drag and drop word documents and then open them directly with the phone as i can do with android.

i had to upload the documents to skydrive then login and redownload them....

secondly i love tinkering with custom roms and changing every app to perfrom the way i want, its too hard to explain unless you have used an android rom such as AOKP or Paranoid or xposed module called gravity box.
you can literally tweak every single aspect of your phone from dpi, to notification leds, sounds, vibrations, the type of clock,lockscreen, pretty much whatever you feel like tweaking to your needs or taste.

when wp or for that matter ios lets me do that then i will consider them until that point android will remain my choice.

Drag and drop support is definitely there since they switched from WP7 (Windows CE) to WP8 (Windows NT). You have access to the whole folder file system now (no more Zune syncing).

Yeah if you want to tweak every aspect of the phone and cook Roms and everything, then Windows and iOS probably aren't the best platforms for you right now. Personally I just like having a fast, efficient reliable phone and leave the tweaking/experimental stuff to my non-essential PCs.

This is expected. WP is a fast, optimized OS that from day 1 has been faster and smoother on much lower end hw.

Android is a bloated pig running on top of a JVM (till ART which still isn't out), got hw accel years after release, and still has terrible lag. Using Android on anything but a top end phone is a pain. Google really doesn't care because oem's will keep coming out with faster phones every few months.

Defcon said,

Android is a bloated pig running on top of a JVM (till ART which still isn't out)

Actually ART is already available in KitKat. It's just not enabled by default. As far as VM's go, you do realise that dotnet and WP software runs on top of a VM right?

Defcon said,

got hw accel years after release

Wrong again. Android had hardware acceleration years before project butter. It just didn't render the entire UI at a locked frame rate like it does now.

Defcon said,

and still has terrible lag. Using Android on anything but a top end phone is a pain.

I get absolutely zero lag on my stock Android devices. OEM skinned devices are another matter entirely.

I've seen some awful lag on a Lumia before. Other people have noted it too. So, no WP isn't the lag-free smooth experience you purport it to be.

Defcon said,

Google really doesn't care because oem's will keep coming out with faster phones every few months.

If Google didn't care, they wouldn't have moved most of the key services and apps over to the playstore so most users get updates independent of carriers/OEMS.

And now that Android L and Project Volta are coming to fruition, I have every confidence that Android will best Windows Phones battery life.

simplezz said,

Actually ART is already available in KitKat. It's just not enabled by default. As far as VM's go, you do realise that dotnet and WP software runs on top of a VM right?
.

how many times are you going to keep repeating this misinformation? I've already told you in the other article's comment section that you can write native c,c++ apps on windows phone.

vcfan said,

how many times are you going to keep repeating this misinformation? I've already told you in the other article's comment section that you can write native c,c++ apps on windows phone.

There's no reasoning with him. Basically it's M-Dollar must die in his lifetime.

simplezz said,

Actually ART is already available in KitKat. It's just not enabled by default. As far as VM's go, you do realise that dotnet and WP software runs on top of a VM right?

Wrong on both counts. ART isn't final in KitKat as you well know. And WP/.NET use ngen for phone apps and many desktop apps, there's no VM at all. Its what ART is trying to copy.


simplezz said,

Wrong again. Android had hardware acceleration years before project butter. It just didn't render the entire UI at a locked frame rate like it does now.

So you agree with me.

HW accel in some parts. WP had the equivalent of project butter from day 1, so did iOS. Android still doesn't utilize multiple cores efficiently, or at all depending on version.

simplezz said,

I get absolutely zero lag on my stock Android devices. OEM skinned devices are another matter entirely.

Good for you. Unfortunately the majority of android devices are not Nexus. And you can't really blame oem skins, look at AOSP changelogs and there are plenty of inefficiencies left in Android.

simplezz said,

If Google didn't care, they wouldn't have moved most of the key services and apps over to the playstore so most users get updates independent of carriers/OEMS.

And now that Android L and Project Volta are coming to fruition, I have every confidence that Android will best Windows Phones battery life.

Google only tests Nexus devices, and in fact new releases are built and tested on 1 device only. Its upto oem's to then port and certify it to their devices. Which is why custom roms never work well on anything but NExus because unlike WP/Windows, there is no standatrd hardware reference platform and everything has to be tailored to hardware.

This is partly the fault of Linux (no ABI) and partly the history of Android, a kludged up OS based on a kludged up JVM (Dalvik) + Linux. There is really no getting around that. In contrast WP and iOS were brand new OS's designed form the ground up

Defcon said,

Wrong on both counts. ART isn't final in KitKat as you well know. And WP/.NET use ngen for phone apps and many desktop apps, there's no VM at all. Its what ART is trying to copy.

Who mentioned anything about final? When is software ever final? I'm sure ART will evolve past Android L too. It doesn't mean it's not on there though:


ART is a new Android runtime being introduced experimentally in the 4.4 release. This is a preview of work in progress in KitKat that can be turned on in Settings > developer options. This is available for the purpose of obtaining early developer and partner feedback.

http://source.android.com/devices/tech/dalvik/art.html

What were you saying again?

Defcon said,

So you agree with me.
HW accel in some parts. WP had the equivalent of project butter from day 1, so did iOS. Android still doesn't utilize multiple cores efficiently, or at all depending on version.

LOL. Being obtuse and pretending what you said was correct doesn't make it so. Your last two statements are demonstrably false. It also exposes your ignorance of the Android platform in general.

Defcon said,

Good for you. Unfortunately the majority of android devices are not Nexus. And you can't really blame oem skins, look at AOSP changelogs and there are plenty of inefficiencies left in Android.

OEM skin ≠ Android. How many times do I have to say it really? Android is the base system, just like Windows is. Do you also believe OEM bloatware = Windows on the desktop too? Of course it isn't. It's third party software. That's why you can't compare the battery life of a HTC with sense against stock Windows Phone. It's either stock vs stock, or not at all.

Defcon said,

Google only tests Nexus devices, and in fact new releases are built and tested on 1 device only. Its upto oem's to then port and certify it to their devices.

As it should be. There is no strict hardware reference in Android except in devices like Android One. And if OEM's add their own bloat on top (Touchwiz, Sense, etc), that has to be tested to make sure it's compatible. However, all that gives OEM flexibility and a way to differentiate their respective devices. Unlike WP, where every device is virtually identical.

Defcon said,

Which is why custom roms never work well on anything but NExus because unlike WP/Windows, there is no standatrd hardware reference platform and everything has to be tailored to hardware.

Actually, custom roms work well on numerous devices, including the Samsung Galaxy line. Unlike WP which doesn't even have any custom roms available. What you get from an OEM is it. There's absolutely no customisation or alternatives if you don't like WP.

Defcon said,

This is partly the fault of Linux (no ABI) and partly the history of Android, a kludged up OS based on a kludged up JVM (Dalvik) + Linux.

You have no idea what you're talking about do you. Of course Linux has an ABI, without it, nothing would run. The NDK has a well defined ABI:
http://www.kandroid.org/ndk/docs/CPU-ARCH-ABIS.html

Defcon said,

There is really no getting around that. In contrast WP and iOS were brand new OS's designed form the ground up

You don't have a clue about WP's beginnings do you? WP was originally based on Windows CE. Yes, that ancient and creaking Windows Mobile OS. Built from the ground up? Haha. Not even slightly. All Microsoft did was slap a sliverlight (flash) player as the front end. That's why it ran at a fixed frame rate. And the reason they have a hardware spec is so they can precompile and optimise it for a specific architecture. They don't let the OEM's have access to the source and optimise it themselves.

simplezz said,

You don't have a clue about WP's beginnings do you? WP was originally based on Windows CE. Yes, that ancient and creaking Windows Mobile OS. Built from the ground up? Haha. Not even slightly. All Microsoft did was slap a sliverlight (flash) player as the front end. That's why it ran at a fixed frame rate. And the reason they have a hardware spec is so they can precompile and optimise it for a specific architecture. They don't let the OEM's have access to the source and optimise it themselves.

what a load of crap you are spewing. windows mobile is an os that uses the windows ce kernel. windows phone 7 is an os that uses the windows ce kernel. Silverlight is not flash,and the os shell doesn't even run on Silverlight like applications do. it runs and uses an internal native Microsoft API. I would know, I decompiled and studied the shell executable. im sorry but nobody should bother responding to this guy at this point.

vcfan said,

what a load of crap you are spewing. windows mobile is an os that uses the windows ce kernel. windows phone 7 is an os that uses the windows ce kernel.

How does that not agree with what I just said? :laugh:

vcfan said,

Silverlight is not flash

It's an equivalent of flash. One that virtually no one besides Netflix uses. And even Netflix supports html5 video now.

vcfan said,

and the os shell doesn't even run on Silverlight like applications do.

I said the front-end (UI) runs on Silverlight, and it does.

vcfan said,
it runs and uses an internal native Microsoft API.

You don't say. And there was me thinking it ran a Linux API :laugh:

Not surprising, given how little actual use a WP gets. You can't control your A/V system with it, nor your home automation, nor your cable box...I guess you can place phone calls, and get "Cortana" to set appointments and reminders for you though, so there is that...

John Nemesh said,
Not surprising, given how little actual use a WP gets. You can't control your A/V system with it, nor your home automation, nor your cable box...I guess you can place phone calls, and get "Cortana" to set appointments and reminders for you though, so there is that...

I don't really need to control all that stuff anyway. In fact, I prefer not to.

John Nemesh said,
Not surprising, given how little actual use a WP gets. You can't control your A/V system with it, nor your home automation, nor your cable box...I guess you can place phone calls, and get "Cortana" to set appointments and reminders for you though, so there is that...

Actually, you can control your AV system, there are numerous home automation solutions and you can definitely control your cable box. You can even use Cortana to control your home automation.

I control my AV System, Home Automation and more on my old Lumia 920 running WP 8.1. I have been following your posts lately and either you are sincerely clueless or type these comments to instigate ....

really, because Bose, Marantz, Denon, RTI, Tivo, Crestron, URC, RTI and every other CE brand I deal with ON A DAILY BASIS does NOT support Windows Phone.

Let's hope so, it's about time Android was made more efficient. It won't do much to help the millions of Android users who'll never get the update mind you.

No benchmarking of the two phones? This is a total BS article to make Windows phone users and their empty app store feel better...

This Ginny person is even comparing the HTC One (M8) Windows version to the wrong phone. The regular HTC One (M8) Android version is not stock Android. It has Sense and other bloatware on it.

Someone benchmark this with the HTC One (M8) Google Play edition phone please--> https://play.google.com/store/..._One_M8_Google_Play_edition

This is Neowin we're talking about here. The same website which ran a GNU/Linux Munich story that was pure disinformation and made up facts. There is little hope of getting a story which isn't made to please the resident Microsoft fanboys.

Well this is manufacturer specs and the WP version has Sense on it as well.

We'll need to see some real world tests, but I do expect WP will be better for battery life. More interesting will be to see how graphic intensive games run, which has better framerates, and also how playing them effects battery life.

While some people will always stick to Android for certain apps, for other people on the fence who don't need some specific app, knowing that the phone will last longer and run better would be reason enough to go either way.

If true, I am pretty sure Sense on the HTC One (M8) Windows phone is a scaled back version compared to the Android version. Microsoft has more control over Windows phones then Google does over other Android phones. Regardless, we don't have any benchmarks just what HTC wrote on their website. They could have tested the Windows version under totally different parameters.

Disdain said,
How is the article BS when, like you said, the numbers are pulled from HTC's website?

It's says right in the title "Windows Phone has better battery life than Android" and the article is based on a tweet from "Ginny". The battery life numbers from HTC's website are meaningless (not independently benchmarked) and we don't even know if HTC tested both phones under the same conditions. The Android version has full Sense and other bloatware on it which will effect battery life. Like I said and as well as others is that the GPE (stock) version would be a better comparison.

Clear now why this is BS?

Edited by 01Michael10, Aug 20 2014, 6:23pm :

Disdain said,
How is the article BS when, like you said, the numbers are pulled from HTC's website?

Because HTC phones aren't stock Android. It's like comparing one desktop environment to another. There will doubtless be performance impediments compared to stock because it's running another layer on top. More demanding UI = less battery life. It's a given.

The only fair comparison that matters is stock Android vs stock Windows Phone. Until we get that, it's not even a debate.

Regardless, even if WP does have a small lead, Android L and Project Volta completely negates it.

01Michael10 said,
No benchmarking of the two phones? This is a total BS article to make Windows phone users and their empty app store feel better...

This Ginny person is even comparing the HTC One (M8) Windows version to the wrong phone. The regular HTC One (M8) Android version is not stock Android. It has Sense and other bloatware on it.

Someone benchmark this with the HTC One (M8) Google Play edition phone please--> https://play.google.com/store/..._One_M8_Google_Play_edition

The "regular one" is going to be the one 99% of consumers will be purchasing. Nobody but a fanboy is going to pay $700 for a phone just because it's branded as a "Google" edition.

simplezz said,

Because HTC phones aren't stock Android. It's like comparing one desktop environment to another. There will doubtless be performance impediments compared to stock because it's running another layer on top. More demanding UI = less battery life. It's a given.

The only fair comparison that matters is stock Android vs stock Windows Phone. Until we get that, it's not even a debate.

Regardless, even if WP does have a small lead, Android L and Project Volta completely negates it.

Tell me which extra background services run in "non-stock" Android devices that don't run in "stock" Android, and how much CPU time do they use?

TheShark said,
Well this is manufacturer specs and the WP version has Sense on it as well.

We'll need to see some real world tests, but I do expect WP will be better for battery life. More interesting will be to see how graphic intensive games run, which has better framerates, and also how playing them effects battery life.

While some people will always stick to Android for certain apps, for other people on the fence who don't need some specific app, knowing that the phone will last longer and run better would be reason enough to go either way.

HTC Sense (as in the skin) is not running on Windows Phone.

TMYW said,

The "regular one" is going to be the one 99% of consumers will be purchasing. Nobody but a fanboy is going to pay $700 for a phone just because it's branded as a "Google" edition.

I agree which is why I have a Nexus 5 myself. The question at hand is if Windows gets better battery life then Android on mobile phones and it can only be answered if comparing apples to apples.

Even if you get a little better life with a Windows phone today so what? Android L and project Volta have already been mentioned... Android has 10x more phone choices, way more apps, and the option for 3rd party ROMS (if using a Nexus phone even alternative OS options).

Edited by 01Michael10, Aug 21 2014, 1:01pm :

TMYW said,

Tell me which extra background services run in "non-stock" Android devices that don't run in "stock" Android, and how much CPU time do they use?

Which phone? Nexus 5, which I have that would none. Stop trolling... You know OEMs and carriers load crappy skins and other bloatware on Android phones which of course use CPU and battery resources. Google Touchwiz...

I can't wait for a in-depth review (specifically from Anandtech - can't trust sites with inherent biases a la Neowin/wpcentral/etc.). I am suspecting WP will have the upper hand in battery life, but I also want to see what Android L will do to the battery life on the One M8.

tsupersonic said,
I can't trust sites with inherent biases
Oh please, they're pulling straight from the mfg.'s website. If anything, HTC would be biased against WP because Android sells wayyyyyy more units.

greenwizard88 said,
Oh please, they're pulling straight from the mfg.'s website. If anything, HTC would be biased against WP because Android sells wayyyyyy more units.
Yeah, mfg is a good baseline, but I want to see real world tests. Mfg. claims only depict talk and standby times, which doesn't tell you the whole story.

And how long does the battery last? And how smooth will it be once you fill it with apps and photos? Sorry Android starts out ok with lots of tweaking and choosing of ROMs, but even then eventually it gets bogged down.

TheShark said,
And how long does the battery last? And how smooth will it be once you fill it with apps and photos? Sorry Android starts out ok with lots of tweaking and choosing of ROMs, but even then eventually it gets bogged down.

That's strange because I have a gig of apps, and about 5 gigs of music, photos, and videos on my 16 gig Nexus 5 and it's still as smooth as the day i brought it.

TheShark said,
And how long does the battery last? And how smooth will it be once you fill it with apps and photos? Sorry Android starts out ok with lots of tweaking and choosing of ROMs, but even then eventually it gets bogged down.

by the time I go to bed at night my battery is around 40% and I charge it every night.

With the new developer preview I got last night the battery life seems to be infinite now, judging by the indicator that hasn't moved all day anyway! (stuck on 25% for the past 10 hrs)

No it's true. I installed the update at 11pm yesterday, left it on charge all night and the battery indicator has been on 25% since I woke up 10 hrs ago.
I thought I was going to run out of battery at work (its 5pm here now) but it's worked all day with no decrease.

londan said,
With the new developer preview I got last night the battery life seems to be infinite now, judging by the indicator that hasn't moved all day anyway! (stuck on 25% for the past 10 hrs)

Either that, or the battery meter is broken :p

(Which, considering I still can't send or receive MMS since the 8.1.1 update, wouldn't surprise me).

I'm not at all surprised by this.

Joe Belfiore and the WP team have stated time and time again that in mobile, battery is king.
Everything in WP is designed around preserving battery, which has unintended consequences for developers.

Ill wait to see. We've been told Froyo will fix it, Gingerbread will fix it, Kitkat supposedly fixed it, now Android L will fix it. Techbeck mentioned a laggy 520, while the 520 I have is much slower than my 920 (not even going to compare my 1520), the 520 still has less ui lag than my nexus 4.

Meduso said,
Ill wait to see. We've been told Froyo will fix it, Gingerbread will fix it, Kitkat supposedly fixed it, now Android L will fix it. Techbeck mentioned a laggy 520, while the 520 I have is much slower than my 920 (not even going to compare my 1520), the 520 still has less ui lag than my nexus 4.

Project Volta is part of Android L. It will do for battery life what Project Butter did for UI frame rate consistency. I'm betting that it will beat WP's battery life on same hardware.

Meduso said,
Ill wait to see. We've been told Froyo will fix it, Gingerbread will fix it, Kitkat supposedly fixed it, now Android L will fix it. Techbeck mentioned a laggy 520, while the 520 I have is much slower than my 920 (not even going to compare my 1520), the 520 still has less ui lag than my nexus 4.

People have already tested the battery life of android L devices, some had 30% extra battery. The L release will almost certainly match or exceed the battery life of windows phone.

Android is a fragmented mess, even in the latest versions permanence also dramatically decreases as you use it more and install more apps.

I've seen tons of flagships, especially from Samsung, with that exact problem. But that's always been a problem, even on old Nokia phones (especially the E and older Asha series).

When your memory gets so full of apps and personal data, the whole OS lags to no end in order to load everything. You've got apps in phone memory, then more apps and personal data on internal memory, then the horrors of people's SD cards. Ugh.

Just yesterday I've had a Galaxy S3 that was so FULL that it took the OS ten minutes just to find the carrier's signal. It would start to overheat when loading all that crap and finally just freeze completely. Biggest pain in the *** backup job I've ever had in my life!

Ugh.

swanlee said,
Android is a fragmented mess, even in the latest versions permanence also dramatically decreases as you use it more and install more apps.

Actually, 20% or more handsets are now running the latest version (KitKat). Fragmentation is much less of a problem now than it was in the past. Heck, my aging Galaxy S III has the latest OS on it! The only phones upgrades are a problem for are the cheap "no name" chinese phones...any major phone from HTC, Samsung or LG will be updated in a (fairly) timely manner.

John Nemesh said,

Actually, 20% or more handsets are now running the latest version (KitKat). Fragmentation is much less of a problem now than it was in the past. Heck, my aging Galaxy S III has the latest OS on it! The only phones upgrades are a problem for are the cheap "no name" chinese phones...any major phone from HTC, Samsung or LG will be updated in a (fairly) timely manner.

20%? LOL! That's sad as ######.

John Nemesh said,
any major phone from HTC, Samsung or LG will be updated in a (fairly) timely manner.

Stop kidding yourself.

Most high-end models (still not all) do receive updates, yes, although it usually takes a forever, but the huge majority of mid-range and low-end models do not, be it samsung, HTC, LG, etc.

not surprising. android is bloated to the core. we've had smooth UIs since windows phone 7 and iOS 1. and took android quad core monster chips to achieve the same.

A little lag doesnt matter tp most and I have seen lag in iOS and WP. In fact, my 520 dual core processor WP 8.1 lags a lot.

And not all of Android comes with bloat.

I highly disagree with you on this. I blame carriers for that. Rooted running stock android it has always been fast and smooth.

johnnyftw said,
I highly disagree with you on this. I blame carriers for that. Rooted running stock android it has always been fast and smooth.

OEMs are to blame as well. Like Samsungs TW.

Yes. I've had phones (ie Nexus S, 4, 5) and they run smooth as butter on stock Google. Carriers and OEMS are indeed to blame, Touchwiz, Sense, etc are bloated as all hell. They don't help the product. It hurts it in my opinion.

Umm... and do you know how much space Android takes? Also, Android requires a LOT more resources just to run even a little bit smooth. Windows (and even iOS) are coded more efficiently, and they optimize it even more with each edition. Android hasn't changed optimization wise in quite some time and still requires monster specs to run effectively. It's a waste of money and resources and Google should look into optimizing their OS.

techbeck said,
A little lag doesnt matter tp most and I have seen lag in iOS and WP. In fact, my 520 dual core processor WP 8.1 lags a lot.

And not all of Android comes with bloat.

I don't have that much personal experience with WP, aside from playing around with my friend's 820 and helping him out from time to time. Looking forward to buy a WP though.

By lag, do you mean longer load times, or lag in animation or opening, closing things?
Maybe it'd be better with cyan?

I've seen android phones with specs about the same as 520 and they observably perform worse.

recursive said,
Windows Phone takes up about 3.5 gigs of the 8 gigs on the HTC. And you call Android bloated?

Yes, it usually takes more place compared to nexus phones, but definitely not against, say, samsung phones.

Besides, The OS install size has nothing to do with performance.

j2006 said,
Android hasn't changed optimization wise in quite some time and still requires monster specs to run effectively. It's a waste of money and resources and Google should look into optimizing their OS.

Moto E and G. I have messed around with both of them and they are pretty smooth with little lag. In fact, the Moto G was compared to the SGS5 and was faster in a lot of instances because of TW. The Moto E lagged less than then Nokia 520 I have now.

eddman said,

By lag, do you mean longer load times, or lag in animation or opening, closing things?
Maybe it'd be better with cyan?

I've seen android phones with specs about the same as 520 and they observably perform worse.

Lag...jerky scrolling images, web pages, menues...that sort of thing. And the Moto E I had for a day or two performed much better than my Nokia 520 did. But that is my experience and others may vary.

techbeck said,

Lag...jerky scrolling images, web pages, menues...that sort of thing. And the Moto E I had for a day or two performed much better than my Nokia 520 did.

Hmm... maybe try resetting your phone? I also worked with a 620 for a while, which has the same specs as 520, and it didn't behave as you say; although that was on 8.0 black.
Was it the same before updating to 8.1?

It got better when I applied 8.1. And scrolling in IE is the main issue. It is jerky and the text is blurred for a second and them becomes crisp. And at times when I unlock the phone or scroll thru tiles, it stutters.

neonspark said,
not surprising. android is bloated to the core. we've had smooth UIs since windows phone 7 and iOS 1. and took android quad core monster chips to achieve the same.

Bloated? Stock Android without the OEM UI framework/apps or carrier crap/bloatware weighs in at just over 150MB and will typically use less than 100MB of RAM. Furthermore most of the Android power management is actually managed by the underlying Linux kernel and parameters, clock/voltage tables or the various CPU/GPU scaling set by the manufacturers. Why even blame Android when the obvious fault lies with the OEMs or their poor software implementations?

While I don't have a Moto E, I did have a Moto X and the 520 was about the same as that so I find it difficult to see how the E could be faster than the X. Either way the dual core very low end 520 still outperforms my (at the time) high end quad core Nexus 4 as far as UI performance and scrolling web pages. It will be very interesting to see the comparisons now that a single phone has the same hardware.

Meduso said,
It will be very interesting to see the comparisons now that a single phone has the same hardware.

It won't help at all, since HTC one is a very powerful phone and I doubt there'll be any noticeable performance differences, if any at all.

Now if we had a low end phone, say 630 level, that came with both OSes, that'd be more telling.

recursive said,
Windows Phone takes up about 3.5 gigs of the 8 gigs on the HTC. And you call Android bloated?

Yes. By 1.3GB.

HTC M8 (for Android):

1.Available storage is less due to phone software. Approximately 10GB (for 16GB) /24GB (for 32GB) storage available for user content. Available storage is subject to change based on phone software updates and apps usage.

HTC M8 for Windows:

1.Available storage is less due to phone software. Approximately 25.3 GB storage available for user content. Available storage is subject to change based on phone software updates and apps usage.

The problem with a lot of these Android comparisons is that people have tested out some Android phones in stores and not in real life. They usually start off ok, but once you fill them up with photos and apps, they just start to grind to a half. WP on the other hand doesn't change no matter how it's pushed or for how long.

It took jelly bean. An update specifically designed to make the ui smoother actually. Even on dual core, jelly bean is smooth.

Stop spreading rubbish

j2006 said,
Umm... and do you know how much space Android takes? Also, Android requires a LOT more resources just to run even a little bit smooth. Windows (and even iOS) are coded more efficiently, and they optimize it even more with each edition. Android hasn't changed optimization wise in quite some time and still requires monster specs to run effectively. It's a waste of money and resources and Google should look into optimizing their OS.

Do you ever get tired of parroting such misinformed crap? Most custom android ROMs are under 400MB, and the software for my nexus 5 is only about 800MB. It runs incredibly smoothly.

Oh and just FYI Android 4.4 was engineered to run well on devices with 512 MB of RAM, they engineered it to be very efficient. Not to mention the upcoming android runtime which will improve performance by about 40% and battery life by about 30%

Try actually educating yourself before commenting on these arguments because the rant you went on here just makes you look ignorant.

Javik said,

Do you ever get tired of parroting such misinformed crap? Most custom android ROMs are under 400MB, and the software for my nexus 5 is only about 800MB. It runs incredibly smoothly.

Oh and just FYI Android 4.4 was engineered to run well on devices with 512 MB of RAM, they engineered it to be very efficient. Not to mention the upcoming android runtime which will improve performance by about 40% and battery life by about 30%

Try actually educating yourself before commenting on these arguments because the rant you went on here just makes you look ignorant.

I'm glad someone called bs on this argument! ANDROID is a streamlined, efficient OS...which gets ruined by "Touchwiz" and "Sense" skins...there is where the "bloat" is, not Android itself!

John Nemesh said,

I'm glad someone called bs on this argument! ANDROID is a streamlined, efficient OS...which gets ruined by "Touchwiz" and "Sense" skins...there is where the "bloat" is, not Android itself!

Who cares? The general consumer likes the UX offered by these OEM-specific skins. That's why they outsell Nexus and Play Edition devices by about 900 to 1.

TMYW said,

Who cares? The general consumer likes the UX offered by these OEM-specific skins. That's why they outsell Nexus and Play Edition devices by about 900 to 1.

The OEM devices outsell the Nexus line because of the OEM's channel relationships, carrier relationships and better advertising. It has very little to do with UX.

Should be interesting to see some reviewers do their own tests now that they have the handsets, or will soon. I still expect the WP version to last longer battery wise but we'll need exact numbers to see how close or not the two come.

Honestly for the difference to actually matters you need to be able to use one of the phone one more day without charging it. If you need to charge both phones after 1 or 2 days of use then the difference doesn't matter at all.

It's like the difference between a 10 hours wireless mouse and a 11 hours wireless mouse (like Mamba and G700). If you are a power user you'll need to charge both every day anyway.

LaP said,
Honestly for the difference to actually matters you need to be able to use one of the phone one more day without charging it. If you need to charge both phones after 1 or 2 days of use then the difference doesn't matter at all.

It's like the difference between a 10 hours wireless mouse and a 11 hours wireless mouse (like Mamba and G700). If you are a power user you'll need to charge both every day anyway.

I don't disagree, which is why I'm waiting for some review numbers to see if it's worth taking note of or not.

True. Those numbers are achieved in controlled lab tests and are not exactly representative of real world battery life.

I think they'd do about the same in reviews and, who knows, WP might even do worse. :|

I suspect that real-world test will show the same thing. Android has always lagged a bit on battery life management. iOS and WM do a better job of forcing multitasking applications to behave.

2hrs isn't much and for most, and depending on how you use your phone, will not even matter. Would be more informative if someone actually did real world tests as I find specs on websites to be highly inaccurate.

But anyway, different OS, what do you expect.

techbeck said,
2hrs isn't much

Right. Tell me that when your phone shuts down in the middle of an important call.

TMYW said,

Right. Tell me that when your phone shuts down in the middle of an important call.

Sounds like a user problem to me and that the user is not prepared when taking/placing a call. I never had a call drop on me because my battery died. If I need to make an important call, I use land line or make sure my phone is charged more than enough.

And depending how you use the phone, wont matter much. I have a lot less battery then most of my friends at the end of the day, all droids, and I have a bigger battery. A few friends have the same phone running stock Android and they have more battery than I.

People can look at raw specs all they want that are posted on websites. Depending on the person, those specs may not even come close to what they are seeing.

wtf? An extra 2 hours of talk time is loads when you need it.

32 extra hours of standby is a massive difference.

Give credit where it's due.

I never denied credit or disputed OP. I said for most and unless you are a power user, it wouldnt matter much. There are a lot less power users out there then regular users.

techbeck said,
I never denied credit or disputed OP. I said for most and unless you are a power user, it wouldnt matter much. There are a lot less power users out there then regular users.

You don't have to be a power user the drain the battery. You can just watch YouTube videos and kill your battery. If you drain 90% of your battery watching stupid videos, that 2 extra hours of talk time could mean the difference between getting to use your phone for 2 hours at the end of the day or not at all.

Maybe power user wasnt the correct wording. I merely meant that depending on how you use your phone, the 2hrs wont make much a difference.

techbeck said,
Maybe power user wasnt the correct wording. I merely meant that depending on how you use your phone, the 2hrs wont make much a difference.

Yes, if you use your phone only 1 hour per day, then the 2 extra hours aren't going to matter at all. If you intend to use your phone only 1 hour per day, then a flagship phone is probably not what you should be buying in the first place.

Sorry I think it doesn't matter what kind of user you are, an extra 2 hours makes a big difference. Most users will face the situation when they are out and about without being near a charging point for a day and will run out of battery.

TheShark said,
Sorry I think it doesn't matter what kind of user you are, an extra 2 hours makes a big difference. Most users will face the situation when they are out and about without being near a charging point for a day and will run out of battery.

There are also plenty of times when one simply forgets to charge a phone overnight. That's when the extra 2 hours is going to make a huge difference.

TMYW said,

There are also plenty of times when one simply forgets to charge a phone overnight. That's when the extra 2 hours is going to make a huge difference.

People will still forget to charge their phones and stuck with the exact same problem.

John Nemesh said,

"Power Users" don't use Windows Phone...


That's the most ridiculous thing I've ever heard. So as a System Administrator am I not a power user?

techbeck said,

People will still forget to charge their phones and stuck with the exact same problem.

And that's when having two extra hours of use will be most valuable. Maybe the difference between 20 hours and 22 hours isn't much, but if you forgot to charge your phone, the difference between having 2 hours and 0 hours is huge.

techbeck said,
Depending if you are a power user or not, it will not matter to most.

What? Battery life is a universal issue, what does being a power user have to do with that?

techbeck said,

People will still forget to charge their phones and stuck with the exact same problem.

Only if they talk on their phone that night until its dead. Because, the 32 hours of standby time or whatever it is will help you get through the night and charge it at work or whatever the next day =).

Dot Matrix said,

What? Battery life is a universal issue, what does being a power user have to do with that?

What people do on their devices directly results in how much battery life they have at the end of the day.

Scabrat said,

Only if they talk on their phone that night until its dead. Because, the 32 hours of standby time or whatever it is will help you get through the night and charge it at work or whatever the next day =).

True. I would just like to actually see tests/benchmarks instead of postings on sites as a comparison. doesnt state whether the GPS, WiFi and other services are on. This is just looking at specs of 2 devices and saying one is better. not a lot to go on. While WP will probably still come out ahead, just not accurate ATM.

Stokkolm said,

That's the most ridiculous thing I've ever heard. So as a System Administrator am I not a power user?

Not if you are using a Fisher Price phone OS...

techbeck said,

True. I would just like to actually see tests/benchmarks instead of postings on sites as a comparison. doesnt state whether the GPS, WiFi and other services are on. This is just looking at specs of 2 devices and saying one is better. not a lot to go on. While WP will probably still come out ahead, just not accurate ATM.

I want bench marks as well =). But I wouldnt be surprised at all if WP was better than Android at battery life and stand by =). But, I am sure this will be tested a lot in the coming months AND I am very interested to see the results!

John Nemesh said,

Not if you are using a Fisher Price phone OS...


Wow, so Server 2012 or R2 aren't real OS's in your world?

Edited by Stokkolm, Aug 20 2014, 7:04pm :

techbeck said,
2hrs isn't much and for most, and depending on how you use your phone, will not even matter. Would be more informative if someone actually did real world tests as I find specs on websites to be highly inaccurate.

But anyway, different OS, what do you expect.

Here comes techbeck again to hold google's side as always. Poor guy ... Brainwashed by google like that ... Wake up

Yup, really brainwashed. Just bought a 520 and most of what I have is MS products. I didnt dispute the OP and said that WP is probably better. It is called voicing MY OPINION. You would know this if you would not be lazy and read all the comments and not reply without knowing the full info.

Seriously, just shutup and dont post if all you are going to do is troll.

P.S...and it wasnt even a real test of battery life. It is just info/text taken off a couple websites. But yea, I guess I am brainwashed.....

Edited by techbeck, Aug 21 2014, 1:05pm :

John Nemesh said,
Nope. If it has "metro" on it, it's a toy, not a real os.

sure, yes, you will receive the nobel prize for your contribution to this post
John Nemesh said,

"Power Users" don't use Windows Phone...


So power users don't even use windows/mac os, only uses Unix and have no social life...

If you were flying from the east coast or mid-west, to the west coast, you're talking about the amount of time it takes to pickup your luggage, acquire a rental car / taxi, and get to your hotel (if it's not at the airport). Instead of your phone dying at baggage claim, it might actually remain usable until you reach the hotel.

With that said, the discrepancy in time may have more to do with WP's battery saver feature. I've noticed it's always been pretty good at extending battery stamina (without all that black & white nonsense); it's been almost comparable to airplane mode.