• 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][montana][11] LineageOS 18.1

Search This thread

mattdpollard

Member
Sep 9, 2020
22
4
I think this ROM is abandoned... =(
I'm going back to the Stock ROM.
It's updated weekly so hardly abandoned, I think!

As far as I understand, once it went official, bugs were to be reported on gitlab, not in this thread. https://gitlab.com/LineageOS/issues/android/-/issues?scope=all&state=opened

This is what we are told to do in the first post in this thread.

So the ROM is active but this thread isn't the main place to raise issues.

I don't know if anyone has raised the OTA update issue in the official bug reporting system, I hadn't until now as it isn't an urgent issue for me. But if you want it fixed as far as I understand that is the place to report it, so I have just reported it as an issue there.
 
Last edited:

jaysonwcs

Member
Apr 21, 2020
9
1
Moto G5S
It's updated weekly so hardly abandoned, I think!

As far as I understand, once it went official, bugs were to be reported on gitlab, not in this thread. https://gitlab.com/LineageOS/issues/android/-/issues?scope=all&state=opened

This is what we are told to do in the first post in this thread.

So the ROM is active but this thread isn't the main place to raise issues.

I don't know if anyone has raised the OTA update issue in the official bug reporting system, I hadn't until now as it isn't an urgent issue for me. But if you want it fixed as far as I understand that is the place to report it, so I have just reported it as an issue there.
Oh, I didn't know that.
I will do that.

Thanks!
 

mattdpollard

Member
Sep 9, 2020
22
4
The OTA update failure continues with today's build (19 July 2021).
I opened a bug report here last week as per the instructions in the first post in this thread, but it does not appear to have been assigned yet: link

Out of curiosity, is there anyone on this thread who is still able to successfully update using in the built-in app?
 

newinnov

Senior Member
Sep 11, 2012
222
52
Hi Jarl,

Montana does not support VoLTE with "vi" carrier, Every time call comes devices switches to 3g instead of taking volte call.
4g bands are supported by g5s too ie - B1, B3, B5, B41 .

Is volte working fine for you guys?
 

newinnov

Senior Member
Sep 11, 2012
222
52
The OTA update failure continues with today's build (19 July 2021).
I opened a bug report here last week as per the instructions in the first post in this thread, but it does not appear to have been assigned yet: link

Out of curiosity, is there anyone on this thread who is still able to successfully update using in the built-in app?
As far as I know , ota update is broken at present for several devices not just for montana with lineage, it used to work fine for older android versions though. SO may be problem with lineage side...
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Thank you! Just curious, what was the core reason of the issue?
    It was a problem with the F2FS driver.
    1
    hello,
    OTA update not working for me again.
    After downloading files, and beginning installation, i got the messages in recovery:

    E:Error opening trace file: No such file or directory (2)
    E:Failed to read /cache/recovery/block.map: No such file or directory
    E:Map of '@/cache/recovery/block.map' failed
    E:failed to map file
    E:Error exit from the fuse process: 1
    Installation aborted.

    OTA installation was working before, i used Lineage recovery on my phone, and system updater which downloaded 685MB package.
    Any tips how to apply the update, and make OTA work again?
    Many thanks in advance
    Same error AGAIN, trying to update to 5-7-2021 version.

    EDIT: typo
    1
    Hello, would one (or more) of you mind posting an output of adb shell dmesg -w after attempting the OTA update and enabling ADB in recovery?
    Hi thanks very much JarlPenguin! I have sent it to you in a message.
    1
    Thanks to all of you for reporting the issue. It's now been identified and fixed. You'll still have to sideload the next build but updates after that should flash OTA fine.
  • 3
    2okPze5.png

    Code:
    #include <std_disclaimer.h>
    
    /*
    * Your warranty is now void.
    *
    * We are 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 us for messing up your device, we will laugh at you.
    *
    */

    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.

    Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.

    Instructions:
    • Download the latest build, recovery image and GApps (if you need them)
    • Flash the downloaded recovery image via fastboot
    • Boot to recovery
    • Format system and perform a factory reset
    • Reboot to recovery
    • Flash the latest build
    • Flash GApps and any other necessary add-ons

    What's working:
    • WiFi
    • Camera and Camcorder
    • Bluetooth
    • NFC
    • Fingerprint - Oreo firmware required
    • GPS
    • OTG
    • Video Playback
    • Audio
    • RIL
    • VoLTE/VoWiFi
    • USB tethering/audio
    • SELinux: Enforcing

    Known issues:
    • You tell me

    Downloads:

    Reporting Bugs
    • All bugs should be reported here: Issue Tracker
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download url:
    Gapps version:
    
    Did you--
    wipe:
    restore with titanium backup:
    reboot after having the issue:
    
    Are you using--
    a task killer:
    a non-stock kernel:
    other modifications:
    
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

    Thanks to:
    @GivFNZ for testing my builds
    @wiktorek140, @karthick mostwanted, @wh0dat, @KalilDev, @AsD Monio, @GoldeneyeS2, @Steve Mathew Joy and @rajatgupta1998 for their hard work on our device sources
    LineageOS team

    Changelogs:

    Code:
    2021-04-08:
    Initial 18.1 build.
    
    2020-10-13:
    Initial release.


    Source code:
    3
    I've uploaded a build for LineageOS 18.1. Official status will be gained shortly after we've tested things on a wider variety of devices.
    2
    I'm not rushing him for updates, just a question to mention that someone still with some interest on his ROM
    I will continue with this project, but only after the 18.1 source is fully ready.
    2
    Thank you! Just curious, what was the core reason of the issue?
    It was a problem with the F2FS driver.
    1
    Help..!!!
    Stuck here for last 3 hours Any solution
    Format your /data partition.