After years of being a rumoured product, the Nokia 9 PureView cold finally see the light of day, if the device that passed China’s 3C certification is indeed the illusive device.

Alleged Nokia 9 PureView passes China's 3C certification, launch...


  • Nokia 9 Pureview could launch during MWC 2019
  • Nokia 9 PureView is rumoured to sport 5 rear cameras
  • Nokioa 9 Pureview has been rumoured since 2017

The Nokia 9 has been the subject of relentless rumours of over two years now. We first heard rumours of the phone back in 2017, and as the years have passed, the rumours just keep coming. In the last few months, rumours of an upcoming Nokia 9 have been gaining some credibility though, with leaks of purported cases and what not. Now, it would seem that the Nokia 9 might have an actual launch date.

HMD Global owned Nokia has announced their event for 24th February during the Mobile World Congress days. Incidentally, a phone with the product code TA-1094 has passed China’s 3C certification process, leading many to believe that this is the Nokia 9, and it could be announced at MWC 2019. However, we do strongly urge some caution as we know that when Nokia launches a phone in China, it may or may not come to international markets right after. The listing says that the phone will be accompanied by an 18watt fast charger, but nothing else. There are no details on the specifications or even the design of the phone.

What we do know, and can naturally expect, is for the phone to sport Zeiss Optics, given that the two companies renewed their partnership last year. A case that leaked earlier showed 7 holes on the back, 5 presumably for the 5 cameras, one for the flash and the seventh hole for an optical sensor. What we can speculate is that the Nokia 9 could come with the Qualcomm Snapdragon 855 processor, which would make sense given that flagship devices should sport flagship specs, but given how long there have been rumours around this phone, it is possible that the prototyping concluded before the Snapdragon 855 was made available to OEMs. Hence, it could potentially just end up coming with a Snapdragon 845. Almost all rumours point to the phone featuring the Snapdragon 845, possibly mated with 6GB of RAM. Rumours also suggest that the Nokia 9 could rock a QHD display. It might also sport a hefty battery.

Rumours of this nature regarding the announcement of the Nokia 9 have come up before, especially around major international events like MWC and even Nokia’s own global product launches, so we would suggest taking this one with a pinch (or two) of salt.

Related Read: Nokia 9 launch postponed due to camera issues: Report

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