Hook

Something odd going on. I'm on the suspended update (20200304) and I still have the issue, It was solved by the nice little volume control app mentioned by @FlyingAntero above.

Yes, to be clear, priority or not, I am simply requesting that LOS be able to do what stock can do. Verizon works on stock using LTE only. It allows the VoLTE and Voice over Wifi switches to be turned on, which appears to be all that is needed for Verizon to work. The user still has to use the mule workaround to get a SIM provisioned for VoLTE, but that's on the user. It works in stock.

Unless they are practicing safe social distancing. 😜

Sheesh. Look, I understand not wanting to wait any longer and deciding to get something else (no, actually, I'm lying, this phone is so awesome, I can't imagine ever getting something else, but the frustration with waiting I understand 😉), but why do you have to throw a hissy fit on your way out the door. Why not just, "Okay, I'm tired of waiting so I'm moving on. Good luck to the rest of you."

You've already received some answers. For me, it's just a matter of convenience. Verizon has hands down the best coverage in our area and anywhere I have gone, but I don't travel much. My wife is on Verizon with her Pixel 2XL and has no intention of changing. Both of us have Prepay plans, but because the are managed together, we save $10 a month. It seems silly that I can't use what the phone is equipped for. On the other hand, I knew this was a possibility. I knew having the radios was no guarantee, I'm familiar with the Verizon's behavior. I could go get an AT&T prepay accoun

Understood. Makes sense.

Do we have a boot image for the 20200306 update yet that can be provided for Magisk to patch?

Well, I went ahead and tried. I'm now thinking this was reported before, but can't remember if it was for Verizon on LOS. I can confirm that Verizon will nor work on LOS. LOS fails to recognize that the SIM is provisioned for VoLTE and all the switched that provision it for the phone on the phone menu (*#*#4636#*#*) sta grayed out no matter whatother settings you play around with. I sure hope there is a solution down the road. Guess it's back to stock for me. 😉

I just got my shipment of 1600 black dots from the UK. It's 8 sheets of 200 dots. They look perfect for the Pro1 screw covers. Whats more, I believe cutting one dot in half would work for the keyboard corners. Lol. 1600. 😄 😎

So, I was planning to jump to LOS Test 11 when I took a look at the issue tracker and saw that it is still being reported as not working with Verizon. That would be a deal breaker for me and I would have to very quickly wipe and return to stock. While part of me say "Aw, go ahead, try it. Maybe it will work for you 😅" most of me is hesitant to go through all of that just for a short test. @tdm What is the status of this. Will it have to get worked out before it becomes official? Is the path to solving it understood? What is your confidence this can be solved soon? This isn't a d

My instructions (to myself) worked perfectly. Titanium Backup even found the backup folder it used before on my SD card the last time I was rooted. Will do a backup to the cloud and play around a bit, and work on data backups (personal files) getting ready for the LOS wipe. Thanks all, especially @david

Thanks for the heads up. Over my head and looks suspiciously like Google doing the M$ thing of making it harder and harder of letting users have control. May be inevitable eventually, but I have mostly old apps and TB has never let me down. Don't so Whatsapp or Viber, but I know that backup doesn't do media for apps. If I run into problems with TB, I'll look at Swift.

Split apks? What is that? I always back up Titanium to SD card and cloud, And, yes, I do know that going to LOS will wipe userdata. Not familiar with Swift backup, but don't like the sound of a program wiping *my* data when you uninstall it.

I am going to root stock using Magisk in order to do a Titanium Backup before moving to LOS. Sorry for being pedantic—I did do this once before—and, since I expect to go to LOS almost immediately, I don't really need to care about being able to unroot for an OTA. However, since I am putting together several sources in this thread, I want to make sure I have sorted things out correctly. I'm pretty sure I have but I really need things to be explicit. So here is what I plan to do. Confirmations and corrections both appreciated. 1) Install Magisk Manager (I have downloaded the most recent,

Also, had you previously installed the 20200304 update? Not being offered anything here and that could be a difference.

Thank you for everything you are doing. I'm probably going to root stock so I can do a Titanium backup and then wipe and try Lineage. It is amazing to have this kind of support for our phones and your hard work is so appreciated. I also appreciate that you are going to put together an AOKP build. I can't wait. But, for now, take care and do what you need to do for your family. I have family in Seattle myself. I just sent you a six pack to get you though. 😉

As you can see from @puppymang above, this happened to him/her and, from my reply to him/her, that it happened once to me. Unfortunately, if they found a solution they didn't report it. Mine was solved after I had to reflash the factory image and therefore I have no idea what solved it, but it hasn't been back since. At the time, I assumed it might have been the January OTA which I took when my phone was reflashed. I assume, since you were checking your SMSC, that you checked to see that your provisioning switches were all on. The funny thing about the SMSC number is mine doesn't sho

Edge Block using Tasker in this post is the best solution I have found. Works really well. An App called Edge Null also works, but not quite as well.

Just to point out, my method works for opening either in portrait or landscape. I do both. And it works fine one-handed.

Based on even what we have here in the USA, assuming they need to vpn to a server or set of servers, the proper security protocols to allow this may never have been set up if working from home wasn't common before this.

Wow! As a former Dirty Unicorns user, I am excited by the possibility of AOKP. Sheesh, now I'll have to start sending you even more beers! 😉

Ah, okay. Must be it... I'm set to swipe. I thought it might be bootloader because I think one of my Nexus phones used a lock icon for the bootloader, but it showed before the lock screen.

Just wanted to point out, I think there IS a bootloader lock status indicator at boot, but it's subtle. When I boot, at the bottom of the lockscreen (after all the logos) is a small (really small) padlock. On mine, which has been unlocked since I received it as it came that way, it shows the lock open (A tiny space between the left side of the bar and the lock). I can't say I know having never been locked, but I would assume that if you are locked, the loop is closed.

Yeah, I think I finally can see the end to end steps and thus will think about rooting this week-end. Since I don't see the boot.img file in the zip (I updated manually), I'd ppreciate the file. Or tell me how to extract it. BTW, are we sure the boot.img changed from January? And, @EskeRahn really confused me, moving all this in the middle of my composing this post... 😉

My manual update got stuck at 43% and then it rebooted my phone spontaneously, but all evidence says I got the full update. 😉 🙄