Smartphone benchmarking is something everyone does first whenever they want to find out the theoretical performance of a phone. It is one of the quickest ways to determine how good the phone performs
However, not all phones are honest about their benchmarks. Yesterday, on AnTuTu’s Weibo, the Realme GT got removed from its benchmarking platform for three months as it was accused of cheating its benchmarks, as a result, it also removed its “impressive” 750,000 score
In comparison, The Xiaomi Mi 11 scored only approximately 708,000 on AnTuTu, that’s 42,000 less points.
AnTuTu stated that the Realme GT score is “not a manifestation of true strength, but obtained through cheating and other means.”
How did they find out the phone cheated?
Cheating Method:
Realme GT Multi-threaded test 
Realme GT Image Test
Before the phone was announced, Realme VP Xu Qi Chase posted a screenshot of the phone’s initial benchmarks with a score of whopping 770,221, which is very high for a Snapdragon 888 device, as most phones using this processor averages for approximately 710K, and Qualcomm’s reference design only reached about 735K. Even if the score was indeed 750K, it still is questionable.
The phone reportedly used delay tactics to run the multi-threaded on its fastest CPU cores as much as possible, this delay tactics caused a higher-than-reality AnTuTu score. The phone was also alleged of manipulating images on the image testing benchmarks by modifying AnTuTu’s reference image. The phone lowered the quality of the image through mosaic colour blocks, causing lesser processing time thus revealing the image much faster albeit with a loss of quality.
Benchmark cheating is not a first for this and many other phones though. Last year, several Mediatek-powered phones were also accused of cheating and anti-competitive behaviour.
Sometimes companies manipulate the system in order to win favour from customers. They also do it to stand-out and say that their phone is unmatched from the competition.
Source: Android Authority, GSMArena.com
You must be logged in to post a comment.