[LG V20 Guides, News, & Discussion] emdroidle:
There have been some reports of this. One of the favored modifications has been to allow overriding whatever checks there are and forcibly enabling fast charging. I've been wondering about the situation, but didn't seem like an urgent issue (yet).

There seem to be a few KDZ files where you must use "upgrade" instead of "refurbish". If it wants to use the other choice, no problem just go for it.

The regions are interchangeable. Most H990* KDZ files, no matter the suffix, are compatible with most H990* devices. I strongly suspect KDZ files for dual-SIM devices will work on single-SIM devices; I've got no idea of the reverse.

The crucial factor is the release date of the KDZ, not the version. For instance the Taiwan 10c KDZ is December 14, just early enough; no 10d has been found, but that would likely be January or later and not work. Generally the 4 digits near the end of the KDZ filename are a date, anything 11xx (November) or 12xx (December) will work.

Depends upon how you define "better". The two particularly notable factors are amount of bloatware and VoLTE support. The SEA/SG/Singapore KDZs are notable for good VoLTE, but horrific amounts of bloatware. The TWN/TW/Taiwan KDZs have little bloatware, but are bad for VoLTE. I suspect the AUS/AU/Australia KDZs may be the best tradeoff. This is partially guesswork, checking yourself may get better knowledge if VoLTE is crucial to you.

Get to the Hidden Menu (go into dialer and dial *#546368#*990#) -> SVC -> Version Info, near the bottom. So far nothing other than 0 has been observed.

The crucial commits are:

ead87a5766be6cc0ff47b25907b3f5847c932324

5a28db6e5c6c9fd453bcd274f5374d0098adbd52

fdc0801640b8bb76431fd9cd79305b34b68172a9

c732e47e3e100f767c294df66eb85769ffa40b6f

88eb120f89ee9edbbfe32ad1a77414d3243a0b3a

df7a6e40b8b65b6e3c7b4a1f07e5d0b9b52955d4

5c47bad356de18cdfcfbf500ef8b5b124cb0819a

90d561544f05826c23a1dba5425002dc0ca19a6e

Those files may fix the camera, but they don't look like a good fix. I'm left suspecting replacing a few of those files directly from LG's kernel source will be a better solution. Some portions looked like they came from older versions of those source files (they were missing some extra checks that had been added later). There were a bunch of refinements I was adding as I was going through them. Hopefully I'll have my own, better variant soon. :)

I'm uploading a temporary patch version of v0.2. I've added in all except one of the publicly available updates. The missing one is the EXT4 data leak after crash, sounds pretty minor since you need the device to crash in order to take advantage. I'm a bit doubtful of being able to control what data leaks in this situation. Additionally it reads like you need a bunch of further kernel updates before the data leak can actually occur (this is based on 3.18, while the problem was found in 4.7).

Alas the 802.11 ("Wifi") and Bluetooth fixes are unavailable to unregistered developers/maintainers for a week. I should be building v0.2.1, which will have those fixes around the 19th. Depending upon how paranoid you are, you may want the first batch immediately.

Alert! A stupid error was made during packaging this kernel. You can either get the updated kernel from the first page, or else simply mount /system read-write and run the command `mv /system/lib/modules/exfat.ko /system/lib/modules/texfat.ko`. Yes even though I know the process, I make this goof too.