yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] decimalman:
Long story short, it's a hotplugging conservative governor, similar in concept to (and inspired by) ktoonservative. There's a few things about ktoonservative that I wanted to improve on. I mostly fixed them, but there's still a few tradeoffs vs. ktoonservative.

It uses a much slower sampling rate than ktoonservative. To compensate, it doesn't step up through each frequency. It estimates what frequency is needed to support current load, and jumps to it. This gives it a similarly fast upward frequency ramp, and very fast frequency decreases when appropriate.

It's also much more aggressive about keeping core 2 offline. It relies on thresholds based on the maximum possible frequency of core 1. This means that it doesn't turn core 2 on unless core 1 won't be able to handle the load alone, and turns it off once core 1 is able to keep up easily.

It ends up favoring lower frequencies pretty heavily, and it keeps core 2 offline a lot. As you'd expect, this occasionally causes problems. Until the changes I made this morning, SNES9x EX was too jerky to play because of the fast frequency drops (it's fine now :D).
[Sprint Samsung Galaxy S III] :
@decimalman Flashed over today's CM10 skank. Will let you know tomorrow night or so how it goes..Tks!:thumbup:
[Sprint Samsung Galaxy S III] galaxys3man30:
Is this the whole kernel or just a governor?

jelly bombed sgs3 jelly bomber 4 life
[Sprint Samsung Galaxy S III] decimalman:
It's a full kernel, built from ktoonsez's github repo. It's actually a couple commits ahead of the latest release.

@mw86 when I started work on dmservative, I did a bit of reading on ARM powersaving. In order to enter a low-power sleep state, both cores have to be in their (wasteful) high-power sleep state at the same time. If there's still any load, one core will always sit in high-power sleep. Forcing one core offline works around this, allowing the other core to enter low-power sleep immediately. A good hotplug strategy will do a lot to help with this (and is a major selling point for dmservative), dramatically decreasing time spent in wasteful sleep states. I'm not sold on race to idle for a phone's workload, but I will certainly agree that it's worth looking into pairing it with hotplug to get better idle performance and to avoid needlessly running both cores.
[Sprint Samsung Galaxy S III] freecharlesmanson:
Good I got my settings down pretty much, I won't talk about battery life because I think it is impossible to analyze just by the governor especially screen on time, me I use the Bluetooth audio, torque, or just the headset for music constantly so screen is hardly on often but that stuff will chew threw battery. Anyway to the point.... only issue I saw was mention of lowering the sample rate to 10k. I think it's a but of a misunderstanding about reactivity it's a two way street with a down threshold. Even if it is just for one sample that the CPU is unloaded it means racing around the frequencies aimlessly you will actually scale quicker with a moderate sample rate because it is more likely to get an accurate average. I think keep the frequency down is essential and from what I read using the second core power per watt is more efficient at lower clock rates. So me I'm still aiming to preempt with the second core and scale up. So far landing 95%of performance gov performance. I can't uv screws with the Bluetooth audio for some reasons

CONSERVATIVE_SAMPLING_RATE="50000"

CONSERVATIVE_UP_THRESHOLD="67"

CONSERVATIVE_DOWN_THRESHOLD="46"

CONSERVATIVE_FREQ_STEP="5"

CONSERVATIVE_SAMPLING_DOWN_FACTOR="1"

CONSERVATIVE_IGNORE_NICE_LOAD="0"

CONSERVATIVE_UP_THRESHOLD_HOTPLUG="68"

Ktoonservative of course and yeah I know doesn't look preemptive but in function is

---------- Post added at 04:49 AM ---------- Previous post was at 04:42 AM ----------

I've been using that for awhile with no performance issues at all. My scaling is good I use the phone hard though so it's hard tell sometime because it needsall the juice
[Sprint Samsung Galaxy S III] decimalman:
Sorry if I missed anything guys, it's like 7AM here and I still haven't slept. :eek:

@mw86: Both links are full kernels. All parameters are tunable. Until I put out a better description of how they interact with each other, I don't recommend changing up_threshold, down_threshold, or hotplug_up_threshold. These 3 are used to control the way that frequency is ramped up, and can be fussy.

