yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Oooh i get it yes very similar to turbo but on a single A57 core thats actually a very good idea man we already have the A57 core 4 on anyway it just needs to be utilized
[T-Mobile Samsung Galaxy Note5] CanMan1:
Yes, and the A53 staying off most of the time instead of staying at 1500 when the A57 is active should save battery. Samsung decided that the A53 should stay at 1500 when the A57 is active which I think is a waste of 1W of power.

The reason Turbo performs better is because of big little migration latency. If latency didn't exist, then using the lowest frequency, little cores, and highest load thresholds would be best.
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Let me revert to 4.2 because i might be able to achieve this on that it has allot more control over the kt gov
[T-Mobile Samsung Galaxy Note5] CanMan1:
For the purpose of sharing with others, it would be better if you can do this on the latest kernel because I doubt most people will be on or revert to 4.2. But if you can make a very efficient profile, then I'm sure some people will switch back to 4.2.

Once I'm done the PCMark for Android tests I have planned, I'll try tweaking ktoonservative with you. If you have good results (with evidence), I may do a preliminary battery life test so you can see time in state and etc

Let me know how it goes so I can give suggestions. I'm looking forward to your results
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
While on 4.4 i have 1 A57 core running and 1A53 shared load still trying to get it just right and test then ill post amd revert and do the same on 4.2

---------- Post added at 07:02 AM ---------- Previous post was at 06:59 AM ----------

Thanks mate ive already managed the A57 core taking load just a single core but i need to getting butter smooth and test it out
[T-Mobile Samsung Galaxy Note5] LiL_Assassin:
4.5 is out if you didn't know.
[T-Mobile Samsung Galaxy Note5] CanMan1:
Try getting the A53 to shut off completely during screen on except when load is high (launching app). During screen off, A57 should shut off and stay off (super conservative), while the A53 is active when needed (active but allowed to deep sleep)

---------- Post added at 11:40 PM ---------- Previous post was at 11:04 PM ----------

Alternatively, try keeping one A53 core active for low load tasks (video?) while 1 A57 core stays idle but on
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Trying to keep most load on a single A57 core shutting down the entire A53 is impossible even with multi core so will need to keep at least one A53 active but idle and using it only under high load (as you suggested) so far i have managed but its really laggy but i haven't lost a single percent battery and since most frequency control have been removed achieving smooth results on v4.4 is proving difficult ill need to revert back to v4.2 to get this it has allot more control that can be fine tuned and have smooth (turbo like) performance while draining minimal battery your idea is pure genius man let me download v4.2 and if your idea proves to have good performance and good battery life (which im sure if both of is work on it we will get it right) maybe uita could even implement it on next release as a kt turbo mode
[T-Mobile Samsung Galaxy Note5] UpInTheAir:
Didn't you read the change-logs? I won't be intentionally adding any more "buggy" governor Synapse controls. . . .
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
you don't have to add or remove anything you don't want to. its just suggestion not a request i like tinkering messing around no one has to fine tune anything i had said it earlier you have the gov well tweaked already. all we are doing here is trying something new and different [emoji12] [emoji16] [emoji106]

---------- Post added at 09:50 AM ---------- Previous post was at 09:09 AM ----------

Sure enough i have a break through v4.2 let do some tests then ill post link here or through pm to profile and you can also have a go
[T-Mobile Samsung Galaxy Note5] Лithium-Фusion:
Oh man truly right, Im getting weird lags when go back to default settings, I mean weird weird.. Rom or something else dont know. One day I will go back to older version of roms and check this thing. In example; when I scroll down-up in Settings, I see the glitches, that makes me mad in these days. Completely freaked out. But when on Turbo, its OK, no lag and glitch. Thats why I call the Turbo is my best friend lol.
[T-Mobile Samsung Galaxy Note5] lastfugi1979:
Can you give a screenshot of your Turbo setting? Would love to try that..
[T-Mobile Samsung Galaxy Note5] Лithium-Фusion:
Just enabled it :) No tweak. Maybe [MENTION=6980302]CanMan1[/MENTION] has some tips about Turbo mode..
[T-Mobile Samsung Galaxy Note5] lastfugi1979:
and you are using "interactive" gov with all default settings?
[T-Mobile Samsung Galaxy Note5] lastfugi1979:
My stats so far....River rom vol 2 and arter97

