yashsingh1/xdaforums huggingface dataset:
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] x86cpu:
Does this only fix the white-balance issue with the Snap Camera? That's the only issue I knew about with it on the v20's. If this is fixed, is there a gerrit commit pushed up so we can have it fixed in LOS?

---------- Post added at 14:22 ---------- Previous post was at 14:18 ----------

I build my own us996 and have the bluetooth "mostly" fixed. (A whole lot better than previously.) The only thing not fixed still is the headphone-jack. Now... my build also is the same as LOS, but does not have any touch-screen issues. Has anyone really tested the LOS us996 build to see if that one has the touch screen bug? (h918 was pulled due to touch screen issues) My unofficial one so far (lack of headphone jack) works fine for daily driver. The only bluetooth issue is sometimes I have to turn it off/on after reboot to connect to my car the 1st time, after that's fine until a reboot. I also had a 50% battery bug (battery reported 50% all the time and would not charge either). I have resolved that one. But did anyone else using the us996 have that issue?

---------- Post added at 14:25 ---------- Previous post was at 14:22 ----------

If you've fixed some, do you know the gerrit commit #'s? I'd be interested in getting some fixed in my own us996 builds. Have you happened to track down how to fix the headphone jack?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] WhiteWidows:
I'll pm you Sunday. I'm at the Cubs game tonight but I'll share what I have tomorrow
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] mking007cn:
Nice to see that, if possible, can you give your build for downloading? If you need, i can give you a ftp account to upload it to my site. Thank you.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] x86cpu:
I could, however I do think that is does as well have the touch-screen bug... BUT I might know why that is. Hopefully knowing why might lead to fixing it. I am not opposed to sharing it, it is an unofficial one after all. I just want to make sure that if it really does not have that same issue so I'm not causing others similar problems. I hope to test this week to be able to track it down.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] kenbrownstone:
Does this build have the touch screen freeze

---------- Post added at 12:24 PM ---------- Previous post was at 12:20 PM ----------

Did u get urs fixed? If so how ? I've flashed werewolf but still nothing
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] The_Keeper86:
The July 8th build of RR doesn't have this issue at least not for me know the H918.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] alexp1289:
Hey guys I'm looking to buy a us996 to use on Verizon is anybody using that phone and does data work well on Verizon? Are there any major bugs that maybe I should wait before buying the us996?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] fr4nk1yn:
I'm guessing I'm the only one with a Vs995 that has no Wi-Fi?

I also had to restore EFS to get past setup connectivity.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Ryuk359:
As someone who bought this phone with misplaced enthusiasm on release, I'll give this advice. Get some other phone. Development is dropping off for this one. I'm stuck with it for a while or I'd do the same. Its a decent phone but there are better ones with better development ongoing. The few good devs we do have are jumping ship as we speak.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] alexp1289:
What phone we're you thinking of getting I'm not sure I want a phone that I can't easily replace the battery in. I hate the idea of a sealed in battery.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] kenbrownstone:
I know.Cant wait til I have cash to do so..I'm sitting here with a phone that the touch screen doesn't work..because of flashing a rom... lol..fml
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Ryuk359:
That's a worthy trade in my opinion if the phone will completely work vs broken features. And this phone has many gremlins. Bluetooth, touchscreen, signal problems, etc. I haven't looked at new phones lately as I've still got a little under a year before I can upgrade. If I had to buy a used phone or byod I'd get a HTC or something with good development. Probably what I'm going with next go around. Check the forums and see what tickles your fancy. Lg did good with the g4 to me. I had one before this phone and I loved it. Miss it every day. Roms were excellent. I think dev is still good last I checked. But I won't be going lg again. Not Samsung either. Had an s7 shortly. Screw knox and its damn root flag. Like I said just browse XDA a little and do not buy this phone. You will without a doubt regret it.

---------- Post added at 03:16 AM ---------- Previous post was at 03:15 AM ----------

You and me both brother. Cash is short but if there's ever a little extra I'm outta this piece.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] CM-Tester:
So at the moment there are still users with no touchscreen and flashing another kernel (if ever possible to everyone) would not help everyone. And as said last posts ago, the dev's are out of this phone and a build-bot throws out a new bad weekly WITH THE DAMN NO-TOUCH-SCREEN-BUG every week...

