what is ur expecting specs for flagship WP 8 lumia phone?


Recommended Posts

mine are

CPU - dual core 1.5GHz

RAM - 1 GB

Storage - 16/32/64 versions

Display - 4.3 inch ClearBlack HD (720 x 1280 pixels)

Camera- 16 MP with PureView technology

Video Recording -1080p HD recording capability

Data Connectivity - LTE

Protection - Corning Gorilla Glass 2

microSD Card Support

Sounds about right. If it's using PureView tech though, way higher MP count. It really only works because of ludicrous megapixels.

Chip will likely be the MSM 8960 Pro, if the WP8/Win8 similarities are to be believed.

mine are

CPU - dual core 1.5GHz

RAM - 1 GB

Storage - 16/32/64 versions

Display - 4.3 inch ClearBlack HD (720 x 1280 pixels)

Camera- 16 MP with PureView technology

Video Recording -1080p HD recording capability

Data Connectivity - LTE

Protection - Corning Gorilla Glass 2

microSD Card Support

I only care about storage and microSD support. The rest of the specs for CPU, display and camera will be a bonus. I think 16MP PureView sounds a bit insane for this year. :)

I understand mentioning the screen resolution, but why mention the screen size? That's completely user dependant in my opinion, I don't want a 4.3" screen.

Yeah, I'm not sure I want 4.3 either feels to big in the pocket. In regards to hardware it will just have whatever hardware Microsoft says it needs just like windows Phone has always worked.

mine are

CPU - dual core 1.5GHz

RAM - 1 GB

Storage - 16/32/64 versions

Display - 4.3 inch ClearBlack HD (720 x 1280 pixels)

Camera- 16 MP with PureView technology

Video Recording -1080p HD recording capability

Data Connectivity - LTE

Protection - Corning Gorilla Glass 2

microSD Card Support

????????????

You expect three different memory versions AND SD Card support? Pick one or the other, having both is dumb.

how its dumb?? its always good to have more storage

Because a manufacturer would never do it, it doesn't make sense for them. Companies either choose the several different fixed memory route (16/32/64) or they choose throwing xx(usually 16gb) memory in with SD card support. Not both.

Sure it'd be nice but not at all realistic and since this is called 'expecting specs' some realism has to be applied.

Because a manufacturer would never do it, it doesn't make sense for them. Companies either choose the several different fixed memory route (16/32/64) or they choose throwing xx(usually 16gb) memory in with SD card support. Not both.

Sure it'd be nice but not at all realistic and since this is called 'expecting specs' some realism has to be applied.

There is nothing in his post that implies that a manufacturer must make three different sizes with SD card support for one product line - the different sizes are simply optional for the manufacturer. Without SD card support, there are no Windows Phone 7/7.5 product lines that I am aware of that provide varying storage, just one size (4GB, 8GB, or 16GB). Rather, the manufacturers differentiate whole devices, like the Lumia 710 and Lumia 900.

mine are

CPU - dual core 1.5GHz

RAM - 1 GB

Storage - 16/32/64 versions

Display - 4.3 inch ClearBlack HD (720 x 1280 pixels)

Camera- 16 MP with PureView technology

Video Recording -1080p HD recording capability

Data Connectivity - LTE

Protection - Corning Gorilla Glass 2

microSD Card Support

Multi-core processors tend to have a lower clock speed than their single core peers, which translates to lower performance per core, but higher performance when maximized. As a result, I would expect a clock speed reduction with the addition of multiple cores. I would not be surprised to see a dual core, 1.2 GHz chip appear in deference to the current single core 1.4 GHz chips (1.5 GHz in HTC Titan/Titan II). Unless there is an honest need, I do not want them to put in 1 GB of RAM for two reasons: it will create an unnecessary performance gap for older phones, assuming they get the update (thus destroying their utility with WP8, natively developed games, which would almost certainly develop for the higher specifications) and it will add cost where it is unnecessary. Honestly, Tango-based phones are getting only 256 MB of RAM and the iPhone 4S still runs on just 512 MB of RAM; there is very little reason that a higher performance kernel should cause the amount of RAM to go up.

I am happy with 16 GB of storage, and I think I would prefer 32 GB in preference to them providing a microSD slot. Otherwise it's just another way for dust and lint to sneak into my phone.

As for the camera, I always want a nicer camera, but I do not want the bubble that exists with the 808 (maybe your suggestion of 16 MP will make that possible). I also find that my camera's tend to suck on phones no matter what because the lens will always end up getting scuffed up by my pocket's lint over time.

For a premium phone, Gorilla Glass is practically a must; my Samsung Focus S definitely did not have it, and I could tell by the cheap feel as well as the two scratches that appeared thanks to my empty pockets (just part of Samsung's overall effort of degrading their quality in order to increase their profits). And to be competitive, they really must use the thinner Gorilla Glass 2.

  • Like 1

There is nothing in his post that implies that a manufacturer must make three different sizes with SD card support for one product line - the different sizes are simply optional for the manufacturer. Without SD card support, there are no Windows Phone 7/7.5 product lines that I am aware of that provide varying storage, just one size (4GB, 8GB, or 16GB). Rather, the manufacturers differentiate whole devices, like the Lumia 710 and Lumia 900.

Samsung Focus :) I have the original Samsung Focus 8GB + 32GB microSD in it. Running perfectly ever since Mango came came out.

that is only sensor size, the resulting photos are IIRC 8MP max.

Yes, it's sensor size, but output size can be chosen by the user. You just get less pixel-grouping with higher megapixel counts (ergo, the higher the output resolution, the more its output becomes like just a 'normal' camera). It can output at up to 38mp on device. I'm reasonably certain I've seen 41mp stills from the 808 as well. And for what it's worth, they looked pretty damn good even at full resolution.

1.4 ghz dualcore s4 chipset. gfx core looks to be quite powerful

768MB ram (doesnt need anymore than that really)

16/32GB storage. doubt 64GB will come in any flavour of phone

no micro SD support

4.3inch screen 1280x768 clearback amoled

16 mp camera. (if it had pureview itd be 41mpx but may sacrifice the spec to have it)

Gorilla glass 2 definately

front camera

thats what i think it will have

I guess I should remind people that the Qualcomm Snapdragon S4 chips, the most likely for WP8, can only make use of a camera up to 20 megapixels. Without some sort of clever external downscaling chip this is the largest you will see.

I guess I should remind people that the Qualcomm Snapdragon S4 chips, the most likely for WP8, can only make use of a camera up to 20 megapixels. Without some sort of clever external downscaling chip this is the largest you will see.

I believe though, if we follow the Win8 and WP8 same core line of thought, that WP8 will allow for Nokia to use another SoC brand and not limit us all to using Qualcomm SoCs like with WP7.x. It's one of the things OEMs have wanted from the start, it'd also help lower costs for them and thus for us.

As far as the whole storage bit goes, I have a 16GB phone from the start and have yet to even use half of it, I dunno, I just don't load up lots of music on it. Having said that, maybe if I had 32GB I'd add more but it's hard to say. One thing though, and why I think 32GB might be limited to only a small number of high end phones is that WP8 should bring with it even more skydrive integration. By that I mean into the music+video hub as well. When you have 25GB (unless you're new and only have 7GB) of online storage to put music up and then stream it to your phone the need for more physical storage, at least for some people, is less.

I guess I should remind people that the Qualcomm Snapdragon S4 chips, the most likely for WP8, can only make use of a camera up to 20 megapixels. Without some sort of clever external downscaling chip this is the largest you will see.

It's still quite possible. HTC use a third party imaging chip on the Titan II for processing, and given that PureView is a collection of technologies, if the technology were to come to Windows Phone, it's likely an additional imaging chip would be added. One way or another, PureView will come to Windows Phone. Pretty sure Nokia already confirmed that.

This topic is now closed to further replies.
  • Posts

    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
    • Tor Browser 15.0.17 by Razvan Serea Protect your privacy. Defend yourself against network surveillance and traffic analysis. Tor is a network of virtual tunnels that allows people and groups to improve their privacy and security on the Internet. The Tor software protects you by bouncing your communications around a distributed network of relays run by volunteers all around the world: it prevents somebody from watching your Internet connection and learning what sites you visit, it prevents the sites you visit from learning your physical location, and it lets you access sites which are blocked. The Tor Browser Bundle lets you use Tor on Windows, Mac OS X, or Linux without needing to install any software. It can run off a USB flash drive, comes with a pre-configured web browser to protect your anonymity, and is self-contained. Tor Browser 15.0.17 changelog: All Platforms Updated Tor to 0.4.9.11 Updated NoScript to 13.6.25.1984 Build System / All Platforms Bug tor-browser-build#41821: Update gpg subkeys for boklm Bug tor-browser-build#41827: Update morgan's keychain with renewed key Download: Tor Browser (64-bit) | Tor Browser (32-bit) | 109.0 MB (Open Source) View: Tor Browser Website | Other Operating Systems Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      526
    2. 2
      +Edouard
      265
    3. 3
      PsYcHoKiLLa
      146
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!