[ROM][H910|H918|LS997|US996|VS995|H990*] UNOFFICIAL LineageOS-16.0 for LG V20

Search This thread

nwananka001

Member
Apr 15, 2020
18
4
GCAM 7.3

Ive been testing GCAM 7.3 for weeks now usint H918 and the one that worked for me is
trCamera_V4_Stay_Safe_Lite_Google_Lib_only
change the front camera to Nexux6P(...default setting/model settings)
 

iTzFeRReTTi

Senior Member
Jun 14, 2012
1,435
387
Boston
LG V20
Ive been testing GCAM 7.3 for weeks now usint H918 and the one that worked for me is
trCamera_V4_Stay_Safe_Lite_Google_Lib_only
change the front camera to Nexux6P(...default setting/model settings)
There's also many others that work but if you're still on LOS 16, then your options may possibly be limited due to Android 10 introducing new APIs and features. I'm on Android 10 and most of the GCam 7.3 builds work just fine for me.
 

nwananka001

Member
Apr 15, 2020
18
4
There's also many others that work but if you're still on LOS 16, then your options may possibly be limited due to Android 10 introducing new APIs and features. I'm on Android 10 and most of the GCam 7.3 builds work just fine for me.

I have installed all the versions of the 17.1 Rom for my H918 device and the Gcam 7.3 though "works", front camera pics come out blurry. the one i mentioned is the only one that doesn't have blurry front camera pics. I only stepped down to LOS 16.0 because bluetooth call doesnt work for my device.
 

aCIDsLAM

Senior Member
Feb 7, 2015
101
24
Filesystem

Is there any way, i can get the rom to use another filesystem besides exfat on ext SD? I am getting corruption errors often with that filesystem on my SD. Forcing me to connect it to a PC, repairing the card,
before the LG V20 can use it again.
 

mangokm40

Senior Member
Jan 13, 2019
135
68
Is there any way, i can get the rom to use another filesystem besides exfat on ext SD? I am getting corruption errors often with that filesystem on my SD. Forcing me to connect it to a PC, repairing the card,
before the LG V20 can use it again.

Well, you could just format the SD card from LOS. This will not allow you to store files over 4GB, though.
 

pm23

Member
Jul 17, 2008
17
10
I have the same issue with Los 17.1...can you confirm that bt calling and everything else works fine on Los 16?
 

mangokm40

Senior Member
Jan 13, 2019
135
68
You mean inside the system, not TWRP? But wouldnt that be exfat too?
Maybe there is a way with magisk to add a filesystem?

If you format the SD from Android itself, you don't get exfat. As I mentioned though, that means limit file size ~4GB.

In LOS16, the standard 'Files' app has a 3-dot menu.
After selecting your SD card from the main (3-line menu), you'll be in the top folder of SD card.
Hit the 3 dot menu and Storage settings->Format
 

lybxlpsv

Senior Member
Oct 9, 2013
77
67
Camera does not work

I'm back from H990DS Latest Stock Oreo, LG UP to v10c and it seems LOS16.0 and LOS17.1 doesn't have working camera at all.
The same build was working before.
Kernel seems to fail when initializing camera looking at the dmesg.
LOS15.1 works just fine
Attached dmesg and logcat.
Hope this helps so that we don't rely on SELinux Permissive.
Code:
[   16.317699] ------------[ cut here ]------------
[   16.317734] WARNING: CPU: 3 PID: 1322 at ../../../../../../kernel/lge/msm8996/fs/sysfs/dir.c:31 sysfs_warn_dup+0x64/0x7c()
[   16.317755] sysfs: cannot create duplicate filename '/devices/soc/8c34a0.qcom,gdsc/regulator/regulator.78/a34000.qcom,csiphy-gdscr'
[   16.317774] Modules linked in:
[   16.317812] CPU: 3 PID: 1322 Comm: CAM_startsensor Not tainted 3.18.113-perf-ga396e465c32-dirty #31
[   16.317831] Hardware name: Qualcomm Technologies, Inc. MSM 8996 v3.x + PMI8996 MTP (DT)
[   16.317852] Call trace:
[   16.317887] [<ffffffc000207a34>] dump_backtrace+0x0/0x254
[   16.317908] [<ffffffc000207a2c>] show_stack+0x18/0x20
[   16.317931] [<ffffffc0004d1218>] __dump_stack+0x20/0x28
[   16.317951] [<ffffffc0004d11d4>] dump_stack+0x60/0x84
[   16.317972] [<ffffffc0002230f0>] warn_slowpath_common+0xa4/0xe8
[   16.317991] [<ffffffc000223028>] warn_slowpath_fmt+0x50/0x74
[   16.318012] [<ffffffc000397f40>] sysfs_warn_dup+0x64/0x7c
[   16.318031] [<ffffffc0003981cc>] sysfs_do_create_link_sd+0x90/0xcc
[   16.318049] [<ffffffc000398248>] sysfs_do_create_link+0x28/0x38
[   16.318068] [<ffffffc000398218>] sysfs_create_link+0x10/0x18
[   16.318091] [<ffffffc00063a448>] create_regulator+0xbc/0x210
[   16.318113] [<ffffffc000636114>] _regulator_get+0x160/0x20c
[   16.318134] [<ffffffc000635fac>] regulator_get+0x14/0x1c
[   16.318164] [<ffffffc0009d9b4c>] msm_camera_config_vreg+0xe4/0x300
[   16.318192] [<ffffffc0009ec9b8>] msm_csiphy_subdev_ioctl+0x170/0x10b8
[   16.318219] [<ffffffc0009edd68>] msm_csiphy_subdev_do_ioctl+0x68/0x94
[   16.318245] [<ffffffc0009763d4>] video_usercopy+0x194/0x544
[   16.318265] [<ffffffc0009ec840>] msm_csiphy_subdev_fops_ioctl+0x14/0x1c
[   16.318288] [<ffffffc000982298>] v4l2_compat_ioctl32+0x74/0xac
[   16.318311] [<ffffffc000376de4>] compat_SyS_ioctl+0x3b4/0x16c0
[   16.318331] ---[ end trace fdf697ee976e98bb ]---

