Hi Guys,
I've been using custom kernel/ROM for sometimes now, and I hear a lot about overclocking.
And I know that overclocking is "not so good" for the phone. Was wondering whether the same applies for under-clocking also.
Oh, and 1 more question is about decreasing just the "Minimum CPU frequency" to something like 245MHz. Will that be bad for the phone?
neo4u said:
Hi Guys,
I've been using custom kernel/ROM for sometimes now, and I hear a lot about overclocking.
And I know that overclocking is "not so good" for the phone. Was wondering whether the same applies for under-clocking also.
Oh, and 1 more question is about decreasing just the "Minimum CPU frequency" to something like 245MHz. Will that be bad for the phone?
Click to expand...
Click to collapse
Our phone support overclocking to 729 max and min 320 if you underclock it your phone will be laggy and not responding . Those frequencies are the best for it and will not harm your phone.
Sent from my LG-P500 using Tapatalk 2
Christian Nothing said:
Our phone support overclocking to 729 max and min 320 if you underclock it your phone will be laggy and not responding . Those frequencies are the best for it and will not harm your phone.
Sent from my LG-P500 using Tapatalk 2
Click to expand...
Click to collapse
ya i know underclocking will definitely reduce performance. What if I keep the Max freq as 600MHz and reduce the Min freq to 245MHz. I just want to know whether it will harm my phone or not.
neo4u said:
ya i know underclocking will definitely reduce performance. What if I keep the Max freq as 600MHz and reduce the Min freq to 245MHz. I just want to know whether it will harm my phone or not.
Click to expand...
Click to collapse
No it will not harm your phone!
I'm using oc since the first week I owned my phone and it's running fine.So, min freq:480(it use the same freq as lower clocks and reduces wakelocks) and max:600 or more
Sent from my LG-P500 using xda premium
FPChaim said:
I'm using oc since the first week I owned my phone and it's running fine.So, min freq:480(it use the same freq as lower clocks and reduces wakelocks) and max:600 or more
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Actually the point of underclocking is to use a different frequency, 245 will use a lower frequency than 480. Also, frequency has absolutely nothing to do with wakelocks, 122 will have the same number of wakelocks as 806. You should set the minimum to whatever works for you, some people like 245, some people like 320, some people like 480. Underclocking can't damage the phone, so use whatever works for you.
bluespoon4 said:
Actually the point of underclocking is to use a different frequency, 245 will use a lower frequency than 480. Also, frequency has absolutely nothing to do with wakelocks, 122 will have the same number of wakelocks as 806. You should set the minimum to whatever works for you, some people like 245, some people like 320, some people like 480. Underclocking can't damage the phone, so use whatever works for you.
Click to expand...
Click to collapse
Are you sure...?Take a look on what fserve posted in his kernel thread:" NOT underclock below 480MHz. At lower speeds, wakeups-from-idle per second are bigger than 480MHz and they share the same voltage, so thats leads to more battery drain. It's recomended to use: MIN 480 / MAX YOUR CHOICE more about it: http://forum.xda-developers.com/showthread.php?t=999064 and here: http://forum.xda-developers.com/show...2&postcount=22"
Edit:link to his thread:http://forum.xda-developers.com/showthread.php?t=1227682
Edit 2ne link is broken and the other got abbreviated so you have to visit his thread
Sent from my LG-P500 using xda premium
FPChaim said:
Are you sure...?Take a look on what fserve posted in his kernel thread:" NOT underclock below 480MHz. At lower speeds, wakeups-from-idle per second are bigger than 480MHz and they share the same voltage, so thats leads to more battery drain. It's recomended to use: MIN 480 / MAX YOUR CHOICE more about it: http://forum.xda-developers.com/showthread.php?t=999064 and here: http://forum.xda-developers.com/show...2&postcount=22"
Edit:link to his thread:http://forum.xda-developers.com/showthread.php?t=1227682
Edit 2ne link is broken and the other got abbreviated so you have to visit his thread
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
I have been using MIN FREQ 245 for the past two days., and I got a better battery life
neo4u said:
I have been using MIN FREQ 245 for the past two days., and I got a better battery life
Click to expand...
Click to collapse
I'm using min freq 480 and my phone sleep very well too
Sent from my LG-P500 using xda premium
I use setcpu to set the clock to 122 - 320 while the screen is off and the phone sleeps very well but sometimes it freezes when I wake it up so I had to change it to 245 - 320 and evertyhing is fine now.
Related
I am on CM7 (n72) with faux's latest 0.2.9 uv kernel, and am undervolted all the way down to 10 mv each on the 389 and 503 frequencies with no performance changes. I have tried setting it with both setcpu and pimpmycpu. I know there can't be a way for my phone to be working at those levels so what am I doing wrong? Am I missing something?
Sent from my LG-P999 using XDA Premium App
If you lowered the voltages to -10 then you have not lower to aggressive. If you lower the volts to much device will not boot. I am at -50 across all values. Lower the volts is supposedly to improve battery (life) performance not speed performance.
To be quite honest with the questions the OP is asking he shouldn't be messing with an UV kernel.
Ok, I believe the kernel has a built in minimum mv that it will run at, regardless of how low you set the values in setcpu. Im certain that faux posted what that low value was once when someone else was bragging about undervolting by -250...you aren't really undervolting that low. However, some of our phones cant even handle that minimum low voltage, so consider yourself lucky.
Sent from my LG-P999 using XDA Premium App
mmapcpro said:
Ok, I believe the kernel has a built in minimum mv that it will run at, regardless of how low you set the values in setcpu. Im certain that faux posted what that low value was once when someone else was bragging about undervolting by -250...you aren't really undervolting that low. However, some of our phones cant even handle that minimum low voltage, so consider yourself lucky.
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
Thank you that's what I was wondering about! Sorry if I didn't phrase my question correctly, I meant the voltages were set at 10 mv, not lowered by 10
Sent from my LG-P999 using XDA Premium App
I ran into the same problems. In another thread, faux123 stated that the way tegra works, each adjacent frequency level should only differ by ~ 100mV. so if you started with 1000mhz @ 1000 mV, then the next frequency will be 800mhz @ 900mV (just an example). so pretty much it all depends on how low of a voltage your top frequency can run on. if your voltage difference between 2 adjacent frequencies is larger than ~100mV, then it means nothing.
again, I gathered this info from faux. I have no sold knowledge whatsoever
prettyboy85712 said:
To be quite honest with the questions the OP is asking he shouldn't be messing with an UV kernel.
Click to expand...
Click to collapse
We all have to start from somewhere, be nice. It sounded like he misspoke.
Hey guys will overclocking drain the battery quicker even with stock voltages?
Sent from my Nexus S using XDA Premium App
Different voltages are specified as stock for different frequencies. As the frequency changes, the voltage does too. Running 1200mhz with the stock 1000mhz voltage will probably cause instability and crashing.
Harrb, great post.
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.
And if increase voltage, the power consumption should also increase.
i haven't played with voltages yet but in my experience the benefits of overclocking are minimal anyway, and they make nexus reboot often and other bad things :/
With the right settings you can get a fully stable and functional overclock, but it is on a per-phone basis due to varying quality of the same CPU during manufacture.
Harbb said:
Different voltages are specified as stock for different frequencies. As the frequency changes, the voltage does too. Running 1200mhz with the stock 1000mhz voltage will probably cause instability and crashing.
Click to expand...
Click to collapse
Currently I'm using icup kernel speedy 5 clocked at 1.4 and its been extremely stable. So what your saying is that the voltages automatically increase when I select a higher frequency, because I did not change them manually.
Sent from my Nexus S using XDA Premium App
xmatrix13 said:
Currently I'm using icup kernel speedy 5 clocked at 1.4 and its been extremely stable. So what your saying is that the voltages automatically increase when I select a higher frequency, because I did not change them manually.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Open NSTools and select Voltage tab. That's the list of "stock" voltages for each frequency.
suksit said:
Open NSTools and select Voltage tab. That's the list of "stock" voltages for each frequency.
Click to expand...
Click to collapse
Thanks
Sent from my Nexus S using XDA Premium App
A CPU governor such as on demand, lulzactive and lazy tells the CPU what clock to be at and automatically change. While reading, it will be at 100 or 200mhz, while playing a game it will be at the maximum clock you tell it to. Saves power this way.
your asian said:
i haven't played with voltages yet but in my experience the benefits of overclocking are minimal anyway, and they make nexus reboot often and other bad things :/
Click to expand...
Click to collapse
yes, usually 1 GHz is enough , UV or OC also may reduce hardware's physical life
OK i have read up a little about live oc, but really i still dont understand it.
In NS tools there are 3 settings.... a % an "oc target low", "oc target high"
As i understand it the percentage is just how much each step of the cpu scaling gets bumped... so if your at 110% @ 1000mhz step it would actually be 1100mhz. And @ 110% the buss speed would be at 220mhz vs the stock 200. (is that correct)
But as far as the other two settings... oc target low, oc target high... what are those?
Really im just looking for a little more incite on how live oc works.
Thanks guys!
You can tell it to live oc within certain frequencies. So if you only want to to be on live oc from 200-800mhz, you can set it to do that
Sent from my Nexus S 4G using xda premium
rocket999 said:
You can tell it to live oc within certain frequencies. So if you only want to to be on live oc from 200-800mhz, you can set it to do that
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
AHHH ok so the min and max are the range in which the live oc takes place. below and above those min and max values it goes back to normal?
how much rise voltages from 1300cpz/100liveoc to 1320cpu/110liveoc?
Bus OC don't work at all. I've tried 3d benchmarks with and without this and there are not difference
Sent from my Nexus S using Tapatalk 2
raulillo88 said:
Bus OC don't work at all. I've tried 3d benchmarks with and without this and there are not difference
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
you must not be doing it right or applying works for me
EDIT: you do realize it will only over clock the freq of the low target and high target.
For example you run your benchmark and your cpu settings are going to be affected on the I/0 scheduler and cpu governor.
if i run Sio ~ On-Demand @ 100/1000 and my Live OC is 1200/1400 your not going to be using the OC settings because its only designed to, to OC the freq you chose it to.
So to make it work for benchmarking purposes i would run Sio ~ Performance @ 1400/1000 or even 1400/1400 so it would only use those OC'ed freqs. and have the Live OC either 1400/1000 say @ 105% or 1400/1400 @ 105% so it run Straight OC'ed freqs only.
trying to make some custom setcpu profiles and curious if anyone knows what the lowest safe cpu speed for when the screen is off and also while in a call and the screen is off?
Right now I'm on VI and I'm running 368 max and 245 min which is the lowest min for this rom. I always run the lowest on min and 1 higher for max on sleep settings. I don't encounter any issues.
Sent from my HTC Glacier using xda premium
Don't go below 200 when screen is off. You'll get the "sleep of death" at the most inconvenient times.
estallings15 said:
Don't go below 200 when screen is off. You'll get the "sleep of death" at the most inconvenient times.
Click to expand...
Click to collapse
I have never dealt with that issue.
Sent from my HTC Glacier using xda premium
coupetastic-droid said:
I have never dealt with that issue.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Well don't do it or you will
Sent from my MyTouch 4G using xda app-developers app
OP, you may want to look into andrev_oc or virtuous oc daemon. Both are superior to setcpu profiles.
estallings15 said:
OP, you may want to look into andrev_oc or virtuous oc daemon. Both are superior to setcpu profiles.
Click to expand...
Click to collapse
Nope, they aren't, i have programed scripts for both and I own SetCPU. Stick with SetCPU
Sent from my HTC Glacier using xda app-developers app
bas3balman said:
Well don't do it or you will
Sent from my MyTouch 4G using xda app-developers app
Click to expand...
Click to collapse
I have already gone under 200mhz for sleep frequencies. Android revolution goes under 200 and I would run it under 200 always till now that I'm on VI.
Sent from my HTC Glacier using xda premium
I run lowest at 187MHz @ 700mV without any problem. I also set my screen off freq to that. Never tried one below that freq.
Here's a little info on using an overclocking daemon vs setcpu taken from the virtuous unity thread.
Introduction to the new Overclocking Daemon
This ROM features a completelynew wayof Overclocking and managing screen states.
The History But before explaining it further, let's talk about previous solutions. There are several different approaches to achieve "screen-state-scaling". That means basically thatthegovernor changes if you turn the screen off and changesbackto normal when turning the screen on.
This is mainly used to restrict the amount of CPU usage (the frequency in fact) during screen off. This can lead to a major battery life increase.
The solutions so far were:
Apps likeSetCPU,which changeautomaticallythe governor based on profiles Integrated solutions in the governor itself
Both these solutions have major problems.
The one with a tuner app is always a little laggy right after turning on the screen because SetCPU (or any other CPU tuner) needs some time to change the governors (up to 7 seconds). This leads mostly to major lag in the lockscreen.
The second solution is the smartass governor. It has already a screen-state-scalingincluded,so it reduces the frequency when the screen turn off. This could be a really nice solution but it has some problems too. Smartass most of the time is not really stable and has problems with its frequency scaling.
Be aware that the daemon only works if all CPU tuner apps are deinstalled. Otherwise it deactivates itself.
ibuddler said:
I run lowest at 187MHz @ 700mV without any problem. I also set my screen off freq to that. Never tried one below that freq.
Click to expand...
Click to collapse
Thats very low. Surprised you do not get any issues.
Wish I could find the thread, but I was on a custom ROM that set the minimum CPU frequency to something below 200 by default, and I couldn't send text or MMS messages. Really weird.
OK, first of all I'd like to apologise for all the questions I keep posting. Im quite a noob with android, and coming from an iPhone, it's been a big leap. I'm just overwhelmed by the android system and how open it is! But I do all this cool stuff to my android like everyone else, although I don't wanna ruin a £350 phone by doing something stupid without guidance! (I'm just a big kid really! ) Which is why I keep posting questions, because it's hard to Google/Search XDA for this stuff...
Whenever I search XDA for 'Nexus 5 Overclocking' all I get is ROM threads, so this will be a thread for everything [under][over]clocking! Share your most effective results, and ask the pros questions!
I'll start it off...
I've Underclocked before, but now I wanna Terry out some heavy emulators (dolphin emulator, Nintendo 64 emulator ect.) But I don't think my phone is powerful enough to run these games full speed underclocked... I want to OVERclock it now, so which apps do I need to achieve this, how do I do it, and what are the most effective values for it?
Thanks,
Pro_Vickers.
Sent from my Nexus 5 using Tapatalk
The kernel defines whether or not you can overclock.
There is no real need to in the nexus 5 though.
If it is choppy at 2.3ghz then there is something wrong with the emulator.
In context I play final fantasy 9 on the psx emulator fpse using opengl graphics (which is limited to single core) and still get a constant 60fps
Sent from my Nexus 5 using xda app-developers app
ProVickers said:
I want to OVERclock it now, so which apps do I need to achieve this, how do I do it, and what are the most effective values for it?
Click to expand...
Click to collapse
Hi,
First you need a kernel with overclock (Franciscofranco, Trinity, ElementalX, etc...).
For the apps Franciscofranco have its own app (Francsico Kernel Updater-> FKU) and Trinity kernel also (Trinity Kernel Toolbox-> TKT), all available on the Play Store.
You can use a "generic" app like Trickster Mod, Play store too.
With the apps you choose your max CPU freq and it's done...
For overclocking there is no "most effective value" it depends of the voltage and what your CPU can handle. 2,4/2,5 Ghz seems reasonable (with some kernels you can go above like 2,8 Ghz).
Try a "safe" overclock first like 2,4/2,5 Ghz, and don't set the CPU freq "at boot" to avoid any problem like bootloop in case your CPU can't handle these freqs.
Maybe you'll need to raise a bit the voltage for these CP freqs, it depends of your CPU binning.
You can apply your settings at boot via the app when you are sure that all is stable (so after a few days of test with your use).
In any case you'll need to test in different situations to see if all is fine (hard and normal use)...
Alex240188 said:
The kernel defines whether or not you can overclock.
There is no real need to in the nexus 5 though.
If it is choppy at 2.3ghz then there is something wrong with the emulator.
In context I play final fantasy 9 on the psx emulator fpse using opengl graphics (which is limited to single core) and still get a constant 60fps
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I've Underclocked and it's choppy, but I know it's not the emulators fault because of the reviews, and I've played with it before I Underclocked... The problem is, I forgot how I Underclocked, so can you tell me how I clock it back to stock GHz?
Sent from my Nexus 5 using Tapatalk
P.S
I have Franco kernel so clocking shouldn't be a problem should it? Also can I use trickster mod for it? Thanks
viking37 said:
Hi,
First you need a kernel with overclock (Franciscofranco, Trinity, ElementalX, etc...).
For the apps Francisco have its own app (Francsico Kernel Updater-> FKU) and Trinity kernel also (Trinity Kernel Toolbox-> TKT), all available on the Play Store.
You can use a "generic" app like Trickster Mod, Play store too.
For overclocking there is no "most effective value" it depends of the voltage and what your CPU can handle. 2,4/2,5 Ghz seems reasonable (with some kernels you can go above like 2,8 Ghz).
Try a "safe" overclock first like 2,4/2,5 Ghz, and don't set the CPU freq "at boot" to avoid any problem like bootloop in case your CPU can't handle thes freqs.
Maybe you'll need to raise a bit the voltage for these CP freqs.
In any case you'll need to test in different situations to see if all is fine...
Click to expand...
Click to collapse
Hi,
I've Undervolted -75, so should overvolt or set it back to stock values so I can safely try out 2.5Ghz?
Sent from my Nexus 5 using Tapatalk
ProVickers said:
P.S
I have Franco kernel so clocking shouldn't be a problem should it? Also can I use trickster mod for it? Thanks
Click to expand...
Click to collapse
Re,
Yes you can overclock with Francisco's kernel and yes you can use Trickster mod...
ProVickers said:
Hi,
I've Undervolted -75, so should overvolt or set it back to stock values so I can safely try out 2.5Ghz?
Click to expand...
Click to collapse
Try with your undervolt...
But in first I would try with the original voltage, not necessary overvolting...
Try and see, only you can know if it will be safe or not...
viking37 said:
Re,
Yes you can overclock with Francisco's kernel and yes you can use Trickster mod...
Try with your undervolt...
But in first I would try with the original voltage, not necessary overvolting...
Try and see, only you can know if it will be safe or not...
Click to expand...
Click to collapse
All I can see in FKU is Max CPU frequency (960MHz), min (422MHz) and GPU frequency (320MHz) under GPU control... What do I tinker with to get it to 2.4GHz?
Sent from my Nexus 5 using Tapatalk
ProVickers said:
All I can see in FKU is Max CPU frequency (960MHz), min (422MHz) and GPU frequency (320MHz) under GPU control... What do I tinker with to get it to 2.4GHz?
Click to expand...
Click to collapse
Re,
Max CPU at 960 Mhz
You only see this CPU freq? Maybe your phone is actually to hot and the CPU freq is decreased?
"Click" on Max CPU freq then scroll down to see all the CPU freqs...
viking37 said:
Re,
Max CPU at 960 Mhz
You only see this CPU freq? Maybe your phone is actually to hot and the CPU freq is decreased?
"Click" on Max CPU freq then scroll down to see all the CPU freqs...
Click to expand...
Click to collapse
Sorry, I mean that's what it's set at, I can see all of the frequencies, but which ones do I set?
Sent from my Nexus 5 using Tapatalk
ProVickers said:
Sorry, I mean that's what it's set at, I can see all of the frequencies, but which ones do I set?
Click to expand...
Click to collapse
Ok...
Hum... you choose the one you want, you want to overclock so overclock. The stock CPU freq is 2,26 Ghz so if you go above this freq you overclock...
Maybe it's why "But I don't think my phone is powerful enough to run these games", like you said, if your max CPU freq was at 960 Mhz...?
Default the stock max freq will be 2260 MHz or 2.26ghz depending on how it's displayed.
I'd leave your undervolt as it is for now and just increase the max frequency and see if it becomes smooth for what you need
Sent from my Nexus 5 using xda app-developers app
viking37 said:
Ok...
Hum... you choose the one you want, you want to overclock so overclock. The stock CPU freq is 2,26 Ghz so if you go above this freq you overclock...
Maybe it's why "But I don't think my phone is powerful enough to run these games", like you said, if your max CPU freq was at 960 Mhz...?
Click to expand...
Click to collapse
Alex240188 said:
Default the stock max freq will be 2260 MHz or 2.26ghz depending on how it's displayed.
I'd leave your undervolt as it is for now and just increase the max frequency and see if it becomes smooth for what you need
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I know that my phone is fast enough (obviously, it's a nexus 5 beast!), and I know that I lowered my CPU frequencies, but it's just that I forgot what the defaults were, and how to change it. I know now, thanks you guys! P.S should I change my min frequency or is that fine?
Sent from my Nexus 5 using Tapatalk
ProVickers said:
I know that my phone is fast enough (obviously, it's a nexus 5 beast!), and I know that I lowered my CPU frequencies, but it's just that I forgot what the defaults were, and how to change it. I know now, thanks you guys! P.S should I change my min frequency or is that fine?
Click to expand...
Click to collapse
Ah ok, you should have explained it at the beginning... , you're welcome
Stock min CPU freq is 300 Mhz..., not sure you'll see any gain to set it to 422 Mhz...
Set it again at 300 Mhz and see...
In any case if sometimes you have a doubt about some stock settings, disable the set on boot option and reboot, all the stocks settings will go back. Or in FKU, App settings then clear data for FKU.