[ROM][OFFICIAL][enchilada][13] LineageOS 20

Search This thread

lord high executioner

Senior Member
Jan 8, 2014
63
18
Just a heads-up:
Today's update stuck at "100% preparing first boot" (or similar, last step before the prompt to reboot, IIRC).
After killing the updater from
Settings -> Apps
on each subsequent attempt the updater constantly crashed.
According to logcat
Code:
03-07 20:50:44.778  1456  1456 E update_engine: [ERROR:update_attempter_android.cc(-1)] unknown(...): Domain=update_engine, Code=generic_error, Message=An update already applied, waiting for reboot
03-07 20:50:44.781  1456  1456 E update_engine: [ERROR:update_attempter_android.cc(91)] Replying with failure: pc:0x568e3ea58c: An update already applied, waiting for reboot
03-07 20:50:44.784  6196  6196 D AndroidRuntime: Shutting down VM
03-07 20:50:44.784  6196  6196 E AndroidRuntime: FATAL EXCEPTION: main
03-07 20:50:44.784  6196  6196 E AndroidRuntime: Process: org.lineageos.updater, PID: 6196
03-07 20:50:44.784  6196  6196 E AndroidRuntime: java.lang.RuntimeException: Unable to start service [email protected] with Intent { act=action_install_update cmp=org.lineageos.updater/.controller.UpdaterService (has extras) }: android.os.ServiceSpecificException: An update already applied, waiting for reboot (code 1)
So. I took the risk and rebooted and things seem to be ok.
 

esbeeb

Member
Jan 25, 2022
11
5
Huawei Nexus 6P
I had my enchilada at the Lineage 19, build from Dec 13, 2022. I just did the update to Lineage 20, build from Feb 28, 2023. The whole process took about 50 min. No bootloops.

Much kudos @LuK1337 !! :giggle:
 
Last edited:

gamertag128

Senior Member
Nov 15, 2021
79
66
Quick Update: since the last Update, I couldn't get my phone to bootloop. I think the problem has been solved 😁 great performance & buttery smooth animations. Great daily driver ☺️
 
  • Like
Reactions: Spaceoid

pdmr

Member
Feb 9, 2014
15
7
Tested twice and it works!!! Thanks!
True, exists at least in my Magisk Manager app (V 25.2 stable). Be aware that this method only works if performed *after* completing OTA installation to the inactive slot but *before* first reboot:

Click the "install" link for Magisk itself:

View attachment 5852473

Next click "install to inactive slot (after OTA)". Follow instructions, reboot and stay rooted


View attachment 5852475
 
  • Like
Reactions: lm089

Spaceoid

Senior Member
Mar 29, 2013
409
161
Dortmund
Aye, thank you.
Today I experienced my bluetooth switching off without any user input for the second time in the last months. No big issue at all. It happened in the gym both times, might be because of the presence of many other bluetooth devices? I'll try and get a log next time it happens.
 

ieee1

Member
Mar 16, 2023
12
1
Thank you so much for creating and supporting the rom. Screen on time appears to be reduced drastically in Android 13 ! I used to get get 5 hours of screen on time ine oos10 on my oneplus 6. I used to charge my mobile once a day. Lineage OS 20, seems to be giving 3.5 hrs of screen on time. Is anybody else observing similar behaviour ?
 

Spaceoid

Senior Member
Mar 29, 2013
409
161
Dortmund
Thank you so much for creating and supporting the rom. Screen on time appears to be reduced drastically in Android 13 ! I used to get get 5 hours of screen on time ine oos10 on my oneplus 6. I used to charge my mobile once a day. Lineage OS 20, seems to be giving 3.5 hrs of screen on time. Is anybody else observing similar behaviour ?
I personally experienced no difference at all between 19 and 20!
 

gamertag128

Senior Member
Nov 15, 2021
79
66
Aye, thank you.
Today I experienced my bluetooth switching off without any user input for the second time in the last months. No big issue at all. It happened in the gym both times, might be because of the presence of many other bluetooth devices? I'll try and get a log next time it happens.
I'm using Samsung bluetooth earbuds for about 2-3 times a week for about 2-3 hours each and didn't notice such behavior 😅
 
  • Like
Reactions: Spaceoid

ieee1

Member
Mar 16, 2023
12
1
I personally experienced no difference at all between 19 and 20!
I am getting 4 hours of Screen on time, with this build. Could you please check the time against "Screen" in Battery usage analyzer(i checked mine, from 100% to 1% of battery capacity). I saw some issues fixed in EvolutionX Rom, related to unusual battery usage. May be, we can also get it fixed in LOS, if the issue is not user specific
 

pw44

Member
Nov 26, 2020
14
1
Dear All,

after the last updates of Lineageos 20 on Sagit, i'm not able to wifi to my IOS tether hotspot.

Is it a known problem?

It worked before the two last updates.

TIA!

Paulo
 

Luk3s

