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

Search This thread

qualo

Senior Member
Jul 22, 2008
74
19
What is the lineage recovery? Where I find it? I'm using lineage 18.1 with twrp but magisk not working . plz help
Is the recovery included with the ROM. Just flash ROM, restart in recovery and sideload gapps and magisk. I did with nikgapps and magisk beta 21 and worked.
 

Ufos92

Member
May 5, 2015
46
11
Anyone tried to dirty flash this over 17.1? And anything not working as a daily?
Dirty flash shouldn't work, you need new firmware. Which you only get through the official rom. There was a lineage upgrade guide for going 16->17 which provided a firmware you could sideload, but all beta versions usually require you to restore stock, upgrade to latest and then clean flash.
That's why no one would even try dirty flashing. Best case you'll get tons of glitches.
 
  • Like
Reactions: best boy

MatteCarra

Senior Member
Feb 7, 2019
53
175
Milan
Wi-Fi disconnects and re-connects frequently when I'm in a call
@LuK1337 I can confirm I have this issue as well.
Are you already aware of the issue or would you need some logs?
If you need logs please link me/briefly tell me where to get them.

I also tested the battery impact and it seems pretty good!
Does anybody know what is sensor "pocket" and what is it used for?
AdvancedBatteryStats is telling me that in the last 7 hours it was used for over 5h.

Thanks a lot!

P.S: Is it better to donate to Luk or to the Lineage paypal?

LineageOS version: 18.1-20210102
LineageOS Download url: https://androidfilehost.com/?fid=17248734326145707962
Gapps version: NikGapps 31-11-2020

Did you--
wipe: Yes
restore with titanium backup: No
reboot after having the issue: Yes

Are you using--
a task killer: No
a non-stock kernel: No
other modifications: No
 
Last edited:
  • Like
Reactions: Shottah072

zeus_10

New member
Mar 3, 2019
2
0
@LuK1337 - in general the build is stable, one issue noticed is that camera freezes during video call when using Whatsapp and signal. Initially I thought it to be permission issue both app set to "ask everytime for camera and microphone" but after changing the setting to "only while using the app" still I am facing same issue.

Anyone else facing the same issue?


Workaround: dismiss the PIP video popup and click on the call in progress notification popup for the video to start again during video calls. (works for whatsapp, does not work for signal)


What is your--
LineageOS version: 18.1-20210110 (have seen this issue on 18.0 as well)
LineageOS Download url: https://androidfilehost.com/?fid=17248734326145712993
Gapps version: https://sourceforge.net/projects/op...ps-arm64-11.0-pico-20210110-TEST.zip/download

Did you--
wipe: Yes
restore with titanium backup: No
reboot after having the issue: Yes

Are you using--
a task killer: No
a non-stock kernel: No
other modifications: No


Attached is the logcat.
 
Last edited:

zeus_10

New member
Mar 3, 2019
2
0
PFA (not sure how to delete this comment).

Was unable to attach logcat file.
Code:
01-14 00:46:20.683 11767 11776 F libc    : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x28fa8615 in tid 11776 ([email protected]), pid 11767 ([email protected])

01-14 00:46:20.880 12408 12408 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

01-14 00:46:20.880 12408 12408 F DEBUG   : LineageOS Version: '18.1-20210110_154641-UNOFFICIAL-enchilada'

01-14 00:46:20.880 12408 12408 F DEBUG   : Build fingerprint: 'OnePlus/OnePlus6/OnePlus6:8.1.0/OPM1.171019.011/06140300:user/release-keys'

01-14 00:46:20.880 12408 12408 F DEBUG   : Revision: '0'

01-14 00:46:20.880 12408 12408 F DEBUG   : ABI: 'arm'

01-14 00:46:20.881 12408 12408 F DEBUG   : Timestamp: 2021-01-14 00:46:20-0500

01-14 00:46:20.881 12408 12408 F DEBUG   : pid: 11767, tid: 11776, name: [email protected]  >>> /vendor/bin/hw/[email protected] <<<

01-14 00:46:20.881 12408 12408 F DEBUG   : uid: 1047

01-14 00:46:20.881 12408 12408 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x28fa8615

