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

[raul16]

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:

Spoiler: dmesg-ramoops

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 ?

 

[shadabkiani]

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:

Spoiler: dmesg-ramoops

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]

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

 

[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]

@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%).

 

[shadabkiani]

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]

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]

Do we still need to uninstall magisk when flashing the latest version since the january build? I'm on that now. (01-15)

 

[raul16]

Do we still need to uninstall magisk when flashing the latest version since the january build? I'm on that now. (01-15)

yes

 

[KEB64]

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]

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)

 

[KEB64]

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.

 

[KEB64]

Works like a charm! Battery life seems improved as well. Thanks again!

 

[bermano]

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?
Thank you

 

[KEB64]

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?
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.

 

[KEB64]

...assuming Pie is based on the same partition scheme. I can't remember. I came from LOS 17 just fine with a clean install.

 

[GoodKingWenceslas]

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]

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.

 

[Qaqee87]

Only android 8.0?
My HTC 10 is 7.0 now : (

 

[raul16]

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.