Chinese Company Oppo is the Latest To Be Caught Cheating on Phone Benchmarks (engadget.com)
An anonymous reader shares a report: You can add another big name to the list of phone makers found cheating on benchmarks. UL Benchmarks has delisted Oppo's Find X and F7 phones from its 3DMark charts after testing from itself and news outlet Tech2 revealed that both devices were artificially ramping up processor performance when they detected the test by name. Oppo acknowledged that it always stepped things up when it detected "games or 3D Benchmarks that required high performance," but claimed that any app would run full bore if you tapped on the screen every few seconds to signal your actions. UL, however, rejected the justifications. It was clear that Oppo was looking for the benchmark by name and not the extra processing load involved, according to the outfit. Moreover, tapping wouldn't be an effective solution if Oppo treated apps equally -- you couldn't get consistent results. Further reading: Huawei Caught Cheating Performance Test For New Phones.
I suspect mostly everybody does that from Facebook to Volkswagen etc. so it isn't limited to technology.
Just don't get caught I guess...
Everything I write is lies, read between the lines.
It seems to me that it'd be fairly easy to add a slider control in the settings app that would let you choose power-saving vs. performance. When full, everything gets the CPU's full capabilities. Put it right next to the control for screen brightness, which people already go to when they want a bit more battery life.
Then you can publish any measured benchmarks you want, and claim great performance and battery life, while pitching the configurability as a feature.
You do not have a moral or legal right to do absolutely anything you want.
They copied the idea from Volkswagen.
sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
GM also lied here too. Never under estimate the reach of American companies.
Gosh, haven't seen that before! /sarcasm
...that values being clever over doing the right thing, with a cool eye toward the consequences.
Adding melamine to baby formula to jack up the protein content? Clever. Not so clever when babies become sick and die because of kidney failure.
Ripping off designs from other companies? Clever. Not so much money needed for R&D. Not so clever when consumers find out there's an inferior product under that familiar user interface.
Cheating on benchmarks? And so it goes...
Those who can, do. Those who can't, write technology blogs.
Years ago, when graphics cards where slow enough that text output was benchmarked, some magazine found their benchmarks on a particular test ran 3 times slower than everyone elses.
Their test displayed the string "The quick brawn fox jumped over the lazy dog." with a spelling error. Everyone else ran the benchmark with the correct text. It turned out the driver maker checked for this particular string, and had a ready-made bitmap for this strong stored into the driver. So they could use a bitblit instead of text drawing and ran three times faster. In the benchmark only.
repost
My boss slaps a folded-over InfoWorld magazine onto my desk, thick enough to kill a rat with in those days. He says with obvious glee, "How bout dem apples?"
It is Steve Gibson's INFOWORLD column of March 8 and Gibson (with obvious glee) has caught a manufacturer of Hercules graphics cards red-handed. The standard WinBench program had conducted a series of tests --- and in one particular test of text display, in which the phrase "The quick brown fox jumped over the lazy dog's back then sat on a tack" is continuously painted on the screen --- the card performed oddly spectacularly. It was that one score that when combined with the others, ranked the card above the competition. Suspicious, Gibson changed a single letter in the test phrase and the card's score dropped to a reasonable range. The card was apparently recognizing that a test was in progress and 'cheating' by failing to actually over-write this static text repeatedly.
I love the comment by the manufacturer when Gibson contacted them (read it!) but what intrigued the industry the most was that the cheat was not to be found in the Windows driver code, it had been embedded into the firmware of the accelerator chip. In the next Winbench version the test phrase jumped around the lazy screen's back during the test, rendering the cheat obsolete.
<blink>down the rabbit hole</blink>