I might get around 1 day standby time and 6 hrs SOT.. sounds ok?
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
I had those too forgot how i cured it but it wasn't turbo

---------- Post added at 01:30 PM ---------- Previous post was at 01:29 PM ----------

Probably just uv idk but turbo is only available on interactive

---------- Post added at 01:36 PM ---------- Previous post was at 01:30 PM ----------

Update i was having trouble getting A57 core to increase frequency from 800mhz turns out the A57 doesn't need to increase frequency to scroll through pages at 800mhz is enough to keep the whole phone running smoothly i had to underclock it to get enough load on so that it increases wow i feel like an idiot also success i am running the whole device using only a core per cluster thats core number 4 and core 0

Woot woot

---------- Post added at 01:41 PM ---------- Previous post was at 01:36 PM ----------

As soon as i get the A57 cluster to fire up cores when say loading apps ill post the profile here and any one on 4.2 can test out and give feed back

Edit and contribute to tweaking i dont have it exactly where i want it to be but i wouldn't mind any helpful input from anyone till we get it perfect [emoji16]
[T-Mobile Samsung Galaxy Note5] Лithium-Фusion:
Yeah, thats all I did.

Quite good :) At least for me..

I dont know, if you remember that I've posted a screenshot of my 3 offline cores before the version which has Ktoonservative support. Yeah, I was using my device with 5 cores online and underclocked as well. Eventhough no glitching, lagging etc. In these days phone is getting warmer than usual with the same usage and I cant see any reason for it :eek: or im getting moron to not see that.. Default or underclocked/volted just getting warm.
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Is it getting warm now or before when using 5 cores i didn't shut down cores in the multicore i used the kt gov so that it favors one a57 core over all a53 and when necessary will fire up all cores but only under massive load [emoji16]
[T-Mobile Samsung Galaxy Note5] Лithium-Фusion:
The warming is now happening. I tried all governors and uv/uc/oc options before. My device never has been getting warm like that before :D Maybe I need to stop flashing something and let the phone get some rest, need that for myself too.
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Revert to an older kernel i felt thay too on 4.4 to be honest
[T-Mobile Samsung Galaxy Note5] Лithium-Фusion:
Before reverting, just undervolted to my usual(14 steps for a57-53, 7 steps for rest).. I'll check what happens.
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Try that maybe it will it will help also try lower your thermals i guess but i don't think it will probably just make your device throttle badly if its still heating up [emoji33] [emoji34] [emoji35]
[T-Mobile Samsung Galaxy Note5] steve97ta:
Showing some Interactive love aka Interbeast. Great speed and so far good on the battery as well.

https://www.dropbox.com/s/wuvwyzed3o1fwi4/Interbeast.txt?dl=0
[T-Mobile Samsung Galaxy Note5] Лithium-Фusion:
Sorry, I see nothing in Interbeast.txt, have you deleted or something?

EDIT: Anyone can share section of wakelock control, WiFi DTIM Interval to better deep sleep, thanks in advance.

My stats:
[T-Mobile Samsung Galaxy Note5] steve97ta:
Weird its not letting me restore it either. Guess I'll clear Synapse data and start again......
[T-Mobile Samsung Galaxy Note5] lastfugi1979:
you guys are turning the heat ON!!!! :p
[T-Mobile Samsung Galaxy Note5] Лithium-Фusion:
Because, your profile hasnt saved by Synapse. Once had this, try to backup with another name or its probably sqlite thingy.. After tapping the backup button, check the notification popup ;)
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Or maybe he used dots and symbols
[T-Mobile Samsung Galaxy Note5] Лithium-Фusion:
Yes thats it, they sometimes dont let the synapse back up. Checking the notification is a good reason for it :D
[T-Mobile Samsung Galaxy Note5] steve97ta:
I must have lol. I cleared the data but I think it may be the new build not saving the profiles
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
4.5 sh is out

Im still 4.2[emoji16] love messing thing up
[T-Mobile Samsung Galaxy Note5] CanMan1:
I had the same lag/freezing before Turbo.

Reset all CPU and Multicore settings to default. Then enable Turbo and Power Aware Scheduling. That's what I use.

The performance interactive governor profile didn't have any effect on PCMark for Android scores. So I leave it on default for potential battery savings.

Yes. See above

There's a battery life thread for this.

