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

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

Search This thread

kecodoc

Senior Member
Apr 29, 2011
550
57
HaiPhong
OnePlus 6
You didn't follow wiki instructions :)
after I redo it all according to the wiki's instructions, everything is greatThe .rom is very smooth and the temperature is cool, after installing I tried using the OK GOOGLE feature but it didn't work.
I use open gaps and don't root the device Can you please help me one more time? I have tried going into settings and checking but no problem found.
Thank you so much
 

diemadedrei

Senior Member
Mar 13, 2012
622
225
OnePlus 6
after I redo it all according to the wiki's instructions, everything is greatThe .rom is very smooth and the temperature is cool, after installing I tried using the OK GOOGLE feature but it didn't work.
I use open gaps and don't root the device Can you please help me one more time? I have tried going into settings and checking but no problem found.
Thank you so much
Which opengapps were you using?
I use these
https://drive.google.com/drive/mobile/folders/1CvN4tZH_VWX17dI2Hlevgy-HfQolOTTW?sort=13&direction=a
They are built off the official repo but with all packages
 
  • Like
Reactions: kecodoc

kecodoc

Senior Member
Apr 29, 2011
550
57
HaiPhong
OnePlus 6

Attachments

  • Screenshot_20210916-230101_Chrome.png
    Screenshot_20210916-230101_Chrome.png
    182.8 KB · Views: 36
  • Screenshot_20210917-002441_Google.png
    Screenshot_20210917-002441_Google.png
    101.5 KB · Views: 36
  • Screenshot_20210917-002431_Google.png
    Screenshot_20210917-002431_Google.png
    121.2 KB · Views: 36

CrysisLTU

Senior Member
Feb 1, 2012
284
356
after I redo it all according to the wiki's instructions, everything is greatThe .rom is very smooth and the temperature is cool, after installing I tried using the OK GOOGLE feature but it didn't work.
I use open gaps and don't root the device Can you please help me one more time? I have tried going into settings and checking but no problem found.
Thank you so much
I'm not sure about Google Assistant - I'm using MindTheGapps and it's not working either.

Edit: Actually, it works fine. Just had to set Google as the default assistant app. D'oh.
 
Last edited:
  • Like
Reactions: kecodoc

daleloco

Member
Mar 24, 2014
8
1
Apps & Games
Seems I have the same "problem" here. Estimated time until full charge seems way too long all of the sudden (1h 30 from 65 to 100%). Not a huge problem though.

Edit: On the fast charger, he even tells me it'd take 6 hours from 65 to a 100 %. I am quite sure back on OOS10/a few LOS builds earlier the predictions were kinda correct.
Last time I charged my phone it said that it would take 14 hours to full charge, luckily it didnt haha
 

kecodoc

Senior Member
Apr 29, 2011
550
57
HaiPhong
OnePlus 6
I am using the latest build from this site:
With one of the configurations for OnePlus 6. Is quite (not a 100%) stable.
Except the slow motion video recording mode is faulty, the other features work quite ok
i tried other versions of Gcam 8.2 and 8.3 but got a lot of errors


Thank a lot
 
Last edited:
  • Like
Reactions: Spaceoid

optimumpro

Senior Member
Jan 18, 2013
6,760
14,245

optimumpro

Senior Member
Jan 18, 2013
6,760
14,245
Just to confirm, let's say my phone is in pocket and I receive call, should the screen wake up inside pocket?

Anyways, I wasn't complaining, was just informing about the behaviour to @batteryIow
Pocket mode is there to prevent accidental wakeups. Waking the screen when you receive a call is not an accident and is expected behavior, not a bug, regardess of where the phone is.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Clean installed LOS18.1 yesterday from Android 11 firmware base. Spent 1 hour figuring out why I was not able to setup my WhatsApp, turned out it had nothing to do with Lineage but because Facebook was down.

    Anyway everything is runnin smooth. Thanks 👍
    2
    So... LOS is not working for me.

    by any chance do you have a link that explains how to go back to stock?

    My phone is not briked but sms is not working and gapps neither.

    Thanks in any case,
    I bet you didn't follow the official install instructions from the LOS wiki.

    Install: https://wiki.lineageos.org/devices/enchilada/install
    Update the firmware if you never had used OOS11 on your device: https://wiki.lineageos.org/devices/enchilada/fw_update

    Also, use MindTheGapps.

    To go back to stock, you could use MSMDownloadTool.
    2
    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!
    2
    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
    1
    Has anybody tried to upgrade fw to 11.1.1?
  • 27
    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.