[LG V20 Guides, News, & Discussion] Tần Quảng:
IMPORTANT: This topic is not general or critical of LineageOS 19+. Simply an objective "experience" of mine, I am not sure if you will get the same error, read, think, consider carefully before upgrading to LineageOS 19+!

I used an LG V20-F800K variant. After following the instructions on the forum, I successfully rooted and installed LineageOS. The first version of LineageOS that I installed and used was LineageOS 18.1 for VS995 variant.

I continued to use LineageOS 18.1 for a long time until recently, I was curious so I switched to LineageOS 20.0. And this is my biggest mistake!

LineageOS 20.0 (Android 13) is fundamentally not too different from LineageOS 19.1 (Android 12L). The user interface on LineageOS 20.0 is identical to LineageOS 19.1, "improvements" like battery saving/optimization (as Google provides) I didn't feel but instead, I felt it drained more battery than on LineageOS 18.1!

That's not all, since LineageOS 19.1 to 20.0, there is an "error" occurring: All data/applications installed in the previous session will corrupted if your device unfortunately crashes. One of the most basic errors an application will encounter is java.lang.UnsatisfiedLinkError or damaged data.

I tried to find out why, and surprisingly, it was because the files (data/libraries) of the corrupted applications would be "trimmed" to 0B(yte)!

I tried to reproduce the error as follows: Try installing / downloading any application / file -> once done, remove the battery of the device (simulating that the device suddenly crashes to power) -> restart the device -> the previously installed / downloaded application / file will have the error that I said above.

Of course, if you actively restart the device this error will not happen. But as long as you accidentally cause the device to suddenly power down, this error will definitely occur (this is a "dangerous" error, when the battery capacity of the LG V20 is quite low, unexpected power failures will happen quite often). This is a serious bug that never appeared on LineageOS 18.1 (or at least I didn't encounter it during use).

Another minor bug I encountered on LineageOS 20.0 was that some apps (like WeChat, AliPay, X (Twitter), Wattpad,...) would run automatically after installation (even if you didn't open them) and every time the device restarted (even if you forced them to stop). I'm not sure if this error appears on LineageOS 19.1 because I haven't tried installing those apps.

Even if you do perform a reboot actively, but since Android 12, there is an option called "Remove permission and free up space", all apps that enable this option will increase the probability of encountering data corruption errors (the app's data file is "trimmed" to 0B) higher than apps that do not enable this option. As far as I know, this option will revoke permissions, delete temporary data files if the application after a long time does not use it. But for some reason, it worked "beyond my expectations", directly damaging the user's data!

After a period of use with a very bad experience on the 2 latest versions of LineageOS. I decided to go back to LineageOS 18.1. But, (by the time this topic is written) you can only use old builds of LineageOS 18.1 that were previously released, if you want to rebuild LineageOS 18.1 yourself to apply the latest changes after the last build is released, the build will be successful, flash ROM also succeeds but your device will hang at the boot animation screen. I also tried asking about this bug on LineageOS's Discord channel, also found the cause but no one fixed it!

I haven't used LineageOS 17 yet, so I don't know if it has the same error. But I'm currently building LineageOS 17 and will test it out soon.

Those are some of the experiences and errors I encountered after upgrading to LineageOS 19.1 and 20.0. So hopefully through this topic, you will have an objective view of LineageOS 19.1 and 20.0, from which to consider carefully before upgrading, especially with Korean variants because I think the probability of encountering the same error as mine will be very high!