Linked by Thom Holwerda on Thu 3rd Oct 2013 16:07 UTC
Benchmarks

With the exception of Apple and Motorola, literally every single OEM we've worked with ships (or has shipped) at least one device that runs this silly CPU optimization. It's possible that older Motorola devices might've done the same thing, but none of the newer devices we have on hand exhibited the behavior. It's a systemic problem that seems to have surfaced over the last two years, and one that extends far beyond Samsung.

Pathetic, but this has been going on in the wider industry for as long as I can remember - graphics chip makers come to mind, for instance. Still, this is clearly scumbag behaviour designed to mislead consumers.

On the other hand, if you buy a phone based on silly artificial benchmark scores, you deserve to be cheated.

Thread beginning with comment 573804
To view parent comment, click here.
To read all comments associated with this story, please click here.
phoenix
Member since:
2005-07-11

Or, spent a bit of time optimising drivers, Dalvik, apps, etc for the existing silicon.

You can get impressive performance gains by compiling AOSP yourself using newer versions of GCC, the Linaro stack, updated drivers, etc.

Problem with Android is it's very much a "lowest-common denominator" situation, where the phone makers don't take a lot of time to optimise for their own hardware.

Reply Parent Score: 6

themwagency Member since:
2013-03-06

Or, spent a bit of time optimising drivers, Dalvik, apps, etc for the existing silicon.


Why not both? The types of benchmarks referenced in this article have more to do with showing the capability of the hardware. The drivers would should benefits for the apps however they wouldn't benefit these types of benchmarks. It doesn't mean performance gains wouldn't be achieved however if they're looking for a benchmark speed crown then silicon optimization is where they'll have to invest resources.

Edited 2013-10-03 16:53 UTC

Reply Parent Score: 1

darknexus Member since:
2008-07-15

Or, spent a bit of time optimising drivers, Dalvik, apps, etc for the existing silicon.

Couldn't agree more. The A7 is the smaller part of why the iPhone 5S is so smooth. The greater part is the optimized operating system. This is one thing Apple has always understood: you don't need nearly as much raw power if you optimize for the hardware you're going to be using. Android is anything but optimized, and OEMs have no interest in improving the state of things for it. Why put the work into code optimization when you can just pack more raw power in and convince people to buy a brand new phone in a year? I'd love to see what Android could be if someone took AOSP and optimized the hell out of it for a specific device as Apple do with iOS. Unfortunately no one making Android phones has any reason to try, not even Google.

Reply Parent Score: 5

leos Member since:
2005-09-21

Or, spent a bit of time optimising drivers, Dalvik, apps, etc for the existing silicon.

You can get impressive performance gains by compiling AOSP yourself using newer versions of GCC, the Linaro stack, updated drivers, etc.

Problem with Android is it's very much a "lowest-common denominator" situation, where the phone makers don't take a lot of time to optimise for their own hardware.


They should take all the time they spend adding crapware and stupid "features" to their phones and spend it on optimization instead.

Reply Parent Score: 3