Friday, April 3, 2020

Samsung insists there is no performance difference between Snapdragon and its Exynos chipsets

Whenever Samsung releases a flagship phone, they usually launch two variants of it depending on the region the phone is released in. One model will sport Qualcomm's Snapdragon chipset, while the other will use Samsung's Exynos chipset, although there has been a growing outcry from customers to Samsung to stop using Exynos.

This is because according to a petition launched on Change.org, it seems that many customers with Exynos-based phones are discovering that they aren't quite as fast compared to the Snapdragon variants, but apparently Samsung begs to differ. In a statement made to SamMobile:

"The Galaxy S20 is a smartphone that's been reimagined to change the way you experience the world and depending on the region, the Galaxy S20 will either ship with the Exynos 990 or the Snapdragon 865. Both the Exynos and Snapdragon processors go through the same strict and rigorous, real-life testing scenarios in order to deliver a consistent and optimal performance over the entire lifecycle of the smartphone."

That being said, while we understand Samsung's decision to defend its own product, recent benchmarks have proven customer concerns to be true. In a review by AnandTech, they put the phones through benchmarks and discovered that the Exynos variants of the Galaxy S20 are slower in terms of performance compared to the Snapdragon 865 variants.

In some instances like web browsing, the difference is huge where the Snapdragon 865 scored twice what the Exynos models scored. In other instances, like video editing, the differences are marginal.

Given that customers pay the same price for either the Snapdragon or the Exynos models, it is understandable that there are some who feel that they might have gotten the short end of the stick. Hopefully with the outcry becoming more public than ever, Samsung will address these shortcomings in the next-gen Exynos chipset.

Source: SamMobile



from Phandroid https://ift.tt/2X8nZT2
via IFTTT

No comments:

Post a Comment