[ROM][OFFICIAL][fajita][11] LineageOS 18.1

Search This thread
Is anyone on fajitaa facing resetting cellular modem (signal icon(s) disappear, then come back as it renegotiates connections for each SIM), wifi connection problems on 5GHz band, or wifi display (Miracast) being broken? I have some users (crDroid, built against LineageOS device trees/kernel/blobs) having problems with these issues since switching to the updated codebase/10.3.10 vendor blobs.
 

just4sc

Senior Member
Dec 25, 2010
115
12
Is anyone on fajitaa facing resetting cellular modem (signal icon(s) disappear, then come back as it renegotiates connections for each SIM), wifi connection problems on 5GHz band, or wifi display (Miracast) being broken? I have some users (crDroid, built against LineageOS device trees/kernel/blobs) having problems with these issues since switching to the updated codebase/10.3.10 vendor blobs.
Don't use MiraCast so can't speak to that but don't have any of the other issues you've mentioned.
 

beamscotty

Senior Member
Dec 17, 2015
208
124
Paris
I discovered a minor bug. I am in Sweden, using Telia as my network provider. Their APN settings have changed some time ago; before it required a proxy IP and port 8080. These are the default settings that come with LineageOS 17 and 18. In order to get an Internet connection one has to remove any proxy IP and the port. Editing the APN worked fine in v.17, but in v.18 you can only remove the proxy IP, deleting the port setting will not be retained when saving the settings. Same goes for MMS.

Internet works somehow even with port 8080 still present, but it would be nice to be able to edit/save APN settings. Also, getting the current settings by default for Telia Sweden would be nice.
 

beamscotty

Senior Member
Dec 17, 2015
208
124
Paris
Magisk question: After upgrading to 18.1, closely following the official instructions, Magisk is gone of course. The Magisk app reports no ramdisk. Which method should I use to install Magisk? I am using LineageOS recovery. Should I just patch the recovery, like it says for Magisk 22? This method seems to have serious disadvantages. Patching by sideloading a zip whilst in recovery is no longer recommended, and can cause boot looping. Most docs refer to TWRP or patching the stock recovery. None talk about patching LineageOS recovery image.

Not having root is driving me nuts.

Edit: I couldn't wait for advise. I went ahead and patched the LineageOS recovery, per instructions, followed by adb pull and flashing the patched recovery. Note: The instructions are wrong - flashing the patched recovery by "fastboot flash recovery" does not work. You have to follow the instructions for first-time installation of LineageOS and flash with "fastboot flash boot". Mine flashed it in to slot B, instead of slot A as ususal when doing a clean install, not that it seems to matter. Magisk is working. However, selecting reboot to recovery doesn't work (documented) and there is no option to boot to recovery in the bootloader either. This is to be expected apparently. Ramdisk support in the bootloader would have been much better/easier.
 
Last edited:
  • Like
Reactions: mcfisch

Knobias

New member
Jan 3, 2019
2
3
Is anyone on fajitaa facing resetting cellular modem (signal icon(s) disappear, then come back as it renegotiates connections for each SIM), wifi connection problems on 5GHz band, or wifi display (Miracast) being broken? I have some users (crDroid, built against LineageOS device trees/kernel/blobs) having problems with these issues since switching to the updated codebase/10.3.10 vendor blobs.
Hello Terminator.J,
i switched yesterday evening from lineageos 17 to 18.1. I decided to do vendor update, because I did not update since half year. I have wifi issues. I cant connect to my wifi with the 6t. I only tried 5GHz. My laptop and other devices connects to the wifi without issues.

I tried yesterday first with 10.3.9, but I'm not sure if I had the problem already. I had the vendor 10.3.9 maybe an hour on the phone before I found a download link to 10.3.10.

In case I shall try something please let me know.

edit: It's working. I reflashed the 10.3.10 vendor firmware. Then it was not working. I disabled the wifi in the settings not at the topbar menu, removed the known wifi connection, enabled gps, enabled wifi, connected to the network and it worked. I don't know if it helps. Looks more like vodoo. :-D but 5GHz works.
 
Last edited:
Hello Terminator.J,
i switched yesterday evening from lineageos 17 to 18.1. I decided to do vendor update, because I did not update since half year. I have wifi issues. I cant connect to my wifi with the 6t. I only tried 5GHz. My laptop and other devices connects to the wifi without issues.

