yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] fluk321:
Thanks !!

mw86, thats helps and explains alot, I was getting lost in translation on a few post, just basically trial and error, but now I have something more to make my adjustments. Does anyone ever toy wit I/O settings when using Ktoonservative governor ? I think pretty sure i'll be using this kernel and governor for awhile, and im late on learning these things...
[Sprint Samsung Galaxy S III] mw86:
I check for pms from you or ktoonsez etc daily. Im not seeing a new pm can you resend it buddy?

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] 02bugeye:
Hey mw86 what's your battery like with the setup your running?
[Sprint Samsung Galaxy S III] mw86:
Its been good for light use of phone and better than it used to during heavuer use as i was getting a lot of peaks into max speed even if it wasn't a very heavy task. For light browsing i usually see around 96-384mhz and bumps up for random loads. I will need to disable a few monitoring tools i have going all the time while getting settjngs settled. Seeing whats happening in everday tasks is important when honing in settings.

I have a Onite extended battery I use most of the time so if i post a battery life pic its harder to compare... The battery lif at idle when i dont use phone is like Freecharlesmanson barely a percent in a few hours if no radio is turned on atleast 3 hours+ with voice radio still on assuming i didnt use phone much so screen didnt effect drain.

I have the non nfc capable Onite 4500mah battery. It has been reviewed bad but I under even heavy use can get well into 7+hours of screen on per charge no idea under this new setup with just light browsing right now... So if you want to see a battery run on it i would have to start that tommorow with no monitoring going. I had posted some previous battery stats in this thread or the other Ktoonservative thread.

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] 02bugeye:
Thanks for the reply. Yeah I saw your post after I wrote this lol. I just want something that performs well but doesn't kill my battery a nice happy medium. I have mine set at bfq and intellidemand right now and battery life seems pretty good. But I'd rather have something that's been tweaked.
[Sprint Samsung Galaxy S III] mw86:
Its worth a try the performance is there when necessary on this but sticks with lower speeds so battery is definitely there. How bout save your settings for intellidemand if using custom ones by taking a screenshot of your values. Load mine up the last one i posted but for it to work for you ir for me to suggest a frequency step percent you or i need to know your minimum and maximum frequency you want to use. Using my config or freecharlesmanson's doesnt require you to use our min or max but will need to have frequency step adjusted for the type of stepping you want to use. If you want to use each frequency in between min and max when needed then frequency step needs to match a balue that will work for the frequencies you choose to use. I use 96-2106mhz which is the largest span of frequency possible and i use 2%frequency step to hit each frequency if the is less distance on your overclocking then you use a higher percent than 2, if its too low for your setup you skip frequency or frequency cant even move up or down.

So what is your min and max?

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] 02bugeye:
It's set at 192-1728. Gives me that little extra power but not to much. And as for the intellidemand I haven't changed anything so it's not to problem to mess with some settings.

Also thanks for the very thorough reply.
[Sprint Samsung Galaxy S III] mw86:
Here you go you need 3% frequency step i tested using those speeds for you. At 3% you will hit every frequency as the governor uses up or down threshold from 192-1728. As you see in the pic the unused frequencies are the ones not set like 96/144/1800/1890/2000/2100mhz. Let us know how it handles for what you do on your phone. Hopefully you see better battery life. If you think sample rate is too low try 15000/20000 instead.

Heres pics

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] 02bugeye:
Thanks a lot I'll give this a shot and run it for a couple days and let you know how it handles.

One other question do you have touch booster enabled? If so what setting do you use?
[Sprint Samsung Galaxy S III] mw86:
See my post above those i showed my entire Ktweakers config. But to answer directly I use it off so that the obly boosts to cpu are based on cpu usage and not too often since i touch my screen all day i end up with too much use of those touch boost frequencies. If you find when scrolling or interacting with phone its lightly laggy you could enable touch boost and set it to lowest mhz on both. This setup isn't going to score higher than performance but it will limit using to much mhz when it isn't a hard work load. Most times yours should sit around 192-500mhz while surfing etc and higher under load. Nova 3 it isn't pegging at max the whole time so im happy. Feel free to post any pics for us to check out. Good luck i hope it either works just how you wanted or brings you to where you want to be after trying it. Cheers bro. If you find you need much more performance after trying this it can be adjusted for a bit more of that but in particular in that case likely freecharlesmanson's favored settings will be more suitable.

