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

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.

Permalink for comment 573843
To read all comments associated with this story, please click here.
Member since:

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