Has anyone noticed if this update helped with the bad signal issues that seem to be Vzw specific?
I still show low signal strength, but at the same time I have a feeling that it is not accurate because I rarely ever have any actual reception issues during calls.Has anyone noticed if this update helped with the bad signal issues that seem to be Vzw specific?
Sigh... of course literally minutes after I spent a good chunk of time figuring stuff out... now to clean install for peace of mind :silly:The VZ specific "K" version is now up on Google website.....SMH
Lol I think I will install the image from Google when I get home as well.....Just becauseSigh... of course literally minutes after I spent a good chunk of time figuring stuff out... now to clean install for peace of mind :silly:
I was asking because I have a Shamu, iPhone 6 plus and my Pixel XL next to me on the desk and the other two have 3 or 4 bars of LTE and the Pixel had 1 bar of 3G.I still show low signal strength, but at the same time I have a feeling that it is not accurate because I rarely ever have any actual reception issues during calls.
I only ever have 1 or 2 bars but they are always LTEI was asking because I have a Shamu, iPhone 6 plus and my Pixel XL next to me on the desk and the other two have 3 or 4 bars of LTE and the Pixel had 1 bar of 3G.
According to someone in a different thread the radio is different than the E build. So something is different but personally I have not noticed a difference yet.Part of me wants to go directly from E to K via TWRP sideload, but at the same time there is nothing working abnormally on my phone with E and the notes for the Verizon build give no real concreate reason to update. Maybe I will get board in the next few days.
I have noticed a huge difference in Bluetooth and wifi connectivity and it looks like the only difference between Verizon's k and the other build is the radio ....From what I can tell anywayPart of me wants to go directly from E to K via TWRP sideload, but at the same time there is nothing working abnormally on my phone with E and the notes for the Verizon build give no real concreate reason to update. Maybe I will get board in the next few days.
I have noticed a huge difference in Bluetooth and wifi connectivity and it looks like the only difference between Verizon's k and the other build is the radio ....From what I can tell anyway
So I have this NHG47K build on my Pixel XL which I got from Google directly but am using on Verizon. I am locked and unrooted, though there is an option to allow OEM unlocking in developer settings. With this build, what is the process for me to unlock the bootloader, unroot, and begin flashing ROMs? I have looked at the different guides and posts, etc. but am not clear on the process for this specific build that was sent out a few days ago.
Thanks so much! I'm assuming I can ignore the bit about depixel8 for Verizon phones since I bought mine from Google and have OEM unlock in my developer options?Process is no different for this build. Follow this guide and you should be golden
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
Correct, just be aware that unlocking the bootloader will wipe your data.Thanks so much! I'm assuming I can ignore the bit about depixel8 for Verizon phones since I bought mine from Google and have OEM unlock in my developer options?
Will keep that in mind! Thanks!Correct, just be aware that unlocking the bootloader will wipe your data.
The VZ specific "K" version is now up on Google website.....SMH