yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] nathanchance:
No offense man but this thread has never been about the technical aspects of developing profiles. That's what soniCron's initial thread is. No need to get upset over that either, developing profiles is more about feel than anything else. Now to answer your question, the target loads work like a ladder system. This is overly simplified, there are some caveats to certain things that I won't dive into. If the load at freq A is greater than the target specified, you ramp up. If it is less, it stays put or ramps down. So if the load at 1248MHz is more than 30, it will keep climbing. If it is 30 or less, it will stay at 1248MHz for the sample time then ramp down.
[Nexus 6P General] HikingMoose:
It's just frustrating that people won't discuss relevant things.

Anyway, I know that's how it's supposed to work. I guess I'm just wondering why it sometimes jumps from idle right to higher clocks without progressively going up through the steps. I've never seen it go from 384 to 460 to 600 etc.

I've only ever had it go up through the steps in succession with conservative governor profiles, with significant home downs and long sample rates.
[Nexus 6P General] nathanchance:
That would most likely be either input boost or hispeed_freq.
[Nexus 6P General] HikingMoose:
Unfortunately no. Sometimes it goes to a freq higher than my high speed, sometimes it's below it. I don't use any boost. So this lead me to start thinking maybe it was scaling straight to a Target load that matches the CPU load. I.e., the CPU load hits 89, so it jumps to whatever clock has a target load of 89. But no one has ever said they work this way (but they do imply it might). They imply it, because a lot if guides say your target loads should go up sequentially. But there's no reason for them to increase sequentially if they only progress up through the clocks one at a time.

You can use an app called CPUFloat to watch your CPUs on any screen you're on.
[Nexus 6P General] snoprosledneck88:
Could it be that from min frequency to Max frequency is a 100% scale. So 384mhz is only lets say 10% of that scale so a target load of 80 for a clock speed of 384mhz is really only 8% of the whole scale so it becomes overpowered very soon and gets passed very soon. To be honest IDK if this makes any sense. It sounds logical in my head but it looks stupid when I type it. I mean, if you out a target load of 99 at 384mhz it still scales up. In this theory that's because it's only 9.9% of the full scale.
[Nexus 6P General] HikingMoose:
I have the same problem. It's hard to get your ideas or in a way that everyone understands. What I write seems so simple to me, it most not be, because no one ever gets it or answerers it properly. Lol.
[Nexus 6P General] deani77:
Maybe you can set hi_speed freq to the lowest speed available like PX battery profile. Or go_hispeed load to 100.

See how freq step up will behave.
[Nexus 6P General] phantom146:
Ill answer it for you..

It does not mean that 1248 is a good speed to target, the fact id 1248 is the most used mhz in our device. To explain it better:

Any inputs within n6p wuthout any tweaked tunables 1248 mhz is the most targeted frequency, unless if we tweak the target loads to decrease its importance. The problem with the configuration above is it would be extremely erratic. It would tend to stick on 1248mhz most of the time even though we wont need it to be there.

The nominal speed is 1248mhz. The problem with the so called "nominal" speed is that it wastes too much and thats why we are modding the tunables to make it drain less. In my own experiments, I find 1248mhz unbearable when it comes to battery life. 960mhz is a good frequency to stick on in my own personal experiments.
[Nexus 6P General] phantom146:
Sorry for the double post. But as a proof thst 1248mhz doesnt have to be a nominal speed see screenshots below. Mind you my gf had been playing with my n6p the whole day with messenger and costant checking on notifications here and there, and 1248mhz is almost untouched
[Nexus 6P General] HikingMoose:
No, it doesn't need to be a nominal or maximal, I was just wondering if there was a way to read the nominal and maximal numbers to choose the best target loads for my usage.
[Nexus 6P General] phantom146:
I only monitor my usage using the frequency cpu timers within the exkernel manager app. I suggest you leave it at stock first and go ahead and do yourthing for a day or at least 2 full cycles so you can see which frequency has been used the most then that will be yoir nominal frequency. If you aren't that much of a paranoid just go ahead and adjudt target loads, make the frequency below your nominal calue the highedt target load so it'll at least tend to stick at a frequency lower than normal to save battery.

