• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[ROM][OFFICIAL][d85x, f400, ls990, vs985] LineageOS 18.1

Search This thread

Zirila

Senior Member
Jul 31, 2015
161
59
I'm still struggling with WiFi and standby.

With LineageOS v18.1 I'll always lose Wifi after a few minutes the screen turned off. I'll get no messenger notifications, internet radio apps stop working, whatsapp desktop loses connection to the phone after a while, and whatever needs an internet connection gets interrupted.

This used to work in LineageOS 17.1.
in 17.1 there was also the option "keep Wi-Fi on during sleep" in the advanced wifi settings. This option is now missing.
however adb shell settings get global wifi_sleep_policy is returning "2"
this means "always on". obviously this setting doesnt change anything related to the problem.

I also made sure there is no battery saving involved with the used apps.

anybody with similar experience?
 
  • Like
Reactions: klaus-hamburg

Ph3ar.

Senior Member
Apr 16, 2016
295
148
I've tried sideloading, I've tried pushing to /sdcard and installing from there, I've tried copying to an actual SD card and installing from there. The result is the same each time: it doesn't boot. Latest version of TWRP (3.5.2), flashing just the OS image, nothing else.

But I've decided to give up with this phone, I've had enough of bashing my head against it.
Sorry to hear it's been giving you a frustrating time. Would you be willing to give 16 a try just to see if it would boot? 17 did have some early issue with rebooting to recovery. I use the LS990 so I can't help much but I do know v16 ran and booted like a charm. If you tried 16 and had the same problem I would think something is just stuffed up with your device . if it booted then that would offer hope. have you tried installing clean rom one time ? Sometimes erroneous factors can have a device stuffed up so to speak. Did you come straight from stock or were you running 16 in the past ?
 

avf32

New member
May 18, 2021
3
0
Sorry to hear it's been giving you a frustrating time. Would you be willing to give 16 a try just to see if it would boot? 17 did have some early issue with rebooting to recovery. I use the LS990 so I can't help much but I do know v16 ran and booted like a charm. If you tried 16 and had the same problem I would think something is just stuffed up with your device . if it booted then that would offer hope. have you tried installing clean rom one time ? Sometimes erroneous factors can have a device stuffed up so to speak. Did you come straight from stock or were you running 16 in the past ?
Trying 16 was suggested to me before, but I couldn't find anywhere to download it.

It didn't run any custom ROMs in the past, as far as I'm aware. When I got it, it was running stock Android 4, although it was rooted. I upgraded it to Android 6 (via 5) using LG Mobile Support, but then I couldn't find a way of rooting that version or unlocking the bootloader, so I reflashed version 4 using LG Flash Tool and went from there.

I'd love to understand more about how the previous Android version might affect installing a custom ROM. From my naive x86 PC point of view, if it's not on the disk, then it doesn't matter, so I'm struggling to understand how it makes a difference. Does a later version of Android update firmware in the hardware, or something, which isn't visible by examining the partitions? Or do not all partitions get overwritten when installing a custom ROM? I did notice that I couldn't even get TWRP to work when I first got the device, and it only started working when I went through the 4->5->6->4 cycle.

Another thing that came up is partitions. It seems that newer phones have A and B partitions, system_a/system_b, recovery_a/recovery_b, etc. My phone only has system, recovery, boot, etc. Also, something about a "super" partition in Android 10 has been mentioned. Might this be the cause of my issues, and if so, do I need to run a script or something to repartition the flash before installing a custom ROM? I'm surprised that I couldn't find much information about this point out there.

Thanks!
 

Ph3ar.

Senior Member
Apr 16, 2016
295
148
Trying 16 was suggested to me before, but I couldn't find anywhere to download it.

It didn't run any custom ROMs in the past, as far as I'm aware. When I got it, it was running stock Android 4, although it was rooted. I upgraded it to Android 6 (via 5) using LG Mobile Support, but then I couldn't find a way of rooting that version or unlocking the bootloader, so I reflashed version 4 using LG Flash Tool and went from there.

