• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][OFFICIAL][enchilada][11] LineageOS 18.1

Search This thread

Spaceoid

Senior Member
Mar 29, 2013
235
64
Dortmund
Gentlemen I awant to ask, I have OOS (Android 9), before flashing 11.1.1.1 should I first flash to this android 10 version because of firmware? Or just flash straight to 11.1.1.1?

I'd do OOS update first, because I think newer LOS builds depend on an up-to-date OOS version. But no guarantee, that's just how I would do it.
 

kecodoc

Senior Member
Apr 29, 2011
550
57
HaiPhong
OnePlus 6
Just a tiny review, story, thank you and probably my first post since a few years now:

Was pretty happy with OOS, no doubt. Then the hassle began a few days ago. Some are apps were acting weird and resisted getting a connection, despite my connection was OK and permissions too. Whether reinstalling, nor clearing really everything at the base of data/data/ from those apps helped. Thought: Maybe do the step to OOS11 now. Made that. Suddenly, now also Android Auto stopped working. Paired, but no connection. Displays "Unknown Device". So back to the scratchboard and bringing back something I really didn't do a long time ago: Get TWRP, clear everything, setup LOS, GApps, SuperSU... ahm... Magisk.

TWRP? Seems to be gone for our devices. Even custom once seems to be vanished. Don't know what happened, but maintenance got dropped? Read through the threads, the latest version should word fine - except encryption. Since this wouldn't be something I need to have: Fine.
Connection my laptop to the device, get the latest SDK platform tools and USB driver. "adb devices" works. Fine. "adb reboot bootloader" working too - I'm happy. Moving all together: "fastboot boot twrp.img"... hmmm... Nothing? Ah, here we go. Qualcomm error. Dang. So, what to do now? MSM? Nope. LOS/CM like I had on all my devices for now.

Recovery from LOS. That might work for me. Again to the bootloader and flashed the recovery. Reboot to OOS now? What happened? "adb reboot recovery". There we go. Fine. Now what? Mhm. Got it. Simpy sideload it in LOS recovery. Fine with that. a/b partition was kinda new for me now. Never had to deal with it, because "fastboot boot twrp.img" was a thing. Never had to install a custom recovery, because: No reason to. So straight forward: Flash LOS, flash MindTheGApps, flash Magisk 23. Switch to fastboot: "fastboot –set-active=_a" & reboot to recovery, flash the other partition the same way > Reboot to system.

Setup straight forward like in the past and was curious, if everything works.

So here the points:
• Android Auto works better than on OOS10 (and obviously 11, because never worked).
• No problems encountered so far over all.
• AOD works like a charm.
• AMOLED dark theme is something OOS should adopt, but probably never will.
• Recovery is a bit underwhelming/simple, but does the job.
• Google Camera Mod (Urnyx) works like it did on OOS.
• DAC seems to be better than on OOS? Maybe? Because my car stereo sounds better, I think. Maybe placebo.
• Kernel seems to be decent, because not pulling a crazy amount of energy for same tasks whilst keeping the device snappy. Tweaked governor possibly. Have to look this up. Maybe placebo too.
• OOS navigation gestures and face unlock will be missed, for sure.

Final verdict: I'm for sure not switching back to OOS. LOS18.1 seems to be stable enough for my daily usage. Thanks for all the efforts and time, you are putting into it!
Lol lineageos is great for both gaming tasks and everyday use,Since using los 18.1 I no longer care about OOS It's true ^^
 

Spaceoid

Senior Member
Mar 29, 2013
235
64
Dortmund
Out of curiosity - do you need to reflash Gapps after every update of LineageOS?
I remember that back then on my Galaxy S4 Mini and my Xperia X Compact I needed to reflash Gapps after every (unofficial) update of LineageOS.
I bought my OnePlus 6 on Ebay and it already had LineageOS and Gapps pre-installed, so I just needed to update LOS to be up-to-date. And I never needed to reflash Gapps. I wonder why that is.
 

kouzelnik3

Senior Member
Dec 29, 2011
463
135
24
Prague
jakubkasanda.g6.cz
OnePlus 6
Out of curiosity - do you need to reflash Gapps after every update of LineageOS?
I remember that back then on my Galaxy S4 Mini and my Xperia X Compact I needed to reflash Gapps after every (unofficial) update of LineageOS.
I bought my OnePlus 6 on Ebay and it already had LineageOS and Gapps pre-installed, so I just needed to update LOS to be up-to-date. And I never needed to reflash Gapps. I wonder why that is.
No you don't need to reflash gapps every update, pomoc twrp and magisk.
 
  • Like