What a #*^_.... situation.

Frustrating.

And yet the v20 have the potential to be a note-3-killer (especially with the LOS-support and because of the same size WITH a replaceable battery)....

Edit:

Should we start a petition or should we all write emails to the los-team to bring the good development back and keep the v20 alive?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] kenbrownstone:
GUYS I GOT MINE FIXED

---------- Post added at 12:50 AM ---------- Previous post was at 12:48 AM ----------

IF YOU HAVE A BACKUP IN TWRP OF A STOCK ROM OR MAYBE A CUSTOM(I USED A STOCK MEGA ROM) I USED ADB SHELL TO RESTORE THAT BACKUP AND BOOOOOOOOOOOOOM..Got my device back..Thank you LORD JUESUS..After 48 actual hours of trying..

---------- Post added at 01:16 AM ---------- Previous post was at 12:50 AM ----------

I DID THIS WHILE HOOKED UP TO TWRP...NEVER KNEW YOU COULD DO THAT..TWRP restore (file name)...it's just the backups name you need not TWRP-BACKUPS-LG BLAH BLAH/...REMEMBER TO ADB DEVICES(to make sure your device is noticed) ..THEN ADB SHELL..THEN twrp restore (file name)
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] SketchyStunts:
That's good to know. I flashed the latest Sprint build last night & got everything working including ARISE. Luckily I'm not being effected my the touch screen bug.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] x86cpu:
I did a clean fresh build and hit the no-touch bug. I got back by flashing twrp 3.0.2 (vs 3.1.1). Then had touch in twrp. Flashed older rom and was ok. I got a dmesg and logcat and trying to determine what caused it. But I do know if I keep by build area with some older files in the /system area it does boot with touch. So at this point I'd rather not release the us996 that I have since I know that it may cause the issue still (sorry). I might if I can verfy it does not, but.... going OFFICAL to UNOFFICAL is a data wipe (and back to OFFICAL). I might get it once the Sep security patches are in.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Omar-Avelar:
What? Everyone else has the issue where the Snap camera has a Shutter speed of 1/4000 without being set automatically on 'known' working builds such as lineage-14.1-20170728-nightly-us996-signed.zip. That's why I posted an older version of Snap.apk to flash so that they can still use the camera and not show 'dark' on boot.

There are other bugs (for people who can only view 2 cameras and not 3) such as the libraries and Kernel not being updated to support the s5k2p7 camera sensor which I have fixed on branch android_kernel_lge_msm8996/cm-14.1_20170811 but don't know how to get them pushed into gerrit yet. I would rather wait for the Kernel changes till [MENTION=4662457]Rashed97[/MENTION] sorts out the touch screen issue tho.

Seems like the new version of Snap.apk which is supposed to have way more features from LGE libraries (such as chrome flash) included does not work well in those 'older' builds yet but maybe it works for you on your custom build at the moment.

Now that you mention that your dirty flashed system partition works with the touch issue... it is most likely that the new Kernel is expecting touch-screen firmware to be placed somewhere else but it is not finding it... and somehow the touch-screen microcontroller/pmic ends up in a state where it cannot be used until a stock boot.img is flashed so that it resets back.

I can see that the us996 defconfigs are using

CONFIG_LGE_TOUCH_FW_PATH="touch/elsa"

However that path might be bogus now on how things got changed and or with the recent Kernel updated. Specifically since Kernel got updated a lot when things broke down.... I will explore on that route later during the day
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] x86cpu:
The camera works find for me...except it's all black. But not fully, it's the white balance that's off, if I aim it at a light I can faintly see it.

It's not only dirty flash system...it's the entire $OUT dir. So if an object is already cache and built, the build considers that fine and does not re-build it. $OUT is usually "~/android/lineage/out/target/product/us996" I moved that entire directory to another to force the build to re-build everything.... that caused the no-touch bug.

That CONFIG_LGE_TOUCH_FW_PATH appears to be the same in the new kernel ... but some of the files do get rebuilt differently since I cleaned things out, so not sure how they are created:

