Moto G Play finally gets Android N (January 2018)

[computergeek541]

Rather shockingly, the Telus version of the Moto G Play has finally been updated to Android 7.1.1.   After many missed timeframe promises, a friend informed me that her phone was just updated to Android N today. 

I think it's fair to say that many users either gave up on ever receiving this update or have even moved on to a different model phone.  it's slighltly amusing that an update to Android N was released today, when Android O is available.

[computergeek541]

---

@Jorno wrote:

Anyone know if the Motorola G 3rd Gen will receive Android N?

---

Sorry, but that phone will most likely never get that update as that model was never in the list of phones that Motorola promised to upgrade to Android 7.  If you want Android N, you'll have to get a new phone or unlock the bootloader of your phone and install a custom rom.

[Jorno]

Anyone know if the Motorola G 3rd Gen will receive Android N?

[computergeek541]

---

@Acekiller wrote:

it surely is ridicuolus to wait for the updates

---

Adding to that ridiculous wait is the fact that some batches of the Telus Moto G Play devices were pernanently stuck on the June 2016 security update even though there were multiple security updates release for the Telus version of this phone after that date.  The only solution that I ever found to that was to manually flash a slightly newer Telus/Moto stock rom using adb and fastboot.  After doing that, all other updates came in, unfortunately, each of which had to installed in sequence. 

[computergeek541]

---

@Shutdown wrote:

Wow your right I had to manually check for it. Thought I'd get a notification.

---

You would likely would have eventually received a notification whenever the phone decided to check for it.

[will13am]

My first foray into custom roms was on the Nexus S with cynaogen mod (which is now lineage).  Back in those days, beta builds meant exactly that.  There would be separate stable builds.  Backup should be done prior to any flash.  Now adays, beta is a production build.  I don't recall having a build that was so bad that actually crashed or caused all sorts of forced close issues.  Go ahead and wait a year for an update that is out of date when it arrives. 

[Mana]

I agree with @Shutdown that there is no point in jumping on the update as soon as it is available to be beta tester on your device. 

I rather wait for a stable version. 

[Shutdown]

I don't mind waiting for updates as long as they stable and we eventually get them.

[will13am]

---

@NDesai wrote:

Phone like Samsung S8 still does not have Oreo and S9 will be announced in February. It's a joke that they take so long to work on it to add their stuff. If regular updates is important to users, get a phone made by Google 🙂

---

This is not surprising at all when there are so many gatekeepers involved.  Samsung has to take a google build and add their code on top.  The touchwiz stuff has more lines of code than stock android.  There is an extensive test period before releasing the package to the carriers.  The carriers have to add their bloat and do further testing. 

I have a couple of phones running lineage.  A weekly build is shipped out on time every time.  If there is anything that I don't like, the dislike lasts a week.  What really needs to happen is a way for google to push out security updates separated from the circus at the manufacturer and carrier.

[Acekiller]

it surely is ridicuolus to wait for the updates

[Shutdown]

Wow your right I had to manually check for it. Thought I'd get a notification.

[NDesai]

Phone like Samsung S8 still does not have Oreo and S9 will be announced in February. It's a joke that they take so long to work on it to add their stuff. If regular updates is important to users, get a phone made by Google 🙂