Hello,
I'm writing this thread to know which processor options would be optimal in our minis. The best settings, which give me the best performance/battery, I've found are:
CPU Governor: SMARTASSV2 (Default)
Min Freq: 19MHz
Max Freq: 748MHz
Undervolt: TRUE
I'm also using Apex Launcher. Which settings are you using?
Note: This are just my results, be careful when you change your processor settings.
fuchini said:
Hello,
I'm writing this thread to know which processor options would be optimal in our minis. The best settings, which give me the best performance/battery, I've found are:
CPU Governor: SMARTASSV2 (Default)
Min Freq: 19MHz
Max Freq: 748MHz
Undervolt: TRUE
I'm also using Apex Launcher. Which settings are you using?
Note: This are just my results, be careful when you change your processor settings.
Click to expand...
Click to collapse
Whats the purpose of Undervolting when you have it's max frequency as overclock?
zvdelossantos said:
Whats the purpose of Undervolting when you have it's max frequency as overclock?
Click to expand...
Click to collapse
Because it undervolts on every frequency below 600, and his minimum is 19, so when the phone is idle or doesn't need all of the processing power he saves battery
The SmartAss governor is very good at picking the right frequencies for any given job, so it doesn't allways run on 748Mhz, not even when you're using the phone.
SmG67 said:
because it undervolts on every frequency below 600, and his minimum is 19, so when the phone is idle or doesn't need all of the processing power he saves battery
Click to expand...
Click to collapse
That is the same very purpose of SMARTASSV2 to undervolt your device when idle or on sleepmode and overclocks it when on process. So ticking the undervolt wont affect your device because the one that manage the frequency will be the COUgovernor.
zvdelossantos said:
That is the same very purpose of SMARTASSV2 to undervolt your device when idle or on sleepmode and overclocks it when on process. So ticking the undervolt wont affect your device because the one that manage the frequency will be the COUgovernor.
Click to expand...
Click to collapse
The SmartAss Governor only governs the frequencies, not the voltage that the Processor uses. there is a difference between the speed the cpu runs on (Mhz) and the amount of Electricity (Volts) it gets fed
Say Qualcomm has said it needs 5 volts to run at the stock frequency of 600Mhz, then the processor will always get 5 Volts, no matter which frequency it uses.
Undervolting will feed it less than the 5Volts when the frequencies are lower, SmartAss won't do that, it will run the 19Mhz still on 5Volts.
(Voltages are examples, i don't know the exact values, but I know that running on 122 or less will be stable on less than half of the nominal power)
SmG67 said:
The SmartAss Governor only governs the frequencies, not the voltage that the Processor uses. there is a difference between the speed the cpu runs on (Mhz) and the amount of Electricity (Volts) it gets fed
Say Qualcomm has said it needs 5 volts to run at the stock frequency of 600Mhz, then the processor will always get 5 Volts, no matter which frequency it uses.
Undervolting will feed it less than the 5Volts when the frequencies are lower, SmartAss won't do that, it will run the 19Mhz still on 5Volts.
(Voltages are examples, i don't know the exact values, but I know that running on 122 or less will be stable on less than half of the nominal power)
Click to expand...
Click to collapse
Nice yes yes. good reply. now I know whats the use of undervolting. thanks for the explanation
SmG67 said:
The SmartAss Governor only governs the frequencies, not the voltage that the Processor uses. there is a difference between the speed the cpu runs on (Mhz) and the amount of Electricity (Volts) it gets fed
Say Qualcomm has said it needs 5 volts to run at the stock frequency of 600Mhz, then the processor will always get 5 Volts, no matter which frequency it uses.
Undervolting will feed it less than the 5Volts when the frequencies are lower, SmartAss won't do that, it will run the 19Mhz still on 5Volts.
(Voltages are examples, i don't know the exact values, but I know that running on 122 or less will be stable on less than half of the nominal power)
Click to expand...
Click to collapse
nice to see some piece of truth over here (not perfect, but well explained)
de-noobing is good from time to time
xda is overcrowded of false answers given by people thinking they know but don't
anywhere, at anytime, newbies asking get fake answers from people wanting to help but failing to do so , due to lack of knowledge.
as everyone, i might be one of these, but try not to be.
make sure you know what you are talking about before spreading your (incomplete or false) knowledge
this was my thought of the day
matmutant said:
nice to see some piece of truth over here (not perfect, but well explained)
de-noobing is good from time to time
xda is overcrowded of false answers given by people thinking they know but don't
anywhere, at anytime, newbies asking get fake answers from people wanting to help but failing to do so , due to lack of knowledge.
as everyone, i might be one of these, but try not to be.
make sure you know what you are talking about before spreading your (incomplete or false) knowledge
this was my thought of the day
Click to expand...
Click to collapse
Would you mind to add that to FAQs to avoid false answers?
Tom.K said:
Would you mind to add that to FAQs to avoid false answers?
Click to expand...
Click to collapse
of course i don't
do you mean only the explanation about oc/uv ?
i can add it, note that a while ago i wrote pieces of information about those things
Hey, thanks a lot for all the replies. I had no idea why my settings worked like i wanted.
Related
Hi All,
I am writing this post to know what are the pros and cons for overclocking the phone. I know it helps to increase the clock rate, however if the phone can support it, why didnt the manufacturers made it that way.
And if we do it, are there any chances that the phone might blow up and stop working or something.
I tried to search on this topic but cudnt find anything.
please reply
Iam using LG Optimus One
Thanks !!
Hello.
The main plus is the increase in productivity phone.
The downside is that, theoretically possible to burn the phone, but I repeat it theoretically.
I myself have clocked the phone and nothing terrible has happened to him.
I don't think anything's going to burn as kermel always goes in panic if it can't handle it.
Sent from my LG-P500 using XDA Premium App
4silvertooth said:
I don't think anything's going to burn as kermel always goes in panic if it can't handle it.
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
The processor won't burn, as 4silvertooth says the kernel will panic and you'll end up in an endless bootloop; 729 - 748 mhz is safe, 800mhz in most cases cause the kernel to panic.
Well oc has nothing to do with proceesor (don't laugh). Well at hardware level the clock (MHz) and processor are two different thing the crystal provides the MHz to processor and in return it computes at that speeds. So by oc we are telling crystal to oscillate at higher frequency. So if our processor can't handle higher frequency it tells kernel get lost I am not doing this for you as I am not able to execute instruction at such speeds. And all the governers are nothing but a rule for processors to execute tasks. Like if you select performance governer it tells CPU to execute at Max speed you have set. So what ever you set the min frequency it always uses Max speed no need to change min if u r using performance governer same for powersaving governer no matter what you have set for max it always work on min. So all the governers has different sets of rules.
Pros: CPU speeds up the execution
Cons: Crystal may get hot.
Bye.
Sent from my LG-P500 using XDA Premium App
22VIN said:
The processor won't burn, as 4silvertooth says the kernel will panic and you'll end up in an endless bootloop; 729 - 748 mhz is safe, 800mhz in most cases cause the kernel to panic.
Click to expand...
Click to collapse
No you wont go in bootloop.
Let me explain.
You will go in boot loop if you have set speed that processor can't handle and selected set on boot option. As the processor can't handle it and you are telling it to be always in that mode. Dont select set on boot. After reboot manually select oc. The second reason would be currepted filesystem as after kernel panic your phone has rebooted with unsaved changes chances are that filesystem table is currepted. Theres a command to check that I forgot name its like chkdsk for Linux. But no rom impliments that on unhandled reboots.
Sent from my LG-P500 using XDA Premium App
Good info
4silvertooth said:
Well oc has nothing to do with proceesor (don't laugh). Well at hardware level the clock (MHz) and processor are two different thing the crystal provides the MHz to processor and in return it computes at that speeds. So by oc we are telling crystal to oscillate at higher frequency. So if our processor can't handle higher frequency it tells kernel get lost I am not doing this for you as I am not able to execute instruction at such speeds. And all the governers are nothing but a rule for processors to execute tasks. Like if you select performance governer it tells CPU to execute at Max speed you have set. So what ever you set the min frequency it always uses Max speed no need to change min if u r using performance governer same for powersaving governer no matter what you have set for max it always work on min. So all the governers has different sets of rules.
Pros: CPU speeds up the execution
Cons: Crystal may get hot.
Bye.
Sent from my LG-P500 using XDA Premium App
Click to expand...
Click to collapse
Sent from my LG-P500 using XDA App
i'm more concerned about the processors life. can overclocking to 729 in long term kill the processor.
coolbuy said:
i'm more concerned about the processors life. can overclocking to 729 in long term kill the processor.
Click to expand...
Click to collapse
Even I am concerned about such facts, and also why didnt the manufacturers made it that way if it can support such speed without any problem.
Thanks for those who replied, Much appreciated
Hello, I have an HTC thunderbolt, rooted with CM7, and installed setcpu and used autodetect and I put the CPU govern to "conservative" with minimum GHz 245 and maximum 1.8GHz and I am just wondering if this is safe? because I read some threads about Compatible kernels and I jave no idea what that means, they were also talkimg about undervolting, which agaim I do not know means, anyways thanks for reading
Watoy said:
Hello, I have an HTC thunderbolt, rooted with CM7, and installed setcpu and used autodetect and I put the CPU govern to "conservative" with minimum GHz 245 and maximum 1.8GHz and I am just wondering if this is safe? because I read some threads about Compatible kernels and I jave no idea what that means, they were also talkimg about undervolting, which agaim I do not know means, anyways thanks for reading
Click to expand...
Click to collapse
If your device will run reliably at 1.8GHz, then there's not much to worry about as long as the voltage isn't too high. High voltages and heat can shorten the SoC's life or kill it altogether. Generally, I don't recommend running that fast because the performance increase isn't as great from 1.6GHz to 1.8GHz as it is from 1.41GHz to 1.6GHz. These cores weren't meant to run any faster than 1.5GHz really, and anything past that doesn't increase the performance as much as the numbers might suggest.
Also, a conservative governor probably isn't ideal if you're willing to run a device that fast. That governor would seldom, if ever, use that kind of speed. I'd suggest smartass, smartassV2, ondemand, or interactive if you're looking to see a good boost in performance.
If you're looking for an app to view and adjust voltages, IncrediControl works well. For all the nitty-gritty of overclocking, I'd recommend reading my OC guide. It's in the "Second Post" of my Q&A thread. If you've got any questions, feel free to hit me up.
So does over clocking just speed things up? What are the real benefits
Boggus said:
So does over clocking just speed things up? What are the real benefits
Click to expand...
Click to collapse
I look at it like this. My screen eats up most of my battery. The less time it's on, the better. Overclocking uses more power for the CPU, but the display spends less time telling you it's waiting. It doesn't really add functionality, just speed and efficiency.
Hello, I keep getting random reboots on my HTC Legend. I don't think the problem is related to the rom because I tried many of them and still the same problem. I've read that it may be related to the radio version but I don't know which version should I upgrade to
ROM: CyanogenMod 7.1.0
Baseband Version: 47.26.35.04U_7.05.35.26L
Did u OC's the CPU? Maybe your frequencies are too high?
Try with a lower one.
Thanks for the reply, yes, i did try lower the Frequencies but still have the same problem
Doryon said:
Thanks for the reply, yes, i did try lower the Frequencies but still have the same problem
Click to expand...
Click to collapse
What frequencies are you using?
have you tried to change governor?
Currently using 787 max. and 400 min. and the governor is set onDemand
Doryon said:
Currently using 787 max. and 400 min. and the governor is set onDemand
Click to expand...
Click to collapse
It could also depend on the Kernel installed, but for a 600 MHz processor, 787mhz seems definitely too high for me. My friend has the same CPU in his ZTE Blade and he cannot OC more than 650mhz (obviously also depends on hardware).
What I suggest, is to OC's just a little above the normal value 600mhz (ex. 633/650mhz), and increase little by little the clock to find out at which freq. your phone start to experience spontaneous reboot.
I would also try the "smartass" governor with a min freq between 19/176 mhz.
Let me know.
yukinok25 said:
for a 600 MHz processor, 787mhz seems definitely too high for me.
Click to expand...
Click to collapse
Some devices (with 600mhz processors) can be overclocked to 864mhz (e.g. HTC Aria; but is overall stable at 806mhz).
Theonew said:
Some devices (with 600mhz processors) can be overclocked to 864mhz (e.g. HTC Aria; but is overall stable at 806mhz).
Click to expand...
Click to collapse
I am agree. My Hero can be overclocked up to 749mhz (525mhz default) , but at this OC suffer from spontanious reboot. The max freq. I can reach is 710mhz without problems.
This is why I said it depends on devices and hardware.
Probably 787mhz is too much for his phone.
I'm using CM9 RC1 on a Note right now and the default settings are 200 Mhz min and 1.4 Ghz max.
Is there any benefit to using a higher min like 500 Mhz or is it just a waste of power? I'd assume it would be slightly faster upon wake up.
You can always try, as long as you know what you're doing. Are you familiar with overclocking, and how to test higher clock speeds without having them set on boot until you have tested for stability. 200MHz seems a bit low for echo 0, but you can try to start bumping up echo table 0 values slowly and at small incremental increases. For instance, from 200MHz, go to 220MHz and test, then if stable bump up to 240MHz and so on. Jumping from 200MHz to 500MHz may not be the best idea without a "seasoning" of the CPU at echo table 0...
Sent from my MB865 using xda's premium carrier pigeon service
I've overclocked on PCs before but I'm not overclocking. I just want to know if there's any benefit to setting a higher min speed.
It probably will not yield any performance increase to clock your lowest frequently scaling higher, since likely your device's governor (I'm assuming) is set to mot_hotplug.
Unless you're using a governor setting of "performance" or the like, your CPU's governor will step down through the kernel's frequently tables as determined by the load. Again, unless you're running a governor setting that does anything but what is similarly done with mot_hotplug the CPU's core(s) will be turned off when not demanded.
Sent from my ME860 using xda premium
Ive been using android overclock. On demand. and staying at 350 to 1420 and its been working really well as far as battery usage
I´ve been using ondemand-noop min 245, max 1024
Ok. That was 2012. Now is 2020. Updates to minimum and maximum for Android 8/9???
quantum-codes said:
Ok. That was 2012. Now is 2020. Updates to minimum and maximum for Android 8/9???
Click to expand...
Click to collapse
Just to have said it: CPU speed affects performance of Android device, doesn't depend on Android version. The more a processor is stressed the more the battery is drained. IMHO CPU speeds matter less than they did in the past, thanks to the advent of multi-core processors as they installed in ( most ) modern phones. Multi-core processors always have a "mixed speed": Not all cores are stressed the same way. Also, note how these multi-cores processors are designed: Octa-cores for example aren't using all 8 cores at once. Octa-cores use 4 high speed cores and 4 low speed power efficient cores. An Octa-core uses the 4 power efficient cores most of the time, but switches to the higher speed cores as needed for power intensive tasks.
I don't think there is a way to configure each cpu-core's max /min speed separately. BTW: Even today most Android apps/games make use of 2 cores only.
Hey, i overclocked my ace 2 to 1100MHZ my question is, is it safe to keep it on maximum at all times?.
1100 MIN and 1100 MAX
Thank you.
That's probably something you shouldn't do as a "full-time" clock speed. Remember, your CPU's scaling frequency is determined upon load called upon from system process, applications, and so on. When load is minimal, the CPU scaling frequently will fall back to lower table speeds, and spike to higher when necessary. Having no "resting" frequency will cause: more heat generated from the lack of these lower frequencies, shortened battery life expectancy, and possibly shortened CPU lifespan.
Unless you're using a governor setting of "performance" or the like, your CPU's governor will step down through the kernel's frequently tables as determined by the load. Again, unless you're running a governor setting that does anything but what is similarly done with mot_hotplug the CPU's core(s) will be turned off when not demanded.
Be kind to your CPU, give it a break. I can't imagine any reason to clock to such high values to run all the time. Don't you put your phone to sleep ever? Why would you want the CPU running at 1100MHz while sleeping? Doesn't seem like a logical idea to me...
Sent from my MB865 using xda's premium carrier pigeon service
Thanks for replying, you are right i shouldn't have it on that frequency at all times when im not using it cause whats the point of that.
I am new to all this overclocking and rooting stuff, got a lot to learn haha.
iFrankie said:
Thanks for replying, you are right i shouldn't have it on that frequency at all times when im not using it cause whats the point of that.
I am new to all this overclocking and rooting stuff, got a lot to learn haha.
Click to expand...
Click to collapse
No worries. Just don't want to see you fry out your CPU by not giving it the ability to have 'downtime'.
Edit: You can even change the scaling frequency at echo 0 to a lower table value, to give even more ability to "rest". If you need any more info, don't hesitate to PM me. I've done a lot of experimentation with overclocking over the last several months...
Sent from my MB865 using xda's premium carrier pigeon service