Nokia only sold 330k Lumia in the US


Recommended Posts

7.8 Says they're not abandoning them. they shoudl have just named it WP8 and avoided the crap as that's what it is, WP8 for older phones, just like older iphones get limited new iOS versions.

Except apps released targeting Windows Phone 8 won't run on Windows Phone 7.8 devices while Apps written for iOS 6 will run on the 3GS, iPhone 4 and iPhone 4S.

So expect the market place to become very fragmented as developers make the decision of whether to use the newer API's present in Windows Phone 8 or target the older Windows Phone 7 ecosystem and limit what their apps can do.

The original article it links to use two 3rd part number to come up with <300k number and it might not be accurate. also it was reported a week ago.

This new estimate is based off Nokia's own official number. so it's more accurate.

T-Mobile selling well could just mean 30k like you said. T-mobile didn't publish any sales number so its hard to interpret selling well.

So out of the 600K, if they sold only 330K Windows Phones then what about the balance 270K? Or did they somehow magically shipped 200K N9s? or People suddenly bought 270K of those dirt cheap prepaid Nokias?

Except apps released targeting Windows Phone 8 won't run on Windows Phone 7.8 devices while Apps written for iOS 6 will run on the 3GS, iPhone 4 and iPhone 4S.

So expect the market place to become very fragmented as developers make the decision of whether to use the newer API's present in Windows Phone 8 or target the older Windows Phone 7 ecosystem and limit what their apps can do.

So Apps targeting iOS6 APIs will magically work on older releases? The phones you list are the phone being sold today and possibly when iOS6 ships. Not entirely direct comparison.

So Apps targeting iOS6 APIs will magically work on older releases?

iOS 6 is being released for the iPhone 3GS. That is a phone that came out several years ago. So if you write an app for iOS 6 it will run on the 3GS. And you can also write an app that will launch and run on iOS5 and iOS6 at the same time. One binary, two different target OS versions and you can choose to include extra API's that will only be used when utilised under an iOS 6 device. But again 3GS, came out in June 2009, still gets iOS 6.

Lumia 900 bought today - Doesn't get Windows Phone 8.

iOS 6 is being released for the iPhone 3GS. That is a phone that came out several years ago. So if you write an app for iOS 6 it will run on the 3GS. And you can also write an app that will launch and run on iOS5 and iOS6 at the same time. One binary, two different target OS versions and you can choose to include extra API's that will only be used when utilised under an iOS 6 device. But again 3GS, came out in June 2009, still gets iOS 6.

Lumia 900 bought today - Doesn't get Windows Phone 8.

So? If Apps target 7.8 APIs, they will work on Lumia bought tomorrow. What's different? At least Microsoft has decency to play fair unlike Apple (3G and iOS 5 were a disaster).

Edit: I don't want to defend Microsoft on 7.8 and I think they should have ported WP8 down to at least the second generation Windows Phones. All I am saying that what they are doing is not very different than similar crap that Apple does (3G & iOS5 or 4 & Siri) or Google continues to do with Android.

Edited by BajiRav

So? If Apps target 7.8 APIs, they will work on Lumia bought tomorrow. What's different? At least Microsoft has decency to play fair unlike Apple (3G and iOS 5 were a disaster).

I loved my 3GS and it ran iOS 5.0 brilliantly. I think you really need to stop reading this stuff online that people moan about because people only moan when there's a problem and those people who have issues with iOS 5 in combination with the 3GS are doing something wrong or have a faulty device.

And the real problem I have with Microsoft is their abandonment of their devices sold today, even devices sold in the future. Pretty much any phone sold right up until Windows Phone 8 launches has been abandoned and once developers begin to target Windows Phone 8 you won't be able to get those new apps for the old devices but with the iPhone, even the iPhone 3G with iOS 4 or the iPhone 3GS with iOS 5 you can still use the App store and get the latest apps.

