GPU Performance

The Meizu M3 note uses an ARM Mali-T860MP2 GPU running at up to 546MHz. This is ARM’s current mid-range offering based on its Midgard architecture. The T860 shares the same feature set as ARM’s premiere T880, but uses only 2 ALUs/core instead of 3 ALUs/core like the T880, reducing overall shader performance by up to 50%. The T860 brings hardware support for OpenGL ES 3.1 + Android Extension Pack (AEP); however, the M3 note seems to be lacking driver support for some features like tessellation.

Xiaomi’s Redmi Note 3 uses an Adreno 510 GPU running at up to 600MHz. Qualcomm does not disclose architectural details about its processors, so all we can really say for sure is that this GPU is a member of the current Adreno series along with the Adreno 530, Qualcomm’s highest-performing GPU. The Adreno 510 also supports OpenGL ES 3.1 + Android Extension Pack (AEP), and the Redmi Note 3 did not experience any compatibility issues running through our benchmark suite.

GFXBench 3.1 T-Rex (Onscreen)

GFXBench 3.1 T-Rex (Offscreen)

Starting with the older OpenGL ES 2.0-based T-Rex game simulation, the Redmi Note 3 separates itself from its peers, easily outperforming the M3 note by a factor of 2.5. Unlike with general system performance, the Redmi Note 3 cannot get close to the same level of performance as higher-priced flagships; the Meizu PRO 5’s Mali-T760MP8 GPU is 68% faster in this test.

The M3 note performs about the same as the Honor 5X and its Adreno 405 GPU. It will be interesting to see if this holds in our other tests. Other than the Moto E, all of the phones in the charts above have 1080p displays, so there’s no real difference between onscreen and offscreen results. The Moto E’s onscreen performance is actually the same as the M3 note’s, albeit at a lower resolution.

GFXBench 3.1 Manhattan (Onscreen)

GFXBench 3.1 Manhattan (Offscreen)

GFXBench 3.1 Manhattan ES 3.1 (Onscreen)

GFXBench 3.1 Manhattan ES 3.1 (Offscreen)

Because only two other phones in this roundup could run the GFXBench Manhattan ES 3.1 test—a point showing that both the M3 note and Redmi Note 3 are ahead of the curve when it comes to graphics API support—we’re also including the results from GFXBench Manhattan, which uses an OpenGL ES 3.0 game engine that stresses lighting and pixel effects.

In Manhattan 3.0, the Redmi Note 3 once again outperforms the non-flagship phones, managing to just stay ahead of the ASUS ZenFone 2. The M3 note falls behind the Honor 5X with a more pixel-heavy workload. It’s even slower than the Moto E’s Adreno 306 GPU when running onscreen. The T860 GPU with only two cores seems insufficient when paired with the M3 note’s 1080p display.

The Redmi Note 3 extends its lead over the ZenFone 2 when running the newer OpenGL ES 3.1 version of Manhattan, while the M3 note continues to struggle.

3DMark Sling Shot 3.1 Extreme Unlimited - Overall

3DMark Sling Shot 3.1 Extreme Unlimited - Graphics

3DMark Sling Shot 3.1 Extreme Unlimited - Physics

3DMark Sling Shot Extreme is another OpenGL ES 3.1 game simulation test that stresses the GPU and memory subsystems by rendering offscreen at 1440p (instead of 1080p like our other tests). This test best highlights the disparity in peak graphics performance between flagship phones and less-expensive models. The Adreno 530 GPU in the OnePlus 3 and Xiaomi Mi5, along with the Mali-T880MP12 in the Galaxy S7, delivers more than 3x the peak performance than the Redmi Note 3. The M3 note, meanwhile, really struggles at such a high resolution, falling even further behind the Redmi Note 3. 

The M3 note consistently crashes when running Basemark ES 3.1, even though this OpenGL ES 3.1 test does not use tessellation. The Redmi Note 3 runs the test fine and scores the same as the Nexus 5X.