01-14 00:46:20.881 12408 12408 F DEBUG   :     r0  28fa860d  r1  de6aed10  r2  00000000  r3  00000000

01-14 00:46:20.882 12408 12408 F DEBUG   :     r4  ddacb58c  r5  e0e156d0  r6  dbcc0010  r7  00000078

01-14 00:46:20.882 12408 12408 F DEBUG   :     r8  00002df7  r9  e881a124  r10 ddad121c  r11 000ff000

01-14 00:46:20.882 12408 12408 F DEBUG   :     ip  e10863dc  sp  ddacb4e0  lr  e0ffd8f7  pc  e0ffd4c4

01-14 00:46:20.940 12408 12408 F DEBUG   : backtrace:

01-14 00:46:20.940 12408 12408 F DEBUG   :       #00 pc 0026f4c4  /vendor/lib/hw/camera.qcom.so (CamX::DeferredRequestQueue::DispatchReadyNodes()+116) (BuildId: 50c452c40840911b1ad21cacaa70720d)

01-14 00:46:20.941 12408 12408 F DEBUG   :       #01 pc 00266901  /vendor/lib/hw/camera.qcom.so (CamX::Node::WriteDataList(unsigned int const*, void const**, unsigned int const*, unsigned int)+144) (BuildId: 50c452c40840911b1ad21cacaa70720d)

01-14 00:46:20.941 12408 12408 F DEBUG   :       #02 pc 001f917b  /vendor/lib/hw/camera.qcom.so (CamX::CAFIOUtil::publishFrameControl(AFAlgoOutputList const*) const+466) (BuildId: 50c452c40840911b1ad21cacaa70720d)

01-14 00:46:20.941 12408 12408 F DEBUG   :       #03 pc 001fa7b9  /vendor/lib/hw/camera.qcom.so (CamX::CAFIOUtil::publishOutput(AFAlgoOutputList const*, CamX::AFHALOutputList const*)+32) (BuildId: 50c452c40840911b1ad21cacaa70720d)

01-14 00:46:20.941 12408 12408 F DEBUG   :       #04 pc 00201385  /vendor/lib/hw/camera.qcom.so (CamX::CAFStatsProcessor::ExecuteProcessRequest(CamX::StatsProcessRequestData const*)+812) (BuildId: 50c452c40840911b1ad21cacaa70720d)

01-14 00:46:20.941 12408 12408 F DEBUG   :       #05 pc 001ebe3d  /vendor/lib/hw/camera.qcom.so (CamX::AutoFocusNode::ExecuteProcessRequest(CamX::ExecuteProcessRequestData*)+996) (BuildId: 50c452c40840911b1ad21cacaa70720d)

01-14 00:46:20.941 12408 12408 F DEBUG   :       #06 pc 002654f5  /vendor/lib/hw/camera.qcom.so (CamX::Node::processRequest(CamX::NodeProcessRequestData*, unsigned long long)+688) (BuildId: 50c452c40840911b1ad21cacaa70720d)

01-14 00:46:20.941 12408 12408 F DEBUG   :       #07 pc 0026ef0b  /vendor/lib/hw/camera.qcom.so (CamX::DeferredRequestQueue::DeferredWorkerCore(CamX::ThreadDataUnit*)+374) (BuildId: 50c452c40840911b1ad21cacaa70720d)

01-14 00:46:20.941 12408 12408 F DEBUG   :       #08 pc 0026ec3f  /vendor/lib/hw/camera.qcom.so (CamX::DeferredRequestQueue::DeferredWorkerWrapper(void*)+38) (BuildId: 50c452c40840911b1ad21cacaa70720d)

01-14 00:46:20.941 12408 12408 F DEBUG   :       #09 pc 00227bd3  /vendor/lib/hw/camera.qcom.so (CamX::ThreadCore::DispatchJob(CamX::RuntimeJob*)+110) (BuildId: 50c452c40840911b1ad21cacaa70720d)

01-14 00:46:20.941 12408 12408 F DEBUG   :       #10 pc 0022810f  /vendor/lib/hw/camera.qcom.so (CamX::ThreadCore::processJobQueue()+126) (BuildId: 50c452c40840911b1ad21cacaa70720d)

