Lenovo was teasing from some time for launching the first fully bezel-less smartphone, but instead they launched Lenovo Z2 which has top-notch, and now another company is all set to launch world’s first smartphone with almost no bezels and will have nearly 100 percent screen to body ratio. Vivo will be launching NEX smartphone on 12th June. Vivo has already showcased Project APEX in Mobile World Congress earlier this year and they had proved that they are capable of developing a truly bezel-less smartphone.
APEX was more like a prototype but now it seems company is all set to launch this device for public and this device is ready to hit the shores and it will be named Vivo NEX.
As per the news company will launch NEX next week on 12 June and Vivo might launch two variants of it the NEX and NEX S.
Recently this smartphone has been seen on live video which appeared on Unicorn Show in China and in video we were unable to see any bezel or any top-notch on the smartphone.
And in this too, fingerprint sensor has been placed under the display which we had first seen on Vivo X21, but unlike X21, here fingerprint sensor is covering nearly half of the screen.
When it comes to specs, then Vivo Nex will have 6.59 inch Full HD+ display screen, under the hood Vivo S will be powered by Qualcomm Snapdragon 845 along with 8GB of RAM while Vivo Nex will be the first smartphone to be powered by Qualcomm Snapdragon 710 processor with 6GB of RAM, both will come with 128GB of storage.
When it comes to camera front, it will have a vertically stacked dual rear camera modules at the rear, 12-megapixel and 5-megapixels and as told earlier, it will have a pop-up selfie camera of 8-megapixel sensor. When it comes to connectivity front, it supports dual-band Wi-Fi, Bluetooth 5.0, GPS, NFC and LTE.
It houses a 4,000mAh battery and support fast charging at 22.5W, which mean it is faster than Dash Charging from OnePlus.
In past we have seen screen becoming bigger and bigger but still manufacturers were unable to find a truly bezel-less smartphone, but this could be a bug step in this direction.