FORUMS

[ROM][ALL VARIANTS] LineageOS-14.1 for LG V20 [Weeklys']

3,861 posts
Thanks Meter: 16,277
 
By albinoman887, Inactive Recognized Developer on 30th November 2016, 09:25 AM
Post Reply Email Thread
DO NOT REPORT BUGS UNLESS YOU HAVE DONE A FULL WIPE, INSTALLED THE GAPPS PROVIDED , AND ARE RUNNING STOCK KERNEL WITHOUT STUPID MODS OR YOUR BUG REPORT WILL BE IGNORED PERIOD. ALSO THIS IS AN ALPHA EXPECT BUGS AND I'M ONLY ONE PERSON

These are OFFICIAL builds of CM/LineageOS-14.1 for LG V20 variants. I did NOT create this ROM, it is an Open Source project by the community for the community and I am the device maintainer of LG v20 as well as many of people contributing to throughout the ROM. thanks to all other coders who contributed to CyanogenMod/LineageOS.

Quote:

Supported devices: H918 T-Mobile, LS997 Sprint, US996 U.S. Unlocked, VS995 Verizon, H910 (AT&T)

Code:
IMPORTANT

* Builds are done on a Weekly basis
* Do NOT ask for support for flashing in this thread.
* Do NOT be rude.
* If you don't get a reply from me in a timely manner about your bug, file a report on JIRA
* Respect all users
* If I see a NOOB question and I don't feel like replying, I WONT.

  • Built from CM source
  • Service
  • Text
  • Data
  • Call
  • Audio
  • WiFi
  • Google Now
  • Bluetooth
  • GPS
  • MMS
  • Video playback
  • Audio playback
  • Internal SDcard mounting
  • External SDcard mounting
  • Camera
  • Video recording
  • IR Blaster
  • NFC

  • 2nd Screen Support
  • VoLTE and WiFi calling do not work yet

  • Do NOT use superwipes
  • DO NOT dirty flash (or if you do, DON"T REPORT BUGS UNTIL YOU DO)
  • Wipe data, cache, and dalvik cache
    *** ((but do not report bugs if you didn't full wipe))
  • Flash ROM
  • Flash GAPPS(No other gapps packages are officially supported!)
  • Reboot
  • Profit
To enable Developer Options go to Settings, About Phone and repeatedly press Build Number.
If you use ADB read this: PSA by CM
If you use reboot to recovery read this: PSA by CM
Regarding new Superuser: PSA by CM



  • Any and all users in this thread who contributed or will contribute to making this ROM as stable as possible
  • Cyanogen Inc & Team-Kang
  • Rashed
  • albinoman887



so here is a donation link if you want to buy me a coffee or pack of smokes (I go through a lot sitting on the PC messing around lol) go ahead. But not required or expected by any means

Note: The name on the Paypal account may say Patricia, this is because it's a family Paypal account.



Thanks and happy flashing!


ROM: https://download.lineageos.org/
Gapps: opengapps.org/


https://github.com/LineageOS
https://github.com/LineageOS/android_device_lge_h918
https://github.com/LineageOS/android_kernel_lge_msm8996
The Following 77 Users Say Thank You to albinoman887 For This Useful Post: [ View ] Gift albinoman887 Ad-Free
30th November 2016, 05:31 PM |#2  
OP Inactive Recognized Developer
Flag Snohomish, WA
Thanks Meter: 16,277
 
Donate to Me
More


Mar 11
** Major Update **
* rebased on CAF 7.1
* massive cleanup of device tree and kernel
* massive cleanup of vendor libs
* Fixed 2nd backlight not matching main backlight brightness (fixes shadow in upper right corner)
* Switched to source built ril, better compatibility and adds support for LTE Advanced (LTE+)
* Enabled noise suppression during calls
* Fixed issues with Google Camera
* Fixed wakelock issues with bluetooth
* aptX support
* Fixed static screen on US996
* A few other updates i can't remember
* Any and all changes from Lineage at time of compile
* Official Nightlies should be coming soon

Feb 14
* Fixed Ambient Display
* Fixed BT Pairing issues on h918
* Fixed Bluetooth not turning on on other variants (ls997,vs995,us996,h910)
* Fixed default bluetooth device name
* CDMA should work "out of the box" now no needing to play with settings (sprint,vzw)
* Disabled VoLTE and WiFi Calling settings as they are broken and causes random issues when dialing out
* Any and all upstream Lineage updates at time of compile
NOTE: as far as i know whats still messed up now is, low audio in video recording, no VoLTE, Quad DAC, and maybe a couple little things (writing this off the top of my head)

Jan 30
* Fixed Bluetooth Wakelock
* Fixed animation glitch when rotating or sleeping device
* Fixed touch inaccuracy in 270 degree landscape mode
* Baseband now shows in system info
* Lots of Lineage updates
* NOTE: Lineage is removing superuser from main rom and making a flashable zip. for now i'm still including it but this could stop at any time. Basically once they have the zip up on lineageos.org i'll remove it
* NOTE2: released for all variants but CDMA devices still have the same data issues. I need more then just pople saying "this works" that works i need LOGS people...


Jan 13
* Attempt #2 at us996 build
* Attempt #2 at vs995 build
* Attempt #2 at h910 build
* Attempt #2 at ls997 build
* All sources synced and up to date as of the build date and time

Jan 10
* Fixed LS997 build to flash without editing script
* initial H910 build

Jan 9
* initial VS995 build

Jan 8
* initial LS997 build
* initial US996 build

Jan 04
* Removed some unneeded telephony related overlays. Seems to fix slow connection of phone calls
* Fixed Wi-Fi Tethering (credit: Rashed)
* Various changes to fix GPS in navigation, not 100% yet but a lot better

Dec 28
* We are now at the same state as the G5 builds
* Removed LED settings since we don't have one
* Add a couple missing build props from stock (dalvik heap size etc)
* Updated mixer_paths.xml to match stock. (no real world difference just good practice)
* Updated telephony libs (fixes the random FC of .timeservice and .dataservice
* Fixed the static during boot animation (was a merge fail of a .dtsi for screen commands)
* Speed improvments do the above fix
* Wide angle camera now is usable in Snap. To use, just tap the button you tap for front camera until you get to wide angle lens
* Synced with latest source
* Picked commits that rebrand CM to LineageOS

Dec 25
* Fixed UI "bleeding" into 2nd screen, still a animation glitch but tracking that down
* Fixed Camera (Picture and Video)
* Fixed LiveDisplay
* fixed auto brightness curve
* Cleanup


Dec 19
* initial test release






https://github.com/LineageOS
https://github.com/LineageOS/android_device_lge_h918
https://github.com/Team-Hydra/androi...lge_v20-common
https://github.com/Team-Hydra/androi...el_lge_msm8996

Contributors
albinoman887
The Following 20 Users Say Thank You to albinoman887 For This Useful Post: [ View ] Gift albinoman887 Ad-Free
30th November 2016, 05:41 PM |#3  
ShotSkydiver's Avatar
Senior Member
Flag Salt Lake City
Thanks Meter: 134
 
Donate to Me
More
I have been working on this for days and it has gone very poorly haha, I've been alternating between attempting to build entirely from source, and trying to at the very least get the latest cm14.1 nightly for the T-Mobile G5 booting, and it's been unsuccessful so far. I've been able to get it stuck at the boot animation, but no matter what I've tried, I can't get adb enabled, so I have zero idea where the issue lies and I've basically just been blindly trying things and hoping it'll give me adb. This is of course super tedious because in order to boot into recovery requires a battery pull, getting to the factory reset screen, waiting for it to boot into TWRP, and quickly running adb reboot recovery within the 1 second twrp is running before it auto reboots. BUT I AM DETERMINED TO GET THIS TO WORK

---------- Post added at 09:41 AM ---------- Previous post was at 09:38 AM ----------

I'm trying to figure out the best boot.img to use, because I'm 99% sure the problem lies somewhere in there, I've tried using the boot.img inside the g5 zip, the boot.img in the stock debloated zip for our device, and I've also tried unpacking and modifying both to various degrees, to NO SUCCESS
The Following 7 Users Say Thank You to ShotSkydiver For This Useful Post: [ View ] Gift ShotSkydiver Ad-Free
1st December 2016, 12:09 AM |#4  
OP Inactive Recognized Developer
Flag Snohomish, WA
Thanks Meter: 16,277
 
Donate to Me
More
Quote:
Originally Posted by ShotSkydiver

I have been working on this for days and it has gone very poorly haha, I've been alternating between attempting to build entirely from source, and trying to at the very least get the latest cm14.1 nightly for the T-Mobile G5 booting, and it's been unsuccessful so far. I've been able to get it stuck at the boot animation, but no matter what I've tried, I can't get adb enabled, so I have zero idea where the issue lies and I've basically just been blindly trying things and hoping it'll give me adb. This is of course super tedious because in order to boot into recovery requires a battery pull, getting to the factory reset screen, waiting for it to boot into TWRP, and quickly running adb reboot recovery within the 1 second twrp is running before it auto reboots. BUT I AM DETERMINED TO GET THIS TO WORK

---------- Post added at 09:41 AM ---------- Previous post was at 09:38 AM ----------

I'm trying to figure out the best boot.img to use, because I'm 99% sure the problem lies somewhere in there, I've tried using the boot.img inside the g5 zip, the boot.img in the stock debloated zip for our device, and I've also tried unpacking and modifying both to various degrees, to NO SUCCESS

have you tried building a eng build instead of userdebug? that will enable adb by default. Hey at least your at the boot animation. thats half the battle. could you put your device trees and stuff on github? we can fork it and i'll give you access to my Team-Hydra orginization github and we can get cracking. I'm gonna PM you my email. hit me up on Hangouts please.

about boot.img . you could "try" unpacking the g5 boot.img and grabbing the init.ivercon.rc or whatever its called and init.cm.rc and then pack those into the stock boot.img but the better solution would be to fork the g5 and then add the differences. but getting ADB going would be the No 1 priority.
The Following 9 Users Say Thank You to albinoman887 For This Useful Post: [ View ] Gift albinoman887 Ad-Free
1st December 2016, 05:03 AM |#5  
jameslapc2's Avatar
Senior Member
Flag The Green Mountain State
Thanks Meter: 68
 
More
Subscribed! Hopefully this actually becomes a reality, otherwise my next phone will be One Plus.
2nd December 2016, 10:39 AM |#6  
OneDon's Avatar
Senior Member
Flag Brooklyn
Thanks Meter: 339
 
Donate to Me
More
This is my first time with a none nexus device, personally I see it as a big step some might say the opposite as in a "big step back" but I see opportunities for this device. I've had my fair share bringing OwnRom (CM based) to the nexus 5 successfully and other experiences with bringing ROMs to dropped devices I've owned. One of questions is how long did it take LG to release there sources for the v10, that's all I'm waiting for tbh. I'm really not in for the making a ROM via a twrp backup I'm more of a from scratch type of guy. Because even over on Google+ they mentioned that tesla ROM (AOSP based) only needed a maintainer for the v20 but there's no source yet.
2nd December 2016, 07:27 PM |#7  
AngryManMLS's Avatar
Senior Member
Thanks Meter: 1,263
 
Donate to Me
More
Quote:
Originally Posted by jameslapc2

Subscribed! Hopefully this actually becomes a reality, otherwise my next phone will be One Plus.

Quote:
Originally Posted by OneDon

This is my first time with a none nexus device, personally I see it as a big step some might say the opposite as in a "big step back" but I see opportunities for this device. I've had my fair share bringing OwnRom (CM based) to the nexus 5 successfully and other experiences with bringing ROMs to dropped devices I've owned. One of questions is how long did it take LG to release there sources for the v10, that's all I'm waiting for tbh. I'm really not in for the making a ROM via a twrp backup I'm more of a from scratch type of guy. Because even over on Google+ they mentioned that tesla ROM (AOSP based) only needed a maintainer for the v20 but there's no source yet.

This thread is ONLY for discussing development of CM14 for the V20 not your back stories on previous devices or saying you subscribed.
The Following 6 Users Say Thank You to AngryManMLS For This Useful Post: [ View ] Gift AngryManMLS Ad-Free
3rd December 2016, 09:30 AM |#8  
OP Inactive Recognized Developer
Flag Snohomish, WA
Thanks Meter: 16,277
 
Donate to Me
More
Quote:
Originally Posted by OneDon

This is my first time with a none nexus device, personally I see it as a big step some might say the opposite as in a "big step back" but I see opportunities for this device. I've had my fair share bringing OwnRom (CM based) to the nexus 5 successfully and other experiences with bringing ROMs to dropped devices I've owned. One of questions is how long did it take LG to release there sources for the v10, that's all I'm waiting for tbh. I'm really not in for the making a ROM via a twrp backup I'm more of a from scratch type of guy. Because even over on Google+ they mentioned that tesla ROM (AOSP based) only needed a maintainer for the v20 but there's no source yet.

source is out. how do you think there are modded kernels. Someone needs to spend the time on making a device tree and with all the stuff that just happened with cyanogen.inc idk if CM is even going to be around in a couple months.
The Following User Says Thank You to albinoman887 For This Useful Post: [ View ] Gift albinoman887 Ad-Free
3rd December 2016, 12:13 PM |#9  
OneDon's Avatar
Senior Member
Flag Brooklyn
Thanks Meter: 339
 
Donate to Me
More
Quote:
Originally Posted by albinoman887

source is out. how do you think there are modded kernels. Someone needs to spend the time on making a device tree and with all the stuff that just happened with cyanogen.inc idk if CM is even going to be around in a couple months.

you are right though.
8th December 2016, 04:01 AM |#10  
Senior Member
Flag Cleveland
Thanks Meter: 47
 
More
Well, just when I was about to abandon all hope and switch back to my G3 but I finally got my build to quit failing around 3%.

I'm not expecting this to boot but I'll take what I can get right now. I'd rather get it to build, try flashing and if renders my V20 useless in the process then I'll just switch back to my G3. I feel my V20 will be more useful stuck in a boot loop than it is now currently with LG's crappy UI mods anyway.

If I can actually get this going to the point where I can at least get ADB going I'll post a download link ASAP but I'm probably way out of my league right now. Is anyone else still trying or am I the only one who is so fed up with the stock ROM that they are still continuing to try and get a build going?
The Following 3 Users Say Thank You to joshtheitguy For This Useful Post: [ View ] Gift joshtheitguy Ad-Free
8th December 2016, 05:58 AM |#11  
Senior Member
Flag Cleveland
Thanks Meter: 47
 
More
I got it to build but it hangs up immediately after the cannot verify message. I'm done for now, see if my backup restores otherwise it is back to my G3 running CM14.1 for now,
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes