Droid Turbo: Lollipop software update?

[I800C0LLECT]

I was really just joking but I guess it could be a possibility?

It could just as easily be an issue of manpower or lack thereof? Maybe VoLTE even?

 

[Phoenix212]

I wouldn't put too much into that, since the Turbo is pretty much a Nexus 6 Mini with some Verizon bloat. If the Nexus can run it, so can the Turbo.

Sent from my Ballistic Turbo

I thought the Turbo was basically a Moto X 2nd gen. with a souped up battery and processor, no?

Either way, your point is well taken.

 

[doogald]

I thought the Turbo was basically a Moto X 2nd gen. with a souped up battery and processor, no?

No, it's really closer to a Nexus 6 with a different camera and capacitive buttons (the screen is physically smaller but has the same resolution). The Moto X is a lower level system on a chip, lower resolution display, 2 GB RAM; the Moto X and Nexus 6 have the same camera, too.

 

[TurboHope]

I was really just joking but I guess it could be a possibility?

It could just as easily be an issue of manpower or lack thereof? Maybe VoLTE even?

Doubtful, im using a phone with built-in buttons running 5.0.2. I would go with the manpower issue being most likely.

Posted via the Android Central App

 

[GeodudeFFP]

+1. This was even brought up when the phone was announced. There were a few people on this site that said there is going to be issue with LP because of the buttons. Darn buttons

Maybe...although it works fine on my old One M7 (but maybe the Turbo has "complicating" issues).

Posted via the Android Central App

 

[thatguy97]

Wow it's been a day since anyone's posted anything

Posted via the Android Central App

 

[mobrules]

Wow it's been a day since anyone's posted anything

Posted via the Android Central App

Thanks for being "that guy"

 

[deesugar]

Wow it's been a day since anyone's posted anything

That's because we're all enjoying our 5.1 lollipop update

 

[vzwuser76]

I just had a thought here, does anyone think that perhaps the reason for the holdup on pushing out LP to the Turbo has to do with Verizon's Advance Calling update not playing well with the baked in VoLTE capabilities in LP? IIRC none of the devices on Verizon that have the Advance Calling update also have 5.1, which is the version of LP that has VoLTE baked in. Any phones that do have Advance Calling are on 5.0.2 or earlier, builds that don't have VoLTE capability. The 2014 Moto X has LP but doesn't have AC, so maybe that is the reason for the delay. I mean we are looking for a reason that affects the Turbo and not other devices. Perhaps if they had simply updated the Turbo to 5.0.2 and had the AC update there wouldn't have been an issue (or as big of one).

I'm thinking they (Verizon & Motorola) thought it'd be better to wait for for 5.1 to take advantage of having VoLTE baked in to go along with their AC update, possibly because there were some issues with AC and the 5.0.X builds, but when they started working on the 5.1 builds, they found a more serious issue with AC and 5.1, and they've been problems trying to make the two work together. Just a thought.

 

[doogald]

I'm thinking they (Verizon & Motorola) thought it'd be better to wait for for 5.1 to take advantage of having VoLTE baked in to go along with their AC update, possibly because there were some issues with AC and the 5.0.X builds, but when they started working on the 5.1 builds, they found a more serious issue with AC and 5.1, and they've been problems trying to make the two work together. Just a thought.

Good thought, but the Verizon Nexus 6 has 5.1 and VoLTE. And we know that the Turbo is almost the same device.

 

[JJ Jones]

More likely that there's one new piece of Verizon bloat that's not playing nice and rather than leave it off and give us 5.1, Big Red is working diligently to figure out how to make it work.

Sent from my Ballistic Turbo

 

[tvouge]

More likely that there's one new piece of Verizon bloat that's not playing nice and rather than leave it off and give us 5.1, Big Red is working diligently to figure out how to make it work.

Sent from my Ballistic Turbo

Maybe.

Honestly, this is all speculation, but maybe since Moto is no longer under the Google umbrella (read, cash to burn) their priorities are on the product lines that make them the most money. This fits well with reality, as most of their solo products are already on some version of lollipop. Moto X, G... Nexus 6.