[   26.253767] Call trace:
[   26.254015] [<ffffffc000207a34>] dump_backtrace+0x0/0x254
[   26.254194] [<ffffffc000207a2c>] show_stack+0x18/0x20
[   26.254367] [<ffffffc0004d1218>] __dump_stack+0x20/0x28
[   26.254509] [<ffffffc0004d11d4>] dump_stack+0x60/0x84
[   26.254667] [<ffffffc0009dfda8>] msm_post_event+0x3fc/0x4bc
[   26.254822] [<ffffffc0009e1930>] camera_v4l2_open+0x294/0x3c8
[   26.254969] [<ffffffc0009758f0>] v4l2_open+0x9c/0xe4
[   26.255116] [<ffffffc0003311dc>] chrdev_open+0xb4/0x198
[   26.255263] [<ffffffc00032b32c>] do_dentry_open+0xf8/0x2b4
[   26.255408] [<ffffffc00032b55c>] vfs_open+0x64/0x78
[   26.255549] [<ffffffc00033c710>] do_last+0x890/0xe28
[   26.255676] [<ffffffc0003369c0>] path_openat+0xbc/0x5b4
[   26.255810] [<ffffffc000336890>] do_filp_open+0x40/0xb4
[   26.255942] [<ffffffc00032ba10>] do_sys_open+0x144/0x250
[   26.256093] [<ffffffc000375694>] compat_SyS_openat+0xc/0x14
 

Attachments

  • dmesg.txt
    241.6 KB · Views: 11
  • logcat.zip
    66.6 KB · Views: 17
Last edited:

Pheckphul

Senior Member
Sep 19, 2014
61
6
SF Bay Area
Moto G 5G
v14.1 and v17.1 are officially supported

No more security patches? last one i saw was in May.

The V20 series is officially supported by LinneageOS, with v14.1 and 17.1 available for all hardware, except the us996, which only has 17.1. Maybe you should consider moving to one of those?

I'm running an old version of v15, and haven't upgraded my h918 to an officially supported version, but I'm considering it. I like security patches. They are the only reason I'd consider an iPhone, because I'm tired of Android vendors' ****ty support. When there no longer is LinneageOS/decent community support for the V20 there is a good chance I, with very, very much reluctance, move to an iPhone.
 

nwananka001

Member
Apr 15, 2020
18
4
I am different coz i dont really care for security patches, i rather have tools like privacy guard that i can use to control app permission and behaviour. I have used all versions of the rom on my phone h918. The reason i am back on 16.0 is because 17.1 doesn't have Bluetooth calling for bt 4.0+. Once that is resolved, i am definitely going to use it.
The V20 series is officially supported by LinneageOS, with v14.1 and 17.1 available for all hardware, except the us996, which only has 17.1. Maybe you should consider moving to one of those?

I'm running an old version of v15, and haven't upgraded my h918 to an officially supported version, but I'm considering it. I like security patches. They are the only reason I'd consider an iPhone, because I'm tired of Android vendors' ****ty support. When there no longer is LinneageOS/decent community support for the V20 there is a good chance I, with very, very much reluctance, move to an iPhone.
 

mcsmart

Senior Member
Aug 8, 2011
152
108
@x86cpu Would it be possible for you to fire up the compiler again in order to update the 16.0 build with merged security patches? That would be awesome :good: 16.0 is rocking the V20, it's much better than stock.

For me 17.1 is way too unstable (lockscreen freezes, BT calling not working, Wifi crashes) so I am going to stick with 16.0 for a while.
 

Lavosu

New member
Jun 8, 2016
3
0
Can anyone offer me some advice? I am currently looking to update my Lineage 16.0 version to the most current one. However, I am unsure if my phone is on ARB 0 or 1.

I've tried to check using ADB and FastBoot, with command "fastboot getvar anti". It returns "anti: (blank)"