ARM processors have a couple of idle states that they can enter while running. WFI (wait for interrupt) doesn't offer much power saving, but an individual core can enter and exit it freely. Retention offers much better power saving, but both cores have to coordinate & be ready (meaning idle) to enter the state together. Individual cores can be completely powered off, but it takes much longer to resume from the powered off state. On the other hand, having the core 2 powered off means that core 1 is able to enter retention state freely when it's idle.

ktoonservative powers core 2 before it increases frequency, and keeps it on until frequency has been reduced basically all the way. dmservative doesn't power on core 2 until load has increased to 69% (configurable) of the maximum frequency, and powers it off when load drops below 33% (configurable) of maximum frequency. This way, core 2 is powered on/off during load as it's needed.

There are plenty of arguments in favor of race to idle. It's pretty well documented that it can save power by getting the processor back into a low-power idle state. On the other hand, ongoing low-demand tasks will benefit from the power reductions of a reduced frequency. I simply haven't explored the effects of high frequencies thoroughly enough to endorse race to idle on a phone yet. I'll have to look into combining it with hotplugging to allow retention state as much as possible, which I think could be a good way to get optimal performance with good battery life.

@freecharlesmanson: I don't like measuring with screen on time either, but it's the accepted metric. I usually end up with about an hour more active time than screen time, which would be a much better way to measure.

Can you point me to an article on the efficiency of a second core vs higher frequency? I haven't been able to find much on the subject. I've been working based on incompete and outdated articles.

Unless I screwed something up in the build, the default sampling rate should be 100k, considerably longer than ktoonservative. The longer sampling rate should allow better estimations, which is important since frequency can change much further every cycle. I've deliberately avoided adding any fancy heuristics to dmservative, but it is smart enough to avoid jumping down to minimum frequency during a momentary lull (it's possible for it to jump from 1512 to 384 in one go, so it's important to be smart about this).
[Sprint Samsung Galaxy S III] freecharlesmanson:
The default values in ktoonservative shouldn't be weighed in it's behavior such as hotplug threshold or sample rate you can make the second core do what ever you want more or less including preempt scaling directly. And you could just set the sample rate to 100k as well. As far as frequencies go I'll try to dig up the basics later but it's a matter of physics every time a gate ie transistor opens and closes it creates a small amount of heat and takes a small electrical charge. You do that extremely fast, the faster you do it means the quicker the heat it created and that means dissipates not quick enough as it heats up resistance increases also transistors have a latency to which they can open and close the closer you get to that limit the more inefficient it becomes the resistance goes up and so on. Which derives the need for higher voltage in each step

---------- Post added at 12:24 PM ---------- Previous post was at 12:18 PM ----------

I tested the hot plug out function for ktoons once but found that it caused latency on initial load. Basically if something intensive loads the CPU to 100 and stays there a very brief and occasional stutter. The only thing if point out about running core 2 preemptively is if it isn't loaded pretty fully then it being on is a waste of power but power per watt it is more efficient
[Sprint Samsung Galaxy S III] freecharlesmanson:
I am aware it's in micro seconds.

And am familiar with load approximation I my self don't see your logic but best of luck I guess it's a hell of allot better then those tools using wheatlyor ondemand or some other.. I do like the idea of racing to idle quickly though. Personally I think if ktoonservative could have a more aggressive down step method it would benefit very similarly
[Sprint Samsung Galaxy S III] mw86:
Im with you maybe you could work on something with Ktoonsez again someday. Been your biggest fan of Ktoonservative.

Using this now its pretty responsive and i am not worried on battery life. Im just going to keep trying more combos. Thanks freecharlesmanson its handling good on 50k sample rate.

Edit: I read what you posted. Very accurate in how things are. I asked Ktoonsez to make a governor very similar to yours based more on Ktoonservative though. All it did was add hotplug down to the existing tunables. Tunables are there for a reason. Freecharlesmanson and I know the extent of what changes these tunables make in Ktoonservative and other governors and is not hard to grasp. I just wanted to understand how you designed yours to run. I mentioned an ideal but was just a thought and not my requirement. I want to try, learn and observe many governors to find one that suits my needs. I can adjust from there. I prefer governors I can make my own. Ktoonservative and many others can be tuned for performance or battery or a little of both. Change when hotplug occurs or up threshold of a frequency and its a whole new design. Put one before the other or vice versa and they have different intentions. Your governor has potential and has its own unique place amongst the others. I still prefer the freedom of varying the tunables for my own uses. You can adjust yours for higher performance, I just didnt realize most of the premise was off of current or max frequency percent usage, not current single or overall accounting two cores usage. I respect your work. I have watched best i can by cpu spy and seeing current usage and speed all day at a rate of 1/2 a second... Best i can do in status bar at all times.

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] freecharlesmanson:
I can see what he means for sure about trying to increase idle aka deep sleep

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

Although I usually accomplish 70% at minimum in that state it would be good to further accelerate that

Pm you mw86
[Sprint Samsung Galaxy S III] decimalman:
There's method to the madness, I swear. :silly:

I don't think idle states are included in deep sleep stats (though I could very well be wrong), but they're visible in /proc/msm_pm_stats.
[Sprint Samsung Galaxy S III] freecharlesmanson:
Yes that part of the story I do like
[Sprint Samsung Galaxy S III] BaronLager:
I'm getting great battery life with the JellyBomb ROM and included kernel, but I think I can do better with ktoonzeses!
[Sprint Samsung Galaxy S III] decimalman:
Derp. The AOSP kernel includes a file /system/etc/init.d/90cpufreq that I was using to lock the settings I was testing. That's why CPU frequency, governor, etc. won't change, and is probably the cause of a lot of crashes.

EDIT: anyone who has flashed the kernel is encouraged to remove the file manually, as it probably will not disappear until a new ROM is flashed. Sorry all.
[Sprint Samsung Galaxy S III] Dolomitersm:
Using Ktoonservative governor (10/31) along w/ Task & Ktoonsez AOKP (10/31) and getting insane battery life. It's a beast getting over a day of battery w/ moderate usage. Thanks also goes out to freecharlesmanson for putting up the governor adjustments. Wish this kernel was available to put on my girlfriend's HTC One S...
[Sprint Samsung Galaxy S III] freecharlesmanson:
Harass the devs as long as it supports hotpluging the can just compile it in. And the governor needs to spread
[Sprint Samsung Galaxy S III] mw86:
I clean installed my roms latest update on Paranoid Android. Yeah it pretty much random at boot after while wpuld just freeze. I luckily use titanium and keep my backup on external sd. Its forgivable though... Thats what flashing random kernels can do. Best to always be prepared for that. No problems here since I just wiped everything. Its the nature of the game. No worries here bro.

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] Jimieo:
I installed the kernel and had run through my battery quicker than I had expected...

freeza's stock LJ7 ROM with a few theme tweaks I've done myself...

Using noop scheduler and ktoonservative since someone had recommended it to me... Truth is I don't know what I am doing with kernels lol... Learning as I go.

Pretty much everything was turned off... Wifi was used at random times throughout the day.. This device is not activated (yet) so I keep it in airplane mode to avoid battery drain from scanning for network signals... Brightness was at the lowest setting.
[Sprint Samsung Galaxy S III] galaxys3man30:
Ktoon kernel don't like tw rom for some reason they can't figure out how to make it better but they r working on it hard thou but I had the problem u r having with the battery I tryed letting it settle for 4 days n still didnt help for me but other people says it works just fine foe them but best of luck bud

jelly bombed sgs3 jelly bomber 4 life
[Sprint Samsung Galaxy S III] Jimieo:
Did you end up going back to stock?

Battery fully charged.. Played 3 levels of Angry Birds Star Wars and my phone is ridiculously hot.. Anyone else have that problem?
[Sprint Samsung Galaxy S III] mw86:
I responded in other thread but another thing is our gpus do happen to get stupidly hot. Hotter than i would of thought a phone should get on a game. If its running max stock speed in whichever governor than its going to be very hot with the gpu running too.

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] Jimieo:
Answered there, but in case you're still here...

noop scheduler, ktoonservative gov min 384 and max 1512... I just disabled the touch boost.
[Sprint Samsung Galaxy S III] mw86:
Answered there.

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] freecharlesmanson:
That's not true it's qos does i tried it out on tw worked fine , frankly you are posting all over looking for a hand out or something you need to do some testing of your own you likely have a hardware problem or a SD card malfunction
[Sprint Samsung Galaxy S III] Jimieo:
Assuming that was meant for me since I did post in two threads about this kernel. Two threads hardly counts as "all over." Especially when both threads were intended for this kernel. Handouts? I don't recall offering to give someone my phone and do this for me. Yes, I am seeking advice and reading where I find help. Like this thread.

I love this community, but it truly amazes me sometimes how when someone seeks guidance in a new area or simply asks for help/advice some talk down to that person and assume they just wait for someone to give them the reply they need.

When it comes to kernels and governors and the rest of it, I am in uncharted territory. I am definitely going to ask the "locals" for advice before I try something on my own, no matter how many survival guide, or in this case references threads I read.
[Sprint Samsung Galaxy S III] freecharlesmanson:
I told you earlier what to do. You need something much more detailed you need to examine you CPU states,and kernel alarms. I truly doubt you have a software issue however it's almost certainly hardware

If it's software though seeing alarms and CPU states is almost the whole story
[Sprint Samsung Galaxy S III] mw86:
Coming from a neutral state Galaxysmans reply was answered by Freecharlesmanson and seems to me was correcting the misinfo of qosmgr to him. I think Galaxysman understood. The advice given to you though was to get better battery stats from the market place to see if its not how the governor, io scheduler or anything else is set but a rogue process or similar.

Lol. CANT WE ALL GET ALONG? we are all friends here. I hope it works out. Evem try OSmonitor one i use shows all process running and can show hidden system ones like those starting with com. Etc

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] galaxys3man30:
Dang I was just stating my experience that's all my bad if made anyone mad wasn't trying too I'm not saying its the kernel or tw it could be my phone I may have a problem with it I know they had a problem with gomgr I know this mw86 n ktoon worked on it I'm not asking for a hand out or anything n I did testing of my own so don't think I didn't do anything to try to figure it out I was just saying that they still working on it I think butbim sorry if I made anyone mad wasn't trying to start a fight or down n devs or nothing I have a respect for all the devs on here n I just to get along on here

jelly bombed sgs3 jelly bomber 4 life
[Sprint Samsung Galaxy S III] onenightstand:
i dont konw why my phone still has a andorid system more than screen.
[Sprint Samsung Galaxy S III] freecharlesmanson:
dunno what did you do with it, if iplay ahour or two of Bluetooth audio media server and ancilary processes in Android take up more then screen time usually
[Sprint Samsung Galaxy S III] mw86:
Try suggestions abkve and get better battery stats. See if anything specific is running too much.

Galaxysman no problem. At this point theres no fix in the future. If your on touchwiz jelly bean with the qosmgr issue you have to rename the file to something like qosmgrbackup. Any name really will work. Problem is simple its a quality of service manager and is actually pointless on a phone. Most devs like Ktoonsez said it has no point being there and just causes probs. When certain custom kernels are loaded on jelly bean touchwiz for some dumb reason it activates and wont go away. Renaming it is the only and simplest fix. I wish i could say me and Ktoonsez has a perm fix but we don't. Credit goes to Ktoonsez it was his suggestion.

Edit: Ktoonservative ftw!

Freecharlesmanson gave me some great suggestions I think he has been working hard figuring better values for thresholds. 96-2106 stock volt

Battery pic not for battery but to show phone use.

With lower down threshold i was using too much upper frequency and freecharlesmansons latest suggestions really seem awesome to me.

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] galaxys3man30:
What is that at the top

jelly bombed sgs3 jelly bomber 4 life
[Sprint Samsung Galaxy S III] galaxys3man30:
I'm running noop n intellidemand 144 to 2106 50 UV n off screen 144 n ktoonznation

