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

Search This thread


Senior Member
Dec 19, 2014
Anyone noticing that the color calibration setting doesn't persist? I click on sRGB, and it's back to the standard calibration after I lock and unlock the phone.
I also noticed that because i always use RGB mode,but try this like me-select RGB and just reboot,then the mode is correctly applied,strange.And one more thing,after reboot everhything is ok until i change wallpaper.Color mode is changed by itself again.Weird

Atul Shyam

Dec 13, 2020
Kozhikode, India

Will this work on an unrooted OP6T running LOS 18.1 with LOS recovery?
  • Like
Reactions: rockynewsmaster


Nov 28, 2015
Anybody experiencing Playstore Certification not showing in Playstore settings?
Also Widevine is L3 on DRM info and Netflix ?
I'm on May 06 nightly with MindTheGapps.


  • Screenshot_20210509-095526_Google_Play_Store.png
    130 KB · Views: 99


Senior Member
Feb 25, 2011
Will this work on an unrooted OP6T running LOS 18.1 with LOS recovery?

No, you need root to use that module. See my 6T Guide Installing Lineage, particularly step 5. Very Optional, Magisk. It covers those very steps.

Note if you follow those steps you will pass safety net and come up certified in the play store. However the test built into the current stable version of Magisk will fail at the moment, as the API is broken. This has been fixed in canary builds. See this link for more. Personally I'm still using the stable build.
  • Like
Reactions: thomasnsr


Oct 4, 2009
Hey guys, I can't find my device when connected to my Windows laptop via USB cable after flashing LOS 18.1. Windows recognises the device and lists it as "OnePlus" under system tray. I tried enabling/disabling USB debugging, selected "Transfer files" option within the notification pull down, tried installing latest device drivers from OnePlus, but nothing seems to work. Any suggestion would be greatly appreciated!
I haven't tried with 18.1, but I installed 17.1 on a different phone, and had the same issue. With the official android build I could transfer files on Windows no problem. With lineage, most of the time it does not recognize the phone when connected, but sometimes it randomly does.


New member
Dec 13, 2016
For who ever wants to know how to install here's the link. Helped me a lot



Senior Member
Mar 23, 2018
I've just bought a fajita for my wife, and installed LOS on it, with MTG (I've upgraded to OOS10.3.10 just before of course). Works perfectly fine, but I have some questions regarding the FOD :
* when i register new fingerprints, it will, towards 33% of registration process, ask me to lift my finger and try again. And even if I don't have my finger on the screen: I press, lift my finger, and a second after, it asks me to remove my finger - after that it can resume registering, but it rarely recognises my fingerprint
* this morning, when I press the FOD, it lights in green, but doesn't react

Are there any tricks to make FOD work better? First time I have one. Thank you

EDIT: well, after a reboot, the FOD option has totally disappeared. Not displayed, not available in security, i've tried removing the pin code, clearing the qualcom biometrics system app cache and storage and restarting, but to no avail.
Last edited:


Senior Member
Jan 27, 2012
St. Louis
Well that took entirely too long to get going. Followed this https://forum.xda-developers.com/t/guide-installing-lineage.4075955/.

Did the following:
1. Unlock Bootloader
2. boot to TWRP using .img
3. Flash TWRP installer
4. Reboot recovery
5. Factory Reset
6. Format Data
7. Reboot Recovery
8. Flash LOS 18.1
9. Flash TWRP installer
10. Reboot Recovery
11. Flash LOS 18.1
12. Flash TWRP installer
13. Reboot Recovery
14. Flash NikGapps-basic-arm64-11-20210514
15. Flash NikGapps-Addon-11-SetupWizard
16. Flash Magisk v23
17. Reboot System

Then it just goes into a bootloop that ends up back at recovery.
Tried repeating steps with older builds of LOS, tried skipping Gapps and Magisk.
Finally did my 1-17 steps again and when it bootlooped back to Recovery, i did the Factory Reset and Format data wipes and ACCIDENTALLY booted to System. It then booted to LOS somehow with no issues. I then went back to recovery and flash gapps, addon-setupwizard, and magisk. Booted to system again and everything is working as expected.

Not sure why this worked. but just putting this here in case anyone else has these issues.


Top Liked Posts

  • There are no posts matching your filters.
  • 3
    About GCam:
    The latest release of Nikita (v1.3) is compatible with OP6/6T

    My config file in attached file.
    A stable firmware 11 in a few weeks?

    Some latest builds were removed (e.g. OP5/5T, OP6/6T)
    So - I WASN'T the only one... 😜
    I rolled back (switched slots) to 7/22 version, and am not longer experiencing the touch issue above. Anyone else experiencing this issue with the 7/29 update?
    Some latest builds were removed (e.g. OP5/5T, OP6/6T)
    I just installed the 7/29 update. The touch response is really off for me where initial touches register as "select" rather than "click". I have to touch a second time often.

    Anyone else experiencing this? Suggestion how to fix?
    I rolled back (switched slots) to 7/22 version, and am no longer experiencing the touch issue above. Anyone else experiencing this issue with the 7/29 update?
  • 9

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

    What's not working :
    • WFD
    Instructions :
    Downloads :
    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.

    What is your--
    LineageOS version:
    LineageOS Download url:
    Gapps version:
    Did you--
    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:
    @LuK1337 Tahnks for all your hard work.
    Will our beloved 6T also get official 18.1 support?
    So I went and read through the RTT docs. One way to make sure RTT is disabled is to remove it from the carrier configuration, lol. So I went and did just that:

    UPDATE: So, I found a better way to do this that doesn't break everything else. You can go to /data/user_de/0/com.android.phone/files and edit the carrierconfig file there, mine was called carrierconfig-com.android.carrierconfig-89148000001882338238-1839.xml. Change the following line:

    <boolean name="rtt_supported_bool" value="true"/>
    <boolean name="rtt_supported_bool" value="false"/>

    And reboot! After that, RTT shouldn't be a bother anymore. This is a bit of a hack, but it works! XD
    Why do the builds say nightly and not stable on the download page? I thought the ROM was "official" and stable now?
    Thanks for your reply! I have a noob question, I can find several guides and instructions on how to install Magisk using TWRP recovery. However, I cannot seem to find any guides on how to install Magisk using Lineage OS recovery.

    Probably because most people on this device are using TWRP, myself included.

    You should be able to use the steps for installing Magisk from 8T Guide. (Should be the key word, as I'm using TWRP, this is untested on this device personally. It is how I would do it though if I needed to try it.)

    It's basically just

    In LOS recovery choose:

    - Apply update
    - Apply from ADB

    Now in the terminal on the PC:
    - sudo adb sideload Magisk-v22.1.zip. (remove sudo if you aren't using Linux)

    If you get a warning about them not being signed, choose flash anyways. We should be ready to reboot to the system now.

    The section there about passing safety net will work as well. Just remember the safety net test in Magisk doesn't currently work.