• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

cnjax

Senior Member
Aug 4, 2011
4,282
10,897
Jacksonville, FL
I know that LG did something funky here to disable the fastboot commands. Anyone knows what I need to do to load recovery? I have H918 10u that I got refurbished from ebay. I did unlock the phone but its just not flashing or just booting to recovery.

target reported max download size of 536870912 bytes
sending 'recovery' (29100 KB)...
OKAY 0.681s
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.700s
You need to check out the laf exploit thread to achieve root and get twrp installed

Sent from my LG-H910 using XDA Labs
 
  • Like
Reactions: egenesis

x86cpu

Senior Member
Aug 25, 2010
1,759
4,094
Rochester
Google Pixel 6 Pro
I know that LG did something funky here to disable the fastboot commands. Anyone knows what I need to do to load recovery? I have H918 10u that I got refurbished from ebay. I did unlock the phone but its just not flashing or just booting to recovery.

target reported max download size of 536870912 bytes
sending 'recovery' (29100 KB)...
OKAY 0.681s
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.700s


You need to check out the laf exploit thread to achieve root and get twrp installed

Plus after, since you are h918 and higher than 10p, you'll need to flash the 15.1 LineageOS. 14.1 won't every support it. Check my unofficial thread, and make sure you flash the 10p version.
 
  • Like
Reactions: egenesis

egenesis

Member
Aug 27, 2017
14
7
Plus after, since you are h918 and higher than 10p, you'll need to flash the 15.1 LineageOS. 14.1 won't every support it. Check my unofficial thread, and make sure you flash the 10p version.

Holy cow!! This keeps getting worse. Wondering why LG wants to make things harder for user when it does not even have much market. I would think they would make it par with One Plus and try to let users do whatever they want rather than trying to compete with Samsung. Anyways thanks!! I wanted to go 14.1 just for more stability, but seems like that's not the case anymore.
 

Exabyter

Senior Member
Mar 11, 2017
231
109
I have the kernel code for Oreo for our devices. Nothing yet, however Lineage is looking to add into the charter a change that requires OTG to work if stock did. Which means.... to go official it'll have to work. So if it doesn't, it'll never to official. Still working on it for Oreo, but unfortunately 14.1 here it's probably slowed down.


Any progress on this issue for Oreo??

Thanks

---------- Post added at 10:27 AM ---------- Previous post was at 10:06 AM ----------

Holy cow!! This keeps getting worse. Wondering why LG wants to make things harder for user when it does not even have much market. I would think they would make it par with One Plus and try to let users do whatever they want rather than trying to compete with Samsung. Anyways thanks!! I wanted to go 14.1 just for more stability, but seems like that's not the case anymore.


Device makers are under a lot of pressure legally and financially from customers, companies and regulators to keep devices secure and not make it easy to trojan devices, circumvent DRM and so on.

The voice of ROM hackers and tinkerers is tiny by comparison so actually most companies would be expected to follow the dollars, and not the ROMing community.

Which is why it's so nice when some vendors pay more attention to us. But as companies like OnePlus get more popular and start trying to woo the US and corporate market (see recent news on this), expect their policies to get more restrictive too. LG just reached that point years earlier.
 

x86cpu

Senior Member
Aug 25, 2010
1,759
4,094
Rochester
Google Pixel 6 Pro
Holy cow!! This keeps getting worse. Wondering why LG wants to make things harder for user when it does not even have much market. I would think they would make it par with One Plus and try to let users do whatever they want rather than trying to compete with Samsung. Anyways thanks!! I wanted to go 14.1 just for more stability, but seems like that's not the case anymore.

It's due to r ARB01. You cannot flash anything pre-10p. There video drivers were updated, so it does require different blobs.

However... my unofficial 15.1 is fairly stable. I'm running it daily too. To me it is not stable than 14.1. "official" status does not necessarily mean stable.

---------- Post added at 11:29 AM ---------- Previous post was at 11:26 AM ----------

Any progress on this issue for Oreo??

Thanks

If this is OTG working for 15.1, that was fixed about a month ago. Encryption works but is "wonky" (sometimes requires a battery pull). Everything is ready to go official, just some last things to tidy up.
 

