yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
For sure, that's usually the case. Before I undervolted it was a common occurrence. Is thermal throttling the only way to get the x though? When i said "complaining about sampling time" I meant that I changed the value to 18000 and a couple times Synapse had the x and the only value that was reset was sampling time back to 45000 (both clusters still overclocked).

Regarding thermal throttling, I've observed a huge decrease in those occurrences since undervolting. Fantastic!

I should have mentioned that I took your advice and immediately changed voltage to defaults after I restored your profile.

That's hard for me to follow. I did not change up thresholds or hotplugging thresholds but I did improve performance by increasing freq_step_raise on both clusters and dropping HMP thresholds.

Thank you!! So to be clear I understand...this is how I currently setup block cycles:

If

sampling_rate = 45000

block_cycles_offline_screen_off = 110

(I also do this for _screen_on)

Then

Cores within this cluster will still scale in frequency but hotplugging will not turn them offline for 110 times (approx 5 seconds at a 45000 ms rate per cycle).

I don't change block_cycles_up or _down at all, and I don't change block_cycles_online_screen_off or _on.

I haven't observed any lag using this, in fact a very noticeable increase in performance...I can measure it by how quickly the edge feeds turn on when the screen turns off (a sum of all performance tweaks, I know).

But if I were to change the block_cycles_up or _down values, it would probably affect performance negatively. Correct?

I will try to wrap my head around that and test it out. Thank you!!
[T-Mobile Samsung Galaxy Note5] Rx8Driver:
Another thing you wanna keep in mind where your sampling rate is concerned in relation to latency with your low hmp values is that you're going to ADD latency by migrating tasks from one hmp domain (53 or 57 "cores") so if your processes are jumping to and fro and your sampling rate can't keep up then synapse should kick the setting (ie you get the X in Synapse for sampling) ......just food for thought :)
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Sorry about that i wasn't clear (i couldn't understand it myself ??? )

What i meant was say A57 multicore

Core0 i believe

For example keep core0 up threshold 10% (not really just an eg) and core1 15% (narrowing hotplug up_threshold) and core2 20% and core3 25% should help performance allot

---------- Post added at 08:06 PM ---------- Previous post was at 07:54 PM ----------

You might be right there because he mentioned that his sampling rate kept going back to 4500 when he gets the x though i never had that happen to me

But then again i never tweaked the hpm that low either simulating turbo was easy on ktoonservative on earlier versions of sky high because we had more control kt gov

One of my favorite govs
[T-Mobile Samsung Galaxy Note5] Rx8Driver:
Well it just got me to thinking, if i were tweaking at this level, I'd be comparing what's faster- ramping up and migrating a task from a53 to a57 with all the latency that's involved- i mean what's the reason for not just using turbo mode?
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
Curiosity and the pursuit of (at this point) an unquenchable thirst for knowledge.

But ultimately, I'm trying to replicate turbo with ktoonz, in order to save more power when my device is idle (without compromising any of the awesome performance of turbo)....because I have modified my device such that edge feeds always appear when the screen goes off (which means my screen is never really off...which in turn means my device never goes to deep sleep).

The idea of hotplugging with ktoonz had intrigued me, to that point. I'm not even certain if any battery savings would be more than a negligible amount, but I'm hoping to save something measurable.
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
Oh yeah....another good reason is because this profile smokes Interactive-turbo! [emoji1] [emoji1] ...I don't know about benchmarks, i don't really do it much, but IRL the responsiveness is unbelievable.

Ktoonz - turbo

Video

...I put sampling rate at 10000 to try and keep up....that's as fast as it goes. So far, so good after 2 hours. Usually my reboots happen every 3.5 to 5 hours, so we'll see.
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Because we love to tweak and understand mate this is xda

Just because it aint broke doesn't mean we can't fix it

We gotta tweak at this level because if we stay with good enough then might as well go stock man

Its a hunger to tinker lol

---------- Post added at 12:29 PM ---------- Previous post was at 12:27 PM ----------