jelly bombed sgs3 jelly bomber 4 life
[Sprint Samsung Galaxy S III] freecharlesmanson:
It's your WiFi. Although you should give the mods to ktoonservative a try it's much much more aggressive at battery saving still performs tip top
[Sprint Samsung Galaxy S III] galaxys3man30:
Like right after I posted those pics my phone goes into random boot loops I could turn my screen on nbturn it back off it would reboot I tryed turning the voltage back up to stock n it still did the same thing I tryed different govs n everything my wasn't hot so I know it wasn't over heating I just went back to a stock kernel I will do some further testing tonight thou when I get home

jelly bombed SGS3 jelly bomber 4life
[Sprint Samsung Galaxy S III] mw86:
Setting volt back to stock still gives boot loop means volts didnt reset. Try clearing Ktweaker data in app info. Then reboot make sure all says default and start over. You want no issues on undervolt try no higher than - 25mv at first. Im sure its only a few frequency causing that issue.

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] galaxys3man30:
Yea I went back when it was doing it but I didn't clear the app data I will do this when I get home at work right now thx for the help guys its greatly appreciated

jelly bombed SGS3 jelly bomber 4life
[Sprint Samsung Galaxy S III] galaxys3man30:
If you could repost the mods for me n I will try that too

jelly bombed SGS3 jelly bomber 4life
[Sprint Samsung Galaxy S III] tlrsax54:
I always got reboots using the screen off profile...I quit setting it and never had the problem again.
[Sprint Samsung Galaxy S III] freecharlesmanson:
Repost what?
[Sprint Samsung Galaxy S III] galaxys3man30:
the mods u did sorry should have said that my bad

jelly bombed SGS3 jelly bomber 4life
[Sprint Samsung Galaxy S III] mw86:
What governor were you using for screen on and off and did you have any undervolt set? Normally that shouldn't happen so one of those could be the culprit. I use screen off profile even Ktoonsez.

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] freecharlesmanson:
No no ktoonsez, he wrote new features into the governor in his kernel
[Sprint Samsung Galaxy S III] galaxys3man30:
oh OK I gotcha now bud thx I still haven't put the kernel back on my phone yet got a sick 6 month old had my hands full

jelly bombed SGS3 jelly bomber 4life
[Sprint Samsung Galaxy S III] mw86:
Sorry to hear that I hope your kid has a quick recovery.

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] galaxys3man30:
thx bud I greatly appreciate that

jelly bombed SGS3 jelly bomber 4life
[Sprint Samsung Galaxy S III] Logix:
Hey so is 5 hours for 40% battery good? starting at 50 percent? im using wheatly and i underclocked a **** load but that dosent matter because i mostly stay at the lowest mhz.Almost all my battery drain is no signal :((((( and wifi and can you under clock down to 100 and is it stable and whats a recommended a UV level for the lower MHZ? some one has to have some good proven settings by now.

Mw whats your set-up? any reboots or lock-ups
[Sprint Samsung Galaxy S III] freecharlesmanson:
Well the kernel supports 96mhz. I wouldn't go more then 75MV down on it.

Yeah if you clock down enough. I couldn't take the performance hit my self
[Sprint Samsung Galaxy S III] Logix:
so its stable to 96 what u have your mv at? im uv down pretty low at least to the point i consider stable only thing i noticed is some times it doesnt wake

what kinda battery life do you get?

and can you post k tweaker settings backups with pictures?

i want a super low uv and uc thats known stable on your device i know all chips are not the same i just want it as reference.
[Sprint Samsung Galaxy S III] freeza:
Between 96mhz and 486 is no difference in mv. If anything you're wasting battery by having it run so slow. It takes longer to complete tasks than it would at 486mhz using the same voltage.
[Sprint Samsung Galaxy S III] freecharlesmanson:
Yeah he is generally right, 192 is as low as I'll go for that reason there is enormous processing difference.

If You Really don't care about the performance though you should try taking ktoonservative and setting it to about

80 up 60 down 55ksample rate 3step freq

And 75up 55 down for hotpluging

I think it would sacrifice performance but would of highly restrictive scaling
[Sprint Samsung Galaxy S III] Logix:
I'm using a little less aggressive 50k samp I'll post my backup and setup after today