http://xdaforums.com/showthread.php?t=3183142

This thread is for synapse tweaking, so I don't think arter97's kernel is relevant.

Turbo is the culprit. The A57 uses more power (up to 5.5W, 4.5W UVed -87.5), so there's more heat to dissipate.
[T-Mobile Samsung Galaxy Note5] Лithium-Фusion:
Yeah just checked it with 4.5. I took a new backup but file size is 0.. Weird. :D

But heating with defaults too...
[T-Mobile Samsung Galaxy Note5] CanMan1:
Is it possible to favor the A57 core(s) over the A53 core(s)? This will help with performance.

When loading app, all cores should be active.

Before posting your profile, benchmark it on PCMark for Android and post the results so we can see how it compares to stock.

The main thing that may make ktoonservative perform worse than interactive is the latency from turning cores on and off

---------- Post added at 10:37 AM ---------- Previous post was at 10:32 AM ----------

Are you at throttling temperatures? Some numbers would be helpful. Use my cool tool profile to see when you're device gets hot:

http://xdaforums.com/showthread.php?p=64980886

During certain activities (app updates), heating up it's normal. Basically anything that loads the A57 constantly will heat up your device

---------- Post added at 10:44 AM ---------- Previous post was at 10:37 AM ----------

Looks like 4.5 will be the last build for lollipop
[T-Mobile Samsung Galaxy Note5] Лithium-Фusion:
What does 'Throttling temperatures' mean? I took this screenshot yesterday. Now seems running lower. About 40- 50 'C.. I've never touched thermal throttling values ever btw.. It used to running at 30-40 before the ''milestone''
[T-Mobile Samsung Galaxy Note5] steve97ta:
I'm back on 4.4.1 and its saving just fine thanks for confirming
[T-Mobile Samsung Galaxy Note5] Лithium-Фusion:
I think, the time is too late to mention UITA and report that, if its the same to others too. Any changes about it in Github? I will check it too but im really bad at reading gh changelog, no matter its easy or not. :sly:
[T-Mobile Samsung Galaxy Note5] CanMan1:
The A57 throttles to 1704 at 80*C with default settings and further if high temperature are sustained.

Your CPU usage is high in that screenshot, so you should see high temperatures.

Use this app to see what's using your CPU and thus causing your device to heat up:

This one can show native Linux processes

https://play.google.com/store/apps/details?id=com.eolwral.osmonitor

This one might be limited to app usage, but it can monitor in the background and has more features

https://play.google.com/store/apps/details?id=com.cgollner.systemmonitor
[T-Mobile Samsung Galaxy Note5] steve97ta:
If you try to restore it gives the sqlite error so I'm going to try whats in his OP
[T-Mobile Samsung Galaxy Note5] Лithium-Фusion:
Umm. Then its already known. I think I havent removed sqlite file from /system/xbin after updating the rom yesterday night.. Gonna try. Thanks.
[T-Mobile Samsung Galaxy Note5] steve97ta:
yeah I removed both and cleared data yada yada then reflashed everything is working again
[T-Mobile Samsung Galaxy Note5] Лithium-Фusion:
Lol, poor me. I hope UITA doesnt look the previous posts :D
[T-Mobile Samsung Galaxy Note5] steve97ta:
Here we go. .. https://www.dropbox.com/s/txo5wukw0yjo70j/Interbeast.txt?dl=0
[T-Mobile Samsung Galaxy Note5] hawkstwelve:
Can someone explain to me what HPM Voltage Control does in Synapse? I went from knowing nothing about voltages to being able to understand more and more (and tweak more and more) all thanks to you guys and this thread but I still don't fully understand what that does? I saw Konsstantine (I think it was him) posted a 'beginner' video for voltages and he puts the HPM all the way down to 0 - is this something you should do if you undervolt, no matter what?
[T-Mobile Samsung Galaxy Note5] UpInTheAir:
No comment. .... :)

There's a great article by AndreiLux linked in my kernel thread Post #3. There are a number of sections. HPM is covered ;)

I would really suggest for anyone to take the time and read every section, even if all isn't understood, but knowledge will be enhanced ;) There's no need to regurgitate it . . .
[T-Mobile Samsung Galaxy Note5] CanMan1:
http://www.anandtech.com/show/9330/exynos-7420-deep-dive

