Related
Hey all,
I come from an extensive background in OC'ing my own systems, pushing them to the extreme for noticeable performance increases. The one thing I know though, is that it does add wear and tear on the components, and shortens their lifespan. Is overclocking the Vibrant really worth it? I'm not sure if, with a ROM like Axura 2.2.5.7 which is blazing fast already, an extra 100 or 200 mHz is really worth the risk/performance.
What do you all say?
howetechnical said:
Hey all,
I come from an extensive background in OC'ing my own systems, pushing them to the extreme for noticeable performance increases. The one thing I know though, is that it does add wear and tear on the components, and shortens their lifespan. Is overclocking the Vibrant really worth it? I'm not sure if, with a ROM like Axura 2.2.5.7 which is blazing fast already, an extra 100 or 200 mHz is really worth the risk/performance.
What do you all say?
Click to expand...
Click to collapse
the only reason i OC is basically just so i can tell myself that i am OCing. If that makes ANY sense. its basically just my phone OCD.
to answer your question, even though you kind of already answered it yourself: the only reason you would actually NEED to OC is if you game a lot on your phone, if you do a lot of multitasking, or if you have a lot of data transfering going on (which i do). other than that, our processor is pretty powerful, and can handle 95% of what is thrown at it.
With that said, since youve indicated that you are satisifed with your phones performance, i would say the only thing you should definately do is install a lagfix (if you havnt already). if you dont need to OC, do your battery/hardware a favor, and dont.....unless you have phone OCD like myself.
PS - not to ramble on, but there was actually a 2-day period where i actually wasnt OCed and i didnt know it (i guess my app reset itself or something). i remember saying to myself during that time that my phone phone seemed a little laggy and much slower than usual....then once i discovered that my OC wasnt applied, it made sense. but keep in mind, i have my phone doing a lotttttt of things constantly, so OCing may not have the effect on lighter users that it does on myself. pretty crazy what a .2 ghz difference makes
Like above stated, OC is only needed if you do some intensive task on your phone. In addition, most of the Overclocking Kernels are targeted at a broad audience, what I meant by that is the developer bumps up the voltage enough so that only a small amount of people experience crashes. However, user generally have no control over the voltage themselves and any increase in voltage is bad for electronic components. (exception being some of Eugene's kernels which allows UV by user).
I don't, its not needed. I like my battery life.
Sent from my SGH-T959 using XDA App
I dont usually oc unless I am near a power source. last night i tried the Dow kernals and wow my phone was dead within ours even while in standby. Imo thats just nuts. Even while Oc'd it shouldnt die that way.
What I am looking for is a kernal thats compatible with nero v3 that will maintain battery life aslong as I dont oc.
I have seen this post http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=28&page=1 on Eugenes forum but non of the info makes sense. The one that does make sense has a older modem than the one I am using.
I guess I am use to the hd2 in which I would underclock to maintain decent battery life and use profiles. It doesnt seem like this cpu likes the profiles. amirite?
I would OC no question if we could get a UV kernel with good battery life like we did with Eclair. I won't do it with Froyo because of the terrible battery on i9000 kernels.
Sent from my SGH-T959 using XDA App
What TopShelf10 said is correct. Basically the trade off is this.... faster kernel.......quicker battery drain. That is the trade off. I have used oc kernels ...I do not use the phone for games, so EVERY thing I do on the phone the oc is not necessary. That statement is true for 95% of us.
BUT, that said, there is some cool macho feeling you get when your phone is in overdrive, just like my car, 350 hp but I live on an island that only allows 25mph speed limit...still, it doesn't change that feeling of awesomeness I get when I start the engine
I had nothing but issues with each and every OC ROM I tried. App alarm, pandora, slacker, ect. It was always something. My phone would actually get random freezes so it made the phone feel slower. Voodoo or OCLF on the other hand work wonders.
is it worth it?
well, here were the trades i had with dow14:
going from 13-14mflops to 18-19mflops in linpack (yeah, it's a benchmark, but it's hard to otherwise convey how the oc directly translated to the phone being extremely fast otherwise).
battery life went from easily going 22+ hours between charges to going 6-8 hours between charges.
however, with the core 1.2 oc i had great battery life and performance. so i assume (and have gathered from reading people more knowledgeable than me) the battery downside is due to it being a i9000 kernel. so hopefully/eventually we will get source for the vibrant 2.2 kernel and get an oc kernel with similar performance but much better battery life.
and until i flashed nero v3 and using voodoo, i kept super io and dow14 kernels on my phone so i could flash the oc if i wanted the performance or flash super io for battery life/day to day.
hello so i am new to rooting androids. i am trying to get the maximum battery life out of my phone. i was told that the combo of Adynalyne's Kernel verson a and Liquid Thundersense v1.45 rom make for good battery life. the thing is that i found this http://forum.xda-developers.com/showthread.php?t=1024338 but it says under features that it is overclocked. were can i get a version of Adynalyne 2.0 that is undervolted and not overclocked. also when i also frond Liquid Thundersense v1.45 at but the link says rom&kernal.
and side not i think that the 10 post requirement to even post a replay on the "development-related forums" is just silly. im not starting a new thread i just want to post a reply.
IMO Das Bamf remix 1.6.3 with control freak 2.0 kernel does wonders for my phone's battery. I usually get 12-18hrs on my battery with BT on most of the time, occasional gps, moderate messaging, a couple of [email protected], a emails from 2 gmail accounts, 20-60 minutes of phone calls, also 4G with stock 1400 battery. Screen 20% with timeout 30 seconds. I run set cpu on smartass
Samsung Fascinate CDMA
Rooted MIUI 1.9.16
Did a brief search here looking to understand how to operate overclocking kernals, but find it/me relatively limited.
I have installed and ran Glitch v11 and v12, played around with HL to LL, and made adjustments to undervoltage utilizing Pimp My CPU and Voltage Control. I have also ran Tweak (though not really a kernal).
My question is this,
am I overclocking when I reduce voltage on Mhz's above 1,000?
If not, could someone point me to, or explain how to achieve overclocking on our phones, and
which kernel and governor do you prefer for overclocking?
As an ammended note, I've installed Tegrak Overclock, but am still looking for a user guide...
Thank you for your time.
If you're the running the glitch kernel...use voltage control, not tegrak overclock...over clocking is when you turn the CPU speed above its normal speed..anything over 1GHz.
under volting is when you turn down the voltage frequency to achieve better battery life...
Any one clock speed may perform more or less stable with different under volting unfortunately all of our phones will vary in performance so one setting that works for one may not be the best for another so experimentation is really the best option...this applies for schedulers and governors as well.
I personally overclock as high as I can until it freezes or crashes..then I go 1 setting down...I then try undervolting different steps observing the stability of my phone...when I find what I like,I run it for a few days, then if its still nice and stable I will apply on boot.
The different leakage values are affected by the hardware quality of the chips in our phones which also vary..I start with high and see how high I can overclock..note the setting, then try medium..see how high I can overclock and so on...just as a reference..high leakage creates the most heat and is the least efficient, but works for most phones, while low leakage is the most efficient and generates the least heat and will work with not as many phones
Sent from my SCH-I500 using XDA App
efan450 said:
If you're the running the glitch kernel...use voltage control, not tegrak overclock...over clocking is when you turn the CPU speed above its normal speed..anything over 1GHz.
under volting is when you turn down the voltage frequency to achieve better battery life...
Any one clock speed may perform more or less stable with different under volting unfortunately all of our phones will vary in performance so one setting that works for one may not be the best for another so experimentation is really the best option...this applies for schedulers and governors as well.
I personally overclock as high as I can until it freezes or crashes..then I go 1 setting down...I then try undervolting different steps observing the stability of my phone...when I find what I like,I run it for a few days, then if its still nice and stable I will apply on boot.
The different leakage values are affected by the hardware quality of the chips in our phones which also vary..I start with high and see how high I can overclock..note the setting, then try medium..see how high I can overclock and so on...just as a reference..high leakage creates the most heat and is the least efficient, but works for most phones, while low leakage is the most efficient and generates the least heat and will work with not as many phones
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Efan450,
Thanks.
How do you over-clock using Glitch and Voltage Control? I see that Voltage Control goes up to 1,300Mhz, but it's at 0 above 1,000Mhz and can be dropped down to -200mV. Is overclocking just the process of decreasing that voltage on Mhz's above 1,000Mhz's
FJRSport said:
Efan450,
Thanks.
How do you over-clock using Glitch and Voltage Control? I see that Voltage Control goes up to 1,300Mhz, but it's at 0 above 1,000Mhz and can be dropped down to -200mV. Is overclocking just the process of decreasing that voltage on Mhz's above 1,000Mhz's
Click to expand...
Click to collapse
come on man.. Clock speed (mhz) and undervolting are 2 completely different things.. Forget the voltage.. No changing the voltage is NOT overclocking.. You overclock by changing your maximum clock above 1000mhz which is stock for this phone.. Try long pressing 1200mhz and selecting set as max.. Now your overclocked to 1200mhz..
Sent from the fascinate that holds the record benchmark on antutu
No decreasing the voltage is simply undervolting whether it's over 1000 or under. The idea behind undervolting is increasing battery life, but you can't necessarily go and set each level to the maximum undervolt (200) you half to see what works. Increasing the processor speed is overclocking, stock speed is 1000 so anything over that is over clocked. As far as how far as how far you can over clock depends mostly on 2 things, 1. the kernel your using, ( for example if it shows 1300 in the list that means thats all that specific kernel supports) 2. It varys greatly between phones. For example with glitch you can overclock to 1700 but very few phones can run that high for longer than a few minutes!
Hope that helps.
Sent from my SCH-I500 using xda premium
Yes.. And the fact you say your running glitch and your max oc is only 1300 my guess is you broke your kernel with tegrak overclocks module.. Delete tegrak and stop downloading overclock apps. or any other root app unless you know fully the consequences first.. If after deleting tegrak, and rebooting, if your voltage control don't show a maximum clock of 1700 mhz, then you will need to reflash your glitch kernel
Sent from the fascinate that holds the record benchmark on antutu
Neh4pres,
Yeah, I kind of feel like a heel. For some reason, I had a brain fart when looking in the 'General' section of Voltage Control. I see now how to overclock.
Regarding ost #6:
When I flashed MIUI 1.9.16, I did not install any kernel; so it was kind of a half truth in that while running 1.9.9 I did have Glitch installd. Nevertheless, I still have Voltage Control installed.
mkropf,
I see that now, and thought as such earlier, but needed some clarification.
Having so many issues with Glitch and 1.9.9, I'm hesitant to install Glitch, but interested to see if it runs better on the newer MIUI...
Thank you two for answering my newbie questions.
FJRSport said:
Neh4pres,
Yeah, I kind of feel like a heel. For some reason, I had a brain fart when looking in the 'General' section of Voltage Control. I see now how to overclock.
Regarding ost #6:
When I flashed MIUI 1.9.16, I did not install any kernel; so it was kind of a half truth in that while running 1.9.9 I did have Glitch installd. Nevertheless, I still have Voltage Control installed.
mkropf,
I see that now, and thought as such earlier, but needed some clarification.
Having so many issues with Glitch and 1.9.9, I'm hesitant to install Glitch, but interested to see if it runs better on the newer MIUI...
Thank you two for answering my newbie questions.
Click to expand...
Click to collapse
There are no issues with glitch.. It is what I run.. Very smooth.. Just have to give your phone time to adjust and build cache
Sent from the fascinate that holds the record benchmark on antutu
Landscape
Re-installed Glitch v12 ML last night and have it overclocked @ 1,200 with no under-voltage...yet. Want to see any adverse effects.
I started at 1,300 and it locked up then rebooted within 5 minutes.
A concern I have is that now my phone will not Auto Rotate to Landscape even though I have Auto-Rotate 'on' in Settings.
I've scoured Sixstrings Glitch thread to no avail. Though it's not needed anymore, I also flashed the cleaning script just to see if it would make a difference.
Is there a work around or fix for this?
Make sure you're on the latest 9/15 version of the kernel. Anything before that will kill all of your phone's sensors.
http://forum.xda-developers.com/showthread.php?t=1252871
sageDieu said:
Make sure you're on the latest 9/15 version of the kernel. Anything before that will kill all of your phone's sensors.
http://forum.xda-developers.com/showthread.php?t=1252871
Click to expand...
Click to collapse
That was it. I had re-installed the older Glitch v12 that was already on my PC. Deleted them and downloaded the newer Glitch kernels to experiment with.
Thanks!
FJRSport said:
Re-installed Glitch v12 ML last night and have it overclocked @ 1,200 with no under-voltage...yet. Want to see any adverse effects.
I started at 1,300 and it locked up then rebooted within 5 minutes.
A concern I have is that now my phone will not Auto Rotate to Landscape even though I have Auto-Rotate 'on' in Settings.
I've scoured Sixstrings Glitch thread to no avail. Though it's not needed anymore, I also flashed the cleaning script just to see if it would make a difference.
Is there a work around or fix for this?
Click to expand...
Click to collapse
under volting helps stability.. I use -50 for everything above 1ghz.. Your phone may vary
Sent from the fascinate that holds the record benchmark on antutu
OC & UV settings
neh4pres said:
under volting helps stability.. I use -50 for everything above 1ghz.. Your phone may vary
Sent from the fascinate that holds the record benchmark on antutu
Click to expand...
Click to collapse
Yeah, locking and rebooting was while using the older version of Glitch v12. With the 9/15 dated Glitch I'm at 1300 now with the following settings:
Deadline / ondemand
200 - 1300
1300 -25
1200 -25
1000 -50
800 -50
400 -75
200 -75
1.2GHz is the best I say if you want good battery with a higher frequency. 1.4GHz is the best for anyone who uses their phone alot. Samsung did add 1.2GHz overclock in their source.
Sent from my SCH-I500 using XDA App
Back to running MIUI without Glitch.
Things that make you go, Hmmm?
For some reason, every time I accessed the keyboard for Google+, it hung, then froze, and 3 of the four times rebooted. The fourth time I needed to remove the battery to reboot. So I re-flashed MIUI 1.9.16 (effectively removing Glitch) and have 0 problems.
Bummer, I like Glitch too.
I'm in the same boat, however they redone the latest glitch merge and posted it last night so I'm thinking we'll be back in good times
Sent from the most custom, custom rom Miui 1.9.16 and currently the best kernel Jt
mkropf said:
I'm in the same boat, however they redone the latest glitch merge and posted it last night so I'm thinking we'll be back in good times
Sent from the most custom, custom rom Miui 1.9.16 and currently the best kernel Jt
Click to expand...
Click to collapse
are you using JT's 9/12 kernel?
if so...did you overclock it?
i'm on jt's 9/12 with miui 1.9.16 and wondering if I can / should overclock and undervolt it. I'm just trying to maximize battery life at this point.
Try the new glitch posted last night, it is fantastic.
Sent from my MIUI SCH-i500
sageDieu said:
Try the new glitch posted last night, it is fantastic.
Sent from my MIUI SCH-i500
Click to expand...
Click to collapse
what voltages are you running?
also for anyone..
is there any way to directly compare two kernels? like a test or something?
I can't decide between JT's 9/12 and the new glitch..
worshipNtribute said:
what voltages are you running?
also for anyone..
is there any way to directly compare two kernels? like a test or something?
I can't decide between JT's 9/12 and the new glitch..
Click to expand...
Click to collapse
You wouldn't want to use my voltages, I put everything way lower than anybody else does or recommends and am just lucky that it is stable for me but it causes the sleep of death for anyone else.
For comparison, just run JT's kernel for a bit and then flash glitch and try it... once you play with OC/UV and voodoo color you won't be able to go back. (you'll be able to but you'd have to be insane.)
I finally quit over-thinking the sucky battery drain on the new Miui. Originally, I thought using the Bali Kernel would solve this (it did in the older versions) but on the new version 9.23 Miui, the Bali 2.21 would not flash.
Well, went back to my old way of thinking and doing, and just changed the voltage settings on the current kernel
The result was dramatic, went from 10 hours (100% to 5%) on my phone to 15 hrs (100% to 35%) This makes it good enough for me to work all day use my phone ( Phone, camera, text, video, etc) without having to do an interim recharge.
For those who need more on how to, here is a link along with the app you can use:
http://forum.xda-developers.com/showthread.php?t=829731
There is another link inside this posting that explains voltage settings you should read it will help you get the gist of UV settings
I set to 1.2 = -75mv, 1.0 = -50mv 800 = -50mv and 400 =-25mv
This worked well for me but you need to check to make sure it is stable.
Go to the Apps store and D/L "stability test" app. Very useful.
If you want a different app for voltage settings take a look at setVsel app it will also work well.
Either way, an easy fix with a very acceptable outcome.
Hope this helps some of you...
you may want to do some stability testing, because if you're not on Glitch ML or LL, -75uv on 1.2 tends to be unstable, at least in my experience. You have more leeway on the low end than the high. For instance, -50uv at 1ghz and above is typical for most users, but for 800 and below you can easily go to -100uv, or even -150uv or -200uv for 200mhz and 100mhz.
kaintfm said:
you may want to do some stability testing, because if you're not on Glitch ML or LL, -75uv on 1.2 tends to be unstable, at least in my experience. You have more leeway on the low end than the high. For instance, -50uv at 1ghz and above is typical for most users, but for 800 and below you can easily go to -100uv, or even -150uv or -200uv for 200mhz and 100mhz.
Click to expand...
Click to collapse
Not Raining at all Like I said I used what worked for me, phones are all different and in my case my phone is a business tool so my approach has to more conservative and this works perfectly as configured for this phone.
I agree it does not resolve some of the bigger issues that Stockish Kernels possess, but under-volting did resolve the extreme battery drain I was experiencing.
I would prefer using Bali kernel by DrHonk but the new 9.23 Miui build had a few things added to it which will require a change of code and a re-syncing of the revised Bali kernel. DrHonk is aware and is working on this already. Until then, this fix will suffice until there is a update kernel release
BTW, thank you for the lower setting recommendations, I ll play around with that on the weekend.
Just updated the settings in my signature after a bit more testing with the Glitch Medium Leak (ML) Kernel. Was a little surprised that the settings were stable, but after 12hrs, they are rock solid, and battery life is noticeably better.
Did the same thing for my Samsung Fascinate (wifi only, as a poor-man's iPad) and while I couldn't get the settings above 1000mhz stable, the 1000mhz and under settings I used on my Vibrant were stable on the Fascinate as well.
Did you keep the other UV settings for example like 1.3 = -0mv or did you disable them (in SetCPU this is done by unchecking them)?
Just curious is most people who root/use custom ROMs overclock, and if so, what settings do you typically use in SetCPU?
I'm using a S2, rooted with latest Unnamed ROM and find myself contemplating if I should make any changes with SetCPU. Lots of options, and Unnamed has all the different governor options, etc. just really looking for some best practices that people who overclock often.
Would appreciate seeing what you consider to be stable overclock options that give a good boost without causing excessive heat/stability issues.
I'm coming at SetCPU with limited experience so I do appreciate any tips that might see rudimentary, or if there are better resources that teach about this I'd appreciate any links as would like to get a better technical understanding of all this. Thanks in advance.
I use No Frills CPU, and I just set it to 1.6 max/ondemand. Absolutely no heat issues or stability issues, so I just stuck with it. Battery life is good.
most maybe but only by a little bit. a good number of people underclock and undervolt their devices to try and get better battery life. to be honest, the newer phones dont need overclocking to handle the current apps and stuff. the older phones like the nexus one and older need overclocking tho. i leave my gs2 stock. what we really need is dual core support before OC becomes worth it on my phone. ymmv
I have never overclocked mine, phone runs smooth as butter at 1.2 so I don't see the need to go farther. Plus I like my battery lasting more than 24 hours...
I overclock my s2. im running unamed 1.3.0. I like run different speeds at different at different battery percents. 1.6 till 75% 1.4 till 50% 1.2 till 25% 1000 till 15% 800mhz till dead. i had some problems with 1.4 ghz but i tweeked the voltage and that did solved my problem. I'm at 50% battery with normal usage. display 1hr 25mn phone calls for 47min and android os for 56min. my phone doesn't get any hotter then it did before i overclocked. I just did it to say i did. It will prolly help a little unless you like emulators then it will help alot. i have to overclock my iconia a500 to 1.6 if i want to play n64 games.
I'm on UnNamed 1.3.1 with the latest entropy dd kernel and am very happy with the stock CPU speed
Sent from my Samsung GT-I9100