Newsletter
As we watch the countdown to Canadian devices getting their Android 6.0 Marshmallow update, Telus has come out with their updated Marshmallow schedule and below we have posted the list. While there are shifts and changes, which are to be expected, there is one glaring omission from the January update – the LG G3, which was scheduled for its update on March 14, has been removed from the listing altogether. When our source contacted Telus about the situation they said, “we will be getting the update for the G3, but don’t have a specific date yet. We’ll communicate availability on our website as soon as we receive it.” So that is good news for LG G3 owners – you may have to wait a while longer, but it sounds like the device will eventually receive the upgrade.
Looking further at the chart, we see that the Samsung Galaxy S6 Edge Plus and Note 5 are scheduled for their Marshmallow upgrade on March 16. Following will be the Moto X Play on March 21 – longer than normal for a Motorola device…could this be because of the Lenovo takeover…will Moto devices take longer to update from now on? It will certainly be something to keep an eye on for future upgrades. Two of the Alcatel Pixi 3 models are new to the list, specifically, the 4-inch and 4.5-inch model will get some bug fixes and a security update on March 22. The Samsung A5 will see some bug fixes and a security update on March 23. That same date, March 23, the Kyocera DuraForce is scheduled for its Lollipop and security update. The Samsung Galaxy S6 Edge will have to wait until March 30 for its taste of Marshmallow and security updates – we realize the Galaxy S6 Edge+ is newer, but one would think the update files would be close enough for them to receive them at the same time. The Samsung Galaxy S6 users must wait until April 13 for its Android 6.0 loving.
It is so tempting to etch the date of your update in your mind as though it is set in stone, but dates are always subject to change as the Telus disclaimer states – “All dates are approximate and subject to change. See the Software Update Life-Cycle blog post for more information.” While we tend to blame the carrier, most of the time it is the manufacturer that must do rigorous testing to make sure there are no snafus during the upgrade. The carriers must then test the device on their network to make sure it runs stable and the Industry Canada regulations must be met. If there are problems along the way, the entire process may have to start over. It could be so easy if they just used pure vanilla Android and not their own UI.
