yashsingh1/xdaforums huggingface dataset:
[HTC One A9] Ultramanoid:
Funnily enough my paid camera application doesn't work ( see the green blob I posted in the thread before ) nor do many others, but the two open source I also mentioned do work fine, FreeDCam and OpenCamera, and both have threads in XDA.
[HTC One A9] roomwithoutwalls:
Hello,

I'm a fairly new user, so please have some mercy on me.

I flashed CM13 a couple of weeks ago on my A9. Everything worked fine. Clean-Flashed CM14 yesterday and so far everything works fine as well, except mobile data/SIM. There's literally no mobile data connection and barely any connection at all. I'm allowed to receive SMS from time to time, but doing phone calls is impossible. Tried every previously suggested bugfix and nothing worked for me. Kinda sucks.

Carrier is o2/1&1 (Germany) (if that matters for any reason).

Thanks in advance

UPDATE:

So I basically tried flashing the boot update image a second time after reinstalling CM14 and it worked. Not sure what I missed the first time, but whatever. Yet I have to put up Plane Mode at least once everytime I reboot the phone, bit annoying but a way to get around. Then I had the strange problem of not seeing in -or outgoing calls. Fixed that by selecting Google Phone as default dialer und turned up all notifications for it. Strange this hasn't been done by default, but better mention it, if anyone else encounters this bug.

Google Camera is not working as well. Had to install the Snap.apk The_scam uploaded (Thanks!).
[HTC One A9] eliah94:
Will try this out. Is it enough to deactivate the google camera? Or how can I completely uninstall it?

Update:

Managed to uninstall the Google camera via adb.

However, flashing the latest nightly didn't install the camera app. Now I tried to install it from Cyan Apps, but it crashes right away.
[HTC One A9] The_scam:
try using this: http://www.mediafire.com/?3ztw314l4n9i3db
[HTC One A9] Ultramanoid:
Something went wrong flashing because Snap camera is part of the CM 14 nightly installation. There's no reason why that application would not be installed while all the rest do. I'd make a backup and try a clean flash to double check.
[HTC One A9] eliah94:
This works flawless. Awesome, thanks!
[HTC One A9] Xtaner:
Hey!

I've got exactly the same problem with Carrier Telekom (Germany) too.

I can only establish a LTE Connection if I install CM14 twice. But anyway I can't install nightly updates.

Every time I install a new Nigthly, the phone looses LTE connection again and I can't reestablish the LTE connection.
[HTC One A9] nhanbui.white:
did build 24/12 bug fix camera issue, and could use 3rd app camera?
[HTC One A9] Ultramanoid:
I see the same problems with many cameras on the latest ( last ? ) build of CM 14. Green blobs except with FreeDCam and OpenCamera, which do not have problems.

Work on the Hiae for LineageOS is already in progress ! (๑˃̵ᴗ˂̵)و

https://github.com/LineageOS/android_device_htc_hiae-common
[HTC One A9] scott8281:
Wow this is awesome. So glad to hear CM will live.. albeit under another name.
[HTC One A9] loner.:
CM will live albeit under another name?

Sent from my HTC One A9
[HTC One A9] scott8281:
Yes.

LineageOS: "Yes, this is us."

https://www.reddit.com/r/cyanogenmod/comments/5k723j/lineageos_yes_this_is_us/
[HTC One A9] Ultramanoid:
I was thinking we were in for a dry jump of several weeks, possibly even months, but looks like they intend to start nightlies ( more like weeklies now, apparently ) pretty soon.

It's probably going to be messy, with those first Lineage builds. If nothing else because all of the re-naming of things.

Jenkins is also still building, the CM December 25th build came out just fine, so keep getting those while you can, just a few days until they shut that one down.
[HTC One A9] scott8281:
Is anyone running 12/25 ? I plugged phone up at 39% and it's telling me it's charging rapidly and it will be 3 hours before fully charged.
[HTC One A9] loner.:
I am still hoping that CM, or LOS makes encryption a option, not the forced encryption that is on this OS now.

Sent from my HTC One A9
[HTC One A9] Ultramanoid:
I am, but this 'charging rapidly' has been showing up for a few builds now. It is not charging rapidly though, just says so. Shows up at random.

Edit : To be clear, I'm not saying rapid charging doesn't work. I'm saying I don't have a quick charger, yet I get the message anyway, but charging goes as slow as usual.

Other devices have it enforced too, and people make patchers as well, doesn't look like once decided to enforce it, the developers have ever gone back.

At least TWRP for those devices can handle the encryption, as it does with the hTC 10 for instance. That would be the best solution obviously, have encryption AND a working recovery to go with it.
[HTC One A9] loner.:
Twrp can't handle encryption on my One A9 either.

Sent from my HTC One A9
[HTC One A9] The_scam:
Well, if you are using a Samsung fastcharger, the oem one, or anything supporting quickcharge 2.0... it will still be "rapidly chaging", just not as a fast as qc 3.0
[HTC One A9] Ultramanoid:
Actually most of the time I'm using a charger from SONY ( because I have mostly SONY devices, and also because it's smaller than any other to carry around ); not a quick charger as far as I know.

Also the 'charging rapidly' message shows at random. Sometimes it does, sometimes it doesn't, always with the same charger. It started a few builds back, but I can't say exactly when.
[HTC One A9] nhanbui.white:
i am used cm 14.1 on my device (cid 621) S-on international, how can i return to custom. Can i relockbloader, download any ruu.zip rom cid 621 and flash by recovery?
[HTC One A9] loner.:
Cyanogen will not even try and polish the nightly's up any before they leave?

Sent from my HTC One A9
[HTC One A9] MGfusion:
Nope,it's all shut down
[HTC One A9] Ultramanoid:
To clear things up; Cyanogen ( Steve Kondik, original developer ) left Cyanogen ( the company ) recently, and explained that the company would likely keep the intellectual property ( which includes the name, ironically... ) and I mentioned it in this thread before, he hoped or thought developers would have a couple of months to figure out what to do with CM open source code as a project. The code is not owned by the company, luckily.

Cyanogen ( the company ) shut down everything, and not on December 31st as they had announced, but suddenly.

Cyanogen ( Kondik ) and most CM developers, made a "fork" of the code, which is open source, rebranded as Lineage, and are setting things up to continue work, as we speak. There is nothing they could do as "Cyanogen" anymore, that name is owned by the company and they shut down everything, etc.
[HTC One A9] scott8281:
Here's an update

http://lineageos.org/Infrastructure-Status-and-Official-Builds/
[HTC One A9] loner.:
Like a lot of others, I read all this in the same blogs you obviously read. Just because of the main players in Cyanogen disagree doesn't mean that they shouldn't have enough pride in their work up to this date not to finish with a product in good working order. It doesn't appear they stopped by a specified date, its more like they just abandoned the project.
[HTC One A9] Ultramanoid:
This is rather off-topic, but seems you didn't quite understand what happened; in short, developers could not use the name anymore, or the servers, or anything, nothing has been abandoned, in fact everything that matters ( the code and work done by developers ) has been saved, the infrastructure has been shut down by the company and despite the developers' ongoing efforts, a substitute is not yet in place. It costs time and money, particularly for such a large project.

The company is an empty dead husk that keeps property of the name and mascot, what will it do from now on is anybody's guess. Cyanogen ( Kondik ), the developers, and the code for applications and roms is now Lineage.

If you want to build a CM 14.1 rom for your Hiae you can do it right now, and polish it as much as you want. The code is available for you or anyone who wants to do so. It will take you time, resources, and work, but no one stops you from doing it. Or you can wait for the first Lineage rom which will be exactly the same, only the names will change.

May as well mention that the company was well funded and paying salaries and now the developers are setting Lineage up from scratch. Have you donated money or resources ? I certainly did, even before CyanogenMod had a company behind it.

Also to note, they did release a final stable version of CM 13. 14.1 was and still is in development. And nightlies ( provided for free by CM directly or developers also freely using their code to build themselves ) are unstable, not production level software, people use them at their own risk.

Edit : May as well add, that in Western countries and the U.S. in particular where most of this is happening, this is a time full of festivities and holidays, not exactly the best for working on setting up a massive project serving millions of users for free. Tone down the entitlement attitude a bit.
[HTC One A9] loner.:
I totally understand and it is a bit off topic as you say. It does seem the project was abandoned to me, you call it the way you want.

By the way why do you say I have entitlement attitude? You don't know me at all or what I donated to the project! Do you just like to sit behind you keyboard and shoot people down and say they have a entitlement attitude if their opinion is not yours?
[HTC One A9] Ultramanoid:
I know only what you post, which is clear.

You did understand that LineageOS code is CM code, exactly the same, even branches keeping the cm prefix which they will until there is a new version of Android ?

It doesn't seem like it, when you say it's been abandoned. How has it been abandoned ? Can't you access GitHub and see it there even now, going on ? Didn't you see Gerritt and Jenkins working until the very second the company changed the DNS and blocked it all ? Wasn't it building until the 25th ?

Because there sure were CM builds for all devices until the 25th, the day the company shut it down. How is that abandoning anything. You think the infrastructure could be duplicated in 24 hours to make Lineage available the 26th and because it's not, it has been abandoned ?

Edit : Maybe the confusion comes from the name of the company, and thinking the company made CyanogenMod. The company had money, intellectual property, and paid salaries. The open source code and the developers are what made CyanogenMod, and what is Lineage, now.
[HTC One A9] loner.:
That sounds a bit OCD.

But yes I know that CM does not own the open code. I also know this is off topic so if you want to continue your rant maybe you should take it to a CM blog if they are any still up.
[HTC One A9] Ultramanoid:
Clearly your confusion comes from the fact that the original developer, the company, and the product all have 'Cyanogen' in their names, being different things.
[HTC One A9] loner.:
No confusion here. You need to move on.
[HTC One A9] Ultramanoid:
Talk about assumptions... I'm not sitting, but pretty far from home and office because of work. Haven't used a keyboard in days.

But yes, time to move on.
[HTC One A9] bjo81:
I have a One A9 since three days and installed CM 14.1 on it. The first evening all went fine, but since yesterday it is unable to use mobile data. The status of the SIM says 4G or 3G and "trying to connect", but it can't get a connection. I've tested the SIM in my gf's Nexus 5x and it entered 4G immediately, so it's no issue with the SIM.

I'm really confused, did the 3G/4G modem broke after one day?

Restarting the phone several times and flashing the build of 25.12. again did not help.
[HTC One A9] Ultramanoid:
Please search the thread before asking. ( It's actually an XDA rule. )

It has been reported that encryption interferes with the modem in some devices. There's a boot patcher to prevent encryption.

It has been also reported that it affects German carriers in particular, are you in Germany ?
[HTC One A9] bjo81:
I'm really really sorry that I haven't searched the thread for the mobile data issue before.. I'm in Germany and use o2 as carrier.

A solution of another user was disabling the "startup protection" which is related to the screen lock. After disabling it (still having PIN enabled), the issue seems to be gone - without boot patcher.
[HTC One A9] :
Lineage 14.1 Custom Build

Hi [MENTION=535343]all[/MENTION]

First i want to wish everyone a good start into 2017 :)

Since i can't wait for Official Unofficial Builds :D, i have built Lineage for hiaeuhl by myself, everything is working so far (Same Probs like the last CM Version).

Here is the Link:

lineage-14.1-20161231-UNOFFICIAL-hiaeuhl.zip

https://drive.google.com/file/d/0B2sX5OM4VzJXTmJ5ak91QWFGVmM/view

I hope that it's ok when i post it in this old CM Thread, i don't want to open a new Thread only for this. :)
[HTC One A9] :
Now i am building Lineage for hiaeul. But before i share it here i want to know if it's dangerous that i use the files (With device/htc/hiaeul/extract-files.sh) from the hiaeuhl build ? Since the cm download server lokks like it's dead i haven't got a copy of the latest cm-14.1 hiaeul build to extract these files.

Like i said, i only want to know if it can harm the US Phones in any way or if the files are compatible.
[HTC One A9] Ultramanoid:
The_scam, would you consider changing the thread title to LineageOS ? It's still 14.1, that hasn't changed, but all the builds from now own are going to be Lineage for sure.
[HTC One A9] nhanbui.white:
Does it work with 3rd camera app suck as messenger or camera 360?
[HTC One A9] JS.zip:
here's a copy of the last cm- 14.1/hiaeul. https://drive.google.com/file/d/0B17SUqP44loIWFNLSHBFdmNycm8/view?usp=drivesdk. Thanks for trying to build.
[HTC One A9] :
If it has been working with the 25/12 build of cyanogen the chances are good that it's still working, Facebook Messenger isn't working (Crashes when i click on the Camera button).

Like i said should have the same problems like the last cyanogenmod build.

[MENTION=7906730]JS.zip[/MENTION]

Thanks for the Link, it's building right now, i will upload it later when i wake up :)

So i wish everyone a happy new year, much fun, health, luck and peace :fingers-crossed::highfive::victory:
[HTC One A9] The_scam:
Sorry for the delay, changing now...
[HTC One A9] :
Lienage 14.1 hiaeul

Hi [MENTION=535343]all[/MENTION]

Happy New Year :)

I have built Lineage for hiaeul, but can't tell if it work, because i have no One A9 US. If someone will try it here is the Link:

lineage-14.1-20170101-UNOFFICIAL-hiaeul.zip

https://drive.google.com/file/d/0B2sX5OM4VzJXSFdKMEtqS0dfdXM/view?invite=COD1i9oM&ts=5868d973
[HTC One A9] ps3hacker3:
Can confirm this working as of right now
[HTC One A9] Ultramanoid:
That build was a good start into the year, thank you. ツ

( As you said, same bugs, some Lineage renaming, and mostly working as before. )
[HTC One A9] scott8281:
I'm not sure what all you need from the build. I noticed that someone posted the 12/25 build but I also have the 12/24 build. It was more stable. I had an issue with 12/25 but now I can't remember what the problem was. In any case if you need it just let me know and I'd be glad to upload it to my google drive for you.
[HTC One A9] :
Thank you for the offer, but i don't think it would made a difference, since it only extracts the binary blobs and they should be the same in every build.
[HTC One A9] loner.:
Unofficial nightlys.

https://xdaforums.com/showthread.php?t=3528558

https://www.androidfilehost.com/?w=...iles&sort_by=upload_date&sort_dir=DESC&page=1
[HTC One A9] loner.:
I don't think anyone has offered to maintain the LineageOS for this device yet.

I hope they find someone soon.
[HTC One A9] Ultramanoid:
This device luckily has a maintainer, as opposed to many others that don't ( looking at sadly neglected SONY, for instance... ); Ethan Chen ( intervirgil ) is the main developer for it, same as it was with CM.

Seriously, check Gerrit or GitHub some time and see the work, this is a developers' forum, after all.

(っ´▽`)っ

The servers to deliver official builds are not in place though, which is a different issue. Code development is ongoing, from which aries2747 has been building and posting here.
[HTC One A9] mlecho:
Has anyone else had video issues with 14.1. Currently, i'm running cm-14.1-20161225-NIGHTLY-hiaeul from the nightlies and all is good except for taking video w/ the cm stock camera. The video frames skip. Infact, on playback, i can hear the audible "ding" when the button was tapped to start recording. Then it's super jumpy. Audio is fine.....thoughts ?

And i did read / search the thread. The only issue i had similar was the greenblobs when using OpenCamera. I really like the CM camera and would love to solve this issue. Perhaps Lineage will?
[HTC One A9] Wegig:
Just flash cm 14.1 nightly build & openGapps stock on my htc one a9. But google camera FC, i try install other camera like htc camera is FC too. Can anyone help me please??
[HTC One A9] Ultramanoid:
Camera support on Lineage ( also CM 14.1, same code ) is not up to the level it was on CM 13. The Snap camera that installs with the rom by default should work. Other cameras may not.

I posted several times before, the open source cameras Open Camera and FreeDCam work for me, tweaking settings; sometimes with Cam 1 API support, sometimes with Cam 2 API.
[HTC One A9] mlecho:
Snap Camera takes stills and pano fine....it's the video that is choppy. Open Camera images are all green with a corner that is as expected. I'll try FreeDCam, but it appears this choppy effect is true w/ any camera
[HTC One A9] Ultramanoid:
I don't use or have Snap installed, can't comment on that. The other two work for me, both video and stills, however they crash often and like I said, sometimes one has to change API to make it work. Video works definitely better for me on FreeDCam. Hopefully with new blobs from hTC things will improve eventually.
[HTC One A9] mlecho:
can you explain that? "change API"

blobs?
[HTC One A9] Ultramanoid:
In those two camera applications you can switch ( in settings ) from the old deprecated ( but still functional ) original camera API to the new camera2 API. See which one works best for you. In theory we should be using camera2 API, but most camera applications still use the old one.

Blobs are the proprietary chunks of code ( as opposed to the open source code from AOSP ) from vendors ( such as hTC ) that get released when a new Android version comes out, camera drivers and things like that are usually proprietary. I'm guessing ( haven't had time to look into it in detail honestly ) the camera stuff we have is not up to date to use in Android 7.
[HTC One A9] intervigil:
HTC's camera libraries seem to be exporting an N-incompatible set of stream formats for the front camera. I don't think this will be easily addressable without an N release from HTC. The camera HAL that we have from M appears to be HAL version 3, but even running the front camera in HAL 1 mode does not work correctly. The current setup is the only way I managed to get the front camera to capture pictures and video, but it seems to only work with Snap (and several other third party apps I have not tested). I have patches that make the front camera more usable with apps (hangouts, FB messenger, google camera work in my testing) but result in the inability to capture video. I'm not sure if that's better or not.
[HTC One A9] mlecho:
So it's the ROM....it appears all camera apps are doing this on my device.... here is an example of the result: https://www.youtube.com/watch?v=1UqBHZjiwOg&feature=youtu.be

just to be clear, i'm the only one? i've tried reformat/reflash as well (several times)
[HTC One A9] Ultramanoid:
Read the post right before yours, from this device's Lineage maintainer. It explains the situation regarding camera related development at present.

I believe N has been released by hTC for the 10 already, presumably the A9 should get it in short.

Edit : The 1.36.2 version of Open Camera, just released, on camera1 API, records video fine. I just tested. This is with the last Lineage build posted in this thread.
[HTC One A9] mlecho:
i think i found my disconnect...how do i "enable" camera1 to take advantage of Open Camera?

---------- Post added at 02:48 AM ---------- Previous post was at 02:35 AM ----------

NM.... Found it but still chippy
[HTC One A9] bjo81:
I've tried to build the actual version of LineageOS, but it fails while brunching:

Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/home/bjo/android/system/out/target/product/hiaeuhl/obj_arm/SHARED_LIBRARIES/libtime_genoff_intermediates/export_includes', needed by '/home/bjo/android/system/out/target/product/hiaeuhl/obj_arm/SHARED_LIBRARIES/libandroid_servers_intermediates/import_includes', missing and no known rule to make it
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed

I've sourced envsetup and breakfasted before, OS is Debian 8.6.
[HTC One A9] :
Have you extracted the binary blobs from a previous build ?

croot

cd devices/htc/hiaeuhl

./extract-files.sh (Without a folder it tries to get the blobs per Usb from your Smartphone, when you mounted an image from Cyanogen or Lineage you have to mount it to a directory named system and then use the path to extract it [like, mounted to /home/user/system, then the command is ./extract-files.sh /home/user, the script automatically looks in the system folder in that directory]).

After that you can begin the build with brunch hiaeuhl.
[HTC One A9] loner.:
Has LineageOS nightlys started yet?
[HTC One A9] Ultramanoid:
Not yet, we can check here :

http://status.lineageos.org/
[HTC One A9] bjo81:
Thanks for the hint with extracting the blobs from an image. I was trying to build it in a VM in a DC, so no chance of connecting the smartphone to it ;)

I hope I'll get the build process working, the last time I've build CM on my own was LegaxyXperia a long time ago.
[HTC One A9] The_scam:
I changed the thread name, sorry it took so long. Thought I changed it ?
[HTC One A9] mlecho:
we are getting closer....

https://download.lineageos.org/
[HTC One A9] loner.:
I hope someday soon that Android users can update to the latest security patches as they come out.
[HTC One A9] :
I will be posting builds as often as I can for hiaeul.

https://drive.google.com/open?id=0B73K4KsF6hfeTnFuU1J2ZlgtbjA

I also have the proprietary files if anyone cant seem to extract them from an old nightly or the device (or if you just want to be lazy)
[HTC One A9] :
https://xdaforums.com/showpost.php?p=69988232&postcount=79

In this Post i have described how to get the files from an older build (like the last cm14.1 build), it's a bit tricky but once you have converted the image you can use it any time later again (If needed) until new binary blobs will be provided (Think when the A9 becomes nougat then the devs will extract new blobs from there to provide better functionality).
[HTC One A9] :
I said I was having trouble silly. I figured it out after a while. :P
[HTC One A9] scott8281:
Thanks man. Flashed it tonight and all is well on my Att A9
[HTC One A9] nhanbui.white:
When will u finish this build for hiaeuhl, i am very expected a build which work perfectly on camera app (video) and 3rd camera apps
[HTC One A9] Ultramanoid:
mlecho is not the maintainer or developer for the A9, nor is he making builds for users.

And about the camera, you'll have to wait until blobs from hTC's N release for the A9 make it into Lineage code, as explained in the thread previously.
[HTC One A9] mlecho:
How about the video from your camera? (https://xdaforums.com/showpost.php?p=70396116&postcount=251). Given Ultramanoid's point about blobs for A9 nougat not yet available, can i safely assume the video is choppy for this build as well?
[HTC One A9] :
I don't have any issue with the latest builds. I use open camera. It does crash when switching between video and camera but other than that it seems to be fine.