yashsingh1/xdaforums huggingface dataset:
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] thiswasnttaken:
Still not touch screen on the latest builds
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] CM-Tester:
Still??? Hey Dev's.. What are you doing... We can't control the phone by brain... We need touchscreen some more years:laugh:
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] irsuv:
Does someone have the new update for 8-22 or am I missing something and it was pulled intentionally
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Omar-Avelar:
Those last versions are getting a lot of Kernel reworks by Rashed. And seems like that for most variants they create a failing situation where the touchscreen freeze at boot. so I would avoid them for now, and that might be why the got pulled?

(You could flash it and use a custom Kernel on top if you're feeling adventurous tho... if you can find those versions still)
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] irsuv:
Should have figured. Just wasn't sure. Thanks for the heads up.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] CM-Tester:
The us996 new one is still there... And as said here some posts ago, it have the issue too.

https://download.lineageos.org/us996

Thats dangerous for unskilled users
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] wargear:
Is there a fix for the touchscreen freezing issue? TWRP is frozen as well... wish I'd seen the posts before i flashed it. Stuck at setup screen so adb isn't working any ideas folks?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] mking007cn:
i use us996 and downloading is fine. if u have problem for downloading, u can download from my site:

https://resource.mking007.com/rom/us996/lineage-14.1-20170728-nightly-us996-signed.zip
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] sjavvaji:
Grab a USB-C OTG cable and use a mouse or just restore to stock and reroot if ADB is not working in TWRP.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] irsuv:
I have the h918. Do you have a download for that. I use a custom kernal anyways.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] CM-Tester:
I can't see upcomming changes for the horrible no-touch-screen-bug in the changelog of us996...

https://download.lineageos.org/us996/changes/#!

Do the dev's know this fundamental problem???

EDIT:

Btw. In the second-screen-bounty-thread they talk about something (maybe) ready thing to use....

Someone tested it already with this lineage rom here?

Any experience then, you would like to share?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] pbedard:
There working hard for us bro just wait til theu bring the awsomeness
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Omar-Avelar:
Which version of stock did you came from? I've flashed the us996 (10h-NoRoot) stock Image-dtb keeping the init ramdisk files and I can boot LineageOS with it just fine but still get that phone to only see 2 cameras instead of 3.... mmmm, there is something fishy with some of this phones not seeing the 3 cameras (and no, they are not clones)... anyone has more ideas?

The thing that I could see wrong is the following:

Working phone:

us996:/ # cat /sys/class/camsensor/sensor_name/sensor_name
FCam:hi553^^RCam:imx298_lgit^^RCam1:imx219

No rear camera working phone:

2|us996:/persist # cat /sys/class/camsensor/sensor_name/sensor_name
FCam:hi553^^RCam:^^RCam1:imx219

Any one has any idea idea how to get the camsensor device to correctly populate or why this phone is behaving like that?

That sysfs device get's populated with the following in the Kernel code:

drivers/media/platform/msm/camera_v2/sensor/msm_sensor_driver.c

#ifdef SENSOR_INFO
static ssize_t show_LGCameraSensorName(struct device *dev,struct device_attribute *attr, char *buf)
{
pr_err("show_LGCameraSensorName: rear_camera_name [%s] , front_camera_name [%s], rear2_camera_name [%s] \n", rear_sensor_name, front_sensor_name, rear2_sensor_name);
return sprintf(buf, "FCam:%s^^RCam:%s^^RCam1:%s\n", front_sensor_name, rear_sensor_name, rear2_sensor_name);
}

static DEVICE_ATTR(sensor_name, S_IRUGO, show_LGCameraSensorName, NULL);
#endif

But I still have no idea why it did not find that mx298_lgit camera on these phones...

Update:

Attaching two dmesg outputs in the relevant sections on where I believe is the problem... anyone wants to take a stab?

