Slashdot Mirror
Leak Shows What Could Be Nokia's New Windows Phone 8 Devices
Nerval's Lobster writes "Did images of Nokia's upcoming Windows Phone 8 smartphones leak a few days early? That's the question after a Twitter feed, @evleaks, posted a set of images early on Aug. 31. The first, it claimed, was of the '4.3-inch Nokia Lumia 820,' while the second purported to show the '4.5-inch Nokia Lumia 920 with PureView.' Corporate-sanctioned leaks are a fairly regular thing in the tech world, but they tend to follow well-defined patterns: a public-relations executive — wait, sorry, 'unnamed source' — will email a journalist with an image of an upcoming device, for example, or a disgruntled former engineer will data-dump information onto their blog. Glossy publicity images originating from a new, relatively unknown Twitter feed is less common, although the Twitter feed in question has leaked other images in the past."
Because Windows is just the worst mobile OS there is and MS are not to be trusted even if they did make a reasonable one. Even Symbian was better
They messed up in a big way when they left Maemo out to die
OH no they used the round corners that are claimed to be innovated and owned by Apple..!!
Someone call judge Koh!
Join the Slashcott! Feb 10 thru Feb 17!
non-twitter location for these please?
I hope this isn't the real debut of the Pureview technology on Windows Phone.
With that tiny lens assembly, it seems inevitable if it is the real deal that large compromises will have been made to the image quality.
For those who don't know, the Nokia Pureview technology, currently found only on a single Symbian phone, is a breakthrough in imaging quality on smartphones/compact cameras. It is hands-down the best image quality on any smartphone, it is arguably the very best compact camera in the world, and in some circumstances has even been demonstrated to outperform mirrorless cameras like micro 4/3.
I'm amazed and sorry for Nokia. How can such a big and successful company simply evaporate?
*crickets*
I am a Windows Phone early adopter (Lumia 800).
I just want to say: Fuck you Nokia, and Fuck you Microsoft. And you ask what Apple is doing that you are not. How about not leaving your users behind?
Fuck you.
These could have been MeeGo phones, with QT and the nice UI from Nokia N9.
I guess MS would have none of that.
"The agriculture ministry is not in charge of Gundam" - Japanese ministry official.
With a real windows kernel, native code, removable storage, GPU, explicit support for tightly integrated third party voip, better execution than andriod on development tools, application isolation and a coherent platform for developers it seems like a big win over any of Microsofts previous mobile platforms. If they really did fix my WP7 gripes as the limited information seems to suggest I'll definatly give it a try.
If Microsoft does allow third party apps to be installed outside the appstore the free choice in hardware and software for the platform is a big win in my view over the closed ecosystems where one company has control and a say over everything.
Now if only they would do something about the spartan butt ugly metro typography meme.
Except looking at a picture of cell phone is about the same as looking at a generic ATX case and saying "Look at how fast this computer is!"
This bears repeating.
http://www.elmundo.es/elmundo/2011/11/03/navegante/1320329583.html
MÃ"VILES | Ãsltimos modelos del fabricante
Nokia eligià nombre 'Lumia' pese a saber que significa 'prostituta' en español
Efe | Helsinki
Actualizado jueves 03/11/2011 15:13 horas
El fabricante finlandés de teléfonos mÃviles Nokia decidià bautizar su nueva gama de dispositivos dotados de Windows Phone con el nombre de 'Lumia' pese a saber que ese término significa 'prostituta' en español, informaron medios locales.
Después de que Nokia presentara la semana pasada el Lumia 800 y el Lumia 710, sus primeros teléfonos inteligentes equipados con el sistema operativo de Microsoft, diversos medios de comunicaciÃn, foros y redes sociales calificaron la elecciÃn de este nombre como una "grave metedura de pata" de la compañÃa.
Sin embargo, Nokia explicà que conocÃa esta acepciÃn, aunque finalmente se escogià el nombre porque 'lumia' es "una palabra española muy antigua caÃda en desuso desde hace tiempo".
SegÃn el diccionario de la Real Academia Española, 'lumia' es un sustantivo poco usado y de origen incierto que significa 'prostituta', y al igual que su variante 'lumi', forma también parte del argot urbano. ...
"Los resultados mostraron que mÃs del 60 por ciento de los consumidores españoles pensà que era un gran nombre para un producto de tecnologÃa mÃvil. Les sugerÃa en primer lugar 'luz' y 'estilo', en lugar del otro significado, mÃs oscuro y negativo", explicà la compañÃa en su blog oficial.
-------------------
So let's do the math. "More than 60 percent" can mean 66, so let's call it 2/3rds. The other third thinks you have a filthy mouth.
Heh heh
--
BMO
My Droid 1 is running ICS and will soon run JB. That is the advantage of an open source OS.
What advantage? The iPhone 3GS was released a few months before the Droid and the 3GS runs the latest version of iOS 5 and will soon be running iOS 6.
My Droid 1 is running ICS and will soon run JB.
That is the advantage of an open source OS.
What advantage? The iPhone 3GS was released a few months before the Droid and the 3GS runs the latest version of iOS 5 and will soon be running iOS 6.
The 3GS is painfully slow in iOS5. It's good that it works, but users should be warned before upgrading.
"I zero-index my hamsters" - Willtor (147206)
The 3GS is painfully slow in iOS5. It's good that it works, but users should be warned before upgrading.
The __OldModel__ is painfully slow in __NewOS__. Its good that it works, but users should be warned before upgrading.
Score:-1, Obvious
Because overheard "That guy from my job found me a used Lumia real cheap and that piece of trash had viruses all over!" could really get you in trouble.
My Droid 1 is running ICS and will soon run JB. That is the advantage of an open source OS.
What advantage? The iPhone 3GS was released a few months before the Droid and the 3GS runs the latest version of iOS 5 and will soon be running iOS 6.
The 3GS is painfully slow in iOS5. It's good that it works, but users should be warned before upgrading.
And the Droid 1 is not painfully slow in Android 4 (ICS) compared to the Droid 4?
The Droid 1 suffers even more than the iPhone 3GS. The Droid going from a 550 MHz single core CPU to a 1.2 GHz dual core while the iPhone goes from 600 MHz single core to 800 MHz dual core.
Actually it all depends on the application. I test on a 3GS running iOS 5. Slower but not painfully so. If your app does not take advantage of dual core (or more accurately threading) the boost is not that great. Keep in mind that a snappier more responsive user interface does not necessarily indicate performance. The user interface may update more quickly on a dual core but the task initiated by the previous action may still take about the same amount of time. User interface design and coding is sometimes about manufacturing the perception of performance.
You don't sue someone with no money.
My droid 1 is clocked at 1.2Ghz.
The lack of ram is a far bigger issue for the D1 and the 3GS than the CPU.
My droid 1 is clocked at 1.2Ghz.
Your 2009 Droid 1 is running at 1.2GHz rather than the 550MHz (underclocked from 600MHz) stated on Wiki and various other sites and the up to 600MHz stated on Motorola's developer site?
The lack of ram is a far bigger issue for the D1 and the 3GS than the CPU.
In terms of RAM the iPhone 3GS has 256MB compared to 512MB in the 4 and 4S. In comparison the Droid 1 has 256MB as well but the Droid 4 has 1GB.
Either way you look at it, CPU or RAM, the Droid 1 to Droid 4 comparison seems more painful than the iPhone 3GS to iPhone 4S comparison.
I'm more excited to see Jolla's offering
Yes my 2009 droid is overclocked to 1.2Ghz. I have in fact clocked it up to 1.25Ghz before.
The fact that the iPhone4S is more than a year behind in specs should not be held against the D1. Your examples do more to show how relatively outdated the iPhone 4S is than anything. Hopefully the 5 at least brings a 720p screen.
Also the Droid 4 should not be considered a successor since it has a locked bootloader and a low res screen. At the time the D1 was released it was a high res screen, higher than the 3GS by the way.
these phones have been moving around in nokia related companies for a long time now, im amazed no photos have leaked before, these confidentiality agreements must be working damn well. thats how it usually goes, we see a new prototype and half a year later world goes ooh-aah over some released pics and im like, man, this is old.
The 820 pic looks too much like the HTC HD7 that I'm typing this with.
Strange things are afoot at the Circle-K.
Your examples do more to show how relatively outdated the iPhone 4S is than anything. Hopefully the 5 at least brings a 720p screen. Also the Droid 4 should not be considered a successor since it has a locked bootloader and a low res screen. At the time the D1 was released it was a high res screen, higher than the 3GS by the way.
The point is not that the iPhone 4S is behind the Droid 4. The claim was made that an iPhone 3GS is painfully slow compared to the current model. My argument is merely pointing out that this is even more of an issue for the Droid 1.
If we accept your argument about the Droid 3 being the true successor then we have a device with the same RAM as the iPhone 4S and a 1GHz dual core CPU vs the 4S's 800 MHz dual core. My point seems to still hold.
Yes Apple seems to be releasing updated hardware months later than Motorola. If the iPad 3rd gen is a clue then a 1GHz CPU and 1GB RAM would be likely for the iPhone 5. I don't think the screen will go 720p. The previous screen update exactly doubled the resolution. That made software compatibility very high as the automatic scaling of graphics worked very well. I suppose they could just run existing apps in a 960x640 subset of the screen with a black frame filling out the rest of the 1280x720 display. That is similar to what happens when running an iPhone app on an iPad.
bullshit, they call it ios5 but they take out half the features. Microsoft is just being honest (they give you most of the features of windows 8 with 7.8) they just don't call it 8. If apple changed to a more advanced kernel the 3gs would be dropped in a heart beat.
the iphone is finally coming in more than 2 colors!
They lost a lot of good will by planting their former employer Elop as the new CEO of Nokia to not only push WP but also destroy any independent OS Nokia had been building up until then. This is especially troublesome since one of them was the only attempt at an open true Linux OS (QT compatible!) on the mobile market. While the N900 was more of a hacker's tool the N9 universally got great reviews, it simply lacked support from Microkia as it was serious competition to WP (and any other advanced smartphone OS that nowadays tries to mimic true multi-tasking). They paid Nokia off with 1 billion USD to toss their indepency aside and go from free software to walled garden.
No the droid 3 is not a successor either. It is also a locked down mediocre device. There is no motorola equivalent.
Apple is not months behind they are now at least a year behind. The point is a 3GS is slower than a D1.
I doubt the iPhone5 will have a 1920x1280 screen, but that would be great. The point I was making is the current iPhone screen is a relic and badly needs to be updated. The DPI should hopefully at least stay the same, but the device will be slightly larger.
No the droid 3 is not a successor either. It is also a locked down mediocre device. There is no motorola equivalent.
Apple is not months behind they are now at least a year behind. The point is a 3GS is slower than a D1.
I doubt the iPhone5 will have a 1920x1280 screen, but that would be great. The point I was making is the current iPhone screen is a relic and badly needs to be updated. The DPI should hopefully at least stay the same, but the device will be slightly larger.
The point is a 3GS is slower than a D1.
How is the 3GS slower, the D1 and 3GS have the same CPU and RAM? The D1 CPU is 8% slower and its running Java apps rather than native binaries but that is nitpicking. And no, I do not count overclocking. That is not the user experience that nearly all D1 users had/have. Plus overclocked CPUs, especially severely overclocked like the one described generally have errors. Note that not all overclocking induced errors are obvious, resulting in crashes, etc. Sometimes the CPU simply gives the wrong answer after a specific sequence of instructions. The sequence and errors are different for every overclocked CPU so its not something easily tested for.
I doubt the iPhone5 will have a 1920x1280 screen, but that would be great.
I was not suggesting that. That would seem pointless given that we are already at the limits of the human visual system. 3 to 3GS was a doubling but that would seem to be a one time thing. I'm just arguing that an increase to 720p seems unlikely since it is not a whole number multiple, a 30% taller screen would be needed to maintain pixels per inch and keep unstretched legacy apps just as readable. Yes it would be nice for new apps but I expect too many backwards compatibility problems. Besides, on a 3.5 inch screen can one really see a difference in a video rendered at 960x640 vs 1280x720?
The D1 can be clocked far higher than a 3GS, the D1 can run a stripped version of Android, the D1 can have swap enabled or other such tricks. Yes, testing after overclocking is needed.
To not include those is just apple fanboism. These are real advantages that I use. An open OS has these advantages.
We are not at the limits of human vision. I am human and can see the pixels on an iPhone4S. I can see the difference on 3.5" screens. Hopefully, the iPhone5 will be a little larger though. I think you need a visit to the eye doctor not named jobs.
There is no testing for overclocking. Again, errors can be subtle, a simple incorrect answer and it can be dependent upon instruction sequences. The sequence of instructions can vary, the type of error can vary, the point at which an individual CPU begins experiencing such errors can vary, ... overclocking makes devices unreliable.
There is lots of testing, people have been doing this with desktop CPUs for years.
We are talking about a phone here, not the computer in charge of launching the nukes. If it becomes unreliable clock it down, not a major risk.
Have you never overclocked a desktop CPU?
There is lots of testing, ...
There is lots of inadequate testing, its the nature of the beast with respect to overclocking.
Again. The failure mode is not "works fine" vs "crashes". At some speed a particular CPU will experience failures. These failures will start out quite subtle, literally 2+2=5 sort of stuff and will progress in severity as higher speeds are attempted. Where the subtle failures begin, and where that line is crossed between subtle and crashing, will be different for every CPU. The prerequisites for these failures will differ. A certain sequence of instructions may be needed on one CPU, a different set of instructions on a different CPU. Maybe specific data patterns are required. And by different CPUs I am talking about two CPUs that came off of the same production line, not different makes and models.
Unless you have very sophisticated test apparatus, the sort of stuff only Intel, AMD, etc have, you really can't effectively test an overclocked CPU. All you can hope to achieve is to recognize the CPU that fails earlier and harder than its peers.
The false sense of security in overclocking is in part due to the way CPU vendors once filled orders. For simplicity lets say a vendor offered a CPU in slow, medium and fast versions. The production line only makes the fast version. CPUs that fail testing at fast are retested at medium and slow. Sometimes there would be more slow CPUs ordered than were available, so the company would sell CPUs that actually passed testing at medium or fast as slow CPUs. An overclocker might get lucky. He might buy a slow CPU that actually passed testing at fast. However the overclocker has no way of knowing if this is the case, or if the CPU sold as slow really did fail testing at fast. Again, that failure may only be recognizable by the special testing rig the vendor has, and not by some test suite an end user has.
... people have been doing this with desktop CPUs for years.
And experiencing the exact sort of problems I described. Sometimes aware, sometimes not.
We are talking about a phone here, not the computer in charge of launching the nukes. If it becomes unreliable clock it down, not a major risk.
Still its a hobbyists/hacker thing where unreliability is accepted to a degree. Which is why I don't count overclocking as a performance improving option for the public at large. Another reason I don't count overclocking is that it shortens the lifespan of the CPU. That is another long discussion and I assume I am boring you enough. :-)
Have you never overclocked a desktop CPU?
More importantly I've had experience identifying the subtle sort of problems I described.
The x86 CPUID instruction can return a vendor id string, "GenuineIntel" for Intel CPUs. I've seen an otherwise seemingly working CPU return a vendor id string with a one bit error when overclocked, misspelling the string. I've seen an otherwise seeming working CPU throw a general protection fault when loading an immediate value into a register when overclocked (if you haven't programmed in assembly language just trust me that the preceding is impossible in a working CPU), and dependent upon a certain sequence of instructions. I've seen basic math instructions (ADD, MUL, etc) return erroneous results, causing an array index calculation to go horribly wrong in a seemingly working overclocked CPU. By seemingly working in all these cases I mean the machine booted and appeared to run fine, appeared to run various apps and games fine, but one program or the other would consistently crash or misbehave when overclocked.
So what?
What does this have to do with anything? Yes, over clocking can possibly have repercussions, so can getting out of bed in the morning.
All you are saying is that you are an apple fanboy and will discount anything that is at all modified from the way the one true jobs gave it to you.
So what? What does this have to do with anything?
You asked for my experience with overclocking.
Yes, over clocking can possibly have repercussions, so can getting out of bed in the morning.
You just don't (or do not want to) get it. Its not "can possibly have", its "usually does have".
All you are saying is that you are an apple fanboy and will discount anything that is at all modified from the way the one true jobs gave it to you.
Yeah, demonstrating that overclocking makes CPUs unreliable and shortens their life is Apple fanboyism. That is quite desperate. Given your desperation to cling to the notion that overclocking is good for everyone I suggest you rethink who is the fanboy in this discussion.
Too bad it does not do either of those regularly.
I actually do overclock a D1 and it has been doing fine for years that way.
I am not suggesting anything is good for everyone, but my reality conflicts with your claims.
my reality conflicts with your claims.
Really. How does your reality conflict with the subtle type of errors that I discussed, the simple incorrect calculation rather than a crash? The type of error that goes by unnoticed. Recall the Intel FDIV bug? Overclocking errors can result in errors of that nature but different in their specifics on every CPU.
Because it does not impact my life.
Errors so subtle no one notices them are not important. I am not doing my taxes on my D1. BTW the only reason the D1 was ever clocked down to 550 was for battery life.
Where is the risk? Oh noes my grocery list might be off by 1 carrot!