Hello guys,
I'm here to ask for all of your opinions about the cpu Profiles, frequencies and governor.
For screen on I'm currently using 1200mHz on performance, I would like to know if it would save more battery by using on demand governor.
Some months ago I had a discussion with few xda members about this subject. But that was on aurora v4. Now I'm currently on v5 u17. Let me know your opinion. Thanks
Sent from my U8800 using xda app-developers app
To be honest, I've never experienced any benefits of setting cpu profiles for screen on, screen off etc. Your phone will work much more smoothly if you stick as close to the defaults as possible.
I don't use profiles. My min is 245 and max 1200, using on demand governor.
For a while I experimented with profiles, and had bad lag when unlocking the phone, and terrible battery use when screen on.
Independent of profiles, your governor will put your phone into deep sleep when the screen is off anyway.
Do a search for "race to idle" this explains in more detail the benefits of using ondemand as opposed to other governors in terms of battery use etc.
IMHO, Android as a platform would be far better served if people stuck close to the default settings and cpu profiles. Most of the time, any negligible benefits are just placebo.
Sent from my U8800 using xda app-developers app
So according to the race to idle running with performance governor saves battery
Sent from my U8800 using xda app-developers app
In theory yes, but if your cpu is always running at max frequency, ie even when doing nothing, then no.
I have done tests, and my battery always lasts longer using ondemand as opposed to performance, or other governors.
Sent from my U8800 using xda app-developers app
Use interactive/bfq that's the best in my opinion
Sent from my U8800-51 using xda premium
Related
Every TF is different. Someone has reported being able to unvervolt by -250 or more. I don't know how the hell he did it. Anyway, I thought I'd start this thread to let people show off their OC and UV settings. I thought I could get a feel on what the stable limits are.
Remember, guys, it's only considered stable if the camera doesn't freeze. I don't care how much stress test you do. If your camera doesn't work, then it's not stable.
The 2 lowest clock settings there are, it's like 250 and 320 mhz or something I can run a 250 undervolt. This is extremely useful because I run on interactive and my tablet runs on almost no battery at all while on standby.
As for my underclocks up from that to about 1590s(My tablet can't handle 1600s) I have a steady 65 undervolt for all frequencies. I found battery life to be amazing...
Sent from my Inspire 4G using XDA Premium App
Hi there! What are you using to undervolt and/or overclock? I'm using CPU Master Free to overclock, but it doesn't have any undervolting options.
EDIT: also, which kernel are you using that supports Undervolting and Overclock?
Prime kernel doesnt seem to support uV at the moment
Blades does
Clemsyn does
Dont think netformer does
Settings im still playing and waiting for uV on prime kernel as ive found it the most stable at the moment will post back later
ThEiiNoCeNT said:
The 2 lowest clock settings there are, it's like 250 and 320 mhz or something I can run a 250 undervolt. This is extremely useful because I run on interactive and my tablet runs on almost no battery at all while on standby.
As for my underclocks up from that to about 1590s(My tablet can't handle 1600s) I have a steady 65 undervolt for all frequencies. I found battery life to be amazing...
Sent from my Inspire 4G using XDA Premium App
Click to expand...
Click to collapse
Does your camera work when you set everything to -65? My camera will not work if I unvervolt 608 or 456 mhz.
QQ
Sent from my Transformer TF101 using Tapatalk
Yes it works, everything does.
Sent from my Transformer TF101 using xda premium
Now that we have a new way to overclock in v14 there are near unlimited variables to overclocking with this kernel. I've found a good balance of performance with 1300ghz step and live OC value of 121%. Let us know what has worked for you. You may include voltages as well.
I'm using reborn90's settings
200-1000; 110% live oc arm volt; 800/950/1100/1175 int volt; 1000/1000/1000/1025
Seems rather steady, I also recommend turning save on boot in settings of nstools before applying these settings just in case xD
Sent from my SCH-I500 using xda premium
I am on 100-1300 with 116% Live OC, haven't played with voltage yet but everything runs great.
I can't seem to get any live OC percentage stable and anything around 118% + automatically freezes and reboots.any suggestions?
Sent from my SCH-I500 using xda premium
mleonm5 said:
I can't seem to get any live OC percentage stable and anything around 118% + automatically freezes and reboots.any suggestions?
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Do you UV first then live oc? Or is it just stock voltages?
Sent from my SCH-I500 using xda premium
For the most part I just use stock voltages when playing around with live OC because I haven't found any voltages in threads that i'm sure are stable.
Sent from my SCH-I500 using xda premium
mleonm5 said:
For the most part I just use stock voltages when playing around with live OC because I haven't found any voltages in threads that i'm sure are stable.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
it depends on how far you phone can go, some can oc more then others but some less then others, I usually never go passed 1.2ghz ,I'd rather save battery.
Sent from my SCH-I500 using xda premium
Just my opinion, but since Android 4.0 relies so heavily on the hardware rendering capabilities of the phone you'd be better off to UNDERCLOCK the CPU to 800mHz, and apply the Live OC to say 125% and have an effective CPU speed of 1000mHz while increasing the GPU clock by the same amount. I've tried it and it works very well but I didn't stick with it long enough to see how it affected battery life. You will need to modify your voltages though. I was at 1250mV on the 800mHz step.
If anyone is interested in just using stock settings, i found this thread interesting:
http://forum.xda-developers.com/showthread.php?t=1424064
100-800 mhz, 125% live oc.
So how much of a change have you noticed from Stock kernel to Glitch. I tried OCing once.. and it froze.. and phone died.. and ended up having to wipe / re-flash. Probably user error though
Just wanted to say I accidentally OC'd to 1.4ghz with 110% LOC and man did this thing fly and didn't even crash.
Sent from my ICS Mesmerize
I noticed I'm able to achieve higher stable oc (over 1500) using low leakage voltage and live oc of 116 or less. Without low leakage i can barely acheive 1400 oc at anything over 110 live oc. Never noticed this much difference in internal voltage stability in previous kernel version. I wonder what's changed?
So I was trying to mess around with CPU profiles and I noticed that the low end of the CPU is clocked at 1GHz. If I lower it with Rom Toolbox, it just goes right back up after I leave the menu. the profiles won't stick, governors don't make a difference, and I'm a little confused.
Can someone shed some light on this for me?
I thought the lowest speed was 384 MHz? Install CPU Spy and check what it says.
It is 384MHz. The lower frequency change because of project butter that make the cpu run at a higher frequency when you touch the screen.
Sent from my Nexus 4 using xda app-developers app
Dont you need a custom kernal in order to change the clock speeds?
sent via xda premium with nexus 7
No, we can already change it but it won't stick since it has its own frequency management.
Sent from my Nexus 4 using xda app-developers app
Is this somewhat similar to perflocker in HTC devices? It had to be disabled to change any cpu settings AT ALL with the stock kernel.
hervelo said:
No, we can already change it but it won't stick since it has its own frequency management.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
That is why..
sent via xda premium with nexus 7
ed10000 said:
I thought the lowest speed was 384 MHz? Install CPU Spy and check what it says.
Click to expand...
Click to collapse
You're right. I guess it just has its own profile to set at 1GHz when the screen is on, because the CPU Spy showed it in Deep Sleep/384Mhz for the majority of the night.
test1
Is it ok for me to have a task in Tasker that changes the governor everytime the phone sleeps and wakes? Is that harmful to my device?
not sure about if it's dangerous or not but I am curious a to why you would want to... sleep is sleep not much of anything happening to warrant a change
Sent from my Nexus 4 using xda premium
QUIETLYloud said:
not sure about if it's dangerous or not but I am curious a to why you would want to... sleep is sleep not much of anything happening to warrant a change
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well, I've found that my battery lasts a lot longer when the powersave governor is on, even while in sleep. When the screen is on I have it change to ondemand so i get a nice smooth UI. When in sleep with ondemand on, it drains faster than when I have powersave on and have it clocked to 288000 MHz.
Brendan12695 said:
Well, I've found that my battery lasts a lot longer when the powersave governor is on, even while in sleep. When the screen is on I have it change to ondemand so i get a nice smooth UI. When in sleep with ondemand on, it drains faster than when I have powersave on and have it clocked to 288000 MHz.
Click to expand...
Click to collapse
You have it clocked at 28.8 GHz? Pretty sure you're going to melt your phone. (I kid)
I believe he meant 288 GHz. He's from the future and is trolling us.
Sent from my Nexus 4 using xda premium
Branden pls
Sent from my Nexus 4 using xda app-developers app
Totally fine, but you might encounter stability problems.
Lol. My bad, was just copying what Trickster Mod said.. :/ I have the min at 288 MHz so when power save is on it underclocks to that.
I just don't want to screw up the hardware by jumping back and forth between ondemand and powersave.
Sent from my Nexus 4 using Tapatalk 2
Try out this Tasker script : http://forum.xda-developers.com/showthread.php?t=1018245
hello guys.
i just want to ask this very simple question, what MAX lowest freq i set on the G2? stock at 2.3ghz. can i set it at 1.5ghz? will it battery life?
thanks
Yes you can adjust cpu but you should have root. If you have root then use setcpu
Sent from my GT-I9001 using xda app-developers app
thanks man! yes i have root, and i already set my Freq at 1.7ghz. so, will it somehow increase battery life? or battery will be the same?
thanks
Not that much if you do a lot yes but if you use it moderately it will be useless
Sent from my VS980 4G using Tapatalk
Create different profiles in setcpu . I had made a profile in which when i yurn off the screen the cpu comes to 252mhz(maximum) which saves battery
Sent from my GT-I9001 using xda app-developers app