---

wrote:

In fact my sister bought a Moto G5S Plus yesterday and it came with the Oreo version already. So no, they won't wait 'til G6 launch. (I have a moto G5 plus and I'm waiting for the release too.)

---

Joking right?

I don't believe that Moto G5s plus came with Oreo out of the box. Can you take a screenshot of about phone of G5s plus and post it here?

I'm pretty sure it'll be 7.1.1 that is Nougat.

---

wrote:

In fact my sister bought a Moto G5S Plus yesterday and it came with the Oreo version already. So no, they won't wait 'til G6 launch. (I have a moto G5 plus and I'm waiting for the release too.)

---

Are you sure about what you said? I don't think so. My friend has just recieved a G5s Plus an hour ago and it is on Nougat 7.1.1 with October security patch.

Disappointed from Moto bcz when lenovo purchased Moto they destroy everything in moto.1)Wrost service of moto.2) Standard didn't maintain by Moto brand.They thinks lots of customer who's faith in Moto they are foolish.3)Very slowly rolling out Oreo for G5+ while other companies rolling out Oreo for eligible devices.Moto in last.Very cheap.

---

wrote:

---

---

 

They don't have the resources allocated to do monthly patch cycles for all of the devices they are trying to support. Unlike custom ROM teams, they can't just apply Google's patches and push out because there's no way to roll back, and no supported backup method. They have to do regression testing against a lot of other code. Can you imagine the grief a bad update could cause? Bricked devices. Lost data.

---

Not writing this for the benefit of anyone here, only with the slim hope that the PTB may come across this:

Then, if all that is true (and know way of knowing if it is or how much) the least Lenovo-Moto could do would be to make  some kind of announcement--prominently displayed somewhere where it can't be missed--along the lines of,

"We understand the concerns of many of our users regarding the KRACK vulnerability. Rest assured, we are currently developing a patch for all affected users, which we will release as soon as possible." 

The closest anyone from staff has come to this, as far as I can see, is from 11/02, completely buried somewhere in a thread I found only by doing an extensive search, "We're aware of the issue, and we are developing a plan to address it. However, there is no specific timing to share."

That, instead of letting everyone concerned twist in the wind--exacerbated especially with the thinnest of comments of "senior" contributors here in a Lenovo supported forum such as, "No one here has a date, and moto doesn't provide dates," along with a most patronizing suggestion to visit a site with the most basic, entry level information regarding protecting oneself.

>>Can you imagine the grief a bad update could cause? Bricked devices. Lost data.

And can you image the possible grief an unpatched android phone may cause its user: ransomware, phishing, MiTM attacks, theft of credit card, banking and other sensitive data, etc.? And not askng for a monthly update, just a godamn patch for something that's been known by vendors weeks before its public announcement around mid-October.

Oreo with Dolby Atmos update my Moto g5 plus   please 

---

wrote:

---

wrote:
Can you imagine the grief a bad update could cause? Bricked devices. Lost data.

 

 

And can you image the possible grief an unpatched android phone may cause its user: ransomware, phishing, MiTM attacks, theft of credit card, banking and other sensitive data, etc.? And not askng for a monthly update, just a godamn patch for something that's been known by vendors weeks before its public announcement around mid-October. 

---

---

As I said, I've got lots of active devices that will never see a patch from the OE/Carrier, and there are millions more out there. Devices on store sheves right now.

I don't like how Motorola/Lenovo is handling things, but I can understand it.
A known attack that has known ways of protecting against being exploited is far less of a PR problem than a bad patch would be.

It's just part of dealing with low budget devices in the Android world. And yes, the Moto G is a low budget device.

If you want reliable, quick updates you have to buy top end, flagship devices, and replace them ever 2 years.
(or forgo OEM/Carrier support)

Older devices or lower tier devices are a mess.

I would hope the Moto Z family is getting better support, but I have little confidnce that Lenovo manages to do anybetter there. The Droid line is all more than 2 yrs old so I expect it's been abandonded.

(RETIN Channel) The November security patch update is here.... 159.2 mb 

Version : NPN25.137-92

When company releasing the Oreo update in Moto G5 plus other brands are already released the latest update of Oreo , Nokia also getting the new Oreo update

I have downloaded the POTTER_NPN25.137-92_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip. Seems to be for the 1683, I have the 1687. Can supply exact specs if that would be helpful. Only difference I can see is the '83 is dual sim, mine is single.

<edited - flashing discussions and link to flashing not allowed>