Your just as intrigued as i am with ktoonservative this governor has HUGE potential some people might not understand it but it does
[T-Mobile Samsung Galaxy Note5] Rx8Driver:
I think is got great potential, but if just seems to me that there's inherent limitations because of latency, in things like hotplugging the cores and migrating tasks, that negate much of the performance?

---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------

For instance I've yet to improve upon interactive with only a bit of undervolting for responsiveness of UI and overall pwr efficiency. But that's just me...
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
Speaking purely of performance, my experience has been superior to Interactive turbo by using the ktoonz profile above. I'm super impressed with it. I have experienced zero lag (I think in part due to the advice from both of you to reduce sampling time).

I can almost live with a reboot every 3-6+ hours....but, stability is important, and when that is also factored in, Interactive turbo wins by default.

I don't have any experience analyzing kmsg logs so I have no idea what to look for...but I have seen a lot of lines like "....is no longer affine to cpu5". So, researching what that means confirms that the problem is with migrating tasks from one cpu to another. My research indicates it's likely that a task is executed on a cpu and that core is hotplugged while the task is still executing, throwing the error...and some tasks cannot be migrated.

I wonder if my issue is that a system ui task (or some other important task) starts on A53 and 1 millisecond later is forced (or attempted) to migrate to A57 and fails, collapsing the system. This scenario would never happen with Interactive turbo, since that tasks actually start on A57...not migrated a millisecond later.

Or, if [MENTION=5663089]Rx8Driver[/MENTION] is correct, maybe the latency just builds up, like wound up magnetic fields in a star, and just explode after a few hours of operation. In this scenario, I would expect to experience other symptoms...lag/stutter/slowness....but I experience none of that. Just perfect performance right up to the moment of a reboot.

Or, I have no idea what I'm talking about (likely since only two weeks ago I didn't even know what tunables were) and it's something completely different.

[emoji1]
[T-Mobile Samsung Galaxy Note5] Rx8Driver:
Well you're definitely correct that some processes CAN'T be migrated and must finish on the cite they start on or eventually just fail...I'm no expert but it seems there should be a way to specify what domain you want a certain process or type of process to start on. This way you could make a sensitive app or function start on the big cores instead of the little ones. I feel like you may want to approach your tune from the opposite perspective- enable turbo on ktoonservative then set your thresholds to move your lower priority processed OFF the big cores until all the foreground stuff is finished, since it's a race to idle...
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
Thanks for confirming about process migration...[emoji106]

I think turbo mode is exclusive to the Interactive governor...I think enabling it with ktoonservative doesn't do anything? I could be very wrong about that... That is exactly what my first attempt was here .

That is an interesting approach though that I could try with the Interactive governor. The point of all this is to try to take advantage of hotplugging for power saving....which I think I could do with Interactive by using the shell script I posted here if I can figure out how to disable Samsung's version of mpdecision.
[T-Mobile Samsung Galaxy Note5] Rx8Driver:
Don't we need Samsungs version cuz of the Exynos cpu?

---------- Post added at 09:37 PM ---------- Previous post was at 09:35 PM ----------

Edit: i mean isn't Samsungs implementation unique because of the source code for the Exynos cpu? I mean they never truly released all the code for exynos, only kernel code, so i feel like they wouldn't make special implementations of it weren't necessary. They WANT their chip to outperform snapdragon, and so far they do- i want an 8890 device so bad!
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
I don't know...I'm definitely in uncharted territory there and way over my head. But when I was contemplating the idea of hotplugging Interactive, and researching it, I came across that script...but before running it you have to stop mpdecision or it doesn't work.