Reactions: Spaceoid

CrysisLTU

Senior Member
Feb 1, 2012
293
361
Out of curiosity - do you need to reflash Gapps after every update of LineageOS?
I remember that back then on my Galaxy S4 Mini and my Xperia X Compact I needed to reflash Gapps after every (unofficial) update of LineageOS.
I bought my OnePlus 6 on Ebay and it already had LineageOS and Gapps pre-installed, so I just needed to update LOS to be up-to-date. And I never needed to reflash Gapps. I wonder why that is.
I would do a clean flash on a used device from eBay. You never know what could be on there.
But yeah, Gapps stay after OTA.
 

kecodoc

Senior Member
Apr 29, 2011
550
57
HaiPhong
OnePlus 6
Is there a way to access Android/data without having to root the device? Because I need to extract a large game file into Android/data,with other file management applications copy and decompression speed is very slow therefore I need to use the winrar application but can't read files in android/data (i have granted memory access to winrar app)
But it requires permission to be accessed by the files app with other app i get notification but with winrar no notification at all.
Thank you guys please help.
 

Attachments

  • Screenshot_20211013-235409_RAR.png
    Screenshot_20211013-235409_RAR.png
    55.5 KB · Views: 69
Last edited:

ipha

Member
Nov 6, 2016
18
10
OnePlus 6
Google Pixel 6 Pro
Is there a way to access Android/data without having to root the device? Because I need to extract a large game file into Android/data,with other file management applications copy and decompression speed is very slow therefore I need to use the winrar application but can't read files in android/data (i have granted memory access to winrar app)
But it requires permission to be accessed by the files app with other app i get notification but with winrar no notification at all.
Thank you guys please help.

Yes, but it looks like winrar doesn't properly request permission to access android/data.

If you haven't yet, try Solid Explorer -- it's the best file manger I know of.
 
  • Like
Reactions: kecodoc

AshraafAzhar

Member
May 17, 2014
29
13
Selangor, Malaysia
Yesterday, I installed Lineageos 18.1 on my friend's Xiaomi Redmi Note 9 Pro(miatoll) and he complained about camera sharpness when using his company apps to take pictures. So he planned to install gcam.

But I said to him that installing gcam probably won't help him as the apps uses camera directly instead of using camera apps such as Snap or Gcam, is this correct or is there any workaround?
 

CrysisLTU

Senior Member
Feb 1, 2012
293
361
Yesterday, I installed Lineageos 18.1 on my friend's Xiaomi Redmi Note 9 Pro(miatoll) and he complained about camera sharpness when using his company apps to take pictures. So he planned to install gcam.

But I said to him that installing gcam probably won't help him as the apps uses camera directly instead of using camera apps such as Snap or Gcam, is this correct or is there any workaround?
You are in the wrong thread (this is for enchilada). But yes - Gcam wont help with camera quality on other apps.
 
  • Like
Reactions: AshraafAzhar

kecodoc

Senior Member
Apr 29, 2011
550
57
HaiPhong
OnePlus 6
Hello friends please help
I am on lineageos 18.1 rom and want to install Dolby digital in current magisk is there any version that works? I want to ask before trying because I am currently using a non-root rom
 

spartan268

Senior Member
Oct 13, 2013
927
348
OnePlus 6
Anyone else having inconsistencies with Android Auto working?

Seems like if I plug it in, it'll only work once every 5 - 6 times. I tried disabled USB debugging which didn't help. Went through the settings available for AA and found nothing helpful. I ensured it had all permissions inside the app. Any other ideas?
 

leaderred

Senior Member
Dec 2, 2010
66
12
OnePlus 6
Hey guys, how do you prefer to update this rom? TWRP or build in updater? Since now I always use TWRP. But with magisk and gapps it always cost some time for everyday little weekly rom release.

Does los updater keep magisk and gapps? I use Nik Gapps.

And can I flash TWRP from los recovery or du I need to go threw fastboot TWRP Installation?

Thanks for your help.
 

CrysisLTU

Senior Member
Feb 1, 2012
293
361
Hey guys, how do you prefer to update this rom? TWRP or build in updater? Since now I always use TWRP. But with magisk and gapps it always cost some time for everyday little weekly rom release.

Does los updater keep magisk and gapps? I use Nik Gapps.

And can I flash TWRP from los recovery or du I need to go threw fastboot TWRP Installation?

Thanks for your help.
I use LOS recovery. It's officially supported and thus less issues.