I'd love to understand more about how the previous Android version might affect installing a custom ROM. From my naive x86 PC point of view, if it's not on the disk, then it doesn't matter, so I'm struggling to understand how it makes a difference. Does a later version of Android update firmware in the hardware, or something, which isn't visible by examining the partitions? Or do not all partitions get overwritten when installing a custom ROM? I did notice that I couldn't even get TWRP to work when I first got the device, and it only started working when I went through the 4->5->6->4 cycle.

Another thing that came up is partitions. It seems that newer phones have A and B partitions, system_a/system_b, recovery_a/recovery_b, etc. My phone only has system, recovery, boot, etc. Also, something about a "super" partition in Android 10 has been mentioned. Might this be the cause of my issues, and if so, do I need to run a script or something to repartition the flash before installing a custom ROM? I'm surprised that I couldn't find much information about this point out there.

Thanks!
Rather than go through all of that I would go back to the basics . Maybe start from a clean installation of Android L or M. Then start with 16 . I would root and install an older version of twrp like 2.8 . Then before you attempt anything else make yourself a good nandroid of your stock rom . That way if something goes wrong you can keep restoring that stock rom and have a firm base to return to without having to go through re-rooting and re-installing twrp. . Once you've got that done then maybe someone here will post a link to 16 for you. 17 and both 18 have been a bit contrary with more bugs than 16 had. I think if you can just get 16 working good then try the upgrade path from there to 17 or 18. You won't have to worry about partitions at that point. Hopefully some of the people with your variant will step up with a little advice . The path I'm pointing you on is a solid one but it gets you back to a good point of having the phone at stock , then getting a TWRP from the times on it, then rooting , getting a good nandroid established and going from there. Don't jump ahead with TWRP or the latest Magisk versions until you have to. Version 2.8 to 3.0 of Twrp were nice and stable for 16. Magisk 20.4 was nice and stable as well. From my own experience there are some bugs interacting between the latest roms , magisk and twrp. I haven't been able to determine which of the 3 or even all 3 for that matter . Once you find out if 16 works then make another good nandroid at that point. protect that step before you try anything else . That will give you another toe hold to fall back to. We'll try to help you out. Seeing the bugs and problems with the latest rom, magisk and twrp makes me think you picked a bad time to go from stock to 17 or 18. Focus on 16 for now. Someone please post the man a link to the last v16 lineage build for his variant. . Lets help this fella out.
 
Last edited:

williamvds

New member
Jun 9, 2020
2
0
I've installed (microG) Lineage 18.1, built 7th of May 2021, clean upgrade from an encrypted microG 17.1. It appears to be mostly working:
- I got a decryption prompt on first start up, I assume because internal storage wasn't wiped
- Rotation works but the compass is still broken as it was in 17.1 (tested with "Compass" by Phillip Bobek from FDroid)
- GPS sometimes works, maybe takes a while to get a fix, just as in 17.1 (tested with "GPSTest" by barbeauDev from FDroid)
- Bluetooth doesn't start up

Would the compass and GPS issues be resolved by restoring the original Lollipop firmware? Should I bother going through all that process?

Digging into the logcat I can see an obvious reason for Bluetooth failing:

Code:
05-22 12:52:58.426 12712 12740 E droid.bluetoot: [0522/125258.426453:ERROR:config.cc(104)] config_new: unable to open file '/data/misc/bluedroid/bt_config.conf': No such file or directory
05-22 12:52:58.426 12712 12740 E droid.bluetoot: [0522/125258.426634:ERROR:config.cc(104)] config_new: unable to open file '/data/misc/bluedroid/bt_config.bak': No such file or directory
05-22 12:52:58.426 12712 12740 E bt_btif_config_transcode: btif_config_transcode unable to load XML file '/data/misc/bluedroid/bt_config.xml': 3
05-22 12:52:58.426 12712 12740 E bt_btif_config: init unable to transcode legacy file; creating empty config.
05-22 12:52:58.434 12712 12745 E bt_btif_storage: btif_storage_get_adapter_property: Controller not ready! Unable to return Bluetooth Address
05-22 12:52:58.434 12712 12745 E BluetoothServiceJni: adapter_properties_callback: Status 1 is incorrect
05-22 12:52:59.674  3772  3969 E BluetoothManagerService: MESSAGE_BLUETOOTH_SERVICE_DISCONNECTED(1)
05-22 12:53:01.027 12785 12807 E droid.bluetoot: [0522/125301.027485:ERROR:config.cc(104)] config_new: unable to open file '/data/misc/bluedroid/bt_config.conf': No such file or directory
05-22 12:53:01.027 12785 12807 E droid.bluetoot: [0522/125301.027717:ERROR:config.cc(104)] config_new: unable to open file '/data/misc/bluedroid/bt_config.bak': No such file or directory
05-22 12:53:01.027 12785 12807 E bt_btif_config_transcode: btif_config_transcode unable to load XML file '/data/misc/bluedroid/bt_config.xml': 3
05-22 12:53:01.028 12785 12807 E bt_btif_config: init unable to transcode legacy file; creating empty config.
05-22 12:53:01.035 12785 12812 E bt_btif_storage: btif_storage_get_adapter_property: Controller not ready! Unable to return Bluetooth Address
05-22 12:53:01.035 12785 12812 E BluetoothServiceJni: adapter_properties_callback: Status 1 is incorrect

This might just be a bad build missing the bluetooth config. Could someone send me the stock /data/misc/bluedroid/bt_config.conf? I didn't have much luck searching the LineageOS repositories.


I was having the same issue after reverting back to 17.1, indicating this was an issue with the data partition. Same problem after wiping the "internal storage" in TWRP and reinstalling. Getting the decryption prompts after wiping was suspicious, so I flashed the latest LineageOS recovery and did a clean install. Bluetooth is now working normally.
 
Last edited:

Zirila

Senior Member
Jul 31, 2015
161
59
Regarding the WiFi Issues:

it seems like the issue is related to an issue with Anrdoid 11 and RFC 5006 setting in FritzBox Routers. I managed to fix this issue with a workaround I found here:
https://support.google.com/pixelpho...nden-die-wlan-verbindung?hl=de&msgid=72989707
To anyone reading having the same setup: Pixel 3 / FRITZ!Box 5490: Log into your FRITZ!Box through http://fritz.box/ or http://192.168.178.1/ in my case. AVM FritzBox instruction on the UI. Then go to View: advanced in the bottom, if you haven't already.
  1. Home Network / Network
  2. Network Settings tab
  3. Ip Addresses / IPv6 Addresses
  4. DNSv6 Server in the Home Network / Also announce DNSv6 server via router advertisement (RFC 5006) was enabled in my settings -> disable it and click apply
After that, I had none of the mentioned WiFi issues anymore. luckily.
But the more interesting question is: Why is this setting (RFC 5006) in the router NOW a problem with Lineage18.1/Android11 when it wasn't a problem before with LOS17.1/Android10?
Shouldn't the fix be on LineageOS / Androids side instead of disabling a router DNSv6 setting that is common in millions of devices?
 
  • Like
Reactions: klaus-hamburg

Zirila

Senior Member
Jul 31, 2015
161
59
The default camera app "Kamera" doesn't work when trying to record a video. it says:
"Could not start media recorder. Can't start video recording"

tried wiping all data of the app, resetting all permissions, still not working. any fixes?
 

fubag

Senior Member
Apr 9, 2010
325
49
WV
anyone having issues flashing the latest builds on LineageOS using TWRP that is resulting in super long starting animation boot, that eventually reboot the phone back into the TWRP recovery? I have a D850 for reference

I was fine on the May 14th build but trying 5/28 and 6/4 is resulting in issues now...tried wiping cache/dalvik and no beuno for reboots :'(
 

fubag

Senior Member
Apr 9, 2010
325
49
WV
New issues with latest builds 06-11 on D850...using custom TWRP provided by HardStyl3r; cannot install MindtheGapps 11.0 build for arm...throws up mount system error 1 everytime...any luck for anyone else? I've tried wiping and starting again, no luck
 

hellenicboy

