Paul says no WP8 update for current phones


Recommended Posts

xeleraph

But Microsoft aren't refusing to make a commitment, they're just not saying anything. People like patseguin are just panicking because of rumours in the blogosphere. I've probably seen just as many rumours suggesting that current phones will get an upgrade as those suggesting that phones won't get an upgrade so it doesn't seem sensible to make decisions based on anything but an official announcement.

Uh, not saying anything is refusing to make a commitment.

Microsoft has already been asked repeatedly about this issue and they've refused to say anything, not even to quash unfavorable rumors when WP is in bad need of all the positive press it can get. That's more than enough legitimate reason for anyone who cares about upgrade paths to panic.

  • Like 1
Link to post
Share on other sites
Muhammad Farrukh

Hard to believe the Windows Phones just released would have such a short life if we follow this news... HTC Titan II , Lumias and all other WP phones!

PS if they were testing WP8 on Lumia 610 , i doubt higher end phones can't run WP8.

They'll get it. Dont worry.

At least I hope :s

Uh, not saying anything is refusing to make a commitment.

Microsoft has already been asked repeatedly about this issue and they've refused to say anything. There's more than enough legitimate reason to panic.

Not until we get the word, no

Link to post
Share on other sites
xeleraph

Not until we get the word, no

Not for you, maybe. But for everyone else who doesn't have irrational emotional investments in WP and are subscribing to nothing more than wishful thinking, yes.

Like I said, why take the risk?

Link to post
Share on other sites
patseguin

But Microsoft aren't refusing to make a commitment, they're just not saying anything. People like patseguin are just panicking because of rumours in the blogosphere. I've probably seen just as many rumours suggesting that current phones will get an upgrade as those suggesting that phones won't get an upgrade so it doesn't seem sensible to make decisions based on anything but an official announcement.

You're 100% right. I wonder why MS won"t make an official statement and ensure the success of their platform. Could it be because the news is not good?

Link to post
Share on other sites
Muhammad Farrukh

Not for you, maybe. But for everyone else who doesn't have irrational emotional investments in WP and are subscribing to nothing more than wishful thinking, yes.

Like I said, why take the risk?

In my opinion, there is no risk. At all.

Microsoft knows Windows Phone is not doing great. Its like shooting oneself in the foot. Which is unlikely. At least to me.

I don't think Microsoft is that stupid

Link to post
Share on other sites
xeleraph

In my opinion, there is no risk. At all.

That's your opinion.

Microsoft knows Windows Phone is not doing great. Its like shooting oneself in the foot. Which is unlikely. At least to me.

I don't think Microsoft is that stupid

The fact that WP isn't doing great is exactly why Microsoft would want to shut off upgrade paths. Which of the two would most likely lead to increase in market share: prioritize existing customers and alienate carriers, or just screw over the 1.9% of users who bought WP and suck up to the carriers by pandering to their customization and lock-in demands so WP can be marketed to the wider masses like Android did so successfully?

Link to post
Share on other sites
Muhammad Farrukh

like Android did so successfully?

Conversely, we have iPhones :p

Link to post
Share on other sites
xeleraph

Conversely, we have iPhones :p

iPhones are different. Carriers will never want to let anyone else do to them what Apple did, ever. Apple got away with it because carriers didn't foresee what would happen to them in the long term if they submitted themselves to Apple's thumb, which is why Microsoft isn't likely to foist the same conditions on carriers successfully.

Link to post
Share on other sites
simplezz

There is no official word on it, that the devices won't get Apollo update.

They, most likely, will.

You just contradicted yourself. If there is no official word, how do you know it's "most likely"? Microsoft's silence is deafening regarding this issue.

Link to post
Share on other sites
jakem1

You're 100% right. I wonder why MS won"t make an official statement and ensure the success of their platform. Could it be because the news is not good?

As I said previously, I suspect that they're still working with partners to work out how the upgrade will work and who will receive it. If that's the case then they're just not making an official statement because they don't have any news to report, not because they're trying to trick people into buying phones that won't receive an upgrade.