http://www.anandtech.com/show/9330/exynos-7420-deep-dive/5

Start by setting it to 0. When UV maxed, increase it linearly with voltage for more stability.
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
I had also mentioned it's might have reached thermal throttle because with me even on 4.4 my phone was running hotter then normal on github its mostly cortex brain fix

---------- Post added at 04:51 AM ---------- Previous post was at 04:41 AM ----------
[T-Mobile Samsung Galaxy Note5] CanMan1:
I haven't really tweaked ktoonservative before, so it might be awhile before I can do anything with it.

---------- Post added at 01:58 AM ---------- Previous post was at 01:56 AM ----------

Have you tried turning on Turbo with ktoonservative? I'm curious if it has any effect. It could help with forcing the A57 to be used
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Turbo is interactive only cant be run on ktoonservative thats the effect i was aiming for on the kt gov to have a turbo like effect but with the turbo drain

---------- Post added at 11:33 AM ---------- Previous post was at 11:31 AM ----------

So far ive managed to move load successfully onto A57 without the need of the A53 core im posting now then you can give it a go im still working on it to make more battery friendly i think i can get more out of it

---------- Post added at 11:38 AM ---------- Previous post was at 11:33 AM ----------

https://drive.google.com/file/d/0B8Ps-jVB8IblTVJMQ1habUR1b0E/view?usp=docslist_api this is a very early stage of tweaking im jusy posting for anyone who wants to have a look and test it out any input would be helpful and tweaking to perfect ALSO V4.2 sky only i can't get the results im looking for on newer versions im still trying to this just right so any help is greatly appreciated

---------- Post added at 11:45 AM ---------- Previous post was at 11:38 AM ----------

Btw this is like a turbo ktoonservative profile what it does is shift load onto A57 cluster leaving the A53 cores mostly offline (only core 0 remains active) its smooth and should be battery friendly but its not tested i just finally managed to get working
[T-Mobile Samsung Galaxy Note5] Rx8Driver:
I'm not sure turbo is the culprit, i was having heating issues on 4.4.1 without turbo......

Edit:: i found the cause of my heat issues- hardware issue with my usb, some moisture got it somehow and made my usb think a gear vr was plugged in, in the background, was running my Wakelocks wild and making my device heat up and trigger thermal to 1704 of a57....i think i got the issue ironed out, thank you Mr $8 Heat Gun ;)

---------- Post added at 07:39 AM ---------- Previous post was at 07:26 AM ----------

I just want to tell everyone here [MENTION=6311359]muffinsmuffy[/MENTION] [MENTION=6980302]CanMan1[/MENTION] and everyone else that this is one of the best threads I've followed in a long time. Unfortunately, this past month i haven't had the kind of time i used to have to contribute, but sporadically, and that's going to change over the next few weeks as my schedule settles down and leaves me more time to test n tune....but in my absence you guys have done an amazing job of further our understanding and getting some really cool results! Well done!
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Awww thanks mate [emoji106]
[T-Mobile Samsung Galaxy Note5] CanMan1:
I jumped to a conclusion too quickly there, but then I replied with instructions for determining what process is causing high load. But your situation is an odd one that I think only you could have figured out.

I'll repost it with the voltage lines removed, then I'll compare performance to Turbo in PCMark for Android.

I'll also try reducing the profile to just the ktoonservative settings.

Once you post a more complete profile, I'll do a work battery life comparison.

---------- Post added at 10:58 AM ---------- Previous post was at 10:46 AM ----------

I've got close to 10 more work battery life tests to run. My phone is getting tortured ;)
[T-Mobile Samsung Galaxy Note5] nahsen27:
Mate have you interactive profile?

sorry my english
[T-Mobile Samsung Galaxy Note5] CanMan1:
Reset all CPU and Multicore settings to default. Then enable Turbo (CPU gov Tab) and power aware scheduling (Multicore Tab)

PCMark Work Battery life score:

~6300

7h

[MENTION=6311359]muffinsmuffy[/MENTION] See attached and below

I suggest a version system so we can track changes, so I've relabelled your profiles with 1.0.0 and a more descriptive name. Explanation:

*.0.0

The first number is for major revisions (eg. starting fresh or having a different goal)

1.*.0

The second number is for revisions

1.0.*

The third number is for minor revisions (eg. fixes or reverting changes)