I tried yesterday first with 10.3.9, but I'm not sure if I had the problem already. I had the vendor 10.3.9 maybe an hour on the phone before I found a download link to 10.3.10.

In case I shall try something please let me know.

edit: It's working. I reflashed the 10.3.10 vendor firmware. Then it was not working. I disabled the wifi in the settings not at the topbar menu, removed the known wifi connection, enabled gps, enabled wifi, connected to the network and it worked. I don't know if it helps. Looks more like vodoo. :-D but 5GHz works.
Interesting. Had someone in telegram report that turning off wifi calling & carrier video calling toggle stopped the cellular modem reset issue for them, by the way.
 

snaggen

Member
Jan 20, 2011
15
6
I discovered a minor bug. I am in Sweden, using Telia as my network provider. Their APN settings have changed some time ago; before it required a proxy IP and port 8080. These are the default settings that come with LineageOS 17 and 18. In order to get an Internet connection one has to remove any proxy IP and the port. Editing the APN worked fine in v.17, but in v.18 you can only remove the proxy IP, deleting the port setting will not be retained when saving the settings. Same goes for MMS.

Internet works somehow even with port 8080 still present, but it would be nice to be able to edit/save APN settings. Also, getting the current settings by default for Telia Sweden would be nice.
I found two Telia online APN, the default didnt work but the other one worked fine.
 
  • Like
Reactions: beamscotty

beamscotty

Senior Member
Dec 17, 2015
208
124
Paris
I found two Telia online APN, the default didnt work but the other one worked fine.
Yes, like I said, LineageOS has had the wrong default settings for a long time now. At least from v.16. Basically you should remove any proxy and port values, both in the Internet and MMS APN settings for Telia to work.
 

beamscotty

Senior Member
Dec 17, 2015
208
124
Paris
Having used v.18.1 for a few days now, I notice that battery drain is tremendous. This was not the case in v.17. On the positive side, it has solved a few niggling problems with Outlook, Teams and other apps I use for my work. It seems, subjectively, faster and smoother than v.17, but that may just be an impression.
 

Eric_Lev

Senior Member
Jan 27, 2019
1,163
2,296
Angers
androidfilehost.com
A brief feedback:
I just bought an OP6T (OOS - fw 10.3.09) and previously I had an OP5T.
I installed LOS 18.1 and MindTheGapp with success via LOS recovery following the official instructions.
Today, I updated successfully LOS via OTA updater (from 0430 to 0506).
No problem so far.
FYI:
- I am not rooted and as expected CTS failed (BL unlocked) ... (but no need to pass safetynet here)
- I'm using the GCAM app of Nikita (7.4 v2.0)

As I'm thinking of upgrading my fw from 10.3.09 to 10.3.10 using the official instructions, I have two questions:
1- Is it highly recommended or optional? ... because of this commit sdm845-common: Update blobs from OOS 10.3.10
2- Do I have to remove my screen locks (fingerprint and pattern here) before updating fw? ... I was doing it with my OP3T and OP5T.

Thanks @LuK1337 !

Edit: 1- I just updated the fw ... (see screenshots) ; 2- I removed my screen locks ... (as a precausion)
 

Attachments

  • Screenshot_20210506-152206_Settings.png
    Screenshot_20210506-152206_Settings.png
    153.6 KB · Views: 75
  • Screenshot_20210506-152843_LineageOS_Settings.png
    Screenshot_20210506-152843_LineageOS_Settings.png
    159.6 KB · Views: 76
Last edited:
  • Like
Reactions: thomasnsr

Atul Shyam

Member
  • Dec 13, 2020
    14
    7
    Kozhikode, India
    I just flashed official Lineage OS 18.1 on my unrooted OP6T with lineage recovery. The Rom works absolutely fine, however, I cannot seem to run banking apps such as Paytm, Amazon Pay, etc. Any Idea on what to do? I cannot sacrifice these apps.
     

    rirozizo

    Senior Member
  • Jul 6, 2010
    2,861
    1,548
    wonderland... soon
    OnePlus 6T
    I just flashed official Lineage OS 18.1 on my unrooted OP6T with lineage recovery. The Rom works absolutely fine, however, I cannot seem to run banking apps such as Paytm, Amazon Pay, etc. Any Idea on what to do? I cannot sacrifice these apps.
    You can flash Magisk and enable Magisk Hide, that way you pass SafetyNet and Magisk can hide itself from the apps you want to use.

    I'm a little rusty with these things though, so take my suggestion with a grain of salt. You can always just uninstall Magisk if that didn't work out for you.
     

    Blac Caesar

    Senior Member
    Jul 31, 2012
    518
    237
    @LuK1337 thank you, and the other LineageOS devs for building this.. I really appreciate your hard work and dedication to the fajita. 18.1 is working perfectly for me.. followed Lineage's upgrade steps, no GApps. Booted fine, no loops or crashes. Thanks again!
     

    Top Liked Posts

    • There are no posts matching your filters.
    • 3
      I've installed the latest version, and I'm having trouble with audio through Bluetooth. The sound comes from the phone speaker even when connected to the Bluetooth.
      Same issue here.
      Go to Settings -> Connected Devices -> that little cog wheel next to your Bluetooth device, and then turn off HD audio.
      SBC HD is being turned on by default in this week's fajita build, but not all Bluetooth devices can handle it. If the BT device doesn't work well with it, the audio will end up playing through your phone instead. Some changes have been merged in since to make SBC HD an optional codec instead of being mandatory, so it won't be automatically enabled by default for new devices, but you'll need to wait for next week for those builds.
      2
      Yeah I noticed that too. It seems that lineage OS broke the stock fast boot mode somehow, although I didn't know this was possible, it will no longer connect to PC. So they integrated a new fast boot "fastbootD" into the lineage OS recovery, and only this one will connect to PC. But they included a button to get to the stock fast boot mode for compatibility reasons.

      I could be way off here, correct me if I'm wrong, but this is my best guess based on the very limited info I can find and my personal experience
      No, that's completely wrong. The existence of fastbootd is not because Lineage broke abl's ability to accept fastboot commands--it's because of this: https://source.android.com/devices/tech/ota/dynamic_partitions
      And since abl (bootloader) won't be able to detect the partitions within said "super partition", Google specifies a userspace fastboot implementation to provide instead, fastbootd: https://source.android.com/devices/bootloader/fastbootd

      fajita doesn't ship with dynamic partitions, so technically, fastbootd isn't actually needed. However, the fastboot implementation in fajita's abl doesn't ever allow the user to flash to the critical partitions (all the firmware-related partitions), even if you run `fastboot flashing unlock_critical`. But, since fastbootd runs in the same environment as recovery, and since the restriction on touching critical partitions doesn't apply when in the recovery environment, shipping fastbootd for fajita and telling users to use that instead to flash updated OOS firmware works around that issue. (This is not needed on other devices that actually lets users flash critical partitions from abl fastboot, like mata [Essential Phone])
      2
      Yeah, as I had restored my data after updating, I needed to re-add (or re-authenticate) my cards. Got an error that they could not be used in stores.
      If you're passing SafetyNet then just wipe google play services data and reboot. I noticed that they no longer have a button that lets you recheck whether your phone is *safe* again.
      1
      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"/>
      becomes
      <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
      1
      So a couple of things about RTT for Verizon...

      I think its the culprit for why there is a couple/few seconds when a call is made that the other side can't hear anything from my end. I know that I kept being hung up on when ordering takeout because they didn't hear anything from my end in the first few seconds of the call.

      And another thing that is even more annoying (and may be fixed on the latest LOS but I'm pretty sure i tested and it was not) was that the phone signal disconnects/resets every 15 mins or so. Had a long call with my niece from another state and I had to call her back at least 5 or 6 times during it because of the frequent DCs.

      Fellow Verizon user. That it correct about the RTT issue. I had the same pause happen. I hear it should be fixed in the next LOS build. Hope it fixes 911 calls too. I will report back.

      I have never had any issues with random disconnects like you mention on Verizon on this phone with any ROM. Not sure why that would be.
    • 9
      @LuK1337 Tahnks for all your hard work.
      Will our beloved 6T also get official 18.1 support?
      Eventually.
      8
      2okPze5.png


      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.

      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:
      5
      Why do the builds say nightly and not stable on the download page? I thought the ROM was "official" and stable now?
      lmao.
      4
      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.
      3
      Just gone official