But I dont believe in nominal and maximal values.. Ive been tweaking interactive parameters for almost 3 years and the words nominal is a made up word for me
[Nexus 6P General] HikingMoose:
I also don't like the term nominal and maximal. Mostly because no one agrees on the definitions or how to use them. I've been tweaking kernels for a long time, but I usually make adjustments that I understand, and then monitor the kernels behavior, then tweak again... And again... And again. Lol.

I'm trying to keep my clocks as low as possible, but still want them to be able to ramp up if needed. It's just so hard to really dial it in to really respond exactly how I want. I'm close, but still want to improve my battery use some. But I've got it pretty smooth.
[Nexus 6P General] phantom146:
Tweaking kernels brings the einstein with you but doing it too muxh makes you a flat earth theorists :silly: I suggest for you to tweak your kernel only and if only needed.. being paranoid about battery life only makes your battery really worse..

I constantly see this thread and just scratch my head when a profile was updated.. I mean why would you update something you were supposed to have "tested" hundreds of times if there are no changes in kernel parameters?

Remember that battery does not always mean a lower cycle. The thing is you have to choose between 2 things. Lower down your frequency and finish tasks slower(takes more time therefore more battery) or ramp it a small portion and finish your tasks quicker (takes less time but a little bit higher frequency)

Ramping down frequencies does not mean you have saved a battery. Ramping down is good but too much is a paranoidal thing to do. Balance it out between the two. May I ask what you do the most with your phone?
[Nexus 6P General] HikingMoose:
I let it ramp it plenty. I just can't tolerate it behaving like ondemand, spending 50% of the time at the highest clock. Even at idle, and no apps running, I don't feel it needs to be at fill speed just to idle with the screen on. But to each their own, I'm not the type to tell people how to use they're phone's. I don't like the stock settings, my goal is to try to get Android to be "somewhat" smooth, but not wasteful. You can't have both performance and battery life, you have to balance it to suite your own needs.
[Nexus 6P General] phantom146:
Well if you want it to ramp down quickly put timer_slack to -1 or a low ms and ramp timer_rate a little bit higher.

I have my own tweaks as well and I am pretty much satisfied at how its performing.. My mantra for my tweaks as I have discovered is not to use target loads but rather the input boosts and the delay coming from hispeed_delay. If you are interested at at least trying it, hit me up.

And snother thing, I do suggest max_freq_hysteresis to 0
[Nexus 6P General] deani77:
I would love profile that act like conservative on light task... But act like ondemand when needed... Interactive can give that but need right tweaks to do so... With 8 cores like our phone... It will be a bit hard to get good result
[Nexus 6P General] deani77:
Testing out your governor. Thank you for sharing it.
[Nexus 6P General] phantom146:
Thanks and you are welcome :)
[Nexus 6P General] nathanchance:
I like the overall look of this profile, seems like it should perform fairly well. Also enjoy the explanation, good job! :good:
[Nexus 6P General] phantom146:
Thanks [MENTION=6842057]The Flash[/MENTION]! would love to hear a feedback from you and most people here tho :smile:
[Nexus 6P General] weazie:
Hi and thanks for the profile! Sorry for not understanding how to correct the other tunables if needed? Thanks!
[Nexus 6P General] phantom146:
The .txt file if you applied it should do the trick, you dont neef to do anything if you applied it.

But if you want to apply it manually just go ahead and input the numbers one by one on a kernel editing app, the values for all tunables was shown in the post.

I just emphasized that I used 0 max_freq_hysteresis since stock and most kernel tweaks use 80000, and NO YOU DONT NEED TO CHANGE ANYTHING
[Nexus 6P General] shadowstep:
Thanks for the detailed explanation! Seems like a very rounded profile, glancing quickly over the values. Going to definitely try it out for a few days. Also, welcome to the 6P scene! Glad to have you around. :)
[Nexus 6P General] phantom146:
Its my pleasure :) I hope if you find the tweaks good enough let it be your daily interactive profile ;)
[Nexus 6P General] Spartan117H3:
Yeah the section I'm supposed to read is the "Nominal Clock Rates," right? The problem is, I'm not following what exactly I'm supposed to do. I'm supposed to keep the first cluster on performance, how do I disable the second cluster? Then raise the Min CPU Frequency of the first cluster. Then turn back on the second cluster and set it to power save. Wait, so I just raise the Min CPU frequency until the issue goes away? Is there anyway to set the min CPU frequency on a per app basis?

