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.
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.
Hey, I saw that all CPUs are currently locked down to 1593mhz. Our chip should have 2x1.5ghz for general use and 2x2.1ghz for high performance tasks.
But in stock as in custom Roms, I see all CPUs locked down, max freq 1593mhz and no control over queue processing, either from hotplug or CPU front. Is there something I missed? Or LG just lied to us?
I know from thermal point of view that our device would not be able to sustain 2.1ghz for a long time, but if the frequency is not even available, it is a serious matter... +500mhz is not something to overlook!
If thats true, thatd be a heartbreaking, the first thing I look to before choosing a device, is clock speed
Unlock the game optimization
I checked on cpu-z and frequencies. With optimization on, it won't go over 1,5 ghz but with that option off it is easily jumping to maximum clock speed (faster battery drain). Stock rom, don't know about custom roms.
Linux User said:
I checked on cpu-z and frequencies. With optimization on, it won't go over 1,5 ghz but with that option off it is easily jumping to maximum clock speed (faster battery drain). Stock rom, don't know about custom roms.
Click to expand...
Click to collapse
You mean game optimization in settings/battery? I think we do not have that option in custom ROMs (I am currently trying Aicp 12.1) and never changed it in stock. I will try going back to stock to disable that option and see if the frequency table changes... If it does, it will be a pre-requisite before flashing custom ROMs in our device. Still, it is something the kernel should handle.
I would underclock the device on my own, as I did with my good old G2, but not having the option for the CPUs to scale as intended is not cool...
Well, frequency table shows no change with stock, but somehow, CPUs 3 and 4 scale up to 2150mhz now.
I guess LG did not cheat in the strict sense of the word, but just does not want us to have control over our devices...
Sent from my LG-H850 using Tapatalk
Floodland said:
Hey, I saw that all CPUs are currently locked down to 1593mhz. Our chip should have 2x1.5ghz for general use and 2x2.1ghz for high performance tasks.
But in stock as in custom Roms, I see all CPUs locked down, max freq 1593mhz and no control over queue processing, either from hotplug or CPU front. Is there something I missed? Or LG just lied to us?
I know from thermal point of view that our device would not be able to sustain 2.1ghz for a long time, but if the frequency is not even available, it is a serious matter... +500mhz is not something to overlook!
Click to expand...
Click to collapse
So... I was freaked out after reading this thread, so i rushed to check using cpu Z and it turned out that mine is clocked at 2.15, so i don't know what is wrong u
The Snapdragon 820 inside the LG G5 has a quad-core processor which has 2 cores clocked at 2.15 GHz and two other cores clocked at 1.6 GHz (1593 MHz), it's the way the manufacturer (Qualcomm) decided the processor to be, the LG G5 is not underclocked. Some users may get different results in applications like CPU-Z or AnTuTu depending on which core the application is based on.
Android_420 said:
The Snapdragon 820 inside the LG G5 has a quad-core processor which has 2 cores clocked at 2.15 GHz and two other cores clocked at 1.6 GHz (1593 MHz), it's the way the manufacturer (Qualcomm) decided the processor to be, the LG G5 is not underclocked. Some users may get different results in applications like CPU-Z or AnTuTu depending on which core the application is based on.
Click to expand...
Click to collapse
The frequency table shown by kernel adiutor (or any kernel tweaking software) shows ranges 307-1593 for all processors.
I know the hardware behind, my first though was that LG underclocked it. Now I see the phone just hides its behavior and does not show the real table (or the available software is not able to see it).
We will need additional kernel development in order to effectively control the core speeds in our devices.
Case closed, thank you for the responses.
Floodland said:
The frequency table shown by kernel adiutor (or any kernel tweaking software) shows ranges 307-1593 for all processors.
I know the hardware behind, my first though was that LG underclocked it. Now I see the phone just hides its behavior and does not show the real table (or the available software is not able to see it).
We will need additional kernel development in order to effectively control the core speeds in our devices.
Case closed, thank you for the responses.
Click to expand...
Click to collapse
old versions of kernel auditor are buggy with the g5, they see it as a single quad core instead of big/little dual 2 cores. You need the newest kernel auditor.