This thread's discussion is locked. If it doesn't give you the information you need, head to its forum board for active discussions or to start a new discussion.
What's the point of this page if the dates displayed are meaningless. Earlier today the note 5 showed due to receive marshmallow today. Now it's been pushed back once again to the 25th. Might as well put coming soon to all of them.
This is ridiculous. I bought a Nexus 6 cause it gets updated quickly. Then a warranty issue pops up and I'm sent the Note 5. It's a nice phone but cripes I had a Nexus cause I liked the updates and now you guys can't get your act together. It's total bs. How the heck do you delay the release again on the day it's set to roll out and you wait till 5pm to announce that. Get your freakin act together!
We know you're eagerly awaiting this update and definitely hear you.
While we try our best to ensure updates align as closely to the target date as possible, circumstances can sometimes arise that might see these dates being pushed back or delayed altogether.
We spoke to the product team about the current status and the good news is that the update is still happening - March 25th, tentative - while the bad is that it's been slightly pushed back from the original target.
If we receive any further news regarding this update, we'll share it with you here!
With all repect there needs to be a date set and stick to it with a working update. This is the fourth change of date for this Note 5. First the 9th, 13th, 16th and now MAYBE the 25th. This is frustrating. No one can say this update was fine yesterday and not working today. I don't believe it will happen the 25th at this point. I don't know if it a telus issue or a Samsung issue, but it seems someone doesn't have their act together and it reflects poorly on both.
I understand the circumstances arise that cause updates to be pushed back, but there is no reason for the amount of delays in this case. Going from March 9 to 13 to 16 to 25 is simply unacceptable. I would be perfectly fine with a later date, say if the 16th had been the first date announced. In that case the delay to the 25 would of been hard, but acceptable. How this has been handled with the update being pushed back in the middle of the day, and no explanation is unacceptable.
Rogers and Bell are in the same boat. No release date. Samsung is well known for delaying updates because of bugs. Rogers doesn't even have a scheduled release date listed for any Samsung device currently.
Maybe Telus should reset the date to coming soon. People like myself are frustrated because our expectations are being poorly managed. Better just to get a surprise update on our screens and have iphone guys joke about the poor schedule of updates on Android phones than to be resetting dates again and again and again and again. If we have a note 5 we have a premium device and are paying premium dollars for our plans. We expect and deserve better than this.
I agree with Paul. Since TELUS or Samsung are having problem delivering updates per their schedules, they should just say "Coming soon", or abandoning the whole concept of having a schedule. I do also understand that things don't always go as planned, but when you're pushing back an update for the THIRD time, don't embarass yourself by giving another date. People will just stop believing...
Please stop crushing our expectations!
Unfortunately, for those of you who may not be aware, pushing updates is not as simple as copying a file to a server and pushing a button.
Once Google provides the updated code to the phone maker, they go through it with fine toothed comb, add in their specific add-ons (except Nexus) then test and test and test. When they feel it's ready, they push to each of their OEM's like Telus, Rogers and Bell. All of this is controlled by Country obligations (India got M first, no idea why but they did), regional OEM (AT&T, Telus, Orange etc) and by things like volume sales and so forth.
Once Telus gets their hands on it, they go through it with fine toothed comb, add in their specific add-ons (except Nexus) then test and test and test (again). If anything comes up, it's back to square one. Fix it, then then test and test and test. Now imagine that this has to happen for ALL the devices that are identified as recipients by the manufacturers (HTC, LG, Samsung, Kyocera, etc). Resources are not limitless (although that's a seperate arguement altogether).
Now that all the testing is done, the scheduling begins, again perhaps the contractual obligations come into play (or not) however each scheduled device has a deployment date (usually includes a claw back period in case something nasty comes out that wasn't found in testing. Rare but it happens). And each device goes through the process.
So, for all of you raising concerns about why a device date was missed by a day or two or telling a service provider to "get your freakin act together", realize that you are part of a much larger project and your specific device may or may not be high up on the global deployment plan. Nobody is going to die if the upgrade takes a day or a week or a month longer. Chill out and be surprised when it does arrive. Just like Xmas only better.
We know many of you are waiting anxiously for the Android M update on the Note 5 & S6/Edge devices. The update was delayed because of a bug Samsung discovered during testing.
We will post a revised timeline once the OEM submits a new build.