Any way to force a security patch update?

[RK928]

Mine is still on the May security patch, I see there's now a November Android patch so that means I'm 2 behind at least. I try doing the phone update about once a week and it tells me I'm up to date. Mine is an unlocked version, bought direct from Motorola, on ATT GoPhone.

Is everyone's MXPE on the May update also? Any way to force a security update?

 

[Jheebs]

Ha ha... That's funny! May is the latest for this so called "flagship"... So hurry up and wait like the rest of us!

 

[katesbb]

Yup, May update here as well.

Just bought mine via Best Buy. Running on Verizon.

If I understand what I've read, Motorola decided to release our updates in batches rather than monthly.

 

[acejavelin]

Carrier and purchase place is not relevant, retail devices are updated by Moto (Lenovo) directly...

Problem is, Moto has mostly abandoned devices over 6 months or so old. We are told we will get Nougat, I'll believe it when I see it. Moto is a mere shadow of what it was, it's just a name to Lenovo.

And yes, May is the current security patch level we have.

 

[J Dubbs]

And we haven't even gotten 6.01. Although I'm kinda glad, I've read plenty about it causing more harm than good Nougats a deal breaker for me, if we don't get a stable, solid performing version this WILL be my last Android phone

 

[acejavelin]

And we haven't even gotten 6.01. Although I'm kinda glad, I've read plenty about it causing more harm than good ������ Nougats a deal breaker for me, if we don't get a stable, solid performing version this WILL be my last Android phone ������

6.0.1 on Moto devices is stable, it was only implemented "where needed", meaning India and some of Europe... although it is thought the real reason was it exaggerated the phantom scroll/touch issue more than 6.0 so the roll-out was halted.

There are several stable Nougat ROMs, but we already know we won't be getting it officially... As of now anyways, regardless of the petition with nearly 13,700 signatures requesting it.

This goes back to what Lenovo has done to Moto, they bought the company for the brand name and recognition, and other than that they have just sucked it dry and destroyed it. These (Moto G3 and MXPE) are my last Moto phones.

(EDIT: Sorry I thought I was in the Moto G 3rd Gen section)

 

[pizza_pablo]

My MXPE (US-Verizon) has Nov 1, 2015, for the Security Patch.

 

[telrod11]

My MXPE (US-Verizon) has Nov 1, 2015, for the Security Patch.

I'm still on the May security patch (Cricket).

Anyone else seen a November update?

 

[Jheebs]

I'm still on the May security patch (Cricket).

Anyone else seen a November update?

That's last November...2015

 

[telrod11]

That's last November...2015

Wow.... (slaps head)
Am I some kind of a slow optimist or what?

 

[acejavelin]

My MXPE (US-Verizon) has Nov 1, 2015, for the Security Patch.

MXPE is an unlocked device, it wasn't sold by carriers to my knowledge, so all updates come directly from Moto... the current release is a May 1, 2016, security update.

 

[straygator7]

I just received the September security update this morning.

 

[Ry]

I just received the September security update this morning.

what's the system and build number?

 

[straygator7]

what's the system and build number?

System version: 24.221.8.clark_retus.en.US retus

Build number: MPHS24.49-18-8

Android security patch level: September 1, 2016

 

[Ry]

System version: 24.221.8.clark_retus.en.US retus

Build number: MPHS24.49-18-8

Android security patch level: September 1, 2016

Thanks!

 

[pizza_pablo]

System version: 24.221.8.clark_retus.en.US retus

Build number: MPHS24.49-18-8

Android security patch level: September 1, 2016

What country are you in?
Which carrier do you use?

 

[straygator7]

I'm in the USA, and on Verizon Wireless.

 

[pizza_pablo]

I'm in the USA, and on Verizon Wireless.

So am I, on both accounts.
My latest is May 2016 and I just checked software updates and nothing new.
Odd....

 

[Ry]

MXPE is an unlocked device, it wasn't sold by carriers to my knowledge, so all updates come directly from Moto... the current release is a May 1, 2016, security update.

Actually - it's usually the OEM that actually hosts and pushes the update regardless if it's a carrier phone or not. While the update won't come from a carrier, approval can come from a carrier.

For example, Motorola still submits the Moto X Pure Edition and it's updates to Verizon for testing. This is why some updates can be delayed if you have a certain carrier SIM in the phone.

 

[pizza_pablo]

Actually - it's usually the OEM that actually hosts and pushes the update regardless if it's a carrier phone or not. While the update won't come from a carrier, approval can come from a carrier.

For example, Motorola still submits the Moto X Pure Edition and it's updates to Verizon for testing. This is why some updates can be delayed if you have a certain carrier SIM in the phone.

I'm not surprised by Verizon wanting to maintain as much control as possible, even if the hardware did not originate with VZW.

I am puzzled at the difference in arrival time, of the security patch, within the same service provider.