[ROM][OFFICIAL][guacamole][11] LineageOS 18.1

Search This thread

xXRapToRiXx

Senior Member
Nov 15, 2014
537
155
i just cleaned it up so try again now. Should be better on the battery. If you all like it I can push it on gerrit so Luk1337 can aprove and merge it. All these patches should be LOS rules friendly!

View attachment 5283391View attachment 5283393
I tested your kernel out for a bit because on stock kernel i noticed the phone getting slightly warm when watching a basic 1080p 30fps YT video (in the youtube app). I patched your boot.img in latest stable Magisk and flashed the patched image via franco kernel manager. After reboot in the magsik app the ramdisk status (which used to be "yes" was now "no". I thought you might wanna know this...
I don't know exactly what ramdisk does but since the stock kernel supported it I found it weird that yours said "no" in magisk manager.
 

daniel84cs

Senior Member
Dec 27, 2011
2,624
5,440
OnePlus 7 Pro
This ROM is exceptional, I also flashed its recovery to use it as a daily driver. I definitely prefer it to oxygen, I have been using LOS since the time of the nexus, since the time of Cyanogen. Light and spotless as always, the queen of custom ROMs. However, it is very easy to install it even cleanly from TWRP and then switch to the LOS recovery. I tested it a bit unecrypt, but it runs too well, so I use it as it should be used, without root, without google and with its recovery. Thanks again Dev.
 

eminem_b

Senior Member
Sep 11, 2012
397
229
Plovdiv
www.smirky.net
This ROM is exceptional, I also flashed its recovery to use it as a daily driver. I definitely prefer it to oxygen, I have been using LOS since the time of the nexus, since the time of Cyanogen. Light and spotless as always, the queen of custom ROMs. However, it is very easy to install it even cleanly from TWRP and then switch to the LOS recovery. I tested it a bit unecrypt, but it runs too well, so I use it as it should be used, without root, without google and with its recovery. Thanks again Dev.
Can you please share your experience with the camera?
Do you have OOS Camera or GCam?
Do all the hardware cameras/sensors work?
 

daniel84cs

Senior Member
Dec 27, 2011
2,624
5,440
OnePlus 7 Pro
Can you please share your experience with the camera?
Do you have OOS Camera or GCam?
Do all the hardware cameras/sensors work?

I haven't tried LOS camera because I use gcam with the service provider (to not install google play services). With gcam the photos are excellent, comparable to the original camera, some users say even superior, you use all 3 sensors. You can also install OOS camera, but it only works as a camera, don't go video etc.
I recommend gcam, you can find more info about it on telegram groups.
 

T-RoR

Senior Member
Mar 5, 2008
52
7
Probably shouldn't have used nikgapps. Noticed that on my other devices people were having issues with them, heh.
Knowing this would have saved me a lot of work. Roger that.

One question, in gesture navigation I have removed Navigation hint, however this appears sometimes in some games and does not allow me to use that screen area. Is there any solution?
 

skythian

Senior Member
  • Nov 22, 2011
    117
    36
    Still not passing for me on latest canary build. Anyone else having this issue?
    Yes same for me (even with the canary build). But if you are using MagiskHide props with fingerprint change and UniversalSafetyNet fix, it is likely passing even if Magisk shows that it doesn't. GPay etc all work for me.
     

    envying

    Senior Member
    Mar 15, 2012
    125
    13
    I'm still having issue with safenet passing (both failures, basicintegrity, ctsprofile, and evaltype N/A).

    Here is what I got.
    was on OOS through MSTOOL reflashing;
    then update to latest OOS10;
    had on unofficial 18.1;
    start with dirty upgrade to official 18.1;
    never had the chance to pass safenet on Magisk;
    got some occasional reboot;
    backup with Titanium;
    back to LOS recovery, and did the factory reset;
    reboot, and updated to latest Magisk;
    still won't pass, even with module MagiskHide Props;
     

    HippoMan

    Senior Member
    May 5, 2009
    1,643
    483
    Hippoland
    I'm still having issue with safenet passing (both failures, basicintegrity, ctsprofile, and evaltype N/A).

    Here is what I got.
    was on OOS through MSTOOL reflashing;
    then update to latest OOS10;
    had on unofficial 18.1;
    start with dirty upgrade to official 18.1;
    never had the chance to pass safenet on Magisk;
    got some occasional reboot;
    backup with Titanium;
    back to LOS recovery, and did the factory reset;
    reboot, and updated to latest Magisk;
    still won't pass, even with module MagiskHide Props;
    Which version of Magisk are you using? There is a known problem with Magisk 22.1 which causes it to incorrectly report SafetyNet failure, even though SafetyNet is actually passing.

    This problem has been fixed in the latest Magisk canary version.

    If you're using Magisk canary and still are having this problem, then it's not due to Magisk, and perhaps something about LOS 18.1 or some other issue.
     

    Top Liked Posts

    • 1
      For me LOS work great, I don't have any bugs in the animations and it is much better than the PE. In my opinion many complain because they didn't follow the official procedure, they have TWRP , DFE , magisk , magisk modules and other kernels. If you use it CLEAN VANILLA , FOLLOWING THE INSTALLATION PROCEDURE , IT WORK AWESOME.
      IF YOU WANT GAPPS FLASH ANOTHER ROM WITH GAPPS PREINSTALLED.
    • 4
      Hi, first of all, thank you for your work!

      I just updated to 18.1 from 17.1, and noticed that the back gesture doesnt produce a vibration effect anymore. Vibration isnt broken, everywhere else it seems to work fine. Just the back gesture doesnt do it anymore.

      Is this a known issue? Or intended? Or did I mess something up?

      Logcat and dmesg are attached. I do have Magisk installed, but the logs were captured with no modules enabled. I did notice something in the logs. When it vibrates, it produces something like this:

      Code:
      04-11 17:35:05.166   935   935 D vendor.qti.vibrator: QTI Vibrator reporting capabilities: 3
      04-11 17:35:05.168   935   935 D vendor.qti.vibrator: QTI Vibrator off
      04-11 17:35:05.181  1095  2628 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
      04-11 17:35:05.181   601   601 I servicemanager: Found android.hardware.vibrator.IVibrator/default in device VINTF manifest.
      04-11 17:35:05.182  1095  2628 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
      04-11 17:35:05.182   601   601 I servicemanager: Found android.hardware.vibrator.IVibrator/default in device VINTF manifest.
      04-11 17:35:05.185   935   935 D vendor.qti.vibrator: Vibrator on for timeoutMs: 10
      04-11 17:35:05.187     0     0 I [20210411_17:35:05.185729]@0 aw8697_duration_store: val:10
      04-11 17:35:05.187     0     0 I [20210411_17:35:05.186206]@0 aw8697_activate_store: value=1
      04-11 17:35:05.187     0     0 I [20210411_17:35:05.187083]@3 aw8697->pm_awake: 1
      04-11 17:35:05.203   935   935 D vendor.qti.vibrator: QTI Vibrator off
      04-11 17:35:05.207     0     0 I [20210411_17:35:05.203444]@3 aw8697->pm_awake: 0
      04-11 17:35:05.207     0     0 I [20210411_17:35:05.204415]@1 aw8697_activate_store: value=0
      04-11 17:35:05.207     0     0 I         : [20210411_17:35:05.206860]@3 aw8697_haptic_stop_delay wait for standby, reg glb_state=0x07

      But when I do a back gesture I only get this. No "Vibrator on for ..." and no aw8697 logs.

      Code:
      04-11 17:35:16.548   935   935 D vendor.qti.vibrator: QTI Vibrator off
      [...]
      04-11 17:35:16.556   971  1456 I BpBinder: onLastStrongRef automatically unlinking death recipients: <uncached descriptor>
      04-11 17:35:16.556  3885  4083 I Finsky  : [204] rmc.a(1): Sending Heterodyne sync request for package com.android.vending
      04-11 17:35:16.558   971  1455 I BpBinder: onLastStrongRef automatically unlinking death recipients: <uncached descriptor>
      [...]
      04-11 17:35:16.567   971  1455 I BpBinder: onLastStrongRef automatically unlinking death recipients: <uncached descriptor>
      [...]
      04-11 17:35:16.570  1095  3695 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
      [...]
      04-11 17:35:16.573   601   601 I servicemanager: Found android.hardware.vibrator.IVibrator/default in device VINTF manifest.
      04-11 17:35:16.574  1095  1609 D InputDispatcher: Waiting to send key to Window{45a7a43 u0 com.topjohnwu.magisk/com.topjohnwu.magisk.ui.MainActivity} because there are unprocessed events that may cause focus to change
      04-11 17:35:16.574   971  1455 I BpBinder: onLastStrongRef automatically unlinking death recipients: <uncached descriptor>
      [...]
      04-11 17:35:16.577  1095  1609 D InputDispatcher: Waiting to send key to Window{45a7a43 u0 com.topjohnwu.magisk/com.topjohnwu.magisk.ui.MainActivity} because there are unprocessed events that may cause focus to change
      04-11 17:35:16.578  1095  3695 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
      [...]
      04-11 17:35:16.583   601   601 I servicemanager: Found android.hardware.vibrator.IVibrator/default in device VINTF manifest.
      Also RE#2: I merged a set of interesting changes. You should notice some nice improvement in the next build.
      4
      Just did an OTA update of the latest OTA.
      The 'restore images' button didn't work.

      But installing magisk to the inactive slot did!
      I don't know if it was that, or NOT using NikGapps that made it work.

      But I finally don't have to restore everything so I'm very pleased!
      Bootloop with OTA update issue is fixed with 1st may release in NikGapps. Glad that your ota update worked out. Feel free to flash nikgapps again, I'm sure you'll have seamless ota update even with nikgapps.
      3
      Haptic feedback same at OOS , even better , great update , thanks :)
      2
      OK built a Los kernel with the GPU commit from code aurora and the lz4 option in ramdisk and misc gamepads enabled. I can post the commits if you want to cherry pick them. BTW new lineage vibrations are very nice.
      2
      Hey all, strange behaviour regarding SafteyNet!!

      So I've been checking in on this thread as of late as I'm currently on 17.1 thinking about 18.1 but trying to find out what works, what doesn't SafteyNet being one of the concerns.


      but, here I am on 17.1 LineageOS still and SafteyNet has been passing all green for months.

      today I notice I'm failing SafteyNet all of a sudden on Magisk and 3rd party SafteyNet check apps are advising I am failing as well, however, I am able to still use applications that normally don't function with fail SafteyNet and I have just used google pay twice.

      so what I'm saying, if your testing and it says your failing, you may be actually passing. please try to test with google pay or a SafteyNet app like Pokemon go and kindly confirm back please.
      Yes, I mentioned that above. It turns out to be a known issue with the SafetyNet checker in Magisk.

      It now seems to be fixed in Magisk Canary:
      https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84846949
    • 16
      FYI, next week you'll get the first official 18.1 build.
      Follow official installation instructions on https://wiki.lineageos.org for upgrade/install and https://gist.github.com/luk1337/6c18b1910fa38292f2d5fbd3df47fd91 for firmware update as OOS 11 FW is needed.
      10
      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:
      7
      As someone who doesn't have that much experience in flashing, it' not a rhetorical question for me. Do I understand it correctly that the FW update is not necessary when updating from 17.1 to 18.1, since there is no information about it in the corresponding instructions in the wiki?
      It is a rhetorical question. I clearly said that OOS 11 firmware is needed; you wouldn't be running OOS 11 firmware on Lineage 17.1, would you? Also I'll update wiki warning when first build is out.
      4
      Just did an OTA update of the latest OTA.
      The 'restore images' button didn't work.

      But installing magisk to the inactive slot did!
      I don't know if it was that, or NOT using NikGapps that made it work.

      But I finally don't have to restore everything so I'm very pleased!
      Bootloop with OTA update issue is fixed with 1st may release in NikGapps. Glad that your ota update worked out. Feel free to flash nikgapps again, I'm sure you'll have seamless ota update even with nikgapps.
      4
      Hi, first of all, thank you for your work!

      I just updated to 18.1 from 17.1, and noticed that the back gesture doesnt produce a vibration effect anymore. Vibration isnt broken, everywhere else it seems to work fine. Just the back gesture doesnt do it anymore.

      Is this a known issue? Or intended? Or did I mess something up?

      Logcat and dmesg are attached. I do have Magisk installed, but the logs were captured with no modules enabled. I did notice something in the logs. When it vibrates, it produces something like this:

      Code:
      04-11 17:35:05.166   935   935 D vendor.qti.vibrator: QTI Vibrator reporting capabilities: 3
      04-11 17:35:05.168   935   935 D vendor.qti.vibrator: QTI Vibrator off
      04-11 17:35:05.181  1095  2628 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
      04-11 17:35:05.181   601   601 I servicemanager: Found android.hardware.vibrator.IVibrator/default in device VINTF manifest.
      04-11 17:35:05.182  1095  2628 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
      04-11 17:35:05.182   601   601 I servicemanager: Found android.hardware.vibrator.IVibrator/default in device VINTF manifest.
      04-11 17:35:05.185   935   935 D vendor.qti.vibrator: Vibrator on for timeoutMs: 10
      04-11 17:35:05.187     0     0 I [20210411_17:35:05.185729]@0 aw8697_duration_store: val:10
      04-11 17:35:05.187     0     0 I [20210411_17:35:05.186206]@0 aw8697_activate_store: value=1
      04-11 17:35:05.187     0     0 I [20210411_17:35:05.187083]@3 aw8697->pm_awake: 1
      04-11 17:35:05.203   935   935 D vendor.qti.vibrator: QTI Vibrator off
      04-11 17:35:05.207     0     0 I [20210411_17:35:05.203444]@3 aw8697->pm_awake: 0
      04-11 17:35:05.207     0     0 I [20210411_17:35:05.204415]@1 aw8697_activate_store: value=0
      04-11 17:35:05.207     0     0 I         : [20210411_17:35:05.206860]@3 aw8697_haptic_stop_delay wait for standby, reg glb_state=0x07

      But when I do a back gesture I only get this. No "Vibrator on for ..." and no aw8697 logs.

      Code:
      04-11 17:35:16.548   935   935 D vendor.qti.vibrator: QTI Vibrator off
      [...]
      04-11 17:35:16.556   971  1456 I BpBinder: onLastStrongRef automatically unlinking death recipients: <uncached descriptor>
      04-11 17:35:16.556  3885  4083 I Finsky  : [204] rmc.a(1): Sending Heterodyne sync request for package com.android.vending
      04-11 17:35:16.558   971  1455 I BpBinder: onLastStrongRef automatically unlinking death recipients: <uncached descriptor>
      [...]
      04-11 17:35:16.567   971  1455 I BpBinder: onLastStrongRef automatically unlinking death recipients: <uncached descriptor>
      [...]
      04-11 17:35:16.570  1095  3695 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
      [...]
      04-11 17:35:16.573   601   601 I servicemanager: Found android.hardware.vibrator.IVibrator/default in device VINTF manifest.
      04-11 17:35:16.574  1095  1609 D InputDispatcher: Waiting to send key to Window{45a7a43 u0 com.topjohnwu.magisk/com.topjohnwu.magisk.ui.MainActivity} because there are unprocessed events that may cause focus to change
      04-11 17:35:16.574   971  1455 I BpBinder: onLastStrongRef automatically unlinking death recipients: <uncached descriptor>
      [...]
      04-11 17:35:16.577  1095  1609 D InputDispatcher: Waiting to send key to Window{45a7a43 u0 com.topjohnwu.magisk/com.topjohnwu.magisk.ui.MainActivity} because there are unprocessed events that may cause focus to change
      04-11 17:35:16.578  1095  3695 E VibratorService: Failed to issue command to vibrator HAL. Retrying.
      [...]
      04-11 17:35:16.583   601   601 I servicemanager: Found android.hardware.vibrator.IVibrator/default in device VINTF manifest.
      Also RE#2: I merged a set of interesting changes. You should notice some nice improvement in the next build.
    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