yashsingh1/xdaforums huggingface dataset:
[One (M9) Original Android Development] The_Walking_Playground:
Hi,

The device changelog in the Hima TWRP thread indeed shows fixes for "AOSP Oreo" encryption, as does the change log at the bottom of the M9 device page on the TWRP site.

TWP
[One (M9) Original Android Development] An3skmbi:
I don't think it is specific to encryption. I also have no deep sleep, but have not enabled encryption. I'm monitoring the wakelocks and cannot yet point to a culprit, although qpnp_fg_memaccess is always on top.
[One (M9) Original Android Development] jongreeny:
"Hi,

The device changelog in the Hima TWRP thread indeed shows fixes for "AOSP Oreo" encryption, as does the change log at the bottom of the M9 device page on the TWRP site.

TWP"

Apologies you are of course correct I completely missed it. Thanks for the help[emoji41]
[One (M9) Original Android Development] supachris:
Oh, you have same device as me, but newer firmware. Does anyone know how to update?
[One (M9) Original Android Development] bubba1601:
Go-to to the firmware section for the M9 here on XDA and follow the tutorial.
[One (M9) Original Android Development] supachris:
Indeed, I encrypted the phone again and now it seems to be correct in deep sleep while not in use.

Strange...
[One (M9) Original Android Development] boredherobrine13:
So...too early to ask for Android P?
[One (M9) Original Android Development] supachris:
I have to correct myself :(

Today morning the battery level was down to 78% again. And again the ...gcrypt... hours of kernel wakelock, and no deep sleep. Only after reboot some minutes in deep sleep, but overall, there seems to be still a bug in ecryption.

I reverted to unencrypted, and now the phone enters deep sleep again. Very strange
[One (M9) Original Android Development] An3skmbi:
I can confirm the issue, see screenshots. Although I also had no deep sleep unencrypted, but can now see the crypt wakelocks.

EDIT: After a reboot and about an hour of non-usage, deep sleep is at 67% and the crypto wakelocks around 14%. Battery usage at around 3% p/hour.
[One (M9) Original Android Development] Anoses:
could you give me a link to the tutorial :confused:
[One (M9) Original Android Development] bubba1601:
Really?

You are in an HTC One M9 forum so all you had to do was look at the different M9 sections and find "firmware"

S - on and S - off will affect what you can and can't do so READ the read me section first.

https://xdaforums.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698

https://xdaforums.com/one-m9/development/firmware-t3068243

---------- Post added at 05:41 AM ---------- Previous post was at 05:31 AM ----------

Direct link to firmware and tutorial here

https://xdaforums.com/one-m9/development/firmware-t3068243
[One (M9) Original Android Development] supachris:
I did further investigation and tryouts. After removing the encryption, the deep sleep was fully working. But after one day, deep sleep again was not entered and the phone consumed over 20 percent battery over night.

So I checked the possible background battery eaters. I disabled the Google location service, switched to device only. Also I changed the wifi sleep policy to 1, meaning wifi enabled only when connected to charger. And I disabled the wifi wakeup available/enabled. All can be made by put settings global by adb.

So, since the reboot after doing this, the phone enters deep sleep and the mem_access wakelock is shifted to the 5th position or so. Phone consumed only 5 percent over night with 92% deep sleep time.

I will watch this further...
[One (M9) Original Android Development] supachris:
I did more tests, but obviously the hardware encryption breaks the deep sleep mode, so the battery drain is huge.

Another question: Is the FM radio supported by LOS?
[One (M9) Original Android Development] roadkill42:
Can any body here figure out how to get this rom to work on HTC bolt I will test I don't have PC running yet to try my self
[One (M9) Original Android Development] jam0688:
I noticed AICP was mentioned is that being developed for just the himaul or is it for all hima variants and is there any tests builds available. I currently have the himawl variant and I prefer AICP so i was curious about this after seeing it [MENTION=8276284]Claymore1297[/MENTION]]

---------- Post added at 09:13 PM ---------- Previous post was at 09:06 PM ----------

Nevermind I found them!! Lol. Sorry about that!
[One (M9) Original Android Development] bahha:
Can anyone confirm if the IR-blaster works. It tried to use it with my camera as a remote shutter but it didn't work. it worked before trying this rom.
[One (M9) Original Android Development] The_Walking_Playground:
Hi,

Yes, I can confirm it works. Depending on the program you're using, you may have to change a setting. See this post: https://xdaforums.com/one-m9/orig-development/rom-lineageos-15-0-gsm-himaul-t3700218/post76863700

