Lumia 830 is a joke with spec


Recommended Posts

Cause CPU isn't the end all.  It has a front and rear LED camera that isn't a POS. A larger, better display, and other perks of a more premium device - like a camera button.

 

 

Exactly, it's not just one thing but everything overall that you should look at. 

What are you going to use that CPU on anyways?

a phone of course... :p

 

 

I've been disappointed with most of the new Lumia's over the previous models, the 530/535 seems worse than the 520, and the 635 lacks a lot of features the 625 had.

 

Not sure if I am even going to test the 830, I'll probably just be disappointed.

This is also why Android phone is better

I've been disappointed with most of the new Lumia's over the previous models, the 530/535 seems worse than the 520, and the 635 lacks a lot of features the 625 had.

 

Not sure if I am even going to test the 830, I'll probably just be disappointed.

 

The retail prices for the new ones also start lower than the older ones did, you should take that into account.   What did the 625 start off at and what did the 635 start off at?  

I upgraded from a 625 to a 830 and haven't regretted paying ?300 for the phone out-right

 

what I like

 

5" 720p screen (feels no different from holding the 625 which had a 4.7" screen)

10Mp Purview camera (with dedicated button)

Premium feel and look of the device

Sound Quality is excellent

excellent battery life

no lag when using the device

has the apps that I need

128Gb SD card support (currently using a 32gb Micro sdhc card)

  • 3 weeks later...

I think Microsoft should simplify its product line

530 (what we have now but with 1GB RAM and FFC)

630 (530 with larger screen)

730 (what we have now)

830 (730 + larger screen)

930 (current 930)

1030 (930 + larger screen)

1330 (930 + faster processor + super sampling PV camera = basically top end specs on all counts)

1530 (1330 + larger screen)

I think Microsoft should simplify its product line

530 (what we have now but with 1GB RAM and FFC)

630 (530 with larger screen)

730 (what we have now)

830 (730 + larger screen)

930 (current 930)

1030 (930 + larger screen)

1330 (930 + faster processor + super sampling PV camera = basically top end specs on all counts)

1530 (1330 + larger screen)

 

I think they should just have three models.

 

Lumia Nadella, a 4 inch phone with entry level specs.

Lumia Gates, a 5 inch phone with decent specs.

Lumia Ballmer, a 6 inch phone with cutting edge specs.

  • Like 4

This is also why Android phone is better

 

blondes are better then brunettes

Sorry but why should I spend over $400 on a phone that have the same CPU as the 635 and 535 for $120 and $49?

 

if you judge a phone by specs alone, you have a lot to discover outside the Android "more corez!!!!" model

I personally think they should adopt a naming model like this:

 

530: basic entry level with 3G, 512MB RAM, SD200, 3.8-inch 480p display.

531-534: 530 with simple internal spec-changes like RAM / antennae (carrier variants).