I think you should sit tight and continue to enjoy your phone. As others have said, both Nokia and Microsoft have too much to lose to not offer upgrades.

Link to post
Share on other sites
simplezz

Actually, thinking about it now, it makes perfect sense. Windows Phone 6.x didn't get an upgrade to 7, and 7.x won't get an upgrade to 8. So if the pattern holds, 8.x won't get an upgrade to 9.

Link to post
Share on other sites
.Neo

That's your opinion.

Do you always repeat things that have just been said?

  • Like 1
Link to post
Share on other sites
xeleraph

Do you always repeat things that have just been said?

When emphasis is needed, yes. I assume you have some sort of point you're trying to make, but I can't quite figure out what it is, can you help us out here?

Link to post
Share on other sites
Stoffel

When emphasis is needed, yes. I assume you have some sort of point you're trying to make, but I can't quite figure out what it is, can you help us out here?

somebody started with the following: In my opinion......

That's when you replied, That's your opinion.

It's kinda stating the obvious no?

Link to post
Share on other sites
xeleraph

somebody started with the following: In my opinion......

That's when you replied, That's your opinion.

It's kinda stating the obvious no?

You mean like what you're doing?

Link to post
Share on other sites
downhillrider

im starting to think that MS will say sorry gen 1/2 users. if you want apollo buy a new phone. they have the money to absorb any potential financial hit. lets be honest, the windowsphone base is so small it might not matter.

Link to post
Share on other sites
BajiRav

I think it's going to be pretty simple. First gen phones i.e. those that came with Windows Phone 7.0 will not receive update. The second gen. phones such as Samsung Focus * and Lumias except for the low end devices will receive WP8. Much like what Apple did initially (and still does from usability perspective i.e. iPhone 3G received iOS 4.0 but it was next to useless).

Link to post
Share on other sites
Muhammad Farrukh

In my opinion, all of the current ones will get Apollo

Link to post
Share on other sites
MorganX

If the Lumia's do not get WP8, this will be disastrous for the platform. And I'm a huge fan of it. Terrible.

Link to post
Share on other sites
MorganX

If this is true, all Apple needs to do is release a 4.3" screen iPhone and its game over.

Link to post
Share on other sites
.Neo

When emphasis is needed, yes. I assume you have some sort of point you're trying to make, but I can't quite figure out what it is, can you help us out here?

I take it by "us" you mean yourself. Muhammad Farrukh was christal clear about stating his own personal opinion regarding the matter. Your post added absolutely nothing to that.

Link to post
Share on other sites
Muhammad Farrukh

If this is true, all Apple needs to do is release a 4.3" screen iPhone and its game over.

*In House' voice* Hmmmm...

While the only thing 'missing' in the iPhone, to me at least, is the big screen, I doubt Apple will completely dump 3.5' and go straight to 4.3''

There is a decent amount of market that doesn't care about the screen sizem and doesn't need a big one.

If we can get it in two flavours, 3.5'' and +4.0'', it will boast the sales pretty high, since a lot of people, like me, are resistant to the iPhones just because of the screen size

Link to post
Share on other sites
Aethec

Thurrott says WP8 requires multi-core processors. That would be an insane marketing decision since Android would get all the "cheap" phones you get for free with small contracts.

Besides, we know Windows "8" (actually, a modified Win7 build) can run (or, at least, display the task manager and the Solitaire game) on an old ASUS developer device (see the B8 post on WOA).

I think (just a guess) that the reason MS is silent is that it's not performant enough on really low-end phones for now, and they don't want to promise anything. If they say WP8 will be on all phones and for some reason it isn't, there'll be a backslash. If they say "high-end phones will get an update", people will understand "low-end phones won't" and there will be a backslash. :/

Link to post
Share on other sites
MorganX

*In House' voice* Hmmmm...

While the only thing 'missing' in the iPhone, to me at least, is the big screen, I doubt Apple will completely dump 3.5' and go straight to 4.3''

There is a decent amount of market that doesn't care about the screen sizem and doesn't need a big one.