When I try it, it doesn't work...whether I put "# stop mpdecision" or not...so researching why, I learned that mpdecision is for qualcomm devices. I'm assuming exynos uses something else, and I'm assuming it works the same way...but I'm reaching, admittedly.
[T-Mobile Samsung Galaxy Note5] Rx8Driver:
Edit edit (lol): I'll see what i kind find out right quick about mpdecision, i only know what i know lol i don't have all the answers by a long long long shot! That's why I'm glad there's guys like you and muffs and of course all the devs who document and discuss this stuff here....our talking this stuff out might be exactly what triggers an idea of genius proportions for the next person reading along! I love it!

---------- Post added at 09:42 PM ---------- Previous post was at 09:41 PM ----------

So your thinking there's a doppelganger of Samsung's design that's not being disabled?
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
Well....i think whatever it is has to be disabled for ktoonz hotplugging to work (not sure), so I don't necessarily think it's a secret...I just don't know how to make it work myself.
[T-Mobile Samsung Galaxy Note5] Rx8Driver:
Disabling mpdecision is what prevents a stock kernel from being able to control the hotplugging (i assume thus allowing whatever you're implementing to take ovdd control) and can increase performance but also sometimes hurts battery efficiency. So what is Samsung's solution? I'm thinking DVFS or the likes....

---------- Post added at 10:03 PM ---------- Previous post was at 09:49 PM ----------

Take a look at this, it has great info

https://drive.google.com/file/d/0B80obHdczwZoTndMSUMzeXZLTXM/view?usp=docslist_api
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
Thanks man...I'll need to chew on that a few more times than normal before swallowing.

OT from the direction I've been going, but on the back burner is a project to tweak Interactive for optimal frequency use (and maximize battery)...but it seems that synapse (or sky high?) doesn't have many of the tunables that I've read about. Thoughts?
[T-Mobile Samsung Galaxy Note5] Rx8Driver:
I feel like if skyhigh doesnt have the tunables then likely nothing does
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
Yeah, I'm certain uita has included all possible ways to customize his kernel.

That might actually explain why there isn't something like "delay_go_hispeed"...

Wait...so you have a qualcomm chip? Then you might actually be able to hotplug Interactive:

su

stop mpdecision

echo "0" > /sys/devices/system/cpu/cpu7/online

That should take 7 offline....echo 1 to put it back online.

And of course, it might break your expensive device............
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
He has an exynos as well but in the states we are getting snapdrogon variant

Also if its possible to load a gov module eg ondemand that does have interactive and ktoonservative properties and also used to be samsung stock gov ??? I could be wrong

Side note skyhigh has the most tunables but there are some missing from it

You could try another kernel tunning app

Faux clock might be what we are looking ill give it a go i purchased it a while ago
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
I can confirm faux has the ability to hotplug cpu on interactive ill have to do some testing

But it seems to work also i had to purchase it again i dont know why but it seems something went wrong ive emailed the developer for a refund

Edit

Option is there but not selectable

Im still on a stock kernel so when i get home ill flash latest skyhigh and see if there are changes (mostly wanna test snake charmer) missed faux
[T-Mobile Samsung Galaxy Note5] Rx8Driver:
No no, I've got Exynos, just a 7420 when i WANT an 8890 lol
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
I feel like I just had a eureka moment! I/O tuning. I forgot about that tab because I always leave them at defaults. Well, the affinity errors in kmsg indicate a problem that might be fixed with the scheduler, right? Have a look at that tab....RQ Affinity is set to aggressive as default. I'm disabling it....then researching all those different schedulers and tunables.

If there's any I/O experts out there, I could sure find your thoughts useful!

*fingers crossed*
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Im no expert in anything but i can help out where i can i have a little knowledge
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
Thanks man!

Well, I think I'm on to something...but I'm having a hard time getting it straight in my head. In the kmsg logs after a reboot, I often see complaints that read ".....is no longer affine to cpu6" ....or several cpus. So, my thought is that there must be a system process that collapses the system when the HMP scheduler attempts to migrate it to a different core.

I got excited last night when I discovered the RQ Affinity setting in Synapse. But this morning when I read the description, I'm second guessing myself. I think default = aggressive should help prevent my situation from occurring, and changing to disabled might make it more likely that I have those affinity errors.

I'm still testing it out, but I have had 2 reboots in 10.5 hours. HMP 1 and 25....RQ Affinity disabled.

So....I think I'm onto something with looking into I/O settings, but I'm still not sure what exactly my plan is.

Check out this post and others by him in that thread. It appears that I am beginning to walk down the same path [MENTION=2143933]martinoff[/MENTION] did 2 years ago. Searching that thread for "affinity" is fruitful.
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
So from my understanding you still have the reboot bug ???
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
If I leave HMP at 1 and 25, yes....I get a reboot every 3.5-6+ hours.

The lowest stable HMP that I've found (further testing needed) is 250 and 150....but at that point I'm losing performance compared to Interactive turbo.

I am trying to stabilize (by correcting the affinity errors) the very low HMP settings that really give outstanding performance.

Edit: The other option would be to actually use Interactive turbo, and hotplug it with Faux? Were you able to do that with sky high?
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Unfortunately no its actually worse on faux clock then it is synapse a huuuge amount of setting are missing

Edit

Have to tried playing around with little packing ???

At all also you trying to get maximum performance from kt correct let me work on one for ya im sure i can come uo with a performance profile with dropping hpm that all and without reboots
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
Yeah, I've played with it quite a bit actually. I leave it disabled on this particular profile because it does exactly the opposite of what I want. I'm trying to get most processes to pack the big cores instead of LITTLE (just like turbo mode).

I do leave Power Efficiency Scheduling and PEWQ both enabled though...it helps keep A53 clean to have any processes assigned to A53 forced to cpu0 first.
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Ok buddy can you post your profile i wanna try test it out on my device and see what tweaks can be done to keepperformance as is but without reboot bug
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
Sure, here's the profile I'm experimenting with.

I have this one at default voltages, extrapolated increases on oc frequencies....I was trying to rule out uv as a cause for reboots, but normally I run at -75.

Edit - I might have accidentally saved that with fiops scheduler instead of the default cfq scheduler that i usually use....fyi.
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
So, after a solid 36 hours of tuning and testing Interactive, I'm learning that [MENTION=5663089]Rx8Driver[/MENTION] might be right. I think I had kt tweaked to peak performance. I believe I had it tuned better that turbo mode with default interactive tunables. I'm not sure if it was latency or not, but I just couldn't keep it stable enough to use every day. I never was able to experience any battery savings due to the hotplugging, tweaked like I had it....in fact it drained slightly faster than Interactive (anecdotal).

So, for the last 36 hours, I've been testing and learning how to tune Interactive. Definitely, it has been more battery friendly. After reading this article and learning how to tune this unique version of the Interactive governor for 7420, I can confidently say I've easily exceeded the crazy performance that I squeezed out of kt...and at roughly the same drain.

And my ASV 7 is very stable at -100...surprisingly.

https://www.dropbox.com/s/9jyq7qhoc4q512k/Interactive.turbo_-_oc.uv_-100_-_hi.prf.txt?dl=0
[T-Mobile Samsung Galaxy Note5] LiL_Assassin:
Not sure if this was the issue. But downloaded the none audio version and i think that may have fixed the wierd freezing issue when i would open synapse. But running the last linked profile. Was power saving mode enabled?

Edit. It came back...i have no idea why it randomly freezes. If i uninstall synapse. It goes away. But means i cant change kernel parameters. And this can happen even before i change anything. I cant even switch off my device unless i force reboot it to download mode.
[T-Mobile Samsung Galaxy Note5] montojo2003i:
Can anyone tell me what's wrong and how to rectify it?

I'm on S6 with ported S7 marshmallow custom rom. Came from a different kernel before.

Thanks to anyone who can help.
[T-Mobile Samsung Galaxy Note5] Rx8Driver:
Make sure synapse has all the permissions it needs, but i can't run a skyhigh kernel until there's T/W8 kernel source for note 5 to be able to help you. Synapse can be testy from a dev perspective sometimes...the kernel has to have all the synapse functions coded in, what kernel you on?
[T-Mobile Samsung Galaxy Note5] montojo2003i:
I'm on hacker kernel v14 for MM.
[T-Mobile Samsung Galaxy Note5] Rx8Driver:
Well i would suggest clearing synapse data and seeing if that works. Beyond that I'd say check with the kernel dev and see if it's a known issue or what...
[T-Mobile Samsung Galaxy Note5] montojo2003i:
Good suggestion, mate. I'll try that and will let you know.
[T-Mobile Samsung Galaxy Note5] Rx8Driver:
I also remember an issue once where synapse was getting confused between packaged kernel busbox and system busybox and i had to remove the sqlite3 and something else from system/bin and xbin....oh that was a synapse error restoring profiles....Probably wouldn't affect your situation at all actually smh lol
[T-Mobile Samsung Galaxy Note5] montojo2003i:
I did clean the synapse data but for some reason the old setting sticks and same old error pops up.
[T-Mobile Samsung Galaxy Note5] bighit101:
[MENTION=6311359]muffinsmuffy[/MENTION] Ohh man im def doing something wrong because I have the same rom and kernel as you and I'm avg about 4.5 - 5 SOT :(

Help me get to your level plz! :)
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
Edit: Nevermind...
[T-Mobile Samsung Galaxy Note5] Rx8Driver:
Well, I'm now running SkyHigh 2.9 on MM, so after a little testing I'm going to get into tuning her! [MENTION=5020814]RuggedHunter[/MENTION]
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Sup mate sorry guys been out of action for a while had some medical issues

