• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM] [11.0] [PME] LineageOS 18.1 [UNOFFICIAL]

Search This thread

raul16

Senior Member
Thanks for the update.

But the reboot loop issue is still there. And my phone panic rebooted as well 3 or 4 times since I installed the build less than 12 hours ago. All happened while performing normal activities, not the heavy ones. Like opening file explorer, etc. In previous build, it only happened when doing heavy tasks like opening Aspahlt 9, or doing mukltitasking in apps. Also, that was fixed by running my phone in 720p resolution insted of default 1440p. However, in this build, even 720p resolution doesn't seem to reduce stress.

The following logs have been attached:

adb shell su -c "cat /sys/fs/pstore/console-ramoops" > console-ramoops.log
adb shell su -c "cat /sys/fs/pstore/dmesg-ramoops-0" > dmesg-ramoops-0.log
adb shell su -c "cat /sys/fs/pstore/dmesg-ramoops-1" > dmesg-ramoops-1.log
adb shell su -c "cat /sys/fs/pstore/pmsg-ramoops-0" > pmsg-ramoops-0.log
could not replicate your issues. no crash / reboot in daily usage - I've started using 0912 as main phone on 13/09 (!)
dmesg-ramoops provide some insights on what happened:

on first file [ aka -0]
<3>[ 13.184846] BUG: scheduling while atomic: exe/1206/0x00000002
<6>[ 13.184861] Modules linked in:
<6>[ 13.184872] ------------[ cut here ]------------
<2>[ 13.184879] Kernel BUG at ffffffc0000d0650 [verbose debug info unavailable]
<0>[ 13.184887] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
<6>[ 13.184894] Modules linked in:
<6>[ 13.184905] CPU: 3 PID: 1206 Comm: exe Tainted: G W 3.18.140-lineage #394
<6>[ 13.184911] Hardware name: HTC Corporation. MSM8996v3 PME_JAPAN PVT (DT)
<6>[ 13.184917] task: ffffffc06681b000 ti: ffffffc0669dc000 task.ti: ffffffc0669dc000
<6>[ 13.184930] PC is at __schedule_bug+0x40/0x44
<6>[ 13.184937] LR is at __schedule_bug+0x3c/0x44
on second file [ aka -1]
<3>[24353.054198] BUG: scheduling while atomic: ogle.android.gm/15670/0x00000002
<4>[24353.054214] Modules linked in:
<4>[24353.054226] ------------[ cut here ]------------
<2>[24353.054233] Kernel BUG at ffffffc0000d0650 [verbose debug info unavailable]
<0>[24353.054240] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
<4>[24353.054246] Modules linked in:
<4>[24353.054258] CPU: 1 PID: 15670 Comm: ogle.android.gm Tainted: G W 3.18.140-lineage #394
<4>[24353.054264] Hardware name: HTC Corporation. MSM8996v3 PME_JAPAN PVT (DT)
<4>[24353.054271] task: ffffffc064360000 ti: ffffffc072f38000 task.ti: ffffffc072f38000
<4>[24353.054285] PC is at __schedule_bug+0x40/0x44
<4>[24353.054292] LR is at __schedule_bug+0x3c/0x44
<4>[24353.054298] pc : [<ffffffc0000d0650>] lr : [<ffffffc0000d064c>] pstate: 60000145

besides LOS i have installed NikGapps [0815] core, gmail, maps, YT, Google, Netflix. Magisk 23.0 (with hide enabled) for passing CTS. No other modules installed as no need.
what configuration do you have / use ?
 
could not replicate your issues. no crash / reboot in daily usage - I've started using 0912 as main phone on 13/09 (!)
dmesg-ramoops provide some insights on what happened:

on first file [ aka -0]
<3>[ 13.184846] BUG: scheduling while atomic: exe/1206/0x00000002
<6>[ 13.184861] Modules linked in:
<6>[ 13.184872] ------------[ cut here ]------------
<2>[ 13.184879] Kernel BUG at ffffffc0000d0650 [verbose debug info unavailable]
<0>[ 13.184887] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
<6>[ 13.184894] Modules linked in:
<6>[ 13.184905] CPU: 3 PID: 1206 Comm: exe Tainted: G W 3.18.140-lineage #394
<6>[ 13.184911] Hardware name: HTC Corporation. MSM8996v3 PME_JAPAN PVT (DT)
<6>[ 13.184917] task: ffffffc06681b000 ti: ffffffc0669dc000 task.ti: ffffffc0669dc000
<6>[ 13.184930] PC is at __schedule_bug+0x40/0x44
<6>[ 13.184937] LR is at __schedule_bug+0x3c/0x44
on second file [ aka -1]
<3>[24353.054198] BUG: scheduling while atomic: ogle.android.gm/15670/0x00000002
<4>[24353.054214] Modules linked in:
<4>[24353.054226] ------------[ cut here ]------------
<2>[24353.054233] Kernel BUG at ffffffc0000d0650 [verbose debug info unavailable]
<0>[24353.054240] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
<4>[24353.054246] Modules linked in:
<4>[24353.054258] CPU: 1 PID: 15670 Comm: ogle.android.gm Tainted: G W 3.18.140-lineage #394
<4>[24353.054264] Hardware name: HTC Corporation. MSM8996v3 PME_JAPAN PVT (DT)
<4>[24353.054271] task: ffffffc064360000 ti: ffffffc072f38000 task.ti: ffffffc072f38000
<4>[24353.054285] PC is at __schedule_bug+0x40/0x44
<4>[24353.054292] LR is at __schedule_bug+0x3c/0x44
<4>[24353.054298] pc : [<ffffffc0000d0650>] lr : [<ffffffc0000d064c>] pstate: 60000145

besides LOS i have installed NikGapps [0815] core, gmail, maps, YT, Google, Netflix. Magisk 23.0 (with hide enabled) for passing CTS. No other modules installed as no need.
what configuration do you have / use ?
My configuration is as follows:

Firmware 3.22.970.9 Japan (I recently flashed this. My original was WW though)
LineageOS 18.1 Build 20210912 (latest)
NikGApps Basic 20210815 (latest)
NikGApps Addons (GBoard Gmail Calculator Calender Maps Photos Wallpapers PlayGames)
Magisk v23.0 (latest, the one that requires flashing patched boot.img)
Advanced Charging Controller (ACC) module with app
I replace stock fonts (all Roboto ones in /system/fonts/) with Lato
I also replace bootanimation with Google Pixel's

P.S. The panic reboot/bootloop usually happens more frequently when I flash new build and set up apps and other stuff. But once the phone is all set up with apps and everything, it usually doesn't happen that much. Like I told you in the first 12 hours, when I was still installing apps and setting them, it paniced like 4 or 5 times, and often ending up in reboot loop. But now in the last 12 hours, everything seems to be OK. I am playing Asphalt 9 like usual frequently and it's all good.
Maybe I should try different firmware. The WW one that was originally there in the beginning.
 

raul16

Senior Member
My configuration is as follows:

Firmware 3.22.970.9 Japan (I recently flashed this. My original was WW though)
LineageOS 18.1 Build 20210912 (latest)
NikGApps Basic 20210815 (latest)
NikGApps Addons (GBoard Gmail Calculator Calender Maps Photos Wallpapers PlayGames)
Magisk v23.0 (latest, the one that requires flashing patched boot.img)
Advanced Charging Controller (ACC) module with app
I replace stock fonts (all Roboto ones in /system/fonts/) with Lato
I also replace bootanimation with Google Pixel's

P.S. The panic reboot/bootloop usually happens more frequently when I flash new build and set up apps and other stuff. But once the phone is all set up with apps and everything, it usually doesn't happen that much. Like I told you in the first 12 hours, when I was still installing apps and setting them, it paniced like 4 or 5 times, and often ending up in reboot loop. But now in the last 12 hours, everything seems to be OK. I am playing Asphalt 9 like usual frequently and it's all good.
Maybe I should try different firmware. The WW one that was originally there in the beginning.
if panic / reboot happens only when you do new apps install / setup I would recommend to keep on using it (as seems stable now !) and monitor if will panic/reboot again while you use it for next few days.

PS:
our kernel for msm8996 ( 3.18.140 ) still misses some upsteam commits that other siblings (like OP3/3T or Leeco X2) have for various code bug fixes (including I/O schedulers).
once we could identify more accurate which kernel module throw these errors the fix could be found / applied ;)
 
  • Like
Reactions: shadabkiani
@raul16 Yeah, the same used to happen with previous builds too, but it becomes stable in a day or so. I have also decided to stick with 720p resoultion as the performance plus battery life show significant improvement. I also monitor RAM usuage, and it is improved with 720p.

What about your battery indication? Does your battery percentage show correctly? Or is it another bug that only I'm facing? (I use ACC module to fix it)
 

raul16

Senior Member
@raul16 Yeah, the same used to happen with previous builds too, but it becomes stable in a day or so. I have also decided to stick with 720p resoultion as the performance plus battery life show significant improvement. I also monitor RAM usuage, and it is improved with 720p.

What about your battery indication? Does your battery percentage show correctly? Or is it another bug that only I'm facing? (I use ACC module to fix it)
battery UI displayed % is still an open issue only on charging as the values displayed seems to get stuck to a lower value after some time and does not show / read the real SOC value (!)
after charge (full or else) the UI % is aligned with the SOC value (max deviation of 2%).
 
battery UI displayed % is still an open issue only on charging as the values displayed seems to get stuck to a lower value after some time and does not show / read the real SOC value (!)
after charge (full or else) the UI % is aligned with the SOC value (max deviation of 2%).
You mean when you unplug the charger, it shows correctly then?

This doesn't happen with me. It gets stuck there. When I unpug the charger,it still stays there. I keep using phone. Once the actual % gets down to the displayed stuck value, then it shows correctly, and drops down accordingly from there upon use.
To fix that, I use ACC with setting such as it charges for 50 seconds then pauses for 10 seconds. That way charging is refreshed every minute and percent goes up correctly.
 

raul16

Senior Member
You mean when you unplug the charger, it shows correctly then?

This doesn't happen with me. It gets stuck there. When I unpug the charger,it still stays there. I keep using phone. Once the actual % gets down to the displayed stuck value, then it shows correctly, and drops down accordingly from there upon use.
To fix that, I use ACC with setting such as it charges for 50 seconds then pauses for 10 seconds. That way charging is refreshed every minute and percent goes up correctly.
same here.
i did not install ACC as I just unplug and replug my charger when i notice the stalled value and then the % value jump to the actual correct one ;) so in the end it ends up showing 100% ...
I is more elegant with ACC but i didn't install it so that i will find some time to proper look into it and fix it !
 

KEB64

Senior Member
Jan 25, 2012
755
82
Phoenix, AZ
Thanks for the reply. Is it just uninstalling the apk? Assuming it is, do I need to flash the zip again after re-installing the apk? Or is there something else I need to do to get rid of the zip install?
 

raul16

Senior Member
Thanks for the reply. Is it just uninstalling the apk? Assuming it is, do I need to flash the zip again after re-installing the apk? Or is there something else I need to do to get rid of the zip install?
No. you do not need to uninstall the apk.
in recovery mode, before flashing the new version, uninstall only the magisk.zip (rename the magisk*.zip to uninstall.zip and install it), before that you should uninstall all modules you have installed.
after you install rom and boot OK you can just reinstall magisk.zip via TWRP. the apk will survive and see magisk OK so you can reinstall your modules again (if needed)
 
  • Like
Reactions: KEB64

KEB64

Senior Member
Jan 25, 2012
755
82
Phoenix, AZ
No. you do not need to uninstall the apk.
in recovery mode, before flashing the new version, uninstall only the magisk.zip (rename the magisk*.zip to uninstall.zip and install it), before that you should uninstall all modules you have installed.
after you install rom and boot OK you can just reinstall magisk.zip via TWRP. the apk will survive and see magisk OK so you can reinstall your modules again (if needed)
Much appreciated! Thans for the detail.
 
  • Like
Reactions: raul16

bermano

New member
Sep 29, 2021
3
0
just wondering, anyone try nfc feature with this ROM?. I currently using htc10 with LOS 16. my only problem is nfc feature doesnt read a tag, but its work perfectly to transfer a file into another nfc phone via nfc beam. thingking to try different upgrade. is it rom / kernel related? :D
Thank you
 

KEB64

Senior Member
Jan 25, 2012
755
82
Phoenix, AZ
just wondering, anyone try nfc feature with this ROM?. I currently using htc10 with LOS 16. my only problem is nfc feature doesnt read a tag, but its work perfectly to transfer a file into another nfc phone via nfc beam. thingking to try different upgrade. is it rom / kernel related? :D
Thank you
I don't have any tags myself, but I do have Google Pay set up. NFC activated. Haven't tried it yet but when I do I can report back. I would think if that works then tags would work. Beaming files is different (I think). Can't hurt to make a backup of your system and give it a shot.
 
