AndroidTM Benchmarks

Performance Comparison of Android Devices

Notes On the Graphs

Below is a list of factors to take into consideration when view the benchmark graphs.

Minimum Sample Size

For a device type to be included on the charts it needs to have had at least 5 submitted results. This is to help avoid a single really good or really bad result from throwing a device into a completely incorrect place in the chart. Due to the final score being an average of all benchmarks submitted for that device it is still possible for one or more incorrect results to throw off the whole result when there is a small sample size. For this reason we have included information in the graph about how many devices of that type have been benchmarked. To see this information simply move the mouse over the bar of the device you are interested in. A higher sample size means the data is more likely to be accurate. (Update: for a couple of new rare devices we have included results from a single sample.)

An Example of the Charts Tooltips
An example of using the charts tool-tips to get more information.
In this case, it is showing that the "Acer Iconia Tab A500" has an overall average PassMark of 2,035. It is ranked 6th, has 2 samples and an average CPU Mark of 2,490.

Different Operating Systems and different environments

The PerformanceTest Mobile software is designed to run on several different versions of Android operation systems. These different OS have different levels of efficiency and as such a specific device might perform better or worse depending on what OS is installed. Many of these results were submitted by our users. In some cases some of the devices might have had configuration issues leasing to sub-optimal results. When a large number of samples are available this is not an issue but when only a small number of results are available it can sway the results.

Real Life Performance Comparison

The rating the devices are given here represents their peak performance and not necessarily their real world performance with any specific software application. This is especially true in the case of devices with multiple cores. While PerformanceTest Mobile was designed to make use of all cores/CPU’s at once, many real world applications are not designed with this in mind, especially older applications. Unlike single core/CPU systems these systems will only show their full potential in high-performance situations such as when heavily multitasking is required, the average user might not see nearly as much improvement from them.

Naming of Devices

Due to the fact that these graphs are automatically generated the names of the devices have been taken straight from the devices themselves. However, some devices do not provide correct names. This can be seen in cases where custom ROMs are loaded onto the device. The actual device may identify themselves as something different. From time to time, we will try to clean up the names and make them more readable. In some cases we have picked up names of rare or low volume devices. Just because you haven't heard of a particular device, doesn't mean it doesn't exist.

Version of PerformanceTest

The current results have been collected over using PerformanceTest Mobile V3 and up. As of Apr 28, 2020, we are no longer providing PerformanceTest Mobile V2 and older results. The last result list for PerofrmanceTest Mobile for Android V2 can be found here. The current data on public charts is from PerformanceTest Mobile V3 and above.

What happened to V4 through V9?

See the FAQ, Why did versions jump from V3 to V10 for the Android release and how does this effect the results?

Duplication of Device types in the graph

Some people have contacted us to tell that we have messed up and duplicated various devices in the graph . To the best of our knowledge this is not the case. What we have done is separate out devices by their model.

In other cases, there may appear to be a duplication, such as with the Samsung Galaxy S II (SC-02C) and Samsung Galaxy S II (GT-I9100). In this case Samsung has released two different versions of this same device. In situation where the device specifications are simliar enough, we will try to group them together under a single entry.