Edit: my mistake thought i was in same thread. Here is where i posted what i use on my phone all of my ktweaker settings.

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

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] 02bugeye:
I'm sure it will work out pretty good. I'll post some screen shots in a few days after its gone through its paces. And like I said performance wise I really don't need it to be crazy just fast enough. So I think these settings will work just fine. Maybe I'll adjust the sampling rate like you said and see how that does
[Sprint Samsung Galaxy S III] freeza:
My settings updated:

Set to run at 1.99 ghz when connected to a charger. That's why the Times are so high on it.
[Sprint Samsung Galaxy S III] mw86:
Nice setup Freeza! Looking good there.

Off a full charge surfed for 30min before bed last night and then unplugged phone at 95%. 8+hours later i check and still 95%. Seems im not getting any excessive battery drain having my second core kick in so often. Still need to get a good frequency table on it.

Ran out of hosting on Tapatalk so here is pic via imageshack

https://imageshack.us/a/img15/277/batteryt.jpg

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] clothednblack:
Love the ktoonez gov, has done wonders for my battery.

Ridin the Mystic jellybean unicorn on my blazing SG3

---------- Post added at 05:15 PM ---------- Previous post was at 04:58 PM ----------

I have noticed that the "down threshold hotplug" doesn't show up for me to have the option to adjust it.

Ridin the Mystic jellybean unicorn on my blazing SG3
[Sprint Samsung Galaxy S III] mw86:
Are you on the latest version of Kt747?

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] clothednblack:
10-22-12 is what my zip says

Ridin the Mystic jellybean unicorn on my blazing SG3

---------- Post added at 06:52 PM ---------- Previous post was at 06:50 PM ----------

Can't find a newer one for us cellular

Ridin the Mystic jellybean unicorn on my blazing SG3
[Sprint Samsung Galaxy S III] freecharlesmanson:
Use photo bucket
[Sprint Samsung Galaxy S III] freecharlesmanson:
Yeah That's Way old you need the new one
[Sprint Samsung Galaxy S III] clothednblack:
Where is the new one for us cellular? I found Verizon and at&t and sprint. Lol

Ridin the Mystic jellybean unicorn on my blazing SG3
[Sprint Samsung Galaxy S III] mw86:
I prefer photobucket. Any easy way to get the share url via phone? I have photobucket app but last i tried it only helped to upload and via browser i had trouble copying the urls, maybe it runs better on android browser now?

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] freecharlesmanson:
No app works flawless even gives you image tags in the link
[Sprint Samsung Galaxy S III] freecharlesmanson:
I think us cell will be either Sprint or tmo but look up there parent company
[Sprint Samsung Galaxy S III] clothednblack:
My zip shows......

KT747-Kernel-AOSP-JB-USC-10-22-2012-2

I give up looking for now, every zip I find is for different carrier's

Ridin the Mystic jellybean unicorn on my blazing SG3
[Sprint Samsung Galaxy S III] freecharlesmanson:
Yes but you either have the same variant as Sprint, T-Mobile, att so likely one is usable with no I'll effects
[Sprint Samsung Galaxy S III] clothednblack:
I get that, just Google like crazy with no straight answer, must be searching with the wrong question

Ridin the Mystic jellybean unicorn on my blazing SG3
[Sprint Samsung Galaxy S III] freecharlesmanson:
Yeah it is just a question of what variant I know people using tmo kernels on the Sprint one, I once flashed an att kernel it just screwed my rotation they are all very close to the same device...
[Sprint Samsung Galaxy S III] clothednblack:
I thought it was at&t, but just tried it and it failed to flash, bad link from the original place I got the version I'm stuck on now. Lol not my lucky day

Ridin the Mystic jellybean unicorn on my blazing SG3
[Sprint Samsung Galaxy S III] clothednblack:
I'm updated, went to the source and got it ;)

