1. segler's Avatar
    I will wait a little longer before I sideload it, the J file.
    01-16-2017 11:57 AM
  2. Bobcat54s's Avatar
    Not me. Still waiting
    01-16-2017 01:24 PM
  3. Nate Silver's Avatar
    I've had it for a few weeks now, I believe. Also have gotten the Jan. 5 security patch.
    01-16-2017 06:23 PM
  4. blackhawk77#WN's Avatar
    I got the OTA to the "I" version and sideloaded J.
    01-17-2017 10:44 AM
  5. segler's Avatar
    Got tired of waiting, and sideloaded the J file that has the Jan 5 security update.

    That is all fine, but I'm really tired of fighting the usb drivers in recovery mode. Both of my windows machines and my linux box lose the adb connection as soon as you do "adb reboot recovery".

    It took complete uninstalls of the android sdk and reinstalls to get google usb drivers that would work. Good grief.
    01-30-2017 08:43 PM
  6. vzwuser76's Avatar
    Got tired of waiting, and sideloaded the J file that has the Jan 5 security update.

    That is all fine, but I'm really tired of fighting the usb drivers in recovery mode. Both of my windows machines and my linux box lose the adb connection as soon as you do "adb reboot recovery".

    It took complete uninstalls of the android sdk and reinstalls to get google usb drivers that would work. Good grief.
    And that's the reason I and some others aren't comfortable doing that. I know just enough about computers to be dangerous, but I wouldn't be comfortable side loading the update.

    By the way, I'm still on 7.0 and December 5 security patch. Called Google several times (at an hour+ each time) and the sessions ranged from completely useless to adequate. But they still have no answer on why I haven't gotten it and tell me to be patient. Someone was supposed to call me back the same day I called last time, that was Friday, today is Monday. Starting to lose faith in Google's stellar support. Maybe that only applies to current year hardware.
    01-31-2017 01:48 AM
  7. opuntia2's Avatar
    Got tired of waiting, and sideloaded the J file that has the Jan 5 security update.

    That is all fine, but I'm really tired of fighting the usb drivers in recovery mode. Both of my windows machines and my linux box lose the adb connection as soon as you do "adb reboot recovery".

    It took complete uninstalls of the android sdk and reinstalls to get google usb drivers that would work. Good grief.
    I also had issues with loosing the driver when in Recovery Mode and what worked for me what instead of selecting the "apply update from ADB" I wiped the cache partition and when I did that and it went back into recovery mode the drivers popped-up. And like I said in another thread, having customer sideload the build is a completely unacceptable solution to this problem. There's not a snowball's chance in hell that 99.9% of the public would want or can go thru that procedure to get the update.
    01-31-2017 09:29 AM
  8. segler's Avatar
    Interesting theory on the other thread. If you got the V update via ota, you got 7.0 with the December security update. Note that this file is not included in the ota website. Kindof an orphan.

    The theory is that google somehow does not know that your V version is available for the I or J ota to 7.1.1.

    Thus, you won't get the J update until google senses your V.

    Or google is still helping verizon sell pixels.
    01-31-2017 10:32 AM
  9. mookiekillsit's Avatar
    I haven't gotten a damn thang since the Dec security update.
    02-06-2017 03:49 PM
  10. thethruth34's Avatar
    I just got mine 20 mins ago. OtA
    02-07-2017 10:07 PM
  11. dyastrab's Avatar
    Just got mine 2 minutes ago. Not Rooted. Not in beta program either.
    02-07-2017 10:43 PM
  12. mookiekillsit's Avatar
    Just got mine as well last night.

    In Ohio FWIW
    02-08-2017 07:39 AM
  13. cridleyjr's Avatar
    I will wait a little longer before I sideload it, the J file.
    I received the update this morning 2/8. Everything is working great and the visual voicemail is also working.
    02-08-2017 01:41 PM
  14. segler's Avatar
    I got the Verizon 7.1.1 Feb ota pushed, but only after taking the bull by the horn and sideloading the Jan 7.1.1 J build.

    If you are on the Verizon 7.0.0 V build, I think you're stuck there. Google does not sense your phone because the V build is not listed on their ota webpage.
    02-08-2017 06:37 PM
  15. TrekkieMonster's Avatar
    I received the update this morning 2/8. Everything is working great and the visual voicemail is also working.
    THANK YOU for mentioning visual voicemail. I also got the 7.1.1 upgrade 2/8 followed by the February update on 2/9. I poked around a bit, but didn't notice anything different really, but I never went into the phone. I have VV now, too (about damn time - I bought the phone when it first came out.)

    Although, I had a phone app update earlier in the week, and I noticed the interface was somewhat different after that, including the in-call options. Didn't check the voicemail tab then, either, so not sure when this happened. Just glad to have VV again.

    One other thing that I mentioned in another thread. I initially had a problem with Daydream, but that resolved. However, in looking into that issue, I discovered that I can no longer find the control for Daydream. It's no longer under the Display setting in the Settings menu. Can anyone point me in the right direction? No issue, I'm more just curious where it went.
    02-11-2017 06:44 AM
LINK TO POST COPIED TO CLIPBOARD