May 20, 2017
9
0
After about 6 hours, I have managed to update my HTC 10 from Oreo 8.0.0 - thank you for the great work. In return, the least I can offer is a summary of my challenges.
1. The instructions on posting #1 were very specific but for someone new to Android (but with decades of experience with computing), there was not enough detail so I relied on other sources. I followed posting #1 as closely as I could.
2. Some of the files needed were missing and I had to find alternate sources. The hardest file to find was probably the "HTC Driver" that worked with Windows 10. I found it here https://www.windowsdrivers.org/htc-fastboot-usb-driver-download
3. I could talk with the phone but I couldn't get into "fastboot" mode because it no longer exists. It's now called "download"
4. I could not unlock the phone because I did not have the "HTC Driver" - basically, retrieving the oem information would not work unless "HTC Driver" was installed ... however, you could put the phone into fastboot mode
5. I finally managed to install the TWRP recovery software but when I tried to reboot, the phone locked up. That's when I discovered I needed to hold down "Volume Down" and "Power". After about 10 seconds the buttons flashed and after another 5 seconds, the phone rebooted.
6. I couldn't work out how to get into recovery mode (I rebooted, selected the boot menu, boot recovery)
7. I went into wipe, wipe file data, wiped the other internal partitions.
8. I rebooted so I could copy the files to my external storage card via the phone.
9. When I went back into Restore mode, I installed LineageOS 18.1 (September Edition) and Google Apps. After I rebooted, a warning message appeared (which i didn't expect). The screen went blank and 20 minutes later, nothing happened. I tried to recover (Volume Down and Power) but this didn't work. I then realised that I had to hold the buttons down for about 20 seconds (rather than 15 seconds) and there are no flashing buttons.
10. I re-wiped everything and only installed LineageOS and rebooted and it worked fine.
11. I went back into recovery mode and installed Google Apps and rebooted and it worked fine.

As a side note, the process for unlocking the phone was a pain, but in small ways. If you didn't select using the ALT key, you'd end up with "(bootloader)" in the middle of your device information and the unlock process would not work.

But .. in spite of all of that, it worked. For a person who has almost never used Android, 6 hours is probably a reasonable expectation.

I hope the information helps someone else. Basically, follow the steps in post #1 carefully ... but if you don't understand, look at other instructions, specifically for the HTC 10.

GKW
PS Running the OS for the first time takes about 4 minutes. Running the OS with Google Apps installed takes much longer ... but you will see an animation (lines and a circle) on the screen if everything is working fine.
 

KEB64

Senior Member
Jan 25, 2012
755
82
Phoenix, AZ
After about 6 hours, I have managed to update my HTC 10 from Oreo 8.0.0 - thank you for the great work. In return, the least I can offer is a summary of my challenges.
1. The instructions on posting #1 were very specific but for someone new to Android (but with decades of experience with computing), there was not enough detail so I relied on other sources. I followed posting #1 as closely as I could.
2. Some of the files needed were missing and I had to find alternate sources. The hardest file to find was probably the "HTC Driver" that worked with Windows 10. I found it here https://www.windowsdrivers.org/htc-fastboot-usb-driver-download
3. I could talk with the phone but I couldn't get into "fastboot" mode because it no longer exists. It's now called "download"
4. I could not unlock the phone because I did not have the "HTC Driver" - basically, retrieving the oem information would not work unless "HTC Driver" was installed ... however, you could put the phone into fastboot mode
5. I finally managed to install the TWRP recovery software but when I tried to reboot, the phone locked up. That's when I discovered I needed to hold down "Volume Down" and "Power". After about 10 seconds the buttons flashed and after another 5 seconds, the phone rebooted.
6. I couldn't work out how to get into recovery mode (I rebooted, selected the boot menu, boot recovery)
7. I went into wipe, wipe file data, wiped the other internal partitions.
8. I rebooted so I could copy the files to my external storage card via the phone.
9. When I went back into Restore mode, I installed LineageOS 18.1 (September Edition) and Google Apps. After I rebooted, a warning message appeared (which i didn't expect). The screen went blank and 20 minutes later, nothing happened. I tried to recover (Volume Down and Power) but this didn't work. I then realised that I had to hold the buttons down for about 20 seconds (rather than 15 seconds) and there are no flashing buttons.
10. I re-wiped everything and only installed LineageOS and rebooted and it worked fine.
11. I went back into recovery mode and installed Google Apps and rebooted and it worked fine.

As a side note, the process for unlocking the phone was a pain, but in small ways. If you didn't select using the ALT key, you'd end up with "(bootloader)" in the middle of your device information and the unlock process would not work.

But .. in spite of all of that, it worked. For a person who has almost never used Android, 6 hours is probably a reasonable expectation.

I hope the information helps someone else. Basically, follow the steps in post #1 carefully ... but if you don't understand, look at other instructions, specifically for the HTC 10.

GKW
PS Running the OS for the first time takes about 4 minutes. Running the OS with Google Apps installed takes much longer ... but you will see an animation (lines and a circle) on the screen if everything is working fine.
Welcome to the world of custom ROMs. Next time should take you 30 min. to do the install.
 

raul16

Senior Member
Only android 8.0?
My HTC 10 is 7.0 now : (
you must upgrade it to Oreo [android 8] first. check for updates maybe you can still find the HTC servers up and able to upgrade officially !
if not, check the HTC 10 thread(s) where you should find required htc Oreo RUU for your specific CID & MID.
don't forget to do first a full backup of your system + data.
 
  • Like
Reactions: Qaqee87

Top Liked Posts

  • 1
    @raul16 Update: I just reflahed the ROM with NikGApps Core version. No apps installed yet. Now I have rebooted the phone a number of times and that reboot-loop issue hasn't happened yet. So now I know it was wrong with some app beffore that used to cause the issue, not the ROM. I will update you after some more tests.
    1
    Thank you for the update. Running very well here.
  • 5
    new build available lineage-18.1-20211014-UNOFFICIAL-pme.zip

    log:
    October 2021 Security patch
    los: upgrade A11 from r43 to r46 build RQ3A.211001.001
    pme: code upstream, backport + optimizations
    pme: kernel charging, scheduling while atomic bug
    3
    Thanks for the welcome.
    If I were to do this process again, 30 minutes sounds about right.

    I have a few questions I hope someone can help me with.

    #SDCard Corruption
    1. For some reason, my 64gb memory card corrupted. I reformatted it and it seems ok.
    Q1: Is corruptions of SDCards normal?

    #Upgrading to a newer LineageOS - easiest method?
    2. If I upgrade LineageOS, I assume I download the new ROM, erase the partition and re-install LineageOS. Is that right? LineageOS also asks for the backup (to restore) when it's first installed. Is that a SeedVault backup?
    Q2: What's the best way to restore my data if I upgrade LineageOS?

    #"Free Up Space" when I have 32gb (Internal) and 60gb (External)
    I managed to install Brave Browser using Play Store. There was an update and when I tried to update, LineageOS said "Free Up Space" (despite having many gigabytes of free space) I uninstalled Brave and tried to re-install Brave. Play Store still said "Free Up Space". Brave was installed in Internal Memory.
    Q3: Does anyone have any suggestions on what's happening here?

    #What is Magisk?
    I read the description of magisk. It talks about rooting the phone. Can someone explain in simpler terms what this tool actually does (ie. If it's not installed, I can't do XXX ... or If it is installed, you can now do XXX). I vendor unlocked my phone. I could install TWRP and LineageOS ... so in theory, I should have full control of the phone... right?
    Q: Do I need Magisk?

    Thank you for any help anyone can give me. Q3 is probably my biggest problem right now (ie. I can't install any additional apps). I am very comfortable wiping everything and starting again ... but if that's the suggestion, then the answer to Q2 would be appreciated.

    GKW
    1. when initially install LOS 18.1 from any other ROM (stock or custom) it is required to format /data in TWRP. if your SDCard was setup as external you should format that too to avoid issues (like encryption);
    2. within same version (aka LOS 18.1) dirty flash of the update will do just fine. GApps should survive (backup and restore via addon.d scripts). Magisk modules must be removed (via .app) and Magisk unistall (in TWRP only) before flash to avoid bootloops; after flash of the update need to wipe cache & dalvik then reboot to system.
    3. check what freespace you have on your internal memory as seems to be full (no space); move (what you can - like pictures. music, movies, games) from internal to external (removable) memory or as an option integrate your external memory into internal memory ...
    4. Magisk is a very useful app if you need to install modules that add to system functionality (not available as is in LOS 18.1 /system) usually called mods;
    or you need to pass Google CTS for using banking / netflix apps. LOS18.1 does not alter build fingerprint nor hide open bootloader which fail to pass basic CTS (!); magisk hide solve that ;)
    or you need to have root access for some special apps that require it to enable extra functionalities (that are useful to you);
    1
    Thanks for the reply. Is it just uninstalling the apk? Assuming it is, do I need to flash the zip again after re-installing the apk? Or is there something else I need to do to get rid of the zip install?
    No. you do not need to uninstall the apk.
    in recovery mode, before flashing the new version, uninstall only the magisk.zip (rename the magisk*.zip to uninstall.zip and install it), before that you should uninstall all modules you have installed.
    after you install rom and boot OK you can just reinstall magisk.zip via TWRP. the apk will survive and see magisk OK so you can reinstall your modules again (if needed)
    1
    No. you do not need to uninstall the apk.
    in recovery mode, before flashing the new version, uninstall only the magisk.zip (rename the magisk*.zip to uninstall.zip and install it), before that you should uninstall all modules you have installed.
    after you install rom and boot OK you can just reinstall magisk.zip via TWRP. the apk will survive and see magisk OK so you can reinstall your modules again (if needed)
    Much appreciated! Thans for the detail.
    1
    Only android 8.0?
    My HTC 10 is 7.0 now : (
    you must upgrade it to Oreo [android 8] first. check for updates maybe you can still find the HTC servers up and able to upgrade officially !
    if not, check the HTC 10 thread(s) where you should find required htc Oreo RUU for your specific CID & MID.
    don't forget to do first a full backup of your system + data.
  • 21
    header_htc_10_xda.png


    LineageOS 18.1 is a free, community built, aftermarket firmware distribution of Android 11 (R), which is designed to increase performance and reliability over stock Android for your device.

    Disclaimer:
    Code:
    #include <std_disclaimer.h>
    /*
    * Your warranty is now void.
    *
    * We are not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at us for messing up your device, we will laugh at you.
    *
    */

    LineageOS is based on AOSP with contributions from many people within the Android community. It can be used without any need to have any Google application installed. If needed you can install any GApps package available for R.
    LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
    The source code for LineageOS is available at Github repo. And if you would like to contribute to Lineage OS, please visit Gerrit Code Review. LineageOS changelog is whatever was merged into Gerrit.

    Instructions:
    1. make a FULL backup first from your actual system.
    2. before installing make sure you are running the latest stock Oreo from the latest HTC Sense.
    3. install as recovery the latest TWRP recovery 3.5.0_9-0 ( thanks @Captain_Throwback )
    4. if you are encrypted, - coming from stock Oreo - take a full backup of all your data, boot into TWRP and format data (the option which requires you to type "yes") and clean flash accordingly.
      This is due to encryption changes. Do not skip this step or you will be locked out of your system by a password prompt.
    5. after format /data you must reboot to recovery to be able to copy needed files to flash on /sdcard
    6. download the latest ROM zip and GApps (optional - if needed) from the downloads section below
    7. wipe system, cache, and data if coming from another AOSP based rom
    8. flash ROM zip in TWRP, add install more zip's and flash also GApps (optional), thus you get best integration of vanilla LOS with GApps;
    9. reboot to system and make initial settings & configurations; also check and configure your apps permissions;
      Note: don't enable option Lineage recovery during setup as you will lose TWRP (overwrite by LOS Recovery app) and you need to reinstall it again!
    10. optional: flash the latest Magisk and reboot to system to setup Magisk app [wait for it to load]
    Enjoy ;) latest LOS 18.1 [Android 11] on your HTC 10.

    Downloads:
    Known Issues:
    1. IMS - VOLTE
    2. SlowMo
    3. SeLinux permissive

    Reporting bugs:
    Bug reports without a proper description of the issue and a logcat will be ignored!

    Credits:
    • LineageOS Team & Contributors
    • Code Aurora Forum
    • TWRP Team
    • Magisk Team
    • Fagyi & all HTC 10 contributors

    Special thanks:
    @fagyi

    Source code:

    LineageOS Gerrit Review
    LineageOS source
    Kernel source
    Device source
    Vendor source

    XDA: DevDB Information
    [ROM] [11.0] [PME] LineageOS 18.1 [UNOFFICIAL], ROM for the HTC 10

    Contributors:

    raul16

    Donations
    donations are not mandatory but very welcomed
    If you like my work and want to support development or buy me a coffee PayPal Donate

    ROM OS Version: Android 11_r43
    ROM Kernel: Linux 3.18
    ROM Firmware Required: OREO
    Based On: LineageOS 18.1

    Version Information
    Status:
    Stable

    Created on 2020-12-12
    Last Updated 2021-10-14

    Screeshots:
    Screenshot_20210117-120922_Trebuchet.pngScreenshot_20210117-121007_Trebuchet.pngScreenshot_20210117-121550_Magisk_Manager.pngScreenshot_20210117-122433_SafetyNet_Test.pngScreenshot_20210117-122533_Settings.pngScreenshot_20210117-123005_Trebuchet.png
    9
    ----------------------------------------------------
    2021-10-14
    ----------------------------------------------------
    October 2021 Security patch
    los: upgrade A11 from r43 to r46 build RQ3A.211001.001
    los: changelog here
    pme: code upstream, backport + optimizations
    pme: kernel charging, scheduling while atomic bug

    ----------------------------------------------------
    2021-09-12
    ----------------------------------------------------
    September 2021 Security patch
    los: upgrade A11 from r40 to r43 build RQ3A.210905.001
    los: changelog here
    pme: device sensors, init code fixes & optimizations
    pme: kernel BFQ I/O scheduler & other code fixes

    ----------------------------------------------------
    2021-08-14
    ----------------------------------------------------
    August 2021 Security patch
    los: upgrade A11 from r39 to r40 build RQ3A.210805.001.A1
    pme: device & kernel code fixes & optimizations
    pme: update blobs for media/display/graphics

    ----------------------------------------------------
    2021-07-12
    ----------------------------------------------------
    July 2021 Security patch
    los: upgrade A11 from r38 to r39 build RQ3A.210705.001
    pme: device & kernel code fixes & optimizations

    ----------------------------------------------------
    2021-06-22
    ----------------------------------------------------
    Fix - encryption support enabled for /data partition
    Fix - speaker sound
    New - included LOS 18.1 changes from 16.06 to 22.06.2021 (inclusive)

    ----------------------------------------------------
    2021-06-16
    ----------------------------------------------------
    June 2021 Security patch
    los: upgrade A11 from r37 to r38 build RQ3A.210605.005
    pme: compile kernel with gcc
    pme: various device code fixes

    ----------------------------------------------------
    2021-05-16
    ----------------------------------------------------
    May 2021 Security patch
    los: upgrade from A11_r34 to A11_r37 RQ2A.210505.003
    pme: compile kernel with gcc

    ----------------------------------------------------
    2021-04-30
    ----------------------------------------------------
    April 2021 Security patch
    los: upgrade from A11_r32 to A11_r34 RQ2A.210405.005
    pme: compile kernel with gcc [gcc version 4.9.x (prerelease)]
    pme: kernel optimizations
    pme: various code fixes from CAF & mentainers

    ----------------------------------------------------
    2021-04-05
    ----------------------------------------------------
    March 2021 Security patch
    los: upgrade from A11_r29 to A11_r32 RQ2A.210305.006
    pme: compile kernel with clang-11
    pme: treewide fix use of uninitialized variable
    pme: various code fixes from CAF & mentainers
    pme: BACKPORT radio driver from Google wahoo
    pme: UPSTREAM kernel 3.18 changes from LineageOS & CAF
    pme: BACKPORT kernel 3.18 changes from LineageOS & CAF

    ----------------------------------------------------
    2021-02-09
    ----------------------------------------------------
    February 2021 Security patch
    los: upgrade from A11_r27 to A11_r29 RQ1A.210204.004
    pme: merge CAF tag LA.UM.8.6.r1-05300-89xx.0
    pme: updated info security patches applied
    pme: UPSTREAM kernel 3.18 changes from LineageOS & CAF
    pme: BACKPORT kernel 3.18 changes from LineageOS & CAF

    ----------------------------------------------------
    2021-01-15
    ----------------------------------------------------
    January 2021 Security patch
    pme: touch: Improve logging output
    pme: touch: Fix code style issues
    pme: Use CodeAurora ImsService implementation for RCS
    pme: Add AOSP RCS packages
    pme: Remove dead RCS packages
    pme: manifest: Remove Trust interface entry
    pme: Deduplicate handheld_core_hardware.xml copy rule
    pme: Inherit from AOSP product makefiles in the common tree
    pme: Remove [email protected]
    pme: Migrate to Health 2.1 HAL
    pme: Replace [email protected] with audio.service
    pme: Enforce vintf manifest override
    pme: Move supplicant service init to wpa_supplicant

    ----------------------------------------------------
    2020-12-12
    ----------------------------------------------------
    December 2020 Security patch
    Initial beta release LOS 18.1 for HTC U10
    6
    new build available lineage-18.1-20210622-UNOFFICIAL-pme.zip

    log:
    Fix - encryption support enabled for /data partition
    Fix - speaker sound
    New - included LOS 18.1 changes from 16.06 to 22.06.2021 (inclusive)
    5
    new build available lineage-18.1-20211014-UNOFFICIAL-pme.zip

    log:
    October 2021 Security patch
    los: upgrade A11 from r43 to r46 build RQ3A.211001.001
    pme: code upstream, backport + optimizations
    pme: kernel charging, scheduling while atomic bug
    5
    new build available lineage-18.1-20210912-UNOFFICIAL-pme.zip

    log:
    September 2021 Security patch
    los: upgrade A11 from r40 to r43 build RQ3A.210905.001
    pme: device sensors, init code fixes & optimizations
    pme: kernel BFQ I/O scheduler & other code fixes