While benchmarks don’t always provide a realistic impression of day-to-day performance, they still do give an idea of the raw processing power your phone carries. AnTuTu has now become one of the more popular Android benchmarking applications out there, and this update brings it to version 3.0.1.

At first glance, the app seems to have a new Holo-inspired interface, which allows actions like swiping between screens, but not much else. Internally however, it does bring a new OpenGL ES 2.0 3D benchmark to test 3D gaming performance, and a new 2D benchmark to test 2D gaming performance as well as a variety of bug fixes. It also adds a nice comparison page where you can compare your phone’s score against the score of many other phones on the market.

Here’s the complete changelog of v3.0.1:

  • New OpenGL ES 2.0 3D benchmark for 3D game performance test.
  • Fully new 2D benchmark for 2D game performance test.
  • Add compare page to compare scores with hot devices.
  • Auto stop the benchmark if detected the app has been modified.
  • Redesigned and adjustment app UI.
  • Enhance SDCard path detection.
  • Fixed some web page auto pop up bug.
  • Fixed sometimes get stuck in splash screen.
  • Fixed submit score page appear twice after benchmark.
  • Update Italian and Ukraine translate.

AnTuTu remains true to its roots and keeps its solid benchmarking process that we are all familiar with. It continues to give you the breakdowns of the scores by category along with the comparison with other phones mentioned earlier.

Tanay Sood
Tanay is a sophomore at Rutgers University studying Business Analytics and Information Technology. A veteran prowler of the XDA forums, his current phone of choice is Nexus 4. You will usually find him scouring the web for new ROM's to flash or new sitcoms to watch.
  • Justin W

    I’m not sure why, but my Nexus 4, prior to the update, was only scoring about 9000. After the update (which brought new graphics tests as well), I am scoring well over 17,000. Are these benchmarking softwares not well-received by JB 4.2, or is there something else causing this large of a change in benchmarks?

    • Not all benchmarks are accurate for the Nexus 4 because some processors are unused/deliberately under clocked to conserve power. Of course, during real life use, you wouldn’t notice a thing (because when the cores are NEEDED, they WILL be used). So it’s possible that the high scores the second time around are due to the dev optimizing the tests to take full advantage of the 4’s processing power.