Monday, August 20, 2018

Huawei Mate 20 renders surface, show off unique triple camera setup

At some point in the near future, Huawei is going to launch a phone called the Mate 20. And, when it arrives, it may feature one of the more unique camera setups we’ve seen on the back of a smartphone to date.

Thanks to the folks over at XDA-Developers, we’ve got a look at the upcoming Huawei Mate 20. They state that they built these renders based on photographs of the actual handset that they were able to see. Unable to post those photos for now, the renders show us what Huawei is working on, and it certainly looks like an interesting device.

Huawei-Mate20-front-leak

Up front, the Mate 20 is going to have a notch, but will be teardrop-shaped and small. It’s good to see that we’re already getting very small notches, because if we have to have them it’s never a bad thing to have them take up as little space as possible. That notch will host the front-facing camera along with a front-facing speaker just above it.

The report has the major bullet points in the specs department filled out: a 6.3-inch AMOLED display with a resolution of 2244×1080, a HiSilicon Kirin 980 processor, 6GB of RAM, and 128GB of built-in storage. There may be other variants available at some point, too, but the report doesn’t have any information on those.

The Mate 20 will reportedly feature a 4200mAh battery, a 3.5mm headphone jack, USB-C port for charging, and it will be running Android 9 Pie out of the box.

Huatei-Mate20-rearcamera-leak

But most striking is the triple rear camera setup. Instead of having a vertical orientation, these three cameras will be housed in a square with rounded corners, with the three cameras taking the top-left, bottom-left, and bottom-right spots. The top-right spot will play host to the flash.

And that’s all we’ve got about the upcoming Mate 20. The rumor mill will more than likely have more to offer soon enough, before Huawei makes the handset officially official.

What do you think of the handset’s design?



source: androidandme

0 comments :