[LG V20 Guides, News, & Discussion] xdav20:
My first post after 8 years

Hello again, after more than eight years of being away from XDA community I'm back. I hope I don't have to run again, health issues. Registered a new id as I no longer have the old one.

I've been following this thread, as well as others, since bought my LG V20 H990DS just over a month ago. I had to learn everything all over again but now I'm glad I know far more than before from all the knowledge is being shared by everyone, thank you all.

I own one LG G Pro 2 D838 and one LG G Pad 8.3 V500 variants since 2014. I am somewhat familiar with LG ROMs. With the knowledge I gained in LG V20 threads alone I managed to go further and remove rctd, lg backup, and fota from my D838 and, for now, the rctd from V500 which was more difficult for me.

I have successfully rooted my H990DS, thanks to all developers involved. Since I have purchased my H990DS, I only used it to flash all variant kernels, to backup, reconfigure, and test things out. I have also removed LG Backup and ccmd from V20 ramdisk successfully. Since we can flash the boot partition directly from twrp it was very straight forward, once figured everything out. My LG D838 remains my primary device until I can feel confident I have a solid setup like I have with D838 before switching to V20. D838 (SD800) is one of LG's best phones ever and after three years and with newly applied tweaks I did to it I have never felt I'm using a slow/old phone. I had to upgrade to a newer phone because I do not like non-stock custom ROMs and nougat which is not available for my D838, nor MM, is the most future proof Android version for the next four years or so and like many of you choosing V20 for the removable battery for me was a must have feature too. I think I have 8 or 9 original v20 batteries now, just to be on the safe side. I can assure you, I equally spoilt my D838 with the same level of attention too. Still have three new batteries to go through.

Naturally, for my very first post I had to cover few things before getting to the actual point of this post. I have the camera issue as well but I have another problem that is far more annoying to me and that is the USB OTG issues. Just before I get to the USB issues, Device Info HW app lists 4 supported/drivers/items/lens/sensors after flashing jx's kernel. These are; hi553, imx219, imx298, and s5k2p7. Having read the entire thread, I do not recall anyone mentioned 4 items being listed. Also, since 'imx' prefix is usually used by Sony, why do I have all the camera issues too? I assumed Samsung lenses are the culprits.

This USB problem has been mentioned before in this thread but no one took it seriously. Here how things have started acting up. Since I was on Android Kitkat version for the most part of the past three years I had to format all my USB sticks to Fat32. When I noticed V20 supported exfat and when upgraded my D838 and V500 to Android LP, a month ago, which supported exfat too then I decided to adopt exfat format and reformatted all my USB drives and SD Cards to exfat.

I believe, not after rooting but after flashing one of the kernels that was released at later date in this thread messed up everything. I had to reformat everything back to Fat32 as V20 no longer could recognise anything with exFat format. This problem has persisted no matter what kernel I flashed after this issue came to an existence. I believe jx's variants are the worst because if I plugin a Fat32 formatted USB drive and reject it and plug it back again then I have to pull the battery out as I get a type of Blue (yellow, I think) Screen of Death. So, after each use of USB I have to reboot which after rooting my V20 has the longest boot time of any device or pcs I own. Furthermore, with my infected V20 when I reject the Lexar S75 128GB, formatted Fat32, when I plug it to my notebook, every time, Win7 needs to scan it, but not with my other USB stick which is 64GB.

Today, my second LG V20 H990DS has arrived and right away I tested an exfat USB drive (reformatted the same Lexar S75) and I never got promoted to format the disk and after rejecting it and plugging it back to a Win7 notebook no fix scan was promoted either. With previously reported USB OTG problem in this thread and many about charging issues, I can confirm a bad seed resides in all kernels (or most) and would like to request the developers to check to see what is missing from stock kernels that introduces the mentioned problems please.

If there was a single bad kernel among all the released kernels, to this date, then reflashing a good kernel cannot fix (or reverse) the problem entirely, that is why I used the word infected. In such case, the problem needs to be identified so a solution can be provided.

I'm not going to modify anything on my 2nd V20 for comparison and testing. The ROM version is 10e which is higher than what I bought just over a month ago. Let me know if I can be of any help.