[ 20.552188 / 08-31 01:59:07.264][3] msm_sensor_match_id: read id: 0x0 expected id 0x298:
[ 20.552235 / 08-31 01:59:07.264][3] msm_sensor_match_id chip id 0 does not match 298
[ 20.552269 / 08-31 01:59:07.264][3] msm_sensor_check_id:1432 match id failed rc -19
[ 20.641263 / 08-31 01:59:07.354][3] msm_sensor_match_id: read id: 0x0 expected id 0x298:
[ 20.641281 / 08-31 01:59:07.354][3] msm_sensor_match_id chip id 0 does not match 298
[ 20.641293 / 08-31 01:59:07.354][3] msm_sensor_check_id:1432 match id failed rc -19
[ 20.734228 / 08-31 01:59:07.444][2] msm_sensor_match_id: read id: 0x0 expected id 0x298:
[ 20.734260 / 08-31 01:59:07.444][2] msm_sensor_match_id chip id 0 does not match 298
[ 20.734288 / 08-31 01:59:07.444][2] msm_sensor_check_id:1432 match id failed rc -19

If I reflash stock it works fine, but not with LineageOS so far... so it cannot be a bad EEPROM in the camera... mmm
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] yplim2300:
Does thi rom support H990ds model ?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] FQuimson23:
Not atm. The "All Variants" moniker is for those before the H990DS was ever rooted. Misleading now, but not before.

Currently, Lineage OS (and all other ROMs based off of AOSP and this) supports US996 (Unlocked), H918, H910, LS997, and VS997.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] WhiteWidows:
So after working on my own fixes for lineage, today I noticed a few new builds for the ls997. I decided to flash the lastest and to my horror I lost touch in both the rom and TWRP. My adb in twrp is "unauthorized" so I cant do much there.

I booted into fastboot and flashed a boot.img from a older build with working touch. Nada, no touch in either the rom or TWRP.

I dont have a type-c otg. Any other ideas? Does the otg with a mouse work in TWRP to restore a backup?

Side note, these need to be reported and taken down.

*UPDATE*

Got touch back in TWRP

Basically downloaded an older lineage build with working touch and extracted the boot.img

Booted into fastboot by holding down the volume down button then connecting the usb cable the flashed the boot.img then recovery.img.

This got me touch back in TWRP. I can write it up better if anyone wants but Im too tired now.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] toastyp:
This has been an unfortunate issue in the latest builds. The two methods I've heard that are successful is to use fastboot to reflash the recovery image, then hardware combo into twrp. Or to rerun dirty santa from step 3. Try that and let us know how it goes.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] pbedard:
Its a known issue if youve been following
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] toastyp:
I was curious if you know if flashing the werewolf kernel before booting into system fixes the broken touch screen.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] pbedard:
Yes it does
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] yplim2300:
Does this ROM support all LG V20 models? Dual and single SIM ?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] CM-Tester:
Yes, i know :) i was just wondering about meanwhile the second new nightly on the us996 (and other new nightly´s on the other variants) with the no-touch-screen-bug (Should we shorten it to "NTSB" ? :laugh:) and if the dev´s maybe don´t notice about this bug.

Puhhhh... good question... i got the 2 us996 beginning of august and then i directly started the processes about unlocking the bootloaders, twrp, and flashing (one with weta for my wife (she "loooves the second screen";)) and my one with lineage).

If i remember right, it was 10f or 10h on both, but i can´t confirm that.

What i can confirm, is, that on both phones all 3 cameras work well...

(At my one with lineage i have to use "Open Camera" because the stock lineage cam app shows the 2 rear cameras like a dark-room... Open Camera works fine).

I am still on 20170728 (the latest nightly without NTSB (no-touch-screen-bug))
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Omar-Avelar:
I have found more interesting things. The phones that do not work with the non-wide-angle lens on LineageOS are running a daemon from Qualcomm in their stock ROM's that apparently toggle on and off the camera sensors for power savings.

The daemon is called /system/bin/mm-qcamera-daemon

And as you can see on the dmesg:

And this is the thing that is missing from these phones is exactly this extra EEPROM read by subdevid to fully discover the sensor:

However I cannot seem to replicate this behaivour on stock LineageOS yet...

UPDATE: I have no idea what now... LineageOS does have the file but requires me to be root to see it

us996:/ # ls -l /system/bin/mm-qcamera-daemon
-rwxr-xr-x 1 root shell 30372 2008-12-31 19:00 /system/bin/mm-qcamera-daemon
us996:/ # ls -lZ /system/bin/mm-qcamera-daemon
-rwxr-xr-x 1 root shell u:object_r:mm-qcamerad_exec:s0 30372 2008-12-31 19:00 /system/bin/mm-qcamera-daemon

What could be different? Mmmm
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] mking007cn:
give me the build u want, i will try

BTW: I won't come here every day so maybe u need wait for a few days.

---------- Post added at 11:07 AM ---------- Previous post was at 10:31 AM ----------

I also use us996, and i use 20170728-nightly now. as i know, the early build(build in June as i test) has problem for storing video recording, but catching picture work fine for all three camera, and 20170728-nightly's build-in camara app can't connect to rear cameras(both two), but u can use third camera app such as Google Camera or Open Camera to replace it(i only test these two apps, they work fine with all three cameras).
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] CM-Tester:
Yes, i can confirm that. 20170728 works good with third party cam app. But a big problem is the non working headphone jack. Hope in a future build (without the no-touch-screen-bug) it is fixed.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Omar-Avelar:
[Background: The problem here is that the camera is not reported/initialized/discovered as part of mm-qcamera-daemon for some US996 variants that I have (that I plan to give to family), the rear camera is in no way accessible and this is not the 'black' screen bug by default]

I still have not fixed the 3 cameras on this US996 variants that I have in my possession :(.

However I believe that now I am getting close, the thing is that there are some user-space vendor libs that are missing that get the EEPROM discovery to work on these, more specifically the below one did not exist in the current LineageOS builds:

libmmcamera_brcb032gwz_s5k2p7_eeprom.so

I used the big hammer and so I have copied over a bunch of updated vendor/libmmcamera2*.so*.libraries over LineageOS and now also the binary mm-qcamera-daemon but I would need to do more testing over the weekend to get it is working :)!...

...Or do you think we could get updated prebuilts in this regard [MENTION=3322708]albinoman887[/MENTION] ? I would gladly donate! ;)
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] CM-Tester:
So today 20170901 for us996 is out... Already someone with experience?

For new/unskilful users: Be aware... The last 2 versions before this one have a failed touchscreen after flashing!

EDIT:

Is it a "feature" or a bug?

When the phone is locked, you can swipe down from the top and set wi-fi, mobile data and more on/off BEFORE you type the unlock-key...???
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Omar-Avelar:
Last update, I got it working today. I can finally give this phone to my sister! :)

I grabbed the info from https://github.com/LineageOS/android_device_lge_v20-common/blob/cm-14.1/proprietary-files.txt and extracted the missing libraries from an updated stock us996 ROM.

And also the files from /system/etc/camera/s5k2p7_chromatix.xml was missing. After doing that and setting the appropiate SELinux policies and permissions I now have the 3 cameras up and working on these 'new' US996 phones. I don't know if this applies still to other variants with users complaining that they can only switch between two cameras.

I am attaching a flashable zip of my solution if anyone's interested :cowboy: here :

flashable-us996-s5k2p7_eeprom-camera-fix.zip, and hopefuly we get this fixed/added on the prebuilts some-time soon :)

UPDATE: There is still one last problem with focusing, it kepts saying in the logcat something like:

E LGCameraParameters: int32_t qcamera::QCameraParameters::setFocusPeaking

UPDATE #2: The focusing is fixed by using some kernel changes:

I had to get all the references to lgit_s5k2p7 had to be put in place as Kernel changes that were required from LS997 sources, such as the following files

drivers/media/platform/msm/camera_v2/sensor/actuator/msm_actuator.c

drivers/media/platform/msm/camera_v2/sensor/ois/msm_ois.c

