yashsingh1/xdaforums huggingface dataset:
[One (M9) Original Android Development] sverfaillie:
Look at the first post, there is a special version of twrp needed. I guess it is due to that.

TWRP Recovery (SAR) - https://github.com/CaptainThro...droid_device_htc_hima/releases
[One (M9) Original Android Development] hyperair:
It's not that -- I was on the TWRP Recovery (SAR) version the whole time. 20200605 gapps just didn't work for me.
[One (M9) Original Android Development] Claymore1297:
#### New build is up!! ####

the build is containing mainly the following:

-june ASB's

-minor fixes

-last Lineage fixes

-new calender app etar

-lmkd replace lowmemorykiller

-GPS improvements

You should now be able to update via OTA app.

Enjoy!
[One (M9) Original Android Development] Ebizza:
Do I lose any data if I update via the OTA app?

Only my bottom speaker works now. Can it be fixed?
[One (M9) Original Android Development] sverfaillie:
Update works perfect through ota. Both of my speakers work after ota.
[One (M9) Original Android Development] Ebizza:
Okay. But do I lose all my data?

---------- Post added at 10:03 PM ---------- Previous post was at 09:28 PM ----------

I'm on the latest build (June), but I still have the same issue.. Only my bottom speaker works. And this has been happening since I moved from stock to custom. If I go back to stock, it works fine. Call sound is very low, and I have to put calls on speaker to hear. My callers hear themselves cause the mic is at the bottom speaker. Is there any way I can edit the speaker file or something? Or any app I can use?
[One (M9) Original Android Development] Claymore1297:
Which HTC Firmware,you are using?
[One (M9) Original Android Development] Ebizza:
4.28.401. 3 It's the international (GSM) version I think. What do I do to fix my speaker issue?
[One (M9) Original Android Development] Ebizza:
Would appreciate if anyone can send their mixer_xml file.
[One (M9) Original Android Development] Claymore1297:
mixer_paths.xml of the ROM is this one:

https://github.com/AICP/device_htc_hima/blob/q10.0/configs/audio/mixer_paths.xml
[One (M9) Original Android Development] Locked_Character_#90:
I have an european himauhl version, using this rom and other Lineage OS roms; my interlocutor hears the echo of his voice during calls with me, there is a way to fix? Please
[One (M9) Original Android Development] Ebizza:
I also have the same issue. Unfortunately, all the guides I'm seeing only increases or decreases the volume of my bottom speaker
[One (M9) Original Android Development] shadowalker2014:
I have similar issue also when I first installed Los 15 I had to change my speakers to fix it
[One (M9) Original Android Development] Locked_Character_#90:
What speakers have you used for replacement? From american version? now I have European version.

I think there is also a software fix but for now i can't find anything and i don't have the skills to do it. Thanks anyway to all of you who keep updating this beautiful device!
[One (M9) Original Android Development] Ebizza:
Yeah.. I think it's a software issue.
[One (M9) Original Android Development] tiratored:
I also have an echo, and my daughter has an echo. Phones are the same, himawhl. When I rolled back to previous firmware, the echo disappeared on both devices. I don’t care. But callers are crazy! :)
[One (M9) Original Android Development] Claymore1297:
Which previous firmware?
[One (M9) Original Android Development] tiratored:
For example, stock firmware. Or firmware based on Android 8 or 9. On AIСP, my daughter and I also have an echo.
[One (M9) Original Android Development] Claymore1297:
#### New build is up!! ####

the build is containing mainly the following:

-july ASB's

-minor fixes

-last Lineage fixes

Enjoy!
[One (M9) Original Android Development] UnwindingThree8:
I just installed it for the first time. Thank you for the hard work. Everything seems to work except quick charge for some reason. Is this a known bug?
[One (M9) Original Android Development] UnwindingThree8:
Also can anyone tell me what the most recent compatible gcam (mod) version is or is the one in this build the most recent compatible version?
[One (M9) Original Android Development] weinberk:
At the risk of sounding like a complete newb: Is this hima release compatible with the himawl (Verizon)?

This would need to be 1x-CDMA/3G/LTE compatible on the Verizon network to work for me. I've searched and searched, but don't see any definitive answer. I know that when there were official LOS releases for the M9, hima and himawl were separate. This thread title says hima/himawl which makes me optimistic, but the codebucket repository only has a 17.1 hima folder. Is it a single ROM for both versions?

Thanks.
[One (M9) Original Android Development] Claymore1297:
Yes, it is a unified Rom ;)
[One (M9) Original Android Development] nhdung0209:
Hi admin, does this rom support Sprint?
[One (M9) Original Android Development] Flyhalf205:
How is battery compared to stock?
[One (M9) Original Android Development] Claymore1297:
Well i never used stock, but got after a battery replacement 6 h of sot.
[One (M9) Original Android Development] nuno26coelho:
GPS problem

Hi guys.

Im testing this on my phone but discovered that the GPS is not working. Also i cannot save phone number in the sim card cause it doesn't show anywhere when chossing place to save phone numbers.
[One (M9) Original Android Development] Claymore1297:
Whivh HTC firmware you are using. GPS works here fine
[One (M9) Original Android Development] Flyhalf205:
Speakerphone volume is low on my himawl
[One (M9) Original Android Development] Claymore1297:
so you finally found your device :)

Well speaker have always been on AOSP-based roms a issue on hima, this is due the fact we can't activate DSP-mode on speaker hal.

On most devices the speaker are over powered and sound was very bad. So I added speaker protection on speakers and I also ship

JamesDSP, so you should be able to adjust the speaker volume to the desired level.
[One (M9) Original Android Development] Flyhalf205:
I'll give that a try. It has been a very long time since I've been on XDA. It is nice to see that work has continued on this device.

I did a repo sync and thinking about building again but only using this phone temporary.
[One (M9) Original Android Development] weinberk:
Encryption working? Boot loop

Is encryption working in the latest July build? It's not for me, I got stuck in a boot loop.

I flashed TWRP 3.40, wiped my himawl (Verizon HTC m9) which was previously running an old LOS 15.1 installtion, installed the July build, and restarted. It booted right up. Wifi worked, Cellular worked. After the LOS welcome dialog, I entered a device pin, then I went to settings->security->encryption and did an encrypt phone.

It showed the little green android guy on the black screen for about 1 second, and then restarted. I get the HTC logo for about 15-20 seconds and then it restarts again, back to HTC logo for 15-20 seconds. Boot loops.

I was able to get into TWRP. I wiped data, and restarted, but it still went to the HTC logo boot loop.

Then I tried wiping system and reflashing LOS. No luck, still the HTC logo boot loop.

I also tried doing a factory reset in TWRP, then going to wipe->advanced and repairing system and data (I don't know if that was necessary), then reflashing LOS 17.1, but that hasn't worked either.

I'm now downloading an old stock-ish RUU in the hopes of that getting me out of the bootloop, then going back to LOS 17.1 after a wipe.

I've seen this before with these phones with older LOS versions. Any suggestions or discussion of your experience would be appreciated!!

EDIT: I tried one of [MENTION=531642]santood[/MENTION]'s circa 2018 RUU's. Wiped and installed the Zip from TWRP (which isn't easy to get into during the looping). The boot loop does stop. When installing, in the aroma installer, I told it not to force encryption. The phone boots, I get the verizon logo, then a prompt that the phone's encrypted. I can enter whatever password I want, it says the password is correct but the data is corrupt. It then restarts and the process loops - but there's no boot loop.

I tried wiping that in TWRP and reinstalling LOS17.1, but I get right back to the HTC boot loop. I'm lost...
[One (M9) Original Android Development] idontkn1:
You'll need to format the data partition in TWRP. It's the one that will ask you to type yes after choosing it.
[One (M9) Original Android Development] Claymore1297:
I added a "how to build" into OP, like you did this once ;)

Note, we have now a unified device-tree and a vendor partition. :)
[One (M9) Original Android Development] weinberk:
Encryption Broken? Boot Loop

Thanks [MENTION=2636173]idont[/MENTION]n1. That cleared it up. I did sill need to wipe system and reflash LOS.

[MENTION=1345360]CLAYMORE1[/MENTION]97, I tried again a couple different times without success.. Clean start, wiped everything, reformatted data, installed LOS 17.1 (July). That's all. Nothing else. I selected a pin (several times with a pin longer than 4 digits, once with just 4 numbers = no difference). Once I start encrypting, the black screen with the green android guy flashes up for a second, the phone restarts and it boot loops white background with HTC logo. I've definitely seen this same behavior several times, starting with 15.x I believe. I >>think<< this worked in 14, and then if you wiped system but didn't touch data and installed LOS15, it kept encryption on. It's a been a long time though....

I'm using TWRP 3.40 from twrp.me - Is that the wrong one? Any suggestions / thoughts?

It seems unlikely that I'm the only one who has tried encryption....
[One (M9) Original Android Development] Claymore1297:
in LOS(CM) 14 encryption was broken.

On which HTC firmware you are? You should be on latest (4.x)

Logs would help I think.
[One (M9) Original Android Development] weinberk:
What logs? Do you mean from TWRP -> advanced -> copy log?

I'm on 4.49.605.16 (himawl Verizon from Jan 2018)

TWRP 3.40: I've seen other posts by you talking about needing TWRP SAR version. The 3.40 build right on twrp.me says it is system as root. Should I be using your 3.3.1 https://github.com/CaptainThrowback/android_device_htc_hima/releases/tag/3.3.1-1 instead?

Are there adb commands(or TWRP terminal or a fastboot trick, or other commands) I should try running to completely repartition everything? I've poked around in TWRP and wound up erasing the /vendor FOLDER in the system partition. Shouldn't I have had a vendor partition instead of just a folder? I know this specific phone had issues back in the LOS 14 days, it's had CM13, and probably CM12 on it. I really don't know when it was last partitioned, nor what partition structure you recommend. I assume the LOS installer doesn't repartition.

And thanks for the personalized help. I don't mean to monopolize your time!! Hopefully your suggestions here not only help me, but help others too.
[One (M9) Original Android Development] Claymore1297:
HTC Firmware version is OK I think.No, this ROM has a vendor-partition.

EDIT: twrp version, you are using is OK

EDIT2: I also ended in a bootloop
[One (M9) Original Android Development] weinberk:
Alight, if I go to internal storage, I do see /vendor. If I go to wipe, should the vendor partition be an option? It's not. I don't know if this has to do with anything.

I'm sorry to keep asking, but do we know if encryption works in this build? I just don't know if I've got something wrong/incompatible, am somehow doing something wrong, or if encryption just doesn't work for anyone.
[One (M9) Original Android Development] weinberk:
[MENTION=8276284]Claymore1297[/MENTION] - it stinks that you're getting the bootloop too, but at least I can rest easier that the problem can be reproduced and it's not just silly old me. What's your gut? Is this fixable?

Thank you!
[One (M9) Original Android Development] Claymore1297:
everything is fixable ... but we need to find it ;)

Can you try to encrypt without setting a pin before encryption.
[One (M9) Original Android Development] weinberk:
[MENTION=8276284]Claymore1297[/MENTION], I tried that in one of the tests before. With a pin already set, you need to confirm it, but if it's not set, it makes you set one first. Didn't matter, still boot looped.

I guess there's not demand for encryption if this hasn't been brought up before, and I hate to demand anything ever, but it sure would be nice to have it...
[One (M9) Original Android Development] nuno26coelho:
I finaly manage to install this rom again but i'm having trouble installing the gapps pack. Wich version do you guys recomend?
[One (M9) Original Android Development] nuno26coelho:
Got the android working and the gappk right, but the GPS still not working. Help guys!!
[One (M9) Original Android Development] Claymore1297:
GPS ist Working fine here. Logs please
[One (M9) Original Android Development] nuno26coelho:
logs? what's that?

---------- Post added at 02:11 PM ---------- Previous post was at 01:12 PM ----------

The thing is, when i turn the GPS on, in the upper menu of the sreen, it apears the icon just by the right upper corner as it should be, but when opening the google maps for ex. it cannot find my position. The same in other app that need positioning like for finding gas stations and such. Althoug i believe that it did worked in just one app.

GPS is on and the high precison mode.

Need help here guys.

Cheers. Thanks.
[One (M9) Original Android Development] Aprate:
Thanks for this great rom!

At first i couldn't get lineageos to boot my phone even though it was soff, but my bootloader was still locked(dumb me, thanks [MENTION=3437245]scotty1223[/MENTION] you helped me out).

Thats why i couldn't find any info regarding this and it wouldn't boot past the white htc logo, but all is fine now!
[One (M9) Original Android Development] nuno26coelho:
I tried the 17.0 version of the rom and it seams to work fine, location worked fine as well. But when i flashed the 17.1 back the location continued not working. It does not manage t get a location for any app. What do i do? How do i solve this?

---------- Post added at 10:52 PM ---------- Previous post was at 10:35 PM ----------

Does it have anything to do with the gapps version i'm using? i'm using the 20200229m this seamed to work with the 17.0 rom.
[One (M9) Original Android Development] Claymore1297:
#### New build is up!! ####

the build is containing mainly the following:

-august ASB's

-minor fixes

-last Lineage fixes

Enjoy!
[One (M9) Original Android Development] StraightDroid:
Thank's as always for your time ....
[One (M9) Original Android Development] nuno26coelho:
I will try this, maybe it will solve my location problem. Thanks!
[One (M9) Original Android Development] nuno26coelho:
I sucefully installed the latest build of the 17.1 rom but the location still not working.

Any help here please?
[One (M9) Original Android Development] nuno26coelho:
So the latest build is working fine with the latest version of the gapps.

After some tests i find out that the location by exclusevely GPS is working properly outdoors, but indoors it does not give you your position by WIFI/Google location.

Does anybody knows was happening?~

The Location in my Samsung Galaxy A51 5G indoors works perfect by WIFI...

Thank you all for your work!
[One (M9) Original Android Development] shadowalker2014:
Kudos to [MENTION=274326]clamore[/MENTION] for keeping this legend alive.

Recently, I install lineage os coming from aicp after having drastic performance issue and now after clean installation of Los, am experiencing significant drop in charging speed compare to aicp. I will like to know if there is any workaround for it. Thanks
[One (M9) Original Android Development] shadowalker2014:
Hi, I will like to know if there is any logic reason for aicp charging speed to be faster than Los or if the problem is my device.
[One (M9) Original Android Development] Claymore1297:
#### New build is up!! ####

the build is containing mainly the following:

-september ASB's

-minor fixes

-last Lineage fixes

Enjoy!
[One (M9) Original Android Development] SunEater:
Thankx a lot sir u are the reason that my himaul is alive?? and up to date?.
[One (M9) Original Android Development] SpicyTuron:
A very large thank you for keeping this phone alive! I'm keeping this phone until it dies, and since I have no money to buy a new one. Hahaha.

Thank you so much [MENTION=8276284]Claymore1297[/MENTION], you are my hero.
[One (M9) Original Android Development] ratdude747:
Had an odd issue the other day... pretty sure my phone overheated and cooked the CPU, but I'll mention it here in case I'm missing something.

Started having bootloop issues. TWRP is stable; I used the file manager to pull any data I wanted to the SD card and re-installed.

Now it's rebooting a few minutes after getting to the google setup screen. even if I leave it on the "welcome screen" within a few minutes it reboots... and never makes it to the welcome screen again (have to hard reset and force it to download mode to shut it down).

I do have the latest TWRP, using the latest image and GAPPS. (tried older versions of each, to no avial). If I install without installing GAPPS, it just boot loops without ever giving a meaningful screen.

At least I have a spare M9... too bad I'm in Mexico on a work trip and I left the spare at home. Just my luck :(
[One (M9) Original Android Development] jkrajcir:
OTA update works fine

Hi,

OTA update is OK, everything works fine.

Thank you for your work.
[One (M9) Original Android Development] StraightDroid:
Thanx again für your time. Do you think about a plan for version 18 ? Yes I know that question is early. I ask because of you private time.
[One (M9) Original Android Development] nuno26coelho:
Once more location is not working, with an GPS test APP i can ser that GPS is working and it can get the satelites and show the coordenates. But when i open apps such Google Maps and click on the position button nothing happens.

Can anybody help?

Enviado do meu SM-A516B através do Tapatalk
[One (M9) Original Android Development] nuno26coelho:
Thank you so much [MENTION=8276284]Claymore1297[/MENTION] for your work!
[One (M9) Original Android Development] ratdude747:
Got the phone to run... sorta. Got it to run long enough to complete setup with the SIM card removed, but as soon as I plugged it in, it overheated and back to boot loop city. She's cooked, not likely a ROM issue.
[One (M9) Original Android Development] ratdude747:
Home from mexico, spare M9 does the same thing.

I'm fairly certain it's something with my SDXC card... pulling the card allowed it to run, and re-inserting would cause a bootloop a minute or two later. This card had been hit-and-miss within Lineage anyway; sometimes it would come up as needing reformatted, even though TWRP sees it every time (but would show up as usable if I rebooted once or twice), so I dunno.

Anybody else have weird SDXC behavior?

Edit: Replaced the SDXC card, no more problems. The old card was acting in a similar squirrely way on one of my workstations, so that card is toast (it's a three year old or so Adata 128GB, replaced with an equivalent SanDisk card).
[One (M9) Original Android Development] Claymore1297:
I know, the screenshot is an AICP-build .. but this just means, there will be a lineage-build too sooon.... :)
[One (M9) Original Android Development] Pfony:
short correction to 3.:

it was AICP 13.1
[One (M9) Original Android Development] UnwindingThree8:
I distinctly remembered upon doing this and rooting my m9 that everything was green/succeeded in magisk safety net. Yesterday I saw it failed safety net. No idea when that happened though. Any idea what the problem is? Same with my HTC 10 running LOS 17.1 for that matter.

Edit: EdXposed tripped it but after deleting it again I didn't clear data from play store services and the like which solved it. Sorry still new at all this
[One (M9) Original Android Development] janeku:
Hello .

For service purposes I need to install stock rom.

Where I can find stock rom for M9 (links please) ?

Also after service would I be able to reinstall Lineage OS ?

Regards,
[One (M9) Original Android Development] Pfony:
Boot loop after switching from LOS 17.1 to AICP 16.0 and back

Hi,

PLEASE I need your very urgent assistance:

For testing reasons I switched from LOS 17.1 (built 2020-09-21) to AICP 16.0 (built 2020-11-15) yesterday.

Before I did that I created a backup of my LOS (TWRP 3.4.0-0 and partitions: boot, system, data (excl. storage)).

After installation of AICP 16.0 (just wanted to test if the echo in voice calls is finally history ==> YES :D) I went back into TWRP-recovery and restored my just created backup with no error messages or anything.

So pressed "reboot" but then my phone loops in the "htc" boot screen :(.

I have no encryption or magisk.

I cannot restore my backup but I can install LOS 17.1 (built 2020-09-21) or AICP 16.0 (built 2020-11-15) at any time and it works.

But my attempts to restore my own backup fails.

I very much need your urgent help, because I relied on having the backup and did not backup any of my stuff (e.g. notes, calender events..., messenger history....).

Any idea is very very much appreciated!

Thanks in advance.
[One (M9) Original Android Development] bertoteo:
Mirror cast

Trying to cast screen mirroring on sony android TV 7.0 the phone reboots (lineage 20200921)

Does anyone know how to solve?
[One (M9) Original Android Development] Pfony:
My SOLUTION / Workaround

OK, I have found a workaround for getting my data restored:

I installed the LOS ROM completely as fresh installation (wiped before: boot, system, data (excl. storage)), then went into TWRP recovery and restored ONLY "data" partition from my last backup....and voila I got all my personal data back.

OK I had to re-download stuff like some GPS maps but ALL my important personal data have been restored.

Just wanted to share with you for anybody having experienced the same situation. :angel:
[One (M9) Original Android Development] bertoteo:
Echo in voice calls you mean with the speakerphone?

Going back to LOS the issue persist again or you solved?
[One (M9) Original Android Development] Pfony:
Hello bertoteo,

I switched several times back and forth....but my "workaround" was the only way to get my data back (i.e. restore only "data partition" on a freshly installed LOS).

I wonder if other user experienced the same or can just somebody try:

- to create a backup

- wipe

- install fresh

- (try to) restore their own backup

I have absolutely no idea what is wrong, but it is reproducable and always ended in a boot loop.
[One (M9) Original Android Development] bertoteo:
I meant about the eco problem

---------- Post added at 07:52 PM ---------- Previous post was at 07:48 PM ----------

I meant about the eco problem if you solved
[One (M9) Original Android Development] Pfony:
Hello bertoto,

when switching back to LOS the echo is there again. So it obviously has something to do with the programming in the ROM itself and obviously this has been fixed in AICP 16.0 (built 2020-11-15). I tested with my most annoyed friend and he was so happy not to hear himself as an echo :cool:

My hope is now that it will be fixed in next LOS (Android 11) ROM.

@Claymore1297 : do you have a rough estimation on when the LOS ROM will be released?

Thanks sooo much for all your fantastic work! (y)
[One (M9) Original Android Development] Claymore1297:
Today the first hima-build for LineageOS 18.0 has been released. When I find out, how to create a thread on this new XDA-frameworks, I will do it.

Builds can be found here:

index - powered by h5ai v0.29.2 (https://larsjung.de/h5ai/)

index - powered by h5ai v0.29.2 (https://larsjung.de/h5ai/)

mirror.codebucket.de

You will need a clean flash.

Enjoy!
[One (M9) Original Android Development] Claymore1297:
link to LineageOS 18.0 thread:

https://xdaforums.com/t/rom-11-0-0-himaul-himawl-lineageos-18-0-unofficial.4199175/
[One (M9) Original Android Development] Selocan20:
Hey there,

I‘ve problems with Battery after flashing to lineageOs 17.1 or 18.

Both Versions with same problem.

yesterday Night 43% Battery. Today in the Morning Battery was empty.

Do you have any Solutions for this issue?

on Stock Rom there wasn‘t any Problems wirh Battery like that