Is that fastboot command's output indicative of an ARB0 device? Is there any other method to check ARB version?
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 78
    yUIn6TF.png

    WARNING: BETA BUILD. There are numerous issues still.

    Disclaimer

    Your warranty is now void.
    I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.

    Nougat firmware needed for fingerprints to work correctly : https://forum.xda-developers.com/showpost.php?p=79342931&postcount=939

    Introduction

    LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device. More info.


    These are my UNOFFICIAL builds of LineageOS-16.0 for LG V20 variants. I did NOT create this ROM. I am helping to contribute to this ROM. Thanks to all other coders who contributed to LineageOS.

    IMPORTANT

    • BACKUP! These are UNTESTED builds. Please be ready to recover your previous ROM. If it kernel panic, boots into bootloader, etc... grab as much info as you can.
    • Builds are done periodically (see download below)
    • Do NOT be rude.
    • Respect all users.
    • Any and all users, please help each other. I have a us996 variant, so other variants might have some issues.



    For broken issues see 2nd post

    Issues:

    • us996 static on boot: Unlock bootload from LG, using dirty Santa causes static on boot, will not fix. (Flash the us996-DS version)
    • WiFi or Bluetooth MAC is "00:00:00:00:00:00" - You wiped the misc partition, you'll need to fix: https://forum.xda-developers.com/showpost.php?p=70474540&postcount=12 (Should be fixed by static hax thanks for @Blaises)
    • 5Ghz tether not working due to "error"
    • H918 - ARB1 .. flash the 10p version, ARB0..flash the PRE10p. (10p is where the ARB got tripped to 1)

    Install
    • You can upgrade from 15.1 (UNOFFICIAL) to 16.0. If you are not on my UNOFFICIAL yet, flash the to-x86cpu.zip first (and reboot recover before upgrade, not reboot into system).
    • I would suggest the TWRP from Phoenix591 (See Thanks section below)
    • Flash to-x86cpu.zip if needed. (See Downloads below)
    • Flash UNOFFICIAL ROM
    • Wipe cache, and dalvik cache
    • Magisk if you choose
    • Flash GAPPS (I use nano)
    • Reboot and wait....

    (Copied from OFFICIAL thread)
    To enable Developer Options go to Settings, About Phone and repeatedly press Build Number.


    Bugs
    If you encounter issues/bugs that are not known, please report. This is not the OFFICIAL ROM, but I can help to get any issues fixed. I use the us996 variant. If I can replicate your issue then I can track it down. If I cannot, please provide as much detail as possible. Logcats are great.
    Please indicate what v20 variant you have (h910, h918/p, ls997 us996, vs995, h990/ds) athe dated version. Any mods (no judgment) as well.
    I am aware people run mods or change things. I am not against it (as I do myself). However, if needed I may ask you to data wipe (you can say no), or remove a mod that might be interfering. I will do the best I can.


    Thanks


    Downloads
    ROM: UNOFFICIAL downloads (Note date)
    Gapps: arm64 nano 9.0


    Sourcesrs/0B51rjK5Hd_P5NmpwY1o4VmlyaUk


    UNOFFICIAL downloads
    46
    Issues

    WARNING: This build is running in permissive mode.

    What is working:

    What is NOT working:
    • VoLTE and WiFi calling do not (and most likely never will).
    • 5.0 Ghz Hotspot (still)
    • Bluetooth will fail if you wipe (clean flash).
    • NFC
    • IR
    • Encrpytion is untested, so it may fail.
    • Fingerprints will only work until a reboot. You can then enroll again. If you get an error in enrolling, the fpdata is "full", and you will need to do the following as root and reboot. You can then enroll again:
      Code:
      rm /data/system/users/0/fpdata/user.db
      rm /data/system/users/0/settings_fingerprint.xml
    • Most likely safteynet will fail. This build is in permissive mode, unsure if anything can help to fake it (nor will I try).
    • Gamma Kernel will not work without updates to it. Camera will definitely break.


    Anything else NOT listed above might or might not work. I will adjust as necessary and reports. If anyone has any knowledge and can troubleshoot and fix the NOT working items, let me know.
    27
    Here you go guys, the first Lineage 16.0 test builds for Gamma Kernel:

    https://www.androidfilehost.com/?w=files&flid=286757

    Let me know what you guys find out ;)... I will create a separate thread after we know there are no weird things going on and the weird ones get fixed. Hopefully we can help out with a few things as we all begin testing LineageOS 16.0 for our beloved V20!

    UPDATE: Fixed link... oops!
    24
    lineage-16.0-20190514-X86CPU

    lineage-16.0-20190514-X86CPU

    • May security update.
    • Fixed issue with deep sleep.
    • Added 3 finger swipe screenshot (settings/system/advanced/gestures to enable)
    24
    lineage-16.0-20190327-X86CPU

    lineage-16.0-20190327-X86CPU

    NOTE: The h990 is the last in the build, it crossed the GMT date, so it labeled lineage-16.0-20190328-X86CPU

    • Brightness adjustment try.
    • I hope (and needs testing), that Bluetooth/WiFi work now on a clean (data wipe) flash. This means no more having to come from 15.1.
    It took way to much time to track down the issue with getting Bluetooth address on a reset.