LineageOS | Discussion : Support

Ultramanoid

Senior Member
Apr 24, 2011
3,368
4,758
263
日本
Lineage is site doesn't even list a9
Will say it again ( repeating from Lineage itself ), a batch of 80 devices out of 130 get the first Lineage build. Neither A9 models are in this initial batch. ( Nor the flagship hTC 10 for that matter, or many others. ) Plus there are issues with hTC's ongoing N release to be solved, to merge those releases into Lineage.
 
  • Like
Reactions: The_scam
G

GuestK00271

Guest
You won't see any builds for 14.1 until HTC has released N kernel source code and I've had some time to rebase on top of it. The current state of the camera is just too unstable to justify a release.
That's what i thought :) I only wanted to tell that our Phone is on the official list for supported devices, hope it won't take too long till htc release the source :)

I am still waiting for the Nougat Update for the International Version hiaeuhl :) Hope this won't take too long, too :)

But i have a few questions, too.
For hiaeuhl, when the kernel source from htc is published for hiaeul, could it work for hiaeuhl, too, or do you need the sources for hiaeuhl seperatly ? (Or are the two Versions compatible so you need only one source ? )
Same question for the binary blobs (Are they equal on both or different so that both sources are needed ?)
 

intervigil

Senior Member
Jun 5, 2009
347
1,309
0
Bay Area
That's what i thought :) I only wanted to tell that our Phone is on the official list for supported devices, hope it won't take too long till htc release the source :)

I am still waiting for the Nougat Update for the International Version hiaeuhl :) Hope this won't take too long, too :)

But i have a few questions, too.
For hiaeuhl, when the kernel source from htc is published for hiaeul, could it work for hiaeuhl, too, or do you need the sources for hiaeuhl seperatly ? (Or are the two Versions compatible so you need only one source ? )
Same question for the binary blobs (Are they equal on both or different so that both sources are needed ?)
Right now hiaeul and hiaeuhl (in relation to Lineage, HTC's code is very likely different) share the same kernel and proprietary files. The difference is in the non-HLOS part (firmware, bootloader, modem).
 
Last edited:

The_scam

Senior Member
Jun 27, 2016
270
82
0
Tucson
Yo, I got Android pay working on CyanogenMod (latest 12/25/16 build) just disable built in root, and flash magisk and use phhs superuser. Make sure to turn on magisk hide in magisk settings
 

Ultramanoid

Senior Member
Apr 24, 2011
3,368
4,758
263
日本
Looks like HTC hasn't released the kernel source yet. Unfortunately until that happens the few 14.1 builds that have been compiled are as good as it gets.

http://www.htcdev.com/devcenter/downloads
Hope it doesn't take too long, but there have been issues with hTC rolling out Nougat itself, never mind the kernel source.

Wish there was at least a build this week with camera as it is, if only because the February security update is already live for some devices, which worries me way more than having a less than perfect quality for photos.

I wouldn't recommend at all using old CM builds from back in December, that's already two security updates behind.
 

BigDiqSeitz

Member
Dec 15, 2016
20
0
0
I have installed the lineage 17.1.2017 on my hiaeuhl and my sound with the speakers sounds too strong and my sound with my headphones is a bit quiet?
Can somebody help me ???
 

Ultramanoid

Senior Member
Apr 24, 2011
3,368
4,758
263
日本
  • Like
Reactions: BigDiqSeitz

kr1shna

Senior Member
Dec 24, 2012
96
16
0
Kearny
You have to install root explorer and delete /system/lib/hw/audio_amplifier.msm8952.so and /system/lib64/hw/audio_amplifier.msm8952.so to get rid of the headphone problem.
 

Ultramanoid

Senior Member
Apr 24, 2011
3,368
4,758
263
日本
You have to install root explorer and delete /system/lib/hw/audio_amplifier.msm8952.so and /system/lib64/hw/audio_amplifier.msm8952.so to get rid of the headphone problem.
That was for old versions. Read through the thread and you'll see that was fixed and merged a while ago.