Binary files us996.NO_TOUCH//obj/KERNEL_OBJ/firmware/touch/elsa/L1L52P1_1_08.img and us996/obj/KERNEL_OBJ/firmware/touch/elsa/L1L52P1_1_08.img differ
Binary files us996.NO_TOUCH//obj/KERNEL_OBJ/firmware/touch/elsa/L1L52P1_1_08.img.gen.o and us996/obj/KERNEL_OBJ/firmware/touch/elsa/L1L52P1_1_08.img.gen.o differ
Binary files us996.NO_TOUCH//obj/KERNEL_OBJ/firmware/touch/elsa/L1L52P1_1_13.img and us996/obj/KERNEL_OBJ/firmware/touch/elsa/L1L52P1_1_13.img differ
Binary files us996.NO_TOUCH//obj/KERNEL_OBJ/firmware/touch/elsa/L1L52P1_1_13.img.gen.o and us996/obj/KERNEL_OBJ/firmware/touch/elsa/L1L52P1_1_13.img.gen.o differ
Binary files us996.NO_TOUCH//obj/KERNEL_OBJ/firmware/touch/elsa/L1L57P1_1_10.img and us996/obj/KERNEL_OBJ/firmware/touch/elsa/L1L57P1_1_10.img differ
Binary files us996.NO_TOUCH//obj/KERNEL_OBJ/firmware/touch/elsa/L1L57P1_1_10.img.gen.o and us996/obj/KERNEL_OBJ/firmware/touch/elsa/L1L57P1_1_10.img.gen.o differ
Binary files us996.NO_TOUCH//obj/KERNEL_OBJ/firmware/touch/elsa/L1L57P1_1_13.img and us996/obj/KERNEL_OBJ/firmware/touch/elsa/L1L57P1_1_13.img differ
Binary files us996.NO_TOUCH//obj/KERNEL_OBJ/firmware/touch/elsa/L1L57P1_1_13.img.gen.o and us996/obj/KERNEL_OBJ/firmware/touch/elsa/L1L57P1_1_13.img.gen.o differ

(us996 dir works). Files are the same size, just different .. however some are the same. The ones that are the same are the L0L57P1* and the L1L57P1_1_07.img one. vs. the ones above.

Submitting patches: https://wiki.lineageos.org/submitting-patch-howto.html

Gerrit: https://wiki.lineageos.org/usinggerrit-howto.html

Uploading: https://review.lineageos.org/Documentation/user-upload.html
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] FlawlesStyle:
Another week without an H918 build, I don't see it active on Jenkins. Are we waiting until the touchscreen kernel issue is addressed before we get weeklies again, or is this variant done?

Camera glass (replacement) cracked for the second time on mine, so I don't plan on staying with this phone for long anyways, but figured I'd ask for future plans before jumping ship.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] x86cpu:
It was pulled due to the no touch screen working bug. It does appear all v20's have it. So most likely the others might be pulled shortly (or should be) too.

---------- Post added at 13:01 ---------- Previous post was at 12:13 ----------

Here is my us996 build. I've tested it and I have no issues and am running it. I'll add others once major changes are in there. Keep in mind this is UNOFFICIAL, you will need a data wipe going to this and back to OFFICIAL once those builds are fixed. I'll only be providing us996 UNOFFICIAL builds. Bluetooth is mostly fixed in this. The headphone jack still does not work in this build. If fixed I'll add that.

https://drive.google.com/drive/folders/0B51rjK5Hd_P5NmpwY1o4VmlyaUk?usp=sharing
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] mking007cn:
Thank you for your nice work. i will try it this weekend. and if you can post the md5sum/sha1sum for your build? Becouse google driver don't support downloading continue from the point of interruption, i can't make sure if it has been completely downloaded. Using hash-sum, i can check it.

BTW: i hope to get your authorization to upload this build to my website, so people who can't use google driver(like me in China) can get this build. If you need, i can give you a ftp account.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] The_Keeper86:
Anyone know if the touchscreen issue Lineage. Will ever be fixed in later builds? Seems most devs have jumped ship which is a shame.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] emdroidle:
I don't have a timeframe for when I'll be jumping onto the current LineageOS kernel, but once I do touchscreen is kind of important to me for some reason. :)