I never set the first cluster to performance/second cluster to power save when initially plugging in these values, was I supposed to do that?
[Nexus 6P General] xSilas43:
You can't you have to keep one core on and set it to powersave. but I have already done all that work for you when I made CyanLion so it would be easier for you to run that script/profile and then tweak it from there if you find you need to.
[Nexus 6P General] The Destroyer:
xSilas, I really appreciate your work on these settings and scripts, but I haven't had much success with either biothrawn or CyanLion. Both scripts (possibly) have caused my 6P to bootloop numerous times randomly when using them. My phone was in my pocket a couple times when I pulled it out to see it in the middle of booting. It even restarted randomly in the middle of the night after hours of deep sleep.

Can I prove it was the scripts? Not certain. But I have been testing various scripts back to the Stable V1.0 days and none have caused a random reboot like these two have. I have no idea what is it, but I am going back to Ghostpepper for now which worked the best for me out of any so far. Will report back any findings. If I do encounter any issues I will try and do a fresh install and give CyanLion another chance as it was very smooth and working great for me aside from the bootloops and crashes.
[Nexus 6P General] xSilas43:
Yeah it is not possible for these settings to cause a bootloop so it is likely left over dirty data. I would recommend going to settings > storage >cached > clear all cached data, and then booting into twrp and either doing a clean install, or atleast reflashing your rom and kernel, then wipe both caches.
[Nexus 6P General] Spartan117H3:
I put the CyanLion.txt (renamed to CyanLion) into the gov_profiles folder, went to EK manager, CPU->Gov profiles, loaded CyanLion, applied on boot, rebooted, then re-disabled touch boost because it became enabled again. Is that all I have to do?
[Nexus 6P General] xSilas43:
You don't need to reboot after applying the script but I would definitely recommend wiping all your caches if you haven't. yes that and CPU boost as well if it isn't disabled. You can also try reflashing you kernel that has fixed things like this before.
[Nexus 6P General] Spartan117H3:
Disable the input boost frequency and input boost miliseconds (these settings are in CPU Boost) that were enabled with Ghostpepper? And wipe dalvik and cache, got it.
[Nexus 6P General] xSilas43:
Correct! or set to 0 if you can't disable.
[Nexus 6P General] Badger50:
Just a shout out to Jimsilver73! Your Sidious 2.0 script + Cataclysm + Kylo r37 5.3 is pretty darn awesome as well. Smooth and fast. Another great piece of work my friend. Thanks again :)
[Nexus 6P General] Badger50:
Moving on to CyanLion to see what gives. All these scripts are great guys!! Thanks for all the time and effort you put into them. It is much appreciated :)
[Nexus 6P General] abhipati:
How do I install the script using Kernel Adiutor App ?
[Nexus 6P General] giant22000:
Either execute the .sh or enter manually. There are plenty of shell script executers on the playatore that make it easy to do.
[Nexus 6P General] yahoowizard:
Do you know why it doesn't stick if I change it? I just left Adiutor set to "Interactive" which was default, and in the Governor settings, I changed whatever was in the title post for the optimal settings. I did "Apply on Boot," and when I came back to the application, the settings were reset.
[Nexus 6P General] xSilas43:
Are you on stock kernel?

P. S. I have updated the script and profile to R5, it makes the big CPU scale up better under heavy load, ex) gaming
[Nexus 6P General] daleski75:
Just updated to CyanLionR5 with AK31 and giving it a go, no touchboost disable on ak either so playing around with the input boost frequency which defaults to 0:302400 1:302400 2:302400 3:302400 4:0 5:0 6:0 7:0

I take it this means the minimum frequency will always be 302mhz when an input is detected?
[Nexus 6P General] belloni:
Hi Silas, whats changed in r5?
[Nexus 6P General] Ntress:
Im a little confused after reading this thread.. confused of all the profiles..

can anyone recommend me a profile he is using? thanks:)
[Nexus 6P General] darkdreamz:
Mind posting your battery page with what apps you're running?
[Nexus 6P General] doki81:
not sure why... i try r5 on ex-kernel...it gave me random reboot again...have to revert back to my ghostpepper v1.1..
[Nexus 6P General] NuLLV01D:
Try the latest CyanLion script. Links in the OP and previous posts
[Nexus 6P General] shadowstep:
Yep, already running on it. Just one small question, I don't see any value defined for the timer_slack tunable for the big cluster (cpu4) in your profile. Is it intentional or should be the same as the little cluster (i.e. 380000) or should it be something else entirely?

