Just curious what everybody is setting their cpu minimum frequencies at. I am not too concerned with battery life so I was thinking of setting mine a little higher to keep everything as smooth as possible. Is there a risk to raising the minimum frequency?
Sent from my VS980 4G using xda app-developers app
pwshadow said:
Just curious what everybody is setting their cpu minimum frequencies at. I am not too concerned with battery life so I was thinking of setting mine a little higher to keep everything as smooth as possible. Is there a risk to raising the minimum frequency?
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
I think you would benefit more from choosing another governor instead Try intellidemand or interactive := Both of these should be better than ondemand
pwshadow said:
Just curious what everybody is setting their cpu minimum frequencies at. I am not too concerned with battery life so I was thinking of setting mine a little higher to keep everything as smooth as possible. Is there a risk to raising the minimum frequency?
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
i have mine set at 300000 so when my phone goes into deep sleep it's using little cpu power, but i also have interactive governor so that when i turn the screen on there's no delay and the kernel and cpu have what they need to be snappy.
this thread tells you all you need to know about governors and i/o schedulers.
http://forum.xda-developers.com/showthread.php?t=1663809
Related
Anyone know why?
Oxygen 2.2.2, Smartass Governor, underclocked to 800mhz.
I've seen many people state that there was no appreciable difference from 1000-800 mhz.
Thanks.
SComp23 said:
Anyone know why?
Oxygen 2.2.2, Smartass Governor, underclocked to 800mhz.
I've seen many people state that there was no appreciable difference from 1000-800 mhz.
Thanks.
Click to expand...
Click to collapse
use the ondemand governor. smartass on the ns sucks.
SComp23 said:
Anyone know why?
Oxygen 2.2.2, Smartass Governor, underclocked to 800mhz.
I've seen many people state that there was no appreciable difference from 1000-800 mhz.
Thanks.
Click to expand...
Click to collapse
Smartass is probably not ramping up the speed as moving the home screens is not taxing on the cpu. Thus your phone is likely running at your min CPU speed. Try setting a different governor or raising the min CPU speed.
Sent from my Nexus S 4G using xda premium
SComp23 said:
Anyone know why?
Oxygen 2.2.2, Smartass Governor, underclocked to 800mhz.
I've seen many people state that there was no appreciable difference from 1000-800 mhz.
Thanks.
Click to expand...
Click to collapse
What kernel do you use? Try netarchys for stock. Then change to smartass with 200 min 800 max mhz.
Sent from my Nexus S 4G
obsanity said:
What kernel do you use? Try netarchys for stock. Then change to smartass with 200 min 800 max mhz.
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Netarchy.
I changed it back to On Demand, 100mhz/800mhz. Problem solved.
SComp23 said:
Netarchy.
I changed it back to On Demand, 100mhz/800mhz. Problem solved.
Click to expand...
Click to collapse
Then it must be something with the oxygen ROM because I'm on CM7 and it doesn't make any difference smartass or on demand.
Sent from my Nexus S 4G
simms22 said:
use the ondemand governor. smartass on the ns sucks.
Click to expand...
Click to collapse
I just had another person in another thread swear that smartass was the best on Oxygen for battery life and performance. I'm confused now...
To be fair, I've experimented with interactive, on demand and smartass all at 800mhz and not noticed any difference in either performance nor battery life.
Sent from my Nexus S 4G
LordLugard said:
I just had another person in another thread swear that smartass was the best on Oxygen for battery life and performance. I'm confused now...
To be fair, I've experimented with interactive, on demand and smartass all at 800mhz and not noticed any difference in either performance nor battery life.
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Not all phones react the same.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
Not all phones react the same.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Why would my NS4G running Oxygen and yours running the same rom and settings behave differently?
Sent from my Nexus S 4G
General rule of thumb (for my phone anyway):
1200MHz, ondemand governor. Ondemand works the best on the NS :O
khartaras said:
General rule of thumb (for my phone anyway):
1200MHz, ondemand governor. Ondemand works the best on the NS :O
Click to expand...
Click to collapse
How's that on battery though?
After running at 800MHz, I really haven't noticed an appreciable decline in performance, but I have noticed decreased battery consumption.
LordLugard said:
Why would my NS4G running Oxygen and yours running the same rom and settings behave differently?
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Not all hardware is equal. My CPU may be able to run lower voltages than yours can. Your CPU may OC higher than mine etc. There could be a setting in a rom or kernel that your phone runs fine, but may cause mine to reboot.
Sent from my Nexus S 4G 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
Ive been getting smoother results underclocking the G2 at either 1.7 or 1.9 and knock on seems more quick to response, but when I tried video recording the 60 fps isn't smooth when you are clocked at the regular speed.. beware...I ran a benchmark on quadrant standard and got 17,250 constantly so it is underclocked per core... I want to hear your opinion on this and do you plan to underclock or already are. I feel like the ability to be more smooth within the UI helps a lot more now..let me know your thoughts!
bencozzy said:
From using trickster mod and setcpu to underclock they only underclock cpu0 the other three still use the full frequency range.
What app are you using?
Click to expand...
Click to collapse
No frills CPU control :0
At 1.9 my Antutu was the same add the One and oddly the graphics test dropped 15-20 frames even though we are not under clocking the GPU.
Sent from my VS980 4G using XDA Premium 4 mobile app
That's really odd tbh o.o did you try quadrent as well? :0
jrgilbert79 said:
At 1.9 my Antutu was the same add the One and oddly the graphics test dropped 15-20 frames even though we are not under clocking the GPU.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I got way higher even at 1.7ghz :0
jrgilbert79 said:
At 1.9 my Antutu was the same add the One and oddly the graphics test dropped 15-20 frames even though we are not under clocking the GPU.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
HeXaLox said:
I got way higher even at 1.7ghz :0
Click to expand...
Click to collapse
You're saying that by underclocking, you're getting a smoother UI but lower benchmarks?
No i got a higher benchmark than the guy who replied on my post. I did get a smoother UI and everything is less laggy. Ill post a pic of 2.3ghz idk if its actually at 1.7ghz or 2.3ghz ill do another test
whittikins said:
You're saying that by underclocking, you're getting a smoother UI but lower benchmarks?
Click to expand...
Click to collapse
All this is true. Just tried. It might be a TINY bit slower ui THOUGH
Sent from my LG-D800 using Tapatalk 4
What settings did toy use? Deadline? Noop? Interactive gov?
Sent from my VS980 4G using XDA Premium 4 mobile app
I am using the app called No-frills CPU Control and for 1.7ghz I am using row and Ondemand as the I/O governor and same settings for the regular clock as well..
jrgilbert79 said:
What settings did toy use? Deadline? Noop? Interactive gov?
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Underclocked at 1.7ghz first then regular clock at 2.27ghz
jrgilbert79 said:
What settings did toy use? Deadline? Noop? Interactive gov?
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am tending to believe that the regular clock speed is actually overclocked...just like how the galaxy s4 is overclocked 200mhz more than normal...however I could be wrong..
If you really want to see if this odd issue is actually happening download an app called Multicore CPU Control (the only app of its kind that seems to work with the LG G2). I use this to save battery by turning off all but one core, but it allows you full control over all your cores.
Download it, create a profile, and set each core to what you want. I had to save the profile first, then go back in to edit the latter 3 cores' frequencies.
I would suggest setting the min and max to the same and choosing Performance for the governor. Use a different app to set the scheduler.
Be sure to have something like Kernel Tuner to ensure that all your cores are running as you intended. If not, go back into Multicore CPU Control and re-save your profile again.
Would love to hear the results afterwards!
I used Multicore CPU Control.
The only way to set clock to CPU 1,2,3 is let them always active. If I leave dynamic for these cores, they still go up to 2,26 GHZ. I think this the reason why HeXaLox have a little decrement when underclock because it only did for one core.