1.1.0a_1.0.0-Based

The "a" means it is fork "a". All profiles with that letter are based on "1.0.0-Based" and should have that in the name for reference. Forking should be used when your just trying things and don't want to merge it in the main profile (in this example 1.1.0 is the main profile). It can also be used when more than one person makes changes to a profile and posts them.

The name of the profile should have a brief description of the changes. And when sharing it, the post should have a list of changes unless it is a major revision. Some examples (not perfectly labelled):

11.0.0_Universal-Based_Performance_Turbo_A57.txt

11.0.1_Power_Aware_Scheduling.txt

11.0.2_A57-m800.txt

11.0.3_A57-Default-Gov.txt

11.0.4a_Logs.txt

11.0.4b_Logcat-Auto-Suspend.txt

11.1.0_A57-M1704_A53-M1296.txt

11.1.1_GPU-M600.txt

11.1.2_A57-m600.txt

11.1.3_A53-M1000.txt

11.1.4_GPU-m100-HS160.txt

11.2.0_11.0.3-Based_A57-m600_GPU-m160-HS266.67.txt

If you can suggest a better system, then I'll relabel the profiles.
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Lol my first 9 test were canman1 kt test [emoji16]
[T-Mobile Samsung Galaxy Note5] CanMan1:
First results are really bad. Before sharing another profile, make sure it scores at least 5000 (stock kernel), or preferably ~6000 (Turbo)

https://i.imgur.com/1th2IHa.png

Now I'm feeling quite pessimistic about ktoonservative out performing interactive overall. Maybe the added latency isn't worth the extra power savings from shutting down the cores, and the interactive WFI C state is already very good at saving power without much latency.

I think interactive with turbo will continue to be the overall best for performance and battery. Especially when you consider that it only takes 10s to configure correctly.
[T-Mobile Samsung Galaxy Note5] muffinsmuffy:
Possibly correct my main problem was getting the A57 core to take over iu fast enough to keep up with ui input so i had to keep it checking for input rather rapidly which will effect battery dramatically hence that profile was not close to a final release it was just a test to see if it can be done shift load to A57 im starting from scratch now rebuilding on what ive learned from the A57 response time and how it behaves the kt gov has allot of potential more then i imagined the A57 cluster can handle video playback at 500mhz and iu input as well on a single core its truly amazing how powerful that cluster actually is having it scale up to 2100ghz is a huge waste of power with proper gov optimization i think we get increase in battery far beyond what interactive is capable of

---------- Post added at 11:16 AM ---------- Previous post was at 11:12 AM ----------

Ive seen in your graph that the a57 maxs out at 1.6ghz which the same result i was aiming for i don't want it ramping frequency to 2.1ghz so success i had to work out allot of kinks to get it [MENTION=1247388]1.6[/MENTION]GHZ will lower it a tiny bit and before firing up another core it call on the A53 core 0 work in progress have faith we will get it right
[T-Mobile Samsung Galaxy Note5] CanMan1:
I forgot to mention that I only restored your governor tunables since that is what I wanted to test. All other CPU settings were stock.

The problem with lowering minimum frequencies is that it reduces responsiveness (PCMark scores) because of switching frequency latency. Latency must be considered when tuning. The potential advantage of lowering min frequencies is lower power consumption during Low constant load (Eg video). But given that Turbo uses ~1.65W average in PCMark (11.55Wh/7h), the extra power savings should be calculated before deciding if it's worth it.

1704MHz would be a better (4/3 core) choice based on the power consumption curve. But single core and Multicore power consumption curves are different (see AnandTech). The advantage of using a single core is the mostly library 3 increase in power consumption. This allows you to use the max frequency with almost no loss in efficiency.

500 on the A57 seems like it would be slightly less efficient than A53 1000MHz.

Lowering the max frequency affects UI responsiveness, and power saving mode has the same effect (based on my testing). So I prefer to use power saving mode when needed for a small efficiency increase. Racing to idle is another reason why manufacturers use high frequencies that use more power.

Reading and understanding the article by Andrei will help with CPU tuning:

http://www.anandtech.com/show/9330/exynos-7420-deep-dive/6

I think ktoonservative will offer little to no benefits over interactive. And since the tunables of 4.2 will not be included in future kernels, it might be a wasted effort that could be better spent tuning interactive.