yashsingh1/xdaforums huggingface dataset:
[One (M9) Original Android Development] vizzy:
I know imagine it's due to a lot of M8 users have not moved across. The M7 and M8 always had plenty. But I'm still grateful for those that have moved across like flar etc!
[One (M9) Original Android Development] p50kombi:
I still have my HD2 :)

Let's hope HTC drop the source soon...

These weird charging anomalies are driving me nuts..

Sometimes it charges quickly, sometimes it takes ages...can't put the finger on why...
[One (M9) Original Android Development] itzsnookums:
I totally understand, btw I know what you're talking about on charging, I have one of those charger cords that lights up and changes depending on how fast it is charging, (it's sweet) and works great, but with the m9 sometimes it lights up normally, sometimes it doesn't, usually have to unplug several times to get it to work....But works everytime with everything else.....Just an observation
[One (M9) Original Android Development] donmarkoni:
Charging bug is on software side and is fixable... ;) But lets not go to much off topic here...
[One (M9) Original Android Development] p50kombi:
Tell you what..you tell me the fix and I will stop going OT :) sounds like a good deal...

You're right though...back to topic..
[One (M9) Original Android Development] donmarkoni:
Check my sig. (hint: ROM) ;)
[One (M9) Original Android Development] p50kombi:
yeah, I'm not a fan of viper though.

too much customisation :)

If someone could release the fix as a standalone, or give a documented guide so I can implement it in the rom I'm using, that would be fab.
[One (M9) Original Android Development] BUBBA DUB'S:
[MENTION=4684315]flar2[/MENTION], so I've been reading and testing out i/o scheduler and try to get fiops to stick by selecting it then toggling the power'ish symbol to the right in your app and also changed the readahead value to 2048 and the readahead value sticks after a reboot, but the i/o scheduler goes from fiops to noop for some reason. Do I have to do something outside of your app to get it to permanently stick?
[One (M9) Original Android Development] flar2:
Not sure why it would go to noop, isn't row the default?

There must be something else changing the setting, make sure no other apps, scripts or rom settings are overriding the setting.
[One (M9) Original Android Development] flar2:
It's unfortunate. This is likely my last htc phone. I can't really justify spending $850 on a phone and it sits on my desk because no source = no kernel and no users. I have to sell quite a few apps to recover those $$$
[One (M9) Original Android Development] BUBBA DUB'S:
Row and 256 is default settings, I tried changing once and not toggling the powerS button to the right and it would always reset to row and 256. After I toggled the button to the right which illuminated to verify it was pressed, everything stuck except the i/o scheduler. I will try all the options to see if others stick and report back.

---------- Post added at 08:00 AM ---------- Previous post was at 07:52 AM ----------

So I set it to deadline, and after reboot it went to bfq, I then set it to bfq, and after reboot it switched to deadline. I will continue to try different variations, but my device seems to get it mixed up after reboot lol.
[One (M9) Original Android Development] Quadrider10:
hopefully for android 5.1 and android M gets released they will start sharing sources. but from what it looks like, if they dont, since most HTC users are advanced users, they will end up in the gutter real fast!
[One (M9) Original Android Development] liam_davenport:
It's like this with all devices, HTC for you..
[One (M9) Original Android Development] iElvis:
Development in general seems to have slowed down. If you look in the S6 forums, it's even quieter. I was thinking was dead here. There's even less going on over there even though its sold more than the M9.
[One (M9) Original Android Development] flar2:
I don't pay much attention to Samsung, but I hear it can be extremely difficult to develop for Samsung devices because they are so locked down and have many hardware variations.
[One (M9) Original Android Development] flar2:
I'll check mine tonight. Try clearing app data for now.
[One (M9) Original Android Development] BUBBA DUB'S:
This device is 2 months into development, as much as users think development will halt are to antsy to flash something new. This platform (5.0.2) offers so much that the dev's haven't needed to modify. 5.1 offers additional security patches, but the Android M platform pretty much is what we have now plus the ability to restrict certain permissions. Badboyz 1.1 plus flar2 kernel (and app) makes this phone a beast. This is just my opinion and understand each individual user's experience is different. It is unfortunate that users who relay on social reviews judge this device below par. If anyone knows something that the m9 can't do feel free to enlighten me.

---------- Post added at 10:07 AM ---------- Previous post was at 10:06 AM ----------

Will do, I'll clean davlik/cache when I have a full charge and report back.

It's not a issue due to the fact I change settings based on what I am doing, I just occasionally forget to check/change settings after reboot
[One (M9) Original Android Development] liam_davenport:
Sorry for the OT but what does this have to do with htc not releasing full source?
[One (M9) Original Android Development] BUBBA DUB'S:
Lol nothing, I was on a rant from a different thread. I also am frustrated (assuming you are) that the source code isn't released in a timely fashion. Also sorry for the OT.
[One (M9) Original Android Development] v1rk:
Everyone who owns the device has there own opinion based on usage etc, i know people have sold the m9 and brought something different. If you want to further discuss use pm or report post as this is leading off topic
[One (M9) Original Android Development] BUBBA DUB'S:
I agree, my apologies. I am going to continue testing different variations with this kernel and app. Sorry again for straying off topic.
[One (M9) Original Android Development] flar2:
I don't mind if discussion goes off topic.

I expect the 1.40 source will come fairly soon now that the OTA is official. We never get source for leaked bases. That doesn't solve my problems, but that's not a concern for HTC.
[One (M9) Original Android Development] BUBBA DUB'S:
Looks like OTA's are slowly starting to roll out.

https://mobile.twitter.com/LlabTooFeR/status/608567895921160192?s=09
[One (M9) Original Android Development] BUBBA DUB'S:
[MENTION=4684315]flar2[/MENTION], so I wiped both cache in recovery, cleared all app data and still seem to have the i/o scheduler switch (fiops to noop) after reboot. However , when I force close the app and start it again it switches back to fiops which is the one I set it on.
[One (M9) Original Android Development] flar2:
Restarting the app shouldn't make any difference. No settings are applied when the app starts or stops. How long after reboot are you waiting to check this? Maybe restart and give it a couple minutes and then check.
[One (M9) Original Android Development] BUBBA DUB'S:
Nailed it! I rebooted just let it sit for a few mins and every setting was how I set it and didn't change. I guess it just happen initially on start up.
[One (M9) Original Android Development] iElvis:
So who else is checking htcdev repeatedly to see if the 1.40 kernel source has dropped? :laugh: ;):p
[One (M9) Original Android Development] Whiskey103:
I don't, I expect you to tell us when the moment is there [emoji12]
[One (M9) Original Android Development] BUBBA DUB'S:
@ flar2 , So fiops scheduler didn't perform the way I had expected switched to bfq which so far has been snappy and better for me than fiops. If you wouldn't mind sharing what specs work best for you that would be awesome. I'm going to give the old gal a full charge and run bfq for the entire day tomorrow.
[One (M9) Original Android Development] Quadrider10:
Question, would disabling 2 A53 cores and 2 A57 cores reduce temps and increase battery life? Or would only disabling 2 A57 cores yell better results as far as heat and temp?
[One (M9) Original Android Development] ZeroInfinity:
Don't even try 2x2 combination, I did that before and it turned the phone into a major lagfest :p
[One (M9) Original Android Development] Quadrider10:
Performance has been the same in everyday stuff.
[One (M9) Original Android Development] curiousGeorge:
CPU Settings do not stick

Here's what I went through so far to unlock the 2ghz speed HTC promised.

Bought S-off

Installed elementalX0.3

Bought EX kernel manager

The app does not even offer the 2ghz speed for cluster 1, and when I try setting it on cluster 2, it reverts after 2 seconds regardless of whether the little power icon next to it is checked.

Complete failure to accomplish this simple objective. Also, why does the app not offer voltage options like the screenshot shows?
[One (M9) Original Android Development] ZeroInfinity:
FYI: the first cluster, the "LITTLE" core is an A53 processor and has a maximum clock of 1.5GHz. the second cluster is an A57 "big" core which is the only cluster that has 2GHz max clock.

If you see the OP, this kernel is in it's early alpha stages, most features are not up yet. The screenshots are just an example of the app.
[One (M9) Original Android Development] curiousGeorge:
Okay, thanks. Didn't know about the little cores being maxed at 1.5ghz.

How do I make the big cores get to 2ghz (and remain able to get to 2ghz on demand?) The app keeps showing the max speed revert to 1.5.
[One (M9) Original Android Development] ZeroInfinity:
iirc HTC's pnpmgr is not letting the clock speeds stick, that's probably why. Tbh it's highly recommended you leave the clock settings, you don't want it to get hotter right? :p maybe in the future Flar2 or other devs will find a way to change clocks while bypassing pnpmgr's rules. Besides, big.little is quite new, there's a lot of new things to learn and it will take time for kernels to progress with this chipset :) Also, HTC releases new kernel sources every month or so after a new OTA update is out so we also need to wait for that.
[One (M9) Original Android Development] flar2:
CPU frequencies never stick on htc phones because of pnpmgr. You should just leave the frequencies alone for best results.

The 2GHz freq is actually used when the load demands it.

On the app's latest beta, you can click on CPU Times and then go to the menu and select cluster 2 and you'll see that it occasionally uses the top frequency, depending on how hard the phone is working.

I'm not doing voltage control on my new devices for several reasons. One, the new chipsets are already very power efficient and there is no gain from undervolting. Second, voltages are already optimized very well. Finally, too many users were undervolting and then complaining of instability. It's not completely ruled out, but unlikely.
[One (M9) Original Android Development] guidogsbn:
After using intensively: Nice temperature behavior of this kernel!
[One (M9) Original Android Development] itzsnookums:
I'm in love, flar you the man
[One (M9) Original Android Development] 00mpollard:
Running this kernel for 24 hours now, no issues so far!

Great work, thank you :)
[One (M9) Original Android Development] 030575753:
Glad to see u here!!!!
[One (M9) Original Android Development] beats4x:
[MENTION=4684315]flar2[/MENTION], extremely excited to see you here, especially after all the google play headaches you've been having. Also the patience you have displayed in getting the nexus 6 to the point it is.

For a first go at it, this kernel is running pretty well. The only issue I have noticed is that Sense will lag terribly, go through redraws of the homescreen and such. It is not every time, but it is frequent enough. Thought I'd drop in and let you know.

Edit: Not even sure this is kernel related now that I think about it, if not, tell me to gtfo ?

Again, thanks for all your work, on all the devices you work on (I own them all except the Motorola devices and love your kernel on each one ?) Can't wait to see the new and improved ElX app!
[One (M9) Original Android Development] Cryosx:
I think the governor is the problem. Changing it back to interactive will make things smoother.
[One (M9) Original Android Development] flar2:
It's going to take some time to tune the governor. It's a lot less aggressive than interactive right now. I don't know if pnpmgr works with it either. It would be helpful to know how to recreate lag situations.

Unfortunately you can only tune manually at the moment because no apps properly handle octacore. But I would suggest increasing active floor freq to 8.

The governor with be the key to optimizing performance vs battery life and keeping heat down without throttling.

If we are taking about redraws, it is probably not kernel related unless I've somehow made disk reads slower. That happens when something is pushed out of memory and has to reload. Memory stuff is completely stock.
[One (M9) Original Android Development] p50kombi:
Where can I find the active floor freq?

If I use your app, the governor options are completely empty,,,
[One (M9) Original Android Development] flar2:
Everything is different on this new platform

IIRC, the settings are now at

/sys/devices/system/cpu/cpu0/cpufreq/ElementalX

And for the second cluster, replace cpu0 with cpu4

I'm trying to finish up my new app and get it back on the play store. Once I do that, I will be back to this device and get it tuned up and add some features.
[One (M9) Original Android Development] p50kombi:
so with 8, do you actually mean 8?

It is now 960000

Seems a big change :) not to mention it's decreasing it :)
[One (M9) Original Android Development] flar2:
Whoops, I meant sampling down factor.

That will make the floor freq active longer.
[One (M9) Original Android Development] beats4x:
[MENTION=4684315]flar2[/MENTION], I wish I could give an exact way to recreate it, but the closest I can get to that is that all um doing is opening up, say, hangouts, messaging a few people, then hitting the home button. I get a blank homescreen, and it takes a few seconds for everything to repopulate. Sometimes longer. I've done what you said, but one question, from the way you worded your instructions, you made it sound like I only need to change the sdf under cpu0 and cpu4, is that correct?

Again, thanks for your time.
[One (M9) Original Android Development] flar2:
Yes, changing for cpu0 and cpu4 will change governor settings for their respective clusters.

I haven't seen the problem you are describing, it sounds like the launcher is getting booted out of memory. This would have nothing to do with the governor.
[One (M9) Original Android Development] beats4x:
Okay, just thought I'd drop in and make sure. Thanks [MENTION=4684315]flar2[/MENTION]
[One (M9) Original Android Development] frankcck:
The situation for me was while I doing multi tasking, let's say listening music, chatting, and XDA or Chrome, when I switched between each app, the music would stuttering in the background, and apps are laggy. I don't have home launcher redraw issue though.

hTc one M9 LET THEM STARE
[One (M9) Original Android Development] flar2:
This could be the result of using a different governor, not sure. In the past, I've had to keep the governor named the same as the default governor or pnpmgr wouldn't work correctly. HTC uses pnpmgr to do a lot of app specific performance enhancement.
[One (M9) Original Android Development] fallenangel408:
awesome to see you on m9 my friend it works on latest ARHD perfectly...cant wait for the goodies especially the double tap features :good:;)
[One (M9) Original Android Development] INMAN85:
FYI booting on sprint running viper! I know it's international but tried it. Testing everything now!
[One (M9) Original Android Development] INMAN85:
Settings sticking as well!
[One (M9) Original Android Development] flar2:
Wow, it works on sprint!

Anyone try a Verizon phone?
[One (M9) Original Android Development] BUBBA DUB'S:
[MENTION=4684315]flar2[/MENTION] , do you know If the quick/fast chargers throttle back based on CPU temperature? And if they do is there any way to raise that value slightly?
[One (M9) Original Android Development] frankcck:
Benefit from UV for me is less heat but totally understand your points.

And always believe in your works.

Thanks man.
[One (M9) Original Android Development] Quadrider10:
X2! I would love to see this! :D

I've been playing around with disabling cores, and so far the best combination ive found between battery life, heat, and performance is either 2 A53 cores and 2 A57 cores OR 4 A53 cores and 2 A57 cores. in everyday ussage, i notice no difference between the 2 probs because it allows the A57 cluster to acutally hit 2GHz and stay there longer. on Antutu, 8 cores got a score of 54k while 6 core was 52k and 4 core was 50k. GPU performance was the same between all of them. I also tried a 3x3 combination. although this combination reduced heat, for some reason, all scores were lower.

IMO, i think a good combination for cpu cores is 2x2 at stock clocks or 4x2 with A57 clocked at 1.8GHz to reduce heat and save power.

Whats strange is that if you turn on power saver mode, the phone heats up more and uses more power then when not on power save mode IE. disabling all 4 A57 cores.

personally, my ultimate goal for this phone is to get as best battery life as possible while still maintaining a smooth experience with the best possible GPU performance. To do that, throttling needs to stop cause once the CPU heats up, it starts to throttle the GPU from 600MHz to 390MHz then 310MHz.
[One (M9) Original Android Development] pmacevad:
Very informative. Thanks for sharing your testing experience.
[One (M9) Original Android Development] colorprint:
still no kernel updates for 1.40 firmware?
[One (M9) Original Android Development] liam_davenport:
Waiting on htc source
[One (M9) Original Android Development] Quadrider10:
[MENTION=4684315]flar2[/MENTION] nice app update!
[One (M9) Original Android Development] BUBBA DUB'S:
+1
[One (M9) Original Android Development] Alcolawl:
Just to clarify, the "Performance Level" tuneable in the app works on a scale of 100; 100 meaning maximum performance? I know this tweaks the "min_budget" facet of the governor, would you mind explaining what this does exactly? I'm assuming 100 means the A57 cluster is more inclined to boost its core clocks and help out with workloads?

Nice update too, btw. I really like that I can see the big cluster's frequency table now.
[One (M9) Original Android Development] flar2:
0 is least likely to use A57, 100 is most likely.

The setting is meant to override pnpmgr, which assigns a "budget" to A57 usage. As soon as the heat risea a little, pnpmgr sets the budget to 0. This setting will not let pnpmgr reduce the budget below the specified value. Setting it to 100 could cause more heat generation.
[One (M9) Original Android Development] flar2:
It does throttle, I don't know if there is a way to change it
[One (M9) Original Android Development] Goldenstarc:
flashed on viper 2.3.1 (lastest android update) and my m9 reboot every 2-3 min
[One (M9) Original Android Development] guiltyundertaker:
Read the guide on viper thread. This kernel is on 1.32 base and is not compatible with 1.40, it causes reboots, you need to wait for updated kernel here and reflash viper Rom selecting 1.40 kernel in setup...
[One (M9) Original Android Development] donmarkoni:
So? You failed to read warning on VenomROMs site and then you expect somebody else to solve your problem, right?
[One (M9) Original Android Development] tigerland:
hey man, do you recommend me to flash this kernel with viper 2.3.1? I'm just curious.
[One (M9) Original Android Development] donmarkoni:
Really? Really!?! Have you read previous few posts? You need to read only three post before your question. So, do read! Don't be ignorant!

I can't believe it...
[One (M9) Original Android Development] sdamark:
Depends on your device, carrier, firmware... I'm using this kernel with ViperOne 2.3.1 on a VZW M9. Works great. It will also work on Sprint and TMOus if you are still on stock firmware.

If you have updated 1.4 firmware do not use this kernel. Random reboots and problems will arise.
[One (M9) Original Android Development] donmarkoni:
Spoon feeding doesn't help, bit I appreciate your effort to help.
[One (M9) Original Android Development] sdamark:
We all were green once upon a time.

If more people would read and search first, most of this nonsense would not occur.
[One (M9) Original Android Development] tigerland:
Thanks guys, but my firmware is the latest one 1.40, and I'm owing the international device version.
[One (M9) Original Android Development] BUBBA DUB'S:
Elementalx 1.32 not 1.40 , elementalx 1.32 not 1.40... If you don't know then now you know... Elementalx 1.32 not 1.40.

Viper users are excluded if using 1.32 kernel/firmware on 2.0.0 or higher. Just check the correct options in aroma or you will pay dire (with reboots).
[One (M9) Original Android Development] Goldenstarc:
Thanks but I did that !

I already have 1.40.401.8 firmware it's not my problem

I have to wait for new version of this kernel

That's what is told indirectly
[One (M9) Original Android Development] iElvis:
<tapping foot and glaring at HTC>
[One (M9) Original Android Development] Andrewbud:
http://dl4.htc.com/RomCode/Source_and_Binaries/himauhl-3.10.49-g9d36a74.zip

1.4 kernel HTC Asia. Can this be used :questionmark; (keyboard went all french on me.)
[One (M9) Original Android Development] flar2:
It just takes me to the HTC home page, but at some point I will probably be able to download it.
[One (M9) Original Android Development] Andrewbud:
I have it on Google drive if you want. Took over 3 hours to download, HTC server sucks.

Our locals are pretty similar, not sure why the link doesn't work.

https://goo.gl/g40bcf

Tried the link.. Brings me to the Canadian HTC site homepage... poop.

Anyway. Link provided is the zip file containing the source.
[One (M9) Original Android Development] flar2:
It's finally downloading...slowly
[One (M9) Original Android Development] Andrewbud:
Probably quicker from google if you're eager ;)
[One (M9) Original Android Development] iElvis:
This isn't the 1.40.401.8 base that all the ROMs are using, but the differences are probably minor at best.
[One (M9) Original Android Development] flar2:
Update!!!

For 1.40 base (probably doesn't work on 1.32, I didn't test it)

A couple notes:

-This uses your existing ramdisk!

-I just patched in my changes from the previous kernel

-I've just booted this up now, it hasn't been tested very well

Let me know how things work out. I'll continue with development of features/fixes soon.

Download:

ElementalX-m9-1.00

Changes:

-update installer

-use existing ramdisk

-update HTC source g9d36a74 (1.40 base)
[One (M9) Original Android Development] :
I could kiss you!

Working for me.
[One (M9) Original Android Development] Quadrider10:
sweet!

---------- Post added at 12:15 AM ---------- Previous post was at 12:04 AM ----------

The 1.40 kernel does not work in 1.32 base.
[One (M9) Original Android Development] flar2:
They have the exact same features anyway
[One (M9) Original Android Development] guidogsbn:
Works without problems after install, will test it over the beginning day here. Only in App Ex Kernel Manager it offers me new update 0.03= beta kernel for 1.32.

Same thing already after updating firmware to 1.40! So it's only the app:good::cool:

Thank you for this highspeed update!
[One (M9) Original Android Development] :
I've encountered a bug where after installing, my device became self-aware and started to call himself Barry. "Barry" started asking about his creator and his purpose, but unfortunately I don't know much about [MENTION=4684315]flar2[/MENTION] so I just told him he was made out of love. I told him his purpose was to make my life easier and it tried to kill me. After a huge fight with "Barry the HTC One M9", I managed to get him into recovery and reinstall the kernel. Everything is back to normal now. I think.
[One (M9) Original Android Development] mcnaget:
Kernel 1.00

I just tried with latest Leedroid 7.6.0 but keeps restarting.

regards