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.
Related
Hi... I have rooted my Samsung GS2 and payed for the OC app TEGRAK ..
But every time I go over 1400mhz the phone gets very unstable.
It even feezes at 1400 mhz when i use my navigon app...
I have tested it at 1500 mhz.. But reboots in a kind of save mode.,,,
At 1400mhz i runs Quadrant smooth with 4200 in score
And 56 MFLOPS in Linpack
But why is my phone so unstalbe?
But why is my phone so unstalbe?
Click to expand...
Click to collapse
Because it's supposed to run at 1.2Ghz.
If every SGS2 was able to run at 1.4Ghz without any issue I guess Samsung would have set them at 1.4Ghz by default (since battery life is obviously the least of their concerns ^^). When CPUs are produced, there's always variations in quality. what usually happens on x86 CPUs is that they're tested, sorted according to their max stable frequency, and then sold under different names and at different prices. For Exynos my guess is that any CPU that fails to pass the 1.2Ghz bar is just ditched, and they keep the others, some of which will work at 1.4Ghz, whereas some won't.
Now if you want to gain more stability, you can always try to increase the voltage, it usually gets more stable as voltage increases, but it also gets hotter (which can cause it to crash, or may even permanently damage the processor).
BlueScreenJunky said:
Because it's supposed to run at 1.2Ghz.
If every SGS2 was able to run at 1.4Ghz without any issue I guess Samsung would have set them at 1.4Ghz by default (since battery life is obviously the least of their concerns ^^). When CPUs are produced, there's always variations in quality. what usually happens on x86 CPUs is that they're tested, sorted according to their max stable frequency, and then sold under different names and at different prices. For Exynos my guess is that any CPU that fails to pass the 1.2Ghz bar is just ditched, and they keep the others, some of which will work at 1.4Ghz, whereas some won't.
Now if you want to gain more stability, you can always try to increase the voltage, it usually gets more stable as voltage increases, but it also gets hotter (which can cause it to crash, or may even permanently damage the processor).
Click to expand...
Click to collapse
At 1.4ghz the phone will also get hotter and it decreases the lifetime if you run 24/7 at 1.4ghz
Ok.. I know about the x86 cpu's.. But didn't think it was the same in ARM cpu's-
But I see ALOT SGS2 that runs 1800mhz..
I guess that I just have one of the not so OC lilkes...
Overclocking won't always work for everyone at same levels.
I've also seen evidence to suggest that OCing significantly reduces the life of the SGS2. Nobnut had his phone vastly overheating even on stock speeds, and constantly rebooting... He overclocked. A number of others reported similar.
Overclocking is not simple and it is not that you just click on 1400/1500 MHz and you are Overclocked. A lot of things matter here. When we overclock in our Desktops then we have to test it very thoroughly, setting up the right VCore, Bus voltage, Multiplier, checking the stability and temperature etc. etc. Tegrak OC is a nice and simple software to use, but it can't be perfect when you can't set all the settings manually other that just higher the clock rate. Personally I'd always stay with stock speed as incorrect OC could harm my CPU and GPU.
Regards.
If you know anything about overclocking then you'll understand that there are a variety of factors that affect the overclocking of a system. The overclock headroom you get from a processor varies, add to that the variables in component tolerance in the circuit board and you have a huge variety of factors that can limit the maximum frequency that you can overclock your system to.
I'll give you an example using my computers. Click on the images below:
Both processor overclock similarly on using the same components and that was the maximum I could get out of them. Now when I bought an EVGA X58 Classified motherboard and overclocked the Xeon W3520 I got it up to 4704 MHz with less vCore and less CPU VTT. All of this was done with aircooling.
My point is that not all systems will overclock the same even though they share the same model components.
just a quick question
Depends on what the phone is doing. Stock can go to 1200mhz if required. By the same token, if the phone only needs 200mhz for a given task, then that's what it will use.
In what context are you asking the question ?
No basically i was checking antutu benchmark and the maximum it said was 800mhz.
was i just looking at the wrong info or is it the max its clocked at? cpu it says is 200 - 800
Default Clock speed for the Galaxy S2 is 200mhz to 1200mhz (1.2Ghz)
In Antutu, if you click on the 'i' on the bottom of the screen and scroll to System Info, it should show CPU Frequency as 200.00 - 1200.00 MHz, unless you have it underclocked.
Also, from what i understand, Antutu aswel as other apps always show the S2 cpu as ARM Cortex-A7 processor, when in actual fact its an ARM Cortex-A9 processor
Have you set a profile in an app that can set the CPU min/max (Voltage Control, Set CPU, etc, etc) ? I use 200-800 as a default profile.
So far as benchmarks/info they provide are concerned, I wouldn't know given I personally think benchmarks are a complete waste of time (and have never run one on my phone).
Essentially, on stock, your CPU should have a 200-1200mhz range, and the CPU speed at a given point in time will vary depending on what the phone is doing as I said in my previous post.
Oh I see thanks to both of you
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.
Does anyone know if changes made to scaling governor or clock speeds are applied to all four cores or only to core #1? How would you verify that said changes have been applied to all cores?
I dont know much about this stuff and just assumed that it applied to all cores, but today i was just wasting some time with benchmarking apps and in the Device Details tab of the "Vellamo Mobile Benchmark" app, it showed only Core #1 was effected by any changes i made. The other three cores were unchanged...any thoughts?
I used "no-frills cpu control" to select governor and clock speed.
Thanks
I am certain that any change in governor for core 0 will affect the other cores equally.
Sent from my Nexus 4 using xda premium
I was messing around with this a bit ago. I use perfmon app. Any change in frequency or governor only seem to effect core 0. Also in that process I noticed my cores1-3 got stuck at only up to 1134 MHz. I can't seem to fix that anymore
Sent from my LG-E970 using Tapatalk 2
after waiting impatiently for the arrival of your op2 , many are disappointed with the low battery standby....specially if you are using LTE.
issues :
1) even having such a large battery, getting poor battery life.
2) even if the phone is idle, battery drains :crying:
so after having it for almost 2 weeks, i have learned most of the cpu tuner and battery saving apps wont work with op2, its not because of software, basically snapdragon 810's big little architecture is new and apps in the market are not compatible with this octacore new chipset.
and because of very less manufacturers are using this SOC as we now know why... and they were right... it heats up a lot!!! so app developers have not concentrated an specific app for this SOC.
so after lots of mix and matches, finally have come up with a stable solution as follows :
a) your phone should be rooted.
b) install 3c cpu manager from playstore.
c) open minimum 6 apps in background maximum the better.
( remember if no apps are running in background then cpu manager will show only maximum 1.555 ghz. max frequency and 384 mhz low frequency single setup only and big little architecture dual setup wont be shown ie: 810 has 4 cores running @ 1.555 ghz max and other 4 cores @ 1.76 ghz max. and both setups at 384 mhz minimum. )
d) open cpu manager, there should be 2 different setups, if not then open more apps in background, simply change the governor to ON-DEMAND, from interactive and set it on and reboot, as i have noticed with interactive governor even during standby, processor does not stays idle at lower frequencies.
after changing the governor, i have noticed that during standby cpu frequencies are in idle or at the lowest. which highly improvises the battery standby life and haven't noticed any performance degradation.
you can even limit the higher cores frequencies from 1.76 ghz to 1.55 ghz... improving up-to some limit of over heating issues and better standby time.
these are just the findings i discovered with my phone, so don't blame me if anything goes wrong, do it at your own risk.
buntybauva said:
after waiting impatiently for the arrival of your op2 , many are disappointed with the low battery standby....specially if you are using LTE.
issues :
1) even having such a large battery, getting poor battery life.
2) even if the phone is idle, battery drains :crying:
so after having it for almost 2 weeks, i have learned most of the cpu tuner and battery saving apps wont work with op2, its not because of software, basically snapdragon 810's big little architecture is new and apps in the market are not compatible with this octacore new chipset.
and because of very less manufacturers are using this SOC as we now know why... and they were right... it heats up a lot!!! so app developers have not concentrated an specific app for this SOC.
so after lots of mix and matches, finally have come up with a stable solution as follows :
a) your phone should be rooted.
b) install 3c cpu manager from playstore.
c) open minimum 6 apps in background maximum the better.
( remember if no apps are running in background then cpu manager will show only maximum 1.555 ghz. max frequency and 384 mhz low frequency single setup only and big little architecture dual setup wont be shown ie: 810 has 4 cores running @ 1.555 ghz max and other 4 cores @ 1.76 ghz max. and both setups at 384 mhz minimum. )
d) open cpu manager, there should be 2 different setups, if not then open more apps in background, simply change the governor to ON-DEMAND, from interactive and set it on and reboot, as i have noticed with interactive governor even during standby, processor does not stays idle at lower frequencies.
after changing the governor, i have noticed that during standby cpu frequencies are in idle or at the lowest. which highly improvises the battery standby life and haven't noticed any performance degradation.
you can even limit the higher cores frequencies from 1.76 ghz to 1.55 ghz... improving up-to some limit of over heating issues and better standby time.
these are just the findings i discovered with my phone, so don't blame me if anything goes wrong, do it at your own risk.
Click to expand...
Click to collapse
This has nothing to do with apps, just poor drivers on the kernel side, scheduler isn't properly coded for this SoC, and the fact that there is no dynamic hotplugging options available without causing the phone to reboot under certain circumstances doesn't benefit us any. Check out some of the custom kernels, as they may increase your idle battery life, on my own kernel I saw .5% drain per hour max. For reference I saw about 20 hours idle and sitting at 89% on my kernel.
DespairFactor said:
This has nothing to do with apps, just poor drivers on the kernel side, scheduler isn't properly coded for this SoC, and the fact that there is no dynamic hotplugging options available without causing the phone to reboot under certain circumstances doesn't benefit us any. Check out some of the custom kernels, as they may increase your idle battery life, on my own kernel I saw .5% drain per hour max. For reference I saw about 20 hours idle and sitting at 89% on my kernel.
Click to expand...
Click to collapse
i really appreciate your findings with the kernel, but my post is intended for people like me who does not wants to mess up with a stock kernel, so that future OTA updates can be patched without much hassle.
as you see, oxygen os is quite new and incomplete when compared with other's have to offer. so i expect lots of future updates immediately by the OP to improve and stabilize the OS.
I am giving snapdragon battery guru a try, it's for Qualcomm processors. But I'm not very experienced in this stuff. I think it has helped but if someone with more experience wants to give it a try. Maybe they can shed some new light on this subject.
This is the result with on-demand governor settings when phone is idle. with stock kernel and stock frequencies.
Ondemand has always been my fvorite for all past phones. in op2 however it always reverts back to original after interactive. the best battery saver for any phone is swithching to 4.4.2. Azimg batteru life. unfortunately notpossble with op2
buntybauva said:
i really appreciate your findings with the kernel, but my post is intended for people like me who does not wants to mess up with a stock kernel, so that future OTA updates can be patched without much hassle.
as you see, oxygen os is quite new and incomplete when compared with other's have to offer. so i expect lots of future updates immediately by the OP to improve and stabilize the OS.
Click to expand...
Click to collapse
Being rooted alone will prevent OTA updates. You have to flash the full stock ROM when there's an update anyway which would overwrite the kernel.