It does suck for us, as the end users, but it makes sense to me that they would focus their now more limited resources on projects that have the most impact on their bottom lines. The Turbo is mostly a Verizon product, outsourced to Moto. Yes there are variants of it sold outside of the United States, the Motorola Maxx. Guess what? That variant already has lollipop.

But, I could be wrong. Just seems like a possibility to me.

Posted via the Android Central App

 

[miesnerd]

Regardless of their reasons or priorities for delays, I've learned i cannot count on Verizon from all of this. My next phone, regardless of price (and m stingy by nature) will be on the network I want by my standards. My contract is up in a year, and Verizon has only given me motivation to say goodbye.

Posted via the Android Central App

 

[mobrules]

I was super happy with my turbo, coming from RMHD. Battery life was my main concern. However with as long as this is taking makes me wonder if the AC issue brought up above is correct. Or maybe it's another piece of software. The longer it goes on the more I wonder if it will even happen at all. Being a flagship device this hasn't been taken care of the correct way.
I however am one that fought to keep my UDL package. So I feel kind of screwed. But in my defense since they made it hard to keep unlimited, I feel it's my duty to use as much as possible. There are several new devices coming with large batteries and swappable batteries so maybe I will consider that.

 

[Clocks]

I just had a thought here, does anyone think that perhaps the reason for the holdup on pushing out LP to the Turbo has to do with Verizon's Advance Calling update not playing well with the baked in VoLTE capabilities in LP? IIRC none of the devices on Verizon that have the Advance Calling update also have 5.1, which is the version of LP that has VoLTE baked in. Any phones that do have Advance Calling are on 5.0.2 or earlier, builds that don't have VoLTE capability. The 2014 Moto X has LP but doesn't have AC, so maybe that is the reason for the delay. I mean we are looking for a reason that affects the Turbo and not other devices. Perhaps if they had simply updated the Turbo to 5.0.2 and had the AC update there wouldn't have been an issue (or as big of one).

I'm thinking they (Verizon & Motorola) thought it'd be better to wait for for 5.1 to take advantage of having VoLTE baked in to go along with their AC update, possibly because there were some issues with AC and the 5.0.X builds, but when they started working on the 5.1 builds, they found a more serious issue with AC and 5.1, and they've been problems trying to make the two work together. Just a thought.

Volte on verizon works great on the nexus 6, even when using the non-verizon nexus 6 5.1.1 software. Whatever issues might have existed they cleared up before it hit the nexus 6.

 

[Ry]

I was super happy with my turbo, coming from RMHD. Battery life was my main concern. However with as long as this is taking makes me wonder if the AC issue brought up above is correct. Or maybe it's another piece of software. The longer it goes on the more I wonder if it will even happen at all. Being a flagship device this hasn't been taken care of the correct way.
I however am one that fought to keep my UDL package. So I feel kind of screwed. But in my defense since they made it hard to keep unlimited, I feel it's my duty to use as much as possible. There are several new devices coming with large batteries and swappable batteries so maybe I will consider that.

Not sure how you have to fight hard to keep UDP. It's not hard at all to keep unlimited.

 

[Ry]

More likely that there's one new piece of Verizon bloat that's not playing nice and rather than leave it off and give us 5.1, Big Red is working diligently to figure out how to make it work.

Sent from my Ballistic Turbo

Or..

Updates for the first and second generation Moto X, Moto G, and Moto E are all ahead of it.

Didn't this happen with the 2013 DROIDs too? While it got 4.4 rather quickly, it skipped 4.4.2 and got 4.4.4 later.

 

[doogald]

Didn't this happen with the 2013 DROIDs too? While it got 4.4 rather quickly, it skipped 4.4.2 and got 4.4.4 later.

Yes, in fact, Verizon made Motorola push a minor network update in May 2014 rather than 4.4.2 (or a build of 4.4.2 that included the minor network update), despite the fact that Motorola was ready to test 4.4.2. Earlier they also made Motorola include the Jellybean blue color status bar network icons rather than the white KitKat icons with the first 4.4 update (which I rather liked, but, still, Motorola obviously had to change the KK framework manually), though they finally relented with the 4.4.4 update.

