09-16-2013, 04:54 PM #1
- 82 Posts
There's several threads in a lot of different locations, so rather than try to post to all of them, I thought it would be easier to post a new thread.
Right now over on the Windows Phone User Voice feedback site, there's 20 times more votes for what the name for a yet-to-be-released "personal assistant" should be named than there are votes for Microsoft to push updates direct to the phones, bypassing carriers.
Personally, to each their own, but I think that's a bit messed up. Especially when you consider how many people aren't happy about the whole update situation.
Now, I know, there's some people that are going to say "just flash the ROM and be done with it", "get an unlocked phone", "the process is more complicated than that" or whatever. That's fine, if you want to think that way, go ahead, but I don't think that either one of those should be necessary for my phone to be up to date with software. Maybe it means Microsoft has to restructure the deals they have with the carriers. I don't know, but I think it's important for Microsoft to know that we're not happy with the way things are and they need to do something to change it.
Here's the highest-voted post on the topic: Own the update process
Let's keep it going, get it to the top of the list, get it noticed, get some attention from Microsoft.
But, if it's more important for you to be able to call your phone some strange name, that's fine, just don't be upset when you never get the update that lets you use the assistant in the first place.
09-16-2013, 05:17 PM #2
- 981 Posts
"Carriers should not be allowed to arbitrarily block updates"
So peeps think that this is just an arbitrary decision ? That's not believable even if you don't like the process.
Re : T Mobile board meeting in hell " are we going to update 810 owners to GDR3 ? spin the wheel and lets see "
09-17-2013, 08:17 AM #3
- 82 Posts
Just giving this a bump in order to keep it alive. Even if you're not a fan of the exact wording, but you're still not happy with the update process, throw in a few votes.
I would hate to see something that aggravates so many people become less important than what phone which celebrity is using.
But, that's just me...
09-17-2013, 08:23 AM #4
- 934 Posts
Look, if Netgear wants to update my router firmware they do not have to get my phone company to OK it first. It is no different for mobile phone companies. It's just that they like to block things like Datasense for as long as they can to increase their revenue. The trouble is that the phone companies often run the phone shops for mobiles, but don't have the same monopoly in the land line world. So manufacturers need to keep them sweet to get sales. The best way to protest is to never by from a company store. Go down the supermarket instead. It won't solve your problem, but will discourage the practice in general.
09-17-2013, 09:04 AM #6
- 2,777 Posts
Just playing devils advocate here. I have an unbranded 8X and received GDR2 about a week before my carrier O2 rolled it out. I have had nothing but issues since the update and the subsequent firmware update and the list of problems is getting worse and increasing by the day.
If carriers block or hold an update there may well be legitimate reasons behind it rather than the carriers just being obstructive.
09-17-2013, 09:11 AM #7
- 70 Posts
To me it is an easy fix.
When MSFT make an update available to the carriers they need to set a firm deadline for it to be tested and approved so that the update can be released world wide to all customers on all carriers at the same time or within a deployment of two weeks i.e. Like apple do with iOS updates
If for some reason the carriers can't meet that deadline MSFT would them still make the update available to all handsets at the same time however they would display a disclaimer before the update is installed, advising the user that it is a generic update which has not been approved by the customers specific carrier and therefore they cannot guarantee the performance of the handset. Then give the end user the option to either continue and install the update or wait until the carrier approved update is available.
This way MSFT would keep the customers happy with a consistent update process and the carriers will still have the ability to test the updates before they are deployed, in turn it will hopefully motivate them to have their testing completed before the deadline.
- 09-17-2013, 09:14 AM #8
- 09-17-2013, 09:25 AM #9
It is just part of deal that carriers need to spend time doing acceptance testing on any updates on the phones that are branded by them. It is to ensure that these updates, no matter how small it is, (1) won't mess up their network (2) won't increase support calls or device exchanges. None of that is to test for your benefits.
09-17-2013, 10:24 AM #10
- 995 Posts
Microsoft have no power over the carriers. Microsoft will be begging them to take/support their phones. If Microsoft do this, just watch, the carriers will just drop WP. It doesn't sell like an iOS or Samsung device, so why care?
Nokia have already shown the solution. Rip as much as possible out of the OS, and make it into "apps", which can then be updated quickly and easily, without any sort of carrier control. That way the carriers only have a basic husk of a phone to test, so its an easy quick job for them.
- 09-17-2013, 10:31 AM #11
Disagree with this completely. I do not want to receive an update and then find something seriously wrong due to the carrier changing something that MSFT either doesn't know about or didn't antisipate. If a carrier is delaying an update I'm sure there is good reason for it.
- 09-17-2013, 10:39 AM #12
If you want the carriers out of your update path, buy an unlocked, unbranded device. Or get an iPhone.
Apple is still the only company with the chops to dictate update terms to carriers.
09-17-2013, 11:44 AM #14
- 189 Posts
MS seems to be going backwards instead of forward. Instead of trying to have every feature all the others do, stay with what sets you apart (Live Tiles) and make it work, flawlessly. Build on what you have, make it stable, reliable, awesome, THEN add features once per year through Windows Update, or the replacement to Zune Software, aka, Xbox.
- 09-17-2013, 12:08 PM #15
I know nothing about the logistics behind updates, but I'm not sure it's possible to totally bypass the carriers on carrier locked phones. I've heard that Apple's updates go to the carrier, but Apple gives them a strict timeline of when to have it ready to go. So it's not like Apple skips the carriers completely, just that they carry a big stick.
- 09-17-2013, 12:56 PM #16
iOS updates are given to the carriers, but it's nothing more than a courtesy because the carriers can't stop the update if something is wrong.
There have been a number of network connectivity issues with the iPhone on Verizon. VZW has raised objections to the update release schedule, and Apple releases the update anyway.
Apple gas total, absolute control over the iPhone. As many devices as Samsung sells, they have zero control over update schedules.
Sent from my Galaxy Nexus using Tapatalk 4
09-17-2013, 01:36 PM #17
- 488 Posts
- 09-18-2013, 07:37 AM #20
09-18-2013, 08:01 AM #22
- 10 Posts
I live in Japan. Still no Windows Phone 8 here. I bought an HTX 8X from Expansys. Just got it fully operational. Last night when I bought it, it did 4 updates! Now I am on GDR2. No. Problems. I think MS needs to allow their phones to be updated via wifi or via there PC app. It would make things on parity with Apple.
- 09-18-2013, 12:03 PM #25
As much as we might want this, AT&T will do whatever it wants up to and including holding up new devices and support. Does anyone know if there is an agreement between MS and AT&T that updates MUST pass through them?
- By bruceabbott2 in forum General Tablet & Laptop DiscussionReplies: 18Last Post: 09-20-2013, 02:53 AM
- By mlcooper54 in forum Nokia Lumia 822Replies: 3Last Post: 09-18-2013, 12:20 AM
- By user4545 in forum Samsung ATIV SReplies: 1Last Post: 09-16-2013, 05:29 PM
- By andrenunes1 in forum App SpotlightReplies: 1Last Post: 09-16-2013, 02:27 PM