7.1.1 for the Nexus 6P on Verizon

[vzwuser76]

A question for the last 2 posters, where you already on 7.1.1 or were you still on 7.0?

I called last night to Google support since it had been a week and the CSR never called me back. It was as frustrating as my previous calls were. The rep told me that all devices not on 7.1.1 would have it by the end of the 2nd week of February, aka this week. He asked if I was still on 7.0 or 7.1, and I said all my previous calls said I was still on 7.0. He told me to be patient because they'd only released 7.0 in December and 7.1.1 in January. I replied that 7.0 was released in September/October and 7.1.1 was in December. He told me I was incorrect!

I swear these reps have no idea what they're talking about. It's like they have their cheat sheet with approved questions to ask callers. And they're not even in the US, because when I called at 10pm last night the rep greeted me saying good afternoon!

At this point, if I don't see it by the end of February (and that's being generous IMHO) then I'm done with Google going forward. If this were any other company like Samsung or Moto, it would be pitchforks galore. But here we've got a device that's touted as getting the latest software in short order and it's almost 2 months after any updates. I don't recall this happening with any previous Nexus update, so if this is their plan going ahead, this is where I get off.

 

[Nate Silver]

Was already on 7.1.1 in my case. Don't recall just when I got that OTA.........about a month/6 weeks ago maybe?

 

[Robisan]

I called last night to Google support since it had been a week and the CSR never called me back....

I took a shot at calling Google support Thursday of last week and my initial call went as yours have gone - pretty much utter nonsense. The guy even tried to sell me that since they were already working on 7.1.2 that we'd probably have to wait for that. After the call I took the 'how did we do' customer service survey and chose dissatisfied on all questions.

A couple of hours later I got a call back from someone else at Google to follow up, since I'd indicated in the survey that they had not resolved my problem. Guy seemed like a reasonable, thinking human being, I explained the situation, he seemed to understand the issues and agreed this was a problem. Was told he'd look into it and that he'd try to resolve it within a few days. As of Monday evening I haven't heard back, nor received an OTA on my phone.

 

[Robisan]

Was already on 7.1.1 in my case. Don't recall just when I got that OTA.........about a month/6 weeks ago maybe?

I know it was awhile ago, but if you recall, were you on the December NBD91V build when you received the 7.1.1 OTA or some other 7.0 build? Puzzled why you got the 7.1.1 OTA while many of us are stuck on December/NBD91V. TIA

 

[opuntia2]

A question for the last 2 posters, where you already on 7.1.1 or were you still on 7.0?...

I was already on 7.1.1 but only because I just recently sideloaded the N4F26J build. Previously I was on NBD91V, which was 7.0, and I think was some kind of black hole that if you had that build it was preventing an OTA update to the "J" build.

 

[Nate Silver]

Geez, no, I'm sorry. Don't recall what build it was. I got 7.0 on beta, then the final OTA. Then pulled out of the beta and got 7.1.1 OTA. I've never side-loaded anything, all was OTA, if that helps.

 

[psipher]

I just got the OTA push.
I was on 7.0 (Dec update), got the 7.1.1 (Jan update, 621 MB) then a separate OTA for the Feb update.

 

[thethruth34]

same here

 

[crosspatch]

At this point, if I don't see it by the end of February (and that's being generous IMHO) then I'm done with Google going forward. If this were any other company like Samsung or Moto, it would be pitchforks galore. But here we've got a device that's touted as getting the latest software in short order and it's almost 2 months after any updates. I don't recall this happening with any previous Nexus update, so if this is their plan going ahead, this is where I get off.

I'm with you. I'm not content with the way some customers seem to outrank others. Or, if that's not the case, they should at least COMMUNICATE to explain what is going on with the updates. And yet, they don't even do that when you ASK them directly.

I only really care about this nonsense because I want the security updates. You're constantly being chided to keep on top of updates, but look at what a time-wasting source of frustration it is when you do.

No way I'm ever using a Crapple device, so I guess if this pushes me over the edge, I'll use a burner and my Garmin GPS. I'm beginning to feel liberated just thinking about it.

 

[vzwuser76]

I just got the OTA push.
I was on 7.0 (Dec update), got the 7.1.1 (Jan update, 621 MB) then a separate OTA for the Feb update.

Do you know what build you were on with 7.0? Did it end with the letter V? Because that appears to be the one that I and some others are stuck on.

 

[Robisan]

Got the OTA push - installing 621.4mb 7.1.1 update now.

Complete. Took me from Dec 5 build NBD91V to Jan 5, 2017 build N4F26J.

Checked for update and immediately download/installed Feb 5 security patch, build NUF26K.

Finally I have an up-to-date phone again!

 

[vzwuser76]

Got the OTA push - installing 621.4mb 7.1.1 update now.

Complete. Took me from Dec 5 build NBD91V to Jan 5, 2017 build N4F26J.

Checked for update and immediately download/installed Feb 5 security patch, build NUF26K.

Finally I have an up-to-date phone again!

That's reassuring to hear. Now I'll just have to wait for mine to come around.

 

[HaboobZ]

I just received the 7.1.1 update last night for my VZW 6P - OTA. Not on beta or anything.

Guess things are finally rolling.

 

[GW X]

Newbie here. Just received the official OTA 7.1.1 update on my Verizon 6P. I was under the impression that I would have the Pixel UI or at least some of it with the update. Was that just ignorant of me?

7.1.1 looks exactly the same as 7.0 on my 6P.

Here's the info I see in settings: Android version 7.1.1. Baseband version: angler-03.79. Build number: NUF26K.

I thought I would have quick app shortcuts, I don't. No new emoji (which is fine with me).

Is Verizon to blame? Google?

At this point, the only way to get quick app shortcuts is if I use Nova/Action/some other launcher, which I'm not opposed to, but thought I would just enjoy Pure Android for a bit.

 

[GW X]

Just downloaded Pixel UI APK, so now things look and work like I thought they would/should. Mostly.

 

[Robisan]

At this point, the only way to get quick app shortcuts is if I use Nova/Action/some other launcher...,

I'm using Nova and 7.1.1 brought some new quick launch options. For example, a long press on Google Maps brings quick launch for navigation to Home and Work.

 

[Mugley]

I updated to 7.1.1 this morning on Verizon and quick app shortcuts are working.

 

[dyastrab]

Got it last night. Not rooted or in Beta.

 

[vzwuser76]

Nothing yet here, maybe they're punishing me for calling into support too much.

 

[GPuba]

Geez, no, I'm sorry. Don't recall what build it was. I got 7.0 on beta, then the final OTA. Then pulled out of the beta and got 7.1.1 OTA. I've never side-loaded anything, all was OTA, if that helps.

Same here.

By the way, I just received my Feb security patch about 30 min ago.