Ridin the Mystic jellybean unicorn on my blazing SG3
[Sprint Samsung Galaxy S III] freecharlesmanson:
There ya go
[Sprint Samsung Galaxy S III] asaa:
Quick question... Which would use more power?

Core1 at maximum clock speed but core2 disabled, or Both cores enabled, each at 1/2 maximum clock speed?
[Sprint Samsung Galaxy S III] freecharlesmanson:
Most likely 2 cores, it's a hard question to answer sometimes it's very load specific an single thread UNoptimized would almost certainly manage to do worse on dual core but more often then not Android is pretty multi threaded these days if nothing else the second core will be more efficient by producing less heat
[Sprint Samsung Galaxy S III] mw86:
And to add to Freecharlesmanson's statement you can also consider even though half mhz on each core in the dual core scenario those two cores calculate two things at same time so for example every sec in dual core vs single it can accomplish two tasks at the exact same time where as single core can only process on single thing at one given moment (well it can calculate multiple things byt imagine it is doing it a single file line with no cutting lol)

Now mhz being cut in half will have an effect on speed of the calculation but the much lower milivolt required for half the speed will keep heat down which adds to power consumption too.

There is no concrete answer.

1500mhz single core 1200mv stock

750mhz dual core about 1025mv each while stock.

The dual consumes more mv per sec but calculates faster possibly due to the nature of dual core.

Given long term usage single core likely will use less juice but overal and in short periods of time i do have a feeling the two cores will finish the job faster and return to idle (almost no power draw) well before the single core at higher mhz.

Its all theory and no way to be absolutely sure on any of it.

Edit: actually in using Ktoonservative on my settings i posted i found once dual core activates it runs lower than half the mhz of single core. On my tunables most times all that is needed is 96-384mhz for almost all tasks. Check my frequency tabke of used frequencies as those were the highest used mhz havjng dual core active until idle is reached.

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] decimalman:
For the specific question you asked:

On the S4 processor in the SGS3, one core at 1512 will should use somewhat less power than two cores at 756. However, you'll never rarely see an either-or situation where usage gets divided up 50/50 between cores. Generally an app will either max out all available cores, or it will max out only one core while other tasks execute on the other core.

More generally:

In theory, in a multi-threaded workload it's always more efficient to use two cores instead of one. In practice, it's a tossup. There are some situations where only one core is needed, and others where both cores will save power. As far as I can tell, keeping core 2 off more aggressively can sometimes reduce power use by 5-10%. Factor in everything else using power, and 10% of the (already pretty efficient) processor's power really isn't worth worrying about.

Edit: Don't trust the voltage table. Voltage doesn't correlate well to power usage on our processors, and AFAICT above 1GHz or so the processor outright ignores the voltage setting (hence people able to set their highest freqs to 700mV). If Trepn weren't so hideously broken on our phones, it would be easier to investigate what's actually happening.
[Sprint Samsung Galaxy S III] crazymook:
So whats the scheduler of choice w/ ktoon? ive seen people using cfq, bfq and some mention deadline and sio.

and do you (charlie) have screen off max mhz set to something or do you have that set at default? ive seen 96mhz and 486 mentioned a few times.
[Sprint Samsung Galaxy S III] clothednblack:
BFQ and 96mhz screen off, undervolted on all levels :)

Ridin the Mystic jellybean unicorn on my blazing SG3
[Sprint Samsung Galaxy S III] mw86:
I agree on all of that except the end. The highest mhz available will crash if you use 700mv. Reboot with settings applied at boot retest. I had a situation where early ktweaker didn't apply volts for anything. But when rebooted it set correct and i found plenty can crash if undervolted to much in any range from 96-2106mhz.

Just around 1200-1225mv 2106mhz will just crash and reboot. I'm not going to argue about it i just know after testing thoroughly i know when voltage tables were being used or not. I also know my phone would have issues or reboots untill i brought my voltage back up high enough. I started low on everything and went up.