01-14 00:46:20.941 12408 12408 F DEBUG   :       #11 pc 00227e45  /vendor/lib/hw/camera.qcom.so (CamX::ThreadCore::DoWork()+216) (BuildId: 50c452c40840911b1ad21cacaa70720d)

01-14 00:46:20.941 12408 12408 F DEBUG   :       #12 pc 00227d5d  /vendor/lib/hw/camera.qcom.so (CamX::ThreadCore::WorkerThreadBody(void*)+56) (BuildId: 50c452c40840911b1ad21cacaa70720d)

01-14 00:46:20.941 12408 12408 F DEBUG   :       #13 pc 0008183f  /apex/com.android.runtime/lib/bionic/libc.so (__pthread_start(void*)+40) (BuildId: a5f6095b1756b81b09cabe26469c9f89)

01-14 00:46:20.941 12408 12408 F DEBUG   :       #14 pc 00039e65  /apex/com.android.runtime/lib/bionic/libc.so (__start_thread+30) (BuildId: a5f6095b1756b81b09cabe26469c9f89)



01-14 00:43:40.966   867  1403 F libc    : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x28fa8615 in tid 1403 ([email protected]), pid 867 ([email protected])

01-14 00:43:41.154 11755 11755 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

01-14 00:43:41.154 11755 11755 F DEBUG   : LineageOS Version: '18.1-20210110_154641-UNOFFICIAL-enchilada'

01-14 00:43:41.154 11755 11755 F DEBUG   : Build fingerprint: 'OnePlus/OnePlus6/OnePlus6:8.1.0/OPM1.171019.011/06140300:user/release-keys'

01-14 00:43:41.154 11755 11755 F DEBUG   : Revision: '0'

01-14 00:43:41.154 11755 11755 F DEBUG   : ABI: 'arm'

01-14 00:43:41.155 11755 11755 F DEBUG   : Timestamp: 2021-01-14 00:43:41-0500

01-14 00:43:41.155 11755 11755 F DEBUG   : pid: 867, tid: 1403, name: [email protected]  >>> /vendor/bin/hw/[email protected] <<<

01-14 00:43:41.155 11755 11755 F DEBUG   : uid: 1047

01-14 00:43:41.155 11755 11755 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x28fa8615

01-14 00:43:41.155 11755 11755 F DEBUG   :     r0  28fa860d  r1  e402d7f0  r2  00000000  r3  00000000

01-14 00:43:41.155 11755 11755 F DEBUG   :     r4  e38ea6f4  r5  e5c574d0  r6  e38ea708  r7  00000000

01-14 00:43:41.155 11755 11755 F DEBUG   :     r8  00000363  r9  ee211124  r10 e38eb21c  r11 000ff000

01-14 00:43:41.155 11755 11755 F DEBUG   :     ip  e7ede3dc  sp  e38ea648  lr  e7e558f7  pc  e7e554c4

01-14 00:43:41.217 11755 11755 F DEBUG   : backtrace:

01-14 00:43:41.217 11755 11755 F DEBUG   :       #00 pc 0026f4c4  /vendor/lib/hw/camera.qcom.so (CamX::DeferredRequestQueue::DispatchReadyNodes()+116) (BuildId: 50c452c40840911b1ad21cacaa70720d)

01-14 00:43:41.217 11755 11755 F DEBUG   :       #01 pc 002724af  /vendor/lib/hw/camera.qcom.so (CamX::DeferredRequestQueue::FenceSignaledCallback(int*, unsigned long long)+68) (BuildId: 50c452c40840911b1ad21cacaa70720d)

01-14 00:43:41.217 11755 11755 F DEBUG   :       #02 pc 0027d623  /vendor/lib/hw/camera.qcom.so (CamX::pipeline::NonSinkPortFenceSignaled(int*, unsigned long long)+42) (BuildId: 50c452c40840911b1ad21cacaa70720d)

01-14 00:43:41.217 11755 11755 F DEBUG   :       #03 pc 002666a1  /vendor/lib/hw/camera.qcom.so (CamX::Node::processFenceCallback(CamX::NodeFenceHandlerData*)+2196) (BuildId: 50c452c40840911b1ad21cacaa70720d)