Hondroid

Senior Member
Oct 1, 2013
177
54
23
New York
www.facebook.com
With "h918", x86cpu means the model of the v20, you have.... There are some models on the market... us996, h918, vs997, h910, 990ds, vs995...
You can check that, by pulling the battery out... There should be a sticker like this, where you can read the model-type:

https://i.imgur.com/gZO5KpA_d.jpg?maxwidth=640&shape=thumb&fidelity=medium

After you checked that, just post the model-name here...

With "10p", x86cpu means the original software version, you came from. In original OS you can check that, by going to the settings/about the phone, but now you are already at a custom rom and i have no idea how to check that after flashing.

I know its an h918 but im pretty sure im not on 10p bc i rooted and flashed WETA over a year ago.
 

CM-Tester

Senior Member
Oct 20, 2016
345
160
Düsseldorf
Short Update:
Dirty Flash with the newest nightly (20180715) on us996 (with TWRP) was no problem (After it, wiped cache and dalvik). Everything seems to be smooth.

PS.
Security Patch Level is 05.06.2018 (5. June)
 

Exabyter

Senior Member
Mar 11, 2017
231
109
Short Update:
Dirty Flash with the newest nightly (20180715) on us996 (with TWRP) was no problem (After it, wiped cache and dalvik). Everything seems to be smooth.

PS.
Security Patch Level is 05.06.2018 (5. June)



The last time I updated (I am also using a US996) I just used the built in LOS updater which downloaded the zip file, rebooted to recovery (I'm using TWRP), invoked the flash via TWRP and restarted, all with one button push. ?

I assume it's just doing a dirty flash as well, have no idea if it wipes cache/dalvik, but I have a feeling it does not.
 

CM-Tester

Senior Member
Oct 20, 2016
345
160
Düsseldorf
The last time I updated (I am also using a US996) I just used the built in LOS updater which downloaded the zip file, rebooted to recovery (I'm using TWRP), invoked the flash via TWRP and restarted, all with one button push.

I assume it's just doing a dirty flash as well, have no idea if it wipes cache/dalvik, but I have a feeling it does not.

I think it didn't (just the dirty flash). But after an update it is always better to wipe cache/dalvik, so there are less problems after it.
 

almony8

Senior Member
Dec 6, 2010
910
227
Where can I find a build for ls997 that is from may 2017? I'm told it's hard to find but I really need a copy of it
 
Last edited:

Exabyter

Senior Member
Mar 11, 2017
231
109
I can't get the "Portable WiFi Hotspot" feature to work no matter what settings I try.

Is this a known problem on this device??

TIA


EDIT: I just tried the same feature on my LG G4 running an older build of LOS 14.1 (completely different mobile carrier) and it doesn't work either. Shows "error" next to the on/off button just like my v20.

I'm beginning to think that feature was someone's idea of a bad joke.
 
Last edited:

CM-Tester

Senior Member
Oct 20, 2016
345
160
Düsseldorf
I can't get the "Portable WiFi Hotspot" feature to work no matter what settings I try.

Is this a known problem on this device??

TIA


EDIT: I just tried the same feature on my LG G4 running an older build of LOS 14.1 (completely different mobile carrier) and it doesn't work either. Shows "error" next to the on/off button just like my v20.

I'm beginning to think that feature was someone's idea of a bad joke.

On my us996 with 20180715 weekly the Hotspot is running without any problems...
 
Last edited:

Exabyter

Senior Member
Mar 11, 2017
231
109
On my us996 with 20180715 weekly the Hotspot is running without any problems...


Very interesting. I have similar problems on my G4 (h811) running 2017-11-28 nightly (Gapps pico) and my v20 (US996) running 2018-07-01. (microG)

Any suggestions for what string(s) to look for in logcat to troubleshoot this? Below is a filtered/cleaned up logcat snippet at ERROR level. Note that in some cases the "set country code" apparently succeeded:


Code:
[DEVICE INFO]
build.board: MSM8996
build.bootloader: unknown
build.brand: lge
build.cpu_abi: arm64-v8a
build.cpu_abi2: 
build.device: us996
build.display: lineage_us996-userdebug 7.1.2 NJH47F 20180701 dev-keys
build.fingerprint: lge/elsa_nao_us/elsa:7.0/NRD90M/162831845a3a3:user/release-keys
build.hardware: qcom
build.host: a6f9ad0f807c
build.id: NJH47F
build.manufacturer: LGE
build.model: LG-US996
build.product: elsa_nao_us
build.radio: unknown
build.serial: LGUS99617964d33
build.tags: release-keys
build.time: 1530423031000
build.type: user
build.user: root
version.codename: REL
version.incremental: 7323eade16
version.release: 7.1.2
version.sdk_int: 25


[LOG LEVEL: ERROR]

[GOT LOTS OF THE FOLLOWING LINE, REMOVED ALL BUT THIS ONE FOR BREVITY]

07-30 10:50:09.562 W/ResourceType(3680): No package identifier when getting name for resource number 0x00000000



07-30 10:50:11.245 W/WindowManager(2442): Attempted to remove non-existing token: [email protected]

07-30 10:50:12.590 E/ANDR-PERF-RESOURCEQS(584): Failed to reset optimization [2, 1]
07-30 10:50:12.591 E/ANDR-PERF-RESOURCEQS(584): Failed to reset optimization [2, 1]
07-30 10:50:13.260 W/WindowManager(2442): Attempted to remove non-existing token: [email protected]
07-30 10:50:13.369 E/ActivityManager(2442): applyOptionsLocked: Unknown animationType=0
07-30 10:50:13.490 E/ANDR-PERF-RESOURCEQS(584): Failed to reset optimization [2, 1]
07-30 10:50:13.491 E/ANDR-PERF-RESOURCEQS(584): Failed to reset optimization [2, 1]
07-30 10:50:13.550 W/TileUtils(21342): Found com.android.settings.Settings$PaymentSettingsActivity for intent Intent { act=com.android.settings.action.SETTINGS pkg=com.android.settings } missing metadata com.android.settings.category
07-30 10:50:13.554 W/TileUtils(21342): Found com.android.systemui.tuner.TunerActivity for intent Intent { act=com.android.settings.action.EXTRA_SETTINGS } missing metadata 
07-30 10:50:14.037 W/AlarmManager(2442): Unrecognized alarm listener [email protected]08a
07-30 10:50:14.037 E/BatteryStatsService(2442): no controller energy info supplied
07-30 10:50:14.046 E/KernelWakelockReader(2442): neither /proc/wakelocks nor /d/wakeup_sources exists
07-30 10:50:14.058 W/BatteryStatsImpl(2442): Couldn't get kernel wake lock stats
07-30 10:50:14.070 W/NetworkIdentity(2442): Active mobile network without subscriber! ni = [type: MOBILE[LTE], state: CONNECTED/CONNECTED, reason: connected, extra: VZWINTERNET, failover: false, available: true, roaming: false, metered: true]
07-30 10:50:14.077 W/BroadcastQueue(2442): Background execution not allowed: receiving Intent { act=android.net.wifi.STATE_CHANGE flg=0x4000010 (has extras) } to com.here.app.maps/com.here.app.trafficprobegen.WifiIntentReceiver
07-30 10:50:14.215 E/WifiHAL (2442): wifi_event_loop: Read after POLL returned 4, error no = 0
07-30 10:50:14.221 W/BroadcastQueue(2442): Background execution not allowed: receiving Intent { act=android.net.wifi.STATE_CHANGE flg=0x4000010 (has extras) } to com.vonglasow.michael.satstat/.GpsEventReceiver
07-30 10:50:14.221 E/WifiHAL (2442): wifi_cleanup: Read after POLL returned 4, error no = 0
07-30 10:50:14.221 E/WifiHAL (2442): Event processing terminated

07-30 10:50:15.143 E/SoftApManager(2442): Failed to set country code, required for setting up soft ap in 5GHz
07-30 10:50:15.147 E/WifiController(2442): WifiControllerSoftAP start failed
07-30 10:50:15.149 E/WifiHAL (2442): wifi_event_loop: Read after POLL returned 4, error no = 0
07-30 10:50:15.149 E/WifiHAL (2442): wifi_cleanup: Read after POLL returned 4, error no = 0
07-30 10:50:15.150 E/WifiHAL (2442): Event processing terminated

07-30 10:50:15.442 E/WifiMonitor(2442): killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
07-30 10:50:16.061 E/WifiHW  (2442): Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory
07-30 10:50:16.204 W/WifiNetworkHistory(2442): Upgrading network 0 to android.uid.system:1000
07-30 10:50:16.206 W/WifiNetworkHistory(2442): Upgrading network 1 to android.uid.system:1000
07-30 10:50:16.206 W/WifiNetworkHistory(2442): Upgrading network 3 to android.uid.system:1000
07-30 10:50:16.207 W/WifiNetworkHistory(2442): Upgrading network 2 to android.uid.system:1000
07-30 10:50:16.340 W/AlarmManager(2442): Unrecognized alarm listener [email protected]08a
07-30 10:50:16.341 E/BatteryStatsService(2442): no controller energy info supplied
07-30 10:50:16.365 E/KernelWakelockReader(2442): neither /proc/wakelocks nor /d/wakeup_sources exists
07-30 10:50:16.367 W/BatteryStatsImpl(2442): Couldn't get kernel wake lock stats
07-30 10:50:16.372 E/BatteryStatsService(2442): no controller energy info supplied
07-30 10:50:16.380 E/KernelWakelockReader(2442): neither /proc/wakelocks nor /d/wakeup_sources exists
07-30 10:50:16.381 W/BatteryStatsImpl(2442): Couldn't get kernel wake lock stats
07-30 10:50:16.391 W/NetworkIdentity(2442): Active mobile network without subscriber! ni = [type: MOBILE[LTE], state: CONNECTED/CONNECTED, reason: connected, extra: VZWINTERNET, failover: false, available: true, roaming: false, metered: true]
07-30 10:50:16.394 W/BroadcastQueue(2442): Background execution not allowed: receiving Intent { act=android.net.wifi.STATE_CHANGE flg=0x4000010 (has extras) } to com.here.app.maps/com.here.app.trafficprobegen.WifiIntentReceiver
07-30 10:50:16.421 E/WifiHAL (2442): wifi_event_loop: Read after POLL returned 4, error no = 0
07-30 10:50:16.424 E/WifiHAL (2442): wifi_cleanup: Read after POLL returned 4, error no = 0
07-30 10:50:16.424 E/WifiHAL (2442): Event processing terminated
07-30 10:50:16.441 W/BroadcastQueue(2442): Background execution not allowed: receiving Intent { act=android.net.wifi.STATE_CHANGE flg=0x4000010 (has extras) } to com.vonglasow.michael.satstat/.GpsEventReceiver

07-30 10:50:17.350 E/SoftApManager(2442): Failed to set country code, required for setting up soft ap in 5GHz
07-30 10:50:17.351 E/WifiController(2442): WifiControllerSoftAP start failed
07-30 10:50:17.352 E/WifiHAL (2442): wifi_event_loop: Read after POLL returned 4, error no = 0
07-30 10:50:17.352 E/WifiHAL (2442): wifi_cleanup: Read after POLL returned 4, error no = 0
07-30 10:50:17.353 E/WifiHAL (2442): Event processing terminated
07-30 10:50:17.683 E/WifiMonitor(2442): killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
07-30 10:50:18.445 W/WifiNetworkHistory(2442): Upgrading network 0 to android.uid.system:1000
07-30 10:50:18.445 W/WifiNetworkHistory(2442): Upgrading network 1 to android.uid.system:1000
07-30 10:50:18.446 W/WifiNetworkHistory(2442): Upgrading network 3 to android.uid.system:1000
07-30 10:50:18.447 W/WifiNetworkHistory(2442): Upgrading network 2 to android.uid.system:1000
07-30 10:50:18.604 W/AlarmManager(2442): Unrecognized alarm listener [email protected]08a
07-30 10:50:18.605 E/BatteryStatsService(2442): no controller energy info supplied
07-30 10:50:18.610 E/KernelWakelockReader(2442): neither /proc/wakelocks nor /d/wakeup_sources exists
07-30 10:50:18.611 W/BatteryStatsImpl(2442): Couldn't get kernel wake lock stats
07-30 10:50:18.613 E/BatteryStatsService(2442): no controller energy info supplied
07-30 10:50:18.620 E/KernelWakelockReader(2442): neither /proc/wakelocks nor /d/wakeup_sources exists
07-30 10:50:18.621 W/BatteryStatsImpl(2442): Couldn't get kernel wake lock stats
07-30 10:50:18.633 W/NetworkIdentity(2442): Active mobile network without subscriber! ni = [type: MOBILE[LTE], state: CONNECTED/CONNECTED, reason: connected, extra: VZWINTERNET, failover: false, available: true, roaming: false, metered: true]
07-30 10:50:18.638 W/BroadcastQueue(2442): Background execution not allowed: receiving Intent { act=android.net.wifi.STATE_CHANGE flg=0x4000010 (has extras) } to com.here.app.maps/com.here.app.trafficprobegen.WifiIntentReceiver
07-30 10:50:18.680 W/BroadcastQueue(2442): Background execution not allowed: receiving Intent { act=android.net.wifi.STATE_CHANGE flg=0x4000010 (has extras) } to com.vonglasow.michael.satstat/.GpsEventReceiver

07-30 10:50:18.746 E/WifiHAL (2442): wifi_event_loop: Read after POLL returned 4, error no = 0
07-30 10:50:18.746 E/WifiHAL (2442): wifi_cleanup: Read after POLL returned 4, error no = 0
07-30 10:50:18.747 E/WifiHAL (2442): Event processing terminated

07-30 10:50:19.689 E/SoftApManager(2442): Failed to set country code, required for setting up soft ap in 5GHz

07-30 10:50:19.696 E/WifiController(2442): WifiControllerSoftAP start failed
07-30 10:50:19.701 E/WifiHAL (2442): wifi_event_loop: Read after POLL returned 4, error no = 0
07-30 10:50:19.702 E/WifiHAL (2442): wifi_cleanup: Read after POLL returned 4, error no = 0
07-30 10:50:19.702 E/WifiHAL (2442): Event processing terminated

07-30 10:50:20.005 E/WifiMonitor(2442): killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
07-30 10:50:20.944 E/ANDR-PERF-RESOURCEQS(584): Failed to reset optimization [2, 1]
07-30 10:50:20.945 E/ANDR-PERF-RESOURCEQS(584): Failed to reset optimization [2, 1]
07-30 10:50:21.039 W/WifiNetworkHistory(2442): Upgrading network 0 to android.uid.system:1000
07-30 10:50:21.040 W/WifiNetworkHistory(2442): Upgrading network 1 to android.uid.system:1000
07-30 10:50:21.041 W/WifiNetworkHistory(2442): Upgrading network 3 to android.uid.system:1000
07-30 10:50:21.041 W/WifiNetworkHistory(2442): Upgrading network 2 to android.uid.system:1000
07-30 10:50:21.158 E/BatteryStatsService(2442): no controller energy info supplied
07-30 10:50:21.165 E/KernelWakelockReader(2442): neither /proc/wakelocks nor /d/wakeup_sources exists
07-30 10:50:21.165 W/BatteryStatsImpl(2442): Couldn't get kernel wake lock stats
07-30 10:50:21.633 E/ActivityManager(2442): applyOptionsLocked: Unknown animationType=0

07-30 10:50:21.725 E/ANDR-PERF-RESOURCEQS(584): Failed to reset optimization [2, 1]
07-30 10:50:21.725 E/ANDR-PERF-RESOURCEQS(584): Failed to reset optimization [2, 1]

07-30 10:50:31.032 W/IInputConnectionWrapper(23328): finishComposingText on inactive InputConnection
07-30 10:50:31.032 W/IInputConnectionWrapper(23328): finishComposingText on inactive InputConnection
07-30 10:50:31.032 W/IInputConnectionWrapper(23328): finishComposingText on inactive InputConnection
07-30 10:50:31.049 W/IInputConnectionWrapper(23328): finishComposingText on inactive InputConnection

07-30 10:50:33.121 W/WindowManager(2442): Attempted to remove non-existing token: [email protected]
 

Exabyter

Senior Member
Mar 11, 2017
231
109
2.4 or 5? 5 has been known is not working at the moment.


Interesting. I tried both actually on both devices - no go.

I'll double-check 2.4 again tonight.

(Pity tho - 2.4 is ridiculously congested in my neighborhood. I've had hardware hotspots in the past that were so overwhelmed by all the signals around here on 2.4 ghz that they would shut down a couple minutes after power up because they couldn't find clear air to transmit on)
 

CM-Tester

Senior Member
Oct 20, 2016
345
160
Düsseldorf
Interesting. I tried both actually on both devices - no go.

I'll double-check 2.4 again tonight.

(Pity tho - 2.4 is ridiculously congested in my neighborhood. I've had hardware hotspots in the past that were so overwhelmed by all the signals around here on 2.4 ghz that they would shut down a couple minutes after power up because they couldn't find clear air to transmit on)

Ok i checked it again with my laptop and HotSpot of the V20 us996 (2,4 GHz)... It runs :)
 
  • Like
Reactions: Exabyter

Top Liked Posts

  • There are no posts matching your filters.
  • 75
    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.

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

    Code:
    [B]IMPORTANT[/B]
    
    * 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.


    c4ypvbf.png

    • 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

    bJO9QqG.png

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

    2jpqfKR.png

    • 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



    w5xnyz0.png

    • 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

    cvU6373.png


    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!

    l5SakBJ.png

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

    lSuV72q.png

    https://github.com/LineageOS
    https://github.com/LineageOS/android_device_lge_h918
    https://github.com/LineageOS/android_kernel_lge_msm8996
    19
    sB7atuO.png


    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


    l5SakBJ.png



    lSuV72q.png

    https://github.com/LineageOS
    https://github.com/LineageOS/android_device_lge_h918
    https://github.com/Team-Hydra/android_device_lge_v20-common
    https://github.com/Team-Hydra/android_kernel_lge_msm8996

    Contributors
    albinoman887
    18
    the second screen is more than likely rooted into LS's Framework (notifications) and not a public source. meaning to make it work like its current state will be more than adding a few apps.
    just my 2 cents

    yeah i'm not even gonna try and bother emplementing its features i just want to disable it. i tried playing with the dts for the panel which i got the display to the right size but it messes up touch and hw overlays. wm overscan causes gltiches wm size bases its size off the center of the screen so to get everything out of the 160px 2nd screen you need to set it to 1400x2400 which isnt ideal and it causes glitches on rotation. my goal is to either A: fix the hw overlays then mod the touch driver to offset itself.. B: change wm overcan C: fix the scailing issues with the overscan option... been trying for days with Rashed but still nothing new..

    got cam and ok google from any screen working though :)
    13
    Could you do a build of Beanstalk or Resurection Remix for T-Mobile? Or are those still far away?

    I'm getting my device h918 tomorrow to join in the fun. I'll be officially maintaining for RR
    13
    new builds posted. major updates... if you have issues do a full wipe... make a backup before flashing... should be good though. even though i havent released a build in almost a month ive been working every single day to get thsi phone closer to stable status... we are pretty much there minus a few things like volte and low video recording volume. I should be enabling lineage nigtlies sometime soon. (week or two) after that this thread will no longer be updated... Ive spent hours and hours and HOURs on this and although it was fun I have everything I need for a DD working and the donations arent really something to write home about. I will still be working on it but i might not take as much of a active role in the xda community part until a new los version like los 15 or something comes out. We have a few great devs in here who have forked my work and are in contact with me on probably a weekly, if not daily basis. Basically i'm just saying if i dont post for awhile dont worry. thats a good thing. that means the device is stable enough i can just allow the cm servers to build and i can maintain the functionality of what it is at this state by fixing new bugs that crop up (if they do) from new source merges) But honestly i'm getting ahead of myself the nightlies arent even going for v20 yet so....


    Enjoy the build guys.

    let me know of any bugs if any