I definitely agree paying attention to mv per mhz isn't important in discussion of the efficiency of dual core. Its as you say a toss up.

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] decimalman:
It's something weird that was happening to a few people over on the AT&T device thread. Nobody ever figured out a good explanation for it, but it looked to me like the processor just ignored the settings altogether. The guy who reported it posted Trepn screenshots (http://xdaforums.com/showpost.php?p=33835531&postcount=390), and it doesn't appear to have any effect, except that it'll crash most people's phones. :p

I certainly didn't mean to encourage anyone to try running at 700mV.
[Sprint Samsung Galaxy S III] mw86:
Okay cool i see. Im a Sprint GS3 user so for me i have to give the voltage table respect. Many at Sprint thread had to get down whats safe or not as just dropping 75mv across board was too much for most. Many seem fine with 50mv down but i found for mine im fine with 25mv and then a select few mhz 50-75mv at most. Sounds like a bug in something unique to AT&T handsets. Most other users here should be very careful undervolting any of the mhz. Did the same issue occur not using ktweaker to apply the volts and using an alternative overclock program such as System Tuner, Android Tuner, SetCPU etc?

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] decimalman:
I don't think it's unique to AT&T. I'm using a Sprint GS3 as well, and while I can't do 700mV, 900mV works for me. Either way, it obviously wouldn't be stable if it were actually running at voltages like that. It doesn't measurably reduce power consumption either, so I assume that something else is overriding the UV settings for those frequencies.

I didn't see in the other thread whether anyone tried applying the settings outside of KTweaker, but I do my tuning directly in sysfs rather than use a tuner app, and the settings definitely applied.

I went looking through the source code to see if I could find out what's going on, but I find Code Aurora's code to be totally unreadable so I gave up. :(
[Sprint Samsung Galaxy S III] clothednblack:
Us cellular user here and no issues with mine.

Ridin the Mystic jellybean unicorn on my blazing SG3
[Sprint Samsung Galaxy S III] mw86:
I posted in the thread you linked. I spoke of my experience with the issue. To elaborate i did have the issue some time ago on my Sprint handset too but i found a way to check when voltage was being listened to and it works for me now. I posted my volt table there. If i go too far under those i get instability.

Straight up ive had that issue. As of now wroks correct for me but earlier Ktweaker i did have the issue especially when ktweaker didnt exist and i was using system tuner and or set cpu.

Paranoid Galaxy S3 on Tapatalk 2

---------- Post added at 09:45 PM ---------- Previous post was at 09:28 PM ----------

Is it actually applying though? Ive ran this test on those and phone will reboot or crash on mine.

Try this get this app and run the multithread mflops test a few times in row. If no crash try setting max mhz to the min 96-96 in other words and rerun so to be sure governor isnt changing to a frequency not undervolted as much.

The app is Stability Test free from Playstore.

If that doesn't reveal instability try Antutu Benchmark on the cpu tests at the mhz you are undervolting at 700mV.

If you are wondering why bother its because one day you could be doing something important and your phone could just shut off.

Besides the above there is one test i know works. Run antutu at 2106mhz 1350mv and monitor temps on the cpu not battery and then undervolt to maybe 1275-1290mv and also check temps. Battery temp will always be 70-120F and never higher.

Temp Monitor i use to actually see cpu temp but System Tuner is free and works for that too. Now compare temps if volts didnt apply for real you will have the same temps. 1350mv @2106mhz on Antutu easily should be hitting 170-190f and the max you see on 1275-1290mv should be considerably less. If its the same you need to check through and see whats causing it. Could be wiping ktweaker settings may help, reflashing kernel and making sure to use a kernel cleaner may help and beyond that after kernel install and booted to android i cant stress enough to reboot mount all the partitions and fix permissions as most issues arise from not having admin rights of the files involved in the kernel etc.

Im serious that i have tested all this for months thoroughly and this is what ive learned from it.

It is very possible your handset can run that mhz at that mv but how far have you gone to be sure any of the volts have actually applued and effected anything.

Once i was sure on mine i noticed substantial temp drops under load with an undervolt and possibly a battery saving but definitely not something i can say for sure but i know the temp difference was definitely there.

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] clothednblack:
I will look into that ASAP, but no random reboots here

Ridin the Mystic jellybean unicorn on my blazing SG3
[Sprint Samsung Galaxy S III] decimalman:
That's crazy.

