Droid Turbo Marshmallow Update?

[Guck]

You are actually incorrect. Once a company, Motorola in this case, has completed an update for a phone it can be installed on it. This means if you bought the phone directly from them it can be updated, such as a Moto X. If the device is sold through a carrier(also called a partner), then the update, which is already complete and approved for the device, is released to them to review, edit, and decide when to push out. So when Motorola's website says the Droid Turbo update is complete and pending partner release, it means they've given the completed update to Verizon to do with it as they wish.

[Tidbits]

Wrong... Motorola already went in record you are wrong... HTC, and Sony too. Carriers don't touch the code.

Do you think these manufacturers are going to hand their source code to hundreds of companies and have not one lrake of their source code? Come on now let's be serious here. Not even Microsoft allow that much leeway.

[Tidbits]

Also that message is a generic message. It even says that on unlock and unbranded devices if they are going to make an update for. So when you see partner support there's more to it than just the carriers.

[Guck]

You must be very ignorant when it comes to Android, or AOSP, which stands for Android OPEN SOURCE Project. The entire OS is completely open for anyone to see, modify, and use, that's why you'll find custom ROMs on different phones. Phone manufacturers will get the stock ROM from Google, and then tweak it so it will work with the specific phone's hardware, remove features the phone can't support or they don't want on it, apply their own launcher (like Touchwiz), and add any new bloatware. When they are done, they give it to the carriers, who tweak it how they want, be it to make sure it will work on their networks, removing any features they don't want usable, adding bloatware, etc, and then they pass it on to the consumer.

[Tidbits]

Yawn... you must be ignorant.

AOSP is open source. The Motorola specific software and code is proprietary. It is not in AOSP branch and it belongs to Motorola. Also learn the difference between ASL and GPL before making claims about ones knowledge. Thanks have a great day.

[Tidbits]

Also you are wrong about how things are done. Even manufacturers own printed timelines they've posted says the way you say it is done is wrong.  Go figure on who the ignorant one is when the manufacturer own documents says it's wrong.

[Jecko]

Y

[Tidbits]

The part about giving the code to carriers is wrong. Manufacturers have said. We tell the carriers we are working on an update and per contractual agreement carriers give their software packages to manufacturers in advance and they incorporate said code. All their printed documented timelines reflect this.  HTC went as far to make their picture based with numbers and steps. Those low level reps from manufacturers say whatever to get you off the phone because their little computers won't tell them the answer and it's easier to lie as they know you'll buy it even when there is documents from their higher ups that says otherwise.

[Alanhagg]

Guck, I think you miss the point, that most Verizon customers are not

hackers, or at the least, not interested in rooting their phones. Depending

on the carrier puts us behind the eight ball in many ways, but it also

helps in warrantee situations.

Don't be hard on our impatience. We all need to bug Verizon...

soli fide, soli gracia.

[SandTrout]

My question was trying to figure out what to do to protect our DROID Turbo

from Stage fright threats ... My friends with DROID Turbo2 phones got a

security update ... But we original Turbo owners running Lollipop are still

vulnerable.

Mary