7.1.1 for the Nexus 6P on Verizon

[Bruce39]

I bought the 6P with the intention of someday possibly moving to Fi. Now on Verizon, enrolled on beta sometime in mid Nov. Received the Nov update end of Nov. I just received the Dec update today. I believe this is the final beta build of 7.1.1. The next update should be the real deal. When? have no idea,.Verizon is always the last, usually after AT&T. I have had no major problems, just minor issues. I am a very light user & what is a minor issue to me could be a big problem for a power user.

 

[ncapp11]

Followup:

The problem goes away when I turn off 4G LTE calling.

For now, I'll keep that turned off.

Thanks! My wife was having the same issue and this seems to have fixed it. Hopefully it gets corrected and she can flip back sometime soon .

 

[Lon Mok]

edit.

 

[Lon Mok]

If I make a call, and said call goes to voice mail (on the receiving end), my phone will end that call. I can call people and if they answer, call quality is great and so far I haven't seen a dropped call. It's only when the receiving caller's line goes long enough to go to voicemail. It's like this phone is timing out, rather than letting the phone continue to voice mail.

Any ideas?

That is exactly what was happening to me on my 6P on Verizon. It only happens when I'm calling T-mobile phones though. I made calls to Landlines and AT&T phone, no problem. But when I call a T-mobile phone, it goes straight to voicemail and receiver gets Missed Call. But the same T-mobile lines can call me no problem, it's only outbound calls.

Disabling the "Enhanced 4G LTE Mode" has fixed the issue for now. I was reading in news, this is new for 7.1.1, but is that feature enabled by default? Or maybe because I pulled my SIM from my Pixel over and it enabled it automatically.

 

[blackhawk77#WN]

Anyone here anything about the verizon 7.1.1 release? I did the enhanced 4G disable but it seemed like I couldn't use data and talk at the same time anymore?

 

[Mindworm]

Bump...anyone hear anything?

 

[NotFromHere]

Bump...anyone hear anything?

The latest update, N4F26J, fixes the issue.

 

[Mindworm]

If true, 7.1.1 to Verizon in the coming......week/month/????

 

[NotFromHere]

If true, 7.1.1 to Verizon in the coming......week/month/????

I gave up on waiting a long time ago. Sideload the OTA. https://developers.google.com/android/ota

 

[myriad46]

It's been out for a while, now. Have you tried pulling it from the system update screen? Try power cycling your phone. Sometimes that will push it through. Unless I was different because i was coming out of the Beta, but I got it in December and then another ota with January's security update.

 

[GPuba]

I have a 6p (Verizon) and a Pixel C. Was already on 7.1.1 with the December security patch. Left the beta group after reading the post immediately above mine, did what myriad46 recommended, and got the January security update immediately on both devices.

 

[Mindworm]

I wasn't part of the beta, hence my headaches…

 

[GPuba]

I wasn't part of the beta, hence my headaches…

I would enroll her phone in the beta program, get the 7.1.1 update and security patch, then immediately unenroll. Her phone will then be fine.

If you get the 7.1.1 update, but for some reason not the January security patch, still download the update, unenroll from the Beta program, then manually check for the January security patch. You should then receive it.

 

[Bobcat54s]

Just curious, I see lots of people enrolling in the beta program, getting the update, and then immediately unenrolling in the beta program. Why not just stay in the program?

 

[vzwuser76]

Just curious, I see lots of people enrolling in the beta program, getting the update, and then immediately unenrolling in the beta program. Why not just stay in the program?

I can't speak for everyone, but for me it was to get the update without having to wait for the que to reach me. If you're in the beta, you may get updates that really mess with your phone. On a backup that's fine, but I wouldn't want that for a daily driver.

Btw I enrolled in the beta for around 24 hours (Sunday night to Monday night). Never saw the update while I was in beta and haven't seen it show up since. I tried clearing cache partition and cycling power when I was both in and out of beta, but I'm still on 7.0.

 

[rticknor]

I'm on Verizon and my 6p is still on 7.0. My last update was December.

I just thought i'd try and force the 7.1.1 update by enrolling in the beta just long enough to install, then leave. However, I just enrolled in the beta, tried to check for an update and nothing. Is the update still not valid for Verizon 6P users?

When I updated to 7.0, I enrolled in the beta program and that same second got the OS update notification.

 

[vzwuser76]

I'm on Verizon and my 6p is still on 7.0. My last update was December.

I just thought i'd try and force the 7.1.1 update by enrolling in the beta just long enough to install, then leave. However, I just enrolled in the beta, tried to check for an update and nothing. Is the update still not valid for Verizon 6P users?

When I updated to 7.0, I enrolled in the beta program and that same second got the OS update notification.

Same same here, I'm still on the December security update even though my Pixel got it over a week ago. I talked with Google last week and they told me it would get here eventually, and that because I enrolled and unenrolled to get 7.0, that might make it take longer to get the update. Why that is I don't know.

 

[Robisan]

I'm assuming (hoping) the N4F26J 7.1.1 build for Verizon will be released as an OTA with the January security update.

 

[opuntia2]

Has anybody with VZW that has not enrolled in the beta received 7.1.1. yet? I'm fine with OTA but I'm beginning to feel like the red-headed stepchild here.

 

[Mindworm]

And rightfully so.

This has been a very non-nexus experience for those of us who don't jailbreak or fiddle and just wanted a top end pure android experience. Very frustrating.