Related
What is it? Purpose? How do you do it? How does it optimize my phone?
Sent from my Hero using XDA App
Google is your friend. Search CPU OVERCLOCKING.
Sent from my HTC Hero using XDA App
It's something cool, you could use SetCPU or Overclock Widget, and it's like adding rocket-fuel to a campfire.
ddotpatel said:
Google is your friend. Search CPU OVERCLOCKING.
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
the time it took you to be a smart ass you could have just said what it did.
i did a search for it and yet it wasnt informative enough. hence why i came here and asked.
Google want enough? Wow! Over clocking increases the clock speed of your cpu making it calculate faster.
Sent from my Hero using XDA App
silver2kgti said:
the time it took you to be a smart ass you could have just said what it did.
i did a search for it and yet it wasn't informative enough. hence why i came here and asked.
Click to expand...
Click to collapse
Alright, then I'm sorry Google couldn't answer your question. (Which is odd, since overclocking is kinda popular.)
Anyways, Overclocking means to "Make the CPU go faster than it was designed for". Some devices "like the hero" can jump from 518mhz to a stable 691mhz by overclocking, this increases the speed of the CPU so that programs and the OS can work faster.
But overclocking is about finding the highest speed, while having the stability to use it. Since it's no use to overclock, if it makes your phone unusable to use. (Force closes, phone freezing etc.)
Overclocking CAN harm your device, if you take a too high value. But if you stay inside a stable zone, there shouldn't be any harm to your device.
You can experience that the phone is getting a bit hot, or that the battery is emptied faster than normal.
Since the CPU drains so much power, there are settings that allow to set a different clock (how fast the device should go in mhz) when the phone is at sleep. So that it can run at a much lower frequency, when you don't use it.
ROM developers normally post ( 691/197 ) or something at their thread, the first number is the CPU speed when it's on and you're using it. And the other is when the phone is at sleep.
If there's anything other you want the answer to, ask it here.
But, please use Gooogle search Before posting anything.
Overclocking increases the clock speeds of a CPU. And as a result means it can do *things* faster.
Overclocking on a desktop PC tends to increase the voltages to overclock the device over this isn't really an option on a phone as it has limited battery life. So overclocking on a phone is normally done by software changes. When CPU makers make a CPU they can not be 100% accurate on the performance of that chip - in fact its very much the opposite, so after each chip is made it is tested and then given a clock speed and locked to that, overclocking breaks that and allows you to manually increase the clock, however overclocking capabilities will be different on every device.
If you take an example of an Intel Chip, a 2.66GHz Core-2-Duo, this is exactly the same chip as the 3.06GHz however when tested it wouldn't run as fast so Intel sell it at a stable clock speed.
Overclocking the hero shouldn't really have any implications for the device, however overclocks can reduce the life-time of a CPU (and any other hardware you might overclock). You shouldn't notice much extra heat from the device as the voltages being used are not changing.
Hope that cleared some of it up for you.
silver2kgti said:
the time it took you to be a smart ass you could have just said what it did.
i did a search for it and yet it wasnt informative enough. hence why i came here and asked.
Click to expand...
Click to collapse
Did you forget to press the search button?
Some of the top results from google:
Wikipedia
What is Overclocking?
What is overclocking?
What is overclocking?
Overclocking Guide
Really was that so hard?
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.
hey all, long time reader, first time poster. i have some questions in regards to overclocking your phone. whats the point? Im not trying to find the forum trolls, nor am I knocking the practice, im genuinely curious about the end result.
im a hardcore PC junkie, so im very familiar with the process, hell my desktop is currently overclocked by a 1ghz (AMD 965 BE @ 4.2ghz).
i have the HTC Evo 3d, best phone ive ever owned, and at first the idea of overclocking it was very interesting, but as i thought about it, the more it didnt make any sence. the phone already get warm when you start pushing it, especially when gaming, i can only imagine how hot it must get when you start upping the voltage to squeeze a extra couple hundred mhz out of it. also how much of a performance increase would you notice? the phone already, runs like butter in my opinion, i cant imagine a extra 100-200mhz would be noticable at all. it just seems like alot of work and risk for a almost a not noticable end result.
if im incorrect in any of my assumption, please correct me, lol even just saying that ive overclocked myr phone is awesome, im just looking for some valid reasons in favor of OCing
no one? lol i guess its not as widely done as i thought it was lol
I don't ever OC my phones for the simple reason that they are battery powered. But I understand why most people do it. Usually it is a good thing to have all the tools at your disposal for whenever you might need it. Most kernels that support OC are usually driven by apps such as SetCPU, which have options to have the CPU constantly OC'd or on-demand basis. If the user was to run a high demand app such as the video camera with a 1080p res, there be more processing power available for the app to accomplish whatever it needs in a less intensive manner.
that makes sense i suppose. having a quick launch app that allow on demand overclocking would be pretty cool. ill have to look into this a little bit further.. thx
The reason is simple - my phone is too slow.
I am using HTC Hero which is 2+ years old. The speed is so slow (528MHz), the machine lags even running the Dolphin browser. I recently root it and install a custom rom, overclock it to 6xx MHz. I feel my Hero has revived and I think it still can be used for a couple of months more.
So I installed SetCPU today. Been testing the kernels ability to work underclocked at the max of 918mhz. Also set the scaling to conservative. After a days use it's been as good as normal full speed, 1512mhz
The battery lasted throughout the day, compared to my first two days of stock settings with only 6 hours of good use.
I'll keep playing. Still want to do some testing and benchmarks to make sure it's not under performing. But at least at the user level it seems to react the same.no lag.
I did confirm the clock speed out side of SetCPU using system panel.
Sent from my rezound.
Don't bother using benchmarks to rate a phones performance that is a fatal error there. Benchmarks never effectively rate a phones performance. I just go by how smooth the phone runs and it does it run everything I throw at it. If so gg pz end of story.
zetsumeikuro said:
Don't bother using benchmarks to rate a phones performance that is a fatal error there. Benchmarks never effectively rate a phones performance. I just go by how smooth the phone runs and it does it run everything I throw at it. If so gg pz end of story.
Click to expand...
Click to collapse
True, but people still like to get the general idea. There are many factors.hence why I said the over all feel seems the same. Im going to use antutu, and quadrant. 5 times each to get a range.=-)
Sent from my rezound.
Izeltokatl said:
True, but people still like to get the general idea. There are many factors.hence why I said the over all feel seems the same. Im going to use antutu, and quadrant. 5 times each to get a range.=-)
Sent from my rezound.
Click to expand...
Click to collapse
Well whatever works for you. Just saying Quadrant is a poor tool to use to bench for many reasons which I won't go over. Antutu is nice for SD speed testing I think, oter than that meh. Benches are just for numbers for people to flex their epeens with. They just really don't truly gauge a devices performance.
zetsumeikuro said:
Well whatever works for you. Just saying Quadrant is a poor tool to use to bench for many reasons which I won't go over. Antutu is nice for SD speed testing I think, oter than that meh. Benches are just for numbers for people to flex their epeens with. They just really don't truly gauge a devices performance.
Click to expand...
Click to collapse
Benchmarks do have a some good uses... while comparing different phone models with benchmarks can be iffy, it can give an overall insight, (things like graphics capabilities with very GPU extensive games) but in the end user experience and daily use are the real judges.
Where benchmarks can be of the most use, is when comparing changes to the same phone model.
E.G. Comparing performance impacts of AOSP vs Sense, overclocking and under-clocking, and de-sensing/bloat removal.
When used for these reasons, you can get a really good feel for how changes are affecting your device overall. Even then, benchmarks are not the be all end all, and user experience is still important. As you may introduce lag or other performance issues that do not show up in benchmarks.
Which temp root method are you using? Mine isn't staying rooted long enough for me to justify using setCPU at all...
The new version and the one that comes with the newest clean tool stays until reboot.
Marine6680 said:
The new version and the one that comes with the newest clean tool stays until reboot.
Click to expand...
Click to collapse
Thx for the info, guess I must still be using the outdated method. I'll run the latest version of Scott's Clean tool and give it a shot.
Izeltokatl said:
So I installed SetCPU today. Been testing the kernels ability to work underclocked at the max of 918mhz. Also set the scaling to conservative. After a days use it's been as good as normal full speed, 1512mhz
The battery lasted throughout the day, compared to my first two days of stock settings with only 6 hours of good use.
I'll keep playing. Still want to do some testing and benchmarks to make sure it's not under performing. But at least at the user level it seems to react the same.no lag.
I did confirm the clock speed out side of SetCPU using system panel.
Sent from my rezound.
Click to expand...
Click to collapse
Please let us know what settings you use that work for you.
I generally stay temprooted unless I'm going to be away from a charger for a bit and need BT (since you can't turn BT back on after temproot). I wouldn't have SetCPU autostart on boot (since it won't ever be able to get root access immediately after boot).
Meanwhile, I also set it to conservative and will see what that accomplishes.
A kernel needs to support setcpu, stock kernels do not. You need to flash a custom kernel, so you need a development phone or s-off.
Sent from my ADR6400L using XDA App
This kernel apparently does work with SetCPU. I've confirmed using other cpu monitoring apps that the clock speed changes are capped.
I own 7 android phones, and have been rooting, overclocking, undervolting each and every single one of them (well one I still cant get rooted). I know when the cpu is under clocked and when it is not. Been doing these tweaks for 4 years now. If you use a tool like System Panel, at stock settings you can see the max cpu around 1500 on our little bad boy. When it peaks out the clock speed is shown. When you under clock it, then check again it won't go beyond the max cpu set in my testing I put a ceiling at 918mhz. System Panel reported full CPU usage (100%) at clock speed 918mhz. Typically with stock kernels, your absolutely right, changes to SetCPU do nothing at all to the real cpu. Which is confirmed, when I reboot and dont have root, if I attempt to use SetCPU and make the changes, System Panel reports 1500mhz (roughly) at full load regardless of what I set it to in SetCPU. If I did this to any of my other phones with stock kernels, you are correct it makes no difference as SystemPanel reports the stock max setting.
No I'm not being mean or aggressive, just saying. =-) And no don't believe me, but test it yourself and confirm or prove me wrong some other way and I admit error. Either way, half the fun is messing with the phone and trying to get it to do things it should not do.
Grnlantern79 said:
A kernel needs to support setcpu, stock kernels do not. You need to flash a custom kernel, so you need a development phone or s-off.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Sent from my rezound.
Izeltokatl said:
No I'm not being mean or aggressive, just saying. =-) And no don't believe me, but test it yourself and confirm or prove me wrong some other way and I admit error. Either way, half the fun is messing with the phone and trying to get it to do things it should not do.
Click to expand...
Click to collapse
Or I would say, "half the fun is messing with the phone and trying to get it to do things it should have always been allowed to do...." Just sayin'.
Are you using the profiles at all? Im interested to know what seems to be working out the best for you.
Izeltokatl said:
True, but people still like to get the general idea. There are many factors.hence why I said the over all feel seems the same. Im going to use antutu, and quadrant. 5 times each to get a range.=-)
Sent from my rezound.
Click to expand...
Click to collapse
In my view, the "benchmarks" would be an OK measurement if you were comparing apples to apples.
I tried running both Linpack and Quadrant on the very recently and dearly departed Incredible right after a fresh reboot and having charged the battery overnight...when the thing should have been at it's freshest.
I got wildly different scores each time I ran it after a reboot...knowing that on both programs the scores would improve the more times you ran the test.
It didn't seem to me that either program was a reliable indicator of what my phone was capable of. I didn't even trust them to tell me whether something I'd done...cleared cache or deleted bloatware...had any real effect.
It simply boils down to how the phone feels. That's not scientific, but it works for me.
douger1957 said:
In my view, the "benchmarks" would be an OK measurement if you were comparing apples to apples.
I tried running both Linpack and Quadrant on the very recently and dearly departed Incredible right after a fresh reboot and having charged the battery overnight...when the thing should have been at it's freshest.
I got wildly different scores each time I ran it after a reboot...knowing that on both programs the scores would improve the more times you ran the test.
It didn't seem to me that either program was a reliable indicator of what my phone was capable of. I didn't even trust them to tell me whether something I'd done...cleared cache or deleted bloatware...had any real effect.
It simply boils down to how the phone feels. That's not scientific, but it works for me.
Click to expand...
Click to collapse
Linpack and Quadrant are not reliable benchmarks. TBH I don't take any of the benchmarks seriously, they are more for entertainment for me. But to each their own right?
Yeah some of the benchmark apps are a bit unreliable to say the least...
If I use one, I try to use ones that Anandtech uses. I trust them to find the better benchmark tools.
can some one recomend me some volts settings and gpu setting.. after i put on the overclocking kernel my galaxy is getting hot... know i got litening rom and still getting hot... i need some setting?? the battery drain fast..???
everything is not easy there r plenty of posts on ov/oc tweaks search or find in general section....
rocky23 said:
everything is not easy there r plenty of posts on ov/oc tweaks search or find in general section....
Click to expand...
Click to collapse
OP - ^^ this. Good advice. Start with stock voltages & gradually decrease until you get to the lowest possible whilst remaining stable. As Rocky has said, there's no shortcuts (apart from the the posts on this subject on here), it's trial & error.
And the other thing, don't expect to see massive increases in battery life with undervolting. Yes, you'll get some increase over the life of a whole charge, but it won't double your battery life or anything like that. So far as the heat issue is concerned, of course your phone is going to get hot if you overclock.
The phone is only made to go to 1200mhz out of the box. If you want to overclock, heat is something you're going to have to learn to live with; tho undervolting might reduce the heat produced by overclocking a little bit.
Overclocking is the same as undervolting in that some CPU's can handle more or less than others. Your phone might be able to handle 1600mhz just fine whereas the CPU in mine might only be able to handle 1400mhz. Same with undervolting, stable values for me might cause your phone to crash.
adding to the above you could also check this thread:
http://forum.xda-developers.com/showthread.php?t=1572538
made by ArchenzeEL
Its an EXCELLENT thread to start with as there is quite some information as well as sample values for you to play with. Keep in mind that those values might not work with you but you can experiment a bit in order to find the values most suited to your phone.
Also i think you should take a look in this thread
http://forum.xda-developers.com/showthread.php?t=1369817
its a LONG LONG read but it will help you in the end understand how overclocking/undervolting works in general...