[ROM][OFFICIAL][enchilada][12] LineageOS 19

Search This thread

mobileanimal

Senior Member
Jul 23, 2013
56
14
Hi all, I just installed this on my OP6 hoping it might have corrected an issue with 18.1 and VoLTE, but it did not. If I turn on airplane mode, then turn it back off, I lose VoLTE calling. *#*#4636#*#* > Phone info > 3 dots > IMS Service Status will no longer show Registered for IMS registration - it will show "Not Registered" and stay that way until the phone is rebooted. Voice over LTE will show as Unavailable. The VoLTE switch is still enabled in SIM settings. I don't see anything interesting in hours of searching through logcats. Can someone else let me know if they're also seeing this issue when turning on airplane mode and back off before I attempt a full rebuild?
Thanks
 

HoreaM

Member
Oct 4, 2020
7
0
Does anyone else always get the location privacy indicator whenever they unlock their phone on the new build, even if the location is turned off?
The icon in the upper right corner I'm referring to:

2022-05-26 11_47_31-Window.png
 

lm089

Senior Member
Jun 26, 2011
650
207
Munich
Are you on the latest build 19-20220524-NIGHTLY-enchilada ? This issue is supposedly fixed in latest build.
same situation as @HoreaM: I had skipped last week's build (20220517) because of this behaviour, and installed this week's (20220524) because of the "exempt" note in this build's change list, but since then I'm seeing the same on every wake-up. The green icon then disappears after a second or so. In my case this is with location turned on, btw.
Tested freezing some apps that I know are using GPS data, but no change.
Also sometimes in between e.g. while I'm typing this here the icon keeps appearing for a short moment
 
Last edited:

madman

Senior Member
Apr 21, 2011
1,652
466
Planet Earth
OnePlus 5
OnePlus 6
If you pull down and tap on the notification, it will tell you what is location indicator is for. Is it for phone services again? I have been running the latest build (I did upgrade to the one which had the problem in between) and don't see that issue of phone service location indicator anymore. I do see some people on reddit/gitlab saying they still see issue. I don't know how/why.

There is another change coming to exempt some more stuff from location indicator. Maybe that will help? But unless someone here tells what app (like com.android.phone for TeleService) I don't know if they can do anything.
 
  • Like
Reactions: lm089

treyy

Senior Member
Nov 19, 2010
255
30
Bootloop happens if you don't execute "adb enable-verity" after the installation of ih8sn.
if you want to remove ih8sn then remove the files manually using adb or install rom using recovery(as mentioned in lineage wiki, just dont wipe data).
@vikash1994b THX for your answer.

When i install ih8sn like this :

enable usb debugging and rooted debugging in the developer options
* reboot phone
* extract the ih8sn.zip and put the files in your adb folder
* execute the following commands in your adb folder:
adb wait-for-device root
adb wait-for-device remount
adb wait-for-device push 60-ih8sn.sh /system/addon.d/
adb wait-for-device push ih8sn /system/bin/
adb wait-for-device push ih8sn.rc /system/etc/init/
adb wait-for-device push ih8sn.conf /system/etc/
*reboot phone

Do i have to execute "adb enable-verity" before or after the last reboot? Thx
 

lm089

Senior Member
Jun 26, 2011
650
207
Munich
Any simplex way for maintaining twrp when updating nightly?
If you are using Magisk you can try what I posted at #163:


Only disadvantage of that method is that using the LOS updater is extremely slow, at least on my device. Still that's how I do it
 
Last edited:

madman

Senior Member
Apr 21, 2011
1,652
466
Planet Earth
OnePlus 5
OnePlus 6
I appreaciate that LOS gives me battery history since last full charge (I heard AOSP/Pixel software made it history of last 12/24 hours) but this is definitely buggy. Like those percentages of app battery usage is out of what like 200% ? 300% ?

Screenshot_20220526-085002_Settings.png
 

vikash1994b

Senior Member
Dec 7, 2012
1,016
611
27
New Delhi
Xiaomi Mi 3
Xiaomi Mi A1
@vikash1994b THX for your answer.

When i install ih8sn like this :

enable usb debugging and rooted debugging in the developer options
* reboot phone
* extract the ih8sn.zip and put the files in your adb folder
* execute the following commands in your adb folder:
adb wait-for-device root
adb wait-for-device remount
adb wait-for-device push 60-ih8sn.sh /system/addon.d/
adb wait-for-device push ih8sn /system/bin/
adb wait-for-device push ih8sn.rc /system/etc/init/
adb wait-for-device push ih8sn.conf /system/etc/
*reboot phone

Do i have to execute "adb enable-verity" before or after the last reboot? Thx
Doesn't matter before or after reboot, you can execute it just after installing ih8sn and then reboot.
BTW there is a powershell shell script too in the folder for installing ih8sn.
 
  • Like
Reactions: treyy

gamertag128

Senior Member
Nov 15, 2021
50
33
@vikash1994b THX for your answer.

When i install ih8sn like this :

enable usb debugging and rooted debugging in the developer options
* reboot phone
* extract the ih8sn.zip and put the files in your adb folder
* execute the following commands in your adb folder:
adb wait-for-device root
adb wait-for-device remount
adb wait-for-device push 60-ih8sn.sh /system/addon.d/
adb wait-for-device push ih8sn /system/bin/
adb wait-for-device push ih8sn.rc /system/etc/init/
adb wait-for-device push ih8sn.conf /system/etc/
*reboot phone

