Nokia Lumia 920 spec list will reportedly include 8-megapixel camera, wireless charging [UPDATED]Alex Wagner - Editorial Director of News and Content
Late last week, some alleged renders of the Nokia Lumia 920 made their way online, offering an early glimpse at what may be one of Nokia's new Windows Phone 8 handsets. Now some of the device's purported specs have made their way online to give us a better idea of what the Lumia 920 is all about. According to sources speaking to The Verge, the Lumia 920 will feature wireless charging capabilities thanks to a magnetic strip hidden in the phone's rear, and the Qi wireless power standard is said to be supported. The Lumia 920 will also reportedly pack an 8-megapixel rear camera that Nokia is planning to brand as PureView due to its image stabilization capabilities and camera software. We're also told to expect a 4.5-inch HD display, 1.3-megapixel front shooter, 1.5GHz dual-core processor, 32GB storage and 1GB RAM on the Lumia 920.
So long as these rumored specs hold true, it sounds like Nokia is really planning to take advantage of Windows Phone 8's new hardware support to beef up its new flagship handset, though I'm sure some folks will be bummed that the 41-megapixel camera found on the 808 PureView isn't making its way into the Lumia 920. Still, Windows Phone fans on AT&T should be pleased with the 920, and they could have the opportunity to get one to call their very own in late October or early November. Thankfully we won't have to wait that long to get our first official peek at the device, as it's expected to be introduced at Nokia and Microsoft's big shindig in New York City on Wednesday. So what do all of you Windows Phone folk think of the Lumia 920 as it's rumored today? Think it could be your next phone?
UPDATE: The @evleaks Twitter account has posted more Nokia device images, one of which is a wireless charging pad. The red puck has room for a smartphone to be placed on top of it to be charged. Below that is another shot of both the Lumia 920 and 820, respectively, also posted by @evleaks.