Related
so, i am using the Fear Rom and with the OC karnel. i played around the max sittings to 1.4 and tried quadarant. amazing score of 4150. nice... but what will happen if i keep it at 1.4 ?
will it over heat the phone / burn the GPU/CPU when playing games for example ?
i understand the battery life will be shorter. but what other disdvantages ?
ll_l_x_l_ll said:
so, i am using the Fear Rom and with the OC karnel. i played around the max sittings to 1.4 and tried quadarant. amazing score of 4150. nice... but what will happen if i keep it at 1.4 ?
will it over heat the phone / burn the GPU/CPU when playing games for example ?
i understand the battery life will be shorter. but what other disdvantages ?
Click to expand...
Click to collapse
You could dmg ur cpu. But Tegra is known to run 1.8Ghz stable. So with 1.4 you should be good.
Sent from my LG-P990 using XDA App
Oh!! Great 1.8Ghz but only 1.4Ghz is very drain my battery to much.
In the long run, your cpu might get affected but its shouldn't happen so soon.
That said, in my honest opinion, don't need to OC the chip.
The same OCing rules apply from the PC World. The same batch of chips have varying maximum OCing capabilities and thus different stabilities. Although you can stably run a chip at a higher clock, it will definitely shorten its life (Sometimes it could kill it in a year, sometimes beyond what we can measure.). Chip makers purposefully OC chips during tests to simulate the stress effects of using the chip over a long period of time (OCing that makes it seem like the chip is being used for months or years.). Nvidia sticks the Tegra at 1 GHz half because it's cheaper to do so (don't need to ensure higher clock rates which would mean a larger percentage of their chips won't last doing it.) and half because of marketing (At the time, no one has 1.2 GHz like we do now. From what I've seen, Tegra 2 can do 1.2 GHz easy.).
So what it comes down to is how long you plan on keeping the phone and how lucky you are. =)
Imo, in the interest of power savings (P = (V^2)/R), the gains of OCing having an exponentially worse effect on battery life.
imho theres currently no point in oc'ing the Tegra2 in Optimus at all.
Theres no real life benefit, only theoretical benefit when running benchmark apps for show off.
Theres not a single application or game out there today that require more processing power than what the Tegra delivers at 1ghz - and not a single one out there that will run any better or faster by oc'ing because the demand for processing power to run the application or game at its maximum capacity are allready met at 1ghz
Basically there are only negatives in terms of decreased battery and cpu life for nothing but a screenshot of a higher quadrant (or whatever) score
If at some time in the future you should run into a game that would not run smoothly unless the cpu are oc'ed then it would make sence to do so - but for now not.
The games available today either do run perfectly smooth at 1ghz or if they dont, then they dont because of poor programming or other factors and they would still run poorly even if the cpu are oc'ed
Actually there are real life benefits until you find a game which really lags when you run it. Meaning, you should leave it as it is until next year.
It may damage the CPU like what others say but since lower clocks are undervolt it might last as long as a non OC (Stock).
But it will kill the battery faster as you will have to charge more often due to the higher power draws.
hi folks, thinking about leaving oc on permenantly (1200 mhz) I an aware of the dangers, but thought about getting some facts, my question is, how long have people been running art 1200 mhz without any issues, how many weeks or months?
Sent using TCP/IP
1200mhz refers to the highest clock. Your phone doesn't stick to that frequency all the time. It generally scales from 100mhz to 1200mhz. It doesn't really matter if you overclock your device except for effects on battery and I don't think there would be any effect on the Hardware as much as that of an Overclocked computer cpu and considering the average number of months people tend to use their mobile device before getting a new and a better phone.
dhiru1602 said:
1200mhz refers to the highest clock. Your phone doesn't stick to that frequency all the time. It generally scales from 100mhz to 1200mhz. It doesn't really matter if you overclock your device except for effects on battery and I don't think there would be any effect on the Hardware as much as that of an Overclocked computer cpu and considering the average number of months people tend to use their mobile device before getting a new and a better phone.
Click to expand...
Click to collapse
my phone spends approx 20% of its time at Max freq, thats 1/5 th of its time. I think there would be more potential damage than a computer cpu as these have much better cooling (fans), I just want to know how long people have run at say 1200 without any issues.
Sent using TCP/IP
Longest time: two weeks ... whitout problems ...
I'm been overclocking my SGS for over 6 months now, no issues at all.
"Standard" voltage values seems to work fine on my device (1350mV at 1200MHz, 1400mV at 1300MHz) but I've tried to undervolt a bit more than once and had no issues as well.
Bye
There are absolutely no dangers in OC/UV. The worst thing to happen is a freeze or reboot once in a while if u go too high. I've been having 1.5mhz w/ some UV for like 2 months and nothing happened so no worries.
Been doing that for about a month now. No problem.
Knowledge is Power. Guard it well.
there are no risks if you overclock your device,but of course depends on how you do it. first of all i would not go past 1300mV which is the physical limit of our beloved hummingbird..of course you can do that,but past 1300mV you are going to shorten the life of your CPU. if you change phone every year then,there's no problem
then if you want to overclock keeping safe voltage values just get Tegrak Overclock,don't activate the "CPU MAX frequency" option,go in optimization tab instead and push up the max frequency by little steps keeping the voltage at the default value of 1275. test it a bit till you reach the most stable one. for example my CPU it's totally rocksolid 'till 1132MHz at 1275mV,no more. but there are CPUs which can archieve better results. then if you want to optimize and save battery consumption you can play a bit with UV on the other frequencies,cheers
Hey Everyone, I just wanna know if I Can OC My SGS to 1.2GHz Without any problems, Because I heared that OC SGS is not stable and It's dagerous for my Phone's Life, I that True ?
-Thanks For Replying-
Shadow Life said:
Hey Everyone, I just wanna know if I Can OC My SGS to 1.2GHz Without any problems, Because I heared that OC SGS is not stable and It's dagerous for my Phone's Life, I that True ?
-Thanks For Replying-
Click to expand...
Click to collapse
Yes you can, depending on the kernel you use, oc your phone even up to 1.5 ghz.
Flash Glitch, MNICS, Devil or Semaphore Kernel for ICS roms
Do so with care as OCing WILL degrade your processor faster.
It depends a bit on your luck. Processors aren't all the same (variance in quality during manufacturing), the 1 ghz that is the default is considered a 'safe' level and every processor will be able to do that frequency. Usually though, there's a fair amount of buffer, so most processors can go beyond 1ghz to say 1.2 without any issue.
As the frequency increases, stability decreases. This means your phone will become more prone to crashing. Some people are lucky and can go very high (1.5, 1.7?), while others might start facing instability at 1.2. Won't know until you try. It's unlikely to cause permanent damage anyway, just change back to 1.0 if it's unstable
It probably does increase wear and tear of processor somewhat, but considering people will buy a new phone within 1-2 years, there's really no problem
Oc SGS 1.2Ghz
nwsk said:
It depends a bit on your luck. Processors aren't all the same (variance in quality during manufacturing), the 1 ghz that is the default is considered a 'safe' level and every processor will be able to do that frequency. Usually though, there's a fair amount of buffer, so most processors can go beyond 1ghz to say 1.2 without any issue.
As the frequency increases, stability decreases. This means your phone will become more prone to crashing. Some people are lucky and can go very high (1.5, 1.7?), while others might start facing instability at 1.2. Won't know until you try. It's unlikely to cause permanent damage anyway, just change back to 1.0 if it's unstable
It probably does increase wear and tear of processor somewhat, but considering people will buy a new phone within 1-2 years, there's really no problem
Click to expand...
Click to collapse
I Have "[email protected]" Kernel Up to 1.3Ghz, I Don't face any problems When i OC to 1.2GHz,, Games run smooth (Real racing 2) And the phone is Very responsive,, But when i play about 2 Hours My phone's temperatur increase (Just a Little Bit) but i don't know if it may Effect my Phone's Life,,
Shadow Life said:
I Have "[email protected]" Kernel Up to 1.3Ghz, I Don't face any problems When i OC to 1.2GHz,, Games run smooth (Real racing 2) And the phone is Very responsive,, But when i play about 2 Hours My phone's temperatur increase (Just a Little Bit) but i don't know if it may Effect my Phone's Life,,
Click to expand...
Click to collapse
Being electronics' worst enemy, heat can and will kill your phone. But that's only if it reaches those temperatures. Overclocking your phone naturally will increase heat from the processor. Check your phones temperature. If you're reaching 50C or over, you're getting too hot. The general rule of thumb is this: if it's uncomfortable to the touch, your phone is too hot.
Most phones should get to 1.2 GHz without a problem. Keep in mind that LiveOC is NOT THE SAME as adding another frequency step, which was the traditional way of overclocking. Some kernels do one, some do the other, and some do both. Adding an additional frequency step to get to 1.2 GHz should be capable by most if not all phones. LiveOCing to 1.2 GHz won't be nearly as compatible, as it overclocks the bus, GPU and CPU.
upichie said:
Being electronics' worst enemy, heat can and will kill your phone. But that's only if it reaches those temperatures. Overclocking your phone naturally will increase heat from the processor. Check your phones temperature. If you're reaching 50C or over, you're getting too hot. The general rule of thumb is this: if it's uncomfortable to the touch, your phone is too hot.
Most phones should get to 1.2 GHz without a problem. Keep in mind that LiveOC is NOT THE SAME as adding another frequency step, which was the traditional way of overclocking. Some kernels do one, some do the other, and some do both. Adding an additional frequency step to get to 1.2 GHz should be capable by most if not all phones. LiveOCing to 1.2 GHz won't be nearly as compatible, as it overclocks the bus, GPU and CPU.
Click to expand...
Click to collapse
+1
I've been playing with the undervolt limit of this phone and it seems to have a large amount of play. Obviously every processor is unique so some of your S6's have a lower tolerance for undervolting. I'm using Hacker v11 with Synapse and I can get my A53 cluster @ 1.5 GHz down to 1000mV though I feel it can go lower. I have the A53 underclocked to 1.2 GHz @ 900mV for now and the A57 running 2 processors @ 1.4GHz and sitting at 825mV (just flashed v11 so Synapse reset the values and I've yet to UV the A57 much). Aside from benchmarking with various apps I notice no lag or slow downs running at the lower clocks and using only 6 cores.
My GPU is OC'd to 852MHz but I haven't UV'd it yet. Before v11 I had it at 856.25mV and still stable. HPM and various busses are going to be UV'd again and they seem to take it very well. I'll update this, hopefully later this evening, with more UV values.
I'd like to put our data together and figure out an average UV this phone can take and also see some more extreme values as well. It should be a good starting reference for anyone wanting to get longer life out of their battery along with the phone itself. While we're at it I'd lie to get some lower limits for the clocks and number of cores while still maintaining a smooth experience.
A53 (Hacker v11, starting w/ highest freq.)
1056
1012
962
918
875
843
806
781
750
725
693
675
650
631
625
A57 (Same as above)
1081
1065
1043
1012
981
943
912
875
943
818
800
775
750
731
718
693
675
662
650
643
637
631
GPU
887
831
787
743
718
675
668
Memory Bus(Lowest to highest)
575
575
581
593
593
600
650
675
725
743
768
800
831
Internal Bus(Lowest to highest)
637
637
643
675
712
737
737
743
743
750
793
800
Image Signal Processor(Lowest to highest)
650
650
700
737
806
These are what I'm using right now. I plan to take them down even more in the near future (I already have on some). Of course dropping the power doesn't count for much if the CPU is running too many cycles to finish a task so I'll be messing with the amount of cores and frequency as well.
I recently was running 7 clicks (which on Hackerkernel in Synapse I think is 6.25mv per click) on the Big cores and 6 clicks on the little ones. I also tapped each step in the gpu and busses down 3 clicks and undervolted the GPU too, at about -3 clicks as well. Seemed pretty stable.
benjmiester said:
I recently was running 7 clicks (which on Hackerkernel in Synapse I think is 6.25mv per click) on the Big cores and 6 clicks on the little ones. I also tapped each step in the gpu and busses down 3 clicks and undervolted the GPU too, at about -3 clicks as well. Seemed pretty stable.
Click to expand...
Click to collapse
The only thing I'm not sure about is the "Apollo HPM voltage margin" and it's exact function. I assume it's the max amount hardware performance monitor will allow the CPU/busses to be undervolted when it feels the demand on the CPU vs. it's clock is below a threshold. I'm sure I'm totally wrong though lol. So I'm going with 1 tick above the 25000 default (31250).
Have you ran a stress test with your setup or just put it through the daily motions to check for stability?
KCRic said:
The only thing I'm not sure about is the "Apollo HPM voltage margin" and it's exact function. I assume it's the max amount hardware performance monitor will allow the CPU/busses to be undervolted when it feels the demand on the CPU vs. it's clock is below a threshold. I'm sure I'm totally wrong though lol. So I'm going with 1 tick above the 25000 default (31250).
Have you ran a stress test with your setup or just put it through the daily motions to check for stability?
Click to expand...
Click to collapse
I think you're probably right. I don't know much about it myself but that sounds like a solid guess to me. I haven't done any major testing other than yeah just daily use and see if it reboots. I couldn't ever get any.ore than about 6 or 7 increments under on either cpu. I read that the big cores need about 25mv more than the little ones to be stable.
Oddly, I got to a point the other day where I realized that i just barely can't make it through 2 full days so I might as well max performance and just accept charging every night even though I usually have 40 to 50% left, but the stanbdy is always so bad that I end up starting the second day with only 40% or less and thus can't make the whole day. Anyway, so I switch from underclocked with less aggressive govs to max clock and more aggressive govs and I think battery life is oddly better now somehow and standby seems unchanged.
benjmiester said:
I think you're probably right. I don't know much about it myself but that sounds like a solid guess to me. I haven't done any major testing other than yeah just daily use and see if it reboots. I couldn't ever get any.ore than about 6 or 7 increments under on either cpu. I read that the big cores need about 25mv more than the little ones to be stable.
Oddly, I got to a point the other day where I realized that i just barely can't make it through 2 full days so I might as well max performance and just accept charging every night even though I usually have 40 to 50% left, but the stanbdy is always so bad that I end up starting the second day with only 40% or less and thus can't make the whole day. Anyway, so I switch from underclocked with less aggressive govs to max clock and more aggressive govs and I think battery life is oddly better now somehow and standby seems unchanged.
Click to expand...
Click to collapse
While it seems odd there's a reason that moving to a higher clock setting can improve battery life though it seems counter intuitive. If you have a task that needs to be done, it's going to request time on the processor. The amount of cycles it takes to complete it will be longer at a lower frequency vs. a higher one. So while it's working at a higher clock rate and drawing more power per cycle its getting the job done much more quickly and overall uses less power. This is the same reason having multiple cores gives us longer battery life. Of course the OS, apps, and phones capabilities have also became more demanding so we don't notice it as much anymore. The trick is finding the lowest frequency we can operate at without diminishing noticeable performance and not increasing the clock cycles needed for tasks by very much. Underclocking can help with this as well if dropping the clock rate by a significant margin isn't feasible.
KCRic said:
While it seems odd there's a reason that moving to a higher clock setting can improve battery life though it seems counter intuitive. If you have a task that needs to be done, it's going to request time on the processor. The amount of cycles it takes to complete it will be longer at a lower frequency vs. a higher one. So while it's working at a higher clock rate and drawing more power per cycle its getting the job done much more quickly and overall uses less power. This is the same reason having multiple cores gives us longer battery life. Of course the OS, apps, and phones capabilities have also became more demanding so we don't notice it as much anymore. The trick is finding the lowest frequency we can operate at without diminishing noticeable performance and not increasing the clock cycles needed for tasks by very much. Underclocking can help with this as well if dropping the clock rate by a significant margin isn't feasible.
Click to expand...
Click to collapse
It is very interesting. I'm now backing off max clock, one increment at a time on both core sets to see where they meet. So far just down to 1500 little and 2000 on the big. Seems to be pretty good.
Hey, kinda late to the party but I recently got an s6 and starting to mess around with undervolting... Problem is I don't know where to start. Where do I get synapse? I'm not familiar with synapse but I did use kernel adiutor in the past.
I'm using this ROM:
https://forum.xda-developers.com/galaxy-s6/development/rom-galaxy-s6-stock-debloated-t3812822
Along with this kernel:
https://forum.xda-developers.com/tm...oc-uc-twsited-kernel-7-0-t-w8-f-flat-t3652139
Any help is appreciated. ?
When i play games like moderncombat5 i have 60fps but after a while the frames drop in some scenes where it didnt 3-5 minutes ago. When i check the cpu/gpu i can see that it throttles and causes these framedrops. But the phone doesnt get hot. Since it isnt possible to mess with thermal values at the moment. I wonder if there are some optimal cpu/gpu clocks where it will not throttle and performance will stay the same all time regardless of how much you stress the cpu/gpu. Because i'd rather have a underclocked cpu gpu than having thermal throttling while stressing the phone. On oneplus3 i didnt have this much thermal throttling playing mc5. I also feel the thermal throttling throttles way to early.
And yes i tried almost all kernels/roms out there it was a better experience on the op3
Thanks!
All CPUs have slight variations, some may be slightly more efficient than others of the same model. To get the best performance, you're going to have to underclock and test on your own phone bit by bit.
Anova's Origin said:
All CPUs have slight variations, some may be slightly more efficient than others of the same model. To get the best performance, you're going to have to underclock and test on your own phone bit by bit.
Click to expand...
Click to collapse
I know i have pvs lvl 1 across the board thats why i wonder why i didnt have this issue on the oneplus3
nadejo said:
I know i have pvs lvl 1 across the board thats why i wonder why i didnt have this issue on the oneplus3
Click to expand...
Click to collapse
What file did you open up to view that i looked a few months ago in the typical spots but found nothing.
954wrecker said:
What file did you open up to view that i looked a few months ago in the typical spots but found nothing.
Click to expand...
Click to collapse
I dont remember. But it was hard to find. Anyways i found out that the cpu allways throttles down to little 1209 mhz and big 1440 mhz. When gpu is running on max clock. Will make further investigations now to find perfect cpu & gpu freq.
It seems regardless of what cpu profile / governor you use and regardless if the phone is charging or not. The cpu will allways throttle down to 1209 little and 1440 big. And the gpu also throttles but i can't monitor the exact values currently. This throttling even happens when gpu is running on min freq. And even when you set big or little cluster to min freq.
Im pretty sure the thermal throttling of the oneplus3 is broken. Because:
Thermal throttling should be decided by many factors. (General soc heat generated by gpu/cpu/and ram) also the system should be aware by the values and should handle it intelligently.)
It seems there is only one heatsensor used to throttle all at once and the throttling stops at 1209mhz little and 1440mhz big. If the temperature still rises the phone simply doesnt give a f*** why i think there isnt even a point of using this stock throttling method. And no its not accurate. And no its not usefull because, it throttles regardless what heat the phone has. Because it doesnt react to soc heat. It reacts to one of the components and throttles everything. Why it can't check the other temparatures aswell and throttle other components diffrently if even needed at all.
Issue: lets say little or big cluster is overheating because the cpu load is very high on it. (And no you wont see this throttling by simply running perf gov. It needs load/ working tasks on it, means you gotta play some heavy 3d games)
The thermal throttling just brakes down both clusters including the gpu. Was the big cluster or the gpu running cool? The thermal throttling doesn't give a f***. Could the loads/tasks been shared with or pushed to the big cluster. Thermal values dont care. Could some rly simple sort of hotplug turn the overhating little cluster off to let the big cluster do the rest before it rather throttles everything on the f... phone . -nope - Its annoying. Rly just try it out yourself. I really hope to see some improvements by oneplus. And no the phone is not bad at all. It's just some things are not optimized yet. Like touch latency which is worse than on galaxy s3 but i don't mind it just giving you an example so you can imagine how bad the thermal throttling must be.
Allways remember setting the cpu clock values so low that they dont throttle anymore doesnt mean gpu will throttle less often. All compenents will throttle without comparing other compents clock rate and heat.
My question: is the thermal throttling decided by the soc itself or are there different thermal throttling values on each phone brand using sd821?
And is it possible to port these values from lets say pixel phone?
I'm on cm13 and its kernel default is a bit lower than stock. I had the screen on full brightness and was charging the battery so temps above 100°. I played dead trigger 2 on highest settings on a level with lots of special effects and weapons with lots of splatter. Got throttled when the temp hit 103° everytime. I was running performance on cpu and gpu and i tested it without charging and still get throttled.
954wrecker said:
I'm on cm13 and its kernel default is a bit lower than stock. I had the screen on full brightness and was charging the battery so temps above 100°. I played dead trigger 2 on highest settings on a level with lots of special effects and weapons with lots of splatter. Got throttled when the temp hit 103° everytime. I was running performance on cpu and gpu and i tested it without charging and still get throttled.
Click to expand...
Click to collapse
Im using laos 14.1 with latest ex kernel.
As is said thermal values are broken. Its not right to throttle down to same speed if charger is plugged as battery heat is higher and soc heat should be higher too. So i think it also throttles unnecesserily low without the charger being plugged.
Did any one find a solution to fix this?
Up up up
years of tired because of this ****ting throttling issue
Well do this at your own risk, go to system/vendor/bin and cut the file named "thermal-engine" to other directories in your sd card. This will completely disable thermal throttling. Perfect for gaming.?
Up up!!! This issues persists to me.. i even put my oneplus 3t in front of 8" fan for every gaming. Is there anyway to maintain the cpu frequency at higher rate during thermal throttling? I don't want to totally disable the thermal throttling... Seems unsafe... Enlighten me if you would
I think its time for gamer's to switch to a gaming oriented phone to avoid this thermal throttling and im looking forward to buy Black Shark which is Xiaomi backed gaming phone with custom rom (not miui) something different and that too is gaming focused hopefully it will be available globally soon ! :fingers-crossed:
J's said:
Up up!!! This issues persists to me.. i even put my oneplus 3t in front of 8" fan for every gaming. Is there anyway to maintain the cpu frequency at higher rate during thermal throttling? I don't want to totally disable the thermal throttling... Seems unsafe... Enlighten me if you would
Click to expand...
Click to collapse
There is no risk if you disable thermal throttling, the CPU will shut itself down if its temperature reaches 100°C
przemcio510 said:
There is no risk if you disable thermal throttling, the CPU will shut itself down if its temperature reaches 100°C
Click to expand...
Click to collapse
If i tilt my phone to the left for gaming, i will be burning my left thumb then.... even around cpu temp of 55.... My OnePlus 3T is gold in colour.. will it be better for heat dissipation if i change to midnight black?
LN2 + Copper pot. Should help.
J's said:
If i tilt my phone to the left for gaming, i will be burning my left thumb then.... even around cpu temp of 55.... My OnePlus 3T is gold in colour.. will it be better for heat dissipation if i change to midnight black?
Click to expand...
Click to collapse
No, the color will have no impact, but it will be even worse when exposed to sun
przemcio510 said:
No, the color will have no impact, but it will be even worse when exposed to sun
Click to expand...
Click to collapse
Thank you... Because the country i living is hot and humid throughout the year so i have to be extra careful ..
Any solution?
blaze95rs said:
Any solution?
Click to expand...
Click to collapse
There's nothing you can do about the throtting, OP3T throttles @60°C tbh in just 10 mins of game play it starts throtting
You have 2 options here
1. Either disable thermal engine as suggested by someone above ( it basically boils your device forget about gaming, temps touchs to 98°C if msm thermal is disabled and around 60 to 75°c it msm thermal is enabled it's seriously hot to touch and high chances of damaging internals
2. Underclock the big cluster to 1209MHz or 1286MHz I tested both, while gaming (2 hrs of pubg @ medium settings) temp's are around 53 to 55°c and never reached 60°c no throtting ( but you know what, games still lag or you will get low fps due to lack of power Lol I'm sorry that's true there nothing you can do about it try playing games in air conditioned room or just buy gaming Phone like Razer they have good heat dissipation, you should not forget the fact that our device is 2 years old. Tbh on a 2 year old phones even optimized games too use lot of processing power which lead more heat. More heat = throttle