Depending upon how things changed when it got broken, this may be difficult.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] sjavvaji:
I don't think many have jumped ship. Most are working on Oreo/LOS15 and second screen right now. We have a mostly working 7/28 rom. It'll probably be the last good one for LOS14.1.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] DougWare:
I opened a bug and added a few notes on 8-31. Rashed took ownership, but there haven't been any replies or updates.

https://jira.lineageos.org/browse/REGRESSION-1043

Doug

---------- Post added at 07:59 PM ---------- Previous post was at 07:58 PM ----------

I may be the exception, but I'm having tons of bluetooth issues on the 7/28 rom. I have a lot of stuttering.

Doug
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] x86cpu:
No-touch bug issue being worked on (close). All v20 builds have stopped until that is fixed. If you have twrp 3.0.2, most likely you can boot back into it, it appears twrp 3.1.1 might have no touch as well, flashing twrp-3.0.2 in fastboot allows twrp booting to recovery. (Can anyone else confirm this?)

BT is crashing on 7/28...alot. Latest fixes it.... but touchscreen issues. See my post above for a us996 variant that is ok (wipe required).

---------- Post added at 17:07 ---------- Previous post was at 17:03 ----------

I'm going to try to have another build tomorrow. It might have the blueborne BT fixes in it too, just need to test it first.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] zeruth:
Im actually fixing to release a build for H918 today :) you know how hard it is to get the proprietary files when lineage pulls the recent updates?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] x86cpu:
There is a repo for that too....
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] zeruth:
All I ended up doing was pulling drivers from last available build and manually copied what was missing. didn't take too long lol. im not too good with this stuff. just like messing around with my own builds.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] albinoman887:
hmm. what are you using to charge it? pc? stock charger? i've been using the rom for almost a week now and my battery isnt dead so i know its charging... its charging right now... ...

Sorry. can't really help you any further until i get more reports. this is what happens with an ALPHA.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] nxsone:
I now man don't bother , I wasn't expecting much from an alpha ,

And no I was using the stock wall charger the wired part is that I also saw the log and its full of tether stuff but as I said I never use theter.

And don't take it wrong the Rom was amazing the battery life was pretty decent until I decide to charge that is.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] yugendreams:
Thanks so much OP for your work. The only thing keeping me from using this as my daily driver is having tethering working. Is DAC working?

Thanks again for your work and look forward to seeing builds. I flashed your first and it was as smooth as butter.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Nirvana Rules:
OP, great job for being an alpha build it's running very good. Thank you and can't wait for some more builds.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] albinoman887:
thanks, and Oh, Nirvana does rule
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] SketchyStunts:
Yes, yes they do
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] ronattack:
Great job OP, nearly daily-driver ready. Although, through my testing I've found that sound doesn't work when recording video and video becomes unplayable at 1080p, even with google camera and fresh install. Great job regardless I prefer this over stock
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] jthrasher47:
[MENTION=3322708]albinoman887[/MENTION] you have done a hell of a job on this sand in lightning speed. I meant to say this earlier but with the holidays I've been out but anyways great job man looking forward to what you put out. Only issue I've seen as what has already been reported which is tethering besides that it runs perfectly smooth and it is my daily driver as a secondary ROM
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] lightninbug:
[MENTION=3322708]albinoman887[/MENTION] you are a genius man! Can't wait to see the next build! Pretty soon this will be out of Alpha, no? Also, will you be switching to the new Lineage OS tree?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] albinoman887:
Yeah, audio actually does work in video recording just very low as if its recording like its a phone call. probably need to manually assign what mic(s) for it to use... the unplayable thing?? i didnt notice that.. hmm the cam default records at 1080 right? cuz thats all i did was use the default settings and make a few short videos. they play but i can only hear myself talking... nothing far away from the phone

thanks. and yeah i switched to Lineage source last night. its the same source just new github etc... gonna be hard not typing CM lol... so should we call in LN?

anyways i should have a new build up either in the next hour or if i fall asleep before the upload is over in about 13 hrs....

EDIT: oh btw... tethering is broken on the g5 too. so thats kind of a good thing... it means its not just us...
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] DarkestSpawn:
As someone who has been around long enough from the first CM build (If memory serves it was CM 5 or 6...its been so long ago) on the OG Droid, it will always be called Cyanogenmod in my eyes. And I will edit in Cyanogenmod for my personal LOS flashed devices till the day AOKP comes back from the dead, then I will use AOKP. Miss my Swagger toggle =)

