Hi, I have some questions with kernels, overclock and governor. I'm using cm10.1 or cm11 or any JB or KitKat and I have some questions:
1- Wich are the best governor for daily use?
2- Wich are the safe levels to overclock the phone?
3- I saw that a lot of people uses OC in Min 122 and Max 806, Is this possible with few risks?
4- Wich are the risks of OC?
5- Should I use a specific kernel? Or the one with the customs ROMs are enough?
5- More questions after I get more information.
Thanks.
PD: I made this thread because the others OC threads are very old, before JB and when ICS was just released I think.
OC 806 can damage your phone for ever manage carefully this
Sent from my LG-P500 using Tapatalk
And what are the safest levels? And best governors? Im actually using smartass min 480 max 729
Overclocking will not "damage your phone for ever." Some of the P500s are stable at higher clock speeds than others, which is typical of mobile CPUs (even the two cores of my Sensation's CPU are stable at different maximum clock speeds). IIRC, my Optimus T was only stable up to 729 MHz. If you try to overclock higher than your phone is capable of, then it will freeze or reboot. There really isn't a "safest" level; any clock speed that your phone is stable at is going to be perfectly safe. Run a stability test or benchmark app from the Play store to check stability. IIRC, another easy way to test stability on the P500 is to open a camera app. The camera tends to crash the phone when the CPU is clocked too high. If you manage to crash the phone by doing any of that, then I recommend dropping down to a lower clock speed. Otherwise, the phone is fine and you can test a higher clock speed. FWIW, I'm pretty sure that most P500s are stable up to 729 MHz, but many of them are not stable higher than that.
I personally like to use Interactive governor. I think I used Interactive with min 480 and max 729 on my Optimus T. Governors Explained
chalo99 said:
Hi, I have some questions with kernels, overcloak and governor. I'm using cm10.1 or cm11 or any JB or KitKat and I have some questions:
1- Wich are the best governor for daily use?
2- Wich are the safe levels to overclock the phone?
3- I saw that a lot of people uses OC in Min 122 and Max 806, Is this possible with few risks?
4- Wich are the risks of OC?
5- Should I use a specific kernel? Or the one with the customs ROMs are enough?
5- More questions after I get more information.
Thanks.
PD: I made this thread because the others OC threads are very old, before JB and when ICS was just released I think.
Click to expand...
Click to collapse
1. I use smartass as governor (well on the jenkins build). It has a balanced battery and performance I think.
2. Regarding safe level, no overclock is safe, unless it is specified that the processor can handle overclocking over a certain period of time. That's why it is designed for a certain clock speed, because at the guaranteed clock speed you can get the most out of your processor without even breaking it.
3. Well overclocking on android depends on the ability of the kernel to handle overclocking situations. Some kernel can handle overclocking very well that the noticable errors are up to a minimum level. While setting the frequency to Min 122 and Max 806, it is not really safe to go to a maximum of 806 Mhz. As specified the maximum (safe) frequency of the processor is 600. so even going for 601 above or to 710 even if other claim that 710 is still a stable frequency will not guarantee that it will we stable at 710. Regarding the risk. overclocking in the first place is risky.
unless yo go y.o.l.o over your hardware.
4. Risks are. 4a. going beyond the maximum temperature your hardware can handle. can lead to fire (yeah it is true).4b. boot failure 4.c crashing of applications. 4.d etc etc.
5. Before, we use to have different kernel developers and different rom developers. as the the passed by and newer devices are being developed, some migrated to newer devices and abandoned the development for our beloved phone. Now I think only 1 developer is still developing (original development not just cuztomizing and stuffs it with design) androidmeda (check "jenkins armv6") and the kernel included in the rom is sufficient enough to handle overclocking (used it and set the freq to 320 - 710 at smartass). I also use sweetnsour's kernel before but i think he too abandoned the development)
5. k
engr_exxi said:
2. Regarding safe level, no overclock is safe, unless it is specified that the processor can handle overclocking over a certain period of time. That's why it is designed for a certain clock speed, because at the guaranteed clock speed you can get the most out of your processor without even breaking it.
Click to expand...
Click to collapse
That isn't true. Processor manufacturing is inexact, so some processors end up with higher clock speed capability than others. As the maker of a device, you have to set the clock speed low enough that ALL of the processors in ALL of the devices function properly. Setting the clock speed conservatively means that most or all of the devices are actually capable of functioning at a higher clock speed, which in most cases -- and certainly in the case of the P500 -- is completely safe. And it is extremely naive of you to believe that every processor or computer you buy is running at the "best and safest" speed as tested by the manufacturer. CPUs are often significantly underclocked simply to allow manufacturers to differentiate pricing. The same thing is done with finished products, including smartphones. For example, my HTC Sensation has a Qualcomm MSM8260 clocked (originally) at 1200 MHz. The HTC Sensation XE has the exact same processor clocked at 1500 MHz.
3. While setting the frequency to Min 122 and Max 806, it is not really safe to go to a maximum of 806 Mhz. As specified the maximum (safe) frequency of the processor is 600. so even going for 601 above or to 710 even if other claim that 710 is still a stable frequency will not guarantee that it will we stable at 710. Regarding the risk. overclocking in the first place is risky.
unless yo go y.o.l.o over your hardware.
Click to expand...
Click to collapse
Again, it is nonsense to say that overclocking this phone "is not really safe." You won't find one example anywhere of a person who has damaged this phone by overclocking it. These things don't get hot enough at any clock speed to damage the hardware.
4. Risks are. 4a. going beyond the maximum temperature your hardware can handle. can lead to fire (yeah it is true).4b. boot failure 4.c crashing of applications. 4.d etc etc.
Click to expand...
Click to collapse
4.a. Heat is probably the only legitimate concern with overclocking a smartphone, and that's exactly why there is no risk with the P500 -- it doesn't get anywhere near hot enough, at any clock speed, to cause any damage.
4.b. This shouldn't be a problem. If your phone is not setting clock speed on boot, then a crash/reboot will send your phone back to the original clock speed. Even if you make a mistake and change a clock speed that is being set on boot (which I actually did by accident just yesterday), you can boot directly into recovery and restore a backup.
4.c. Who cares? As I said before, if your system is unstable as a result of overclocking, then you should lower the clock speed. That isn't a problem.
4.d. *sigh*
But to each his own. If you don't want to go "yolo" with your antiquated $50 smartphone, then by all means, keep it at 600 MHz. Nevertheless, there is absolutely no way that you would damage it by overclocking, regardless of what you may believe.
Well, its overclocking and not overcloaking.
Small error, but make changes in the OP
rhar**** said:
Well, its overclocking and not overcloaking.
Small error, but make changes in the OP
Click to expand...
Click to collapse
I wrote it bad in the title, but in the middle of the post it was OK. Thanks anyway, ****ing spanish that you read it like you write it, or viceversa.
chalo99 said:
Hi, I have some questions with kernels, overclock and governor. I'm using cm10.1 or cm11 or any JB or KitKat and I have some questions:
1- Wich are the best governor for daily use?
2- Wich are the safe levels to overclock the phone?
3- I saw that a lot of people uses OC in Min 122 and Max 806, Is this possible with few risks?
4- Wich are the risks of OC?
5- Should I use a specific kernel? Or the one with the customs ROMs are enough?
5- More questions after I get more information.
Thanks.
PD: I made this thread because the others OC threads are very old, before JB and when ICS was just released I think.
Click to expand...
Click to collapse
The phone won't work above 729MHz. And the only risk i can thinknof is depleting battery life faster.
Im actually using interactive min 480 max 806.
That permit no lag and normal reactivity.
Obviously there is a battery drain than normal.
I've also use a seeder application.
Related
either with setcpu or voltage control...would someone care to just explain how to use these apps.
I understand the governers, and I understand the min / max.
So If I bump that max up to 1400 or even 1600 and leave the minimum down...what exactly does that do?
If paired with on demand does it mean it will use as much processor as it needs to perform a task all the way up to the max of what I have it set to?
also, the thing that seems to confuse me mostly are the individual sliders you can adjust per frequency.
I know this is broad question, but I was just hoping someone wouldnt mind explaining this to me as best as possible...or at least dumb it down for me.
I have googled and searched, and really havent found clear answers to me personally to understand it.
thanks
I personally use voltage control extreme.
In regards to the individual sliders you speak of, I believe that those control how many volts the phone uses at each particular frequency. You don't want to turn the voltages down too low/high though because you can freeze your phone and have other problems.
I use the "conservative" governor and seem to get the best battery life with it.
By overclocking to 1400 or 1600 it allows for your phone to run applications, videos, etc. smoother, by using the remaining cpu capabilities of the phone's hardware. The drawbacks of overclocking are that it sucks the battery very quickly, it can cause the cpu to overheat, and can also decrease the life of the processor.
Hope that helps some!
So what is a safe top end? To run on a daily basis.
Sent from my SAMSUNG-SGH-I997 using XDA App
Every CPU is different, some will handle OC better than others. It all comes down to what is stable for you. Also, it isn't overclocking that decreases the life of the processor, but overvolting. Just set the voltages as low as possible while maintaining stability, test using a benchmarking app. Also, ondemand is the best choice of governor IMO.
Sent from my SAMSUNG-SGH-I997 using XDA App
Perpetrator said:
Every CPU is different, some will handle OC better than others. It all comes down to what is stable for you. Also, it isn't overclocking that decreases the life of the processor, but overvolting. Just set the voltages as low as possible while maintaining stability, test using a benchmarking app. Also, ondemand is the best choice of governor IMO.
Sent from my SAMSUNG-SGH-I997 using XDA App[/QUO
But doesn't overclocking cause the phone to heat up? I suppose it also depends on what temperature the phone is rated to safely run at too though doesn't it? Cause with increased temperatures I am pretty sure the processor's life could be impacted. But that is probably only if you overclock for a extended period of time.
I would suggest staying at 1.2 for daily use, but if you are doing something that requires a little more cpu you can just bump it up until you don't need it anymore.
Just my 2 cents worth.
Click to expand...
Click to collapse
I know that some ppl OC to 1.6 with ondemand gov and use that as a stable setting... others report problems, FCs, ... think it depends on individual phone.
Some stay at 1.4 to be cautious...
The UV section is where I hear a lot of dissenting opinion. Some say -100 across the board gives best battery/stability... others say voltage should be high toward 1600 and UV more as you approach lower frequencies... personally I find that a graduated setup is best but I am not an expert.
Just sayin' what I've read here.
I see a lot of overclocked kernel editions, and I am wonder could someone explane me, except extensive battery draining, instabillity and overheating of device, what is and is there any crucial positive point of overclocked kernels ?
Overclocked kernels are simply kernels whose speed limit had been raised above the stock speed.
That increases perrormans dramatically as is visible by different benchmarks utilities.
You are correct to assume that higher clock would require some extra voltage and that the phone will get hotter. But it is not always noticeable and is mostly depentant on the configuration.
The cpu clock is not always at the highest possible. Different governors define what speed should the cpu be at any time. If there's a lot of work the cpuspeed would increase and if it idles a lot it would decrease.
I love 3 oc kernels, Sebastian's, bricked and faux. They all have different philosophies but all are excelent, do not overheat and save gather.compared to stock though they allow higher cpu freqs.
I suggest you create a nandroid backup and try some of.there kernels. Give it atleast two days.before you make up your mind about it, and try another if you wish, till you find the one that is right for you.
Sent from my HTC Sensation using xda premium
I agree. I never see the point of over clocking. I always limit my processor to 1.18 or even 1.13 and never have any problems with overheating or poor battery life!
I used overclock kernels for a long time on my gs2. Its nearly the same like with a desktop CPU. Every CPU had it's own work range, many CPUs a
are even able to work with higher frequency but lower voltage than standard. This causes in higher speed with lower power consumption!
all you need is a kernel which allows individual voltage settings for each speed which you can set with setcpu.
BUT my opinion is that even the gs2 with 1,2 GHz dual core was faster than any Android app had needed, so the gs3 at all!
ATM I've setted the max frequency in setcpu to 600 mhz and I can't see any lags or missing speed...
So I guess many people are more looking for benchmarking than real practical advantage..
but undervolting is a real great thing for power hungry smartphones!
Gesendet von meinem GT-I9300 mit Tapatalk 2
You all right guys. That is why I asked myself that question because there is hard to find modded kernels with default speeds and all new goodies, because I have noticed even I "limit" overclocked kernel in my Hypersensation CM7 Cyanogen Settings, it happens that some kernels from time to time speeds up to overclocked value, even in settings they were limited, and that impact widespread device causes instabillity ( and corrensponding unpleasent situations of forced battery pulling).
Last good kernel what I find for my CM7 ( I don't like ICS) is Bricked_XE-1.6.beta7 and with this release of CM7 it seems that kernel edition further development stops.It runs on 1526 Mhz and I allways wonder why shouldn't it run "out of the box" on default speed...
Does anyone have suggestion link, (because I couldn't find it )for any CM7 modded kernel with all new goodies, but running on default Sensation XE Mhz speed ?
i have been using overclocked Kernels for a while now and rarely have any problems, the phone is quick, very quick and the battery drain is really not that different and that is running it at 1.72 with both cores permanently on
tin2404 said:
[...] because I have noticed even I "limit" overclocked kernel in my Hypersensation CM7 Cyanogen Settings, it happens that some kernels from time to time speeds up to overclocked value
Click to expand...
Click to collapse
This really should not happen. The maximum frequency for a governor is set through /sys pseudo-fs and (assuming the governor is not buggy) strictly followed. Maybe you have some leftover scripts somewhere messing with /sys?
tin2404 said:
( and corrensponding unpleasent situations of forced battery pulling).
Click to expand...
Click to collapse
And this should -- like already pointed out -- only be the case under heavy load. Normally, a sensible governor will only set frequencies necessary to satisfy the current load.
about time for me to change roms again. i know there are many with this option, but have never chose to pursue that option due to lack of understanding benefits. always seemed to get satisfactory battery life out of phone, but could it be better? i have noticed different speeds on my phone with different roms but is this something that can speed up and keep the smooooth in my phone?
just thought i would get some feedback of the advantages and disadvantages of overclocking and undervolting.
will it harm my infuse?
what are good settings?
what exactly would the OC or UV each do?
if i run a search on this, i know i am going to get the phone book and just figured i would get a more specific answer directly as opposed to piecing little bits together and still not being confident in what my interpretation would be.
everyone in the infuse community always seems to have the answers and dont steer the dullards such as myself in the wrong direction.
you guys are the MAN, and well, you women.....your the woman i reckon
captemo said:
will it harm my infuse?
Click to expand...
Click to collapse
No, so significant damage can be done with overclocking. Alhought if you set your ghz too high your phone might become unresponsive, overheat and/or auto reboot your device. This is normal if your on GB and some ICS roms. Don't see it much on JB becuase the some kernels dont support it. Just be sure to play with your settings and MAKE SURE SET ON BOOT IS DISABLED or else your phone will be stuck in a bootloop when overclocked beyond stable settings.
captemo said:
what are good settings?
Click to expand...
Click to collapse
I usually stick with 1400 ghz because 1600 ghz[max] drains battery too quickly for not much of performance boost and 1600 is considered unstable on most GB and ICS roms. As for CPU governor Id stick with ONDEMAND.
captemo said:
what exactly would the OC or UV each do?
Click to expand...
Click to collapse
OC is over clocking your processor to a higher ghz for better perofmance and under volting is drawing less energy
Is there like a guide saying what each CPU governor does? Because some of them are pretty confusing with their terminology, like smartassv2
Garen21 said:
Is there like a guide saying what each CPU governor does? Because some of them are pretty confusing with their terminology, like smartassv2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1420742
I used to under volt a lot to get better battery life. But it seemed to make a couple apps hang now and then.
I am now on Scotts PA JellyBean ROM. Battery life is very good for me stock with this. So I have left under volt to stock settings.
Normally I'll run on smartassV2 governer. With NOOP i/o. And 100mhz - 1400mhz.. just for a little extra boost.
When I know I'll be playing a game or multitasking, I'll boost it to 1600mhz.
Overall stock settings run amazing, both battery life and performance, on Scott's PA JB and CM10.
After doing some reading, I believe I can get better results from using the above settings. It all depends on what your personal goal is.
The biggest concern you should have when overclocking is mentioned above. Boot loop, just make sure you test it for a while with set on boot un checked.
Undervolting you can go to low and also boot loop, so same applies here... leave set on boot un checked. All phones are different on what settings they run best at. Just gotta play around and see what works for you.
A good rule of thumb for under voting... go down 25mv at a time and test it out... keep going down 25mv until you get a problem or boot loop and then go back.. then you'll know your max.
You can safely under volt more on the lower frequencies than you can the higher ones. Personally I never undervolted more than 100mv across the board. And when I did, I usually kept it around -50mv.
Sent from my SGH-I997 using xda app-developers app
not for infuse but a good reference for ocuv. explains what they do
http://forum.xda-developers.com/showthread.php?t=1827635
Sent from my GT-I9300 using xda premium
This is the best guide I've found covering kernel and system tuning - CPU parameters, governors, schedulers, init.d, loadable modules, etc. It's for the SGS2 (i9000) and some of the governors/schedulers are not available on the Infuse, but much of this is applicable to our phone:
http://forum.xda-developers.com/showthread.php?t=1369817
As for OC/UV, as long as you stay away from the "Performance" governor (this runs the phone at max freq all the time), and undervolting below -75 to -100 you generally will be safe. As phones are different, it is important to test in gradual steps to ensure your phone will be reliable. Use a good CPU manager, like SetCPU, Antutu, or Voltage Control. Make sure you enable the "revert to stock" feature so that you can boot recovery and turn off any bad OC/UV. As noted above, do not check the enable on boot setting until you are certain you have a good config.
The decision to OC should take into account how you use the phone. If your phone is asleep more than 80% of the time on average, you can probably run an OC config and still have overall good battery life (i.e. lasting an entire day with nightly recharges). If you use your phone for music playback or something else that prevents it from sleeping, OC may not be for you. If you run CPU intensive games, it is better to disable UV settings while OCed.
Use CPU Spy to keep an eye on your time at each freq state (and sleep). Use the default battery stats and graph to monitor which apps are consuming the most battery. Use apps like Better Battery Stats, Android Assistant and Watchdog for more detailed monitoring of what is keeping the phone awake and which apps/processes are top cpu resource consumers. With this information you can identify problem apps and decide whether you should remove them from your phone.
From the "unintended functionality" side of the house, there are certain tweaks that will cause your phone to run at max freq ... mucking around with phone properties in build.prop can lead to runaway rild process problems (usually shows up as unusually high "Dialer" in the standard battery stats list and a phone that is warm or hot to the touch). Some of the tweak scripts in adrenaline and tbolt can cause similar problems. There is a known bug in the infuse network drivers that shows up as much higher than normal Android OS battery usage. This can usually be corrected (short term fix) by toggling Flight/Airplane mode off/on. Running the stock UCLB3 GB kernel also seems to minimize this issue (assuming you are running a GB ROM), but flash with caution as you will need to disable voodoo lagfix first. (You will also lose CWM recovery, OC/UV capability, and be on the slower stock file system setup).
I have done a fair amount of experimenting including lots of time on conservative governor with Fmax=1600 and never had any problem that I attributed to OC'ing.
In contrast I did find a limit on UVing. I just updated my thread with my experience on uv here:
http://forum.xda-developers.com/showthread.php?p=32552571#post32552571
The bottom line is that for MY phone, the following works fine:
100 Mhz: 950mv max – 50mv = 900 millivolts
200 Mhz: 950mv max – 25= 925 millivolts
400 Mhz: 1050mv max – 50mv = 1000 millivolts
800 Mhz: 1200mv max – 75 mv = 1125 millivolts
1200 Mhz: 1275mv max – 50mv = 1225 millivolts
1600 Mhz: 1400mv max – 75mv = 1325 millivolts
Some other links with others' experience suggestions about UV'ing for Infuse:
Hozw low is your undervolt?
http://forum.xda-developers.com/showthread.php?t=1693689&highlight=kernel
[Q] Recommended SetCPU settings?
http://forum.xda-developers.com/showthread.php?t=1292836&highlight=setcpu
You’ll note the last thread has comments from Entropy’s settings.
Also Zen and qkster gave advice in the first thread (my thread).
All three guys very well respected and worth listening to.
Entropy mentioned you can uv the higher frequencies more than the lower (different than what was posted earlier in this thread). I don’t know for sure but I’d lean toward Entropy’s advice on that matter.
I think all in all somewhere between 50 and 100 is the max you can expect to undervolt.
What can be achieved varies with phone as stated by many.
You are welcome to experiment with slowly decreasing. That's what I did.
But in the benefit of hindsight, the process of slowly decreasing is tedious. And going beyond the limit was a little scarey for me. Could've been worse if the phone crapped out at a critical time during "experimenting". Like almost everything related to battery life, the results (how much benefit) seem y subjective (difficult to measure quantitatively). Most people say they don’t notice a dramatic difference with UV. If you want to get the low hanging fruit without a lot effort, you might just try 50 down. That's what I'd do if I had to do it all over again.
By the way, setcpu can be set up to provide a failsafe escape route even if you go overboard. There is a zip file that will toggle the setcpu settings off when launched from CWM. You just have to put the zip file on your sd card before you start tweaking. See "safe mode" in the setcpu documentation.
started to wonder at first whether i would get any responses after 218 views and nothing, but i knew the community would come through as they always do. all the regulars as usual regulars ( Zen, Quickster and others) are always eager to help. i think you have all provided me with the valuable info i requested.
thank you much party people
Running: Asus Transformer TF101 (with Tegra 2 chip)
OS: EOS Custom ROM 78 (Jelly Bean) -- And THANKS to 'em!
Short Question: What the heck are those minimum/maximum MHz settings' optimal numbers?
Long Question: My TF101 w/ EOS Nightly #78 has an overclocking feature in it. Very cool. There are not one, but TWO, separate settings for the chip -- a minimum MHz (starting at 200MHz or something) and a maximum MHz (all the way up to 1600MHz). But after I messed some with it (and like a dunce did not write down the original values) I experienced some random reboots, usually after I closed the lid a while and then reopened it.
So, my question's long version (which is actually a number of questions), follows...
* What are the original values of the Tegra 2 chip in one of these babies? I mean, 1000MHz (1Ghz) is probably the maximum default setting, since that's the chip's official rating. But what's the minimum setting supposed to be at?
* Can I do something as crazy as to tell it to run minimum of 1200MHz and maximum of 1600MHz? In fact, I'm trying that right now and it seems to be working.... but I doubt I'll leave it that way even if it does (makes me nervous about messing up the hardware).
* What optimal settings have others tried with this chip in this (TF101) unit.... or even in other Tegra 2 based tablets?
Thanks for reading. Looking forward to comments.
shonkin said:
Running: Asus Transformer TF101 (with Tegra 2 chip)
OS: EOS Custom ROM 78 (Jelly Bean) -- And THANKS to 'em!
Short Question: What the heck are those minimum/maximum MHz settings' optimal numbers?
Long Question: My TF101 w/ EOS Nightly #78 has an overclocking feature in it. Very cool. There are not one, but TWO, separate settings for the chip -- a maximum MHz (starting at 200MHz or something) and a maximum MHz (all the way up to 1600MHz). But after I messed some with it (and like a dunce did not write down the original values) I experienced some random reboots, usually after I closed the lid a while and then reopened it.
So, my question's long version (which is actually a number of questions), follows...
* What are the original values of the Tegra 2 chip in one of these babies? I mean, 1000MHz (1Ghz) is probably the maximum default setting, since that's the chip's official rating. But what's the minimum setting supposed to be at?
* Can I do something as crazy as to tell it to run minimum of 1200MHz and maximum of 1600MHz? In fact, I'm trying that right now and it seems to be working.... but I doubt I'll leave it that way even if it does (makes me nervous about messing up the hardware).
* What optimal settings have others tried with this chip in this (TF101) unit.... or even in other Tegra 2 based tablets?
Thanks for reading. Looking forward to comments.
Click to expand...
Click to collapse
Generally its all up to your specific chip and how much it can handle as all hardware isn't created equal especially Tegra soc's... the stock speed is 1GHz for the TF but could easily run higher... i would only run your min so high if doing benchmarking not everyday use.. it will kill your battery faster, it would tho benefit benchmarking Because it would run at the highest speed and not have a chance to jump to a lower speed... wont do any damage to the chip since it has built in thermal throttling anyways... my suggestion would be setting your min to the lowest and With the max speed start at 1.2GHz with some stability tests, or heavy use at different OC speeds to find your chips sweet spot with both stability, Battery life and performance.. and have fun
DJLamontagneIII said:
Generally its all up to your specific chip and how much it can handle as all hardware isn't created equal especially Tegra soc's... the stock speed is 1GHz for the TF but could easily run higher... i would only run your min so high if doing benchmarking not everyday use.. it will kill your battery faster, it would tho benefit benchmarking Because it would run at the highest speed and not have a chance to jump to a lower speed... wont do any damage to the chip since it has built in thermal throttling anyways... my suggestion would be setting your min to the lowest and With the max speed start at 1.2GHz with some stability tests, or heavy use at different OC speeds to find your chips sweet spot with both stability, Battery life and performance.. and have fun
Click to expand...
Click to collapse
I'm not sure where the "thanks" button is yet here, but will try to figure it out. Wait.... I just did.
Tonight I backed the minimum down to the 800 vicinity (whatever that number is) and left the top number at 1600. My recent test has been to run Angry Bird, which is not the most stable program. It runs just fine at this setting. The battery is draining fast, though.
So you are suggesting that taking it all the way to the basement minimum-wise will still give me fairly stable top end? I keep wondering if there's any relationship at all between the two numbers, if at some point they don't affect one another adversely if too far apart? This idea is based on no knowledge whatever.
So any furhter thoughts welcome.
shonkin said:
I'm not sure where the "thanks" button is yet here, but will try to figure it out. Wait.... I just did.
Tonight I backed the minimum down to the 800 vicinity (whatever that number is) and left the top number at 1600. My recent test has been to run Angry Bird, which is not the most stable program. It runs just fine at this setting. The battery is draining fast, though.
So you are suggesting that taking it all the way to the basement minimum-wise will still give me fairly stable top end? I keep wondering if there's any relationship at all between the two numbers, if at some point they don't affect one another adversely if too far apart? This idea is based on no knowledge whatever.
So any furhter thoughts welcome.
Click to expand...
Click to collapse
It is best to leave the min freq as per default and push only the max freq. Then, you can set application profiles whereby you will allow an oc if you play a specific app(this feature requires an app that is called setcpu). This is to allow you to gain the best battery life(what you did is okay as well, but you'll have less battery life as the proc is running at 800mhz at min)
Otherwise, you can do it manually by setting the governor. For example, when you want to play games, set the governor to performance and oc your proc. When you don't want to play games anymore, then set it back to interactive or ondemand(or any other suggested governor for your device) to allow battery saving
wcypierre said:
It is best to leave the min freq as per default and push only the max freq. Then, you can set application profiles whereby you will allow an oc if you play a specific app(this feature requires an app that is called setcpu). This is to allow you to gain the best battery life(what you did is okay as well, but you'll have less battery life as the proc is running at 800mhz at min)
Otherwise, you can do it manually by setting the governor. For example, when you want to play games, set the governor to performance and oc your proc. When you don't want to play games anymore, then set it back to interactive or ondemand(or any other suggested governor for your device) to allow battery saving
Click to expand...
Click to collapse
I have setcpu but after mucking about with it managed to end up with an unstable system (spontaneous reboots, esp. after closing then opening lid and "waking up" the TF101). Currently I'm just using the EOS Rom's own system settings and having low end all the way to minimum (200 something) and top end at 1500+. The 1600 mhz setting is apparently a problem for this machine (the spontaneous resets again). But at 1500 whatever it seems just fine
One other issue, very important to all of us (harhar), is that Angry Birds seems unstable since I updated to this custom EOS rom. I noted elsewhere that someone said simply turning off wireless would disable ads and stablize the game. I've not tried that yet. Losing angry birds for me would not be a major blow.
What is overclocking?
Overclocking is the process of making a computer or component operate faster than the clock frequency specified by the manufacturer by modifying system parameters. One of the most important techniques is running at a higher clock rate (more clock cycles per second; hence the name "overclocking"), but other parameters, such as CPU multiplier and memory timings, can also be changed and would be considered to be overclocking. Operating voltages may also be changed (increased), which can increase the speed at which operation remains stable. Most overclocking techniques increase power consumption, generating more heat, which must be dispersed if the chip is to remain operational.
Advantage:
Higher performance in games, encoding, video editing applications, and system tasks at no additional expense, but with increased electrical power consumption. Overclocking can extend the useful life of older equipment. Adding noticible response time for multitasking and powerhungry applications and games.
Disadvantages:
Overclocking if it's not done with moderate rate can be very risky and potentialy might permanantly damage your device's hardware, plus it can cause a slight battery drain. If it's done correctly then you're good to proceed.
Undervolting :
Undervolting is reducing the voltage of a component, usually the processor, reducing the voltages of each step less than the original stock voltages.
Advantages:
Increase of Battery life.
The heat that come from the processor reduces.
Disadvantages:
Undervolting if it's applied correctly then it's good, Hard undervolting might make the device unstable and potentily will lead to bootloops and freezes.
CPU
Maximum clock that could be applied on The Galaxy S4 is XXXXmhz and the minimum is XXX mhz . I will add the stock clock values as soon as possible.
More to come asap !
SERIOUSLY?
A guide about overclocking when you don't even know what CPU the specific models will be getting?
AndreiLux said:
SERIOUSLY?
A guide about overclocking when you don't even know what CPU the specific models will be getting?
Click to expand...
Click to collapse
I as well, think that this is a bit strange...
AndreiLux said:
SERIOUSLY?
A guide about overclocking when you don't even know what CPU the specific models will be getting?
Click to expand...
Click to collapse
and probably the S600 version will not be OCable its already has throttling problem due overheating ( + its an OCed version of S4 pro )
Weird thread
sent from an Galaxy s3 GT I9300
Running perseus kernel 33.1 , XELLA 4.1.2 leaked build
forum.xda-developers.com/showthread.php?t=1784401
Dont click,you might regret , I won't be responsible if you brick ur head
jus sawed this guide tosee whats safe minimum voltage and other stuff! better to change title or a how to (i already know btw )
lol this is horrible! where's guide to udenervolt? i also underclaockd m cpu to 1GHZ that feels a lot lot colder and still freaking fast! even think more stable! also i wannt to underclaock the GPU too and also udnervolt it anyone knows how? i got i9500 octa