7.1.1 for the Nexus 6P on Verizon

[Nate Silver]

I'm on Verizon and have had the N4F26J build for weeks, and the January 5th security update for a week or two (both OTA). Its my backup phone and hasn't had a sim in it for some time, maybe that has something to do with it?

 

[Dranik]

I was waiting, but gave up. Sideloaded J build and everything looks good. Have HDVoice and simultaneous data and voice. The only thing that doesnt work is Visual Voicemail - but I'm on prepaid plan so not sure if it should be working in a first place.
Overall, very disappointed with Google, Project Fi, and Nexus. Next time will definitely buy some other brand, at least they don't promise something they cannot deliver on time.

 

[GPuba]

I'm on Verizon and have had the N4F26J build for weeks, and the January 5th security update for a week or two (both OTA). Its my backup phone and hasn't had a sim in it for some time, maybe that has something to do with it?

Same here. I've been getting the updates just fine, and I'm on Verizon.

 

[opuntia2]

Same here. I've been getting the updates just fine, and I'm on Verizon.

Up until the January update/N4F26J build I too was getting the regular security updates just fine, but it's been very quiet lately.

 

[vzwuser76]

I'm on Verizon and have had the N4F26J build for weeks, and the January 5th security update for a week or two (both OTA). Its my backup phone and hasn't had a sim in it for some time, maybe that has something to do with it?

Same as mine is. Still haven't gotten the the update even after a FDR, and when I contacted Google they said they'd get back to me. That was I believe 5 days ago. It's troubling considering their support was excellent when I needed it early on on my 6p. But it seems after the Pixel announcement it's gone down hill.

 

[vzwuser76]

I was waiting, but gave up. Sideloaded J build and everything looks good. Have HDVoice and simultaneous data and voice. The only thing that doesnt work is Visual Voicemail - but I'm on prepaid plan so not sure if it should be working in a first place.
Overall, very disappointed with Google, Project Fi, and Nexus. Next time will definitely buy some other brand, at least they don't promise something they cannot deliver on time.

Just out of curiosity, do you have access to WiFi Calling on Verizon with your 6p? I know we didn't have it before, but just curious if maybe they enabled it in 7.1.1.

 

[Robisan]

I'm on Verizon and have had the N4F26J build for weeks, and the January 5th security update for a week or two (both OTA). Its my backup phone and hasn't had a sim in it for some time, maybe that has something to do with it?

Same here. I've been getting the updates just fine, and I'm on Verizon.

Just to clarify - did you receive the N4F26J via OTA push or did you sideload it? I haven't received an OTA push since December's NBD91V build.

 

[Nate Silver]

Just out of curiosity, do you have access to WiFi Calling on Verizon with your 6p? I know we didn't have it before, but just curious if maybe they enabled it in 7.1.1.

Sorry, haven't tried it. My workplace blocks WiFi calls, so it wouldn't do me much good.

 

[Nate Silver]

Just to clarify - did you receive the N4F26J via OTA push or did you sideload it? I haven't received an OTA push since December's NBD91V build.

In my case, OTA.

 

[opuntia2]

Just to clarify - did you receive the N4F26J via OTA push or did you sideload it? I haven't received an OTA push since December's NBD91V build.

I saw someone theorize on another forum that the issue is that those with the NBD91V build will not get the N4F26J build because the "V" build isn't on Google's OTA download page https://developers.google.com/android/ota#angler

They contacted Google and they were told to sideload.

I have the "V" build via OTA so I'm wondering how it's possible that Google doesn't know about it.

 

[Bruce39]

I am still on NMF26F (Dec. 5 update). I believe this was the last Beta update. I may never get the Verizon Jan update (or any other). Since I joined the Beta program in mid November I can't access my Verizon account from my phone; it says my phone is "an unauthorized phone"; probably because I have non-Verizon software. I know that I can leave beta & go back to 7.0, then get the download from Verizon or download myself; but for now, I don't want to. I am actually on my granddaughter's account as a family member (she gets a good discount from her job) so I don't have to ever access my account unless I just want to. It is nice to not have any Verizon BLOAT on a phone; I actually had to download the Verizon app to access my account (which I can't access now).

 

[psychoD33x]

If I'm on "V" build and want to try and sideload, would I go straight to load "J" build?

 

[vzwuser76]

I saw someone theorize on another forum that the issue is that those with the NBD91V build will not get the N4F26J build because the "V" build isn't on Google's OTA download page https://developers.google.com/android/ota#angler

They contacted Google and they were told to sideload.

I have the "V" build via OTA so I'm wondering how it's possible that Google doesn't know about it.

I also have the "V" build, and also got it OTA, so I don't know how they can claim ignorance about it. Since it's not on their page, if it was an update they pushed, halted and replaced, then why didn't they send the revised update to those on the "V" build? And if nothing else, why not push and update specifically for those on the "V" build? Whatever happened, the update path was broken for a segment of their users, it should be up to Google, not the users, to fix the problem.

 

[GPuba]

Just to clarify - did you receive the N4F26J via OTA push or did you sideload it? I haven't received an OTA push since December's NBD91V build.

I got it via OTA push.

 

[Robisan]

I also have the "V" build, and also got it OTA, so I don't know how they can claim ignorance about it. Since it's not on their page, if it was an update they pushed, halted and replaced, then why didn't they send the revised update to those on the "V" build? And if nothing else, why not push and update specifically for those on the "V" build? Whatever happened, the update path was broken for a segment of their users, it should be up to Google, not the users, to fix the problem.

^^This. I don't care how easy people say it is, I have no interest in sideloading and I shouldn't have to. I have taken the OTA releases when they come, including the December "V" build release, and I expect future updates to be sent accordingly.

 

[opuntia2]

Just to see what they would say I called Google Store support and basically their response was to just wait. They couldn't guarantee when I would get the update but I just needed to wait. I guess that was my mistake for calling on a Sunday, probably not their "A" support team.

When it's time for me to get a new phone I think I'm done with Google.

 

[vzwuser76]

Just to see what they would say I called Google Store support and basically their response was to just wait. They couldn't guarantee when I would get the update but I just needed to wait. I guess that was my mistake for calling on a Sunday, probably not their "A" support team.

When it's time for me to get a new phone I think I'm done with Google.

That's what they told me on Friday, although I'll agree that it seems like their support has fallen off since when I had my 6p new. Maybe the A team was shifted to the Pixel phones.

 

[Dranik]

Just out of curiosity, do you have access to WiFi Calling on Verizon with your 6p? I know we didn't have it before, but just curious if maybe they enabled it in 7.1.1.

WiFi calling not working for me on J build.

 

[opuntia2]

So I bit the bullet and sideloaded build N4F26J. I had a feeling that we were never going to get this build, or if we did it would be some time from now. Except for a driver issue which ate up a bit of time trying to figure out the sideload was pretty straightforward and easy. However, it is completely unacceptable that we have to do this in order to get the most recent update. There's no way that are large majority of the NBD91V build owner will have the ability/time to sideload the correct build. Imaging if Apple told it's users that they had to do the same thing to update their phones, that would never fly.

 

[blackhawk77#WN]

That should be fine, I went from 6.0 to a 7.1 build directly without issue.

If I'm on "V" build and want to try and sideload, would I go straight to load "J" build?