The Nokia 9 is expected to feature a Penta-rear camera setup and come with a a 5.99-inch PureDisplay panel with 2K resolution and HDR10 support.

Nokia 9 PureView with penta camera setup leaked in live images ah...


  • Live images of Nokia 9 leaked online.
  • The image showcase a penta-camera setup on the phone’s back.

HMD Global has already announced that it will unveil some new devices at the upcoming Mobile World Congress 2019. One of the expected phones is the Nokia 9 Pureview that is more or less confirmed to feature a penta-cameras setup on the back. Now, ahead of the official announcement, a couple of live images of the Nokia 9 PureView have surfaced online. The images are possibly the best look at the Nokia 9 PureView till date, even though the phone has leaked extensively in the past. These images were obtained by NokiaPowerUser and while the publication has not cited its source, they are in-line with the renders we’ve previously come across.

The first image gives us a better look at the rumoured phone’s display and front-design. The Nokia 9 PureView can be seen with a standard 18:9 display, without a notch. There are still slightly thick bezels above and below the phone’s display. The Nokia logo can be seen on the upper right corner, besides which is a single front camera, and the ambient light/proximity sensors are on the upper-left corner of the display. The newly leaked images (above) of the upcoming Nokia flagship phone also show off the penta camera setup, however, they seem a bit dubious since there is no Zeiss, Nokia, or Android One branding that we have come to expect on a Nokia phone (and which was also seen on previously outed renders). While the five cameras placed on the back are similar to some previously leaked renders of the phone, it looks like there could be a case on the back panel. 

Previously leaked Nokia 9 renders

Nokia 9 PureView Specs

The Nokia 9 PureView recently passed through China’s 3C certification website that suggested an 18-watt fast charger could be bundled with it. In terms of specifications, it is speculated to be launched running on the Qualcomm Snapdragon 855 processor, however, the device has been rumoured for so long that it could potentially end up with a Snapdragon 845. In that case, Nokia would be making a big mistake as most of its competition is readying Snapdragon 855 devices. Almost all rumours suggest the presence of the Snapdragon 845, that could be coupled with 6GB RAM and 128GB of internal storage. The smartphone could come equipped with a 5.99-inch PureDisplay display panel with 2K resolution and HDR10 support. 

Related Reads:

Alleged Nokia 9 PureView passes China’s 3C certification, launch expected soon

Nokia 9 PureView’s leaked press render hints at in-display fingerprint sensor, reaffirms penta camera setup on the rear

Digit NewsDeskDigit NewsDesk

‘).insertAfter(‘.inside-container p:eq(1)’); */
// $( ” ).insertAfter(‘.inside-container p:eq(0)’);
//method to trunkate the text
function shorten(text, maxLength) {
var ret = text;
if (ret.length > maxLength) {
ret = ret.substr(0,maxLength-3) + “…”;
return ret;

//function to put utm on DontMiss links
$(‘div.dontMiss > a’).each(function(){
$(this).prop(‘href’, $(this).prop(‘href’)+’?utm_source=within_article&utm_medium=desktop&utm_campaign=related’);
//trunkate dont miss content
var sub = shorten($(this).html(),47);
$(‘div.dontMiss > a’).each(function(){
$(this).prop(‘href’, $(this).prop(‘href’)+’?utm_source=within_article&utm_medium=mobile&utm_campaign=related’);

//disabled method to append dontmiss links to page content by Mayank
/*$(‘div.dontMiss > a’).each(function(index){
//loop over each list item

// if(index%2 > 0){
// index = index – 1;
// }
if($(‘.inside-container > p:eq(‘+index+’)’).length){
$(‘.inside-container > p:eq(‘+((index * 2) + 1)+’)’).append(‘

Related: ‘ + $(this).html() + ‘‘ );
$(‘.inside-container > p:eq(‘+((index * 2) + 1)+’)’).append(‘

Related: ‘ + $(this).html() + ‘‘ );

/* if(isDesktop()) {
} */

* ga event tracking on page scroll start and end by Mayank

// Debug flag
var debugMode = false;

// Default time delay before checking location
var callBackTime = 100;

// # px before tracking a reader
var readerLocation = 150;

// Set some flags for tracking & execution
var timer = 0;
var scroller = false;
var endContent = false;
var didComplete = false;

// Set some time variables to calculate reading time
var startTime = new Date();
var beginning = startTime.getTime();
var totalTime = 0;

// Get some information about the current page
var pageTitle = document.title;

// Track the aticle load — disabled
if (!debugMode) {
// ga(‘send’, ‘event’, ‘Reading’, ‘ArticleLoaded’, pageTitle, {‘nonInteraction’: 1});
// console.log(“ga(‘send’, ‘event’, ‘Reading’, ‘ArticleLoaded’, pageTitle, {‘nonInteraction’: 1}”);
} else {
alert(‘The page has loaded. Woohoo.’);

// Check the location and track user
function trackLocation() {
bottom = $(window).height() + $(window).scrollTop();
height = $(document).height();

// If user starts to scroll send an event
if (bottom > readerLocation && !scroller) {
currentTime = new Date();
scrollStart = currentTime.getTime();
timeToScroll = Math.round((scrollStart – beginning) / 1000);
if (!debugMode) {
ga(‘send’, ‘event’, ‘Reading’, ‘StartReading’, pageTitle, timeToScroll, {‘metric1’ : timeToScroll});
} else {
alert(‘started reading ‘ + timeToScroll);
scroller = true;

// If user has hit the bottom of the content send an event
if (bottom >= $(‘.inside-container’).scrollTop() + $(‘.inside-container’).innerHeight() && !endContent) {
currentTime = new Date();
contentScrollEnd = currentTime.getTime();
timeToContentEnd = Math.round((contentScrollEnd – scrollStart) / 1000);
if (!debugMode) {
if (timeToContentEnd = height && !didComplete) {
currentTime = new Date();
end = currentTime.getTime();
totalTime = Math.round((end – scrollStart) / 1000);
if (!debugMode) {
ga(‘send’, ‘event’, ‘Reading’, ‘PageBottom’, pageTitle, totalTime, {‘metric3’ : totalTime});
} else {
alert(‘bottom of page ‘+totalTime);
didComplete = true;

// Track the scrolling and track location
$(window).scroll(function() {
if (timer) {

// Use a buffer so we don’t call trackLocation too often.
timer = setTimeout(trackLocation, callBackTime);

‘).insertAfter(“.inside-container p:eq(2)”);


Source link