If we can get it in two flavours, 3.5'' and +4.0'', it will boast the sales pretty high, since a lot of people, like me, are resistant to the iPhones just because of the screen size

It didn't bother me until I went Titan, and now Lumia. I just don't think I can go back, I still have my iP4, but I squint at it now. But if there's no WP8 update for the Lumia, I just can't support this move by MS. This on top of failure to produce a complete bluetooth stack and remaining silent about when/if they'll fix it. Several app and accessory developers I've contact have no plans to support Windows Phone in their roadmap. Some because of the lack of bluetooth they can't, others are firmly in iOS camp.

I have a bad feeling Microsoft is going to blow it ... AGAIN!

  • Like 1
Link to post
Share on other sites
efjay

II have a bad feeling Microsoft is going to blow it ... AGAIN!

They've already begun with Skype not being available on low cost Tango phones. Min req is 512MB which immediately denies users of those devices a pretty big feature. But who wants to bet Tango will probably get thier app working with the restriction of no background tasks? MS WILL blow it again. Bank on it.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Usama Jawad96
      Twitter updates its policies to prohibit racism
      by Usama Jawad

      Back in July 2019, Twitter updated its platform guidelines to prohibit hate speech against religious groups. Then in March 2020, it once again expanded them to include hateful conduct that dehumanizes people based on age, disability, or disease. Today, the company is banning hate speech that dehumanizes based on race, ethnicity, and national origin.



      In a blog post, Twitter has indicated that hate speech based on race, ethnicity, and national origin will be promptly removed from the platform as soon as it is reported. The company will also be using its automated processes to detect and remove content it deems hateful. Repeat offenders who violate this guideline may get their accounts temporarily suspended as well. The firm has posted the following examples of Tweets that it characterizes as hateful conduct based on the expanded policies:

      All [national origin] are cockroaches who live off of welfare benefits and need to be taken away. People who are [race] are leeches and only good for one thing. [Ethnicity] are mail-order bride scum. There are too many [national origin/race/ethnicity] maggots in our country and they need to leave. Twitter is also working with third-parties to better understand how it can combat this problem. It says that dehumanizing behavior can lead to real-world violence as well, and as such, the ultimate goal is to keep people safe from hateful behavior globally - both online and offline.

    • By Jefferson Mangubat
      Microsoft Outlook for iPadOS now lets you drag and drop files in split view
      by Jefferson Mangubat

      Microsoft has released a new update for its Outlook app on iPadOS that should improve multitasking on the email app. The latest change adds support for drag and drop in split view, among others.

      With the new update, you can now attach files and images by dragging and dropping them from OneDrive, Files, Photos, Safari, and Outlook email attachments when you use apps side-by-side on an iPad. The drag and drop capability, in particular, is not something new with Outlook for iPadOS as Microsoft announced support for this feature for the app's composer last month. Split view was also introduced to Outlook for iPadOS earlier this year.

      In addition, the app now lets you drag and drop contacts from Search to its recipients list. Here's the full changelog on the App Store:

      The update brings the app's version number to 4.60.0 and is now available to download on the App Store.

    • By indospot
      Patch Tuesday: Here's what's new for Windows 8.1 and 7 this month
      by João Carrasqueira



      We're 13 days into October, but it's not truly a new month until Microsoft releases its Patch Tuesday updates for Windows, and as we're on the second Tuesday of the month, that happens today. Along with all supported versions of Windows 10, there are also new cumulative updates rolling out to Windows 8.1 and some Windows 7 users.

      There are two kinds of updates for each operating system - the monthly rollup update and the security-only update. For Windows 8.1, the monthly rollup update is KB4580347 and you can download it manually here. It includes the following changes:

      It also has a couple of known issues:

      Symptom Workaround Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Do one of the following:

      Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.

      When installing a third-party driver, you might receive the error, “Windows can’t verify the publisher of this driver software”. You may also see the error “No signature was present in the subject” when attempting to view the signature properties using Windows Explorer. This issue occurs when an improperly formatted catalog file is identified during validation by Windows. Starting with this release, Windows will require the validity of DER encoded PKCS#7 content in catalog files. Catalogs files must be signed per section 11.6 of describing DER-encoding for SET OF members in X.690.

      If this happens, you should contact the driver vendor or device manufacturer (OEM) and ask them for an updated driver to correct the issue.

      As for the security-only update, it's KB4580358 and you can download it manually here. It only includes the first and last of the bullet points from the monthly rollup. It also has the same known issues as the monthly rollup.

      Of course, for Windows 7, only certain businesses can legitimately obtain the updates, since you need to be paying for extended security updates (ESU) after Microsoft dropped extended support for the operating system at the start of the year. The monthly rollup here is KB4580345, and you can download it manually here. It includes the following changes:

      The update has one known issue:

      Symptom Workaround Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Do one of the following:

      Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.

      The security-only update here is KB4580387 and you can get it manually here. It includes the same changes as the monthly rollup, except the third and fourth bullet points. It also has the same known issue.

      As usual, the monthly rollup updates should install automatically sooner or later, but if you want the security-only updates, you'll need to install them manually from the links above.

    • By Usman Khan Lodhi
      Google Maps for Android widely rolling out revamped search field
      by Usman Khan Lodhi



      Google Maps received a major update earlier this year on the occasion of its 15th birthday. Like other Google-developed apps, its design is always being revamped, and Google Maps for Android now features a pill-shaped search field.

      For a while now, the search field at the top of the app had been a rectangle with rounded corners, but February's bar-focused update removed the hamburger menu for the navigation drawer. The tweaked search bar, which is shaped like a pill, features the four-color pin at the left, a "Try gas stations, ATMs" hint, and a microphone icon. The rounded profile avatar has also been fitted in at the edge.

      The pill, present in the full search interface, fits with similarly-shaped buttons and rounded sheets throughout the current user interface.

      The pill-shaped search field first rolled out to iOS users and appeared on and off for some Android users in recent weeks. Now, it appears that the update is widely rolling out on the stable and beta channels. Hopefully, maps.google.com will also get updated soon.

      Source: 9to5Google

    • By Usama Jawad96
      Microsoft apparently just fixed a Windows security flaw first reported to it in 2018
      by Usama Jawad

      Microsoft fixed quite a number of bugs in this month's Patch Tuesday update, which came out last week. While it packed numerous fixes for various versions of Windows, it did draw some criticism for the handling of a security vulnerability that was reported to it by Google.

      However, it appears that the Redmond giant's security woes are not yet over as a new report claims that the firm just fixed a Windows zero-day exploit that was reported to it back in 2018.



      Last week, Microsoft fixed a security hole in various versions of Windows that mainly deals with the operating system's incorrect handling of file signatures. In CVE-2020-1464, the company noted that:

      In a blog post on Medium, security researcher Tal Be'ery has explained that Bernardo Quintero, a manager at VirusTotal - a service owned by Google - first discovered the vulnerability being exploited back in August 2018. This exploit, internally called "GlueBall", was immediately reported to Microsoft and the findings were published in January 2019 by Quintero. Microsoft acknowledged the issue and added mitigation actions in supporting tools, but stated that it would not fix the issue in the operating system itself. The reasoning behind this decision is not public.

      After this, several blog posts were published by other people, explaining how to use GlueBall to exploit Windows. Then in June 2020, GlueBall was once again highlighted by prominent social media accounts.

      It would seem that roughly around this time, Microsoft began to take this issue seriously and a proper fix to the gaping security hole was finally released in this month's Patch Tuesday. According to Microsoft's security advisory, this flaw was present in Windows 7, 8, 8.1, RT 8.1, Server 2008, 2012, 2016, 2019, and Windows 10, going all the way up to version 2004, and that it was exploited across numerous versions of the operating system.

      In a vague statement to KrebsonSecurity, Microsoft stated that:

      The handling of this incident from Microsoft's end is extremely strange, to say the least. One has to wonder why Microsoft delayed fixing a Windows security flaw for nearly two years, especially when it was present in virtually all major versions of the operating system.

      Source: Tal Be'ery (Medium) via KrebsonSecurity