Our attention is all focused on the Xiaomi Mi 6X, smartphone for which the launch event for the next 25 in April has now been confirmed. Our favorite Chinese company, however, continues to work tirelessly on the development of other terminals, among which, we have seen, there are the mysterious Xiaomi Comet e Sirius.
These two devices will be equipped with the promising SoC Snapdragon 710, what we knew until a few days ago with the name of Snapdragon 670, but according to what has been revealed in the last hours it seems that they will be joined by an additional smartphone equipped this time with a chip Mediatek.
The flea in the ear about the possibility of a device Xiaomi with SoC Mediatek had already put some time ago some rumors circulating on the web, but it is good to remember how they were referred to the Mi 6X and its alleged adoption, then denied, of the Mediatek Helio P60.
What now instead appears to be a Xiaomi with Mediatek chip is it Xiaomi Cereus, a terminal completely new to the news and that only in the last hours has made its first appearance on the database of the well-known benchmark portal GeekBench.
Xiaomi Cereus: check out a new terminal with a Mediatek chip!
The Xiaomi Cereus is a terminal that comes with a SoC Eight-core Mediatek operating at the frequency of 2.0 GHz, a chip whose code name is MT6765 and that most likely is what we will know how Helio P40. This is able to totalize in single core an average score of 745 points, while 3562 in multi core: the results comparable to those of a SnaNagon 625 and therefore suggest a hardware equipment of the mid-range device.
The recording on GeekBench also shows us how the Xiaomi Cereus is equipped with 3 GB of RAM and how its software is based on the latest incarnation of the operating system of the green robot, namely Android 8.1 Oreo. In light of all this we can say that we are facing a device belonging to the Redmi range of the Chinese brand.
Information on this alleged end here Xiaomi Cereus, information which, it should be specified, must be taken with the pliers given the nature of the leak. I remind you that creating fake reports on GeekBench is a pretty easy task for those who can fiddle with the build.prop file of an Android terminal and that therefore the fake could very well hide around the corner.
[Source]