TWP
[One (M9) Original Android Development] bahha:
thanks I tried it and it worked. the peel remote which is a Cancer doesn't.
[One (M9) Original Android Development] phpbb3:
Lol. Yes, of course it is.
[One (M9) Original Android Development] ragerdl:
Please please please don't take this the wrong way. Like many of us, I am kind of paranoid when it comes to security. I already sent claymore a small token of monetary appreciation to thank him for his contributions, and I'm a contributor to other open source projects (fwiw). Fundamentally, is there any way we can _know_ that this image isn't planting a backdoor in our phones? It appears that the official LOS builds offer some guarantees, but we're missing that badge and delivery system at the moment. I'd like to install it... just trying to figure out what level of paranoia I should have when it comes to inputting personal data into my phone after it's installed. Thank you so much for your hard work! You don't deserve to be questioned like this! It's just that the world we live in justifies it :/.
[One (M9) Original Android Development] shaqman89:
Well, why don't you check out the source then?

If you are still unsure whether that matches with the build image, you could always compile it yourself.

Btw, we don't have an official badge for this yet, since there is still issues to be included as official LOS (HW encryption if I am not mistaken), but AICP is official and uses the same code. Can't say that is a guarantee, but it isn't also just some random built image.
[One (M9) Original Android Development] supachris:
Even if you do so, you cannot be sure if there is any backdoor in the modem/baseband firmware. It's like on your PC. There you also can have backdoors in Intel ME or in the UEFI Firmware, even if you compiled and installed your Linux...
[One (M9) Original Android Development] Claymore1297:
first of all thanks for the donation, much appreciated!

As you can see in OP, I'm doing only 3 additional picks, for the builds - so you could also build by yourself, to verify.

So the code is the same, as would be used in a official build.

What garantee you you mean in official builds? the only difference is, that my builds are not signed and not build by LOS-jenkins.

The builds in AFH has got a checksum, so you can verify, that you are not victim of a man in the middle-attack, or something.

About security, I think this is the most secure build for this phone (same as AICP), I'm using the highed kernel-patchlevel (108 (EOL) instead of 84) and the newest ASB-patchlevel.

As it has mentioned before, you can check the sources to verify.

In the following files you can see, which repos this build is using:

https://github.com/LineageOS/android/blob/lineage-15.1/default.xml

https://github.com/LineageOS/android/blob/lineage-15.1/snippets/lineage.xml
[One (M9) Original Android Development] shaqman89:
True. But the question was about the image itself, not about whether he has a backdoor or not.

As for the image, checking the source and doing the compilation yourself from the verified source should be enough if you have the skill to do so.
[One (M9) Original Android Development] Audiotive:
Great job with all the work put into this ROM, I'm loving it, responds super quick. I'm having an issue with the audio though. I've searched the entire thread and still can't find a solution. Everyone seems to have the sound working. I opened up the AudioFX app and it only opens up to a blank, nothing at all then force closes if I try to play some music or play a YouTube video. I downloaded the AudioFX app from the Play Store and it opens up and I can see the equalizer and everything but it doesn't help as far as making the sound work. What am I missing? Is the firmware too old?

Here's my phone info:

hTC download mode

*** UNLOCKED ***

htc_himaul PVT S-ON

LK-1.0.0.0000

RADIO-01.01_U11440601_86.09.50731G_F

OpenDSP-v29.2.6-00492-M8994_0702

OS-2.11.531.19

Sep 8 2015, 14:57:31(591203)
[One (M9) Original Android Development] roadkill42:
Did u do clean in stall also could go into settings then apps clear the cache then reboot
[One (M9) Original Android Development] Audiotive:
Yeah, I cleared the cache and data before installing.
[One (M9) Original Android Development] Claymore1297:
well your firmware is really old, so a update can't be wrong. Can't reproduce the issue here ...
[One (M9) Original Android Development] kunalxda:
Is lazerlord dts eagle commits for wcd9330 has been added in the kernel ?
[One (M9) Original Android Development] comolik:
Again thanks a lot for your efforts, [MENTION=8276284]Claymore1297[/MENTION]. It's great to have a usable and up-to-date LineageOS ROM for the HTC One M9 again, even with working disk encryption!

In my opinion the main arguments for pushing your changes as an official LineageOS port:

people get automated updates

weekly builds don't have to be done by you, so even if you are on vacation or become MIA, people continue to get updates (until something M9 specific breaks)

