Meizu makes a gaffe and responds to the release of the Snapdragon 865+ SoC

Yesterday the eternal rival of MediaTek, the US Qualcomm, presented a new SoC. This looks like an evolution of the previous top of the range and is called Snapdragon 865 +. In this article we have seen all the features of the chip in detail, but we will do more here. Remember when the Meizu's CMO had confidently stated that the processor in question would not be released in 2020? Well, he made a gaffe but he came out with his head held high this morning. Let's see what he said on the Chinese social network Weibo.

According to Meizu's CMO, the Snapdragon 865+ was not supposed to come out this year: things change too quickly according to the brand

In fact, things change too quickly. If the company was really aware of the processor's non-exit Qualcomm Snapdragon 865 +, it means that the manufacturer had announced something to all the telephone houses. Apparently, however, the cards on the table have changed and, contrary to what Meizu expected, the SoC has made its appearance.

meizu snapdragon 865+

In this post published this morning on the Chinese social network Weibo, the company said it was amazed by the news. "SoC news changes very quicklyHe would have said, implying that she was unaware of the impending presentation of the chipset. But what really interests us is what is said below. The Italian translation is what it is, but what is understood by the words of the brand is that it will not focus on the production of another smartphone.

In fact, in line with what he had already announced, Meizu will not produce other top of the range for this year. Rather, it will focus on its latest flagship Meizu 17 (and 17 Pro), improving and maturing it thanks to continue OTA updates. We are of the opinion that the Chinese company is the most correct line of all: there is no need for new top of the range products every six months.

What do you think about it?

Source | Weibo

0 0 vote
Article rating
Subscribe
Notify
guest
0 Declarations
Inline feedback
View all comments