drivers/media/platform/msm/camera_v2/sensor/ois/Makefile

drivers/media/platform/msm/camera_v2/sensor/ois/lgit_s5k2p7_rohm_ois.h

drivers/media/platform/msm/camera_v2/sensor/ois/lgit_s5k2p7_rohm_ois.c
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] mking007cn:
20170728-nightly is not stable yet, it just solve the problem for storing the video recording according to 20170630-noghtly. It's very difficult to connect to my bluetooth device, and often get frozen while calling(i meet this for several times, and i have to pull out the battery so i can reboot the phone.) Not like CM, there is no stable release for us till now.I have to try and find a stable nightly version, it's real a trouble.

---------- Post added at 02:20 PM ---------- Previous post was at 02:16 PM ----------

Can u tell me witch bulid u use? i also use us996 and i have to use third-part app like Open Camera to solve this problem.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] wargear:
OK I got was able to use a USB-OTG cable and mouse to complete setup on the 822 touchscreen freeze. The mouse does NOT work in TWRP otherwise all would be fixed. However I cannot OK the ADB permission screen. I don't have one but can you use a USB hub to have both connected via different cables? It'd all fall apart like a stale cookie if so.... There's hope yet!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] sjavvaji:
Use flashify to flash TWRP 3.0.2. Touch should work in TWRP after that.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] wargear:
SUCCESS!! Touchscreen freeze FIXED! Here's what we did:

1. Boot phone with mouse attached via USB-OTG cable

2. Complete setup and enable Developer Options. In my case I'd flashed Magisk 13.3 setup Magisk Manager verified root with Terminal

3. Installed Flashify and downloaded TWRP 3.0.2-1-US996.img and flashed via Flashify

4. Rebooted into recovery TOUCHSCREEN WORKS! BAM!!

The rest is easy! A very special thanks to sjavvaji for his post above that got me rethinking the situation. I was trying to get ADB working and was not seeing the whole picture it was right in front of me! Thanks again!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] :
VS 995 Confirmed working !!! after flashing via TWRP. Absolutely Genius!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] vikashhero:
I can't remember. Does that verision of TWRP support Nougat encryption?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] CM-Tester:
Meanwhile someone with experience, about more stability and if the no-touch-screen-bug is gone away?

And what about the feature/bug on a locked phone (fast-settings accessable before unlocking the phone)?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Black6spdZ:
will we ever get to see the boot logo instead of garbage screen?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] poixninja:
That's fixed by the kernel, try something like werewolf kernel
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] bluemask69:
Please release a LOS version for H990DS , a lot of people will be grateful with you ! LOS is a fantastic rom!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] shahrukh96sk:
+1
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] sbacham:
+1
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Zacharee1:
Guys, just hit the thanks button. Don't spam +1.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] FlawlesStyle:
I don't see the H918 build failing or even building on Jenkins lately. Are we in purgatory till 15.0?

/edit: Last working build was 0718 for us, right?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Black6spdZ:
I did flash warewolf basilic 2.0 on top of latest build, still garbage screen.. So are you positive on your reply?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] poixninja:
Hm.. its how it was always fixed as far as I knew. Try another kernel? I'm using WETA, but have used werewolf with lineage and no static.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Black6spdZ:
I really want to run Lineage as my DD but withought an indicator light on this phone not having the top lcd functioning is really holding me back.. Still using stock based WETA ATM.. But i really miss my CM/Lineage rom.. Been using them since my first galaxy snd on all my tablets.. Guess times are changing
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] pbedard:
People never apreaciate anything ?? or hit thanks I do a lot
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] SICKMADE:
Guys have been pulled over by the XDA renta thread police! Whoop Whoop!!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] shivaagarwal1:
Any hope for HS990DS?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] kenbrownstone:
I've got the same issue..Flashed a ROM and Gapps then the new magik14.0 and mine won't boot and twrp is frozen screen...What should I do? The ROM won't boot just keeps bootloop and got into twrp and can't do anything.Ive got a USB OTG coming tomorrow if that will help..Saw yours would at least boot but mine won't ..Any tips on how to fix?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] pbedard:
If u can get jt to flash try to flash werewolf kernel
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] kenbrownstone:
How can I do in fastboot or adb? If possible
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] pbedard:
The way i fixed mine waw use step 3 of dirtysanta again

