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.
tegrak promised he was going to upgrade his tegrak overclock app to work with all kernels and it looks like he's delivered! (see http://forum.xda-developers.com/showthread.php?t=1101355
I'd installed the free version as tegrak suggested a couple months back to see if it would work with my phone. It didn't, but yesterday, it upgraded to version 0.6.0.9. I had a bullet kernel that allows OC to 1.2 ghz with no voltage adjustments. The free version doesn't OC but will let you know if the paid version will work with your phone.
The paid version ($2) works. At least on my phone it does. Maybe no need for special kernels anymore. I haven't tried it with a rom that doesn't support OCing and overvolting yet but I'm going to do that this weekend.
The higher speeds need overvolting and there's no directions on how to do it. tegrak overclock will officially only let you go to 1.3 ghz but if you select the fine "optimization" you can go way up beyond that. I immediately zoomed it up to 1600 mhz with no voltage adjustments and the phone locked up and started buzzing. I had to pull the battery and reboot. Don't do that! Go up a little at a time and then let the stability test run (pull down notification screen to see how many seconds are left.)
There are buttons to adjust by small amounts. You should be able to set it at 1.4 ghz with a little overvolting without too much trouble. Right now my phone is stable at 1524 mhz and core voltage of 1361 mv using an "on demand" profile of 100-1524mhz and it's not hot. Quadrant score at that setting was 3201. That's pretty good for a kernel that only supports OC to 1200 mhz.
I couldn't get to 1600 yet without locking up the phone -- needs more overvolting I figure.
If you have sgs overclock, after you up the speed, it will have the top speed bar at the bottom 100mhz and you will have to drag it up there. I don't know why this should make a difference but my quadrant score was in the 2700s before I did it.
Write down your figures 'cause if the phone locks up and you have to pull battery and reboot, the phone will ask you if you really want that speed that didn't work, and when you say "no" you'll be back at the beginning again.
There is more discussion in the 19000 forum on tegrak's 2.3.4 kernel (for I9000) and the OC app. according to tegrak's guide, the Galaxy S can be stably undervolted using his utility at various speeds and I guess save battery life:
speed standard core voltage undervolt
1000mhz 1275 mv 1225 mv
800mhz 1200 mv 1125 mv
400mhz 1050mv 950mv
200mhz 950mv 825mv
100mhz 950mv 800mv
There is a dialog in the app to set the voltage for each of these speeds in addition to setting the OC speed and voltage. I'm not sure whether tegrak has tested this on the various flavors of Galaxy S or whether he means the I9000. I'll just have to see.
here is his figure for a 1200mhz OC.
speed standard core voltage overvolt
1200mhz 1275 1310
Seems to be working good!
All nonsense and misspelled words courtesy of my unsupported samsung device.
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.
Does anyone with a kernel that allows CPU and voltage adjustments know what the lowest stable voltages are for each frequency? It's difficult to test if the voltages are stable across all of the frequencies, which is why I'm hoping others have worked this out already.
Has anyone done research into this and come up with solid numbers? Also, is there an app that stress tests each available frequency? It's pointless using something like antutu to stress test since it will just keep the cpu at my max of 1600mhz, whereas I need to test all of them.
Thanks in advance.
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.