[ROM][HIAEUHL/HIAEUL] Unofficial LineageOS 14.1 (2020/05/30)

Saad. Mk

Senior Member
Jun 26, 2017
128
32
28
Did you try to install Ainur Sauron and Audio Modification Library after installing V4A?
I did indeed and now it works perfectly however I can't find a profile thats loud and does not distort the speakers since 90% of the times I can't hear my notifications
 

onlime1

Member
Mar 3, 2019
34
8
0
Kayseri
I did indeed and now it works perfectly however I can't find a profile thats loud and does not distort the speakers since 90% of the times I can't hear my notifications
My phone is always silent so I can't hear notifications too l:p . I use Speaker Optimization, V style EQ and extra loud settings for listening music from the speaker (and the earpiece for that stereo effect mod thing) and its loud and does not distort that much. Lots better than stock settings I think.
 

Saad. Mk

Senior Member
Jun 26, 2017
128
32
28
My phone is always silent so I can't hear notifications too l:p . I use Speaker Optimization, V style EQ and extra loud settings for listening music from the speaker (and the earpiece for that stereo effect mod thing) and its loud and does not distort that much. Lots better than stock settings I think.
Screenshots would help, PM?
 

The_Walking_Playground

Senior Member
Nov 30, 2017
652
345
63
Hi,

I don't know if anyone is interested in running this ROM while encrypted, but I believe @Captain_Throwback has been working on supporting decryption in TWRP for all of his old HTC devices, so maybe someone can join his Slack testing group and help him get it working? I recall he made a few attempts and failed, but he seems to be in a groove right now, as support for several devices using native TWRP decryption have been added (for Pie, but it seemed to also work on Lineage 14.1). This is a link to the Slack, if people are willing to help: https://join.slack.com/t/twrptestin...FjYjg1ZjAzZGU2Njg3NTFiNjgxZDNhYjNhNTIwNmI3YWI

TWP
 

Saad. Mk

Senior Member
Jun 26, 2017
128
32
28
hello everyone,
how can i understand what is build correct for my one a9? (16gb 2gb ram) "HIAEUHL/HIAEUL"
thanks in advance
Depends on which device you have you can either check the build info in settings and wether if it says hiaeuhl or hiaeul OR boot the phone in bootloader (power + vol down) and on the top you should see some text ending in uhl or ul.
 

Dragonkind

Senior Member
Aug 4, 2012
699
346
93
Chureki
Any news for Lineage 16? Nightlies are available for other devices so is that means intervigil will build LOS16 for our device?
Not yet. Till the dialer bug solved or we won't get LOS 16.0 I think.
The bug is considered as an issue caused by registration of phone status between device and carrier.

Btw, if there's Android security patch 2019-03-05 with Android Webview 72.0.3626.121 uploaded to gerrit,
I'd like to make a bonus build to ensure privacy security.
Another reason, a long-term existed bug had been fixed some days ago.
 

onlime1

Member
Mar 3, 2019
34
8
0
Kayseri
Not yet. Till the dialer bug solved or we won't get LOS 16.0 I think.
The bug is considered as an issue caused by registration of phone status between device and carrier.

Btw, if there's Android security patch 2019-03-05 with Android Webview 72.0.3626.121 uploaded to gerrit,
I'd like to make a bonus build to ensure privacy security.
Another reason, a long-term existed bug had been fixed some days ago.
Thank you for keeping our A9's updated. And about that dialer bug when I was using LOS15.1 , some reboots doesn't have that bug. I was able to hang up the calls and receive SMS's but after another reboot problem occurs again. I think it's not from the RIL. Maybe building LOS16 from zero will not have that bug. Just thinking :confused:
 

Dragonkind

Senior Member
Aug 4, 2012
699
346
93
Chureki
Thank you for keeping our A9's updated. And about that dialer bug when I was using LOS15.1 , some reboots doesn't have that bug. I was able to hang up the calls and receive SMS's but after another reboot problem occurs again. I think it's not from the RIL. Maybe building LOS16 from zero will not have that bug. Just thinking :confused:
I know what you mentioned, so I had guessed it a memory leakage issue.
But after observing more, I found it was related to a certain random error about communicating with carrier end.
I could receive SMS (not sure about sending SMS) and dial out to somebody, but couldn't hang up calls by myself or receive phone calls from others.
Intervigil also got the same surmise noted in his unmerged gerrit for A9.
In fact many firmware got reserved since LOS 13, 14.1 and 15.1, so would 16.0. (ex: mixer_path_wcd9330.xml)
It needs some critical debugging for the compatibility when our A9 upgraded from Nougat.

If I try fixing it by myself, it will mean I have to stop building 14.1, cuz my SSD doesn't have enough space for building two different ROMs at the same time.
Thus it should be started after I understanding how to solve major bugs, or else, I would just keep with 14.1.
 

SB00

Member
Mar 24, 2019
5
0
0
Thank you for keeping this updated. I had to revert back to my A9 and was worried I wouldn't have the latest security patches. :good:
 

kall3

Senior Member
Oct 21, 2015
64
27
0
(...)
If I try fixing it by myself, it will mean I have to stop building 14.1, cuz my SSD doesn't have enough space for building two different ROMs at the same time.
Thus it should be started after I understanding how to solve major bugs, or else, I would just keep with 14.1.
Have you already decided which development branch you will follow? For me LOS 14.1 with bugfixes is sufficient ;)
 

Dragonkind

Senior Member
Aug 4, 2012
699
346
93
Chureki
Have you already decided which development branch you will follow? For me LOS 14.1 with bugfixes is sufficient ;)
Currently I would keep maintaining 14.1, coz A9 is my only phone and I need it more stable.

If I have IQ 200 to figure out the way to solve the major bugs of 15.1/16.0, I'll prefer to build with 15.1.
I'm not sure how far to get 16.0 for daily use, but I know 15.1 is all fine except the phone call function.
As an old model, it's better to be stable than exciting. :highfive:
 

The_Walking_Playground

Senior Member
Nov 30, 2017
652
345
63
Hi,

I don't know if anyone is interested in running this ROM while encrypted, but I believe @Captain_Throwback has been working on supporting decryption in TWRP for all of his old HTC devices, so maybe someone can join his Slack testing group and help him get it working? I recall he made a few attempts and failed, but he seems to be in a groove right now, as support for several devices using native TWRP decryption have been added (for Pie, but it seemed to also work on Lineage 14.1). This is a link to the Slack, if people are willing to help: https://join.slack.com/t/twrptestin...FjYjg1ZjAzZGU2Njg3NTFiNjgxZDNhYjNhNTIwNmI3YWI

TWP
Hi,

There appears to be some good news on this front: https://mobile.twitter.com/Cpt_Throwback/status/1121625281586794497

Maybe someone can try it out and confirm decryption is working?

TWP
 

RRMex

New member
Jul 22, 2014
1
0
0
Ayuda, por favor

Mi htca9 quedó brickeado y por más que trato de regresarlo con el último rom que servía (una versió nigthly de 2017) ya no pasa del logo htc
 

Dragonkind

Senior Member
Aug 4, 2012
699
346
93
Chureki
Mi htca9 quedó brickeado y por más que trato de regresarlo con el último rom que servía (una versió nigthly de 2017) ya no pasa del logo htc
I have no idea about Spanish, but I use Google Translate and guess something from your reply.
Your phone got stucked at the boot screen with HTC logo, and you were using a LineageOS 14.1 ROM released in 2017, right?
You can try to flash your phone with the latest firmware or a whole RUU. (ex: Spanish ver, European ver or any customized versions by your carrier)
And see if it works. Check in this thread first.
If it's still dead, you can gotta pick a new phone this weekend. :p
 
  • Like
Reactions: creisey

creisey

Member
Jan 30, 2012
23
7
0
josi.as
thanks for the great build, i have tried several roms the stock as well as some modded but they all kinda sucked.

this is fast and stable, but i have somtimes a bug:

when the device sleeps (black screen) i cannot unlock it with the fingerprint i then have first to wake it up via powerbutton and after that the finger sensor works. is there a solution for this?

there's another one MTP is not working sometimes, only if i change in the developper options USB to battery loading and back to MTP.

after one unplug the problem is back
 
Last edited:
  • Like
Reactions: Dragonkind