the port is way more accessible to novice users who don't know about xda-developers and merely browse the LineageOS wiki

Since hardware encryption seems to work now, what's left in your opinion before trying to make this port official again?
[One (M9) Original Android Development] Claymore1297:
your arguments are right - whats left is the camcorder bug, which isn't mergeable in that current state.

A complete statement you can find here:

https://xdaforums.com/showpost.php?p=77099786&postcount=712

btw.: I'm currently working on some kernel-updates/improvements, so stay tuned. As soon the august ASB's are getting merged a new build will come up.
[One (M9) Original Android Development] comolik:
Thanks for the update! Looking forward to see whether you find a solution for the camcorder bug :)
[One (M9) Original Android Development] Evengard:
Have anyone managed to get NFC working? Trying to scan some Mifare Classic cards - no success, Android Pay seems to set up successfully, but also actually does nothing... I had NFC working on stock though...
[One (M9) Original Android Development] freed_de:
Discussion about Official LineageOS-ROM

Hello everybody,

it is also important to me to say THANK YOU for the hard work! A high on Claymore1297!!

I'm a bit confused about the "Official ROM" discussion and find it exciting to learn about the background work... so: an answer is not important, but if someone is bored... ;)

There can not be an official LineageOS-ROM at the moment because there is still the camcorder bug, right? But there is an official AICP-ROM, which is also maintained by Claymore1297. Does it also have the camera bug, but a less severe charter, and therefore may be official? Or is the AICP-ROM bug-free, but the code is not compatible with LineageOS, so it can not be easily transferred?

Greetings,

and thanks again!

freed_de
[One (M9) Original Android Development] Claymore1297:
yes, as long this "camcorder-bug" exists, there can't be a official LOS for hima.

The codebase of AICP is the same, so the "bug" exists there also, but on AICP builds there is a mechanism, to get around this.

And no, this cannot done on official LOS builds.
[One (M9) Original Android Development] bubba1601:
There isn't a 11/11 release!

09/11 is the latest.

All the builds will be the same place as all the others in the same folder, unless we are told otherwise.
[One (M9) Original Android Development] fidoedidoe:
Just clarify the situation (and as [MENTION=7682183]bubba1601[/MENTION] stated) there is no formal 11/11 release. The comments I gave earlier were based upon my own personal build of the ROM compiled from source (using instructions given by the Devs in this thread). I will never share my personal builds as this could be seen as undermining the great work the devs are doing here and if nothing else it will certainly cause more clutter / confusion in the thread. At the time of writing the latest official release is dated 09/11.
[One (M9) Original Android Development] Mirenk:
Audio and media can be fixed by this.

ffmpeg codec haven't been ported in lineage-15.0 now, so we need to do...
[One (M9) Original Android Development] Claymore1297:
Sound and Video is now working for me... Thanks a lot ::)
[One (M9) Original Android Development] Flyhalf205:
Are your newer builds able to boot? I can't get any of mine to boot.
[One (M9) Original Android Development] Claymore1297:
Same here.... It only boot, by replacing boot.IMG with an older one...
[One (M9) Original Android Development] fidoedidoe:
Build from 11/11 booted fine..a build from 13/11 fails to boot. I didn't have time to track down cause and at the time suspected human error in build steps. If I find time today I'll see if a diff of source between the two dates reveals anything.

[MENTION=982913]xangma[/MENTION], you reported boot issues originally. Did you establish cause?
[One (M9) Original Android Development] xangma:
I ended up using the official lineage kernel with the chinomofu kernel config of Mirenk's. That is the only way I got official to boot. Otherwise, the white HTC screen would just bootloop (ie kernel wouldn't even start + no logs).
[One (M9) Original Android Development] fidoedidoe:
[MENTION=3082717]Flyhalf205[/MENTION] / [MENTION=982913]xangma[/MENTION] / [MENTION=8276284]Claymore1297[/MENTION] I'll be the first to admit I'm out of my depth here, so no idea whether this helps or not. I haven't see any source code changes between 11th (last good boot) and now, I've only checked: android_kernel_htc_msm8994 and android_device_htc_hima-common. I did unpack boot.img from a working / non working room and a "diff" reveals the following:

diff -r ../../20171113/ramdisk/default.prop ../../20171111/boot/ramdisk/default.prop
31,33c31,33
< ro.bootimage.build.date=Mon 13 Nov 20:56:44 GMT 2017
< ro.bootimage.build.date.utc=1510606604
< ro.bootimage.build.fingerprint=htc/lineage_himaul/himaul:8.0.0/OPR3.170623.013/373ce58194:userdebug/test-keys
---
> ro.bootimage.build.date=Fri Nov 10 13:50:59 CST 2017
> ro.bootimage.build.date.utc=1510343459
> ro.bootimage.build.fingerprint=htc/lineage_himaul/himaul:8.0.0/OPR6.170623.012/61c75dc2d1:userdebug/test-keys
Binary files ../../20171113/ramdisk/init and ../../20171111/boot/ramdisk/init differ
Binary files ../../20171113/ramdisk/sbin/adbd and ../../20171111/boot/ramdisk/sbin/adbd differ
Binary files ../../20171113/ramdisk/sbin/charger and ../../20171111/boot/ramdisk/sbin/charger differ
Binary files ../../20171113/ramdisk/sbin/ueventd and ../../20171111/boot/ramdisk/sbin/ueventd differ
Binary files ../../20171113/ramdisk/sbin/watchdogd and ../../20171111/boot/ramdisk/sbin/watchdogd differ

The diff between default.prop I'm guessing is nothing to worry about (just text / timedate stamp changes). I can't really speak to the impact of changes to the binary files: init and sbin/adbd, charger, uventd & watchdogd - can anyone else?

Happy to help/assist further but will need a little prompting / guidance.
[One (M9) Original Android Development] Flyhalf205:
Here, I have written a how-to list for you to follow. https://wiki.lineageos.org/devices/himaul/build
[One (M9) Original Android Development] Claymore1297:
my build of today boots some seconds and then returned to the bootloader.

I followed the instructions of the "build-doc" (without the 190165), and i picked the new gerrit-change "196446" (Revert "hima: Disable sdcardfs until the kernel impl is done").

Got the following logcat:
[One (M9) Original Android Development] Flyhalf205:
That is where my builds are at too probably since around the 11th. no idea why
[One (M9) Original Android Development] bubba1601:
I didn't realise it was a compulsory requirement to s off a M9 before rooting?

If so, I've done it illegally and rooted my M9 several months ago and its still S on!

I'm not criticising you.......

I also detest people keep asking for updates.

I'm sorry if that distressed you.
[One (M9) Original Android Development] System23:
Hi,

Iam would ask about my problem with Multirom M9 26.11.2017 and lineageos 15!!! in the video i add you see thats nougat primary and oreo secondary rom !!! but oreo wouldn't start , all what happens is so you see in video this screen !!

Know iam have any questions!!

is it the compactibility from Multirom with Oreo?

or

is it the workaround fix compactibility from the oreo kernel

or

is it both of them?

i think more users ,not only me use multirom to test Custom Roms but to uninstall or swap ROMs so that the test ROM been works is needs too many time and too many place on the device!!! my ROM needs 19GB to Swap and 14GB to Backup only for the clean primary Test Lineageos 15 ROM so that it works!!

The second and optional problem is boot/kernel problem with kali-nethunter boot patcher , the rom starts not after install kali package, the source they i used are from your roms boot.img that i unpacked, and i added the zImage to kali bootpatcher from offensive-security!!! the working way 4 oreo is to install builded chroot installer and use them via terminal !!!

greetz Anon23

would everybody take the time to help with this problem?

http://www58.zippyshare.com/v/2kd5EHqU/file.html

Sent by ViperNethunter 6.2.0 M9
[One (M9) Original Android Development] Skorpyun812:
Every HTC I've owned required s off. At the time, no one had cracked himawl. Sunshine was the first to my knowledge. Other variations were unlocked easily but vzw wrote a Locke in the software where you could access bootloader with s off and vica versa.

---------- Post added at 06:44 PM ---------- Previous post was at 06:42 PM ----------

Also, I don't believe it's illegal to root your own property, it just voids the warranty. This could be different in other countries.
[One (M9) Original Android Development] bubba1601:
Sorry, it was a little sarcasm on my part for which I apologized.

I only rooted my M9 less than 6 months ago and it didn't need S off to to root.

All I had to do was unlock bootloader

Flash twrp

Flash magisk

Flash a custom ROM.

Flash gapps

Done.

Been running lineage ever since

Currently I'm running the LOS 15 ROM but its not fully stable at the moment.

And my M9 is still S on
[One (M9) Original Android Development] bubba1601:
Proof right now my M9 is still S on.

I've been accused of telling lies or making things up in these threads as some users claim it's impossible to root an M9 without S off.

As I explained, my M9 is rooted with magisk, and running lineage OS 15 android 8.0 and it's still S on as you can see in my photos below.
[One (M9) Original Android Development] lzgmc:
Is Magisk built in? If so, unroot or use SuperSu for root to fix the signal strength icon.
[One (M9) Original Android Development] bubba1601:
The signal strength doesn't work in LOS 14.1 (7.1.2) either.

Doesn't matter if you are rooted or not, magisk or SU.

Makes no difference I've found.

Magisk is not build into this ROM, and the signal strength is a known bug with this ROM.

In my experience, flashing SU or magisk to root makes no difference to the signal strength.

If that works for you, that's great.
[One (M9) Original Android Development] Skorpyun812:
Yours is the unlocked variant (himaul) So you probably have the FM chip and everything. Verizon variant (himawl) so I have no fm chip at all, they sell more data that way. Verizon also doesn't want you to be able to do anything with your property so they have the firmware altered to make rooting near impossible.

---------- Post added at 03:46 PM ---------- Previous post was at 03:45 PM ----------

P.s. I'm not your dad. You don't have to prove anything to me.
[One (M9) Original Android Development] SoveWar:
stuck in a bootloop

hello everyone,

after my battery ran out, I can't get into my system and recovery. it keeps rebooting .

I tried to use adb but with no luck.

anyone any idea to help me?

Kind regards,

SoveWar
[One (M9) Original Android Development] supachris:
Try offline charging to 20 percent or so, disconnect charger und try to boot. With connected charger, there is no way out of offline charging mode.
[One (M9) Original Android Development] supachris:
It seems like the AGPS is not working (correctly).

After one or more days not using GPS, the fix takes very very long...some minutes.

Does anyone other have this issue too?
[One (M9) Original Android Development] SoveWar:
I got my phone working again, thank you for the help
[One (M9) Original Android Development] HsHTCsen:
Hi, I have flashed this Rom before and had it up and running great. However, I went back to my previous setup for various reasons.

Keen to give it another go but after reading posts about different "builds", I just want to confirm:

To get latest working build I just flash everything I need from OP? And I found Opengapps worked better for me.

Also, has anyone had HTC Sense Home for Oreo working on this Rom?

Thanks
[One (M9) Original Android Development] Claymore1297:
Yes, all you need is in OP
[One (M9) Original Android Development] supachris:
Will you keep this ROM also alive?
[One (M9) Original Android Development] Claymore1297:
Also? yes of course. A new update will arrive in the next few days...
[One (M9) Original Android Development] supachris:
I mean beside of the AICP official version.

Great! Thank you!
[One (M9) Original Android Development] SoveWar:
Got the same problem again: my phone is in some bootloop, but now from a randomly reboot perform from my phone itself. I tried your methode but no luck. I putted it the freezer to keep my phone cool to reboot but also with no luck, last time this did the trick.

I friend of my same its my sim-card, I'm at the moment in a differed country. So I tried to reboot with out a sim but still no luck after 20 hours of trying to reboot.

[update] I used a RUU to flash back to stock, I'll reinstall the custom rom when I'm back home
[One (M9) Original Android Development] HsHTCsen:
Hi, I've just spent the day getting this ROM up and running how I wanted it and everything seems to be running smooth as silk including Magisk and systemless Xposed except for a few random reboots here and there but think I could live with it.

However, I got home and turned WiFi on and instantly I get a reboot. This happens every time I try to turn wifi on.. Instant reboot. Any suggestions please?
[One (M9) Original Android Development] msmita:
i use htc bolt, possible for me to build this version on my device? i think the same SoC can build with this kernel version and android version?
[One (M9) Original Android Development] roadkill42:
That be sweet I'm on bolt to I don't have PC or I try my self . From what I heard from htc the bolt will not get the oero update
[One (M9) Original Android Development] xhoi287:
What new features will the new build bring Claymore?
[One (M9) Original Android Development] Claymore1297:
#### New build is up!! ####

the builds are containing mainly the following:

-randomly appearing deepsleep issue should be solved now

-august ASB's

-new DTS eagle kernel impl by [MENTION=7836278]LazerL0rd[/MENTION] and other DTS-stuff

Enjoy!
[One (M9) Original Android Development] supachris:
Great! I will test is the hardware encryption now works correctly with deep sleep.
[One (M9) Original Android Development] supachris:
Thanks for the new update!

The double tap to wake seems not to be working :(

And can you please enable the ambient display? This would be great!

Thanks a lot keeping this nice phone up to date!