Also, maybe it doesn't matter, but the correct frequency for input boost for the big cluster is 633

6

00, not 633

0

00 (as mentioned by you for the four big cores in the input_boost_freq tunable).
[Nexus 6P General] phantom146:
It should be the same as little cluster 380000, if you check the .txt file im pretty sure its 380000 but kernel editing apps tends to not recognize it (idk why) on big clusters.

The input boost from 633600 doesnt really matter as long as it sticks. Also I'm lazy af and I'm eating pringles right now.
[Nexus 6P General] shadowstep:
Ah, okay. I thought so, so I manually used that value for the big cluster as well. :p Also, checked the settings that you've posted AND your .txt profile too. None of them have the timer_slack defined for cpu4 (/sys/devices/system/cpu/cpu

4

/cpufreq/interactive/timer_slack 380000). Just a heads up. You can edit it when you're done with the pringles. Or maybe not. ;)

It's 1:30 am here, and now you've made me hungry. God damn it. I'm off, time for a midnight snack. :silly: Hasta la vista, amigo! :cowboy:
[Nexus 6P General] phantom146:
Yeah just checked it right now about 30 seconds ago so yeah ill be changing it in the post (idk why it was missing). Well its 4 am here and I am here sitting and wondering what happens to the pringles I eat inside my stomach... I think they're burning inside me.. lol eat well! :cool:

Anyways the post has been updated and I've checked the input_boost parameters for big clusters and 633000mhz does not stick (you will see it'll still be 0 mhz if you clicked on it) so I adjusted it now on the original post and everything's fixed now :)
[Nexus 6P General] deani77:
Day 2 using your profile
[Nexus 6P General] :
Thanks for sharing, SOT highly depends of personel usage, what's yours ? i only see 1 "notable" app used : WhatsApp (7%)

did you use others like chrome, twitter, FB, games, music streaming... no GPS, no wifi ?
[Nexus 6P General] deani77:
Yup... Today only light usage. On 3G all the time and no wifi... Only chatting since I on meeting the whole day.
[Nexus 6P General] phantom146:
Are you using the re-uploaded profile? If yes, well I'd be honest with you, those are great stats (would even be better if you could send cpu times/state). With 3g no wifi all the time? that's some crazy SoT you got there. Any stutters/jitters on your part?

is it smooth? any violent reactions?

Btw, thanks for testing out my profile/tweaks and I really appreciate people like you whom are trying it even just for a day or two, it makes me wanna buy some more pringles. Anyway, again; great stats, and I'm looking forward as to what your opinion is if you play heavy/light games or have done some heavy things in your cat. Cheers!
[Nexus 6P General] shadowstep:
Those are great stats, indeed. My SoT is significantly lower than yours. But then, I've been dirty flashing for ages now plus I've been experimenting with different things, so I wouldn't give much importance to my stats. I'll be clean flashing with a 7.1.2 build soon (just waiting for GApps for 7.1.2 to be uploaded) and then I'll be testing out the profile properly.
[Nexus 6P General] deani77:
I'm using the first version not the re-uploaded. Only change timer slack for big to 380000 and big input boost to 633mhz. Other was stock from your profile.

I was on latest nitrogen ROM with latest flash kernel. Using my own init.flash.rc since I didn't use spectrum profiler.

Will try gaming once I have free time. So far no noticable stutter/jitter since already used to battery saving governor. No camplaint about it

Mine also dirty flash nitrogen weeklies about 2 month after moving from DU because I want to use F2FS. Dirty flash 7.1.2 over 7.1.1 build because lazy to setup my phone.
[Nexus 6P General] HikingMoose:
When you say 3G the whole time, do you mean you had data active all day, or you're just on CDMA instead of LTE? Those are excellent stats, about the same as what I have with my settings.
[Nexus 6P General] phantom146:
Appreciate your further testing with the profile and what you have changed is basically what I have changed on the update so no worries re-applying the settings. Those cpu times were the same as what I get so it's working great for you and I'm happy for it. Mine tends to stick to 1248mhz when I play hi-res 24 bit music which drains my battery along with bluetooth active but that is what I really wanted with the tweak. I hope you have a great cat performance with the tweak. I will be waiting for the heavy usage response, cheers!
[Nexus 6P General] deani77:
I set my phone to WCDMA only since my area didn't have LTE connection. That was really on light usage... I turn on data saver option with only Google play services and Cerberus get unrestricted data access.
[Nexus 6P General] phantom146:
Still great stats considering you have WCDMA on most of the time and not wifi. Please do keep me updated and Ill be waiting for more screenshots.