After seeing how these two phones performed during formal testing, I downloaded a few games from Google Play to see how they handled some real game code. The Redmi Note 3 loaded games more quickly than the M3 note and maintained playable frame rates in “Brothers in Arms 3,” a third-person shooter released at the end of 2014, and “CSR Racing 2,” a popular game based on OpenGL ES 3.0. There were some occasional stutters, but overall the games were playable. The chassis did get warm but not uncomfortably so.

The M3 note had no trouble keeping the frame rate above 45fps in “Angry Birds Star Wars II,” but the other two games I tried were not playable. Even at the lowest quality setting, “Brothers in Arms 3” chugged along at 8-12fps, and “CSR Racing 2” was not any better, averaging around 15fps. 

Based on our testing and first-hand experience, the Redmi Note 3 should handle most games currently available. It supports the latest graphics APIs, including support for tessellation, and is powerful enough to provide an adequate gaming experience, although gameplay will not always be perfectly smooth. The M3 note, like most phones in this price range, struggles when playing more demanding games. It’s certainly fine for playing casual games, such as side scrollers and puzzles, but its two-core GPU is undersized for playing 3D content at 1080p.

System Performance Battery Life & Audio Quality
Comments Locked

79 Comments

View All Comments

  • kpb321 - Tuesday, July 12, 2016 - link

    The article Matt posted is good but the short answer is that it is a combination of the Modem in the SOC, the antenna's/filters/amplifiers in the phone and the software configuration for the Modem that determine the supported band(s). Usually the antenna's/filters/amplifiers are the real limiting factor as modern SOCs all support a large variety of different bands and the software configuration can be changed.
  • Death666Angel - Tuesday, July 12, 2016 - link

    On that point, I think there are people on XDA who have flashed Qualcomm based Chinese phones with missing Band20 LTE and gotten it to work with Band20. Only QC based phones so far though.
  • adityarjun - Wednesday, July 13, 2016 - link

    Thank you all. I had a feeling it was the antenna/amplifier part. I will go over the article Matt posted. Thanks again.
  • ianmills - Tuesday, July 12, 2016 - link

    This review missed the biggest weakness of the xiaomi IMHO. The phone is very slippery and hard to hold. This causes me to hold the phone tightly in order to prevent dropping it. This leads to the next problem. The forced gripping of the phone means that my holding fingers often touch the edge of the screen which means lots of accidental presses. The capacitive buttons at the bottom of the phone are so close to the edge that they are accidentally touched as well.

    I could use a case to remedy this, but this is already as very big phone. Instead I put stickers on to give it texture and make it easier to hold. Works decent but the stickers keep fall off....
  • fanofanand - Tuesday, July 12, 2016 - link

    Sounds like my Nexus 4 that lasted all of 8 days before falling 3 feet to it's demise.
  • ianmills - Tuesday, July 12, 2016 - link

    Much worse than the N4. I remember the N4 being a problem until I learned to hold it properly. I've had the Xiaomi for about 4 months now and holding it is still a major problem. You won't think the N4 back glass is slippery anymore after holding this phone :P
  • Impulses - Thursday, July 14, 2016 - link

    Yeah, glass actually ends up stickier and mates more surface area against anything else... Brushed metal with very smooth edges and no trim ends up being very slippery.
  • Pissedoffyouth - Wednesday, July 13, 2016 - link

    I definitely don't have this problem. You can get ultra-thin grippy cases that don't add much bulk to the phone.
  • TheCurve - Tuesday, July 12, 2016 - link

    Solid and opportune review. Thanks for the good work, Matt
  • jjj - Tuesday, July 12, 2016 - link

    At least for SoCs you haven't reviewed before you guys need a CPU benchmark too. PCMark and Dicsomark are very software dependent and the browsing benchmarks are kinda sucky.

    The clear leader in perf per $ is the 360 Mobile N4. With Helio X20 (MT6797m) , 4GB RAM, fast charging at 899CNY(135$).

Log in

Don't have an account? Sign up now