Member
Dec 29, 2019
15
4
OnePlus 6
  • Like
Reactions: gamertag128

lm089

Senior Member
Hi all,just returned to this ROM from a different unofficial one. Did a full clean wipe and everything. Installation so fwar went smooth, as always.
Trying to install Magisk the official way fails, though:
downloaded lastest boot.img for this ROM, then from Magisk Manager ran the usual patch run, being told in the end the name and olcation of the patched file. The resulting file however has 0 bytes. Tried 3 time, always the same.


UPDATE: never mind, whatever that was, working now as expected
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Material You color picker is back in the latest update, thank you very, very much!
    3
    Edit: People are saying there is an "Install on inactive partition after OTA" option in Magisk app, but I have not been able to find it. Maybe it is worth checking out.
    True, exists at least in my Magisk Manager app (V 25.2 stable). Be aware that this method only works if performed *after* completing OTA installation to the inactive slot but *before* first reboot:

    Click the "install" link for Magisk itself:

    Screenshot_20230303-084730_Magisk.png


    Next click "install to inactive slot (after OTA)". Follow instructions, reboot and stay rooted


    Screenshot_20230303-084746_Magisk.png
    2
    Hi, just by chance today I realized that the LOS download page for this (and most probably any other) device has changed drastically; I guess it was yesterday or the day before that I last visited and back then it still had the design I was used to over the last few years.
    Apparently the download option for LOS recovery is gone, instead I see 3 extra links for boot.img, dtbo.img and vbmeta.img. I understand about boot.img, that's indeed a nice thing to have. But when and why would I need the other 2?
    I looked around at lineageos.org but couldn't find anything. I'd be extremely happy with a quick explanation here, or instead a link to some other page. Thanks!
    On A/B devices like the OP6 recovery is on the boot partition, so the recovery you used to download was just a renamed boot.img. The installation guide was updated to reflect this change.
    2
    Reading a little bit through the LOS reddit and the changelog, the new update seems to have contained a lot of changes to AOSP and UI, which might be the cause to the missing color feature.
    I'm not missing the themed icons, but the option to change theme colours.

    Edit: the next update should fix it 😃 on the change logs for the upcoming patch we can see that the LOS themepicker will be exchanged with the AOSP one. That's probably the reason why there was a conflict in code in first place, which resulted in this „bug".
    2
    What app do you use for taking logs? What is state of the art right now?
    A 'computer'.
  • 32
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 13, 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.

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

    Instructions :
    Downloads :
    GPL compliance :
    Reporting Bugs
    • 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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (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:
    6
    I do not have a device supporting aptX, AAC or LDAC (only SBC), but I read a lot of "offload" and "aac". Maybe this is similar to this patch?
    Just pitching in information. Maybe it helps.

    For me personally everything is flawless. Great work!
    We already set this prop.

    Also, I posted a related comment here: https://gitlab.com/LineageOS/issues/android/-/issues/5381
    5
    Thank you @LuK1337 for keeping this device alive! Updated from 19.1, everything went smoothly and working good.

    Love the new Aperture camera app, results are really nice - pics are nice and sharp, shutter is quick and snappy, UI is nice and the features are good. One thing I noticed though - pictures are 8 megapixels instead of 16 (I set the capture mode to maximize quality, but it's still 8MP). Also, on the video front, FPS is capped at 30 - can't change it in any of the resolution modes. Otherwise, very nice app, will be interesting to see where it goes next and how it grows :)
    5
    Hey, kernel 4.9.x has gone EOL - https://kernel.org/

    Can anyone check which kernel is preinstalled and how lineageos handles EOL kernel? Is it going to be 4.9.x forever or is it updated?
    The sad reality for Android phones is that they use downstream kernels - google takes the linux kernel and changes it to run android, then the chip maker changes that to run on the SoC, then the phone maker changes that to work with all the stuff in the phone. And then you arrive at something that is pretty far away from what that angry Finnish guy has released as "Linux". Add to that some binary drivers and proprietary interfaces, and you get the mess that is android.

    There are actually projects to run the official Linux kernel (called mainline or upstream) on our device, for example the postmarketOS guys here have got all the core stuff working with mainline: https://wiki.postmarketos.org/wiki/OnePlus_6_(oneplus-enchilada)

    However, that takes a lot of reverse engineering, and big parts one takes for granted in android just don't work, because nobody knows how or has been able to spent the weeks of unpaid work to learn. For example, last time I checked, the mainline kernel on the O+6 has somewhat broken cpufreq stuff, and a working camera is still far away.
    4
    For everybody looking for reviews before upgrading to LOS 20.0:

    Stable, snappy & best in class update support are the best way to describe it, in my opinion.

    -------------------------------------------

    I customized and flashed ih8sn.zip to get the play store certified. Android 13 feels a lot like Android 12, but got some customization options, which I was missing. It's been a very pleasing experience so far and I've been very happy to see support for such an "old" device. Huge thanks to all developers and especially luk for their great work.