Besides the time capsule opening, Great work so far. Excited to see its progress.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] ZDeuce2:
LiOS... I don't know, LN reminds me too much of LP... LOL

Common sense isn't all that common

---------- Post added at 06:38 AM ---------- Previous post was at 06:37 AM ----------

Or maybe LineOS?

Common sense isn't all that common
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] OneDon:
Can I get some help here [MENTION=3322708]albinoman887[/MENTION] , After I re-branded it and started to build I came across this error. http://pastebin.com/LiEmdafZ
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] joshtheitguy:
If I had to take a guess it looks like you are missing something in your local manifests, make sure you have these in there:

<project name="TheMuppets/proprietary_vendor_qcom_binaries" path="vendor/qcom/binaries" remote="github" revision="cm-14.1" />
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-14.1" />
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Zacharee1:
I took inspiration from the elementaryOS abbreviation, eOS. I like LOS.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] OneDon:
Thanks for that, didnt have that at all in it. Gonna give it a go again
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] SketchyStunts:
How about LOAD?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] OneDon:
[MENTION=367767]joshtheitguy[/MENTION] & [MENTION=3322708]albinoman887[/MENTION] , Here's my roomservice file http://pastebin.com/GqpZf46K , but still the same error as before http://pastebin.com/KhCByDi5
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Vuciz:
Just in case anyone wants to update before albinoman posts it, it's uploaded here: https://www.androidfilehost.com/?fid=385035244224408409
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] lightninbug:
There is still no theme chooser available for cm 14.1, correct?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] x86cpu:
That works too: https://wiki.lineageos.org/extracting_blobs_from_zips.html
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] zeruth:
Here is a working touchscreen build from today's source for the H918:

https://drive.google.com/file/d/0B4IKgRbR5Mp9N3pLU0NlUGM2c2M/view?usp=sharing

Pretty sure if you are on OFFICIAL builds you will have to wipe to flash this, be warned.

This is a manual fix still. no patch upstream yet. Headphone jack broken, camera darkness etc. still same.

My fix was in kernel/lge/msm8996/firmware/makefile

above

fw-shipped-all := $(fw-shipped-y) $(fw-shipped-m) $(fw-shipped-)

I added

ifdef CONFIG_MACH_MSM8996_ELSA
fw-shipped-$(CONFIG_LGE_TOUCH_CORE_BASE) += \
touch/elsa/L0L57P1_1_35.img \
touch/elsa/L0L57P1_2_00.img \
touch/elsa/L1L52P1_1_05.img \
touch/elsa/L1L57P1_1_07.img \
touch/elsa/elsa_limit.txt \
touch/elsa/elsa_limit_mfts.txt
endif

EDIT: I also got bluetooth working pretty well, uploaded my commit to gerrit, should have nightly builds again as soon as that's approved. for all V20's

https://review.lineageos.org/#/c/189944/
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] x86cpu:
What was wrong with BT? It seemed much better already than the 7/28 version. The firmware/Makefile might be the issue in touch screen. I'll try to test that. But the BT changes might not be necessary as the kernel update fixed most of it. (just broke touch, so noone could test BT)
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] zeruth:
No problem honestly, I just misread earlier thinking BT was broken. Updated the patch so it's just the touchscreen fix. It's really whats important anyways.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] x86cpu:
I'm testing a build now, but I don't think it's still correct. The fwpath that's pulled in at the top should have the correct firmware files already. There might be some changes in there to do, but not exactly what you have. Have you tested with a completly clean (wipe your $OUT dir) build? I've found mine build is caches from 8/12 (pre kernel update), so it never re-built the touch firmware and thus continued to work as well. LOS build-bot starts with a blank $OUT directory.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] zeruth:
It should but it breaks it. If that line of code is still in there even with the firmware paths explicitly stated touchscreen won't work,

I started with a fresh repo sync just yesterday morning. it's a fresh OUT.

Pretty sure listing them the way i do, just copies the already built firmware's instead of building them. (which was the way it was set before the kernel update)
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] x86cpu:
Testing a build now, but it'll be a couple hours to be sure. I think it's only missing the L1L52P1_1_05.img to be fixed.