01-14 00:43:41.217 11755 11755 F DEBUG   :       #04 pc 0026a485  /vendor/lib/hw/camera.qcom.so (CamX::Node::NodeThreadJobFamilyCb(void*)+56) (BuildId: 50c452c40840911b1ad21cacaa70720d)

01-14 00:43:41.217 11755 11755 F DEBUG   :       #05 pc 002806eb  /vendor/lib/hw/camera.qcom.so (CamX::Session::NodeThreadJobFamilySessionCb(void*)+26) (BuildId: 50c452c40840911b1ad21cacaa70720d)

01-14 00:43:41.217 11755 11755 F DEBUG   :       #06 pc 00227bd3  /vendor/lib/hw/camera.qcom.so (CamX::ThreadCore::DispatchJob(CamX::RuntimeJob*)+110) (BuildId: 50c452c40840911b1ad21cacaa70720d)

01-14 00:43:41.217 11755 11755 F DEBUG   :       #07 pc 0022810f  /vendor/lib/hw/camera.qcom.so (CamX::ThreadCore::processJobQueue()+126) (BuildId: 50c452c40840911b1ad21cacaa70720d)

01-14 00:43:41.217 11755 11755 F DEBUG   :       #08 pc 00227e45  /vendor/lib/hw/camera.qcom.so (CamX::ThreadCore::DoWork()+216) (BuildId: 50c452c40840911b1ad21cacaa70720d)

01-14 00:43:41.217 11755 11755 F DEBUG   :       #09 pc 00227d5d  /vendor/lib/hw/camera.qcom.so (CamX::ThreadCore::WorkerThreadBody(void*)+56) (BuildId: 50c452c40840911b1ad21cacaa70720d)

01-14 00:43:41.217 11755 11755 F DEBUG   :       #10 pc 0008183f  /apex/com.android.runtime/lib/bionic/libc.so (__pthread_start(void*)+40) (BuildId: a5f6095b1756b81b09cabe26469c9f89)

01-14 00:43:41.217 11755 11755 F DEBUG   :       #11 pc 00039e65  /apex/com.android.runtime/lib/bionic/libc.so (__start_thread+30) (BuildId: a5f6095b1756b81b09cabe26469c9f89)

01-14 00:43:41.406  1093  1867 I chatty  : uid=1000(system) Thread-6 expire 1 line

01-14 00:43:41.422  1093  1188 I chatty  : uid=1000(system) FileObserver expire 2 lines

01-14 00:43:47.704  9676 11580 E AndroidRuntime: FATAL EXCEPTION: WebRTC-SurfaceTextureHelper

01-14 00:43:47.704  9676 11580 E AndroidRuntime: Process: org.thoughtcrime.securesms, PID: 9676

01-14 00:43:47.704  9676 11580 E AndroidRuntime: java.lang.IllegalArgumentException: supportsCameraApi:2348: Unknown camera ID 1

01-14 00:43:47.704  9676 11580 E AndroidRuntime:     at android.hardware.camera2.CameraManager.throwAsPublicException(CameraManager.java:1002)

01-14 00:43:47.704  9676 11580 E AndroidRuntime:     at android.hardware.camera2.CameraManager.getCameraCharacteristics(CameraManager.java:450)

01-14 00:43:47.704  9676 11580 E AndroidRuntime:     at org.webrtc.Camera2Session.start(Camera2Session.java:304)

01-14 00:43:47.704  9676 11580 E AndroidRuntime:     at org.webrtc.Camera2Session.<init>(Camera2Session.java:296)

01-14 00:43:47.704  9676 11580 E AndroidRuntime:     at org.webrtc.Camera2Session.create(Camera2Session.java:274)

01-14 00:43:47.704  9676 11580 E AndroidRuntime:     at org.webrtc.Camera2Capturer.createCameraSession(Camera2Capturer.java:39)

01-14 00:43:47.704  9676 11580 E AndroidRuntime:     at org.webrtc.CameraCapturer$5.run(CameraCapturer.java:272)

01-14 00:43:47.704  9676 11580 E AndroidRuntime:     at android.os.Handler.handleCallback(Handler.java:938)

01-14 00:43:47.704  9676 11580 E AndroidRuntime:     at android.os.Handler.dispatchMessage(Handler.java:99)