Can you post a screen shot of your sot

Im now mm but hasnt been going too well in term of battery 5 hours sot but on tex rom i have been getting waaaay more then that and ill help out anyway i can
[T-Mobile Samsung Galaxy Note5] Лithium-Фusion:
Hey bro, I hope you are ok now. God cure you, take care.

Powered by Elektrik
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
+1

[emoji40]
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Thanks mate im back up and moving about strong enough to head back to work tomorrow

---------- Post added at 07:31 PM ---------- Previous post was at 07:30 PM ----------

Thanks dude guess what using your edge feed with river rom good work man i like it allot
[T-Mobile Samsung Galaxy Note5] RuggedHunter:
Glad you're doing okay, and that's awesome I hope you like your "cocktailbarservice"!! [emoji6]
[T-Mobile Samsung Galaxy Note5] UpInTheAir:
Welcome back. :)

Sent from my SkyHigh Kernel powered SM-N920C
[T-Mobile Samsung Galaxy Note5] bighit101:
[MENTION=6311359]muffinsmuffy[/MENTION]

Hey, hope your feeling better now.

I recently updated to MM too (TEKXNESIS v2.5), but still battery is not playing nice. I thought MM and the doze feature would make a decent amount of difference but it hasn't. I have included the screen shots. This is snapshot of about 25 min or soo of betterbatterystats.

Using Greenify, Amplify, Net Guard, Naptime and Powernap.
[T-Mobile Samsung Galaxy Note5] jasons1004:
Sky-high 3.1 Kern.....

.....currently running 6.0.1 extreme debloat rom.

Big CPU 600-900

Little 300-1104

Both undervolted by 4 clicks(bus also)

GPU 160-600(undervolted 3clicks)

Multicore 3 options enabled.(pewq etc)

I think that's it...gets me about 7-8 sot with moderate to heavy usage.

(lots of music/YouTube/chrome/metal(Facebook alt)

No noticeable lag really.

Also with Greenify(aggresive doze setting)/naptime app

Always on battery saver mode too.
[T-Mobile Samsung Galaxy Note5] steve97ta:
Is it a comeback? Got tired of stock settings lol. I'll leave this here. Running Tmo 3.1 build

https://www.dropbox.com/s/3illkgw9mn6kahf/Underdog.txt?dl=0