Recommended Posts

It's clear from recent articles about Microsoft depleting stock of Lumia branded phones and making little or no effort to restock them, the writings on the wall and Lumias are being gradually phased out. Microsoft might introduce Surface branded phones at some point in the future, but that's strictly speculation right now.

 

The question is, for anyone that currently owns a Microsoft Lumia device running Windows 10 Mobile, or even for anyone that might be considering buying one while stocks last as perhaps a secondary phone, what is the likelyhood Microsoft could eventually discontinue OS update support for these devices, leaving Lumia owners in the lurch with increasingly insecure devices, and little or no option but to eventually, maybe reluctantly, switch to a phone running Android or iOS ... ?

 

  • Like 1
Link to comment
https://www.neowin.net/forum/topic/1319042-the-unsafe-future-of-lumia-devices/
Share on other sites

If you get a Windows phone now, you are able to upgrade to the latest version of Windows 10 on it. And you are able to upgrade anytime as soon as the new version comes out.

 

It's up to you to use it as primary or secondary.

 

If you are not sure, then you can get either iOS or Android phone so you wouldn't worry about future since they are releasing updates.   

 

But if you get an Android phone from cellular provider then you may not get update right away ... they will release as soon as they are ready to release..   Google releases updates to the unlocked devices right way, Nexus for example.

12 minutes ago, DJGM said:

what is the likelyhood Microsoft could eventually discontinue OS update support for these devices

I would think pretty slim in the short term given it would further dwindle Microsoft's almost non existent market share. If they do yank official support users could possibly still get updated through the insider program. Pretty sure I still get latest updates on my 930 and it's over 2.5 years old.

In a year, Windows Mobile will most likely change yet again to support x86 apps, or a full blown version of Windows 10. So when that happens it will be Windows Phone 7 all over again, and not to mention Windows Phone 8/8.1 phones that aren't able to upgrade to Windows 10 Mobile. Unless Microsoft keeps two branches of Windows 10 Mobile for older phones, and the newer version for the newer chips (Snapdragon 835 supports full Windows on mobile devices) people are going to be left behind yet again.

 

Lets have a look at what Microsoft has done with Mobile.

 

- Windows Mobile up to 6.5

- Windows Phone 7 (any phone released prior to WP7 couldn't upgrade to it)

- Windows Phone 8 ( no WP7 devices could upgrade to this, as well as the recently released Lumia 900, it was only a few months old)

- Windows 10 Mobile - Microsoft promised that all WP8 devices could upgrade to this, but there are quite a few that got left out and can't upgrade

- Windows 10 Mobile/Desktop (2017-18?) Nothing under a Snapdragon 835 will support this.

 

I got onboard with the HTC 8X and Windows Phone 8 because at the time it seemed like Microsoft had finally got their act together, but just knowing what I know now, they aren't any closer today than when they announced Windows Phone 7 in 2010!

  • Like 1
This topic is now closed to further replies.
  • Posts

    • Hi all. I have a seven year old Acer laptop which according to Acer website can't receive the new MS updates. This device lives in my bedroom and is purely a consumption device. No gaming, no nothing. I have followed online instructions and turned off secure boot which now gives me a green tick in W11 Security. Now, I have MWB Premium now for several years and I'm reasonably careful with my online activity with this laptop. I'm also not a gamer in any way so I'm not asking much from this laptop. Given that, am I safe to continue using this device given I've turned off secure boot? That's it, that's my question.
    • finally [Taskbar] Taskbar customization just got easier. As we continue to make improvements to the Taskbar experience mentioned last month, we've introduced a dedicated Taskbar Size setting, making it simpler to find, understand, and personalize your ideal taskbar experience.
    • Let me get this straight... It was a web interface for Gmail, so if privacy at Google wasn't concerning enough you'd be going through two companies. And their big feature was the very thing that would make people consider dumping Gmail.
    • Microsoft's fast coding model MAI-Code-1-Flash comes to Copilot Business and Enterprise by Karthik Mudaliar Microsoft’s recently announced MAI-Code-1-Flash model is now generally available to GitHub Copilot Business and Copilot Enterprise customers. With this support, organizations can have more centralized policy controls and billing while finally being able to use Microsoft’s lightweight, first-party coding model. According to GitHub’s announcement, Business and Enterprise plan administrators must enable the MAI-Code-1-Flash policy in Copilot settings before developers can access the model. Microsoft says that MAI-Code-1-Flash is for fast, iterative coding work rather than the most demanding architectural or debugging tasks. GitHub’s official model comparison page says that the model is great for "general-purpose coding and writing," while it excels at fast, accurate code completions and explanations Microsoft introduced MAI-Code-1-Flash on June 2 as part of a broader collection of internally developed MAI models. GitHub subsequently expanded support to Copilot CLI, the Copilot cloud agent, GitHub.com chat, GitHub Mobile, Visual Studio, JetBrains IDEs, Eclipse, and Xcode, but said support for managed Business and Enterprise customers was still on the way. In Microsoft’s own benchmark testing, MAI-Code-1-Flash scored 51.2% on SWE-Bench Pro, compared with 35.2% for Anthropic’s Claude Haiku 4.5. Microsoft also claimed that the model used up to 60% fewer tokens on SWE-Bench Verified. Do note that these are vendor-run results rather than independent measurements. The model is billed at provider list pricing under GitHub’s usage-based system. GitHub currently lists MAI-Code-1-Flash at $0.75 per million input tokens, $0.075 per million cached input tokens, and $4.50 per million output tokens. For organizations, the main incentive to use MAI-Code-1-Flash is likely to be efficiency rather than maximum capability. A smaller model that responds quickly and limits unnecessary output is quite useful for repetitive agent tasks at scale, especially after GitHub Copilot’s move toward usage-based billing. The "Flash" model is recommended for fast work and not necessarily for huge repositories with loads of context. It's better if teams compare their output with other larger models, especially if they're working on security-sensitive changes and complex, multi-file work.
  • Recent Achievements

    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
    • First Post
      OffsetAbs earned a badge
      First Post
    • Reacting Well
      OffsetAbs earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      462
    2. 2
      +Edouard
      213
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      73
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!