How Many Android OEMs Cheat Benchmark Scores? Pretty Much All of Them
An anonymous reader writes "After Samsung got caught out cheating on benchmarks (Note 3, Galaxy S4) AnandTech has done a detailed analysis of the state of benchmark cheating amongst Android OEMs. With the exception of Motorola, literally every single OEM they've looked at ships (or has shipped) at least one device that does benchmark-specific CPU optimizations. AnandTech also thinks it will get worse before it gets better. 'The hilarious part of all of this is we’re still talking about small gains in performance. The impact on our CPU tests is 0 - 5%, and somewhere south of 10% on our GPU benchmarks as far as we can tell. I can't stress enough that it would be far less painful for the OEMs to just stop this nonsense and instead demand better performance/power efficiency from their silicon vendors.' The article notes that Apple doesn't do any of the frequency gaming stuff."
The benchmark software should randomize the process name on launch
"When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
The phone manufacturers should not be dicks.
The article notes that Apple doesn't do any of the frequency gaming stuff.
Linux is for people who don't mind RTFM.
Isn't that what "Well, they all do it" that we hear so often when anything else cherished is criticised (be it governmental spying, corporate malfeasance or electronics brand screwing customers) means in effect?
The vendors are probably far more concerned with beating OTHER ANDROID sets, since performance between them is a deciding factor that can be "solved" with a single number, whereas comparing iOS performance to Android on a single value is as silly as comparing PPC and x86 on MHz.
Moreover, the competition between each Android device is extreme, whereas you have a lock-in via incompatible applications between Android and, for example, iOS. Someone leaving iOS for merely performance gains would want 50%+ performance increase to leave even a few apps behind (e.g. even if all they lost was the iTunes integration, they'd want a HELL of a lot faster), and since the apps available and OS features on the various Android systems are near identical, if you're leaving a competing ecosystem for Android, any Android is good enough.
With the exception of Motorola...
And Apple. Apple and Motorola/Google are the only two companies that don't boost their devices for benchmark tests. If you're going to give credit to one, please do be fair and give credit to the other.
I respect both of them for that level of integrity and I hope they stick to their guns and remain honest.
I may be an Apple fanboy (and I am) but I'm really looking forward to seeing what Motorola starts releasing in about a year once Google's able to, as they said, flush things out of the system and start releasing truly Google-designed products.
"I can't stress enough that it would be far less painful for the OEMs to just stop this nonsense"
Ever buy a hard drive? Was it really as many gigabytes as it was advertised? These things tend not to get any better once a precedent has been set, even if it is wrong.
'The hilarious part of all of this is we’re still talking about small gains in performance.'
The even more hilarious part is that OEMs are going to the trouble to do this when CPU benchmark scores are a very small factor in the decision of most consumers to buy these phones. I doubt that the ROI is higher than say, oh, improving the user experience of the GUI or call QoS.
Not convinced that it is cheating. For cheating I would have expected to see some evidence of not running a part of the benchmark to get a higher score. But here it looks just to be the OEMs trying to modify the power consumption to game the score. Heh, with that said I guess it is a little swarmy that all of them took the time to change from the default settings just for a bump in the ratings.
I don't consider this to be cheating at all.
It is not possible to create silicon where the best combination of power efficiency and performance is reached with maximum clocks.
For this reason, the phones usually run with clocks smaller than maximum. This'll provide users with performance they want.
In benchmarks and few games, it is essential to do the best phone can do instead of merely what is gotten in "optimal battery usage mode".
It has to be understood that average game (like Angry Birds) does not benefit for last 10% of performance, thus usually it make much more sense to keep maximum power off.
But, when user is benchmarking platform they are really interested in the best platform can do.
(However, if benchmark overclocks then it is wrong, but anything within nominal clocks should be viewed as fine.)
The hilarious part of all of this is we’re still talking about small gains in performance.
The hilarious part of all this is that most people really don't give a rat's as about performance when selecting a phone or even a tablet. The criteria are things like: how does it handle? How intuitive is the UI? Can I watch my favorite online video feeds on this thing? Are any buttons in annoying palaces? What's the price? Does this thing have software to view and edit MS Office files I get sent by mail? The only performance tests these smartphone and tablet things usually get is playing around with a display example in the shop and seeing if the UI is nice and snappy. Nobody excepts tech nerds gives a rats ass that a Samsun Galaxy 4 get a few more FPS in Modern Combat than an iPhone 5.
Only to idiots, are orders laws.
-- Henning von Tresckow
Yes, I'm sure it's all lies where it conflicts with $priorbeliefs.
No kidding!!! What do you say at this point?
Let's call for generalizing Phoronix Test Suite on mobile devices as well...
Is that the table is titled "I Can't Believe I Have to Make This Table". Made me smile.
"Don't meddle in the affairs of a patent dragon, for thou art tasty and good with ketchup." ~ohcrapitssteve
If you measure it, it gets better. Nobody ever stops to think why. They mostly just think they are good managers. But in fact, if you create a measuring tool to measure qualities of a device, the manufacturers will work to make that measurement better. If you make a measurement to determine how your employees are performing, they will perform better according to that measurement. That's just the way it works.
You can't measure everything, so you're best bet is to try to keep the measurement methods secret and change them frequently. Unless, of course, your measurements are intended to improve a particular area, then by all means, measure on.
If you are not allowed to question your government then the government has answered your question.
This is somewhat reminiscent of the MHz wars. The OEMs use all the same OS and they feel they have to distinguish themselves in some way. Except for Samsung, Apple, and Motorola, these OEMs buy their processors from someone else.
Well, there's spam egg sausage and spam, that's not got much spam in it.
I was under the impression that what they were doing was ensuring that the clock speed was running at full, not slowed down for power saving, etc.
No. They are running at a clock speed that no real application will see under any circumstance, either the GPU or CPU cock increased.
It is within what the parts are rated for but not what the device was built to run at normally.
I assume some games and other applications also force the processor to full
There is no way to build a game on Android that can run at the speed the benchmarks are getting run at on each of the devices "cheating".
"There is more worth loving than we have strength to love." - Brian Jay Stanley
There is no way to build a game on Android that can run at the speed the benchmarks are getting run at on each of the devices "cheating".
What happens if you name your game to match the benchmark that the phone is looking for?
Thanks, as I said, I was under the impression they were just ensuring it was not reduced. If there's no way an app could get the same speed then it is most definitely cheating. I'm surprised they don't overclock. If you're going to cheat you might as well do it right.
Given that the devices are operating outside their normal thermal performance envelope, probably it runs for about as long as it takes to do a few benchmarks then the device shuts down from overheating.
No kidding!!! What do you say at this point?
No, he was right. The phones CAN and DO reach that clock speed. Read the AnandTech article. The graph of CPU speed shows it quite clearly.
This has been going on since benchmarks were a thing. So a long time.
GPU in particular had a bad rep for this. However they actually got the benchmark software altered!
Simply checking for a process name and OC, isn't exactly all that sneaky. Maybe a bit unethical, but still. Whoever is running the benchmark could easily check for that. Of course it depends on how closed down the OS is for inspection also.
either the GPU or CPU cock increased.
Whoa, can cell phones do that now? I hold these things to my ear, for Christ's sake!
Instead of automated benchmarks of hardware, why not real world human benchmarking where a group of people is given a set of tasks to do on a given cell phone platform and see who can do them faster?
Automated technical benchmarks make sense when the workloads more or less approximate the benchmark -- video gaming, 3D modeling, disk throughput, etc.
But unless I'm living totally in the dark, most people aren't buying cell phones oriented towards single-task performance (eg, gaming). They get used for many tasks and the fact that I can run some obscure CPU task faster than some other model doesn't tell me if it makes it faster to open an app, etc.
Native Code Execution, it runs as fast as it is going to run.
Got Code?
" the point of benchmarking is to compare "like" things"
THE TWO THINGS ARE NOT ALIKE.
Get it?
iOS not like Android.
either the GPU or CPU cock increased.
Whoa, can cell phones do that now? I hold these things to my ear, for Christ's sake!
Yeah, they'll f**k your brains out... literally.
"Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
Overclocking rooted Android phones has been around for some time. SetCPU is a popular app for it, and many custom roms have a built-in way to control clock speeds and governors.
Not a sentence!
aaand I missed the typo.
That said, given the internet I'm sure someone has "overcocked" their phone, and stuck it in their ear. Probably in Japan.
Not a sentence!
I'd say you must be knew here, but it seems too easy with your SlashID ;-) My mistake was that I believed the first poster that said they were overclocking. I did a ctrl-f for overclocking to read about it, and then from there, jumped to the wrong conclusion that they were improving performance using the technique a Linux professional would likely use. My mistake would have been not reading the article, except I simply don't care all that much. If they were overclocking then that would have been interesting.
Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
Aww, are you frustrated you little shit stain?
Mmm, cooked roosters. I wonder how they taste compared to female chickens.
Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
GPU companies have been cheating on benchmarks for decades. Back in the PCI and AGP days, it was just pretty much expected that graphics cards would include a hack to lock themselves on the shared bus for as long as they felt they needed. Sure, this wasn't benchmark specific, but it was also destructive -- it killed the realtime performance of your PC. Specifically in those days, audio workstation software was broken by these hacks... leading a bunch of counter-hacks necessary to defeat these (and sure, the occasional GPU company savvy enough to offer a non-broken version of the driver online).
And then there was the Intel C compiler.. the one that basically had a "detect Dhrystone" function. And over the years, a whole series of cheats that either made AMD look bad or Intel amazingly good... enough to be much of the meat of AMD's suit against Intel in 2005... which lead to a court order for Intel to stop their compiler producing code that intentionally ran slower on non-Intel chips. And more recently with Intel's AnTuTu cheat, making Intel smartphones look magically better than AMD.. but only on that one benchmark.
And of course, nVidia. nVidia's been cheating at benchmarks for years... though at least some of that came in response to AMD/ATi getting caught cheaping on Quake 3 performance. And recently, too... earlier this year, they had a driver that detected 3DMark (and perhaps other benchmarks) and cheated, by switching to custom PHYSX code rather than running the DLL everyone else runs. And the various cheats on benchmarks for Tegra 2 and Tegra 3 SOCs.
I mean, this is one reason we speak of lies, damn lies, and benchmarks. Everybody cheats at this stuff. Apple used to cheat in the latter days of the PowerPC, even on published SPECmarks, as their stuff kept falling behind Intel.
-Dave Haynie