As the title says, would like to gather your ExTweaks settings. Always looking to improve battery/performance.
What is ExTweaks? From the makers of Voltage Control & SiyahKernel comes a highly configurable kernel tweaker. Requirements at the moment are SiyahKernel 2.6.13 or Entropy's DD 3/5/2012 +. It allows you to change such things as CPU Hotplug, GPU Steps/Voltages, Governor/Scheduler & much more.
Reference on what these settings mean: http://forum.xda-developers.com/showpost.php?p=23616564&postcount=6
Post in whatever format is easier for you. I am currently just listing them from start to end. Here are my current settings: (init.doh 0.4.6b & Siyah)
CPU Tab:
CPU Hotplug Default/50/90/80/100/200/600/1000/600000/AFTR+LPA/0/2/2/2
GPU Tab:
100/160/200/800/850/900/90/55/90/70
Screen Tab:
7/20/0/24
Misc Tab:
Unchecked/500/ondemand/sio/stock
I am aiming for battery with the above tweaks. So what are you currently "rocking"?
Just a heads up, Entropy's DD has been updated (3/5/2012 and Up) to run this also.
I don't have a screen tab on entropys kernel?
Sent from my AT&T cellular device.
jdbeitz said:
I don't have a screen tab on entropys kernel?
Sent from my AT&T cellular device.
Click to expand...
Click to collapse
Probably just something his kernel does not let you configure at the moment.
cwc3 said:
Probably just something his kernel does not let you configure at the moment.
Click to expand...
Click to collapse
That is correct. The idea of ExTweaks is to provide a "universal" configuration app.
Files in the kernel initramfs itself define nearly everything in the user interface - each tab, and each item within a tab.
I can tell you, for example, that the CPU screen has some significant differences from Siyah in my kernel, as I have decided not to include Tegrak Second Core support (It's redundant - the only thing that can't be done with the existing interface is to force the second core on, which is kind of pointless and bad for power management.)
The GPU interface should be nearly the same, but it might change in the future. I'm thinking of changing the down thresholds to "step down target" - Instead of defining it as the percentage load at the current frequency, define it as the target load at the next frequency step down.
I have at least one additional option in misc (Per-File fsync() control) that isn't in Siyah
Entropy512 said:
I have decided not to include Tegrak Second Core support (It's redundant - the only thing that can't be done with the existing interface is to force the second core on, which is kind of pointless and bad for power management.)
Click to expand...
Click to collapse
Been reading up on this myself: http://forum.xda-developers.com/showthread.php?t=1494653
What is your 2cents on hot-plugging?
cwc3 said:
Been reading up on this myself: http://forum.xda-developers.com/showthread.php?t=1494653
What is your 2cents on hot-plugging?
Click to expand...
Click to collapse
I didn't have time to revisit things, but I'm fairly certain, as I mentioned in that thread, that the test was flawed - Plugging in USB appears to fire enough interrupts to block AFTR and LPA from ever getting entered. As a result, one of the bigger power penalties invoked by activating the second core (blocking AFTR and LPA) has already been taken in his tests.
I set second core kickin threshold to 1000mhz and I undeclock to 1000mhz. I set gpu to 100/100/100 @800/800/800. Ondemand governor and noop scheduler.
How is this working for you? Notice ant difference in battery?
Sent from my SAMSUNG-SGH-I777 using XDA
ryude said:
I set second core kickin threshold to 1000mhz and I undeclock to 1000mhz. I set gpu to 100/100/100 @800/800/800. Ondemand governor and noop scheduler.
Click to expand...
Click to collapse
In my opinion, 800 is probably the best place for second core kickin - from 800 to 1000 is where voltage starts rising quite a bit, so you get more work per unit of energy when kicking in the second core at 800 than ramping up to 1000.
Thanks for making this. seems you beat me too it this time. lol.
Here are my settings
CPU
25/75/75/100/300/500/700/800000 AFTR+LPA
GPU
100/133/267/850/900/1000/50/50/75/50/1/1/1
MISC
Ondemand/cfq/Unchecked
Quadrant score of 3507
Could I also use Voltage control in tandem with this to tweak the voltages for each step? *Pretty sure it would cause conflicts/my phone to explode so I was curious...*
I didn't make it - Xan did. I just added support.
In any event, I'm really appreciative and glad to have a new venue to futz with on my phone. I can't wait till I learn what to tweak to get it running at optimal performance. *Not to say these phones are slouches at all though.*
Thanks for sharing your settings folks! Thanks for the information too Entropy.
As for your voltage control settings, ignore the GPU tab in that (He will be removing the GPU tab soon). Just use Voltage Control for changing you CPU voltages & min/max freq. Can also change your gov/scheduler, but ExTweaks does it too.
Please note whatever you save as a startup in voltage control will overwrite whatever conflicts there are with ExTweaks (Gov/Sched/Charging etc).
cwc3 said:
Thanks for sharing your settings folks! Thanks for the information too Entropy.
As for your voltage control settings, ignore the GPU tab in that (He will be removing the GPU tab soon). Just use Voltage Control for changing you CPU voltages & min/max freq. Can also change your gov/scheduler, but ExTweaks does it too.
Please note whatever you save as a startup in voltage control will overwrite whatever conflicts there are with ExTweaks (Gov/Sched/Charging etc).
Click to expand...
Click to collapse
Good to know thanks.
Alucardis666 said:
Thanks for making this. seems you beat me too it this time. lol.
Here are my settings
CPU
25/75/75/100/300/500/700/800000 AFTR+LPA
GPU
100/133/267/850/900/1000/50/50/75/50/1/1/1
MISC
Ondemand/cfq/Unchecked
Quadrant score of 3507
Could I also use Voltage control in tandem with this to tweak the voltages for each step? *Pretty sure it would cause conflicts/my phone to explode so I was curious...*
Click to expand...
Click to collapse
Thanks! I've followed suit as i was pretty intimidated by this. Let's see where this gets us...I'd love to see those cliffs in my battery graph flatten out a bit during screen on.
Sent from my SAMSUNG-SGH-I777 using XDA
Alucardis666 said:
Thanks for making this. seems you beat me too it this time. lol.
Here are my settings
CPU
25/75/75/100/300/500/700/800000 AFTR+LPA
GPU
100/133/267/850/900/1000/50/50/75/50/1/1/1
MISC
Ondemand/cfq/Unchecked
Quadrant score of 3507
Could I also use Voltage control in tandem with this to tweak the voltages for each step? *Pretty sure it would cause conflicts/my phone to explode so I was curious...*
Click to expand...
Click to collapse
Thanks man!! Gonna give these a shot.
Alucardis666 said:
Thanks for making this. seems you beat me too it this time. lol.
Here are my settings
CPU
25/75/75/100/300/500/700/800000 AFTR+LPA
GPU
100/133/267/850/900/1000/50/50/75/50/1/1/1
MISC
Ondemand/cfq/Unchecked
Quadrant score of 3507
Could I also use Voltage control in tandem with this to tweak the voltages for each step? *Pretty sure it would cause conflicts/my phone to explode so I was curious...*
Click to expand...
Click to collapse
I use setcpu from xda, it allows me to set screen off and charging profiles as well as voltages. It helps a lot
ryude said:
I use setcpu from xda, it allows me to set screen off and charging profiles as well as voltages. It helps a lot
Click to expand...
Click to collapse
I might give it a try again. The first time I used it, it seemed as if setcpu worsened the battery life.
Glad so many seem to like my config. still tweaking it, but lemme know how it goes for you guys.
Related
First off i take no credit for the virtuous oc daemon itself, it was developed by rmk40.
And credit goes to -viperboy- for the idea, i used his rom and really liked the oc daemon and saw the difference it makes. Check his rom out here. It has a nice interface to control the oc daemon and other features of the rom.
You can get more info here
DON'T use any apps to adjust cpu with this ie., setcpu, cpumaster, etc.
Ok, here is the deal flash the zip file the script will run by itself the only adjustment you have to make is the virtuous oc settings. This should work with any rom and probably any device i just don't have any other devices to test it on.
Here is how:
Open root explorer (or whatever file manager you use) and navigate to /system/etc/virtuous_oc, you will see 6 files named:
sleep_governor
sleep_max_freq
sleep_min_freq
wake_governor
wake_max_freq
wake_min_freq
These are the files you edit to your liking, i only edited wake_max_freq to read 1836000 or 1.8ghz
The two governor file have different settings and they are:
conservative
userspace
powersave
ondemand
performance
Again edit to your liking i left them ondemand myself seems to work good. I don't really know what the settings do exactly when it comes to these but they seem pretty self explanatory.
To see if it's working all you need to do is open terminal emulator or adb shell and type one of the following:
Current CPU frequency
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
Current CPU governor
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Current min CPU Freq
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
Current max CPU Freq
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
It autostarts using init.d, so MAKE SURE your rom supports init.d, if it doesn't you can still use it but it has to be started manually by entering the following in terminal emulator:
Code:
/system/xbin/virtuous_oc
If you overclock MAKE SURE your kernel supports it, I'm not responsible for any damage incurred
In the future i want to make an app to control the settings but i am still learning that part.
Big thanks to rmk40 for this awesome daemon and -viperboy- the bad ass idea !!
EDIT:
A basic rundown of the oc daemon is it scales up your cpu when you screen is on and scales it down when it is off, so your cpu is not overclocked continuously. It does save on battery as long as you don't get crazy with the overclocking.
rugedraw said:
The frequencies are:
Underclock: 192000 384000 432000 486000 540000 594000 648000 702000 756000 810000 864000 918000 972000 1026000 1080000 1134000 1188000 (stock)
Overclock: 1188000 (stock) 1296000 1404000 1512000 1620000 1782000 1836000 1944000 2052000
There may be some extra ones not listed here. From doing basic math, it seems you have to go up or down in increments of 54,000 when adjusting the CPU speeds. So if you want to UC higher than 192000 but lower than 384000, then you SHOULD be able to add 54,000 to 192000 and use that, or subtract 54,000 from 384000 and go that route.
Click to expand...
Click to collapse
Added my pcm controls to the downloads, this will underclock/overclock(soon i hope) your battery when the battery reaches a specified percent. See this post for more details: http://forum.xda-developers.com/showthread.php?t=1227938
Changelog:
8/11
-Added Juwe11 ram optimization script
-Added speed up SD hack (Set at 3072) Details here
8/14
-Added Uninstaller
8/24
-Added virtuous_oc_pcm
Sweetness! To OC or UC, do you need to to increase or decrease the processor speed by certain increments? If so, please add them the OP for all of us noobs.
Thanks!
Edit: Since you didn't reserve any additional posts, feel free to shoot me a PM if you want me to add anything to this post in the future.
rugedraw said:
Sweetness! To OC or UC, do you need to to increase or decrease the processor speed by certain increments? If so, please add them the OP for all of us noobs.
Click to expand...
Click to collapse
Basically you can set them to what you want within reason, the way i do it is
1836000 is 1.8ghz
1188000 is 1.1ghz
So if you just put a . in between the first 2 numbers its roughly the ghz so
1288000 would be roughly 1.2ghz, at least that's my understanding if i'm wrong i'm sure someone will correct me. I wouldn't go crazy and set it at 2288000 that might do some damage.
Woooohooooo!!!! Im going in. Thank you sir!
hTc Evo [3D]
smokin1337 said:
I wouldn't go crazy and set it at 2288000 that might do some damage.
Click to expand...
Click to collapse
The phone would most likely reboot/crash.
Sent from my PG86100 using XDA App
DDiaz007 said:
The phone would most likely reboot/crash.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
And die! Haha
Id hate to be the one tackling that script :/
hTc Evo [3D]
Why yes, I'll take one thank you.
Dude! Freakin' awesome! I've been hoping someone would create this. Thanks!
smokin1337 said:
Basically you can set them to what you want within reason, the way i do it is
1836000 is 1.8ghz
1188000 is 1.1ghz
So if you just put a . in between the first 2 numbers its roughly the ghz so
1288000 would be roughly 1.2ghz, at least that's my understanding if i'm wrong i'm sure someone will correct me. I wouldn't go crazy and set it at 2288000 that might do some damage.
Click to expand...
Click to collapse
Actually, 1288000 is 1.3 rounded up and 118000 is the stock 1.2 speed, but I get what you're saying.......maybe I didn't do a good job of explaining myself. If you want 1.5, you can't set it at 150000......you'd have to set it at 1512000 (or something like that) because it must go up or down by fixed increments. I don't remember what the exact increments are, but I can look it up and post it if you'd like.
Edit: The frequencies are:
Underclock: 192000 384000 432000 486000 540000 594000 648000 702000 756000 810000 864000 918000 972000 1026000 1080000 1134000 1188000 (stock)
Overclock: 1188000 (stock) 1296000 1404000 1512000 1620000 1782000 1836000 1944000 2052000
There may be some extra ones not listed here. From doing basic math, it seems you have to go up or down in increments of 54,000 when adjusting the CPU speeds. So if you want to UC higher than 192000 but lower than 384000, then you SHOULD be able to add 54,000 to 192000 and use that, or subtract 54,000 from 384000 and go that route.
I haven't tried using this method yet, as I'm already OC'd using viperboy's script. Maybe someone else can test this and confirm it is accurate.
Sent from my PG86100 using XDA Premium App
I'm asking this purely to increase my own knowledge, but what does this do better than SetCPU or other overclocking solutions?
Thanks rugedraw i added the frequencies to the op.
clamknuckle said:
I'm asking this purely to increase my own knowledge, but what does this do better than SetCPU or other overclocking solutions?
Click to expand...
Click to collapse
SetCPU can take up to several seconds to adjust, and it uses RAM also. A Daemon is instantaneous, and uses little to no RAM.
Sent from my PG86100 using XDA App
clamknuckle said:
I'm asking this purely to increase my own knowledge, but what does this do better than SetCPU or other overclocking solutions?
Click to expand...
Click to collapse
This is developed by Virtuous Unity for stability in OC the CPU, Set CPU uses some voltage to run and has been known to be unstable at times, this is the most stable way to control OC frequencies right from boot.
The Daemon works great (I have a version of this I'm testing on the MT4G at the moment) and there are benefits to using it, I would have to say it's important to spend some time reading information on Kernels to better understand what your using and the risks behind it.
Found Here: http://forum.xda-developers.com/showthread.php?t=1143177
( Scroll to the 4th Post for full information on the Daemon )
State-of-the-art-solution
So we (more precisely rmk40) thought of a better solution.
He wrote a native C Daemon which changes the governors instantly without any lag.
This leads to major performance improvements right after turning on the screen and in the lockscreen.
But at the moment this solution is a little bit harder to configure. We are planing to make a GUI for this, so you get the same comfort as using SetCPU.
Nevertheless you can even now adjust the daemon to your needs.
Be aware that the daemon only works if all CPU tuner apps are deinstalled. Otherwise it deactivates itself.
Click to expand...
Click to collapse
smokin1337 said:
Thanks rugedraw i added the frequencies to the op.
Click to expand...
Click to collapse
No worries.........glad I can help with the little stuff. However, it seems like basic math is too hard for me. The correct increments are 54,000 and NOT 48,000. After some careful review, some of the high end OC frequencies had typo's, as well. I changed the info in myl post, but please update the OP, as well. I'm sure most people will be referring to that.
Just set this up on Rewind 2.1 and it appears to be working awesome.. definitely seems smoother then using a screen off profile in setcpu..
What I don't get is why Google doesn't incorporate something like this in all Android builds. It seems there are many things that can be manipulated to improve battery life on Android devices but that these solutions are just being ignored. Anyhoo, I don't think I will ever use SetCPU again...
Useless without voltage control
So this will work with nets kernel, and not against it? Just use it instead of setcpu?
NCspecV81 said:
Useless without voltage control
Click to expand...
Click to collapse
It definitely isn't useless without voltage control. I don't see how saving battery and using no system resources is useless. Plus, you cannot edit voltages on the E3D kernels yet, the sysfs HAVS interface needs to be implemented first.
-viperboy- said:
It definitely isn't useless without voltage control. I don't see how saving battery and using no system resources is useless. Plus, you cannot edit voltages on the E3D kernels yet, the sysfs HAVS interface needs to be implemented first.
Click to expand...
Click to collapse
I believe him. Hell, I all those frequencies I posted came from the OC script he designed for his rom.........which is awesome.
Im trying to underclock the s2 when the phone's screen is off, but when i set it under profiles and put it into effect it will sometimes/most of the time, shut off when trying to awake! I've tried it at various Mhz. I had it at the lowest at first and it didnt' wake up ...so i thought not enough juice to remember all my stuff and it pooped... well i also tried it @ 800 Mhz and also had it set to powersave... im also running widget locker and about 3 widgets(twitter, beautiful widget, and notes), Does anyone know what is going on? Does anyone have any different settings that i should use instead...just trying to preserve battery life when in sleep mode.
Haven't used powersave mode at all yet, It's possible that profile has bugs on this phone.
I have my screen off profile set to 800 mhz and conservative and have had 0 issues so far.
as far as I'm aware powersave doesn't let it out of the minimum frequency (could be wrong). Use the conservative governor instead.
Don't use power save. I have done a lot of testing with this.
Here is the lowest that you can go.
Range: 200-500mhz
Mode: ondemand or conservative
If you go less than 500mhz or put it on powersaver, then it won't wake up from locking the phone.
Thanks
Thanks alot guys, have yall noticed increase battery life using the underclock?
and does widget lock take up alot of battery power? while in "sleep"?
geauxlsu83 said:
Thanks alot guys, have yall noticed increase battery life using the underclock?
and does widget lock take up alot of battery power? while in "sleep"?
Click to expand...
Click to collapse
I noticed that setting it to 200-500mhz increased my battery life by about 15-20%, but I did notice a significant performance drop. 200-800mhz is much less noticeable performance wise, but I didn't check to see what kind of battery life I got on that setting.
As for widgets...I'm not sure on that one either.
geauxlsu83 said:
Im trying to underclock the s2 when the phone's screen is off, but when i set it under profiles and put it into effect it will sometimes/most of the time, shut off when trying to awake! I've tried it at various Mhz. I had it at the lowest at first and it didnt' wake up ...so i thought not enough juice to remember all my stuff and it pooped... well i also tried it @ 800 Mhz and also had it set to powersave... im also running widget locker and about 3 widgets(twitter, beautiful widget, and notes), Does anyone know what is going on? Does anyone have any different settings that i should use instead...just trying to preserve battery life when in sleep mode.
Click to expand...
Click to collapse
Stock kernel or codeworkx's CWM kernel?
If either of those, your screen-off profile MUST include 800 MHz or you'll encounter a sleep of death. It's a common issue with Samsungs, and it is why SetCPU has such a bad reputation on Samsung CPUs, even though the SetCPU author has created kernel patches for nearly every Samsung Android device.
If my kernel or Cyanogenmod 7, screen-off profiles that do not include 800 MHz are OK, HOWEVER:
You must not set a screen-off profile of powersave. The governor mechanics of powersave are not compatible with the "sleep of death" fix. Conservative with min=max=200 SHOULD be OK.
The reason for this is that the CPU enters and exits suspend at 800 MHz (hardware limitation). If the regulator voltages aren't set high enough to support 800 MHz - the CPU crashes.
thanks
yeah im actually flashing your kernel as we speak i looked under a battery thread and they said your kernel is good for battery conservation thanks for your help
actually i flashed it from heimdall and it says it is kernel version is 2.6.35.7 is this yours?
All kernels except my Experimental series say 2.6.35.7 - you need to use CPUSpy to identify the [email protected] that built it.
Anything that comes from me will say [email protected] or, in rare cases, [email protected] until I build a completely new system with a different hostname.
Entropy512 said:
All kernels except my Experimental series say 2.6.35.7 - you need to use CPUSpy to identify the [email protected] that built it.
Anything that comes from me will say [email protected] or, in rare cases, [email protected] until I build a completely new system with a different hostname.
Click to expand...
Click to collapse
Your kernel is nice but can't oc. If I try to go to 1.4 soft reboot city.
Sent from my super modded phone.
Then your phone can't OC.
Not everyone's phone can run at 1.4 or 1.6. There's a reason it's only sold rated at 1.2... As frequency gets higher, the range of "stable" voltages (too low and you crash, too high and you overheat then crash) narrows, to the point where at a certain frequency that varies from device to device, there are no "stable" voltages.
Sent from my GT-P7510 using Tapatalk
Entropy512 said:
Then your phone can't OC.
Not everyone's phone can run at 1.4 or 1.6. There's a reason it's only sold rated at 1.2... As frequency gets higher, the range of "stable" voltages (too low and you crash, too high and you overheat then crash) narrows, to the point where at a certain frequency that varies from device to device, there are no "stable" voltages.
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Well said.
Entropy512 said:
You must not set a screen-off profile of powersave. The governor mechanics of powersave are not compatible with the "sleep of death" fix. Conservative with min=max=200 SHOULD be OK.
Click to expand...
Click to collapse
I wonder is there any tasks or situations that might require freq above 200 while screen off? For example, while playing music or using apps like CardioTrainer (which captures gps, draws track on the map as you exercise).
Also, mine is set to 200..500 conservative for screen-off and CPUSpy shows it spends most time at 200 anyway (deep sleep taken out of consideration).
-- vlad
vladm7 said:
I wonder is there any tasks or situations that might require freq above 200 while screen off? For example, while playing music or using apps like CardioTrainer (which captures gps, draws track on the map as you exercise).
Also, mine is set to 200..500 conservative for screen-off and CPUSpy shows it spends most time at 200 anyway (deep sleep taken out of consideration).
-- vlad
Click to expand...
Click to collapse
This is why I also have my screen-off limited to 500. Once in a while, the phone needs to do a little extra work, and it's better to ramp to 500, get stuff done, then go back to deepsleep. As I said min=max=200 SHOULD be OK, but personally, I wouldn't recommend it.
I would love if SetCPU allowed for different governor tuning depending on profile. e.g. make up/down threshold more battery-biased with screen-off than screen-on. (Slower polling rate, higher up/down thresholds.)
SetCPU root access problem
Hi -
GSII AT&T Stock ROM
Rooted
Superuser v3.0.6
SetCPU 2.2.4 purchased form Market (support the devs!)
Screenshot attached
Cannot obtain root access
I have installed / uninstalled SetCPU a few times
Superuser logs show several apps already allowed but no success or even attempt from SetCPU
I've rebooted. I'm out of ideas
Anyone have any ideas on how to fix?
Thanks in advance
IshouldntbeHere said:
Your kernel is nice but can't oc. If I try to go to 1.4 soft reboot city.
Sent from my super modded phone.
Click to expand...
Click to collapse
Pretty sure it's your phone cause mine OC's to 1.6 with no problem.
BigBopper said:
Hi -
GSII AT&T Stock ROM
Rooted
Superuser v3.0.6
SetCPU 2.2.4 purchased form Market (support the devs!)
Screenshot attached
Cannot obtain root access
I have installed / uninstalled SetCPU a few times
Superuser logs show several apps already allowed but no success or even attempt from SetCPU
I've rebooted. I'm out of ideas
Anyone have any ideas on how to fix?
Thanks in advance
Click to expand...
Click to collapse
Have you tried updating the su binary in Superuser? (Even if you have the app updated, the app itself needs to update the binary.)
Beyond that I have no ideas.
Entropy512 said:
Stock kernel or codeworkx's CWM kernel?
If either of those, your screen-off profile MUST include 800 MHz or you'll encounter a sleep of death. It's a common issue with Samsungs, and it is why SetCPU has such a bad reputation on Samsung CPUs, even though the SetCPU author has created kernel patches for nearly every Samsung Android device.
If my kernel or Cyanogenmod 7, screen-off profiles that do not include 800 MHz are OK, HOWEVER:
You must not set a screen-off profile of powersave. The governor mechanics of powersave are not compatible with the "sleep of death" fix. Conservative with min=max=200 SHOULD be OK.
The reason for this is that the CPU enters and exits suspend at 800 MHz (hardware limitation). If the regulator voltages aren't set high enough to support 800 MHz - the CPU crashes.
Click to expand...
Click to collapse
Ahh, that was my problem. I was using powersave. Do you (or anyone else) see there being a benefit to having a screen off profile?
In theory, a screen-off profile shouldn't help - in reality, it's a line of defense for cases where something goes nuts in the background.
i been using setcpu for a while now and want to no how to use advanced settings.. just looking to make my phone run better.. thanks
I havent used setCPU for a long time so Im not sure if you mean some advance settings in the app itself?
Are you talking about like adjusting the governor settings? Modifying voltages? adjusting I/O scheduler? Tweaking kernel settings? Tweaking VM settings?
EniGmA1987 said:
I havent used setCPU for a long time so Im not sure if you mean some advance settings in the app itself?
Are you talking about like adjusting the governor settings? Modifying voltages? adjusting I/O scheduler? Tweaking kernel settings? Tweaking VM settings?
Click to expand...
Click to collapse
if u go into advanced it has sampling rate..... up threshold......... ignore nice load....... powersave bias...
I really wouldn't mess with those unless you want to brick your device and fry your processor.
evod3 said:
if u go into advanced it has sampling rate..... up threshold......... ignore nice load....... powersave bias...
Click to expand...
Click to collapse
Ah so governor settings then. None of the actual advanced things
Sampling rate has an impact on battery life and smoothness. Set it to around 15000-20000 for good smoothness on a governor, 50000 or so if you want decent smoothness but better battery.
This is how often it samples the load to the CPU to choose if speed should be ramped up or down.
UpThreshold also has a big effect on smoothness as this tells how much load % is needed on the CPU to increase the speed.
Powersave bias is basically slowing the CPU down a certain number of frequency steps. SO lets say you ahve your CPU set at default max speed of 1188000, a powersave bias of 50 would mean your new max speed is 1134000 which is the next step down.
Governor settings change how your governor reacts. Only some governors can be modified and some to more extent than others. I think Conservative has the most adjustment, but the best sampling rate it cna have is only 200,000. So that makes it kind of useless for any sort of smoothness. If you tweaked conservative to give great smoothness then you would be better off with OnDemand as at the same smoothness OnDemand would give better battery life since it can stay at a slower speed more often as its sampling rate is much better.
sitlet said:
I really wouldn't mess with those unless you want to brick your device and fry your processor.
Click to expand...
Click to collapse
Thats kinda terrible advice. All this is doing is changing governor settings. He didnt say anything about wanting to mess with voltages.
alright. ive been playing around and cant find some good governors for what i want.
for hardcore gaming, what governor have you found that works the best
for best batter saving, but still be able to watch videos, surf web, email and just general navigating without it being too slow.
which governors do you guys use for both of those? thanks
Quadrider10 said:
alright. ive been playing around and cant find some good governors for what i want.
for hardcore gaming, what governor have you found that works the best
for best batter saving, but still be able to watch videos, surf web, email and just general navigating without it being too slow.
which governors do you guys use for both of those? thanks
Click to expand...
Click to collapse
anyone?
Use the smartassV2 governor. It regulates the CPU frequency according to load (sorta like ondemand except it works better).
darkghost568 said:
Use the smartassV2 governor. It regulates the CPU frequency according to load (sorta like ondemand except it works better).
Click to expand...
Click to collapse
i tried and i liked it, but it like locked my cpu at 1.24ghz (thats the max i have it set to) and even if i changed it, it would lock to the max frequency????
Quadrider10 said:
i tried and i liked it, but it like locked my cpu at 1.24ghz (thats the max i have it set to) and even if i changed it, it would lock to the max frequency????
Click to expand...
Click to collapse
I'll have v1 of Funky kernel out soon if you want to try out wheatley.
I've been a fan of smartassV2 since the first time I used it on the Thunderbolt. It is as close to an ideal governor as I've ever used. SmartassV2, with a complete sysfs implementation, can be tweaked very nicely. It is a governor that you can really tune so that most of the time it's not running balls out, but it's not loafing along either, which is how a governor SHOULD function. (I like to see a nice bell curve peaking at an ideal frequency, and spiked way out at the bottom frequencies when I look at a bar chart of my time-in-state's.) From what I can tell, few if any devs tune their governors to their kernels. I'm thinking that's how we ended up with a dozen or so governors that are rather similar, yet rarely ideal.
Snuzzo said:
I'll have v1 of Funky kernel out soon if you want to try out wheatley.
Click to expand...
Click to collapse
Wheatley is epic.
Sent from my Rezound using Tapatalk 2
loonatik78 said:
I've been a fan of smartassV2 since the first time I used it on the Thunderbolt. It is as close to an ideal governor as I've ever used. SmartassV2, with a complete sysfs implementation, can be tweaked very nicely. It is a governor that you can really tune so that most of the time it's not running balls out, but it's not loafing along either, which is how a governor SHOULD function. (I like to see a nice bell curve peaking at an ideal frequency, and spiked way out at the bottom frequencies when I look at a bar chart of my time-in-state's.) From what I can tell, few if any devs tune their governors to their kernels. I'm thinking that's how we ended up with a dozen or so governors that are rather similar, yet rarely ideal.
Click to expand...
Click to collapse
Alright now my problem is that I set my CPU to 192mhz lowest and 1.24 max. And that's for normal use. I'm running smart ass2 Nd it's not licking my CPU at max anymore, but it keeps.moving the max to 1.51ghz.
any ideas on how to fix tht?
Quadrider10 said:
any ideas on how to fix tht?
Click to expand...
Click to collapse
No frills CPU in play store
Sent from my ADR6425LVW using Tapatalk 2
Quadrider10 said:
Alright now my problem is that I set my CPU to 192mhz lowest and 1.24 max. And that's for normal use. I'm running smart ass2 Nd it's not licking my CPU at max anymore, but it keeps.moving the max to 1.51ghz.
Click to expand...
Click to collapse
Quadrider10 said:
any ideas on how to fix tht?
Click to expand...
Click to collapse
Yeah. Don't use DSB's kernel. I spent DAYS trying to figure out what his kernel is trying to do as far as governors. I'm not going to talk smack about the guy's work, but I will tell you what I know.
I doesn't appear any of the governors have been tweaked for his kernel. It looks like code was just tossed in there and left however someone else wrote it. For instance, smartassV2 has a sleep_wakup_freq of .998GHz, which is much slower than it should be. It SHOULD be near or equal to scaling_max_freq. Likewise, the max_cpu_load (which determines when the cpu should scale up) is 70, a fairly aggressive number, while the awake_ideal_freq and sleep_ideal_freq are pointlessly high. If I had to guess, these look like parameters for a Snapdragon S1 SoC, not the dual core S3 the Rezound has. No matter what governor you choose, it's only active on "cpu0". "cpu1" runs ondemand no matter what. The reason you have trouble making settings for the governor stick is because the sysfs location disappears and reappears for no obvious reason. It appears when things pop in and out (presumably when cpu1 goes on and off line), things are reset.
Cold hard reality is this: You're NEVER going to optimize any kernel out there to it's fullest potential. Either the options aren't there to tweak, or they behave in inexplicable ways. I can't tell you why DSB's kernel (not to single out a dev or his work, but I'm certain that's the kernel you're talking about) does what it does, but it's so far divorced from optimized on such basic levels you're better off not wasting your time.
As an aside:
After getting a rough feel for what some of these kernels are doing, I'm not at all surprised some kernels have had significant heat and battery drain issues. There are things that simply do not work right or work consistently. The devs shouldn't be blamed for this. These are probably the issues they're trying to work around that they inherited from the sources they're starting from and what makes tweaking them so difficult.
I acutely got everything to work. I'm just trying to overclock the GPU.
The title pretty much explains it all. I apologize if this thread is a repeat.
I'm currently using CPU Master Pro
Sent from my ADR6425LVW using Tapatalk 2
Not quite a repeat, but we do have a few threads on CPU governing. Not many people do it though.
If I MUST use an app, I use the smallest one that works. Otherwise, everything gets done with a script.
DbZ Gokuu said:
The title pretty much explains it all. I apologize if this thread is a repeat.
I'm currently using CPU Master Pro
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
I've been using no-frills CPU Control, but honestly, there really isn't much of a point adjusting the settings on stock rezound unless you want to save power by using conservative governor and/or a lower max speed setting. It does have a nice feature to show poll the CPU frequency, though: in settings, check "Refresh current frequency" then hit the bar graph on the actionbar at top.
Stock rezound already uses ondemand governor, which is essentially the best you will get out of a stock kernel, and the frequency range is set to 384-1.5ghz by default. IO scheduler is deadline, which does not need messing with either.
Note: Do not set minimum frequency to 192mhz; it uses the same power as 384mhz at any given point in time. Also heard it can cause sleep issues.
I'm using android tuner pretty simple and let me do other stuff. Luczative gov with -50 voltage (testing so far good I'm gonna drop another -25 later)
Bump
I'm bumping the thread because it predates kernel source release and the proliferation of kernels for the Rezound.
I'd love suggestions for a kernel/CPU control app that does the following (I've tried SetCPU, Antutu, Incredicontrol, Kernel Tuner, Android Tuner, etc. and they all seem to do some but not all of the preceding):
1. Let me choose governor and IO scheduler.
2. Let me set range for CPU speed
3. Let me set profiles for (1) low battery and (2) overheat
4. Let me see and manipulate CPU voltages where the kernel permits it; and
5. Let me turn on USB fast charge where the kernel permits it (without requiring a separate app/widget), and of course
6. Won't generate more problems than it solves.
Maybe one of these already does it, but Kernel Tuner and Android Tuner completely overwhelm me with information, choices and settings that are meaningless to me. (And, no, admittedly I do not choose to spend a lot of time educating myself on the subject....I'm a professional, not a computer professional, and I really can't afford to concede the billable time. I have always taken the position these machines were tools that we use, not tools that abuse us.)
Thanks in advance for informed and thoughtful opinions.
hgoldner said:
I'm bumping the thread because it predates kernel source release and the proliferation of kernels for the Rezound.
I'd love suggestions for a kernel/CPU control app that does the following (I've tried SetCPU, Antutu, Incredicontrol, Kernel Tuner, Android Tuner, etc. and they all seem to do some but not all of the preceding):
1. Let me choose governor and IO scheduler.
2. Let me set range for CPU speed
3. Let me set profiles for (1) low battery and (2) overheat
4. Let me see and manipulate CPU voltages where the kernel permits it; and
5. Let me turn on USB fast charge where the kernel permits it (without requiring a separate app/widget), and of course
6. Won't generate more problems than it solves.
Maybe one of these already does it, but Kernel Tuner and Android Tuner completely overwhelm me with information, choices and settings that are meaningless to me. (And, no, admittedly I do not choose to spend a lot of time educating myself on the subject....I'm a professional, not a computer professional, and I really can't afford to concede the billable time. I have always taken the position these machines were tools that we use, not tools that abuse us.)
Thanks in advance for informed and thoughtful opinions.
Click to expand...
Click to collapse
Antutu cpu master does all that for me, idk about the fast charge though
Sent from my ADR6425LVW using xda app-developers app
Squirrel1620 said:
Antutu cpu master does all that for me, idk about the fast charge though
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I think CPU master is a good recommendation, chad's Incredicontrol would also be nice and it does have the fast charge function.
Antutu CPU Master, which I have been running, does not have the ability to turn on fast charge. Incredcontrol does not permit profiles.
My name's Harold and I'm a flashaholic....
Well it's like you said, you're probably not going to get all of your wish list. Android tuner is a new app that kinda does everything, but it also costs 10 bucks.
Neo uses kernel tuner, if that helps. Just ignore the technical stuff.
Sent from my Rezound using Tapatalk 2