yashsingh1/xdaforums huggingface dataset:
[One (M9) Original Android Development] Pfony:
Hello Claymore,

first of all: Thanks so much for keeping our phone alive and absolutely up to date!

I was so excited to install LOS 18.0 and especially was fully convinced to finally get rid of the very annoying "echo in voice calls"-bug.

I already tested the AICP 16.0 (built 2020-11-15) and it was fixed (as promised ;) (y)) (as already posted here).

So I just installed very very fresh (wiped everything (cache, data, system, yes even the internal storage)) the lineage-18.0-20201206-UNOFFICIAL-hima.zip .

Here it comes: the echo is still there, not fixed !!!!! Oh no :eek:! Do you have any idea what the difference is between aicp and los regarding voice calls? There must be something.

Changing volume still has no effect even when you put the call on speakers.

Everything else works (as far as I have tested for now) perfectly!

I had so much hope in that....could you please 😇 take another look on this echo in voice calls issue and fix it as on aicp.

Again: Thank you so much for your work.
[One (M9) Original Android Development] Claymore1297:
thanks for the headsup - I forget to merge this kernel-commit into new LOS-tree. will be included in next build!! :)
[One (M9) Original Android Development] jkrajcir:
Hi,

where can I download TWRP 3.4.0-0 with SAR support?
[One (M9) Original Android Development] Pfony:
Hello jkrajcir,

you can download from here: twrp-3.4.0-0-hima.img

@Claymore1297 :

short feedback from your most recent build:

- live display not working + you cannot change color temperature right now

- under "styles & wallpapers" if you want to change from one icon shape to another it is not always applied

- LOS updater gives an error message (most likely because there aren't any !?!?)
[One (M9) Original Android Development] Claymore1297:
livedisplay isn't ready I think.

Which error you get on updater? also logs could be useful here...
[One (M9) Original Android Development] Pfony:
Regarding the updater please refer to the following screenshot:

View attachment 5151349

Also very interesting is the "last checked" date :rolleyes:;)
[One (M9) Original Android Development] Claymore1297:
please try again.
[One (M9) Original Android Development] Pfony:
I think it works again. Great job (y)
[One (M9) Original Android Development] bertoteo:
Same to me. Echo is still there :cry:
[One (M9) Original Android Development] bertoteo:
Echo apart, great job!!!:cool:

Got error 64 on installing opengapps_arm11 posted (i believe for wrong 32bit architetture) but the NikGappsCore64 did well (i don't know which differences there are).

I can't find in development options how to enable advanced reboot (for reboot into twrp)
[One (M9) Original Android Development] Pfony:
@Claymore1297

Just to let you know:

also in your current LOS 18 (20201206) build there still is the problem with unstable bluetooth connections in cars as already described in the LOS 17.1 thread here.

Now I also experienced very unstable bluetooth connections in a Mercedes (2017) with the "command online"-system.

To be more specific:

bluetooth itself is enabled the hole time but opening calls fails at first attempt and after some time waiting the phone starts a second attempt automatically and the call is established correctly. Also, and that is even worse, when having somebody on the phone, after round about 1 minute the call ends or the call's audio is switched to the phone instead of the car's audio-system.....veeery annoying :(.

As assumed in my LOS17.1 post (link above) maybe it has something to do with the phone's switching into lockscreen/sleep after some time of touch-inactivity with the phone and I often get this "worked around" by just click on the power butten (to wake it up from sleeping?!)

Does anybody else has any similar experience with

bluetooth + phone calls + car's audio-system

or am I the only one :unsure:?

Thanks for your investigation :).
[One (M9) Original Android Development] haseebhamid:
My Bluetooth and calls are fine but I'm unable to make wifi hotspot
[One (M9) Original Android Development] supremejustice:
do yall know if file-based encryption is supported on this kind of device ? Cause I tried enabling it and now my phone is stuck in a bootloop :/
[One (M9) Original Android Development] Selocan20:
Edit:

TWRP is okay again.

but i‘ve problems with battery after flashing. At Night the Battery was 47% but today morning the battery was empty.

Any solutions for this issue?
[One (M9) Original Android Development] oneofthekaramosowbrothers:
I had a huge battery drain as well. For some reason I had to flash TWRP again 3.4.0. Because I wanted to use Francos Kernal Manager I installed Magisk to root my phone. The problem disappeared. Coincidence or not, I don't know.

Before the device got unusually warm as well during normal usage.
[One (M9) Original Android Development] bertoteo:
Cannot activate hotspot, the toggle switch off immediately
[One (M9) Original Android Development] multiwirth:
I recently flashed this build on my m9 and i was very surprised.

How did you manage to get that hardware DSP to work correctly?

No more distortion and proper limiter wow that´s amazing!

I saw you reverted the commit from here, would this work just that simple on 17.1 aswell?
[One (M9) Original Android Development] shpitz461:
I remember in some other phones, in order to get VoLTE and VoWifi additional apk's were needed.

At this point I'm going to retire the M9 and put it back in the drawer until it is needed again.

I might do a flashing party at some point to maybe try and figure this one out.
[One (M9) Original Android Development] OGdroidster:
The build props are

#volte setprop

persist.dbg.allow_ims_off=1

persist.dbg.volte_avail_ovr=1

persist.dbg.vt_avail_ovr=1

persist.dbg.wfg_avail_ovr=1

persist.sys.phh.ims.caf=true

I made a working ims apk with permissions in aicp. But we need something to show the hdvoice in the settings app like on the stock rom. On stock you can run hdvoice without ims resistration active just flip on the volte provisioning in the telephone app and turn on hdvoice in the setings app. But i have no clue how to get hdvoice into the settings app like on stock. Thats basically all that is need to do for the custom rom running android 11.
[One (M9) Original Android Development] mmortal03:
Without IMS registration, what would that do, though? It is my understanding that VoLTE will not work without IMS registration.
[One (M9) Original Android Development] mmortal03:
From the 19.1 thread:

@webfeind , I'm testing this with a RedPocket GSMA SIM on LOS 18.1 (not yet 19.1), and data works, but calls aren't going through, so, yes, the next step is for me to test stock, and then test it again after going back to LOS 18.1.

@OGdroidster , correct me if I'm wrong, but I don't believe there's a settings menu on these phones to view IMS registration status. It's not there in the hidden phone information menu like on other phones (or the three dot menu there), and it's not in the About phone SIM menus.
[One (M9) Original Android Development] mmortal03:
Update: VoLTE works for me on stock Nougat after a few restarts of the phone, but after flashing it back to LOS 18.1, calls aren't working, even after multiple restarts. Data and SMS work.
[One (M9) Original Android Development] OGdroidster:
Because you have to have to ims apk in system/privapp and then its written permissions in the perssion folder. Plus you have to have the overlays for the volte to show in the settings app. I have a working apk with permissions that i rewrote and updated from another project. Hopefully whith the help of claymore we can get this working. You also nred the setprops set in the build prop which i posted earlier.
[One (M9) Original Android Development] OGdroidster:
You van run provisioning on or over ims. All you need is the volte provission switch to be active so it works over and not on. If that makes sense. Tbats how it works with my carrier. I think it matters if you are are running a mvno or not.
[One (M9) Original Android Development] mmortal03:
I do know my MVNO supports VoLTE with this phone, because it works just fine in stock.

That's great! Hopefully, @Claymore1297 sees this.

As I posted in the AICP thread, the following options are on the hidden menu in stock:

Turn on / off IMS registration required

Turn on / off VOLTE provisioned flag

Turn on / off SMS over IMS

Here's a screenshot:
[One (M9) Original Android Development] zamarro71:
Why won't it let me overclock? It doesn't go up more than 1344, I want to go up a little more... what do I do?
[One (M9) Original Android Development] mmortal03:
No judgement, but hima phones already generally get so hot that you can't touch them -- I can't imagine how it would be practical to overlock these. What are you trying to do?
[One (M9) Original Android Development] mmortal03:
Same here on lineage-18.1-20211220-UNOFFICIAL-hima, so it looks like encryption is a no-go on hima LOS 18.1.
[One (M9) Original Android Development] Marko Indaco:
Hi, thanks for nice job. Only I found that navbar is a bit bulky since the M9 screen is not that wide, then I would ask if is possible to hide the navbar is some way, maybe with an additional button like in old ViperOneM9 (see screenshot below).

I also would try Ultimate Dynamic Navbar to see if fits this little drawback.

Logcat Reader (F-Droid version) can be good for log reports, just in case needed?

Update: Safetynet passed as well :cool: (since the Props Config didn't show the M9 version in his list, you simply just select HTC 10, then follow the usual procedure).

Swapped to AICP 16.1. Regards 👋
[One (M9) Original Android Development] Claymore1297:
well this is the fix: https://github.com/Claymore1297/and...mmit/8c40179f9147c6f5d344e5509b4871b9e9ec2d42 and the fix is also merged into my LOS 17.1 trees, will see, if I find time to do another build...
[One (M9) Original Android Development] multiwirth:
maybe if you can tell me all repos i need, i can do my own builds probably.

I was confused about android_device_htc_hima-common since it´s default branch is lineage-16.0 but has a lineage-17.0 branch but no 17.1 so idk what to clone :ROFLMAO:

Anyways LineageOS 18 seems to run fine even with Viper4Android so i´ll stay on this probably.

With the fix, the M9 sounds almost as great as my M8 which is really nice.
[One (M9) Original Android Development] Claymore1297:
Sure, will send you my roomservice...

Edit: Plesse look into los 17.1 OP, there is all you need to build. If you have some questions, PM me.
[One (M9) Original Android Development] symetrk:
Hi, new here... (though not completely new to custom ROMs, so some experience with flashing etc). Have been using a previous Lineage version for a while now but the echo issue is really problematic.

Tried an AICP ROM instead which purported to have it fixed but it screwed up my microphone somehow such that it was rendered almost useless, so I'm back to Lineage for the moment, which I quite like otherwise.

I've got this latest version running and it's great overall, but the echo problem persists and I'm wondering if any hope is on the horizon - you mentioned (above) including the fix in the next build - when might that happen?

I'll happily make a donation if that helps with motivation... (won't be a big one, sorry, I'm a musician and times are tough but getting this phone working properly would save me buying a new one for a while!)

Note: the echo is much worse if I try to use speaker, barely acceptable if I put the phone against my head, and a little better - but still present - on wired headphones. I do not have wireless ones, so I can't try that. And as everyone else has pointed out, it's not an echo on my side, it is a problem for the person I'm talking to.

Thanks in advance! Much appreciated! Awesome work in general!
[One (M9) Original Android Development] Ebizza:
Do you have to turn on Legacy mode to use ViPER4Android on your M9? And does the app generally work for wireless buds?
[One (M9) Original Android Development] multiwirth:
Yes and yes

Works fine for me
[One (M9) Original Android Development] bertoteo:
is there any update on the next build with the eco problem solved?
[One (M9) Original Android Development] Pfony:
Additionally to the echo-problem: will the "color temperature"-feature be back in next build? I really do miss that feature, especially late in the evening 😇

We haven't heard any news about the next build...is there anything the community can support you with?
[One (M9) Original Android Development] platinumthis:
I have a question about the Sound , Its Sounds so ****ty in speakers... anyone have Same issuse ? There is clearly a Change , IT Sonds Like the speakers are broke. Cant figure Out was IT IS and how i Turn this Off...
[One (M9) Original Android Development] multiwirth:
The sound just improved by a new commit which enabled back the tfa dsp firmware to protect the speaker/amplifier from distortion.

Not sure what kind of issue you're facing but everything should be better now.

Beforr this commit, the audio will distort quickly at low volumes.

Should be fixed now
[One (M9) Original Android Development] platinumthis:
Nice, this was needed xD
[One (M9) Original Android Development] erdo_king:
Nearly everything works like a charm. Very good work!

But I am unable to connect adb over wifi (usb works).
[One (M9) Original Android Development] Claymore1297:
Logs please
[One (M9) Original Android Development] Claymore1297:
the trees are outdated ... you need this:

hima: lights: Remove libhdidltransport & libhwbinder · AICP/device_htc_hima@a6b2bd4

Change-Id: Ibd0b8bc135ab7b3b99f8771007787483e0d09db2

github.com

Will updated as soon as I have time

But you can look at the AICP-trees, they fit
[One (M9) Original Android Development] platinumthis:
Good Friday Claymore1297, I like your work for the m9 ****ing really someday i will surely donate for it , but for now i dont habe that much Money maybe Nest month hahah. My question is did you notice a pitchy sound ? Espesially when you get a notification its pichty , i tryed to disable tfa it was then off but it still is there , its maybe Dolby 2ts ? Especially in speakers it appers. It Mike Tiere is 100% no bass and More pitchy and noise its just not gold sound for the speakers for real, the other things work Mike a charm all is good but the sound in the speakers is just not that good... It not the amplifier

Rellay i thank you for all , good work for real.

Thumbs UP!
[One (M9) Original Android Development] multiwirth:
Oh a very quick answer, thanks ;)

Will have a look into it
[One (M9) Original Android Development] multiwirth:
Did you already try Viper4Android?

AOSP android doesn't come with the htc boomsound since it's proprietary stuff so the speaker optimizations aren't present in any custom rom.

But still since the tfa amplifier firmware is now used, it should sound much better even without anything.

However i suggest you to try viper4android and enable the "speaker optimization" it's in my opinion even better than boomsound since it sounds more natural and not overloaded and without EQ limiter and such.

The best really is the Equalizer set to "Treble Boost"+ "speaker optimization"
[One (M9) Original Android Development] platinumthis:
Sure i use it, but i do this to the EqualizerView attachment 5219145

And its still pitchy, i dont like the speaker optimization couse i can do better with equalizer but now its not that good, i builded a rom where this was not present and also the call volume steps where then not working, but now i cant reproduce it sadly and got always this pitchy sound... when i got it finally to not pitchy then the volume steps in calls where not working that give me the info its is sucessfully another sound but volume steps not working. Maybe Claymore know it these 2 things are friends this ptichy and the fixed volume steps.
[One (M9) Original Android Development] multiwirth:
That's what i've set up.

View attachment 5219163

Sounds almost as good as my M8

It's currently claymore's first and last build of lineage-18.0

I'm currently syncing sources with AICP trees to build 18.1 will check that if there are any issues for me
[One (M9) Original Android Development] platinumthis:
Edit
[One (M9) Original Android Development] platinumthis:
Nevermind this issue is doe to CrDroid i think, the roms sound in Lineage and Acip are fine

sorry for that i just thinked this is due to same build couse i use also Claymores repo. Really annayoing maybe is something buggy in Building cousing this scratchy pitchy sound... thx for all.
[One (M9) Original Android Development] multiwirth:
@Claymore1297 i ran into another issue

[100% 275/275] writing build rules ...
FAILED:
build/make/core/Makefile:49: error: overriding commands for target `out/target/product/hima/vendor/lib64/hw/keystore.msm8994.so', previously defined at build/make/core/base_rules.mk:513
16:14:31 ckati failed with: exit status 1

#### failed to build some targets (55 seconds) ####

patrick@Patrick-Pc:~/android/lineage_himaul$

i'm not sure what causes it since my knowledge is very limited 😅
[One (M9) Original Android Development] Claymore1297:
will see, if I can prepare the device tree to be ready. Will ping you when done! :)
[One (M9) Original Android Development] multiwirth:
oh that would be nice thanks ;)
[One (M9) Original Android Development] rafaelrprudente:
First of all, thank you very much @Claymore1297 for the amazing job keeping m9 alive until these days! I've been using Lineage 17 (Android 10) for months as my daily device without any issues. It's better than official roms!

So I've upgraded to Lineage 18 and it's very nice overall too, but it does have some bugs (screenshots are not allowed in any app, freezes and lagging).

Do you intend to release new versions of this rom, since the last is from december, 2020?
[One (M9) Original Android Development] multiwirth:
Can you provide more infos about this issue?

Screenshots are working fine for me also no laggs in any kind if you don´t play games on it.

Sadly the Snapdragon 810 has heating issues and will throttle aggressively which can cause laggs but usually this will only hapen if you really push the hardware to it´s limits.

Maybe it helps to clean flash the rom if you upgraded from 17.1
[One (M9) Original Android Development] Claymore1297:
Will build probably tomorrow
[One (M9) Original Android Development] bertoteo:
Will the echo problem be fixed on new build?
[One (M9) Original Android Development] Claymore1297:
#### New build is up!! ####

the build is containing mainly the following:

-march ASB's

-minor fixes

-last Lineage fixes

Enjoy!
[One (M9) Original Android Development] Claymore1297:
no, because we cannot reproduce this here :-/
[One (M9) Original Android Development] bertoteo:
But here you said you forgot to merge the fix:
[One (M9) Original Android Development] chris.android:
So with the new build, during the first time setup when setting a screen lock it doesn't allow you to, the only way to get past this is to skip it.

Another major issue as a result of this is after the first reboot, it gets stuck in kind of a restart loop where it boots to the system but instantly restarts. After multiple tries, I found that the only way to solve this is to not set up a screen lock during the first time setup and just skip it. there are no restart loops if this is done.

Another issue I found is that there is kind of an echo with the notification tones, this wasn't present in the previous build.

Apart from that everything seems good, Great work!!
[One (M9) Original Android Development] Claymore1297:
uploaded another build, which should have fixed the issue described above.
[One (M9) Original Android Development] bertoteo:
Is this fixed too?
[One (M9) Original Android Development] chris.android:
Awesome!
[One (M9) Original Android Development] bertoteo:
Android doesn't boot after updating from december build to latest available. After a while stuck with Lineage's logo it automatically reboots in recovery mode ( Twrp 3.4.0.0 )
[One (M9) Original Android Development] Jaodidyouknow:
Hello i just found my m9 and i installed this rom do i really have to update the software on my m9 to 4.x ? im having such trouble looking for the ruu because my phone shows on download mode himawhl 3.41.651.4 i tried to install the ruu to get OTA but i keep getting error messages but on your rom using aida64 it shows i have a himauhl.

Will i run into any problems if i stay at software 3.41? if yes how can i update it?
[One (M9) Original Android Development] Claymore1297:
Yes you will get issues. Please update your firmware. You can check readme thread for instructions
[One (M9) Original Android Development] rafaelrprudente:
Any one else with screenshot issue? I can't take screenshots at all. Message: app or organization doesn't allow screenshots.
[One (M9) Original Android Development] Claymore1297:
Screenshots are working. This is prob. A restriction in you apps.
[One (M9) Original Android Development] rafaelrprudente:
I don't believe so, since i can't take any screenshot, no matter which app is it, even in home screen or config menu. Anyway, I'll install new build and see what happens.
[One (M9) Original Android Development] Claymore1297:
A log would be good then... It is working here
[One (M9) Original Android Development] Pfony:
Hi there,

great to read that there is a new LOS 18.1!!! Thanks again for the very good work of the maintainers (Claymore and Co).

I got 3 questions regarding the new 18.1 built:

1.

can anybody confirm whether the "echo problem during voice calls" is gone? I wrote about that issue before and there were some attempts by merging something into the kernel (reference here)

2.

since there is no offered OTA update possibility from 18.0 to 18.1 would it be possible to just flash the 18.1 rom by TWRP?

If it is necessary to perform a wipe before that and if so can I just keep the "data" partition in order to not installing all apps and user data from scratch (like messengers, calendar events....)

3.

is the very useful feature "color temperature" back?

Thank you for your continuous support of this phone and making so many people happy !!!
[One (M9) Original Android Development] bertoteo:
For my experience about... I can confirm 1) and 2)
[One (M9) Original Android Development] multiwirth:
I´ve built 18.1 myself and i didn´t have issues with calls at all.

OTA isn´t supported on unofficial versions and in my experience i had to do a full wipe from 18.0 to 18.1 otherwise bootloop.

Updating to future 18.1 builds should be fine though.

Color temperature? You mean live display? No it´s still broken in Lineage 18.1 in general.
[One (M9) Original Android Development] rafaelrprudente:
I've just installed latest version and now everything works fine (screenshots, no freezing, no lagging). This time I did a clean install, so I believe isn't recommended dirty flash from LOS 17 (Android 10) to LOS 18 (Android 11).

Thanks to the developer again! Very good work in m9!
[One (M9) Original Android Development] TeMetaies:
Hello and thanks a lot for caring about htc m9! I just flashed my device with it and all works well but the mobile data connection only gets to H+ in a region I normally get 4G/LTE with other Devices with the same SIM-card. I checked all the settings (APN, prefered network...) already but I still cannot connect to LTE. Maybe the phone doesn't support the european LTE-Bands or did I something wrong? The image from claymore does support 4G isn't it?
[One (M9) Original Android Development] multiwirth:
Was LTE working in stock rom or whatever was installed before?

For me it´s working just fine.

I have the gsm model.

Verizon variants won´t support european lte bands
[One (M9) Original Android Development] TeMetaies:
Thanks! So it came out, that the phone has been produced for the north-america market.... So i think everythink is working as it should do...