yashsingh1/xdaforums huggingface dataset:
[One (M9) Original Android Development] Claymore1297:
which output produces the command on your device?

EDIT: I think we had exact this problem in this thread, so please scroll a bit back and perhaps you'll find the solution :)
[One (M9) Original Android Development] Anjelikk:
What OpenGapps should I use with the latest builds? Nano?
[One (M9) Original Android Development] herr_blaschke:
I figured out it is enough to clear cache on the apps settings and settings storage and switch language from a to b and back to a. This makes search in settings work again.
[One (M9) Original Android Development] Evengard:
Because you didn't elaborate on which stage you are interested in my fingerprint strings I made some experiments to get them all =)

1. ONLY lineage-15.1-20180511-UNOFFICIAL-himaul.zip + open_gapps-arm64-8.1-pico-20180513.zip:

Nag window on each reboot: absent (obviously)

SafetyNet (used a third party app from Play Store to check it):

Basic - pass

CTS - fail (yes it does fail from the beginning, that's why I wanted to see a fingerprint where it doesn't!)

Fingerprint:

[ro.bootimage.build.fingerprint]: [htc/himaulatt_na_gen_unlock/htc_himaulatt:7.0/NRD90M/870623.7:user/release-keys]
[ro.build.fingerprint]: [htc/himaulatt_na_gen_unlock/htc_himaulatt:7.0/NRD90M/870623.7:user/release-keys]
[ro.vendor.build.fingerprint]: [htc/himaulatt_na_gen_unlock/htc_himaulatt:7.0/NRD90M/870623.7:user/release-keys]

2. Same as above + Magisk-v16.0.zip + MagiskManager-v5.7.0.apk

Nag window on each reboot: absent (not Magisk fault)

SafetyNet (used the one from MagiskManager):

Basic: pass

CTS: fail

Fingerprint:

[ro.bootimage.build.fingerprint]: [htc/himaulatt_na_gen_unlock/htc_himaulatt:7.0/NRD90M/870623.7:user/release-keys]
[ro.build.fingerprint]: [htc/himaulatt_na_gen_unlock/htc_himaulatt:7.0/NRD90M/870623.7:user/release-keys]
[ro.vendor.build.fingerprint]: [htc/himaulatt_na_gen_unlock/htc_himaulatt:7.0/NRD90M/870623.7:user/release-keys]

(basically the same, nothing changed)

3. Same as above + universal-safetynet-fix-v2-beta-5-magisk-v14.zip

Nag window on each reboot: PRESENT (yep, that's the culprit)

SafetyNet (used the one from MagiskManager):

Basic: pass

CTS: PASS (yep, that indeed makes the device pass the CTS)

Fingerprint:

[ro.bootimage.build.fingerprint]: [Xiaomi/sagit/sagit:7.1.1/NMF26X/V8.2.17.0.NCACNEC:user/release-keys]
[ro.build.fingerprint]: [Xiaomi/sagit/sagit:7.1.1/NMF26X/V8.2.17.0.NCACNEC:user/release-keys]
[ro.vendor.build.fingerprint]: [htc/himaulatt_na_gen_unlock/htc_himaulatt:7.0/NRD90M/870623.7:user/release-keys]

And it is here where we get that Xiaomi fingerprint, because among other things it seems to fake a valid fingerprint for CTS. It happens that this exact patch was done for some Xiaomi phone on the beginning but ended up working on nearly all phones, which is nice, but because of that alien fingerprint LOS 15.1 (or, more probably, Oreo itself) seems to worry about the vendor firmware. Hence the nag window.

What I wanted to try is to substitute with a fingerprint which is "known to pass" on other himaul devices, hopefully it will be accepted for both CTS and Oreo internal checks.
[One (M9) Original Android Development] Claymore1297:
if you are conected via adb try this command:

adb shell setprop ro.build.fingerprint htc/himaulatt_na_gen_unlock/htc_himaulatt:7.0/NRD90M/870623.7:user/release-keys
[One (M9) Original Android Development] Evengard:
setprop: failed to set property 'ro.build.fingerprint' to 'htc/himaulatt_na_gen_
unlock/htc_himaulatt:7.0/NRD90M/870623.7:user/release-keys'

But anyway even if it worked I'm pretty sure it would make CTS fail again...
[One (M9) Original Android Development] Claymore1297:
you need to be root on adb-shell.

Idk, I don't have any experience with this.
[One (M9) Original Android Development] Evengard:
Now some fresh info here!

I've used the STOCK fingerprint (thanks to this message: https://xdaforums.com/showpost.php?p=76221627&postcount=526 ) - which is an HTC Himaul one. It INDEED DOES pass CTS!!! [MENTION=8276284]Claymore1297[/MENTION] [MENTION=3082717]Flyhalf205[/MENTION] Please consider updating your config files with the

htc/himaulatt_na_gen_unlock/htc_himaulatt:7.0/NRD90M/894012.12:user/release-keys

stock fingerprint as it DOES pass CTS, and maybe your build will pass CTS too after this change without any needed patches.

Anyway, I managed to get rid of the nag window (doesn't matter if you are using the Xiaomi one or not!).

As you saw, there is a discrepancy when using universal-safetynet-fix-v2-beta-5-magisk-v14.zip:

[ro.bootimage.build.fingerprint]: [Xiaomi/sagit/sagit:7.1.1/NMF26X/V8.2.17.0.NCACNEC:user/release-keys]
[ro.build.fingerprint]: [Xiaomi/sagit/sagit:7.1.1/NMF26X/V8.2.17.0.NCACNEC:user/release-keys]
[ro.vendor.build.fingerprint]: [htc/himaulatt_na_gen_unlock/htc_himaulatt:7.0/NRD90M/870623.7:user/release-keys]

As you can see, while ro.build.fingerprint == ro.bootimage.build.fingerprint, the ro.vendor.build.fingerprint is the old one. As I discovered, it actually just compares all these strings on boottime, and if they are all equal - no nag window!

So, all you need to do is:

1. Install everything, including Magisk and universal-safetynet-fix-v2-beta-5-magisk-v14.zip

2. Boot the OS - you will see the nag window, which is completely fine

3. Use any mean to extract the file /magisk/xiaomi-safetynet-fix/post-fs-data.sh (easiest is install Root Explorer and just copy it to /sdcard, then just connect your phone to PC and copy it to PC)

4. Open it and go to line 165

Here you see the used fingerprint (you can change it to the stock one above if you want or just leave as is, doesn't matter for the nag window)

5. You can see theese lines:

$RESETPROP "ro.build.fingerprint" "$FINGERPRINT"
$RESETPROP "ro.bootimage.build.fingerprint" "$FINGERPRINT"; }

Just add this line in between them:

$RESETPROP "ro.vendor.build.fingerprint" "$FINGERPRINT"

Should look like this:

$RESETPROP "ro.build.fingerprint" "$FINGERPRINT"
$RESETPROP "ro.vendor.build.fingerprint" "$FINGERPRINT"
$RESETPROP "ro.bootimage.build.fingerprint" "$FINGERPRINT"; }

6. Get the file back to the phone (the reverse of what you done in 3)

7. Make sure the file have correct permissions! (chmod 644 /magisk/xiaomi-safetynet-fix/post-fs-data.sh from a ROOTED shell)

8. Reboot and enjoy! You will have both CTS pass and no nag window!

UPD: on a side note BLUETOOTH seems to be kinda unstable, sometime crashing and disconnecting then self-recovering and reconnecting back to my headphones.
[One (M9) Original Android Development] Claymore1297:
I will check the fingerprint, thanks for info!
[One (M9) Original Android Development] Evengard:
About the Bluetooth disconnect bug: attached DMESG and LOGCAT on when it happened, but unsure if it is helpful.
[One (M9) Original Android Development] Claymore1297:
we had this already in the past - problem is, all my BT-devices run without error, so I couldn't test it ... I will check this.
[One (M9) Original Android Development] nimbius:
crypt in m9

Ive been rather confused by the status of hw crypt on this phone. Ive built 14.1 with no crypto and see competent performance on the device thanks to the chipsets AES headers, not the platforms

snapdragon crypto framework. if the hw_crypt framework changed between android 6-7 its certainly due to the change in crypto on the device from full disk to file based and multiple boot modes of crypto in an HSM type configuration similar to iPhone. Theres also talk of Google having disabled the HW crypto feature on older phones due to stability issues in its initial rollout...its also possible the phone simply doesnt have the appropriate trusted platform that started showing up in snapdragon 820...in which case it will never have HW crypt.

HTC's latest official release is only android 7.

Again, with AES headers LUKS performance is not appreciably affected as best I can detect in quantifiable tests however im willing to perform more. HW crypt is a hard requirement from the project though...any reason? Can we caveat the official build with a note that performance may be degraded?
[One (M9) Original Android Development] alexboda:
same bug in both versions...... when i try search available mobile networks---it says *error while searching* ((((( sad

and...still no led-notification
[One (M9) Original Android Development] Claymore1297:
LED notification is working on latest build - with some bugs, but working.

Which build are you running?

As mentioned before, provide some logs, otherwisev I'm not able to help.
[One (M9) Original Android Development] massatt212:
What is not working

Camera

Some audio

Developers

has any of these been fixed ?
[One (M9) Original Android Development] Claymore1297:
as mentioned before:

Camara works - for video recording is Footej Camera-app required

Audio works

well, if developers are working ...hm who knows ;)
[One (M9) Original Android Development] massatt212:
Where is the latest Link so i can go crazy

never mind found it
[One (M9) Original Android Development] Claymore1297:
some users reported some bluetooth-related problems.

So, now I want know, how many of you are affected from this and which BT-devices are affected.

Thanks for your input!
[One (M9) Original Android Development] xhoi287:
Theres a official lineage os 15.1 version for htc one A9 isnt there going to be one for M9
[One (M9) Original Android Development] annascott:
I have a big problem - Wear OS app is crashing my phone as soon as bluetooth is on and it's scanning for a watch. I tried resetting all networks, reinstalling the app (I also tried the previous Android Wear version), clear data on app, not using privacy guard, but nothing works and I can't pair my phone.

Any suggestions? I really need my watch.

Update: I also dirty flashed the latest built, and wiped cache. I'm attaching a logcat.
[One (M9) Original Android Development] Claymore1297:
I'm 100% sure, that this is "our" BT-problem, I metioned some posts before.

It seems, that this is only occuring on smartwatches and bt headphones.
[One (M9) Original Android Development] annascott:
I attached a logcat, does it help?
[One (M9) Original Android Development] Claymore1297:
yes, this is always welcome :)
[One (M9) Original Android Development] annascott:
I got it to work! First, sideload a specific version of Android Wear from APKMirror. Then you open the app and turn on bluetooth, it will crash a lot, just tap reopen app over and over and keep going with the pairing process. Once it's done, update to the new Wear OS from the Play store :)
[One (M9) Original Android Development] xhoi287:
Its been a week since i use himawl lastest build and didnt found any major bug.There its only the notification light that doenst work properly.i didnt found any problem with bluetooth since now.i use it as my daily driver
[One (M9) Original Android Development] Anjelikk:
I used a bluetooth speaker with the new build and it worked flawlessly
[One (M9) Original Android Development] xhoi287:
Claymore i think theres a bug in whatsapp.Video call get closed idk if its because of camera or what ,i didnt tried other apps.Give it a look please
[One (M9) Original Android Development] shaqman89:
It would be always better to include a log. I remember it being a standard for bug reporting.
[One (M9) Original Android Development] Saad Saleem:
Need modified updater script

Can you please modify and provide updater script and updater binary for himawhl

i've tried to edit it , it always give errors

I really need for himawhl
[One (M9) Original Android Development] SoveWar:
Hi, I tried to install the himaul built on my himauhl but I get error: "E3004: This package is for device: htc_himaul,htc_himauhl,himaul,himauhl"

(had to remove the url in the quote)

Edit: Fixed it with a TWRP update
[One (M9) Original Android Development] Claymore1297:
I could test this today, and it worked for me.
[One (M9) Original Android Development] Bu'dge:
[MENTION=8276284]Claymore1297[/MENTION] thank you for the update on the new rom....keep up the good work....having an issue though......is anyone having trouble with USB connectivity ?
[One (M9) Original Android Development] iHateWebOS:
I live in the boonies, and depend on pdanet for internet, I keep my phone plugged into USB for hours without issue so far
[One (M9) Original Android Development] Bu'dge:
so i guess its my port giving trouble then, thank you
[One (M9) Original Android Development] alexboda:
the tread is dead ?
[One (M9) Original Android Development] shaqman89:
It might be quiet here but the last activity was only about a week go, so no, it is not dead.
[One (M9) Original Android Development] thafath:
Hello and thank you for your efforts to bring los 15.1 to our phone.

I have been building los 14.1 for a couple of weeks/months, I switched recently to build los 15.1 using instructions in the opening post, it builds with no issue, it was flashed without issue but it ends in a boot loop. Any hint on where to look? Or to debug the issue. Any help is much appreciated.

Thank you.
[One (M9) Original Android Development] Claymore1297:
The instructions in the OP are outdated.

Please switch in you roomservice.xml to my github-repos and everything will be fine.

https://github.com/Claymore1297/android_kernel_htc_msm8994

https://github.com/Claymore1297/android_device_htc_hima-common

https://github.com/Claymore1297/android_device_htc_himaul

https://github.com/Claymore1297/proprietary_vendor_htc

and you need to pick, this commit

https://github.com/Claymore1297/and...mmit/1e597fdbf233d361af1e6ca70ff69cb4c8d9cb73

otherwise, you will end up in a compile-error.
[One (M9) Original Android Development] thafath:
Thank you very much, I will definitely try that and report back here. Have an excellent day.
[One (M9) Original Android Development] Claymore1297:
Good news:

I got incredible help form [MENTION=6366997]UltraM8[/MENTION] and [MENTION=7836278]LazerL0rd[/MENTION] from AINUR AUDIO-team.

Just yesterday [MENTION=7836278]LazerL0rd[/MENTION] included his very own DTS-hpx/sa+ -patch to our kernel, first tests showed a incredible audio quality.

I will make a new build, when next ASB's will getting merged, and which also include these audio improvements.

So stay tuned - this will gonna be big!
[One (M9) Original Android Development] xhoi287:
Can i flash the build without wiping the particion.Im in your lastest build claymore.Like we did with lineage os 14.1 from update section?
[One (M9) Original Android Development] Claymore1297:
dirty flash should be OK
[One (M9) Original Android Development] xhoi287:
Thanks for the answer

---------- Post added at 06:54 AM ---------- Previous post was at 06:53 AM ----------

Thanks for the answer
[One (M9) Original Android Development] Eran baruch:
Great news! Thank you [MENTION=8276284]Claymore1297[/MENTION]!
[One (M9) Original Android Development] thafath:
Thank you very much. I was able to build the rom, and it's working perfectly. Great job.

I had to revert this commit, https://github.com/Claymore1297/and...mmit/3f84b7e45d1327897397ff6958a088774f9ace1a

Getting errors with it.

Thak you again, excellent job.
[One (M9) Original Android Development] Claymore1297:
but then you have no beautiful audio...

This commit solves the compilation error, just pick it:

https://github.com/Claymore1297/and...mmit/1e597fdbf233d361af1e6ca70ff69cb4c8d9cb73
[One (M9) Original Android Development] xlayn:
Can't wait for new build, sound quality back!!!

Question... anyone else have had a problem syncing contacts with DavDroid and owncloud and this build?

Another one, I remember the first build could set the vibrator intensity... Or wast that on los14?

Thanks [MENTION=8276284]Claymore1297[/MENTION]
[One (M9) Original Android Development] thafath:
That did it. Thank you very much for your excellent work on this, much appreciated.
[One (M9) Original Android Development] massatt212:
when will we be seeing the new update
[One (M9) Original Android Development] Claymore1297:
soon :)
[One (M9) Original Android Development] woodman:
Hello [MENTION=3082717]Flyhalf205[/MENTION], can you please read your PMs?

Thanks

Wood Man

Senior Moderator
[One (M9) Original Android Development] xhoi287:
Lets hope for this version goes in official state.:)
[One (M9) Original Android Development] Claymore1297:
HERE WE GO... #### New build is up!! ####

himaul:

https://www.androidfilehost.com/?fid=962339331458999250

himawl:

https://www.androidfilehost.com/?fid=674106145207494307

the builds are containing mainly the following:

-june ASB's

-beautiful audio

-camcorder fixed (including whatsapp video-recording)

all mayor bugs are solved now, so what left is:

- whatsapp videoplayback-issue (workaround is, restart whatsapp)

- bluetooth-drops on some headphones and smartwatches

- HW-encryption

very special thanks go to [MENTION=6366997]UltraM8[/MENTION] and [MENTION=7836278]LazerL0rd[/MENTION] from AUDIO-AINUR, for the incredible help and enthusiasm.

Follow-up fixes will come ...
[One (M9) Original Android Development] xlayn:
"-beautiful audio" crying while puts headphones on.... installing...
[One (M9) Original Android Development] UltraM8:
I put lot's of efforts on audio at the kernel level, i didn't think hima can get to this dynamics at all, but daaaamn, i like the result. Speaker is an issue tho
[One (M9) Original Android Development] xlayn:
Thank you very much for your effort.

I did bought M9 because of the excellent reviews on audio on GSMArena... sadly it was not supported on lineageos.

Your effort would allow me to enjoy more the device.

Thanks!!!!
[One (M9) Original Android Development] UltraM8:
You can pair the rom with my Ainur Sauron mod - it might give you even better results (u can try at least and decide for yourself)
[One (M9) Original Android Development] xhoi287:
Thanks good job Claymore .If you guys want to know update with dirty flash works.Thanks to all of you guys.
[One (M9) Original Android Development] nimbius:
it works!

Congratulations and thanks to Claymore and LazerL0rd for all the hard work, support, and dedication!!

I have tested this build of 15.1 against my HTC One M9 (ATT) with S-ON and everything functions as expected.

The device also properly encrypts!

Beer is on me next time im in Germany :good::good:
[One (M9) Original Android Development] LazerL0rd:
i hope you enjoy my stuff ;)
[One (M9) Original Android Development] xhoi287:
I have been able to test cam recording and now works in stock camera app whatsapp and telegram in app camera which didnt work in last build.
[One (M9) Original Android Development] xlayn:
Volume is impressive... I use a Fiio e7 and dragonfly black headphone amplifier and dac and volume levels are as impressive as those units... I'm testing with sennheiser amperior and sound it's superb.... I'll try with the akg 550 and senn hd598...

Thanks! all of you who had work to get this device working!!!
[One (M9) Original Android Development] Anoses:
ive found a lot of strange system apps like: cacao, cherry, pumpkin, lavender and tomato are these from gapps or from this rom and what are these for
[One (M9) Original Android Development] xlayn:
I don't have gapps installed on my cel and after dirty install I don't have any of those apps, I did search on the drawer and settings search.
[One (M9) Original Android Development] xhoi287:
I dont have nothing like that too might be something with gapps,which version of gapps you installed?
[One (M9) Original Android Development] Anoses:
now ive looked at the id of these apps they seem to be overlay apps for example

Pumkin org.linageos.overlay.accent.orange

Banana org.linageos.overlay.accent.yellow and so on

they are locatet in /system/app/LinageYellowAccent/LinageYellowAccent.apk

Linage version is 2018 05 11

but i dont what these are for
[One (M9) Original Android Development] xhoi287:
I dont know i dont have these apps im in the lastest version
[One (M9) Original Android Development] Claymore1297:
These are accent colors, you where talking about
[One (M9) Original Android Development] xhoi287:
Everything its fine for me the only problem i found its the video call in whatsapp that dont work
[One (M9) Original Android Development] bubba1601:
That's mentioned in the known issues with the new build. The workaround is to restart WhatsApp - I can confirm this works fine.
[One (M9) Original Android Development] Claymore1297:
it seems, that it is the same issue (video playback+video call) ... restart whatsapp and it work. will have a closer look on it.
[One (M9) Original Android Development] boredherobrine13:
Is there any reason why the GPU is supposed to run at up to 630 Mhz but always reports to be running at 180 regardless of workload? I'm guessing this is what causes UI lag...any known fixes?

Edit: I was able to use a kernel app to change the minimum GPU freq to 630 Mhz. It now shifts between 180 and 630 depending on workload. This is really...suboptimal. It doesn't seem to use any frequencies besides 630 or 180. So either total lag or battery burn, no in-between balance of battery burn/performance. Why is this necessary? Is this a bug the dev can fix?

Edit 2: Despite this frequency adjustment, my device still performs better than only 1% of other HTC One M9s on 3DMark Slingshot Extreme, scoring over a thousand points below what it should. What's up with GPU performance guys? Seriously.
[One (M9) Original Android Development] abbas_392003:
What is the official address of this ROM?
[One (M9) Original Android Development] boredherobrine13:
It doesn't have a website, if that's what you're asking for.
[One (M9) Original Android Development] mfg81:
Just wanted to say the latest build is great.

Tyvm.
[One (M9) Original Android Development] abbas_392003:
I want a site like Rom AICP for the latest update of this Rom
[One (M9) Original Android Development] Claymore1297:
here you can find the latest updates:

https://androidfilehost.com/?w=files&flid=267579&sort_by=date&sort_dir=DESC

typically, I upload a build after latest ABS's are getting merged...
[One (M9) Original Android Development] abbas_392003:
thank you so much my dear
[One (M9) Original Android Development] The_Walking_Playground:
Hi,

I wanted to say thank you for continuing the work on this ROM. I'm using your latest version, and everything seems to be working well, except the IR blaster. When I install AnyMote, there is no response from the TV when toggling the power on the remote. Just to be sure it wasn't my device, I just RUUed back to stock and confirmed that using the same app, the IR blaster functions properly. Is there any way you can look into this? If you need a log of some sort, please let me know. You should be able to test this locally, though, since there are several free remote apps and pretty much everyone has a TV :).

TWP
[One (M9) Original Android Development] Claymore1297:
maybe a SELinux issue:

06-19 23:57:45.354 4262 5036 D Smart IR Remote 1529445465354: transmitting KitKat command, wtf code: false, long cmd: false, on 8.1.0

06-19 23:57:45.658 5037 5037 W Binder:802_8: type=1400 audit(0.0:23418): avc: denied { execute_no_trans } for path="/system/bin/sh" dev="mmcblk0p66" ino=420 scontext=u:r:system_server:s0 tcontext=u:object_r:shell_exec:s0 tclass=file permissive=0

06-19 23:57:45.671 802 3225 E ConsumerIrService: Error transmitting: -1

06-19 23:57:45.672 4262 5036 D Smart IR Remote 1529445465672: transmitted

will have a closer look.

btw. I use "Universal Remote for HTC One" and works fine ...

EDIT: but I think, it hits a neverallow on O...

EDIT2: can you try this:

https://xdaforums.com/showpost.php?p=75711732&postcount=4
[One (M9) Original Android Development] The_Walking_Playground:
Hi,

Thank you for that link. Setting that option worked. Sorry for the false alarm. Thanks for the fast response!

TWP
[One (M9) Original Android Development] massatt212:
testing

idk if im doing something bad

but the sound is still terrible any advice ?

And i cant play music without phone freezing
[One (M9) Original Android Development] Claymore1297:
can you explain what you did exactly... details are welcome