Would you buy a new Windows Phone today knowing Windows Phone 8 is coming? I wouldn't. But I know people buying iPhone 4S's today knowing iOS 6 is coming.

I loved my 3GS and it ran iOS 5.0 brilliantly. I think you really need to stop reading this stuff online that people moan about because people only moan when there's a problem and those people who have issues with iOS 5 in combination with the 3GS are doing something wrong or have a faulty device.

And the real problem I have with Microsoft is their abandonment of their devices sold today, even devices sold in the future. Pretty much any phone sold right up until Windows Phone 8 launches has been abandoned and once developers begin to target Windows Phone 8 you won't be able to get those new apps for the old devices but with the iPhone, even the iPhone 3G with iOS 4 or the iPhone 3GS with iOS 5 you can still use the App store and get the latest apps.

Would you buy a new Windows Phone today knowing Windows Phone 8 is coming? I wouldn't. But I know people buying iPhone 4S's today knowing iOS 6 is coming.

3G, not 3GS. I edited my previous post. I might be jumbling version numbers but I think the last update to my 3G made it next to unusable.

So out of the 600K, if they sold only 330K Windows Phones then what about the balance 270K? Or did they somehow magically shipped 200K N9s? or People suddenly bought 270K of those dirt cheap prepaid Nokias?

Nokia didnt suddenly or magically sold 270k devices.. It has always sold other phones in US but not so much

Nokia sold 1.5 million phones last year during the same period(when Lumia was not even released in US)...

their other phone sales has been reducing in the US market... check the earning sheet its clearly mentioned.

On a related note, Microsoft has again ran away from posting actual numbers but at least they say WP units have doubled Q/Q as per slides on MSFT's earnings call.

Look at Slide #12 here

http://www.microsoft.com/global/investor/RenderingAssets/Downloads/FY12/Q4/SlidesFY12Q4.pptx

(I found the snapshot on techcrunch linked from theverge but since I didn't want to link to techcrunch, I took pains to find this :p )

side note: what a horrible PPT theme.

On a related note, Microsoft has again ran away from posting actual numbers but at least they say WP units have doubled Q/Q as per slides on MSFT's earnings call.

Rough calculations, IDC said Microsoft shipped 3.3 million WP7 devices in Q1 so if sales doubled then they shipped 6.6 million in this quarter, with about 70-80% of the sales from Nokia.

And the real problem I have with Microsoft is their abandonment of their devices sold today, even devices sold in the future. Pretty much any phone sold right up until Windows Phone 8 launches has been abandoned and once developers begin to target Windows Phone 8 you won't be able to get those new apps for the old devices but with the iPhone, even the iPhone 3G with iOS 4 or the iPhone 3GS with iOS 5 you can still use the App store and get the latest apps.

Would you buy a new Windows Phone today knowing Windows Phone 8 is coming? I wouldn't. But I know people buying iPhone 4S's today knowing iOS 6 is coming.

Eh developers that need specific WP8 hardware features can use the 8 SDK, if you don't need those specific features use the 7.8 SDK and your app will work on both. It's pretty much just a drop down box you choose when you're about to compile your app.

And lets be honest, Apple majorly screwed over iPhone 4 owners when they made Siri 4S only even though it was a simple piece of software that connects to Apple's servers. So they aren't exactly saints ;)

7.8 Says they're not abandoning them. they shoudl have just named it WP8 and avoided the crap as that's what it is, WP8 for older phones, just like older iphones get limited new iOS versions.

This is quite frankly the stupidest idea I've heard, and what's surprising is that it even gets repeated so often. Version numbers are there for a reason. When developers see a version number, they know that they can expect a standardized kernel, APIs, and software stack across the board (even if hardware specs might differ across devices). The version number isn't there to appease end users, it's a traditionally important piece of information for developers. The reason that Apple can call iOS 6 for the 3GS as iOS6 is that, even though it lacks Siri, it still shares the same APIs and stacks as iOS 6 on the iPhone 4S and 5, and if any incompatibilities do arise it's going to be due to hardware, not software. Microsoft calling WP7.8 as WP8 when it in fact uses a completely different kernel and APIs is just going to royally **** developers off. It means that they can't effectively target their code for WP8 anymore. It means that you have to write your app twice for the "same" platform, it means that when users report bugs and say they're running WP8 you're going to have to ask them if they're running the real WP8 or the fake one, it means that the SDK and the development process is basically going to be a pile of crap.

