[Essential Phone ROMs, Kernels, Recoveries, & Other] Randal84:
Tried out the latest update yesterday...

I first want to say that I always run a fresh install ( because I flash back and forth ROMs so much) Wipe everything but internal storage (dalvik cache, system, data)install ROM, install TWRP, reboot recovery, install aroma gapps (I like to pick and choose what I want installed) install Magisk, reboot to ROM.

I also as another person posted, had out the gate, Bluetooth crashes. It was intermittent for me, sometimes would happen and sometimes would be fine. After a couple reboots and app updates, it went away. So idk what the cause was but I noticed another person had Bluetooth crashes and I just wanted to say they're not alone.

I've noticed when the phone drops from LTE, to 3G, or 1X (my house and workplace are dead zones) it shows 31000 for the carrier name instead of Verizon. It's never done this before on ANY ROM I've used on ANY device I've had in the past. In fact it normally says Verizon Wireless for 1X and 3G and only Verizon for LTE. I've ran past versions of this ROM and never had this issue, nor have I had it do this on other devices in the past either, and I've been on Verizon for nearly 10 years. Reboots don't fix this issue. I also tried uninstalling and reinstalling the SIM card, with the device on, and it still does it.

The next issue and this is for me, a bigger issue, is now when I get an MMS, or more particular, a screenshot sent to me it comes in blurry. My job involves getting texts from my boss with job assignments, and on a regular basis, screenshots of info related to what I need to do, so when numbers are blurry it makes things a bit harder, so this is for me a big issue. Again this hasn't happened on past versions of this ROM, and definitely not the stock ROM. I have tried other ROMs aside AOSiP on this device and havent ran into this issue there either. The only time I ran into this issue was on my HTC 10 but every single custom ROM that wasn't Sense ROM based (stock ROM) would do it, meaning any ROM that was AOSP/Lineage based (Lineage crDroid, and yes even the HTC10 variant of AOSiP would do it) so I knew it was something specific with that device. This seems to be ROM based, and in my opinion, these issues have something to do with the update and maybe even related to the switch from Quickstep, to Lawnchair as the base Launcher.

I tend to go between this ROM and the stock ROM. As I mentioned I've tried a few others for this device but this seems to be my favorite for a custom ROM. I don't mind Lawnchair over Quickstep, because frankly I don't use Quickstep....or Lawnchair for that matter. Even on the stock ROM I dont use it Quickstep. I use CPL, but the nice thing with Lawnchair is it doesn't interfere with the additional download required to use Google discover on it. Quickstep likes to block it from being installed, so I was happy seeing that the developer used a different base Launcher other than Quickstep, but these issues seem to have came along with the change. Hoping that this can be fixed for the next update. Just wanted to outline some issues I noticed in using the latest update, great job otherwise guys, keep up the great work!