Senior Member
Nov 7, 2010
74
1
Hello all,
I have a d850 rooted. I am coming from android 9 and magisk installed. I installed lineage 18.1 couple months ago and everything is running smooth but phone now shows as not rooted and can't install magisk.
Any thoughts?
Thank you
 

hourwatch

Member
Sep 28, 2014
28
2
EDITED

I have installed this ROM, but it doesn't recognize my SIM. In Lineage 16 worked perfectly, and I have tried another smartphone and works correctly. Any way to fix this?
 
Last edited:

Nexus-3

Member
Feb 28, 2018
8
0
LG G3
Nexus Player
Greetings,

first let met congratulate and thank @HardStyl3r & all the other LineageOS developers for breathing new life into such an old but venerable device!

After OpenGapps finally released packages for Android v11, I attempted to upgrade my LineageOS from v17.1 to v18.1 with little success so far.

My D855 always ends in a login loop, meaning that the arc animation finishes (with the three circles) and the SIM card unlock screen appears BUT 4 seconds later the complete arc reappears and then shows the sim unlock screen again.

Code:
original situation: lineage_os_17.1-2021-04-10 & open_gapps-arm-10.0-pico-20210522
current situation: lineage_os_17.1-2021-04-10 & open_gapps-arm-10.0-pico-20210715



Upgrade combinations tried via TWRP v3.5.2:

lineage-18.1-20210522-nightly-d855-signed.zip
lineage-18.1-20210620-nightly-d855-signed.zip
lineage-18.1-20210710-nightly-d855-signed.zip
lineage-18.1-20210717-nightly-d855-signed.zip


open_gapps-arm-11.0-pico-20210712.zip
open_gapps-arm-11.0-pico-20210713.zip
open_gapps-arm-11.0-pico-20210714.zip
open_gapps-arm-11.0-pico-20210715.zip
open_gapps-arm-11.0-pico-20210717.zip

Comments, hints & suggestions are appreciated.
 

Fractux

Member
Jul 21, 2021
8
3
LG G3
EDITED POST : Trying a few more things before wasting people's time.

Sorry!
 

Attachments

  • LINEAGE - Copy.jpg
    LINEAGE - Copy.jpg
    315.7 KB · Views: 48
  • TWRP - Copy.jpg
    TWRP - Copy.jpg
    311.7 KB · Views: 46
  • TWRP-term - Copy.jpg
    TWRP-term - Copy.jpg
    338.7 KB · Views: 45
Last edited:

kmambu

