yashsingh1/xdaforums huggingface dataset:
[One (M9) Original Android Development] Kirat_XDA:
Camere 2 Api won't work

I couldn't get camera 2 api to work, tried magisk modules, flashing camera 2 zips in twrp, modifying build prop nothing worked. Please help me figure this out
[One (M9) Original Android Development] Max litcher:
Cam2api can't and won't run on the HTC m9
[One (M9) Original Android Development] Kirat_XDA:
I have actually used Google camera on Leedroid Port Rom for M9 (Nougat). I enabled camera 2 api using magisk module. Is this a rom related thing?
[One (M9) Original Android Development] Max litcher:
Yes you can say that because I already asked for this at the beginning of the forum and one of the developers told me that it's nearly impossible to get it
[One (M9) Original Android Development] chayxe:
I have a bad battery, yet to replace it

And I used to get random shutdowns.........a full charge 100% could just run down to 85% and the phone goes off

So I decided to turn of the Big Cores completely using the HotPlug codes in the thermal Config.

After I did that, I got a good battery performance. Battery runs from 100% to about 45 sometimes 40%

Only problem was, the little cores run at Max 1.34Ghz and sometimes the phone lagged and apps loaded slowly.

I run this in adb command to change it

# echo 1555200 > sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

I got the small core to run at 1.5Ghz but when I restart the phone..... everything goes back to 1.34Ghz

It doesn't stick.

I wanted to ask if anyone can help me change the little core Max frequency permanently?
[One (M9) Original Android Development] elitestate:
Does anyone else notice that while playing heavy games pubg in my case that the phone is throttling that much that I'm getting constant spikes of lag. Is there a way to change the kernel ro suit gaming?
[One (M9) Original Android Development] Kirat_XDA:
Is their a reason for that? I need G-Cam port very badly is their some other way around this issue? Help!
[One (M9) Original Android Development] Claymore1297:
I think there is a GCAM 3.x, which works with this ROM. GCAM 4.x don't work, due missing of camapi2.
[One (M9) Original Android Development] Kirat_XDA:
Thanks for replying sir, is it possible that in a future build, we can somehow enable camera 2 api? Or is it just impossible to integrate camera 2 api in this particular rom?
[One (M9) Original Android Development] Dasbi:
says requirements TWRP: 3.2.3-0

i was only able to flash 2.8.5.0 on my phone, wat do?

thanks in advance
[One (M9) Original Android Development] shadowalker2014:
Download 3.2.3 and install using 2.8 from recovery
[One (M9) Original Android Development] The_Walking_Playground:
Hi,

According to FAQ #2 from the TWRP thread, the correct version of TWRP to use with this ROM is 3.3.0-0 ([MENTION=8276284]Claymore1297[/MENTION] you may want to update this in the OP).

However if the only version of TWRP that [MENTION=9912849]Dasbi[/MENTION] could flash was a 2.8.x version, then the issue is old firmware. The only way to be able to flash the latest TWRP would be to update firmware.

TWP
[One (M9) Original Android Development] Dasbi:
yea i just had to update it to a newer version, had to install the older version when on my stock rom, thanks

---------- Post added at 12:22 AM ---------- Previous post was at 12:06 AM ----------

any reason why i would have no sound at all from anything?

bootloader) kernel: lk

(bootloader) product: htc_himawl

(bootloader) version: 1.0

(bootloader) imei: xxxxxx

(bootloader) version-main: 2.6.512.17

(bootloader) boot-mode: download

(bootloader) version-baseband: 1.13.C1144060@60531

(bootloader) version-bootloader: 1.0.0.0000

(bootloader) mid: 0PJA30000

(bootloader) cid: LRA__001

dunno if that even tells anything worthwhile, figured it would be good to include, thanks in advance!
[One (M9) Original Android Development] The_Walking_Playground:
Hi,

Like I said before, firmware is your issue. You're on Lollipop firmware, while you should be on Nougat firmware to use this ROM. I don't think the ROM will work properly with the firmware you have (I'm actually surprised TWRP boots). You may need to S-OFF and convert your device if there's no firmware available for your variant.

TWP
[One (M9) Original Android Development] godshades:
Hi after flash rom, gapps now my phone stuck on logo

What should I do or wait more time :(

Or go to recovery and flash root

my phone status is

locked, s-off

Must I unlock then install rom later

Finally booted after I flash boot.img :D
[One (M9) Original Android Development] Claymore1297:
New build is up!!

the build is containing mainly the following:

- may ASB's

- vibrator intensity decreased a bit

- speaker on max vol fixed due speaker protection

Enjoy!
[One (M9) Original Android Development] Biggie_still:
Boss. Anyway I can get pixel launcher working on this ROM ? Trebuchet doesn't have At A Glance...Also brightness isn't sticking,keeps decreasing it self each time, which camera app would you recommend,Google camera from playstore isn't working.

Can I also flash this new build without wiping anything??
[One (M9) Original Android Development] Claymore1297:
yes dirty flash works
[One (M9) Original Android Development] drpatrickbarry:
I have been using a "paid for" camera "cameraZOOM" for many years in numerous versions of Android and it works perfecty.
[One (M9) Original Android Development] gezge:
Hi

does the Cast work?
[One (M9) Original Android Development] mksahin:
I am using AICP, not Lineage, but in terms of camera, it shouldn't matter. I tried many different camera apps (Open Camera, Footej, etc.). I recommend "HTC Camera" (available at Play Store). Overall, it produces best photo/HDR/video in my opinion. My only complaint about it is that it doesn't use date/time as file name, instead it uses IMAGXXXX.JPG/VIDEOXXXX.MP4 file name format.
[One (M9) Original Android Development] gezge:
Only on the 15.1 works everything
[One (M9) Original Android Development] hamzaalijoiyah:
Is anyone else experiencing UI lags in latest version of LOS. I used Stock deodexed 7.0 rom before and it was so smooth. My phone is S-OFF and on latest Nougat firmware. Just wanted to ask maybe if I'm doing something wrong. Also, is AICP better than this in smoothness, I tried it a while back, and don't remember it lagging this much!!
[One (M9) Original Android Development] Claymore1297:
this is not true!

But maybe you want to specify what you mean ;)
[One (M9) Original Android Development] gezge:
On the 16 the Cast doesn't work.
[One (M9) Original Android Development] Claymore1297:
can you explain a bit more and a log would be helpful
[One (M9) Original Android Development] Claymore1297:
there will be an improvement of CPU-governor settings in the next build.
[One (M9) Original Android Development] gezge:
The cast option (miracast) doesn't word. It tries to connect and it fails. Because of that I am still using th 15.1 version. Thanks
[One (M9) Original Android Development] gregsarg:
Can you provide a log ?

That really is the only way the problem can be addressed....g
[One (M9) Original Android Development] hamzaalijoiyah:
That'd be awesome if we could get Stock ROM like performance on this :D
[One (M9) Original Android Development] Claymore1297:
this feature has been removed by google in P.

But I really don't recommend using the outdated 15.1 ROM...
[One (M9) Original Android Development] hamzaalijoiyah:
Is there a way to reduce minimum brightness on this ROM, cz it still is really bright. I've only found this issue resolved by elementalX kernel, but it only works till Nougat Stock HTC ROMs.
[One (M9) Original Android Development] chayxe:
Please is there a way we can get this overclockable kernel

With all the interactive Governor stuff on the new build?
[One (M9) Original Android Development] Claymore1297:
it is the kernel which is build in the ROM.

The governor tweaks will come in next build
[One (M9) Original Android Development] chayxe:
Thanks Man

I will wait patiently then
[One (M9) Original Android Development] ecompton59:
They have his Dolby that works great with pie it's in the oneplus 6t thread
[One (M9) Original Android Development] billabongstaff:
Hey, guys.

This is a repost, but it's updated now.

For anyone experiencing any sort of screen freeze, lag or ghost touch issues, here is the final solution.

9.5.20 Vendor + Firmware & 9.5.20 Hybrid Kernel are out and they fix all of this for us.

Thank you @Mooatreides

The short how-to:

1 - No point on trying those fixes where you turn this and that off, those are just placebos;

2 - Go here:

https://drive.google.com/drive/folders/1zGc3v1ahsN2dpkPppNAJJMDHKl8jnQmj

3 - Download these two files:

POCOF1Global_9.5.20-ven-firm.zip

&

kernel-beryllium_global_9.5.20-ak2.zip

4 - Flash those zip files using TWRP;

5 - Never again have any screen freeze. You may experience an occasional accidental notification pulldown (ghost touch), but it's very rare and you can live with that.

Explanation:

Quite simply, the magic behind this is that you're flashing a well known original Xiaomi Kernel (from Global 9.3.21) that has no (few) touch issues, instead of running Derp or whatever.

Not a biggie for me, but to each his own.

I, for one, would much rather have a functioning display with an original Kernel rather than rage breaking my screen after 1892132378 times of it freezing and having a custom Kernel just for the sake of it.

If it weren't for @ipdev, you'd have to decompile and recompile Kernels into boot.img and what not. So special thanks to him for making this SO MUCH EASIER.

NOTE:

I am also using a build.prop mod to improve touch response on our device.

Just use the entries below.

********************

touch.presure.scale=0.001

persist.service.lgospd.enable=0

persist.service.pcsync.enable=0

ro.ril.enable.a52=1

ro.ril.enable.a53=0

persist.sys.ui.hw=1

view.scroll_friction=10

debug.composition.type=gpu

debug.performance.tuning=1

#advanced touch settings

touch.deviceType=touchScreen touch.orientationAware=1 touch.size.calibration=diameter touch.size.scale=1

touch.size.bias=0

touch.size.isSummed=0

touch.pressure.calibration=physical touch.pressure.scale=0.001 touch.orientation.calibration=none touch.distance.calibration=none

touch.distance.scale=0

touch.coverage.calibration=box

touch.gestureMode=spots

MultitouchSettleInterval=1ms

MultitouchMinDistance=1px

TapInterval=1ms

TapSlop=1px

**********************

To use them, just add a new line at the end of your build.prop and paste all of the above EXCEPT the ******************** at the beggining and the end.

NOTE:

Obviously I assume you:

1 - Have unlocked your bootloader;

2 - Installed TWRP (or any Custom Recovery);

3 - Have a Custom ROM (or not);

4 - Are running and want to run Android 9.0 Pie;

5 - Know what you're doing.

Let us know how this worked out for you guys (I'm pretty sure it will go smoothly, but still, feel free to reply here so others can see results).

Cheers, guys.

Posts that helped me out:

1 - https://xdaforums.com/showpost.php?p=79184273&postcount=11

(Thank you @Mooatreides)

2 - https://xdaforums.com/showpost.php?p=79184237&postcount=6455

(Thank you @Mooatreides)

3 - https://xdaforums.com/showpost.php?p=79183875&postcount=6446

(Thank you @ipdev)
[One (M9) Original Android Development] Claymore1297:
wrong thread? ;)
[One (M9) Original Android Development] billabongstaff:
No man, just doing a public service, 'cause people everywhere are having this issue and most tend to think it's ROM related and don't even bother to search.

;)
[One (M9) Original Android Development] Claymore1297:
we don't have such issues.
[One (M9) Original Android Development] billabongstaff:
Good for you, man.
[One (M9) Original Android Development] gezge:
Please make to work the 'Cast' and also the sound turns back on Messenger...

Thanks
[One (M9) Original Android Development] Max litcher:
This is not for the HTC m9 are you lost or something bro ? ?
[One (M9) Original Android Development] Biggie_still:
Patiently waiting for the next build
[One (M9) Original Android Development] chayxe:
I currently have all my big cores turned off.

And I used a kernel Manager app to tune the little cores to Max 1.55Ghz

Honestly, i dint even feel my big cores were off.

Apps opened fast enough and games run smoothly

Temperature was very well controlled

Sadly, the kernel limits the little cores to 1.34Ghz by default after every restart.

I wanted to ask if maybe the builder can allow the little core to run at Max sometimes so that maybe throttling will be aggressive on the Big Cores. It might make a huge difference
[One (M9) Original Android Development] Claymore1297:
Thats wrong. The little cores can speed up to 1708 MHz. But you have to configure it.
[One (M9) Original Android Development] chayxe:
Yes please, I configured it to 1.55 using EX Kernel Manager.

And I had a good outcome

But when the system restarts, the core resets to 1.34

And I have to reconfigure...

Unless maybe I leave apply on boot on.

I was only asking if the little core can be allowed to run at 1.5 or maybe 1.7 by systems default so that after a restart it may not reset to 1.34.
[One (M9) Original Android Development] Claymore1297:
Of course, by the boot scripts. You have to configure this by yourself.
[One (M9) Original Android Development] chayxe:
That makes sense....

Please can you educate me a little how to do that?
[One (M9) Original Android Development] Claymore1297:
in boot-script it limits the cores here https://github.com/Claymore1297/and...neage-16.0/rootdir/etc/init.qcom.power.rc#L61

So you can just write a higher value in this file to let the core go on higher freq. - but you have maybe amend the governor-settings too,

if you want to optimize this.
[One (M9) Original Android Development] chayxe:
Thank You Clay....

I will give it a shot and let you know the outcome
[One (M9) Original Android Development] SwitchX1:
Noob here

Hi, first time user of LineageOS here. After much trying with my "new" m9 I managed to update the firmware from stock (at&t) 1.32.502.9 to 3.38.502.41.

Then I installed twrp-3.2.3-1_CPTB-20190315-02-hima and on top of that so I could test Lineage 14.1-20180110-nightly-himaul-signed.

It works good, better than the at&t stock for sure, but the build is kinda old and I'm starting to wonder about the security of a deprecated build, so (now the question):

I'm seriously tempted to try 16.0 that I see has regular updates still, but one of the requirements on the first page is HTC firmware 4.x. Hardcore noob, but I can't see why that's relevant if I ended up wiping all the partitions (did something survive? SBL? where can I check the version of the bare things that are required to install?). It also requires TWRP 3.3.0 but I'll test with 3.2.3 for the time being.

In case the HTC firmware indeed IS required (the most up to date htc fw I had was 3.38) where can I find it? I came across several firmware webs but none offered a full firmware (RUU?) for the 502 (at&t).

Sorry for the long post, I'm doing my best to find the answers by searching the web but the amount of info required it's pretty overwhelming and for you guys this may seem trivial and save me a lot of time.

Thanks in advance!

edit:

I couldn't help it, so I charged the phone 100% and sideloaded 16.0 and gapps... and it worked (fortunately!)
[One (M9) Original Android Development] Claymore1297:
you can simple do the firmware upgrade, by going back to stock and do the HTC-OTA update.

But, if you have no issues with the 3.x firmware, be happy and there is no need to upgrade :). If you are facing strange issues, do the upgrade

and "all" should work.

TWRP 3.3 fixed some issues if you are encrypted.
[One (M9) Original Android Development] SwitchX1:
Thanks! All working for now
[One (M9) Original Android Development] gezge:
Please repar the miracast and the sounds turns back on messenger at the LineageOS 16.0... thanks
[One (M9) Original Android Development] SwitchX1:
Strange Shutdown

I was using the system for 2 full days now but suddenly, I was writing on whatsapp and the phone just turned off, out of the blue. Subsequent reboots land me on the main screen but as soon as the system ends up loading, the warm-night-temp screen activates and the phone just shutdowns again. Is there a way to read a log somewhere to figure out what's going on?

edit: I managed to stop the shutdown by setting airplane mode as soon as the phone allows me... but this is puzzling me
[One (M9) Original Android Development] Jupp Pütta:
Random reboots while charging

I am not shure, if my problem is connected to the post above.

As in an earlier version I again have troubles with random reboots after the phone is fully charged and still connected to the charger (and only in this case). Is there a best way to provide ramoops logs?

Otherwise the new build works fine for me this far.
[One (M9) Original Android Development] chayxe:
Hello Clay,

Please, This is my feedback

I was able to tune the little core to Max 1.7

And Min 1.25

However I used the thermalconfig to Max the cores just at 1.55 ( I now use the "Daily Use" thermal from Team Helix (Mostafa Weil))

With the idea of not burning down my device....

Actually even at 1.7 the device temp was ok till u play constant gaming for like 30mins up

I also went through and kind of turned the GPU up to 630Mhz but realised it ate my battery quickly so I made it the default 180 but changed the governor to -simple_ondemand

I get good gaming (Asphalt 9 - Max Graphics)

The phone sometimes suffer from lags especially when opening an app but it's not regular.

Overall, I can say performance is like 78.5%

Actually Ive been trying to get 2 Little cores at 1.5

And two Big Cores at 2.5 and the rest offline

But its giving me a hard time ...

Until then I will stick to this.
[One (M9) Original Android Development] gezge:
Please make to work the 'Miracast' and the 'sounds turns back on messenger''... thanks
[One (M9) Original Android Development] jmac052002:
Man I just want to thank claymore because I just bumped my new one m9 up to the 4.x.x firmware and flashed this beautiful ROM and im using it as my daily driver and love it, I'm going to donate to you guys for such flawless work, I love android pie and this is what got me into unlocking and modding my phone all those years ago is so I could put great quality ROMs on my phone and enjoy them and I'm def enjoying this one, thanks again
[One (M9) Original Android Development] Claymore1297:
not possible, I already answered this some time ago, see:

https://xdaforums.com/showpost.php?p=79542319&postcount=826

please specify what "sounds turns back on messenger" mean, but don't seems to be a device-issue
[One (M9) Original Android Development] gezge:
When a person speaks with me on messenger he hears his sound turning back. With OS 15.1 it's ok, only on 16.0 is this problem. thanks
[One (M9) Original Android Development] Claymore1297:
which messenger? please more infos and logs.
[One (M9) Original Android Development] gezge:
Facebook messenger
[One (M9) Original Android Development] Claymore1297:
I don't have this, so I need logs ( as mentioned before).
[One (M9) Original Android Development] gezge:
I don't know how to make log. :(
[One (M9) Original Android Development] juuniorLupus:
Hi,

when I do a "repo sync" I'm getting this error:

error: Cannot fetch LineageOS/android_device_qcom_common from https://github.com/LineageOS/android_device_qcom_common

.

I removed this line from roomservice.xml

and I can build it.:good:

Do you think I can install it?

second question:

Do I still have to Extract proprietary blobs?
[One (M9) Original Android Development] Claymore1297:
yeah, repo is outdated and can removed.

No, blobs are in this repo "proprietary_vendor_htc".

Well you can try ;)
[One (M9) Original Android Development] Claymore1297:
New build is up!!

the build is containing mainly the following:

- june ASB's

Enjoy!
[One (M9) Original Android Development] Biggie_still:
Why is it anytime I restarted my phone it will go straight to vibration mode and automatically activate dark mode..also few minutes later I will stop getting notification lights even battery charging light won't show up?

Also inability to use Pixel launcher and any Google camera port is really giving me headache.
[One (M9) Original Android Development] Max litcher:
You can use lawnchair instead of pixel lancher and the only Google cam that's working is this one
[One (M9) Original Android Development] Claymore1297:
The speaker-fix is included in this build and should be fixed.

To the other issues I need logs, as always...
[One (M9) Original Android Development] kall3:
I have the latest version 20190608 in use - without any problems (as before) :) Thank you very much for your time and for the good work.:svetius:
[One (M9) Original Android Development] Biggie_still:
How do I get rid of that back bottom on home screen?? Anytime I enabled swipe up on home bottom with third party launcher it's always there..and my main reason for installing third party launcher is because of At A glance that trebuchet can't offer.
[One (M9) Original Android Development] ayoobelmasry:
The bluetooth problem is still there since the first build, and I have made 3 log- files of the problem ,one per each of the last 3 builds, but you seem to ignore them or you think the problem is trivial and it does not deserve your attention.
[One (M9) Original Android Development] Claymore1297:
or maybe I wasn't able to fix it til now... I can ensure you, I spend many hours to solve this issue
[One (M9) Original Android Development] mksahin:
Why don't you try AICP 14.0 (Pie) for M9 also by Claymore. It has "At A Glance" feature and many others that Lineage doesn't have.

Edit: Just noticed you asked the same question at AICP thread and Claymore already replied.
[One (M9) Original Android Development] Death-Penalty-V:
So I do agree there are still bluetooth audio disconnect issues. However I have noticed after flashing to 5-10 build that if I did a "factory reset" from the settings menu it all but stopped happening. Only time it happens now is when I have lots of background apps taking up memory, and my fitbit wants to drop a log. So like 1-2 times a day, Other than that zero problems. Think it may have to do with dirty flashing and there being code remnants left over cause it used to happen 7 to 20 times a day on 5-10 build before I did this.

Right now I'm downloading 6-8 build and going to flash after that is done.

I think you are doing great clay.:good:
[One (M9) Original Android Development] gregsarg:
Pretty easy....

Check out the first page of the thread.

Our generous Dev has put a link there for an app to capture the logs he prefers.

But please don't post the output in the thread....as we'll all go blind before reaching the end.

Just follow his instructions and I'm sure he will help out....g
[One (M9) Original Android Development] Claymore1297:
I did a bluetooth related change in the build you mentioned, which seems to make bluetooth better working.

I could now reproduce the issue (because I replaced my old BMW, and in the new car I had this issue too) and after this change it only happened one time ...
[One (M9) Original Android Development] ayoobelmasry:
In a span of 70 min. of intended BT connectivity, the problem happens 5 to 8 times. In a 3 hours journey the loss of connection to the car BT is too intense to be considered reliable.
[One (M9) Original Android Development] Claymore1297:
OTA's

Good news everyone!

we can now receive OTA's on this ROM.

thanks to [MENTION=1162986]Captain_Throwback[/MENTION] for the hint, [MENTION=4453138]fagyi[/MENTION] for the idea and finaly [MENTION=6916498]wartomato[/MENTION] and [MENTION=7339792]Codebucket[/MENTION] for their support to make this happen.

Due this I switched also the location, where the builds are located from now on.

The new home is:

https://mirror.codebucket.de/claymore1297/

is is also 1000 times quicker then AFH :).

To get the mechanism work you have to install the builds I made which includes the Lineage-OTA app. You can find the builds in the new location.

OP is also updated.

Enjoy!