Do i have to execute "adb enable-verity" before or after the last reboot? Thx
Which .zip did you use, did it fix safetynet and do you need to do the installation every time, when you update to a new build?

Edit: I didn't extracted a fingerprint on OxygenOS. Could I still do it on LineageOS or is there a need, if I just use the PowerShell script?
 
Last edited:

Top Liked Posts

  • 1
    Just a question out of pure curiosity - no complaint: why is it that LOS 19 is taking so long (at least 1 hour on my device) for an OTA update? [...] Could that have to do with the way I setup the phone, or with apps I installed?
    I also wondered about that and had a look via `logcat`. What happens is that after the actual update installation, `dex2oat` is triggered for the most commonly used apps (seems to be about 50 % of the apps). I'm not sure whether this is a new feature with Android 12, but this usually takes up to one hour for me, too, since I have many apps installed.

    In short, this means the most commonly used apps are optimized for the phone before the reboot to the new system. The same process usually happens when the phone is idle (and connected to the charger) for over two hours, e.g. when charging overnight.

    I think this happening right during OTAs is something new, though, but it likely improves the "post-OTA-experience" a bit since apps will start faster before the first "overnight charge", i.e. "things will settle" faster ;-).

    The time for updates to run through can be improved (at cost of more battery usage) by going into the updater, pressing the three dots in the top right corner, and then in settings selectiong to give priority to the update process. This shortens down the process by 20-30 % for me.
    1
    The time for updates to run through can be improved (at cost of more battery usage) by going into the updater, pressing the three dots in the top right corner, and then in settings selectiong to give priority to the update process. This shortens down the process by 20-30 % for me.
    Thanks, I sure will try that next time (if I remember... ;))
    1
    Thanks, I sure will try that next time (if I remember... ;))
    Maybe it also depends upon how many apps you have installed or sth? I use the priority setting, too, and for me it just took around 30-40 minutes this morning.
  • 2
    Magisk 25.1 is out now. Does the same apply for updates? Should I sideload or just update from the app?
    I updated Magisk through the app and it worked fine
    2
    I updated to the 06-21-22 update and lost magisk and root. I had a patched boot.img I was under the impression that wouldn't be touched when doing OTA updates?
    As clarified just a few posts earlier this appears to not be the case depending on how you installed Magisk.

    Around the time 24.2 came out I had to completely wipe my phone and reinstall LOS. I did so multiple times in different ways for different reasons at that point. Also the way I installed Magisk.
    It appears that the sideload way was the one that remained in the end. After this I noticed that I no longer had to manually install Magisk to the inactive slot between update and reboot. I incorrectly assumed that the following changelog note was the reason:
    [App] Major app upgrade flow improvements

    2
    How can you say it's working fine???
    Because it IS working fine on my phone, didn't have a single forced reboot since quite a few weeks now. No probs with auto rotation
    2
    Does somebody know, why todays update got revoked?
    I have installed it and not facing any issues
    2
    Yeah, I used the recommended way by having the app patch boot.img, followed by flashing it.
    The problem is discussed here:
    In short, when installed via the recommended method, Magisk will not survive OTAs. This appears to be by design by the developer, see this comment:

    The old, unsupported approach (sideloading the .zip) still installs the retention script. That's also how I installed, and retention during OTAs is also still working for me, but that seems not officially supported anymore.
  • 36
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 12, 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:
    6
    Just did a dirty flash from LOS 18.1 and everything works fine.

    I had to reinstall some Google apps (YouTube, Gmail, Keep, GCam, Photos), as they stopped working after the upgrade (maybe because I accidentally clicked No on the Signature verification failed screen while flashing Gapps and didn't notice, then the OS didn't boot. whoops. So I went back into the recovery and flashed Gapps again. Sure enough, the install went through. So be careful and make sure to click the correct button, lol)

    Everything else seems to work perfectly!

    Thanks again LuK for your work!

    In case anyone with Gapps and Magisk wants to try a dirty flash from 18.1, here are the steps I did:
    (you're on your own if things break! better to do a clean flash! magisk isn't officially supported!)

    1. Restored images in Magisk
    2. Removed PIN and fingerprints
    (Not sure if these first two steps are needed, but did them just in case)
    3. adb reboot sideload
    4. adb sideload lineage-19.1-20220426-nightly-enchilada-signed.zip
    5. Advanced->Reboot to Recovery
    6. Apply Update->Apply from ADB
    7. adb sideload MindTheGapps-12.1.0-arm64-20220416_174313.zip
    8. adb sideload Magisk-v24.3.apk
    9. Back->Reboot system now
    5
    I'm using a single SIM and I see the same thing often. I guess it depends on the amount of icons you have in the status bar. I observed this since the first build
    Change the smallest width to 411 in developer options.
    Before OOS 11 it was set to 411 by default but that changed with OOS11.
    4
    I'm on the May 17th enchilada nightly, and came directly from 18.1. I'd like to use ANT+, but no worky :confused:. Is this a known issue? Are there plans to fix it?

    ANT+ also didn't work when I went from 17.1 to 18.1, but I fixed it by upgrading the firmware. I tried that again on 19, but it didn't fix it this time.

    Here is what the ANT Tester app shows on LOS 19:

    View attachment 5619435
    4
    Question: Will there ever be more stable versions than the "nightlies"? I'm unsure where to put them in terms of quality and stability- should they be considered as "alpha" versions? Or are they even more reliable than "betas"?

    Thanks in advance.
    imo the first 2 nightlies were perfectly stable. No crashes, fc, excessive battery drain, whatever. (y)