Redmi K30 leaked poster hints at vertical quad rear-camera setup, dual front cameras
We’ve come across multiple reports about the rumoured Redmi K30 smartphone, information about which has leaked quite a few times by now. A previous report revealed the phone’s screen and now, a new image of the handset has surfaced online, which gives us our best look yet at its rear panel and the main camera setup. The Chinese actor Wang Yibo is apparently endorsing the handset and a new promo image of the actor holding the phone seems to have leaked online. As per a Weibo post that has since been removed, via DroidHolic, the images showcase a new design for the camera setup on the Redmi K30.
It can be seen that the handset sports a centrally placed, vertically stacked quad-camera setup on the back. There’s a circular ring around the camera with a gradient design below which 5G text is placed and no fingerprint sensor is to be spotted on the rear. One would expect Redmi to use an in-display fingerprint sensor on the upcoming handset but as per previously leaked information, the device might come equipped with an LCD screen, which doesn’t support in-display fingerprint sensor. Thus, the fingerprint option is said to move on the right edge of the device.
Another image of the phone, which shows the device from the front, reveals a dual front camera setup, which is housed in a punch-hole display. There are thin bezels around the screen, which are a bit noticeable. The Redmi K30 is expected to be launched in just over a week’s time but it seems like the usual bout of rumours and leaks will be making the rounds on the internet before the smartphone is officially announced.
A previous report about the handset suggests that it could be powered by the Qualcomm Snapdragon 730 or a Snapdragon 730G SoC. It could be equipped with a 6.66-inch screen with a 120Hz refresh rate giving it that smooth interface. Furthermore, Xiaomi CEO Lei Jun has already confirmed that the device will run on MIUI 11 at launch.
from Latest Technology News https://ift.tt/2RexexP
No comments