[OFFICIAL] LineageOS 18.1 for the LG V20

Status
Not open for further replies.
Search This thread

npjohnson

Recognized Developer
lineage-os-logo.png

LG V20

Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.

Introduction:
This is the Official Lineage OS 18.1 thread for the LG V20.

Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

Known Bugs:
  • IMS (VoLTE/Wi-Fi Calling) doesn't work due to framework tie-ins used by the LG proprietary binaries.
  • Find any? Report them according to this guide.
Notes:
  • The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Kernel Source: https://github.com/LineageOS/android_kernel_lge_msm8996
 
Last edited:

stingbandel

Senior Member
Nov 23, 2005
457
50
Do I still need to go back to nougat stock first in order to get all the sensors working? I am now on oreo stock rooted.

thanks
 

exendahl

Member
Feb 22, 2018
7
4
Kathmandu
I flashed lineage 18.1 zip and MindTheGapps.zip together. Lineage is installed but cannot find google service. I tried to reboot to recovery mode but I am stuck on Glitch splash screen. I tried flashing twrp and recovery with fastboot but no luck.
 

hamid_valad

Senior Member
Dec 30, 2009
294
34
Tehran
what are the benefits over unofficial other than updates?
are the issues fixed?

Is the camera working well?
GPS connectivity?
Bluetooth?
IR Blaster?
overheating?
random crashes?

any experience on these issues known with unofficial?
 
Last edited:

Chyrio

Senior Member
Jun 9, 2010
377
51
Not sure if this is my device being dumb.. I try to update to the 18.1 Lineage recovery to update to the new rom and I keep getting "writing recovery FAILED (remote: unknown command)" in fastboot, tried 3 different laptops, 2 different versions of fastboot, 2 different USB cables, disabling screen lock and stuff on the 17.1 rom still installed.. Not sure why I cannot get it to push.
 

Jacky_Chua

Senior Member
Jan 25, 2012
181
58
Thanks for the new version of Android Linegae OS!
Currently I am using Lineage OS 17.1, do I need to revert back to the stock LG firmware before flashing this ROM?
 

pavik62

Senior Member
Apr 20, 2011
580
334
Volgograd
4pda.ru
Спасибо за новую версию ОС Android Linegae!
В настоящее время я использую Lineage OS 17.1, нужно ли мне вернуться к стандартной прошивке LG перед прошивкой этого ПЗУ?
Нет. Но нужно удалить гаппсы 17.1. Протрите систему.
 
  • Like
Reactions: Jacky_Chua

mangokm40

Senior Member
Jan 13, 2019
223
124
On 04-01, I updated to TWRP 3.5.1 and did a clean install of this ROM (04-01). I wiped & formatted, after making a copy of my internal storage to a PC. The install went great. I reinstalled my apps and then flashed Magisk 22.0. Everything I tried worked well (BT, GPS, quad DAC).

Today, I updated to TWRP 3.5.2 and Magisk 22.1. Then, I dirty flashed the 04-15 nightly. Magisk patched new boot.img automatically and everything is working well.

Thanks to npjohnson and x86cpu for keeping my travel device up-to-date. :)

But mostly, thanks to aleasto !!! (sorry about originally overlooking you).
:)
 
Last edited:

pavik62

Senior Member
Apr 20, 2011
580
334
Volgograd
4pda.ru
экранная трансляция не работает. The TV doesn't find it.
 

Attachments

  • Screenshot_20210416-211358_Settings.png
    Screenshot_20210416-211358_Settings.png
    79.3 KB · Views: 246

mangokm40

Senior Member
Jan 13, 2019
223
124
Just clean installed... all is working good except I cant get GPS going nor can I get safetynet to pass in magisk

Anyone any idea on how to fix?

I just turned my phone on. Using GPS Test (chartcross), I had over 20 satellites in view within 2 seconds. It showed over a dozen satellites 'connected' within 15 seconds. But, it took about a minute to get a 3D fix.
This is indoors, in a single-story structure. It's a clear day.

