Friday, January 5, 2018

Nokia 6 (2018) leak brings us images and spec details

We’ve seen a handful of Nokia-branded Android phones launch in the past year, but now it looks like HMD Global is planning to update its first Nokia handset.

The Nokia 6 (2018) has leaked out. Chinese retailer Suning has posted images and spec details of the device, spilling just about everything there is to know about it before HMD or Nokia actually announces it.

Design-wise, the new Nokia 6 looks fairly similar to the old one. There are a couple of differences worth noting, though, like the removal of the capacitive buttons and fingerprint reader on the front of the phone. That fingerprint reader has been moved around back, below the rear camera.

One of the more notable internal upgrades of the Nokia 6 (2018) is its processor. While last year’s Nokia 6 came with a Snapdragon 430 chipset, the new model comes equipped with a Snapdragon 630. It’s also packing 4GB of RAM, just like its predecessor, and 32GB or 64GB of storage. There’s also a microSD slot in there if you need even more storage.

nokia62018colorsleakaam

Other specs of the Nokia 6 (2018) include a 5.5-inch 1920×1080 display, 16-megapixel rear and 8-megapixel front cameras (both with f/2.0 apertures), a 3,000mAh battery, a microUSB port, and a 3.5mm headphone jack.

The Nokia 6 comes preloaded with Android 7.1.1 Nougat, but an upgrade to Android 8.0 Oreo is planned.

Pricing for the Nokia 6 (2018) is expected to start at CNY1499 ($240 USD) for the 32GB model. If you’d prefer the more capacious 64GB version, it’ll cost you CNY1699 ($261 USD).

Considering that Suning has all of these graphics and details about the Nokia 6 (2018), an official launch can’t be too far off. Overall the new Nokia 6 looks like a solid upgrade, offering an upgraded processor, 4GB of RAM, and an aluminum frame, all for around $250. Now we just have to wait for HMD to officially announce the thing so we can find out where else in the world this thing is going to launch.

nokia62018cameraleakaam



source: androidandme

0 comments :