yeah, well I can actually buy one of those.
Can't say the same for the 5s.
![]()
Thank you. More 5s for us. Been waiting here for a while now...
yeah, well I can actually buy one of those.
Can't say the same for the 5s.
![]()
So if they developed code to run this around other apps (like the article vaguely mentions it does) it would be OK?
You're trying to tell me someone on XDA isn't going to be able to write up some code to inject into the system that would give the app they develop a boost if they wanted?
CPU governors have been available on Android since pretty much Day 1. I have been able to *artificially* boost the CPU power for a task based per app or overall. Yes, battery life suffered. Yes, performance increased. But at its core, which is the entire point here, the CPU was capable of doing it - just like this benchmark proved. The CPU did the work it was asked to do. The app was NOT compromised to get around tests, the CPU did the work.
Don't forget that most Apple devices are crammed full of Samsung stuff (including the 5s)...
This is pretty hilarious actually. Why not just always run the CPU this way![]()
yes, at twice the clock rate. Its a tradeoff requiring more power/heat dissipation. Really a shocking testament to how good the A7 w/ARMv8 is (assuming that's the 64-bit score you are looking at and not the 32)
Haha, this shows how much of a different game Samsung is actually playing. Imagine if Apple did this -- they'd be ripped to shreds due to the expectations. With Samsung? "Ah, I see they did it again."
The reason this is of dubious morality is because they are using this code to make it look like their CPU is faster than their competitors ... even those who use the exact same CPU (LG) but didn't put in a governor to inflate the CPU speed. Some reviewers are even glowing about the benchmark scores and noting how much faster it is than the LG despite using the same CPU - when in fact it is no faster at all, it is simply running an execution path optimized for benchmarking. Any other phone could do the same and get higher scores. So this isn't about trying to show what the CPU is truly capable of if your app is optimized or runs a governor, this is about trying to inflate their scores over their competitors (mostly their Android competitors like LG) to make their phone look faster compared to them than it really is for marketing purposes.
Instead of innovating, they're copying and trying to cheat the benchmark. Meanwhile, Apple creates an M7, A7 and a whole lot of new things which are thought through and beyond known limits...
I don't think that Geekbench supports ARMv8 so it must be 32 bit. Look at the release date for the latest Geekbench version vs when Apple released support for ARMv8 in XCODE to developers.
what on earth are you talking about?
cheating is cheating. only cheaters think cheating is ok.
Read every post response to me when I made a similar point.
It's impossible to have an unbiased opinion when it comes to Samsung/Apple. You're one side or the other on this forum.
So if they developed code to run this around other apps (like the article vaguely mentions it does) it would be OK?
You're trying to tell me someone on XDA isn't going to be able to write up some code to inject into the system that would give the app they develop a boost if they wanted?
CPU governors have been available on Android since pretty much Day 1. I have been able to *artificially* boost the CPU power for a task based per app or overall. Yes, battery life suffered. Yes, performance increased. But at its core, which is the entire point here, the CPU was capable of doing it - just like this benchmark proved. The CPU did the work it was asked to do. The app was NOT compromised to get around tests, the CPU did the work.
No, if Apple did it then we wouldn't be talking about it at all. News sources would brush it under the rug.
Samsung is a joke lol. Apple will always be the superior company. If only there was a way to make others see this...like to baptize them or something.
Your view is plain incorrect.
The reason to run benchmarks is to measure what performance the device will produce in normal use. Samsung took steps to show 20% higher values without telling anyone. That's plain old cheating.
If Samsung had gone to Ars Technica and told them "please test how fast this phone can run in a special benchmarking mode", that would have been absolutely fine.
I happen to drive a car with a Diesel engine. The engine is quite deliberately limited. Over 2500 rpm, torque and horse power both drop. The engine itself could deliver the same torque at higher rpm, but that would very quickly damage the engine. The same car could run significantly faster if you were willing to accept that the engine won't last 200,000 miles but only 20,000 or only 200. If the manufacturer wrote "we removed all limits from the engine and achieved 150mph and managed to stop before the engine exploded" that's fine. If they wrote "the top speed is 150 mph" without mentioning engine damage, making their customers believe that they can also achieve that speed, that would be cheating.
Yes he's quite good at whoa is me, we're the victims.
It's just business, man up and quit whining Apple. If you're still sad look at the billions you have. With Apple greed knows no limits.
Many companies have done this and stuff like this in the past, and everyone of them have gotten their allotted share of critique.
Companies like Intel famously tweaks their compilers to produce better code just for some benchmarks, and ATI and nVidia have had special drivers so that certain benchmark runs in certain games ran optimally.