[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Redline:
Testing Different Scenarios

So after sitting down with some more time free, I decided to give things another go after hearing [MENTION=3658695]dilaboni[/MENTION] 's experience, in the hopes that if there's any underlying issue it might help [MENTION=2881807]x86cpu[/MENTION] narrow it down. This post may turn out fairly large.

Here's how it went trying various different scenarios.

I'm using the same beta release version of the ROM, and I'm testing with OpenGapps 24 November 2018.

"Does it work: Yes" is defined as not having the shutdown problem after booting into the OS and core functions work, including WiFi/Calls/Data/Camera/etc. If it's not listed as NOT working in post #2, it functions under the "Yes" condition.

If I also have time to go into settings, enable USB debugging and get my PC to recognise it, I'm considering it still working. This is still after going through all the initial setup processes.

These scenarios also imply everything "sticks" and still works after a reboot.

"Does it work: No" is defined as having the shutdown issue or any other problem that effectively makes the device un-usuable before or after booting into the OS.

Tested on my H990DS with a Samsung 64GB EVO+ microSD card (soon to be a 128GB EVO+) and a single 4G LTE-enabled SIM in Australia. Stock ROM kernel is used as there are no other options.

Clean Flash Scenarios

Clean flash of the ROM, GAPPS Pico and Magisk 17.3 WITH a SIM - Does it work? Yes. Setup passes, normal device behaviour ensues. Pico was suggested by [MENTION=3658695]dilaboni[/MENTION]

Clean flash of the ROM, GAPPS Nano and Magisk 17.3 WITH a SIM - Does it work? Yes. Setup passes, normal device behaviour ensues. Exactly the same as above, just with more included GAPPS from Nano vs Pico.

Clean flash of the ROM, GAPPS Aroma (importing my selected GAPPS options from 15.1) and Magisk 17.3 WITH a SIM - Does it work? Yes. Setup passes, normal device behaviour ensues. Boot takes a little longer with my (personal) heavy GAPPS loadout.

Notes:

Setup crashes a couple times on the "checking for updates" step but recovered and continued fine. You can tap out of the "setup keeps closing" dialogue and it will refresh and continue.

After flashing all of the above in each scenario and rebooting to system from TWRP, the device gets to the LG screen, powers off after a few seconds and then powers on again from the "your device is corrupt" screen. After this, the device boots normally. Initial boot is just under 10 minutes with the ROM, GAPPS and Magisk.

I did not test without flashing Magisk. I'm going to assume that this would also work OK, as there's even less risk involved if you don't have Magisk modifying the stock boot image and potentially causing issues. This did NOT happen in my case though.

Privacy guard (shown as "Trust") appears to function. As does root via Magisk.

Camera works, but it appears it's unable to focus, automatically or manually.

Bluetooth does not

appear

to work (as stated by x86) at all. My Huawei Watch 2 is unable to pickup the phone, and the phone cannot see any other Bluetooth devices.

Summary: If you don't need anything that isn't working, i.e Bluetooth, Camera auto-focus and NFC (un-tested by myself but is said to not be working) then you can probably run this ROM

cautiously

as a daily-driver. I don't doubt that Bluetooth and NFC among other things will be added to work in future builds that can be dirty-flashed over this one.

Dirty Flash Scenarios (the most applicable ones)

Dirty flash of the ROM over 15.1 with GAPPS Aroma (previous apps installed when I clean flashed 15.1) and Magisk 17.3 WITHOUT a SIM installed - Does it work? Yes. All phone functions that worked on 15.1 work on 16.0. Aside from the Fingerprints issue with wiping on reboot, and NFC (which I'm unable to test).

Same as above WITH a SIM installed - Does it work? No. Immediate shutdown on boot as already reported. This makes it pretty explanatory what the problem appears to be.

Same as above WITH a SIM installed in the SECONDARY SIM slot - Does it work? No. Tested this for the hell of it.

Dirty flash of the ROM over 15.1 with GAPPS Aroma and Magisk 17.3 WITH a SIM - Does it work? No.

Dirty flash of the ROM over 15.1 with GAPPS Pico and Magisk 17.3 WITH a SIM - Does it work? No.

Dirty flash of the ROM over 15.1 with GAPPS Nano and Magisk 17.3 WITH a SIM- Does it work? No.

Notes:

The issue with "the device gets to the LG screen, powers off after a few seconds and then powers on again from the "your device is corrupt" screen. After this, the device boots normally." is not present with dirty flashing.

I did not test without flashing Magisk. I'm going to assume that this would also work OK, as there's even less risk involved if you don't have Magisk modifying the stock boot image and potentially causing issues. This did NOT happen in my case though.

Privacy guard (shown as "Trust") appears to function with Dirty flashing too. As does root via Magisk.

Camera works, but it appears it's unable to focus, automatically or manually. Same as clean flash.

Bluetooth works, as stated only under dirty flash conditions by x86.

On my LineageOS 15.1 setup, I have Magisk, Xposed, Gamma kernel and GAPPS AROMA on top of the ROM install. Uninstallers for Magisk & Xposed were flashed before attempting the Dirty scenarios, mainly to eliminate Xposed as a potential issue. This means the total flash steps for the Dirty scenarios consist of restoring my 15.1 backup, uninstalling Xposed, Uninstalling Magisk, re-flashing 15.1 to eliminate Gamma kernel, flashing 16.0 and flashing Magisk 17.3

Hopefully these scenarios are of help to anyone wondering what does and doesn't appear to work with the build we have, and hopefully it helps [MENTION=2881807]x86cpu[/MENTION] narrow down any potential issues being caused.

As a result of testing, I am deciding to stick with 15.1 and wait for the issues with Bluetooth and the Camera to be ironed out so I can then bite the bullet and start completely clean with 16.0. This is only because Bluetooth is how my watch communicates with my phone.

It's safe to assume that dirty flashing to 16.0 is perfectly fine, but I don't like to risk apps not being updated properly for different API versions (Google for example has different versions of Maps, Google Play Services and other things depending on your API level).