Perhaps I shouldn't complain too much about that, as the 2013 Droids probably never would have received a 4.4.4 update if it did get 4.4.2, but the initial 4.4 build had some serious bugs that affected more people than the network update fix they pushed in May (which affected customers roaming in a particular part of Canada, as I recall.)

Again, Verizon does not handle this phone like a flagship. Instead, they market it for its battery life and its Verizon network features (XLTE and VoLTE) and even features that aren't uncommon ("turbo" charging), don't even mention the version of Android, and they don't seem to care whether it has the latest version of Android on it or not. If it was truly a flagship, Verizon would be aggressive about keeping it updated. Instead if they are aggressive about anything, it's that it supports the Verizon network features that they want to push right now.

There are any number of reasons why the update is not ready yet - maybe it's VoLTE not working right, maybe it's Verizon specific software (i.e., the command center widget) not working right, or maybe it's as simple as Verizon needs to update reference material for their call-in support technicians and hasn't finished yet. Or it could be that the leak that it was coming out last week made them stubbornly delay to try to tell employees that future leaks will be responded to in a way to discredit the leak so the recipient of the leak will no longer trust the leaker.

At this point, anything is possible, and it doesn't really matter why, does it?

 

[Almeuit]

I just had a thought here, does anyone think that perhaps the reason for the holdup on pushing out LP to the Turbo has to do with Verizon's Advance Calling update not playing well with the baked in VoLTE capabilities in LP?

I would say no -- Other phones have LP on 5.1 and have Advanced Calling from Verizon. An example is the LG G4.

 

[Ry]

Yes, in fact, Verizon made Motorola push a minor network update in May 2014 rather than 4.4.2 (or a build of 4.4.2 that included the minor network update), despite the fact that Motorola was ready to test 4.4.2.

Network performance/bug fix update seems more important than going up a full version of the OS.

Could you link to where Motorola was ready to submit 4.4.2?

Earlier they also made Motorola include the Jellybean blue color status bar network icons rather than the white KitKat icons with the first 4.4 update (which I rather liked, but, still, Motorola obviously had to change the KK framework manually), though they finally relented with the 4.4.4 update.

Probably to prevent customer service calls post-update on "why are my icons not changing color anymore?"

Perhaps I shouldn't complain too much about that, as the 2013 Droids probably never would have received a 4.4.4 update if it did get 4.4.2, but the initial 4.4 build had some serious bugs that affected more people than the network update fix they pushed in May (which affected customers roaming in a particular part of Canada, as I recall.)

And is the assumption that AOSP 4.4.2 or 4.4.4 would have resolved the problem? Or was the fix rolled into Motorola's fork of the 4.4.4 build?

Again, Verizon does not handle this phone like a flagship. Instead, they market it for its battery life and its Verizon network features (XLTE and VoLTE) and even features that aren't uncommon ("turbo" charging), don't even mention the version of Android, and they don't seem to care whether it has the latest version of Android on it or not. If it was truly a flagship, Verizon would be aggressive about keeping it updated. Instead if they are aggressive about anything, it's that it supports the Verizon network features that they want to push right now.

The way they market it, IMO, they absolutely handle this phone as a flagship. It's their main device. Almost a year later and new ads continue to roll out and the hardware got some additional customization options.

But your definition of "flagship" is different than Verizon. Verizon pushes this device on features that "normals" can relate to. Big battery, up to 48-hours of batter life. XLTE! That must be better than LTE.

Outside of people that post on this forum, the Android OS version is not a sales driver.

There are any number of reasons why the update is not ready yet - maybe it's VoLTE not working right, maybe it's Verizon specific software (i.e., the command center widget) not working right, or maybe it's as simple as Verizon needs to update reference material for their call-in support technicians and hasn't finished yet. Or it could be that the leak that it was coming out last week made them stubbornly delay to try to tell employees that future leaks will be responded to in a way to discredit the leak so the recipient of the leak will no longer trust the leaker.

Or.. they're just not ready to release it.

Verizon and Motorola got an update out for the prepaid second gen Motorola Moto E that got it up to Lollipop 5.1. I think it launched on 5.0.2. That should tell you where the DROID TURBO is in the update queue.