I've read many threads where people say they have their G2 up around 1.5 and I'm just wondering what is considered a safe OC speed?
Some of the threads say there isn't much noticeable difference after 1.2, can any of you confirm this?
I'm on meXdroid right now and I've been keeping it at 1.2 but it gives me the option of going up to 1.516, so I'm wondering if there's any damage that might be done if I go with the max.
kingston73 said:
I've read many threads where people say they have their G2 up around 1.5 and I'm just wondering what is considered a safe OC speed?
Some of the threads say there isn't much noticeable difference after 1.2, can any of you confirm this?
I'm on meXdroid right now and I've been keeping it at 1.2 but it gives me the option of going up to 1.516, so I'm wondering if there's any damage that might be done if I go with the max.
Click to expand...
Click to collapse
I'm running CM7.1 at a max of 1.4 without any problems. Not sure there is such a thing as completely "safe" when overclocking, but I also read about many who are at 1.5 or higher. I did notice a slight improvement going from 1.2 to 1.4 on my phone, but nothing substantial.
its safe to oc at 1.5 the thing is you wont be gaining a lot of performance but you will be draining more juice
After 1.2 the only thing you get is more battery consuccion.
The safe way is keeping the cpu ondemand or conservative between 245 - 1200.
If you want safe battery you can use setcpu and make 2 profiles one in screen off (powersave 245-368) screen on (ondemand 245-1200).
Note: for miui screen off profile have to be (245-768) because (245-368) cause delay in incoming calls.
And remember always the scale depends what kernel you use.
I using now pershoot 2.6.35.14
Is good with battery life so i recommended to you.
I was using ILWT kernel v1.5.1, is more better on battery life but i notice some problems went i use maps.
I hope that help you
Sent from my HTC Vision using xda premium
Ive also looked into this quite a bit and most people say around 1200mhz is the sweet spot for battery and speed.
also overclocking depends on kernel
I've ran mine at 1.42 using Unity sense as a daily driver.
pedroflovera said:
After 1.2 the only thing you get is more battery consuccion.
The safe way is keeping the cpu ondemand or conservative between 245 - 1200.
If you want safe battery you can use setcpu and make 2 profiles one in screen off (powersave 245-368) screen on (ondemand 245-1200).
Note: for miui screen off profile have to be (245-768) because (245-368) cause delay in incoming calls.
And remember always the scale depends what kernel you use.
I using now pershoot 2.6.35.14
Is good with battery life so i recommended to you.
I was using ILWT kernel v1.5.1, is more better on battery life but i notice some problems went i use maps.
I hope that help you
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
The OP is using meXdroidmod which has "tweaKr" script so no need for set CPU and he also has option to adjust voltages and many other tweaks. MeXdroidmod is awesome!
To the OP, just keep it at 1.2 . Like others have mentioned...just wasting juice if any higher.
HTC Vision(G2), meXdroidmod Ghost Chili AIO ROM/ICS CM7 theme.
I have mine at 1.6Ghz set on performance screen on, 368-768 ondemand screen off. I'm a medium/light user and will have around 20-30% left when i plug it in at night.
The amount you can overclock while still maintaining decent battery life really depends on if you're a light/medium/heavy user - because the charge is only being rapidly drained while the screen is on (if you have a sensible screen off profile set up). Light users can afford to run at high speeds on performance govenors, heavy users should run at lower speeds with conservative governors.
As for how safe overclocking is i'm not completely sure what the limits are, but there are people who run their G2's at 2Ghz and get no problems... the biggest danger is probably heat damage to the phone, but the battery will fail before you get to temperatures that will damage the phone so i wouldn't worry about that. The other concern is reducing the life of the cpu, however the longest you will have a phone is around 2 years, and an overclocked cpu will still last far longer than this.
Hope I helped answer your question, I am running Miui btw.
I have a 2.7ghz kernel on cyanogen 7.1 and I call it the Turbo charged g2
Sent from my HTC Vision using XDA App
The maximum speed our G2 can go is 2.03 but if you want battery and spped i recommend setting it up in between 0.9 and 1.3
Hope it helps!
the 7x30 processors are designed to run up to 1.5 so basically it's not oc. and the Desire z/G2 come with underclocked kernels on stock
Currenty oc my dz to 1.5ghz. Can oc to 1.9ghz without any problem.
Sent from my HTC Vision using XDA App
lolocabra said:
the 7x30 processors are designed to run up to 1.5 so basically it's not oc. and the Desire z/G2 come with underclocked kernels on stock
Click to expand...
Click to collapse
seriously?! it can run 1.5ghz without burning the cpu??
Steven How said:
seriously?! it can run 1.5ghz without burning the cpu??
Click to expand...
Click to collapse
Yup, a lot of people are running 1.2 or 1.5 daily.
Sent from my T-Mobile G2 using XDA App
i always thought they took Desire's 1GHz cpu and put it underclocked in the dz... so i oc it to 1GHz...
—————
|RIROZIZO|
—————
Steven How said:
seriously?! it can run 1.5ghz without burning the cpu??
Click to expand...
Click to collapse
That's incorrect from what I've read the CPU the g2 has is a 800 stock its not underclocked or nothing that's how it came From HTC but its a 2nd Gen snapdragon and their for very recealient and efficient and their for can be overclocked .. and from what I have seen and read this CPU has been overclocked more then any other CPU on a phone ... its bad ass!
Oh yeah .. I'm running mine at 1.4max and .122min with ondemand on g-light 2.0.1 rom and no over heating
Sent from my T-Mobile G2 using XDA App
Wow,wat if I run at 384mhz-1.2ghz and the battery become pretty hot? :/
Sent from my HTC Vision using XDA App
andslide said:
I have a 2.7ghz kernel on cyanogen 7.1 and I call it the Turbo charged g2
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Mind give me the link to download the 2.7ghz kernel XD ?
Sent from my HTC Vision using XDA App
Safely ocing to 1.4 on my daily rom.
Sent from my HTC Vision using Tapatalk Pro with Swype
Related
First off, I would like to apologize in advance in case a thread like this exist and I can't find it.. :/ (Search is down, tried Googling) also, if anyone believes this to be in the wrong forum.
ANYWAYS! This is intended to be a preference/opinions thread centering around your OC/UC and Undervolt settings. Feel free to post your current set-up in Voltage Control (or any app of the like) and what Kernel you are running! I wanted to start this to get an idea of what everyone else is setting their UV and CPU clocks to, and possibly give a few of them a try on my own device. :]
Personally all of my clock speeds are at their defaults except for 1000Mhz @ 1200mV. (-75mV). I am also rocking Genocide v1.0 and getting a decent 30hrs of battery life with pretty moderate use.
Post away!
It is kind of pointless since every phone is different so cannot do exactly the same as others. Most can't do 1.4Ghz and most don't wake from sleep at 100 Mhz. All depends what you use your phone for. Mine runs fine at 1.3Ghz except for some TV apps will freeze.
Do you BONSAI?
kennyglass123 said:
It is kind of pointless since every phone is different so cannot do exactly the same as others. Most can't do 1.4Ghz and most don't wake from sleep at 100 Mhz. All depends what you use your phone for. Mine runs fine at 1.3Ghz except for some TV apps will freeze.
Do you BONSAI?
Click to expand...
Click to collapse
I believe that would be my point however.. curious as to what other people are running as far as cpu and voltage is concerned. Their success and failures. What people can get away with and remain stable. I, and others, could then try their setup (taking precautions of course; ie Nandroid backup.) And see what we get. Who knows, maybe I might adapt a set up that runs better on my device than my current one.
Sent from my SPH-D700 using XDA Premium App
Yes, every phone is different, but that is just more of a reason to collect data - perhaps a baseline can be established, which would be helpful in determining if a particular phone is messed up or just at the low end of the scale. Right now it is hard to determine if a particular phone's troubles are caused by low quality or by damaged hardware.
I keep all voltages at stock, and don't use any OC - my phone runs fine as is, and the battery life actually seemed worse with UV (and my screen felt hot with the screen UV).
Sent from my SPH-D700 using XDA App
My phone wakes from 100 but won't do 1.4ghz for even a couple seconds before reboot but 1.3ghz lasts about 20 minutes before reboot and 1.2ghz is stable. As for undervolts it can handle -25 on 1.2ghz and -50 on 1 and 1.1ghz -50 on 800mhz and that's it otherwise becomes unstable and reboots. Battery life and performance seem to meet at 800mhz with a -50 undervolt games run smooth too and 12 hours of battery. Oddly enough benchmarks are consistantly higher on 1.12ghz than on 1.2ghz I wonder if I'm the only one?
Sent from my midnight rom 5.2 genocide 1.0 epic [email protected] using xda premium app
xopher.hunter said:
My phone wakes from 100 but won't do 1.4ghz for even a couple seconds before reboot but 1.3ghz lasts about 20 minutes before reboot and 1.2ghz is stable. As for undervolts it can handle -25 on 1.2ghz and -50 on 1 and 1.1ghz -50 on 800mhz and that's it otherwise becomes unstable and reboots. Battery life and performance seem to meet at 800mhz with a -50 undervolt games run smooth too and 12 hours of battery. Oddly enough benchmarks are consistantly higher on 1.12ghz than on 1.2ghz I wonder if I'm the only one?
Sent from my midnight rom 5.2 genocide 1.0 epic [email protected] using xda premium app
Click to expand...
Click to collapse
Just to throw it out there. Aggressive undervolts will do more harm than good to your battery life. By that, I mean you'll drain your battery even more.
Sent from my SPH-D700 using XDA Premium App
I can only use Genocide kernel to get 1.3ghz at stock voltage with since all the other choices are uv'd. My last two Epics were able to handle uv'd 1.4ghz by 50mV but I'm not really complaining as I think this is a new phone they gave me and not a refurb. I currently have 100-400 uv'd by 100mV, 600-1000 uv'd by 75mV and 1300 at stock.
My phone can handle 1.4 Ghz but only with the stock voltages. If I try to touch it even by 25mV it locks up.
Who all has enabled the 100Mhz step? I noticed when I did my phone went into Deep Sleep a lot less by a noticeable amount. Staying at 100Mhz a lot.
Always interesting to hear about all this theory behind the reasons for undervolting OC and UC, then to hear about the issues (at times extreme) some have. I would also like to know who uses the 100 step and if it is noticeably better on battery life than the 200? Unfortunately I am missing out on it if I am. Still running Genocide here, but with 1.0 at -50mv 800 @ -50 and 600 @ -25. Very stable and still at 30+ battery life. Having 1.0 down 75 made me nervous. although I hear people dropping it down -100mv successfully.
Sent from my SPH-D700 using XDA Premium App
Good tip about "aggressive UnderVolting"...didn't know that actually drains your battery more. Might explain why 6 hours into my day, my battery is down to 30% already!!! I had it set at 1120Mhz UV to 1175mV (Stock = 1300)...
So now I'm going to try 1200Mhz only UV by 50...see what my battery life is after this!
Custodian said:
Just to throw it out there. Aggressive undervolts will do more harm than good to your battery life. By that, I mean you'll drain your battery even more.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Can you explain how this is so? Is this based on any actual research, experimentation, or online documentation, or is this just your own opinion?
Unless your undervolt causes the CPU to hang (I've seen mine start to warm up when it's hung, until a battery pull), I don't understand how providing less voltage to the cpu will cause it to drain the battery faster.
If you change the voltage settings please don't blame the rom developers when you phone bricks...
Sent from Bonsai 7.1.3.1
I'm running Twilight Zone v 1.1.1 RC1-Hajime Taisho, Vision kernel v 1.2
SetCpu-1.450 max
-1.450 min
Quadrant-2377
Linpack-20.577
Voltage Control-1.450
Uv -100
Quadrant-2346
Linpack-21.495
I ran SetCpu, benchmarks, ran VC, benchmarks..... This Epic runs super fast, with no FC's or any other problems at all. I'm currently using VC with the uv-100. As far as excessive battery use, I have Mugen 3200 mah battery. This battery lasts all day in heavy use with no problem.
Sent from my SPH-D700 using XDA Premium App
How many .35 kernels are available? I'm only aware of Umaro's and the stock CM kernel. I'm trying to achieve better battery life, so what kernel are you guys using?
So far, using Umaro's, I'm getting regular battery life, nothing special. Haven't tried the stock CM kernel.
Are they any other undervolted kernels available?
durps said:
How many .35 kernels are available? I'm only aware of Umaro's and the stock CM kernel. I'm trying to achieve better battery life, so what kernel are you guys using?
So far, using Umaro's, I'm getting regular battery life, nothing special. Haven't tried the stock CM kernel.
Are they any other undervolted kernels available?
Click to expand...
Click to collapse
There aren't any others so far. Umaro's kernel is really good for battery life, however it's not up to date with the latest kanged nightly from yesterday.
Ahh, I see. Thanks for the info.
What cpu settings are you running?
durps said:
Ahh, I see. Thanks for the info.
What cpu settings are you running?
Click to expand...
Click to collapse
Right now I'm using a kanged nightly with the "stock" cpu settings of 245MHz min and 1024MHz max, but with the interactive governor. With Umaro's kernel I had at 245 min, 1017 max and the Smartass governor. The smartass is pretty good on battery.
u made all the right moves all i would do is dim screen and keep runnimg apps low.
pimped out g2
btw pyromod 2.0 345 ghz min 1405ghz max on smartass. i fully charge bout 1 a day
pimped out g2
Pershoot released his kernel the other day pretty nice and smooth
Sent from my HTC Vision using XDA App
Alright I'm sleepy so this will be in rambling form but...
I've tried Umaro's and I'm not sure if it was the undervolting (which I haven't looked into tweaking) but my phone kept stuttering no matter which governor I used. I was using Htcclay's Super CM7 1.8 with cpu set to 245/1113
I also used the stock kernel that's been on CM7 with no problems and average to good battery life (10-15 hours of active use: texting, browsing, few calls, and playing the occasional game)
Most recently I've used Pershoots which I had heard worked great. I myself love it. Almost same battery life as stock kernel but everything felt just a little bit smoother performance wise.
Here's a link to Pershoot's thread:http://forum.xda-developers.com/showthread.php?t=847672
The stock cm kernel in my opinion is finally good enough that it doesn't need changed. I have always flashed pershoots and occassionally others, but it truly does not need supplemented IMHO.
Sent from my HTC Vision using XDA Premium App
I'm using savaged zen, and I get around two days of battery on a charge, with normal use.
Min: 368 max: 768
Sent from my HTC Vision using XDA App
Using Pershoots latest kernel, have nothing but good things to say about his kernels. Always my go to kernel.
fedtemis said:
I'm using savaged zen, and I get around two days of battery on a charge, with normal use.
Min: 368 max: 768
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
You're running that on Vision? I can't seem to find it for our device.
Stock CM7 kernel here. I run 245/806 Interactive with automatic brightness. I've found that when wifi is on, keeping the cell radio @ 2G only works wonders. Wifi is set to sleep on screen off, but not when plugged in. 1 day 7 hours on this charge so far with 23% left. I would consider my use light to moderate.
HTC Vision (G2) - CM7 B95 w/AUS radio
Your is not short for you are, but you're is.|It's means it is and never ever anything else.|Pluralization by way of an apostrophe is always wrong!
durps said:
How many .35 kernels are available? I'm only aware of Umaro's and the stock CM kernel. I'm trying to achieve better battery life, so what kernel are you guys using?
So far, using Umaro's, I'm getting regular battery life, nothing special. Haven't tried the stock CM kernel.
Are they any other undervolted kernels available?
Click to expand...
Click to collapse
I'm wondering where can I download the Umaro's kernel. I check out his github (https://github.com/umaro/htc-kernel-msm7x30) only to find out that the source is available.
Will it damage my processor? I wanna use it but I don't wanna kill my phone!
Sent from my Desire HD using XDA Premium App
No, it won't kill your phone but it will drain your battery freaking fast...
Yeah, prolonged overclocking will build heat and may damage your phone. And why do you want to overclock up to 1.9GHz anyway? There's no performance boost after 1.6GHz afaik.
Edit: maximum performance I get is around 1.5 - 1.6GHz average over repeated benchmark of different software.
I got my Virtuous finally at 1.7 GHz (yeah!) and team the Quadrant Benchmark and gained about 200 points more, but I got to agree: there is no performance boost which you can see without benchmarking.
So I will put it back to 1.5, that's enough.
Edit: WTF? I've put it back to 1.5 and got 100 more points than with 1.7?!
i want to know if its safe to overclock my samsung vibrant to 1200 mhz. will doing that shorten the life of my phone in any way.
tinye99 said:
i want to know if its safe to overclock my samsung vibrant to 1200 mhz. will doing that shorten the life of my phone in any way.
Click to expand...
Click to collapse
It will definitely shorten the life of the battery. As for the phone itself I can't really say. I used to use my vibrant @ 1200mhz daily while running bionix 1.3.1. I never really noticed any wear and tear from the overclocking. If your phone runs warm while overclocking you should really consider running the stock voltages. Your phone may overheat and fry your cpu gpu with the high temperatures. So be careful when overclocking.
Meh i dont completely agree...
It will only shorter the life of your battery because the processor will draw about 20% more power which is very small compared to the like 20x more power the lcd takes up.. i dont think youll feel the difference.
The heating up i disagree with too since ive seen processors reach boiling point of water and continue to work.. thats not to say they all will but ive oced my phone to 1.6ghz to benchmark for several minutes and it never got above 41*... the battery heats up alot more when its charging than the processor does most of the time so i wouldnt worry tooo much about that.
Now as to whether the phones llife will lower... yes probably.. youre putting more stress on the processor than if you dont oc.. honestly tho, processors dont die very often so i oc all day as my daily runner, usually to 1.4ghz if my kernel will do it..
Up to you and honestly all of this is my opinion based on my available info etc.. hope this helps
sent from the xda app on my android smartphone.
I have mine Oc to 1.5 and no issues. 1.5 is the Max I would go.
Sent from my SGH-T959 using xda premium
Everything I have read says 1200 is completely safe. I run mine at 1460 with no issues. It obviously draws more battery but using Voltage control app you can adjust the level of battery.
Sent from my SGH-T959 using xda premium
You would be fine with 1.2Ghz, but look into a kernel that supports some slick CPU scalers (smartass is a good, easy choice). You can set that (1.2Ghz) as a max clock and you can let the scaler determine how it gets there (if need be). Running only 2 clocks (OC and deep sleep) seems a bit overkill to me, but to each their own.
Like everyone else said, you ought to be perfectly fine with that value.
The highest I would go is 1500 though
kaiser_bun said:
You would be fine with 1.2Ghz, but look into a kernel that supports some slick CPU scalers (smartass is a good, easy choice). You can set that (1.2Ghz) as a max clock and you can let the scaler determine how it gets there (if need be). Running only 2 clocks (OC and deep sleep) seems a bit overkill to me, but to each their own.
Click to expand...
Click to collapse
Lol, running an overclock on a phone seems a bit overkill to me...
Think about this.. How much copper is strapped up to your phones cpu?
Would you overclock your desktop on a stock cooler?
I feel sorry for the saps who buy phones second hand(especially after reading this thread). (hey wait a minute, that's me too.. Lol)
I never overclock anything.
Ever.
(learned my lesson with an amd Duron 733 back in the day)
Sent from my SGH-T959 using XDA
Hello guys. I just want to take information that there are many tweaks to overclock galaxy s3 to max 1.8 ghz. If we set to maximum overclocking then is there any risk for damage hardware? Because 2 months before i had nokia n8 & i set this device to overclock & it damaged all board,now its totally destroyed. According to my point of view,sometime i think that nokia n8 has only 680 ghz & due to overclock it run on higher clock speed & so that due to low processor it could not manage or handle the higher clock speed & it ran on heavy clock speed continuesly then overload of processor it got damaged. It is my fear for s3. And i think for s3 that it has higher processor with 1.4 ghz,if i set it to 1.8 ghz then there is no risk bcoz of there are cpu governor. With this,the s3 does not run continues on 1.8 ghz higher speed, governor takes control over the cpu to run on higher clock speed according to their high usage like 200 ghz, 500ghz, 800 ghz, 1.4ghz & so on. So i think i can overclock my galaxy s3 with kernel but I'm still confused & I'm not expert. So plz suggest me to do overclock without any damage fear. Thanx a lot.
If you don't know what you are doing, then don't do it!
Sent from my GT-I9300 using xda app-developers app
sfjuocekr said:
If you don't know what you are doing, then don't do it!
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
If i don't but you know then u can tell me about any risk.
NOTHING is without risk, but a good place to start is just to install the latest Siyah S3 Kernel and run it it at 1.6ghz for the CPU and default settings for the GPU. I tried running my CPU at 1.7 and 1.8 and the it wasn't 100% stable and the temps were to high for my liking. Be moderate in your settings and you shouln't encounter any issues.
http://www.gokhanmoral.com/ latest version is 1.7rc1
That will give you a good performance bump with the minimum of risk (in my opinion).
Other than that installing a bloatware free ROM will also give a nice bump. I personally run Omega V29 with the above 1.6 overclock settings and it lightning fast. :good:
There is always a risk involved in overclocking.
1.8ghz isn't stable for most people but 1.7 is quite stable.
How well your device handles overclocking depends on the quality of the chip you got.
This is down to the manufacturing process, you may get a good chip from the middle of the wafer or a not so good one from nearer the edge.
if you want to reduce heat them you should undervolt the CPU, less current means less heat.
Obviously it isn't good for the hardware in the long run but that's what you gotta take into account when you overclock, I've overclocked every phone I've ever had and haven't had any problems but YMMV.
Sent from my Nexus 7 using xda premium
nodstuff said:
There is always a risk involved in overclocking.
1.8ghz isn't stable for most people but 1.7 is quite stable.
How well your device handles overclocking depends on the quality of the chip you got.
This is down to the manufacturing process, you may get a good chip from the middle of the wafer or a not so good one from nearer the edge.
if you want to reduce heat them you should undervolt the CPU, less current means less heat.
Obviously it isn't good for the hardware in the long run but that's what you gotta take into account when you overclock, I've overclocked every phone I've ever had and haven't had any problems but YMMV.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
could u plz tell me that what is the process of undervolt if i undervolt the cpu then it is related to only heat or performence also?
If you use siyah kernel then in the stweaks app that comes with it you can choose how much you want to undervolt.
I suggest starting with -25mv or -50mv and check stability.
I use -100mv without problems but like in said earlier YMMV.
It doesn't give a performance boost per se, but less heat in the chip will mean that it doesn't hit the temperature throttle threshold as easily and that means more performance.
The CPU will begin to throttle (limit clock speed) at around 75c until the temp drops and the CPU is allowed to run at max clock speed again.
Usually you will only hit the temp throttle threshold under very heavy loads, for example repeated benchmarks.
Sent from my GT-I9300 using xda premium
mrjoy said:
Hello guys. I just want to take information that there are many tweaks to overclock galaxy s3 to max 1.8 ghz. If we set to maximum overclocking then is there any risk for damage hardware? Because 2 months before i had nokia n8 & i set this device to overclock & it damaged all board,now its totally destroyed. According to my point of view,sometime i think that nokia n8 has only 680 ghz & due to overclock it run on higher clock speed & so that due to low processor it could not manage or handle the higher clock speed & it ran on heavy clock speed continuesly then overload of processor it got damaged. It is my fear for s3. And i think for s3 that it has higher processor with 1.4 ghz,if i set it to 1.8 ghz then there is no risk bcoz of there are cpu governor. With this,the s3 does not run continues on 1.8 ghz higher speed, governor takes control over the cpu to run on higher clock speed according to their high usage like 200 ghz, 500ghz, 800 ghz, 1.4ghz & so on. So i think i can overclock my galaxy s3 with kernel but I'm still confused & I'm not expert. So plz suggest me to do overclock without any damage fear. Thanx a lot.
Click to expand...
Click to collapse
1.7ghz should be alright for a 32nm chip like the exynos 4412 on our s3. HTC has had their One S (with a 45 nm chip) clocked at 1.7 ghz. The lower the nanoneter, the more ambitious you can be with clock speeds. Try 1.6 or 1.7 ghz with default voltage settings and see how that goes
Sent from my GT-I9300 using Tapatalk 2
nodstuff said:
If you use siyah kernel then in the stweaks app that comes with it you can choose how much you want to undervolt.
I suggest starting with -25mv or -50mv and check stability.
I use -100mv without problems but like in said earlier YMMV.
It doesn't give a performance boost per se, but less heat in the chip will mean that it doesn't hit the temperature throttle threshold as easily and that means more performance.
The CPU will begin to throttle (limit clock speed) at around 75c until the temp drops and the CPU is allowed to run at max clock speed again.
Usually you will only hit the temp throttle threshold under very heavy loads, for example repeated benchmarks.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
You are using -100 undervolt, that mean its high current & mean if i select 25 to 50 then its less current than 100??? & is there any battery improvement if i select less current mean less heat.?
I am using -100mv, as in minus 100mv, 100mv less than stock.
Less current is less heat and *maybe* battery savings.
-100mv is less current than -50mv.
Sent from my GT-I9300 using xda premium
nodstuff said:
I am using -100mv, as in minus 100mv, 100mv less than stock.
Less current is less heat and *maybe* battery savings.
-100mv is less current than -50mv.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I am new to all this just one question, will over clocking drain the battery quicker?
andmax66 said:
I am new to all this just one question, will over clocking drain the battery quicker?
Click to expand...
Click to collapse
Yes atleast while it's using the higher clock speeds.
Sent from my GT-I9300 using xda premium
What's a good kernel for overclocking for the stock I9300 running ICS (don't have the JB yet)? Will the latest Siyah work?
DenethorLenwion said:
What's a good kernel for overclocking for the stock I9300 running ICS (don't have the JB yet)? Will the latest Siyah work?
Click to expand...
Click to collapse
siyah, its most beginner friendly wih stweaks (for ICS you should check 1.5 version if its still obtainable, however should be)
Sent from my GT-I9300 using xda app-developers app
Antutu and Quadrant, all are just bull****. Just to see their manipulated scores, overclocking does not make any sense.
At ground level, applications do not run anything faster as overclocking alone does not work here. Even if you get milli milli milli second improvement which is just nothing against damage of CPU.
Got it?? now start using your phone as it should be and made for.
Before overclocking you should ask yourself Why you want to overclock. If it's because the phone have some lags there is other(safer) way to solve this problem. Honestly I overclock mine for a while (just because I'm a tester) but the S3 is fast enough for everything. You should see my S3. The app drawer appears (almost) instantaneously. Any games play smoothly etc...
On this phone overclocking is possible but useless. If you want to learn how to overclock just to learn how, search in the stickies for the overclocking guide.
I have tried overclocking and undervolting for the last week now and I can say that overclocking has not made any visible difference to my S3. Overclocking seems to be a nice option to have, but the S3 does not need it. Undervolting on the other hand reduces lag considerably when playing games for long periods. Usually my S3 started to get laggy after about 1 hour of Asphalt, but now it does not get laggy at all. I have undervolted by (-)125.
Hope that helps.
When I play pokemon black 2 on nds4droid without overclocking it gives me 20 to 30 fps and when I overclock it to 1.7 GHz i get 28 to 35 fps
Sent from my GT-I9300 using xda premium
Firstly you need a kernel supporting overclocking... Secondly its fine if u wanna play around with your device... Lastly I would suggest u to overclock it to 1704 MHz max (avoiding any boot loops )....
I would recommend Siyah 1.9.1 (as your Kernel) and "Noop" as your I/O Scheduler... In case ure using Siyah as your Kernel, try using "Lulzactiveq" as your governer...
Furthermore u can tweak the governer if u want more juice out of it....
Try it.....
Sent from my GT-I9300 (Hassan Khalid Malik) using xda premium
---------- Post added at 10:50 PM ---------- Previous post was at 10:41 PM ----------
Mr Faeces said:
I have tried overclocking and undervolting for the last week now and I can say that overclocking has not made any visible difference to my S3. Overclocking seems to be a nice option to have, but the S3 does not need it. Undervolting on the other hand reduces lag considerably when playing games for long periods. Usually my S3 started to get laggy after about 1 hour of Asphalt, but now it does not get laggy at all. I have undervolted by (-)125.
Hope that helps.
Click to expand...
Click to collapse
Lag can be reduced by tweaking your governer and some other settings... U don't have to underclock it...
Sent from my GT-I9300 (Hassan Khalid Malik) using xda premium
I have tried overclocking to1600, and although Quadrant stats are higher, I did not notice any difference in normal usage. I am a general usage text and phone calls and email user. Minimal game playing. I stick to 1400 now and everything seems just the same!!
At the moment I am running Sotmax rom and boeffla kernel.
Hope this helps.