It means that you have to write your app twice for the "same" platform, it means that when users report bugs and say they're running WP8 you're going to ask them if they're running the real WP8 or the fake one, it means that the SDK and the development process is basically going to be a pile of crap.

No you don't have to.

If you aren't targeting WP8 features, you compile your app for 7.8 (when it comes time to compile there's a dropdown box with the options 7.0, 7.1, 7.8, 8) and then it will work on both WP7 and 8. If you need to target a specific WP8 feature, then yeah you would have to compile your app for 8.

9ErDV.png

And if a new version comes out, you can easily update your app by changing that target OS to the later one and Visual Studio will automatically take care of adding in the new APIs and such. A good example of this is how people updated their apps from 7.0 to 7.1 (aka 7.5 mango), you just select 7.1, let visual studio do its thing and then your app supports the new features in Mango. Depending on your app you might have to do a tiny bit of extra work just to customize the background caching to your liking (live tiles or w/e) but you don't have to recode the entire thing from scratch.

Microsoft isn't calling Windows Phone 7 Windows phone 8, its calling them 7.8.

No you don't have to.

If you aren't targeting WP8 features, you compile your app for 7.8 (when it comes time to compile there's a dropdown box with the options 7.0, 7.1, Tango, 7.8, 8) and then it will work on both WP7 and 8. If you need to target a specific WP8 feature, then yeah you would have to compile your app for 8.

Microsoft isn't calling Windows Phone 7 Windows phone 8, its calling them 7.8.

Actually, that's precisely what I said. I was replying to a post that said MS should call WP7 as WP8.

This is quite frankly the stupidest idea I've heard, and what's surprising is that it even gets repeated so often. Version numbers are there for a reason. When developers see a version number, they know that they can expect a standardized kernel, APIs, and software stack across the board (even if hardware specs might differ across devices). The version number isn't there to appease end users, it's a traditionally important piece of information for developers. The reason that Apple can call iOS 6 for the 3GS as iOS6 is that, even though it lacks Siri, it still shares the same APIs and stacks as iOS 6 on the iPhone 4S and 5, and if any incompatibilities do arise it's going to be due to hardware, not software. Microsoft calling WP7.8 as WP8 when it in fact uses a completely different kernel and APIs is just going to royally **** developers off. It means that they can't effectively target their code for WP8 anymore. It means that you have to write your app twice for the "same" platform, it means that when users report bugs and say they're running WP8 you're going to have to ask them if they're running the real WP8 or the fake one, it means that the SDK and the development process is basically going to be a pile of crap.

WP 8 isn't a version number in any case, which is the important thing you fail to realize. Windows 7 is also not version number 7 (though that's for technical reasons). So they could call it WP8 as much as they want, and it would still be version number 7.8

WP 8 isn't a version number in any case, which is the important thing you fail to realize. Windows 7 is also not version number 7 (though that's for technical reasons). So they could call it WP8 as much as they want, and it would still be version number 7.8

Okay. So it'd actually be WP7.8 8. Or WP8 7.8. Or we'd have a WP8 that can't, er, run WP8 apps. Uh huh.

Have you considered the possibility that Microsoft is simply smarter than you are, and realized the obvious that trying to pull a fast one and package WP7 as WP8 is simply going to drain their credibility, both among developers AND consumers, EVEN faster than if they'd just announced that their 3-month-old flagship phone isn't really getting WP8 and be done with it?