Btw, have you experienced any lags when:

*Switching fron tasks to tasks

*From a long deepsleep/doze to turning on your display and opening app (are there stutters?)

*Typing with your preset keyboard?
[Nexus 6P General] Daandofreak:
Testing your profile right now on my 6p with latest hells core kernel. Full lte awesome drain. Never had this before. Thx.
[Nexus 6P General] HikingMoose:
I decided to bite, mostly because everyone else was. There's a few things I don't understand in the profile from the logic standpoint. First, you have boost enabled, but set to 0 for small cores and set to the minimum on the big cores - so it's not doing anything. Why not just disable it?

Your advice high speed delays are so small that they're probably I perceivable. The human brain isn't going to notice a 1% of a second ramp delay. If you don't want to delay it, then don't even set it...Right? Maybe that's just me.

I lowered the timer slack down to 100,000 so it wouldn't get stuck at the highest clocks, but the difference between yours at 4/10 if a second and mine at 1/10 isn't a big deal. I may even raise it back up.

Those are observations, not complaints. It does run decent, I'm give it some time and see how it plays out. There's room for improvement, but there's always room for improvement. Mine is not perfect yet, and I've been working on it for months! Lol
[Nexus 6P General] Daandofreak:
Which boost you mean? Input boost?

It's not disabled on little.
[Nexus 6P General] HikingMoose:
What in the? For me, they were all 0 and the big cores were 633.
[Nexus 6P General] phantom146:
Thanks!! Will be waiting for your feedback *looks below* awesome ;) hope you are liking it! Any lags so far? Potato chips?

Input_boost on little cluster should be 600mhz while bigclusters are at 633mhz. It should be low enough to improve battery and high enough to help finish I/O overheads quickly.

Of course it wont be noticeable. If you ramp it up high for hispeed_delay you want to bring lags on your device then. The purpose of it is to delay the frequency as timer_rate kicks in to recompute loads so it'll at least halt a milisecond to decide whether to kick the freq a notch or not (its a computer.. we will never see processes under the hood from the naked eye, and yes they compute in nanoseconds of course unless you sre runnong a snapdrsgon pentium poor lol)

Well it depends on you.. I prefer 380000 due to the fact that frequencies tend to stick to just 600mhz below, the timer_slack is there to provide at least 38ms to let frequencies higher than 1238mhz to stick a little bit (therefore greatly increasing fluidity)

Thanks for your inputs :) It would really help me if yiu send cpu times and any other cinstructive criticisms. Months are nothing.. I've been developing tweaks for 3 years lol. And just an advice, if you continue to tweak and be paranoid at your setups you will never achieve perfection. The word "perfect" is highly subjective and right now for me GlassCannon is :)

Try to reapply the settings. Also just an off topic, I saw your discussion with not getting f2fs in flash's kernel. The cause there is if assuming you really have the right kernel, the rom is the second perpetrator. If the rom doesn't have f2fs patches it'll revert back to ext4.
[Nexus 6P General] HikingMoose:
I didn't have any troubling lag, no worse than most of the other profiles, and better than a lot of them. Battery life seemed very good. I'll reapply it in a bit and see if all of the settings apply and match what you had listed in your post where you first shared it.

Keep in mind, I didn't have any input boost even I tried it. And it still performed admirably. (Although, adding input boost had never given me any real performance improvements, so I never use it).

I understand the timer_slack and why you chose it. I ended up going back to a higher setting. I just go back and forth su much with my settings, one day I have a very, very large timer for slack, then the next day I stop it down to nanoseconds. Then I tweak something else.

Good job.

Edit: oh, I forgot to respond to the f2fs thing. Where I posted that was in a thread for a ROM with f2fs support and many users running it. So, there's a good chance I tried a ROM that supports it. But to take it 54 steps further, I tried 5 ROMs that have f2fs, and I think 2 or 3 kernels. I followed the protocols set forth by each person that has shared how they got it. It's never even come close to working. It's just a hardware issue.