[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Team DevDigitel:
that's my reccomendation but id say if your on 5.5 a dirtyflash would be okay-ish

really as long as your on zv5 deodexed then dirty should be okay. ALL my roms wipe system and that wont change, i can afford to have those bugs come up, ive stayed away from adding the wipe user-data as some may really hate me for that lol..

but i always clean flash, as ive had bugs like yall when i dirty flash. I wipe everything, internal storage as well. I want it to be fresh and be able to see what its like for a new user just flashing my rom, and thats where i base my bug reports and issues from.

The feedback i get from here i compare to my experiences and try to re-create them.

Most of the issues really come from dirty flashes, users restoring app data from titanum etc. Restoring data with twrp overtop a clean install seems to cause apps to just close randomly at times, flashing diffrent boot.img's and flashing other mods like viper etc.

im about certain all of my builds are 100% bug free. Minus the static on boot, and the multi-user bug that shows up once you delete the lgsetupwizard.apk to get into your users profile.

outside of that the viper bugs, magisk bugs, even the static are not rom based, they are all related to outside forces and there is not software change i could make to fix those things, like magisk i ran myself crazy all weekend trying to get it fixed for you guys, i even found the old img bump stuff i used with htc and bumped the image and tried. Its very time consuming and tedious especially when i dont have the knowledge the developer who built it has, and as we all know xda can take some time to get responses etc. Im working to see about the viper4arise with the non-magisk version since its un-resolved for that build but everything else is really 100% as of now.

The boot.img is a big focus for everyone on the LS997 and other variants. Its really just figuring out what part of the debug boot.img is handling the video drivers and the static crap that comes from it, and just copying it over to the stock production image essentially.

as well as i'm still working on modding the systemui for some mods and rom additions.

The 3minit battery and signal bars is a option, but it seems theres some issues with how sprint displays its service and may need some ui edits, as well as the additional reboot options. Both are very unique to this device and uncharted even more on Android N, the way things have changed is huge, and its really shown me a ton of new things i didn't even know before. Its pushed me into compiling complete source code and actually making the edits from the post production stand point.

all in all, its going to take time for some of the not so stock stuff to work out, my test device is also my daily device, and i dont want to throw out random test builds and get back 100 different feedback's and 0 consistency, sometimes its best to just take it slow and do the testing in-house until i have a solid base and can have you guys help with finding the little more hidden issues, like the rotational bug with viper that i never had a issue with until i clean installed viper using dif. options in the aroma.

Even when you dont see me jumping on here vocally i'm always checking on the thread for issues, as well as monitoring the other devs work to see if anything will be bennificcial for us. The t-mobile dev has been a great help as well as the vzw one. And both of their roms are a huge step ahead of mine in the way of "custom" and customization. This is good and bad in my eyes, i love stock but i'm jealous of the amount of work i'm behind when it comes to the sprint users and the 100+ people we have reading up on this rom alone.

Im working with a few people from here and other devs ive met to help speed things along, as well as try and talk some other devs into getting the device and making the switch.

as well i do work with sprint and i try to give out info and help on that area as well when i can.