• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

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

Search This thread

LuK1337

Recognized Developer
Jan 18, 2013
8,446
16,851
Samsung Galaxy S III I9300
Moto G 2014
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:
 
Last edited:

Nikhil

Senior Member
Sep 26, 2012
1,413
2,325
Ahmedabad
OnePlus 7 Pro
Here is the link to working gapps for android R :)

NikGapps-R

- Comes with core package (mininum apps required to run playstore)
- Comes with Pixel Launcher (starting macro, stock and full package) (you need to set pixel launcher as default home app if you're flashing any of those packages)
- Comes with Google Dialer (that replaces aosp dialer) (you need to set Google Dialer as default or use nikgapps.config to retain aosp dialer)
- Comes with vanced youtube (v14), those of you who prefer stock youtube can easily update the app from playstore
- 'Select' option in Recents works perfectly
- App Suggestions works perfectly
- The installation is fully configurable, you can skip installing the package you want, you can skip removal of aosp counter part (using nikgapps.config)

checkout NikGapps Website for all the details regarding the project

You can find the screenshots here :)
 
Last edited:

vladvlad12

Senior Member
May 27, 2020
126
24
25
Bucharest
Not work with Dualboot TWRP with A11 Magisk modded,,it stuck when Patching sepolicy

From what I know the dualboot twrp can not yet decrypt android 11, so it is not possible to run it in a dual boot.

I had the same issue cause I tried to install dual boot withA11 and OxygenOS beta 18, and neither one of them work.

So I installed last stock stable OOS and is working in dualboot.
 

ttle54

Member
Sep 19, 2018
15
1

pro_granade

Senior Member
Jan 22, 2013
1,001
866
Kansas City
The Linage 18.0 was fine running without any Gapps on until I install this Gapps. It's froze and now I have to reflash it. OP, can you included Gapps in your package like Kang, and other Android 11 ROMs? That way, we wouldn't be confused where to download the Gapps for Android 11
I experienced the same thing.
 

Nikhil

Senior Member
Sep 26, 2012
1,413
2,325
Ahmedabad
OnePlus 7 Pro
The Linage 18.0 was fine running without any Gapps on until I install this Gapps. It's froze and now I have to reflash it. OP, can you included Gapps in your package like Kang, and other Android 11 ROMs? That way, we wouldn't be confused where to download the Gapps for Android 11


I experienced the same thing.

Which package did you flash? Could you try the core package to see if that's working for you? Since it has the minimum apps required to run the playstore and any other google app won't conflict
 

Nikhil

Senior Member
Sep 26, 2012
1,413
2,325
Ahmedabad
OnePlus 7 Pro
The Linage 18.0 was fine running without any Gapps on until I install this Gapps. It's froze and now I have to reflash it. OP, can you included Gapps in your package like Kang, and other Android 11 ROMs? That way, we wouldn't be confused where to download the Gapps for Android 11


I experienced the same thing.

Guys,

Its working perfectly, you're experiencing freeze because you're on trebuchet launcher and NikGapps ships pixel launcher that contains overlay that's conflicting with Trebuchet.

You can either skip installating PixelLauncher using nikgapps.config or go to settings -> default apps and set Pixel Launcher as default.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Whoops! Here
    It looks like OnePlus is no longer dumping NV items on 8150 for some reason so we are always falling back to random WLAN MAC...
    I'll remove code that nukes wlan_mac.bin every boot so that WiFi MAC will at least be "stable".
    2
    For people who are unable to boot/flash TWRP try the nebrassy version:

    worked for me with 'fastboot boot TWRP-3.5.1-guacamole-Nebrassy-3.img'
    1
    I can't flash Gapps on LineageOS 18.1nither from the Lineage Recovery nor TWRP. Is there any solution for that?
    try adb sideload
    1
    What can I do to help?
    It also happens in safemode, and reflects rendomly in About Phone as well. It's a bit obnoxious having a new IP every reboot, even if I could just run a boot script with root but ifconfig hwaddr also doesn't affect it
    Hi Ekriirkem, Hi Luk1337,

    I've the same behavior.
    Also try to change MAC with "ifconfig" or "ip", but it doesn't work.

    I'm "glad" to see some others has the same behavoir.

    Model: GM1913

    What is your--
    LineageOS version: 18.1-20210627
    LineageOS Download url: https://download.lineageos.org/guacamole
    Update: OTA
    Gapps version: --

    Did you--
    wipe: yes
    restore with titanium backup: no
    reboot after having the issue: yes, multiple times

    Are you using--
    a task killer: no
    a non-stock kernel: no (whatever lineage installed as-is)
    other modifications: magisk, but behavoir is there with or without root

    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
    It works with latest OOS.
    Never worked with LOS 18.1 Images
    Also installed/flashed latest vendor firmware (https://wiki.lineageos.org/devices/guacamole/fw_update)

    After reboot, the file /mnt/vendor/persist/wlan_mac.bin contains new MACs. The MAC from the first line will be used for the wireless device wlan0. Changing the wlan_mac.bin file has no effect

    Would be nice to set wlan0 adapter to the real HW-address at home and to a random HW-address on Hotspots
    1
    Same output for me; an empty folder. I'm also on the EU model GM1913
    I also just noticed all my sensors are "broken" (mainly because adaptive brightness didn't work, verified with an app that there is no accel/gyro/magnet etc)

    Here are dmesg and logcat from a safemode boot, the random mac that was assigned in About Phone is c0:ee:fb:5f:54:43
    Run restorecon -RF /mnt/vendor/persist as root (in android), that should fix sensors.
  • 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.
    14
    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
    Has anyone tried this ROM with Micro G?
    I am running Lineage 17 Micro G on my OnePlus 6t and battery is amazing!
    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.