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

Search This thread

muphetz

Senior Member
  • May 9, 2013
    239
    68
    OnePlus 7 Pro

    Attachments

    • Screenshot_20210414-173024_Settings.png
      Screenshot_20210414-173024_Settings.png
      78.8 KB · Views: 77
    • Like
    Reactions: cantenna

    HippoMan

    Senior Member
    May 5, 2009
    1,646
    489
    Hippoland
    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
     
    • Like
    Reactions: T-RoR and cantenna

    xXRapToRiXx

    Senior Member
    Nov 15, 2014
    537
    155
    Nice tip, where can I find the stock boot image? I was struggling updating Magisk to the latest version.

    EDIT: Nevermind, I've dumped it form the LOS zip. Now I have the latest Magisk Canary working flawlessly! Thanks.
    How to get the boot.img from that zip? By extracting it I do not get any img. files
     

    LuK1337

    Recognized Developer
    Jan 18, 2013
    8,380
    16,742
    Samsung Galaxy S III I9300
    Moto G 2014
    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.
     

    xXRapToRiXx

    Senior Member
    Nov 15, 2014
    537
    155
    OK I had some time now to play around with the rom and so far it's pretty nice. There are however a few things i am not sure about/ I have some questions about:
    1. Is there a resolution option to switch between 1080p and 1440p like on OOS?
    2. I cannot get google calendar to work, it was not installed via the recommended Mindthegapps and if I try to install it from playstore it does not open. Same thing when copying the APK to System/Product/app and setting permissions.
    3. Is there a burn-in protection implemented for the statusbar, or do I have to keep a manual eye on the brightness levels?

    Thx in advance

    Edit: I solved Problem Nr.2 via using Nikgapps Stock.
     
    Last edited:

    xXRapToRiXx

    Senior Member
    Nov 15, 2014
    537
    155
    Just got 18.1 sans Google Play Services setup and configured on my OP7Pro this morning. I did a fresh install and using the linked instructions was able to update the bits of OP firmware as well.

    Note: When the instructions for that firmware upgrade say to install the 18.1 recovery image and boot into it and access fastboot through it, they absolutely mean it. I glossed over this initially and was frustrated by not being able to flash certain critical partitions until I realized that I had skipped a few steps that turned out to be pertinent.

    @LuK1337 Thank you so much for all of your work! So far so good with 18.1. I'll be updating my wife's device in a couple weeks and she's running Google Play Services and my success today bodes well for that upgrade!
    I don't have phython installed nor Do I have experience with it. Did you or anyone else go through the step "Extract payload.bin using update-payload-extractor" ? If so could anyone just make a dowload link to those files (from latest OxygenOS 11 stable) so I can just download those extracted files? I have searched the thread but could not find anything.
     

    iAnhur

    New member
    Jan 26, 2018
    4
    0
    I noticed the fingerprint placeholder icon is always slightly left or slightly right from where the center of the sensor is. Dunno if this is normal or not but it is slightly annoying.
    Just found this but I also have this so it's good to know it's not just me. I assumed it was just how it is right now. Other than that, I'm finding this to be more stable than OOS 11. I was having a lot of really weird display bugs with OOS
     

    washichi

    Senior Member
    Jan 12, 2012
    141
    79
    OnePlus 3
    OnePlus 7 Pro
    just noticed I can't connect to my PC for File Transfer.
    my phone is recognized as ' Google Nexus ADB Interface' (with ADB disabled).
    PTP work fine.

    Anyone knows if this can be driver related? Didn't have any problem with OOS 11 (or earlier versions).
     

    xXRapToRiXx

    Senior Member
    Nov 15, 2014
    537
    155
    been running a day so far and battery is way better than oxygen. Much more stable and no call bug. Been using Kirisakura_Guacamole_R_1.1.3 kernel with it today to see how battery is too. @LuK1337 are you going to enable the higher gpu step at all on stock kernel?
    Can you give us an update how the custom kernel compares to the build-in Kernel in terms of battery life? I would just flash the custom kernel myself but since I can't get twrp to work backing up boot.img is not possible and i really don't want to reinstall linegaOS completly if i wanna go back to stock kernel. Especially since I also can't make a backup of my data partition withoid twrp working.
    Thx in advance
     
    Last edited:

    travis82

    Senior Member
    Jan 8, 2011
    1,524
    1,688
    38
    Marysville, Washington
    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.
     

    Attachments

    • Screenshot_20210417-160440_SmartPack-Kernel_Manager.png
      Screenshot_20210417-160440_SmartPack-Kernel_Manager.png
      139.7 KB · Views: 68

    zyguo

    Senior Member
    Nov 27, 2011
    91
    5
    OK I had some time now to play around with the rom and so far it's pretty nice. There are however a few things i am not sure about/ I have some questions about:
    1. Is there a resolution option to switch between 1080p and 1440p like on OOS?
    2. I cannot get google calendar to work, it was not installed via the recommended Mindthegapps and if I try to install it from playstore it does not open. Same thing when copying the APK to System/Product/app and setting permissions.
    3. Is there a burn-in protection implemented for the statusbar, or do I have to keep a manual eye on the brightness levels?

    Thx in advance

    Edit: I solved Problem Nr.2 via using Nikgapps Stock.
    1. I used to use a shell command via tasker to change resolution while TV out, it's something like vm size 1920x1080, you can search for the exact format.
     

    wp007

    Senior Member
    Aug 22, 2016
    97
    17

    xXRapToRiXx

    Senior Member
    Nov 15, 2014
    537
    155
    I have to ask, because I didn't get it yet. When I come from rooted official LOS 17.1 with TWRP and Magisk I have to do the following?

    1. Flash Lineage Recovery (or is booting enough?)
    2. Firmware Update (as described in https://wiki.lineageos.org/devices/guacamole/fw_update
    3. LOS Upgrade (as described in https://wiki.lineageos.org/devices/guacamole/upgrade)
    4. Flash Magisk
    5. Dont't have to wipe anything and reboot

    Is this correct?
    Seems about right but wiping Data and cache before installing linage recovery might be a good idea since a clean install is recommended when switching Android versions. I personally would not dirty flash.
     

    wp007

    Senior Member
    Aug 22, 2016
    97
    17
    Seems about right but wiping Data and cache before installing linage recovery might be a good idea since a clean install is recommended when switching Android versions. I personally would not dirty flash.
    Wiping data but not system before installing recovery? But why would it be important to do this before?
     

    xXRapToRiXx

    Senior Member
    Nov 15, 2014
    537
    155
    Wiping data but not system before installing recovery? But why would it be important to do this before?
    The reason I said wipe before is because once you update the firmware files to the new ones TWRP won't boot up. At least for me it does not. Unfortunately you will be stuck with lineage recovery which works fine but when I choose factory reset in lineage recovery it forces you to format data (which includes the internal storage). I don't know about you but for me having to format DATA just to make a clean install is painful.
     

    Top Liked Posts

    • 1
      Thanks @LuK1337 for all the developments. Currently the slider only mutes the tone volume and the notification volume. Could the slider also mute the multimedia volume?
    • 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
      im not gonna get it tonight, too much vodka, but thank you for getting me on my way. been at this for a week and in the last hour or so youve helped me more than anything else has. i bricked again and am using the msmtool to go back to 9 to upgrade to 10. thanks for the help sober matt will take it from here tomorrow
      Yeah no problem man. If you want I can help you out tomorrow. But what happened?
      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
      used msm to downgrade to 9, upgraded to 10 then i was able to boot into twrp 3.4.0. thank you so much my man, or woman. you ****ing rock!
      No problem man. If you need help with anything else I'm here. I may not know much, but I'll try my best to help.
    • 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