Before installing the OTA, I restore images via Magisk, install OTA via the built in updater, go back into Magisk and flash to inactive slot. This way Gapps and Magisk stay intact.
 
  • Like
Reactions: leaderred

Spaceoid

Senior Member
Mar 29, 2013
235
64
Dortmund
I use LOS recovery. It's officially supported and thus less issues.

Before installing the OTA, I restore images via Magisk, install OTA via the built in updater, go back into Magisk and flash to inactive slot. This way Gapps and Magisk stay intact.
I always update via OTA. I always have to patch a new boot.img with Magisk and install via fastboot, but Gapps are kept.
 

CrysisLTU

Senior Member
Feb 1, 2012
293
361
I always update via OTA. I always have to patch a new boot.img with Magisk and install via fastboot, but Gapps are kept.
No need for fastboot. Go into the Magisk app before installing the OTA, click on Uninstall Magisk, then Restore Images. Now install the OTA via the built in updater. Once the OTA update is installed, do not reboot. Go back into the Magisk app. Click on Install Magisk, select Install to Inactive Slot (After OTA), and only then reboot.

Full instructions can be found here: https://topjohnwu.github.io/Magisk/ota.html
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Make sure to use the latest platform-tools.
    Also, you need to flash via the recovery's fastboot menu.
    It worked via the recovery's fastboot menu!

    Thanks
    2
    It wont. If you use TWRP, boot into it, flash OOS 11, then LOS build, then twrp, then reboot recovery (for slot swap), do the process again, flash magisk optionally and reboot. You are done. :)

    Up to you, I just written what I did when I was perfoming this upgrade :)


    Thank you to you two!

    The Firmware upgrade with the Lineage process was very fast. Very probably faster than flashing the whole OOS then LOS.

    I confirm Dash is working now. I'll try to remember next time about the fw upgrade.
    1
    I can't find on the wiki how to flash OnePlus oos version android 11 before flashing lineageos
    Flash LOS 18.1 first to get the necessary fastboot entry in recovery.
    Afterwards flash OOS 11 following LOS wiki.
    1
    Hello!

    I'd like to step up from OOS 9.0.9 to LOS18.1 - and as people here wrote before, the guide on the LOS homepage doesn't describe my scenario either and I don't want to mess up.
    Could someone please assist me? Thanks a lot!!!

    Status today:
    OS: OOS 9.0.9
    Recovery: TWRP Team win recovery 3.2.3-0
    Bootloader: Unlocked
    Kernel: 4.9.106-ElementalX-OP6-3.19#1

    What exactly doesn't fit your scenario?
    I' do the following:

    (Backup personal data)
    Update OOS to latest release ( thus you are at the same point of departure the wiki presumes).
    Flash LOS as described in the wiki.
    1
    So I just update to the latest android 11 and then follow the instructions?
    Do I need to perform the updates between 9.0.9 and the latest A11 via system update or recovery?
    Guess on my way to A11, I'll lose root and the kernel will go back to stock. Will that have a negative impact on the LOS installation?

    I'm just scared to mess it up.

    Given that you use OOS, I'd assume the built-in updater to offer you appropriate updates.
    So, update to the most recent update until you're at 11.
    I've never used OOS, but flashed LOS instantly after receiving my OP6, so I don't know how exactly the OOS built-in updater works.

    Since the LOS installation usually assumes stock, you would be at exactly the point the procedure expects you to be -- no trouble here. I'd say.

    How exactly do you define "mess up"?
    If things go wrong, you will still be able to reset the phone to stock, IIRC there's even a Windows tool to do that for you.
  • 28
    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.

    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:
    3
    If anybody is curious, Ive been crawling through the code commits. Unfortunately, it looks like both Enchilada and Fajita will have to wait for some time due to issues that were encountered when booting. At least for Fajita. It will be some time until we get our first official build.

    UPDATE 1: Both Enchilada and Fajita have been reverted from the hudson branch, which indicates official commit status has been reversed. Our savior Luk has got hands full with work on these issues I imagine, so wait times will extend. Hang tight lads! We will land on Hudson soon, I hope.

    UPDATE 2: That was quick! Seems like Luk figured out the issue for Fajita and has opened a commit to merge fajita to 18.1 official again. Fajita and enchilada are merged to the Hudson branch once again. This is good news, and I am hoping that the enchilada build will be posted and merged on schedule.
    3
    Anyone else having touchscreen issues with the latest build? Like not responding to some touches and not being able to pull down the notification shade?

    Edit: reverted to last week's build and the issue is gone. So some commit messes with the touchscreen.