So I installed Topogigi's 2x ics rom and I found that I can't underclock the minimum cpu speed on a number of cpu speed tweaking apps including, cpu master, voltage control, no frills cpu control. Basically the maximum cpu speed is set to 1000mhz, and the minimum is set to 1000mhz which I can't change. When I used cyanogenmod 7 and the stock gingerbread rom, I could freely underclock the cpu. I was wondering whether this has anything to do with the cpu governer (which is hotplug on this rom) and/or the i/o scheduler.
Link to the rom I'm using:
http://forum.xda-developers.com/showthread.php?t=2007968
Thanks
Related
Unfortunately I can not post to dev section, so hopefully stratos will see my post here:
I had stock JVR with semaphore 1.5 (not v) on ext4 and everything was excellent with this brilliant kernel apart from the well known phone fc.
OC/UV was ok: quadrant scores were approx 1900-2400 on conservative cpu gov and 2500-3000 on ondemand gov.
Now, I flashed the 1.6 beta and my system is noticeably slower on *conservative* cpu gov and quadrant scores dropped clearly below 1500. Ondemand cpu gov seems to work ok but as I was alwaus on conservative I can not be abs.sure
I don't know if it is important but using voltage control app to check cpu function I see that:
a) cpu freq is wildly/unpredictably fluctuating with 1.6beta while this was not happening in 1.5 under conservative cpu gov,
and
1b) reported default voltage is different: for example with sema1.5 1200mhz had default 1275, now in 1.6beta without oc module 1000mhz is 1275 but with oc module 1200mhz have 1300mv by default.
Stratos,
could it be that a) something is broken in the new conservative cpu gov? , b) have you changed the default cpu voltage between v1.5 and v1.6beta?
GrNick said:
Unfortunately I can not post to dev section, so hopefully stratos will see my post here:
I had stock JVR with semaphore 1.5 (not v) on ext4 and everything was excellent with this brilliant kernel apart from the well known phone fc.
OC/UV was ok: quadrant scores were approx 1900-2400 on conservative cpu gov and 2500-3000 on ondemand gov.
Now, I flashed the 1.6 beta and my system is noticeably slower on *conservative* cpu gov and quadrant scores dropped clearly below 1500. Ondemand cpu gov seems to work ok but as I was alwaus on conservative I can not be abs.sure
I don't know if it is important but using voltage control app to check cpu function I see that:
a) cpu freq is wildly/unpredictably fluctuating with 1.6beta while this was not happening in 1.5 under conservative cpu gov,
and
1b) reported default voltage is different: for example with sema1.5 1200mhz had default 1275, now in 1.6beta without oc module 1000mhz is 1275 but with oc module 1200mhz have 1300mv by default.
Stratos,
could it be that a) something is broken in the new conservative cpu gov? , b) have you changed the default cpu voltage between v1.5 and v1.6beta?
Click to expand...
Click to collapse
Unfortunately I can not confirm your results. I just load the conservative governor and tested with and without overclocking. No problems here.
During benchmarking due to high load the frequency it's difficult to drop below the max. So, governor should not make the difference.
The uv value was the same in 1.5.0 (1300mv) for 1.2Ghz but it was wrongly displayed as 1275.
Thanks for you feedback. I will let you know if someone else report problems about the conservative governor.
Hey stratos, thanks for the clarification about cpu voltage.
Re cpu gov, I just did a nandroid restore and confirmed that conservative cpu gov works much better in 1.5
Any ideas on how to explore it further? There is definetely something different here.
I mean, its not just quadrant scores, its memento database loading instantly vs seconds of delay under cons cpu gov in 1.5 vs 1.6beta.
I will reflash again l8r tonight.
Anyhow, this kernel rocks! And I love the tun/netfilter module design.
Sent from my GT-I9000 using Tapatalk
I am running Eclipse 1.3.8, and i have System Tuner Pro (obviously that doesn't matter, though). I keep the clock from 300mhz to 1.2 ghz. However, I can't seem to decide which governor is most efficient.
The following are the 4 that I can't decide between:
Hotplug
mot_hotplug
userspace
ondemand
Can anyone, from experience, say which one will be the most efficient at saving battery?
Official CM7.2 version has only the stock governors. How can i add more governors, like smartassv2?
I want to downclock my ace a bit, but 480mhz is too slow, 787mhz doesn't save anything. Is it possible to add custom frequencies, like 600 or 700?
Flash Firekernel. It will automatically add Smartassv2 and other governors.
Thx a lot smartassv2 @ 614mhz runs smooth & saves a lot of battery
I'm currently on Zeus v7.01 with dianaV2.3+ kernel and I'm wondering what is the best combination of Governor/IO Scheduler/Voltage to obtain the most best battery life.
I'm not searching for best performance honestly, but instead a longer lasting phone. lol
I rarely play games, and smoothness is not a must for me (Nemus Launcher does the job, smoothest launcher ever!)
My current settings are:
CPU Frequency Tweaks
Max freq: 1000
Min freq: 100
DVFS enabled on boot
Voltage Tweak: -5
Governor: ondemandX
Io Scheduler: sio (Simple I/O)
You could try undervolting your phone,because i like performance and smoothness,my setup is like that:
Max CPU frequency:1300Mhz
Min CPU frequency:300Mhz
Governor:Smartassv2
I/O scheduler:deadline.
Sorry for useless stuff,but i like to share
My main agenda is to help, not gain thanks.
UniversalSS said:
You could try undervolting your phone,because i like performance and smoothness,my setup is like that:
Max CPU frequency:1300Mhz
Min CPU frequency:300Mhz
Governor:Smartassv2
I/O scheduler:deadline.
Sorry for useless stuff,but i like to share
My main agenda is to help, not gain thanks.
Click to expand...
Click to collapse
No no it's nice to share your experience!!
Might help others..
Hmm my phone is already UV... -5, if i decrease further wouldn't it be too low to cause instability?
And about IO Scheduler, i don't quite fully understand it.. which one drain least battery?
i am using 100-800 smartass2 sio and -7V without any problems.
Hi,
I'm using Co-Core 8.2 and I want to test One Power Guard to improve my battery life.
But I don't have any idea about which CPU governor and I/O scheduler to choose.
Could someone tell me which combination provides the best balance between power-save and performance?
I'm on Jelly Bean 4.1.2
NB. Cocafe recommends PegasusQ as CPU governor and either SIO/ROW for I/O scheduler but I would like to get some feedback from people already using One Power Guard.
Thanks in advance
luisblop said:
Hi,
I'm using Co-Core 8.2 and I want to test One Power Guard to improve my battery life.
But I don't have any idea about which CPU governor and I/O scheduler to choose.
Could someone tell me which combination provides the best balance between power-save and performance?
I'm on Jelly Bean 4.1.2
NB. Cocafe recommends PegasusQ as CPU governor and either SIO/ROW for I/O scheduler but I would like to get some feedback from people already using One Power Guard.
Thanks in advance
Click to expand...
Click to collapse
Pegasus and sioplus
OR
Hotplug and sioplus
DaRkRhiNe said:
Pegasus and sioplus
OR
Hotplug and sioplus
Click to expand...
Click to collapse
Thanks for the answer. I will give a try with Pegasus
However I noticed that sioplus is not available on One Power Guard settings. Only row and sio.
Is sioplus available in Co-core 8.2?
These apps like this just drains your battery. If you want play with CPU, download a CPU controller app. (like SetCPU) and install CoCore 9.0 which is newest version.
When you don't use phone ; 600 MHz Max & HotPlug
When you don't use phone V2 ; 600 MHz Max & Ondemand & deeper sleep status
When you lock phone, don't decrease speed (too much) because it will use whole CPU if it needs ; 800 MHz Max & Ondemand Q/Lulzactive Q/Pegasus Q
When using ; 1000 MHz Max & Ondemand/Interactive/Lulzactive Q/Pegasus Q
When you get mad and crazy about performance, lock the min to max; 1000 MHz min and max & Ondemand & SmartAss (still exists or not I don't know)
If you increase minimum speed it will keep it. So I suggest always keep min to 200MHz. (if exists 0 MHz I don't remember it too)
Edit: and don't go deeper sleep if you use hot plugger governors like Hotplug, Pegasus, Lulzactive Q
FYI
http://forum.xda-developers.com/showthread.php?t=2312491
Powered by CM11
Thanks guys,
I will compare the battery draining with One Power Guard just to give it a try.
If I don't notice any improvement then I will tweak with SetCPU
King ov Hell said:
Edit: and don't go deeper sleep if you use hot plugger governors like Hotplug, Pegasus, Lulzactive Q
Click to expand...
Click to collapse
Hi again,
What exactly do you mean wit "deeper sleep"?
Is that an option or when the display is off after several minutes?
Sorry for my ignorance
luisblop said:
Hi again,
What exactly do you mean wit "deeper sleep"?
Is that an option or when the display is off after several minutes?
Sorry for my ignorance
Click to expand...
Click to collapse
Go to the CoCore's thread you'll see. It's deep sleep level which can increase your battery life when you don't use the device. It's not about using, it's about when it's stand-by.
Ok
After one day even if One Power Guard is a nice app I prefer to switch governor depending on the display status. So I was thinking about using tasker (instead setCPU) which is already running on my phone and this way not adding more background processes.
I set a couple of task using the CPU control from tasker. It is working fine switching governors but I noticed that the frequencies (min and max) don't change. I tried even with shell script and still I don't get to set the max frequency. Then I prefer to make you a couple of questiosn:
-In tasker when using the CPU control. If I change governor. Should it be set in both CPUs (0 and 1) or only in a single one? In my case i set the governor in both.
-I use the terminal to check the current governor and max frequency (for instance for the cpu0)
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governorcat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
As said above the governor is succesfully changed but that's not the case for the frequency. Then I tried to run a shell script to change the max frequency as follows:
echo #frequency > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
But it seems not working neither. So I wonder if I'm doing something wrong.
NB. By the way I'm happy using the governor hotplug while not using my phone (thanks for the advice). In normal use I set pegasusq with sio and seems working great.