I don't have any custom kernel or GApps. Just latest of this ROM and Magisk 22.1.

I know this helps you ..... none at all. It's just a data point, in case it matters.
 

mmsp15

Member
Dec 11, 2018
28
10
LG V20
Samsung Galaxy S21 Ultra
I just turned my phone on. Using GPS Test (chartcross), I had over 20 satellites in view within 2 seconds. It showed over a dozen satellites 'connected' within 15 seconds. But, it took about a minute to get a 3D fix.
This is indoors, in a single-story structure. It's a clear day.

I don't have any custom kernel or GApps. Just latest of this ROM and Magisk 22.1.

I know this helps you ..... none at all. It's just a data point, in case it matters.
no custom kernel or anything extra either... gonna try another clean load tonight with of course magisk and mindthegapps package and hopefully that fixes else its back to the last build of 17.1 for me for a while :/

UPDATE: A fresh install seems to have fixed GPS (not safetynet yet)... downloaded the newest mindthegapps just in case no idea if that helped or not but GPS working again... I will say however it does take 18.1 a lot longer to get your location than 17.1 did... hopefully this will be fixed some in the future versions :) either way good job LOS team :D
 
Last edited:
Feb 23, 2021
12
2
Noob question. Can i install this rom on my h990n?

Before this, i used lgup to downgrade with nougat 990ds aus rom. It installed but got error at setup wizard. Something about modem not compatible. So now i assume 990ds ≠ h990n even though both are similar
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 24
    lineage-os-logo.png

    LG V20

    Code:
    - Your warranty is now void.
    - You have been warned.
    - Use at your own risk.

    Introduction:
    This is the Official Lineage OS 18.1 thread for the LG V20.

    Downloads:
    Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
    If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

    Known Bugs:
    • IMS (VoLTE/Wi-Fi Calling) doesn't work due to framework tie-ins used by the LG proprietary binaries.
    • Find any? Report them according to this guide.
    Notes:
    • The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
    Kernel Source: https://github.com/LineageOS/android_kernel_lge_msm8996
    10
    Okay, I just merged a literal TON of changes for LGE 8996, please watch for regressions - display should be much more smooth with less artifacting.

    Also, 19.1/20 are in the (long term) works for this set of devices, as the 4.4 kernel port is finally mature enough to use.
    9
    Or don't.

    This is a Lineage thread.

    Just use it for that. Go elsewhere for other stuff.
    ***Moderator Announcement***

    Remember that the developers who make XDA their home are some of our most valuable resources. Treat them with respect. Don't demand support for external projects; developers are not obligated to share or support anything beyond their own prerogative.

    Further, remember that you are entitled to absolutely NOTHING. Our developers work for free, and therefore owe you NOTHING.

    Lastly, keep posts ON TOPIC. Do not promote anything external to the subject matter of the thread, and do not derail the thread into arguments.

    This thread is ONLY for LineageOS 18.1 on the LG V20. If you have questions regarding TWRP, take them to the TWRP thread. Sames goes for SHRP or any other project. The developer has made this clear.
    6
    On my LG v20 H910 with LOS 18.1 lineage-18.1-20210722-nightly-h910-signed.zip
    (nothing else installed, no gapps, no mods, no root, etc...) the "LOS SNAP CAMERA" VIDEO record sound volume is almost 0%

    SAME ISSUE ON Lg v20 H918 !!!!!!! I have that phone also.

    After days of research and playing with mixer_paths_tasha.xml settings I gave up..... PROBLEM VERIFIED: its a LOS snap camera apk issue.

    Then I installed ROM [android 11] UNOFFICIAL SuperiorOS-Xcalibur

    https://xdaforums.com/t/rom-h910-h918-us996-h990-vs996-11-unofficial-superioros-xcalibur.4248255/

    COMING FROM LINEAGE/RR:

    1. Boot into twrp
    2. Do a regular wipe (not format)
    3. Flash Superior zip
    4. Flash magisk (optional but recommended)
    5. Wipe dalvik
    6. Reboot

    CAMERA VIEDO WORKS PERFECT !!!!
    PERFECT SOUND !!!



    To LOS maintainers: Fix the LOS SNAP CAMERA apk or quit screwing around with programming android ROMs. Simple as that. I am a MSEE engineering manager and if I cant do my job right I don't do it at all.


    The LOS snap camera has been broken for a very long time (years) and many people have had to use GCAM or Open Camera and all these people including myself are sick that LOS maintainers can't fix a simple but very important apk in LOS (CAMERA video sound issue). This is well documented all over LOS wiki and github etc.....

    FROM: bernardobas, Senior Member


    "Hi @npjohnson
    Open Camera (and BSG GCam 8.1) uses unprocessed-mic by default to get audio while recording video."


    I am done with LOS until this is fixed. YOU ARE WASTING MY TIME
    Yeah, considering h910/h918 are near identical, makes sense that they both suffer.

    By your own statement, you're an engineer, and should be able to discern based on the info you gave me that it is _not_ an issue with the "Snap Camera apk", instead that we are using compressed audio path, and clearly it isn't processing right (likely a codec issue like I mentioned several posts ago). We could swap it to unprocessed mic input, but that will be garbled and awful - only using that as a last resort as opposed to actually fixing the compressed audio route.

    As for the insults launched - k, stop using lineage then. I literally have not a care in the world whether you use it. I'm doing hard work for free, which, as an engineer, you should understand is often thankless, and your naggy/attacking comments only make me want to never touch the device again :)

    I'll be looking at it sometime this week, but for everyone else on this thread who has been kind and supportive lol.
    5
    On my LG v20 H910 with LOS 18.1 lineage-18.1-20210722-nightly-h910-signed.zip
    (nothing else installed, no gapps, no mods, no root, etc...) the "LOS SNAP CAMERA" VIDEO record sound volume is almost 0%

    SAME ISSUE ON Lg v20 H918 !!!!!!! I have that phone also.

    After days of research and playing with mixer_paths_tasha.xml settings I gave up..... PROBLEM VERIFIED: its a LOS snap camera apk issue.

    Then I installed ROM [android 11] UNOFFICIAL SuperiorOS-Xcalibur

    https://xdaforums.com/t/rom-h910-h918-us996-h990-vs996-11-unofficial-superioros-xcalibur.4248255/

    COMING FROM LINEAGE/RR:

    1. Boot into twrp
    2. Do a regular wipe (not format)
    3. Flash Superior zip
    4. Flash magisk (optional but recommended)
    5. Wipe dalvik
    6. Reboot

    CAMERA VIEDO WORKS PERFECT !!!!
    PERFECT SOUND !!!



    To LOS maintainers: Fix the LOS SNAP CAMERA apk or quit screwing around with programming android ROMs. Simple as that. I am a MSEE engineering manager and if I cant do my job right I don't do it at all.


    The LOS snap camera has been broken for a very long time (years) and many people have had to use GCAM or Open Camera and all these people including myself are sick that LOS maintainers can't fix a simple but very important apk in LOS (CAMERA video sound issue). This is well documented all over LOS wiki and github etc.....

    FROM: bernardobas, Senior Member


    "Hi @npjohnson
    Open Camera (and BSG GCam 8.1) uses unprocessed-mic by default to get audio while recording video."


    I am done with LOS until this is fixed. YOU ARE WASTING MY TIME
    Maybe you should go back to stock? You do realize we do this for free and on our own time? If there are any issues we try to fix them ASAP but with your comments I doubt @npjohnson is going to want to support the device anymore. If there is any issue I would recommend reporting it in a less-hostile way and it might be a simple fix rather than insulting the primary dev for LOS on the device who may now not want to support the device anymore...