Member
Feb 1, 2020
5
0
Hi everyone,
First of all, thank you @HardStyl3r for the Custom ROM, it installed without any issues 😁
The phone is running OK overall but feels laggy at times, would anyone know how to improve the performance of my installation ?
I reduced the resolution through LineageOS settings and it helped a lot, bu it seems like the kernel installed by default s a little bit restrictive regarding CPU frequency 🤔
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Sorry for the late reply.
    Any replies are appreciated, thanks!

    Is this your device and possible Kitkat ?
    Yep, it's the LGD852G.

    Sadly, I've been to almost all those links. I'll check a few more there. I've not had much time today, sadly. On LGROMS, the KITKAT .kdz is a non functioning link sadly, and I wrote to them asking about it, but no reply.

    Most of those links in the google search are already purple (I have been scouring.. lol ), but I'll check all of the one's I may not have visited yet. Thanks for that.

    My model is from Videotron here, and so for a kit kat Firmware I'm looking at any D852G_V10 XXXXXX.kdz . The ones I've tried from LGD852's just brick the phone sadly (It gets stuck in a bootloop), and so does the only D852G_v10.tot file I've found. I've had to recover from hard bricks several times using BoardDiag.

    There is a post here about my phone, but links are all dead, or point to invalid downlaods. https://forum.xda-developers.com/t/quebec-lg-g3-d852g-videotron.2970938/ . Now I found a copy of LGD852GAT-01-V10c-302-500-JUL-15-2014+0.tot , but it bricked the phone, and using those aboot.img and laf.img to bump the boot image, still resulted in teh same problem. TWRP just can't see the block device/storage.

    So I'm looking for D852G10e hopefully, or another kdz, if I use that old post as a reference.

    The problem with TWRP not seeing any storage on the phone happened before the hard bricks, so having to unbrick was not the cause of this current inability to see the phone's storage.

    I'll pour through more links and try more as I can, thanks.

    ---
    One thing that hit me when I was unbricking again yesterday after another KitKat attempt, was that the circuit board itself has "D850" etched on it, so maybe I'll try rounds of D850.kdz I can find to see if those work.

    At least I know how to unbrick the phone, so I'm not worried about taking the risks. :D
    1
    @Fractux Maybe just try reflashing your entire device with LGUP or something and start over.

    I've tried like 10 times from a fresh re-flash of the lollipop rom, at this point.

    /me bangs head against wall. :D

    I'm wondering if there's maybe another ROM I can try flashing, other than the stock D852G that will work on the phone as a starting point?

    I can't find a working full KitKat .kdz/.tot so far to try on this phone. Many dead links, and no replies to direct messages asking if people had a copy tucked away for the 852G.

    I hope to have some time today to plunk around again.

    Thanks again for all the suggestions. I really appreciate it.
  • 16
    V1KTmBM.png



    Code:
    /*
    * 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.
    */

    sFC1ljz.png

    LineageOS 18.1 is a free, community built, aftermarket firmware distribution of Android 11 (R), which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    The source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features

    Lin·e·age
    /ˈlinēij/
    noun
    1. lineal descent from an ancestor; ancestry or pedigree.
    2. a sequence of species each of which is considered to have evolved from its predecessor.

    F2KbTDc.png

    If you encounter any issues with sensors or anything related to hardware, please flash stock rom and then a custom one.
    Check the G3 issue tracker and LineageOS issue tracker before installation.
    Clean flash is recommended, here's the procedure:
    • wipe Dalvik cache, /system, /data and /cache.
    • flash latest ROM zip
    • optional: flash Google apps ARM

    TK3TVvO.png

    Download LineageOS 18.1
    TWRP
    Open GApps ARM BETA BUILDS
    Rooting your phone by Linus Tech Tips
    Stock ROM by @MESA
    3__HacerPermisivo.zip - this switches your selinux to permissive
    bootimage_adb_unsecure by @AdrianDC - debugging, disables adb auth
    Mr_Bump.zip by @dadi11 - fix for Secure booting error (boot certification verify)

    Nh9aiVb.png

    Join G3 development channel on Telegram to get more info about my projects.

    Onx1GCn.png

    @dadi11
    @walter79
    @aleasto

    DPxaQu8.png

    github.com/LineageOS
    github.com/itsHardStyl3r
    device and kernel sources
    local_manifests
    Important: information about open sources from HardStyl3r
    7
    A new update (for a short while) before we'll have official builds. Once the builds are available to download, I'll convert this thread to Official and close 17.1.
    Enjoy.
    5
    New update. Changelog is in the #2 post.
    If no bugs are reported, I'll push the changes to gerrit and hopefully, we'll get official LineageOS 18.1.
    3
    @HardStyl3r , I flashed the new 18.1 build along with the open test gapps on my LS990 . I have to say it's running great so far. Things I've checked and work fine are data, wifi , telephony, camera( both camera and video) and GPS. All work good without any lag or issue. I also rooted with magisk . Had no problems whatsoever with TWRP either. I went through the whole setup process of entering account and restoring all apps from the cloud. GPS locks in super fast and finds lots of satellites . I tried the first 18.1 build you put out and while most stuff worked I can tell this build is smoother and improved. Thanks for all your efforts .

    Warning to all TWRP users ::: . During setup on 18.1 you' must be careful not to check the box offering to update Lineage Recovery . If your on TWRP and you check this box you''ll lose your TWRP .
    3
    Auto update didn't find new version. Attempted a dirty flash of rom only, which resulted in boot loop. Did full wipe, flash rom, bitgaps and magisk and is working very nicely. Thanks HardStyler.

    Auto update will not work until the rom eventually goes official.