Expanding on mw86's post, if you've got a terminal emulator installed, you can also tell whether your voltages are applied with

cat /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

The values it prints are read directly from the kernel, so they're not going to get any more applied than that. :p
[Sprint Samsung Galaxy S III] clothednblack:
Ran both no fc or freeze ups

My other settings ;)

Ridin the Mystic jellybean unicorn on my blazing SG3
[Sprint Samsung Galaxy S III] mw86:
Okay no biggy either way. Thing is if those volts arent applying you wouldn't be getting a reboot it would actually be using stock volts on that frequency... unless you test sometime you cant be sure your seeing any kind of benefit with it set to 700mV. Do you know what i mean? Straight up i simply mean if the voltage table you applied isn't actually changing the cpu's voltage table for real you will see its set to those but it could possibly be using stock. So you don't even have to test but you may want to check into it to be sure you are benefiting from an undervolt at all. If its not setting and just appears to be running that because ktweaker shows it or whichever overclock app then its a placebo effect. As a result of undervolt you should be seeing some kind of benefit either temps, battery life or both. I implore anyone working with an undervolt to try to be sure its actually even working.

How about another test of the theory. You don't need to do this one either just food for thought. Try setting max mhz to a fair level how bout 1000mhz. Now undervolt that to 700mV but be sure Ktweaker temporary is set to not set options at boot. Give a test in that stability test or antutu. If it reboots shuts off or freezes your volts are applying for real. If it doesn't its not working at all. 1000mhz cannot take only 700mV dual core. So do you see what i am pointing out? Every frequency there there is no way it could take minimum milivolt. So if you find they all can take 700mV its not working. In this case you want it to crash or show an issue as thats how you would know its working and you undervolted too far.

Does this make sense? I am asking everyone here actually. Seems to me what i have outlined is a great easy way for any of us to confirm our voltage table is actually being utilized.

Im trying to teach everyone who may be new to overclockimg, undervolting cpus. Its not new to some whom have computers and do the same on them but those who don't do such things this is a whole new world. Respectfully.

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] clothednblack:
Ridin the Mystic jellybean unicorn on my blazing SG3
[Sprint Samsung Galaxy S III] decimalman:
That's amazing. I might just have to see what 96MHz does on my phone. :D
[Sprint Samsung Galaxy S III] clothednblack:
Max at 1000/700mv phone crashed opening the app to test it. I would say my phone does exactly what I set it to do. Thanks for the test's :D

Ridin the Mystic jellybean unicorn on my blazing SG3

---------- Post added at 07:29 PM ---------- Previous post was at 07:26 PM ----------

Btw, I average 15hours of battery life with this set up, and that's what I need. Can't charge at work (I drive a trash truck, no charger) and I use my phone all day

Ridin the Mystic jellybean unicorn on my blazing SG3
[Sprint Samsung Galaxy S III] mw86:
Thank you for entertaining my ideas. You did exactly what was necessary to know. No you can be certain that your using that undervolt for real. Congrats i am happy for you and again thanks for entertaining the idea. Anyone else who reads of this can follow any of the above to check for themselves. I cant say enough... Thank you again for using those theories to test. Great to see some of these S4 cpus are handling so efficient.

[high:five] :)

Now those at the AT&T thread Decimalman pointed out shoukd try similar. If the test isnt crashing for them than they definitely need to look at what could be wrong... Maybe a third party app, permissions not fixed right after kernel install, leftover kernel files... Who knows but i don't think any of the users reporting that issue on AT&T handsets are setting everything up right or to give benefit of doubt maybe something is wrong with the AT&T kernel but my guess is Ktoonsez is very thorough and there is nothing different between the different phone providers Kt747 kernel.

*** as usual Ktoonsez and his kernel rocks!

Btw clothednblack thats one 4ell of a undervolt. Congrats.

Paranoid Galaxy S3 on Tapatalk 2
[Sprint Samsung Galaxy S III] clothednblack:
My pleasure, glad I could help.

Makes me happier seeing confirmation too ;)

Ridin the Mystic jellybean unicorn on my blazing SG3