The OnePlus 7 Pro is showing its immense power, even if the new Android phone hasn’t officially launched yet. The latest leak for the new OnePlus phone is a pair of GeekBench benchmark scores tweeted by @rquandt, and they’re showing excellent performance, though not quite the best performance of any Android phone.
The first benchmark shows a single-core score of 3,384 for the OnePlus 7 Pro's Snapdragon 855 chipset. It also scored 10,494 for the multi-core rating. The second benchmark is higher in both regards, with a 3,517 single-core score and a 10,811 multi-core score.
These are undeniably fast scores, and they bode well for the OnePlus 7 Pro positioning itself to be one of the fastest and best phones around. But, they don't earn it the top spot.
- The OnePlus 7 Pro will have an HDR10+ display
- Here's how OnePlus will ensure you get notifications on its new phone
- Check out the latest details for Android Q
Are benchmarking tests all over the place?
The multi-score score these OnePlus 7 Pro models have mustered are very close to the Geekbench scores we got in our tests for Snapdragon 855 chipset in the Samsung Galaxy S10 and Galaxy S10 Plus. Both of these phones earned a multi-core score of 11,002, giving them a slight edge over what we're seeing from the OnePlus 7 Pro.
That's the front of the pack at present, but that may not be the end of the story.
The leaked benchmarks only offer a small sample of the performance the OnePlus 7 Pro will be capable, and they're not official, as the phone hasn't launched yet.
As not every phone will score the same, it's possible as more and more OnePlus 7 Pro models get benchmarked, we'll start to see scores that edge out Samsung. In fact, an earlier (though, also unconfirmed) OnePlus 7 Pro benchmarking test was reportedly faster than Samsung’s best performance
With the launch of the phone scheduled for May 14 and sales expected shortly after, we won't have to wait long to find out.
- Here are details on the standard OnePlus 7
from TechRadar: computing components news http://bit.ly/2VfuQ8i
via IFTTT
No comments:
Post a Comment