System Performance

2015 was not a great year for Android devices. Snapdragon 810’s problems with throttling severely crippled the performance of high end smartphones. In the case of the OnePlus 2, OnePlus went even farther by putting in code that would detect when Google Chrome was in use and completely shut off the A57 cluster on the SoC. This resulted in web browsing performance that was essentially no better than what you’d find on a $100 phone shipping with Snapdragon 410, which simply wasn’t acceptable given the fact that the OnePlus 2 was priced at around $400.

Like most of this year’s flagship Android devices, the OnePlus 3 uses Qualcomm’s Snapdragon 820 SoC. We looked at Snapdragon 820 not long ago in the LG G5 review and saw that it provided a substantial improvement over Snapdragon 810, which became even greater when you consider prolonged workloads where Snapdragon 810’s A57 cores throttle down and shut off. Given that OnePlus no longer has any reason to put in strange app detection code to manage thermals, we should see a good uplift in general performance and an enormous improvement in web performance.

Kraken 1.1 (Chrome/Safari/IE)

WebXPRT 2015 (Chrome/Safari/IE)

JetStream 1.1

The improvement in web browsing performance when going from the OnePlus 2 to the OnePlus 3 is staggering. This isn't unexpected when you consider that the OnePlus 2 was just running on Cortex A53 cores that were meant for low power scenarios while the OnePlus 3 is using Qualcomm's Kryo cores. In Kraken the OnePlus 3 is over four times faster, while in WebXPRT and JetStream it's at least over two times faster. The OnePlus 2 actually represented a large regression in web performance compared to its predecessor, and OnePlus has brought web performance back to a level that is competitive with the other smartphones on the market with the OnePlus 3.

PCMark - Web Browsing

PCMark - Video Playback

PCMark - Writing

PCMark - Photo Editing

PCMark - Work Performance Overall

PCMark is an interesting test because it depends just as much on a phone's software as it does on the hardware. We've seen how devices with the same SoC can perform very differently, especially in certain sub-tests like the Writing and Photo Editing tests where different runtime and OS optimizations can have a large impact. The OnePlus 3 is no exception, with it achieving higher scores than the LG G5 in every test except for video playback where they have roughly the same scores.

This is not unexpected, as it was demonstrated in the LG G5 review that the G5 has more conservative frequency scaling than the other Snapdragon 820 devices that we've seen, which is reflected in PCMark's tests. In any case, the OnePlus 3 actually gets close to the Huawei Mate 8 in the writing test, and beats it and the LG G5 by a large margin in the photo editing test. In the end the OnePlus 3 places second on our overall chart, with only the Huawei Mate 8 ahead of it, and the gap between it and the Mate 8 being smaller than the gap between it and the Zenfone 2 which is the next fastest smartphone.

DiscoMark - Android startActivity() Cold Runtimes

The OnePlus 3 is over two times faster than the OnePlus 2 with cold app launches where the application isn't resident in memory in any state. This is likely a combination of improved NAND performance, and changes to OnePlus's DVFS settings in addition to the performance improvements that Snapdragon 820 provides on its own. The impact that this has on the performance of the interface is significant, and when I reviewed the OnePlus 2 I noted how painfully slow it was to move around and through the applications. This new testing is a great example of that, with the OnePlus 2 taking 1.3 seconds just to launch apps, while the OnePlus 3 takes under 500ms and is the second fastest device here.

DiscoMark - Android startActivity() Hot Runtimes

The OnePlus 3 improves a bit over the OnePlus 2 when resuming apps that are resident in memory, but not by a great deal. In general, all our devices hover between 250 and 300ms here, with the exception of the Huawei Mate 8 and P9 which are really in a category of their own for performance. While there's no enormous improvement here, the OnePlus 3 is competitive with other high end devices in the market, so there's nothing to complain about either.

One thing worth noting is that our set of apps wouldn't come close to utilizing the OnePlus 3's 6GB of RAM. Unfortunately, no matter how many apps we added, this would actually still be the case. The reason is that OnePlus has implemented very aggressive app eviction from memory, which means that your 6GB of RAM is really just sitting there using energy, and in general the utilization is pretty low. This may be a holdover from when the OnePlus 2 shipped in a 3GB configuration, but it's something OnePlus needs to address in a future OTA update. I'd imagine the Android enthusiast community is already at work on, or has already created custom kernels to alter this behavior as well. With 6GB of RAM you should be able to comfortably keep all of a user's frequently used apps resident in memory.

It's great to see that OnePlus is producing a smartphone with competitive performance once again. When the OnePlus One launched, Snapdragon 801 was the best you could get in an Android smartphone. The OnePlus 2 was an unfortunate victim of Snapdragon 810's heat and throttling problems, but OnePlus certainly didn't help the issue by hardcoding in mechanisms to detect Google Chrome and shut the A57 cluster off entirely. With the OnePlus 3 you get some of the best CPU performance in an Android phone, with PCMark's real-world tests demonstrating noticeable gains over the LG G5 which also uses Snapdragon 820. If I had to sum things up in a single line I'd just say that it's good to see that OnePlus is back in the game.

Introduction and Design GPU and NAND Performance
POST A COMMENT

176 Comments

View All Comments

  • Brandon Chester - Sunday, June 19, 2016 - link

    I hope everyone is happier with the turnaround on this one c: Reply
  • hans_ober - Monday, June 20, 2016 - link

    Yes we are! I wouldn't mind it being two or more weeks late, but 3 months is inexcusable. Reply
  • theduckofdeath - Monday, June 20, 2016 - link

    Yeah, the delay on the big flagship reviews even makes a fast published like this one pretty pointless, as it only compares data with 2015 devices. And we've officially passed the 2016 summer solstice! Rage! \o/ Reply
  • close - Tuesday, June 21, 2016 - link

    Yes, passing the summer solstice always enrages me and saddens me a little... Reply
  • TheProv - Monday, June 20, 2016 - link

    Why did you reported only sequential speeds and not random speeds too? Reply
  • Ditiris - Monday, June 20, 2016 - link

    Quick turnaround, excellent review, much appreciated.

    Shame about the graphics display. I'm in the market, and as you say, a good display would make the phone almost a no-brainer, but instead their choices have more or less removed the phone from contention for me. Hopefully OnePlus rapidly makes good on their promise to update the display. I'll be watching for an update to your review.

    Small error on the Display page:
    I really don’t have anything else to say here, as I’m just so frustrated by OnePlus’s choices here,
    Reply
  • jospoortvliet - Monday, June 20, 2016 - link

    I would wait for the effect of sRGB settings but the low resolution on tgis can't be fixed of course.... Reply
  • niva - Monday, June 20, 2016 - link

    Sorry, the display is only a secondary concern for me. I'm much more concerned about the software and the updatability of the Oxygen OS. This device would be ideal as a Nexus phone, but no, that's too much to ask for.

    On the flip side I think sticking with 1080 is the right thing to do for a whole lot of reasons.
    Reply
  • jospoortvliet - Monday, June 20, 2016 - link

    Not pentile, though, not on this low resolution... for an ips this would be sufficient but the power usage advantage on amoled is far less and with less subpixels it really looks bad. Reply
  • peterfares - Monday, June 20, 2016 - link

    PenTile needs to die Reply

Log in

Don't have an account? Sign up now