Why are people just fixated on the low US number? Overall Nokia sold double the WP devices it did in Q1. It sold zero WP in Q1 in the US, afaik, and now they sold a few. Either case, Nokia has been selling more with each quarter since the start. MS has also said that sales have went up 50% Q/Q. So hmm, growing sales, broader carrier support for WP8 on the way (Verizon, US Cellular, probably Sprint once they get tired of getting raped by their ****ty iPhone deal). This things not over anytime soon.

Funny how people think Nokia would of been better with Android. Had Nokia decided to make Android phones instead, chances are they would of been sued off the market by now. Their current weakened state would of made them a prime target for patent infringement lawsuits (as they wouldn't be able to defend themselves). Plus MS would "bully" them into paying licensing fees to them anyway. Going with MS was their only choice and in the long term will be the best decision they ever made. This is coming from an Android fan as well. As much as I would love to see Nokia joining the fold, I honestly couldn't see them surviving long because of all the nonsense with patents going on right now.

^^ because US market is a huge market and this thread is about lumia sales in US.

Right, that's why you're fixated on it in the other nokia thread as well. Gotcha.

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

    • No registered users viewing this page.
  • Posts

    • Google Meet brings Gemini note-taking to AI Pro and Ultra subscribers by Karthik Mudaliar Google's Gemini-powered "Take notes for me" feature inside Google Meet is now available to Google AI Pro and Ultra subscribers. The features work on Google Meet for web as well as on mobile, and Google says that subscribers can use it for meetings they host in many supported languages. As the name suggests, "Take notes for me" allows Gemini to listen to a meeting, generate a summary, identify action items, and save the notes as a Google Doc in the user’s Drive. After the meeting, the organizer receives an email recap with the summary and action items, while the notes can also be attached to the related Calendar event depending on the meeting setup and sharing settings. The feature isn't automatically turned on for everyone, though. Google says that all meeting participants are notified when note-taking is turned on, and users can start it from the pencil icon in Meet or enable it for future calls through Meet’s meeting records settings. For work or school accounts, administrators can also control whether the feature is available and may require explicit participant consent for note-taking, recording, or transcription features. The feature first launched back in 2024, when it was available just for selected Workspace users. Over the years, Google added refinements and more options, including the ability to enable it when scheduling meetings via Google Calendar. Google's support docs say that the feature currently supports English, French, German, Italian, Japanese, Korean, Portuguese, and Spanish, but only one language at a time. Meetings with multiple spoken languages are not currently supported, and Google recommends using the tool for meetings between 15 minutes and eight hours. The new feature makes Google Meet closer to its rivals that have AI tools already built in. Microsoft Teams has recently started offering Copilot and intelligent recap features that summarize meetings, surface highlights, and help with follow-ups, while Zoom’s AI Companion can also generate meeting summaries from desktop and mobile meetings.
    • GnuCash 5.16 by Razvan Serea GnuCash is a personal and small business finance application, freely licensed under the GNU GPL and available for GNU/Linux, BSD, Solaris, Mac OS X and Microsoft Windows. It’s designed to be easy to use, yet powerful and flexible. GnuCash allows you to track your income and expenses, reconcile bank accounts, monitor stock portfolios and manage your small business finances. It is based on professional accounting principles to ensure balanced books and accurate reports. GnuCash can keep track of your personal finances in as much detail as you prefer. If you are just starting out, use GnuCash to keep track of your checkbook. You may then decide to track cash as well as credit card purchases to better determine where your money is being spent. When you start investing, you can use GnuCash to help monitor your portfolio. Buying a vehicle or a home? GnuCash will help you plan the investment and track loan payments. If your financial records span the globe, GnuCash provides all the multiple-currency support you need. Between 5.15 and 5.16, the following bugfixes were accomplished: Bug 421610 - RFE: Include logical dates for View->Filter by "date range"The Select Range section of the Date tab of the register's Filter By dialog box is changed to provide relative, specific date, or days ago options for the start and end of the filter range. The Show number of days item label is changed to Show from days ago to better reflect what it does. Bug 436105 - esc key not working as expected in register: Enable the escape key to cancel a field edit. Bug 797384 - Gnucash doesn't handle commodity prices with big numerator/denominator properly. Bug 798004 - Next gen UI for stock transactions Bug 799314 - Add "enter now" option in scheduled transaction editor. tab to allow users to select the scheduled transactions to be included in a “Since Last Run…” window. If there are no instances of a selected transaction triggered by today’s date, the next instance is triggered. Bug 799751 - autocomplete crash Bug 799759 - Users can't Enable entries via Checkboxes on Scheduled Transactions PageAllow the Enabled box in the list of scheduled transactions to be operated instead of having to open the transaction editor dialog and change the Enabled checkbox. Also added use of the Name column as the secondary column sort for all the other columns. Bug 799762 - Poor handling of cases where hidden/placeholder accounts are used in the account register Bug 799766 - Double line preference not respected in search register Bug 799767 - POST /accounts in bindings/python/example_scripts/rest-api is broken Bug 799777 - `xaccSplitSetParent`: reparenting a committed split silently drops its KVP slots (online_id, cap-gains links) Other changes & improvements: Numeric values may now be selected to copy in the Accounts page. Add new Finance::Quote source Finnhub.io: Free API key (personal/non-professional use) available at https://finnhub.io. Set FINNHUB_API_KEY environment variable to API key to use this source. As of June 2026, free tier API limit is 60 API calls/minute. The Investment Lots report has new optional columns for Computed Annual Growth Rate. Python Bindings: Improved translation of primary object (Account, Transaction, Split, etc.) so that they can be treated as normal Python objects. This is accomplished with SWIG magic so no existing code is obsoleted. Python Bindings: Better conversion of GLists to Python lists. Python Bindings: Destroy the QofSession in the Python Session dtor to prevent leaving the database locked. [engine] Add first-class online_id accessors for Split and Account and make them available to Python bindings, removing the unused Transaction online_id property. Improve C++ implementation of QofBook. Correct the Doxygen doc for qof_instance_get/set_kvp. [gnc-log-replay.cpp] fix incorrect guid dump Add some Boost library requirements needed by libgnucash-guile to CMakeLists.txt so that missing feature will fail at configure time. Use Compile-time Regular Expressions instead of std::regex in gnc-filepath-utils.cpp and instead of boost::regex in the CSV importer, with the CTRE v3.11.1 header added to borrowed [gnc-filepath-utils.cpp] null check char* arguments Add ChartJS licenses. Removed AEX from list of commodities. euronext.com is now using JS based anti-webscraping. [report-core] always offer options summary in reports. This is useful to debug reports. The Add options summary option is removed because it's no longer optional. Remove remaining obsolete IMContext from sheet Fix blurry text in HiDPI offscreen-rendered widgets Add port field to database connection dialog: The convention of appending the port number after the host isn't obvious. When editing a split in the register treat the account as being changed only if it isn't the one selected before editing instead of if the user performed an edit Return immediately from qof_book_destroy if hash_of_collections is null. If qof_book_destroy is called on a QofBook* freshly created with qof_book_new (usually because it was used to create a session that now must be destroyed) it would try to empty the non-existent hash tables, crashing. Clean up Flathub metadata to solve warnings at flatpak build time. Be consistent in naming GncPluginPage and GncPluginPageRegister HTML: Remove unimplemented function declarations. [gnc-html.cpp] remove unused buggy string conversion functions Convert libgnc-html to C++ Apply -Wall -Werr -Wmissing-prototypes to C++ compilation on Windows and fix the resulting errors. New and Updated Translations: Arabic, Croatian, Danish, Dutch, German, Finnish, Hungarian, Korean, Norwegian-Bokmal, Spanish Download: GnuCash 5.16 | 176.0 MB (Open Source) Links: GnuCash Home page | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally launches WSL Containers in public preview by David Uzondu Microsoft has announced that WSL containers, a feature that allows developers to run Linux containers natively inside Windows without the need for Docker Desktop, is now available in public preview several weeks after Microsoft previewed it at Build 2026. To use the new container feature, you first have to install the latest pre-release version of the Windows Subsystem for Linux by running a quick update command in your terminal: wsl --update --pre-release After installing, you'd get access to the new Linux container CLI (wslc.exe) and the programmable API. Microsoft said that the CLI has a "familiar format" that matches the toolsets developers already use every day. If you know standard Docker commands, your muscle memory will translate directly to wslc.exe, which even features a built-in alias called container.exe. You can quickly run a full Ubuntu KDE desktop container by exposing ports, or pass your graphics card straight into a machine learning environment to run PyTorch workloads. Passing the --gpus all flag inside the run command instantly links your hardware. Image via Microsoft As for the API, developers can now embed Linux container operations directly inside native Windows applications without exposing the command line to users. The team integrated the API directly into MSBuild and CMake, so developers can define container steps directly in project files. Apart from bringing the CLI and API into public preview, Microsoft also said that it's working on a new default file system called virtiofs to speed up file transfer rates between Windows and Linux. Microsoft also introduced an experimental networking mode named consomme, which resolves compatibility issues with corporate VPNs by routing Linux network traffic straight through Windows. One thing to note about WSL containers is that they don't run in your standard WSL distributions; instead, every application and CLI session spawns its own lightweight Hyper-V utility VM in the background. This basically reduces the chances of one app snooping on the container of another app.
    • Google reportedly limited Meta's Gemini access over limited AI compute by Karthik Mudaliar Google is reportedly limiting Meta's use of its Gemini AI models after Meta tried buying more computing capacity than even Google could supply. According to the Financial Times, Google told Meta in March that it could not provide the full Gemini capacity that Meta had requested. This shortfall even disrupted and delayed some of Meta's internal projects. Due to this, Meta even told its employees internally to use AI tokens more efficiently. Meta wasn't the only one to get hit by this sudden refusal by Google; even other customers were affected. But Meta was hit harder because of its unusually high demand for Google's models. The move from Google makes it evident that companies all over are in limited supply of both infrastructure and compute. Alphabet said in April that Google Cloud revenue grew 63% year-over-year to $20 billion in the first quarter, helped by enterprise AI infrastructure and AI solutions. In pursuit of more compute, Meta had earlier signed a multi-billion-dollar AWS agreement as well as a large AMD GPU deal for AI data centers. But the crunch would be short-lived as both Meta and Google have also ramped up infrastructure investments heavily. Meta said in November that it was committing more than $600 billion in the U.S. by 2028 for AI technology, infrastructure, and workforce expansion. In the first quarter of this year, Meta also raised its expected capital expenditure for 2026 to a range of $125 billion to $145 billion, citing higher component pricing and additional data center costs for future capacity. However, this doesn't make the company immune to the current dependence on outside suppliers. Meta has also spent many years promoting Llama as an open-weight alternative to closed models from Google, OpenAI, and Anthropic. But if the reported reliance on Google's Gemini models is severe enough for internal work to get impacted, then it looks like even frontier labs and Big Tech aren't fully self-sufficient. Source: Financial Times
    • I like to reminisce about the good old days, way back in autumn 2025 when building a gaming machine was fun and the drives were about $150 when you caught a deal. Yes duh, back in the day we had it gone. Then baby Skynet came along, hiding in AI datacenters demanding more processing power until it reached singularity. End of a not totally fictional story.
  • Recent Achievements

    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      533
    2. 2
      +Edouard
      269
    3. 3
      PsYcHoKiLLa
      150
    4. 4
      Steven P.
      98
    5. 5
      macoman
      66
  • Tell a friend

    Love Neowin? Tell a friend!