535: 530 with bigger screen (4.8" 540p)

536-539: 535 with internal spec changes.

 

630: premium entry level with 4G, 1GB RAM, SD200, 4" 480p display.

631-634: 630 with internal spec changes.

635: 630 with bigger screen (5" 540p)

636-639: 635 with internal spec changes (ISC, from now).

 

730: basic mid-range with 4G, 1GB RAM, SD400, 4.3" 720p display, 1/3" 7MP sensor

731-734: 730 ISC.

735: 730 with bigger screen (5.3" 720p)

736-739: 735 ISC.

 

830: premium mid-range with 4G, 1GB RAM, SD600, 4.5" 720p display, 1/2.5" 9MP sensor

831-834: 830 ISC

835: 830 with bigger screen (5.5" 720p

836-839: 835 ISC

 

930: flagship with LTE-A, 2GB RAM, SD800, 4.7" 1080p display, 1/2" 21MP sensor

931-934: 930 ISC

935: 930 6-month refresh (like 925)

936-939: 935 ISC

 

1030: hero device with LTE-A, 3GB RAM, SD810, 5" 1080p display, 1/1.5" 41MP sensor

 

1130: 530/630 6" 720p

1330: 730/830 6" 1080p

1530: 930 6" 1440p w/ stylus support

 

Also, MS should preferably discontinue the use of the ISC numbers, and stick with multiples of 5.

Dual-SIM variants of any device should share the device number. Instead of taking on a new number.

I personally think they should adopt a naming model like this:

 

530: basic entry level with 3G, 512MB RAM, SD200, 3.8-inch 480p display.

531-534: 530 with simple internal spec-changes like RAM / antennae (carrier variants).

535: 530 with bigger screen (4.8" 540p)

536-539: 535 with internal spec changes.

 

630: premium entry level with 4G, 1GB RAM, SD200, 4" 480p display.

631-634: 630 with internal spec changes.

635: 630 with bigger screen (5" 540p)

636-639: 635 with internal spec changes (ISC, from now).

 

730: basic mid-range with 4G, 1GB RAM, SD400, 4.3" 720p display, 1/3" 7MP sensor

731-734: 730 ISC.

735: 730 with bigger screen (5.3" 720p)

736-739: 735 ISC.

 

830: premium mid-range with 4G, 1GB RAM, SD600, 4.5" 720p display, 1/2.5" 9MP sensor

831-834: 830 ISC

835: 830 with bigger screen (5.5" 720p

836-839: 835 ISC

 

930: flagship with LTE-A, 2GB RAM, SD800, 4.7" 1080p display, 1/2" 21MP sensor

931-934: 930 ISC

935: 930 6-month refresh (like 925)

936-939: 935 ISC

 

1030: hero device with LTE-A, 3GB RAM, SD810, 5" 1080p display, 1/1.5" 41MP sensor

 

1130: 530/630 6" 720p

1330: 730/830 6" 1080p

1530: 930 6" 1440p w/ stylus support

 

Also, MS should preferably discontinue the use of the ISC numbers, and stick with multiples of 5.

Dual-SIM variants of any device should share the device number. Instead of taking on a new number.

 

Way too complicated.

I personally think they should adopt a naming model like this:

 

530: basic entry level with 3G, 512MB RAM, SD200, 3.8-inch 480p display.

531-534: 530 with simple internal spec-changes like RAM / antennae (carrier variants).

535: 530 with bigger screen (4.8" 540p)

536-539: 535 with internal spec changes.

 

630: premium entry level with 4G, 1GB RAM, SD200, 4" 480p display.

631-634: 630 with internal spec changes.

635: 630 with bigger screen (5" 540p)

636-639: 635 with internal spec changes (ISC, from now).

 

730: basic mid-range with 4G, 1GB RAM, SD400, 4.3" 720p display, 1/3" 7MP sensor

731-734: 730 ISC.

735: 730 with bigger screen (5.3" 720p)

736-739: 735 ISC.

 

830: premium mid-range with 4G, 1GB RAM, SD600, 4.5" 720p display, 1/2.5" 9MP sensor

831-834: 830 ISC

835: 830 with bigger screen (5.5" 720p

836-839: 835 ISC

 

930: flagship with LTE-A, 2GB RAM, SD800, 4.7" 1080p display, 1/2" 21MP sensor

931-934: 930 ISC

935: 930 6-month refresh (like 925)

936-939: 935 ISC

 

1030: hero device with LTE-A, 3GB RAM, SD810, 5" 1080p display, 1/1.5" 41MP sensor

 

1130: 530/630 6" 720p

1330: 730/830 6" 1080p

1530: 930 6" 1440p w/ stylus support

 

Also, MS should preferably discontinue the use of the ISC numbers, and stick with multiples of 5.

Dual-SIM variants of any device should share the device number. Instead of taking on a new number.

You should apply for a job at Nokia's sales&marketing when they start making phones again.

I think they should just have three models.

 

Lumia Nadella, a 4 inch phone with entry level specs.

Lumia Gates, a 5 inch phone with decent specs.

Lumia Ballmer, a 6 inch phone with cutting edge specs.

The Lumia Ballmer should be the model for developers.....

Way too complicated.

Actually, it's based on what they themselves have been trying to do all along.

 

It sounds complicated because I included an option for almost all devices Nokia has released so far. It'll be less complicated if they go by multiples of 5, in which case you would have:

 

530: basic entry level with 3G, 512MB RAM, SD200, 3.8-inch 480p display.

535: 530 with bigger screen (4.8" 540p)

 

630: premium entry level with 4G, 1GB RAM, SD200, 4" 480p display.

635: 630 with bigger screen (5" 540p)

 

730: basic mid-range with 4G, 1GB RAM, SD400, 4.3" 720p display, 1/3" 7MP sensor

735: 730 with bigger screen (5.3" 720p)

 

830: premium mid-range with 4G, 1GB RAM, SD600, 4.5" 720p display, 1/2.5" 9MP sensor

835: 830 with bigger screen (5.5" 720p

 

930: flagship with LTE-A, 2GB RAM, SD800, 4.7" 1080p display, 1/2" 21MP sensor

935: 930 6-month refresh (like 925)

 

1030: hero device with LTE-A, 3GB RAM, SD810, 5" 1080p display, 1/1.5" 41MP sensor

 

1130: 530/630 6" 720p

1330: 730/830 6" 1080p

1530: 930 6" 1440p w/ stylus support

 

There's still one for each screen size, but no room for devices with minor differences.

 

As a point of interest, a 1/2", 21MP sensor would have a pixel size of 2.2 microns, and each pixel would bring in 147% more light than a pixel in, say an iPhone 6, but I also believe nobody will really make smartphones with those sensor sizes anytime soon (but I hope that when they get there, Microsoft will be the first to do so in association with ZIESS, and NOT SONY, because that would hurt my ego pretty bad) :P

 

I think they should just have three models.

 

Lumia Nadella, a 4 inch phone with entry level specs.

Lumia Gates, a 5 inch phone with decent specs.

Lumia Ballmer, a 6 inch phone with cutting edge specs that is wet dream for developers.

Lumia Sinofsky, a 5 1/16 inch phone, that is oval, with a UI similar of late WM6.5 but with tablet elements, without a stylus and with the most vibrant colors, so vibrant that you must wear special googles just to use the phone.

 

There, fixed for ya!

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!