Huawei is about to launch its annual flaghip – The Mate 50 series and the news about the P60 series has already started circling over the internet. The latest one revealed that the Huawei P60 series could come with a chipset made by TSMC AKA Taiwan Semiconductor Manufacturing Company.
According to the input coming from DigitalChatStation, Huawei may get access to a TSMC-made chipset for next year’s Huawei P60 series. However, the tipster suggests that the phone lineup could still be using Qualcomm SoC.
If we look into past launches, Huawei has brought in Snapdragon 888 chipset with the P50 series. The processor was locked only for 4G access and was made by Samsung. However, it’s reported that Huawei P50 series devices with Qualcomm chipset overheated in intense use cases as compared to Kirin 9000.
The Huawei Mate 50 lineup will also be equipped with a Snapdragon chipset but a new one such as the Snapdragon 8 gen 1 but still it may be 4G. Meanwhile, we cannot confirm whether the chipset is supplied by Samsung or TSMC, because they shared the yield for this order from Qualcomm.
Yes, there could be some changes that we may feel in terms of performance and power consumption between the chipset made by Samsung and TSMC.
To be mentioned the tipster has not shared any further details on this matter but the current one seems very interesting.
Two flagship returns:
A report has revealed that Huawei will return to the dual flaghip launch year tradition in 2023. It directly means that the Huawei P60 and Mate 60 series will launch in the same year.
Why it was changed?
Due to past scenarios, Huawei had issues making new smartphones and in 2021, for the first time, Huawei launched only one flaghip – Huawei P50 series. While in 2022, the Chinese tech maker will unveil another – Mate 50 series.
So, from next year, we’ll be able to see, Huawei running a full-on show in the smartphone world.
The post Huawei P60 series to use TSMC made chipset appeared first on Huawei Central.
from Phones Archives - Huawei Central https://ift.tt/sTluU3P
0 Comments