---------- Post added at 05:02 AM ---------- Previous post was at 05:00 AM ----------

Rename were wolf to boot2.img.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] CM-Tester:
Without complaining - just a general question: Do the dev's test a new build before they upload it to lineage-wiki (download-page)? Meanwhile 3 new nightly's on us996 with the no-touch-screen-bug directly after flashing and maybe today a new nightly with it again. More and more users download this ones and come in trouble. It is "ok" to have a non working bluetooth, headphone-jack or wi-fi-calling for example, because it is what it is... a "nightly". But a non working touchscreen should be a reason to not release/upload a nightly. - - - as i said, without complaining, because the dev's do a lot of fantastic work!!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] kenbrownstone:
Extract ? No right
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] WhiteWidows:
No it's a build bot. If you go to the device tree no one is doing **** for these devices. Someone mucked with the kernel a few builds ago that trashed touch screen among other things. I've sent multiple messages over to the Los team they need to pull these builds with no response. The maintainer is not doing anything either. So.my advise is stay away from all Los builds for all v20s.

That being said I build my own for the ls997. Fixed boot, fixed Bluetooth, fixed cdma ril issues, no touchscreen issues, working on other random bugs as well. But I'm not sharing anything until the Los team or the maintainer answers me back. It's condemable they let these builds into the wild yet disregard reports that leave a unusable device. Other unnamed devs I tried to reach out to attacked me for being demanding. If the maintainer has abandoned the device they need to let someone else step up.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] CM-Tester:
Well THAT change a lot... That is as bad, as it could be.

EDIT:

For new/fresh/unskilled users: DO ACTUALLY NOT USE A NIGHTLY FOR THE US996 AFTER 20170728,

IF YOU WOULD NOT LIKE TO COME IN TROUBLE WITH A NON WORKING TOUCHSCREEN

(skilled users are competent to circumstantial flash another kernel to fix the non working touchscreen,

but be warned,- it is not easy, after you got this bug !!!)

[MENTION=1923447]WhiteWidows[/MENTION]:

Thanks for this very usefull information

EDIT-2:

Is there someone, who had actually build his own NEW(-est) build for the us996 with fixed headphone-jack, bluetooth, touch-screen etc.,

who maybe would like to share it after a pm or maybe for all of us ?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] kenbrownstone:
I still couldn't get my screen fixed..Tried fastboot and other stuff. Hell I've never had a issue like this and been flashing since motorzr..I might try another computer .Maybe that will help..But by what I've seen I need to flash another kernel..My windows 10 just got a update and now it pulls up PowerShell instead of command prompt could that be a issue.Ive noticed they are a little different..
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] fr4nk1yn:
Is touchscreen issue only on us996?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] kenbrownstone:
Mine is h918 T-Mobile
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] The_Keeper86:
The H918 apparently has this issue too. I use RR and am on the July 8 build. Hopefully this will be fixed.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] mking007cn:
Thank you for noticafication, but as i know, 20170728-night also have many bug. as my experience， this nightly-build have problem with build-in camera app, bluetooth connection problem. and another trouble thing is the phone will get "randomly frozen" while calling.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Omar-Avelar:
Guys, if you want to know if the "touch screen" bug is still present in the nightlies without testing. Please check:

https://www.cmxlog.com/14.1/us996/

Or the equivalent. The problem lies in the Kernel changes by Rashed and I am sure he is still debugging. So as long as for the nightly does not state any changes in "android_kernel_lge_msm8996" then it is bound to have the bug. Keep monitoring.

On a side note. as we are all waiting for a bunch of bugs to be fixed and people keep on using the 07-28 build. I have created a flashable zip that fixes the built-in Snap Camera [see attached].