01-14 00:43:47.704  9676 11580 E AndroidRuntime:     at android.os.Looper.loop(Looper.java:223)

01-14 00:43:47.704  9676 11580 E AndroidRuntime:     at android.os.HandlerThread.run(HandlerThread.java:67)

01-14 00:43:47.704  9676 11580 E AndroidRuntime: Caused by: android.os.ServiceSpecificException: supportsCameraApi:2348: Unknown camera ID 1 (code 3)

01-14 00:43:47.704  9676 11580 E AndroidRuntime:     at android.os.Parcel.createExceptionOrNull(Parcel.java:2387)

01-14 00:43:47.704  9676 11580 E AndroidRuntime:     at android.os.Parcel.createException(Parcel.java:2357)

01-14 00:43:47.704  9676 11580 E AndroidRuntime:     at android.os.Parcel.readException(Parcel.java:2340)

01-14 00:43:47.704  9676 11580 E AndroidRuntime:     at android.os.Parcel.readException(Parcel.java:2282)

01-14 00:43:47.704  9676 11580 E AndroidRuntime:     at android.hardware.ICameraService$Stub$Proxy.supportsCameraApi(ICameraService.java:906)

01-14 00:43:47.704  9676 11580 E AndroidRuntime:     at android.hardware.camera2.CameraManager.supportsCameraApiLocked(CameraManager.java:1055)

01-14 00:43:47.704  9676 11580 E AndroidRuntime:     at android.hardware.camera2.CameraManager.supportsCamera2ApiLocked(CameraManager.java:1031)

01-14 00:43:47.704  9676 11580 E AndroidRuntime:     at android.hardware.camera2.CameraManager.getCameraCharacteristics(CameraManager.java:423)

01-14 00:43:47.704  9676 11580 E AndroidRuntime:     ... 9 more
 
Last edited:

MatteCarra

Senior Member
Feb 7, 2019
53
175
Milan
Can anyone please test if alarms while the phone is turned off trigger the power on of the device?
I have not managed to make it work on my device, but I'm wondering if maybe it's my fault.
Thanks a lot in advance.
P.S: it seems to work
 
Last edited:

qualo

Senior Member
Jul 22, 2008
74
19
Hello. With last update, 20210306, i can't open videos on WhatsApp or Telegram. Is it there any new setting or something that must be activated/disabled (in gallery, security, etc ...) or is it a bug?. Thanks
edit: videos can be saved and open directly in gallery or Google photos, but not inside WhatsApp or telegram.
 

Top Liked Posts

  • 1
    What about face unlock? Any news?
    not going to add in los
    1
    Clarification on this because I'm also having problems where the prescribed firmware update process doesn't work: is the encryption password separate from the pin/etc used in the usual lockscreen? Would just removing the pin/pass from system settings suffice, or is there a hidden process to it?
    Yes just remove the lockscreen security.
  • 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.
    2
    I built LineageOS 18.1 from official sources today, did a complete factory reset to stock OxygenOS and then flashed my build of LineageOS from today.

    Everything seems to work great so far, you can look forward for the official build on Tuesday i guess ;)
    2
    I reccomend everyone to use nikgapps package...it is most stable in my opinion...and ut hase pixel apps too
    Yes, NikGapps is the best option right now! (+ unlimited google photos storage ;-))
    OpenGapps 11 is not stable for me. (setup crash when adding google account)
    2
    It didn't miss It hink it was merged intentionally after this week's build slot. Wiki is not merged yet for instance. But you're right next build if successful will be 18.1
    I think it is not intentional as fajita (6T) build is scheduled later today.
    EDIT: fajita build is canceled
    EDIT2: never mind, it is being rebuild
  • 15
    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:
    8
    ofcause i want los 18.1 by luk1337.
    me too
    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.
    2
    Clean flash, latest OOS, TWRP, LOS 18 in both slots, and Nikgapps and Magisk Modded. It boots, but NFC it´s no working. All the rest in my initial setup works ok. I didn´t try camera at moment.
    With Magisk Canary it doesn´t boot, goes to fastboot mode.
    At first it doesn´t pass Safetynet test. With Magisk Props module it´s ok. (Correction: Magisk props works with Manager Canary app over Magisk Modded, but root it´s lost)
    Thanks dev for your work!
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone