yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] :
So just a quick update... I finished modifying franco's kernel driver for userspace tuning. Basically, it's a 4 stage limiter.

The tunables are currently setup in the following sysfs files under the path: /sys/module/msm_thermal/parameters

freq_hell

freq_hot

freq_very_hot

freq_warm

poll_interval

temp_step

temp_threshold

freq_warm is the first stage, this is what the max frequency that the cpu will be limited to when the temperature reaches the value in temp_threshold. temp_step will determine the step between each of the next stages. It will step through freq_hot to freq_very_hot then to freq_hell

IE: using the stock values (default step is 4)

@70°C the cpu will limit to 2265600 (warm freq/temp)

@74°C the cpu will limit to 1728000 (hot freq/temp)

@78°C the cpu will limit to 1267200 (very hot freq/temp)

@82°C the cpu will limit to 960000 (hell freq/temp)

This is with a poll time as defined in the poll_interval file. The default is set to 1 second.

Hard-Coded limits (purely for sanity's sake) will be:

40-90 for the temp threshold (please, for the love of god never set 90°C)

1-6 for the temperature step (this will give a max temp between 3 and 18 °C above the temp threshold)

250ms and 3 seconds for the poll interval

and of course, the frequency steps will need to be valid frequencies. Unfortunately, I couldn't think of a way to force them to be linear while allowing them all to be tuned... as I can't think of a way to force them to be set in an order that I could compare them against each other reliably. Basically, if you have anything other than Warm<Hot<VeryHot<Hell... You will see erratic behavior that I cannot be responsible for, if you don't follow this and see erratic behavior It *IS NOT* the fault of the kernel.. It's user error.

This *should* ideally mimic the end-user experience of intelli-thermal except that it should actually work.

does it sound like I missed anything?

*edit*

This is not currently in any builds. Once we modify UKM, this will probably be in a public release.
[Nexus 6 Android Development] str8str:
It's been said don't use it. It's too temperamental. Use kernel auditor or something. That's what I use. Thou I still have issues with cpu settings not sticking sometimes and going to totally different settings also after reboot. I do believe it's a thermal issue cause I can toggle off corr control turn on intelethermal then turn it off and turn back on core control and boom settings reappear. I've even changes the settings in thermal engine su to no avail. Pop on benzo kernel and problem gone. I'm sure now that they know what's causing it it won't be long to a fix.
[Nexus 6 Android Development] apophis9283:
A few things are happening. He wrote the new thermal stuff. Should fix a lot of problems. If you look at our github you will see a squashed commit called the great revert. We kept every feature but killed a sh** ton of junk. The code needs to be added to UKM so people cant set thermal stuff, thats the last piece of the puzzle. I flashed a test build today and was pretty happy with it. It didnt have everything in it, but still. I think you all will be happy, but as not everyone has the same setup, issues may arise. If it happens get a log and one of us will look through it. Also, my anykernel was messed up. it has since been corrected *cough Yoinx *cough :)
[Nexus 6 Android Development] :
Actually... Nobody said "Dont Use synapse" Honestly.. I'd prefer that more people used it... When it comes up with error.. DO NOT HIT THE "X" or 'CHECK', scroll through the tabs, let me know what items are highlighted and what the "S:" value is.

This will help us narrow down what value is screwing with synapse.

Basically, that error means that some setting doesn't match the values it expects after it tried to set them. IE: SOMETHING is overwriting the values. We really need more people to provide more information to narrow this down. I use app lux, which overwrites the KCAL values, causing that error a lot.

The thermal issue was a major error in faux's intellithermal. It simply didn't work correctly anymore. Not Sure why... But the last ... I dunno 8-10 hours that I spent re-writing Franco's driver to basically mimic Intellithermal to the end-user... SHOULD fix those issues...

In the Kernel Adiutor app though, you're missing out on some of my wake gestures tunables though (I plan on adding more...)
[Nexus 6 Android Development] str8str:
Yes I know it's missing some but it works most of the time if thermal is . . . but kernel auditors dev is adding things all the time so it may not be long before it's not missing anything. I know he's actively developing so we'll see.
[Nexus 6 Android Development] :
We actually have to request him to add our sysfs paths.... he will, im sure... if we request them each.

We could always align our sysfs paths with his too.
[Nexus 6 Android Development] mexiken:
I tried to flash this directly over Chroma. Never had flashing issues before, with any kernel really. Was very excited due to all the options it has, but it was a no go. Didn't boot. Stuck at Google screen, then reboot to Google screen, and repeat. Had to dirty flash to get the stock Chroma kernel again.

Any ideas???? Did I miss something????
[Nexus 6 Android Development] str8str:
That would be great.

---------- Post added at 02:24 ---------- Previous post was at 02:19 ----------

Sounds like a bad flash really. Make sure your download was complete md5. I would redownload and try again

---------- Post added at 02:30 ---------- Previous post was at 02:24 ----------

It's weird how intelethermal works fine in say benzo but then not here.
[Nexus 6 Android Development] :
I've had that same conservation with apophis. I think a lot of it has to do with us building on top of straight mm source. While most people just rebased mm on top of LP. There's nothing wrong with this, but sometimes you're just bringing old/inefficient code forward. It's possible that it depends on something else that needed to come forward and we were nah missing it.

Besides. Are you sure it works? Or is it just not causing issues?

This feels like the same discussion I had about faux sound... Which, while it doesn't break anything... It doesn't do anything in mm source.
[Nexus 6 Android Development] apophis9283:
Please wait for next release. Then well deal with issues
[Nexus 6 Android Development] str8str:
If I leave it set to intelethermal on benzo settings stock and survive reboots but not on vortex. You'd think it's working but I'll let you guys figure into it you'll get it

Straight Shooter
[Nexus 6 Android Development] apophis9283:
Finally got a break from work. I killed f2fs. I killed every file. Then started from scratch also added uksm have no idea if they work as i had to head out
[Nexus 6 Android Development] str8str:
Let's give it a go
[Nexus 6 Android Development] apophis9283:
Its not building atm.I added UKSM and its taking a little work to get it not erroring. Then we still need to add stuff to UKM for temperature stuff
[Nexus 6 Android Development] mexiken:
OK, so I downloaded again, checked MD5, all good.

I flashed it, all was well. Then, I reboot. While tweaking some settings, I noticed that the cores were limited at 936 MHz. I tried changing it, and it just bounced back. I tried changing it in the tunables, still stuck. I changed the hotplugs, nada.

Anyone else having that issue??
[Nexus 6 Android Development] :
That's from the intellithermal issue that I've mentioned a few times. It'll be fixed next build.
[Nexus 6 Android Development] str8str:
If you turn off core control then turn on intelethermal then turn off intelethermal and turn core control back on it should fix it. Till they fix it internally.
[Nexus 6 Android Development] apophis9283:
Im trying. Gotta get this UKSM working. Everything elsse is done

Finally, we should be good for a release
[Nexus 6 Android Development] apophis9283:
Kernel version 2.0 is up in op as well as HSB-UKM-3. You need to flash both. Tons of changes/fixes/modificaations (Yoinx did amazing). I hope you all enjoy. F2FS is available but UNTESTED. I think you guys will appreciate Yoinxs thermal stuff. Enjoy

now that 2.0 is out if you have any issues feel free to bring them to the table as long as you have a log
[Nexus 6 Android Development] str8str:
Thanks guys

Straight Shooter

---------- Post added at 21:32 ---------- Previous post was at 21:11 ----------

Something wrong with zip for kernel won't flash keeps failing
[Nexus 6 Android Development] apophis9283:
I think AFH is messed up. Will you flash the one i uploaded to the op. next to ukm
[Nexus 6 Android Development] str8str:
OK will do thx
[Nexus 6 Android Development] apophis9283:
i will add uksm and ksm tuneables to ukm when i get a chance
[Nexus 6 Android Development] str8str:
Still fails

---------- Post added at 21:58 ---------- Previous post was at 21:54 ----------

Still failing. Zip size 7.43mbs. Tried three times flashing and downloading
[Nexus 6 Android Development] apophis9283:
Thats right. Thats the same one i flashed. Give me a minute

Edit, Im a Dumb@@. Im reuploading and ill update op again
[Nexus 6 Android Development] str8str:
Lmfao
[Nexus 6 Android Development] apophis9283:
OP updated with fixed kernel zip. Sorry for the inconvenience
[Nexus 6 Android Development] str8str:
That one did it
[Nexus 6 Android Development] str8str:
So far much better right off the start settings could be changed without issue

Straight Shooter

---------- Post added at 22:53 ---------- Previous post was at 22:42 ----------

Omg my phone started getting hotter and hotter to the point I couldn't hold it now it's smoking. Did you disable thermal?

Straight Shooter
[Nexus 6 Android Development] apophis9283:
No, ive been running the kernel for some time. No issues.
[Nexus 6 Android Development] str8str:
Lol, just funnin ya. Pretty obvious if my phone is burnt up how could I send message. Sorry if I offended

Straight Shooter
[Nexus 6 Android Development] apophis9283:
Nah, youre fine. Liking it so far?
[Nexus 6 Android Development] TransportedMan:
I'm use to using Kernel Auditor, not Synapse. What are SUSPEND MIN FREQ, RESUME MAX FREQ, and SUSPEND MAX FREQ? What do they do?
[Nexus 6 Android Development] str8str:
Yes very good and I'm using synapse which is a first for a while. Good job

Straight Shooter

---------- Post added at 01:44 ---------- Previous post was at 01:42 ----------

Suspend is same as your min cpu setting, resume is same as your max and suspend should be960

Straight Shooter
[Nexus 6 Android Development] apophis9283:
You all should know, yoinx has a ton of time in this. I couldnt have gotten here without him. I learn a lot from him.
[Nexus 6 Android Development] MrSplaat:
For some reason, the last update makes MultiRom crash if MM is set as a secondary ROM.

Edit:

I found that smb135x wakelock is still ticked in Kernel Adiutor even if it's unticked in Synapse. It's the only one that's affected. I was thinking about an app issue, but could it be a small kernel issue?

Also, blu-plug seems to create some issues, at least on my end. If I enable blu_plug, it won't turn off cores anymore, even if I turn some off manually or decrease max cores. No hotplug will then be able to turn off cores until I reboot the phone. Then it's all back to normal.

Besides these things, thanks for this awesome kernel :)

Keep up the good work, both of you!

Edit 2:

Synapse won't save changes and reverts to default after a reboot. Backup Current Profile also gives me an error, telling me to give it name... Well, I've done that and no go :(
[Nexus 6 Android Development] :
I haven't tried mm anywhere but the primary slot, so that's entirely possible. When you say it makes multirom crash, you mean the mr bootloader literally crashes? The mr twrp crashes? Or the rom crashes one mr tries to load it?

The smb135x wakelock is disabled of it shows disabled in synapse. The wakelocks reflect this in my testing. It's possible that Kernel Adiutor is checking another path as well or something and just giving a false value. I'll have to look into the code for it and see where it is checking.

I haven't used bluplug even though I put a little work into it. Apophis9283 will need to share his experience using it, because he swears by that hotplug.

Yeah, synapse is very flaky. It works perfect for some people but not for others. I've posted a boot script that I use (a few pages back now) that sets everything up how I like. To save profiles/settings in synapse you need to type in a name, but hit the check, then save it.... I know, it's dumb.

Also with synapse, even though it tells you that it couldn't apply your settings it usually applied most of them. If more people could do the following it would help me make this down. When it does that, but ok on the 2min popup. Then WITHOUT hitting the check or x buttons, scroll through all the tabs. Most of your settings are probably there. There should be at least one though that doesn't match, it will be highlighted. Please let me know the section, item name, if the name isn't unique in that section (like hotplug share tunable names) I need the item that tunable goes with. Then also the displayed and set values (the displayed shows on the slider and the set shows on the right as S:w/e). Thank you, like I said the more people that help on this, the faster I can narrow it down.

Thanks for the reports.
[Nexus 6 Android Development] MrSplaat:
MR crashes after I've told it to boot MM. The screen goes black, and right before the Google logo is about to pop up, it crashes and tells me to report the error to the MR developer.

Saving profiles in Synapse worked flawless on 5.1.1 with Vortex 1.7.4. As soon as I flashed MM and HSB, this became an issue. Whatever name I put in, it tells me to give it a name and the name gets reverted to "None"

I've checked the settings several times just to see if the canceled boot was a bug, but it was not. All the changed settings gets reverted after a reboot.
[Nexus 6 Android Development] mhsbrian:
Flashed 2.0 with new ukm on clean cataclysm I get a Google logo bootloop. Tried also with octo, same results.
[Nexus 6 Android Development] :
Sounds like something may have gotten messed up with the kxec hardboot then. We'll have to look at it.

Weird about synapse then. I've never had it not try to apply the settings. Normally it applies them, then throws the errors because one wouldn't take the value to match it's database. You shouldn't be seeing a car where no value gets set, unless you're hitting the check or x... Which resets it.
[Nexus 6 Android Development] MrSplaat:
I'll check the script you posted to see if that helps. I've never experienced this before so I'm kinda clueless about what to do... :/
[Nexus 6 Android Development] WhiteEVO:
Same here, installed on 2 different mm builds, clean and dirty, get bootloop at the Google logo.
[Nexus 6 Android Development] :
Has to be a bad download. Google Logo Bootloop means that the bootloader was unable to load anything from the /boot partition. IF that was the case, this wouldn't work for anyone.
[Nexus 6 Android Development] WhiteEVO:
I'll give it another try, thanks for the tip!

---------- Post added at 07:31 AM ---------- Previous post was at 06:35 AM ----------

Sure enough, bad download! Damn, I always forget about that...

Giving up till next update, phone still bootloops at the google screen, I re-downloaded several times, confirmed md5 match and last flash was a clean install, tried several mm roms.
[Nexus 6 Android Development] apophis9283:
Synapse has a few issues. I have attached a screenshot showing you that backing up a profile works. To do this, simply go to the profile tab, Go to profile/config name. name it, then go to the top and hit the checkmark. Then go back down and hit backup current profile. Youre alomost done. Its a hit or miss using the restart synapse button, i can look into making it work better, you may have to reboot.It tells you to reboot or restart synapse so when you do if you look at the top, where it says restore, click on the button and youll see your backup.

To address the issue where synapse isnt keeping the settings. I know this is annoying, trust me I know. Let the phone boot completely and let su grant synapse all its needed permissions. Open the app and as soon as the first page pops up, hit the x button. That will stop it from changing any of your settings. You should be good to go
[Nexus 6 Android Development] str8str:
All the saved profiles are there you have to x restore and then restart they will show. Don't know why it does this but it will then show all your saved profiles. I had to play with it to find mine I suggest the same.

Straight Shooter
[Nexus 6 Android Development] apophis9283:
We may be able to fix the issues of it not sticking, after talking with Yoinx, me and the wife are gonna go do something.
[Nexus 6 Android Development] apophis9283:
Version 2.1 is up in the op. Slowly hacking away at the issues. Enjoy
[Nexus 6 Android Development] str8str:
Not sure what you did but 2.1 is the smoothest yet. I have been using zzmoove for a while now and it's not very smooth as far a governors. Using profile 9 and I can't believe the difference on this build. Thanks. Reboot still don't stick but don't know you got around to that.

Straight Shooter
[Nexus 6 Android Development] apophis9283:
Im trying to work on that. Yoinx has been pointing me in the right direction. We want it so that you all dont need to do that. I agree. I flashed it earlier and ive never seen it go so fast when optimizing apps. I was happy with this build.
[Nexus 6 Android Development] str8str:
Even scrolling thru Tapatalk etc is way smoother. Love it not gonna want to change

Straight Shooter

---------- Post added at 23:27 ---------- Previous post was at 22:36 ----------

If you hadn't tried it yet give profile 6

a go from zzmoove governor. I'm impressed so far

Straight Shooter
[Nexus 6 Android Development] apophis9283:
I made profile 6 a stock setting. It should be 6 by default
[Nexus 6 Android Development] mhsbrian:
I'm really at a loss here, I have verified MD5's on both the kernel zip as well as the UKM installer. I literally can clean flash catacalysm, flash your kernel...It will either sit at google logo for a super long time and do nothing or try to boot and then immediately go black after showing the animation for about 3 seconds then nothing. I can then dirty flash lean/franco any other kernel and then it completes it's boot. I've been on these forums for a while and been through many phones and whatever else I can say to support this, but whatever it is it simply isn't stable for me. I have always used vortex on previous setups and everything was fine but these past few builds it seems like they're flat out not working for me.

I say this will complete respect, I am a Network Administrator by trade so I know there are many variables that could be the issue here, I am not flat out saying it's the kernel IMG, I just can't explain why you guys work and I am borked.
[Nexus 6 Android Development] WhiteEVO:
It's not just you, I've also tried several times dirty and clean on a few different MM rooms, confirming md5. The 2 times I got it to boot, it couldn't find the sim card and I had no network. After setting up the kernel I'd re boot to see if I could get signal and it would just boot loop...I have no problems with any other kernel.
[Nexus 6 Android Development] :
I honestly don't know what to tell you guys. Unfortunately, like stated, there can be a lot of issues at play... And without physically having the device it would be difficult to figure out an issue specific to one or two devices.

However... Could either of you take a dmesg on a working kernel (right after booting). I'm curious if your phones are binned the same, or at least differently than mine and apophis9283's.

Maybe there is something with the voltage table or something for that specific binning. Though, we use similar to other people.

Feel free to pm them to me.
[Nexus 6 Android Development] mhsbrian:
I know for a fact my phone cannot handle overclocks and higher voltages, dont know if that helps, I don't think my phone can even handle anything over 2800mhz without being flakey. I will try to get what you ask but I am in the NOC today so a little busy.
[Nexus 6 Android Development] :
No worries. Just when you take it, it needs to be pretty soon after boot. The info I'm looking for is really early in the boot sequence and gets overwritten after a while.

Thanks.
[Nexus 6 Android Development] mhsbrian:
How would prefer I send you the dmesg? I grabbed mine.
[Nexus 6 Android Development] apophis9283:
pastie it and post link here
[Nexus 6 Android Development] apophis9283:
Fyi i have it set to default frquencies on boot
[Nexus 6 Android Development] mhsbrian:
Here you go guys, I did a liveboot log so you should see everything early.

http://pastebin.com/xyuXzmRr
[Nexus 6 Android Development] xenx:
Mine won't go past the Google logo either. I know mine is binned pretty poorly. My phone pretty much won't boot with any OC/UC as default.
[Nexus 6 Android Development] :
You may be the email I got.

You're bored as 5/13. Definitiely different. But I don't recall seeing a voltage table for 13... I'll look when I get home.
[Nexus 6 Android Development] mhsbrian:
Yep, I sent it
[Nexus 6 Android Development] :
*Disregard* there seems to be some other stuff that we want to try as well.
[Nexus 6 Android Development] apophis9283:
Im hoping the latest changes help everyone who is having issues. Ill have a test build soon
[Nexus 6 Android Development] apophis9283:
Ok heres the deal. EVERYONE HAVING ISSUES, please test this kernel build. Theres not just fixes but some additions. I flashed it and its running great. I still need everyone with issues to test. Even if youre not having issues you can still update to this test kernel.

https://www.androidfilehost.com/?fid=24269982086994649

Hopefully it works.
[Nexus 6 Android Development] xenx:
Test kernel just keeps looping at Google logo like all the other have for me.
[Nexus 6 Android Development] apophis9283:
ok, ill be releasing an update in a bit. if you dont mind. give it a shot. if not, we will keep tracking it down
[Nexus 6 Android Development] apophis9283:
Version 2.2 is up. Sorry if it doesnt work for you. We are doing our best to track the issue down
[Nexus 6 Android Development] WhiteEVO:
2.2 is booting for me! Great job guys, thanks!
[Nexus 6 Android Development] mhsbrian:
The first build you posted worked for me then froze about after 15 minutes of use then proceeded to boot loop after that, I'll play with the 2nd build and see how it goes.
[Nexus 6 Android Development] xenx:
I know you're working on it. Same issue on 2.2.
[Nexus 6 Android Development] :
Just curious, at the top of the synapse status page, what's it say your svs and speed are?
[Nexus 6 Android Development] apophis9283:
Well, one person is fixed. We will just have to dig deeper.
[Nexus 6 Android Development] apophis9283:
Awesome. I wont be happy until everyone has it booting
[Nexus 6 Android Development] :
This may go without saying, but make sure to verify the download md5.

Afh had given me a few bad downloads this week.
[Nexus 6 Android Development] mhsbrian:
2.2 has gave me difficulties but then randomly started booting after I reflashed and flashed ukm again
[Nexus 6 Android Development] :
Still, it's progress at least..

Like you had said. Given your binning, your chipset doesn't have very big tolerances on anything.

Is also possible that something just didn't unpack or repack right with anykernel the first time.

Hopefully it keeps working for you.

Edit:

Also, just people don't think I'm blaming binning as a buzzword... The stock dtsi doesn't even show for anything with a bin of 14 or higher to get to 2.6ghz (stock). So, the higher that svs bin number the tighter the tolerances and basically the lower quality of the chipset.

You can toggle a bit and read up more on soc binning. I've never seen the small tweaks that were made cause these problems for people even getting a kernel to boot though.

But keep in mind, the higher you bin, the less you can tweak your voltages away from stock.