- #FROM GEEKBENCH OVER CHEATING ALLEGATIONS FULL#
- #FROM GEEKBENCH OVER CHEATING ALLEGATIONS ANDROID#
- #FROM GEEKBENCH OVER CHEATING ALLEGATIONS PRO#
#FROM GEEKBENCH OVER CHEATING ALLEGATIONS ANDROID#
The GPe versions aren't clean either, which makes sense given that they run the OEM's software with stock Android on top. This also helps explain why the Nexus 4 performed so slowly when we reviewed it - this mess was going on back then and Google didn't partake. None of the Nexus do, which is understandable since the optimization isn't a part of AOSP. Looking at the table above you’ll also notice weird inconsistencies about the devices/OEMs that choose to implement the cheat/hack/festivities. It’s a systemic problem that seems to have surfaced over the last two years, and one that extends far beyond Samsung. 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. 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. We started piecing this data together back in July, and even had conversations with both silicon vendors and OEMs about getting it to stop. I Can't Believe I Have to Make This Table The table below is a subset of devices we've tested, the silicon inside, and whether or not they do a benchmark detect and respond with a max CPU frequency (and all cores plugged in) right away: The second point however applied to many, many more platforms. We did a lot of digging to confirm that max GPU frequency (450MHz) was never exceeded on the Snapdragon 600 version. The first point applied exclusively to the Exynos 5410 equipped version of the Galaxy S 4. Also on Snapdragon platforms, all cores are plugged in immediately upon benchmark detect. So far, there's no official response from the company.Thanks to AndreiF7's excellent work on discovering it, we kicked off our investigations into Samsung’s CPU/GPU optimizations around the international Galaxy S 4 in July and came away with a couple of conclusions:ġ) On the Exynos 5410, Samsung was detecting the presence of certain benchmarks and raising thermal limits (and thus max GPU frequency) in order to gain an edge on those benchmarks, andĢ) On both Snapdragon 600 and Exynos 5410 SGS4 platforms, Samsung was detecting the presence of certain benchmarks and automatically driving CPU voltage/frequency to their highest state right away. It would be interesting to see how this story unfolds and if OnePlus will take any action. The effect is very similar though - benchmarks scores would indicate a level of performance that just isn't there for apps.
#FROM GEEKBENCH OVER CHEATING ALLEGATIONS FULL#
Instead OxygenOS was found run at its designed limit during benchmarks, whereas just about every other app gets less than the full performance. It's not quite the same case as the cheating modes in the past where manufacturers will tune their phones so they ignore thermal limits when running benchmarks. In Geekbench's books, this is performance manipulation and will also look into other OnePlus devices to see if the same applies to them as well. Or in other words, the system looks for specific apps to utilize its full performance rather than boosting performance when any app demands it. Geekbench says that the system makes performance decisions based on the applications' identifiers rather than behavior.
#FROM GEEKBENCH OVER CHEATING ALLEGATIONS PRO#
That's why Geekbench took the action of removing the OnePlus 9 and 9 Pro from its database. However OxygenOS would not offer the limited performance to benchmarking apps, which Geekbench sees as cheating. In essence, the OxygenOS analyzes the apps it will more often than not limit the performance in what we assume is a bid to extend battery life. In a recent lengthy and in-depth investigation, AnandTech found a very interesting "optimization" on the OnePlus 9 and 9 Pro when it comes to various apps.
0 kommentar(er)
