Hello! i am in the process of overclocking my thunderbolt in order to get better performance with the eternity rom, and i was wondering what you guys oc your phones to? and if you do, what program/setting do you use to do so? (i plan to use a script in init after have found suitable settings)
I, personally, find it pointless to OC the Thunderbolt. The phone is fast and smooth enough for me on the stock speed, plus the battery life is bad enough without adding more strain to it.
However, if you insist on OC'ing, 1.2GHz is a safe bet. Some people can get to 1.4GHz, but then you run into freezing and random reboots. Also remember that individual phones handle overclocking differently. Where one phone can run perfect at 1.4GHz, another might freeze instantly when going that high.
Good OC'ing programs include SetCPU, No Frills CPU, and ROM Toolbox.
I don't overclock. That being said i have OC'd my phone b4 i have had it up to 1.8 Ghz stable, but it doesnt seem to make anything run faster. I use the Thundershed version of CM7 and its super fast. I dont think it could get much faster. and without overclocking i get better battery life.
thanks for the info actually ended up going with the lean kernel which is oc'd on the kernel level, works fairly well
lacrosse1991 said:
thanks for the info actually ended up going with the lean kernel which is oc'd on the kernel level, works fairly well
Click to expand...
Click to collapse
Leankernel is tops. I use battsaver mode which is stock speed and undervolted. Smooth as butter on my phone.
Sent from my ADR6400L using xda premium
Related
I know for the droid there are lots of custom kernels that use very low voltages for high speeds. Do we have custom kernels like this?
The processor in our phone is that of the original 2g/3g iPhone, the 528mhz Qualcomm (that should have been updated 3 years ago).
The processor in the Droid is the same as the iPhone 3gs (except 550mhz clocked instead of 600mhz).
The Droid processor has a floating point co-processor (sort of) which is why the Linpack scores are WAY higher than ours (it doesn't actually mean the phone is faster, it just does certain floating point operations faster).
The Droid processor is also SEVERELY underclocked, probably for power reasons. There is more of a demand in the Droid crowd to control power usage while still increasing speed (hence the low-voltage kernels, etc). "Lower voltages" are found by using different ways to multiply the frequency, but in a processor like ours, we are limited in the different speeds we can multiply (not to mention a ceiling of reasonable operation being usually 800mhz or below).
See, some people want their droids to be at 800mhz. They want that great battery life, to keep things cool, and a small performance boost.
Some want to go up to 1300mhz, maybe because they play games, or because the think they're cool, or whatever. That requires different methods for overclocking (depending on which exact speeds) and uses a lot more juice. You could use a 1300mhz kernel and keep it down around 800mhz (or whatever specific speeds the kernel allows), but that kernel might not be built for low voltage - you might just be still multiplying a number that keeps your voltage high, instead of the 800mhz Kernel that only goes so high, but keeps things easier on the battery.
Our Eris processors are more limited. Pretty much, you want your Eris OC'd (usually to the 700+mhz somewhere is all you get), or you don't. If you don't want it OC'd, you just don't install SetCPU. If you do, you install and use it (or whatever other overclocking app/widget you want).
To use your Eris low voltage, you pretty much need to stay 480mhz or lower. I keep my sleep SetCPU Profile at 122mhz-480mhz. VERY good on battery, and it throttles up to 480mhz (so the phone rings faster) when it's time for a call to come in.
Some Kernels have some things enabled (netfilter for wifi tethering and other things, a2sd enabled, overclocking, etc - depending on how it's put together). It's probably best to have a kernel that allows everything, since with our processors, there's not much of a power drain penalty (none that I know of in fact) for having a different kernel, and just running at 528mhz. I notice no battery difference at 806mhz in fact, it's a matter of having SetCPU profiles (or whatever) set up correctly and effectively.
Here are a few Kernels you might find (but most are incorporated in ROMs already, so you'll virtually NEVER have to flash it - except that I use Ivan's Eris_Official 1.0 ROM with zanfur's beautiful v3 kernel - it works perfectly at 806mhz on my Eris).
AOSP kernel with all the goodies:
http://forum.xda-developers.com/showthread.php?t=688275&highlight=kernel
Zanfur's kernel (my favorite):
http://forum.xda-developers.com/showthread.php?t=679102&highlight=kernel
Kaos posted this one for AOSP:
http://forum.xda-developers.com/showthread.php?t=688439&highlight=kernel
Darchstar posted this one:
http://forum.xda-developers.com/showthread.php?t=686797&highlight=kernel
The point is that for us, it's not that useful to flash kernels. Most of the ROMs you'll download (even the most 'basic' ones) have all the goodies enabled on the Kernel.
Different phone, different hardware, different ballgame.
God damn. Best answer I could have hoped for. Seriously thanks a ton man, that was everything I could have wanted to know thoroughly explained.
nvm. answered my own question hah
I'm on Conap's new CFS Kernel. I multitask a lot so that's the kernel for me. Everything feels more responsive. Like 1.5x the responsiveness from the (I think) BFS kernel nonsensikal comes with. I typed all of this without even a hint of lag.
Sent from my nonsensikal froyo using XDA App
Yeah I've learned a lot since I made this topic a few months ago lol
I'm on V4 cfs
5thAgent said:
I'm on Conap's new CFS Kernel. I multitask a lot so that's the kernel for me. Everything feels more responsive. Like 1.5x the responsiveness from the (I think) BFS kernel nonsensikal comes with. I typed all of this without even a hint of lag.
Sent from my nonsensikal froyo using XDA App
Click to expand...
Click to collapse
Which keyboard did you use?
I'm using Kaos's DroidX keyboard - Froyo port.
Sent from my nonsensikal froyo using XDA App
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.
I'm a a newer android user but quickly picking up on custom ROM's, etc. I'm currently running Alien #4 with the Alien theme and the kernel that comes with alien. I'm always trying to test out new combinations of things to see if I can get the most performance out of my phone while still maintaining a great battery life. So it's a constant trade-off. So my question is
Is there a difference between Faux's stock kernel for the atrix and the one that comes with alien or are the both stock in the sense of the same one as if I were running the Gingerbread release from AT&T?
If I were to install the Faux or kohlk OC kernls, but not install SetCPU would they still run at the higher clock speeds or would they run at 1GHZ until I used SetCPU to overclock? If they only run at 1Ghz, would there be benefit to using those kernels instead? I'm assuming they have more optimizations than just the overclocking. I'm quite happy with 1Ghz as my phone is plenty snappy so I'd rather keep the good battery life of 1Ghz but maybe get some better optimizations if possible.
I understand I can run SetCPU to have it clock down the CPU, but I've tried that on a number of occasions and even with it supposedly capped at 1Ghz, I still saw SetCPU saying my phone was in the 1.1Ghz state a fair bit.
I have faux's 1.3 ghz kernel and my battery life is comparable to the stock 1 ghz kernel.
Faux's stock kernel is a more optimized version of the stock kernel and is pretty good but his best work is put into his OC kernels. I suggest going with one of those...and yes you would need setCPU to get it to run above 1 ghz.
Have you ever run a "quadrant standard" test on your phone? I ran one when I was stock and scored below 1750. When I was on Alien v4 with faux's 1.3 ghz OC, I hit 2500. Now that I'm on CM7 with the same OC (and a little undervolting) I'm scoring above 4700.
Yea I use quandrant quite frequently but for me quandrant scores are good but I use my judgement on which feels the best. I know its now scientific but it works for me.
Sent from my MB860 using Tapatalk
I installed the webtop over hdmi mod on my Atrix and while testing it out, it got very warm in my hand. I opened the setcpu app and noticed that while overclocked to 1.3GHz, the CPU was running at 75C! I lowered it back down to the stock 1GHz and the temp slowly went down and settled at 63C.
It seems that while in webtop mode, the CPU is taxed at 100% all the time so I'm wondering if it's safe to stay overclocked when using webtop.
Everyone has different opinions of what is too hot around here.
IMO the cooler the better. IMI No Atrix should have a temp above 60c and I'm not even comfortable with above 50c either...
Sent from my MB860 using xda premium
I have experienced the same problem and worried that something may fry.... I have had mine overclocked at 1.45 using debian linux and all of a suddent he phone freezes and restarts.... Since it did it to me the second time I have kept my phone at 1Ghz... I am new at this so please don't beat me up too bad for being a noob... Just want to see if maybe undervolting it a little might help or hurt it?
Thanks in advance
Here are some tips I can offer
1.Try re-flashing your custom kernel and see if that fixes the web-top thing and over heating
Whenever the phone is plugged to the web-top it will naturally overheat so it's kinda expected remember now it's gotta work harder since its displaying on lap-dock or TV,but if you can cook an egg on it it might be too hot...lol
2.Set profile for temperature on setcpu so this way once you reach for example 100F your phone will clock down a little and so it might help the heat issue.You can set even more than one temp profile so this way when it reaches 96 it goes down a little then when it reaches 100 it will clock down a little more and such.
3.If that doesn't help,which in my situation it did.Flash a different kernel mayb it's just the one you're using that is causing funny stuff to happen.
Edit: not sure but i think undervolting helps battery but causes more heat,I myself don't undervolt I just created litterally a bunch of setcpu profiles for battery level,screen off,incall,charging,temp,and time and I'm getting 13 hour days at 1.3Ghz and temp profiles have been helping by clocking down when it's too hot therefore saving battery and drastic overheating.I dontlike my phone going anything over 104F it gets me paranoid,but that's just me.
I tried reflashing the kernel but it didn't change anything. I'm using Faux's 1.3GHz overclock kernel for Gingerbread (2.6.32.9). Is there something else I should be using?
sk8trix said:
Edit: not sure but i think undervolting helps battery but causes more heat,I myself don't undervolt I just created litterally a bunch of setcpu profiles for battery level,screen off,incall,charging,temp,and time and I'm getting 13 hour days at 1.3Ghz and temp profiles have been helping by clocking down when it's too hot therefore saving battery and drastic overheating.I dontlike my phone going anything over 104F it gets me paranoid,but that's just me.
Click to expand...
Click to collapse
Do what sktrix said in rest of his post.
I use the stopgap 1.0GHz kernel, and UV does lower temperatures. I would definitely try UV'ing a wee bit. You don't need to go crazy. I am using the following with great results for both temp and battery life:
-50
-50
-75
-75
-75
-100
-100
My setcpu profile clocks it back if I reach 60C, (I idle in the low to mid 30's). Under heavy load I reach around 52C max which is quite acceptable.
Now, granted I am not using Webtop, but the end result for UV should be the same. Lower temps and better battery life. You may also want to try just using 1.0GHz when on Webtop. The phone has more than enough power at this clock speed.
There is a bug with faux's kernel that causes the webtop to clock the phone at max speeds until restart.
Sent from my MB860 using xda premium
I know I'm straying from my correct forums here, however I have an LG Optimus 2X which like the Atrix, is a Tegra 2 CPU.
Our phones get VERY hot, I have had my CPU up to 86C before I decided to back off the stress test. CPUs are very good at handling high temperatures, and IMO you will see no ill effects from doing so, I am unsure of whether or not the Tegra 2 has thermal throttling/shut down, but in my experience they should be fine to around 80C.
The only issue I can forsee is the battery, batteries HATE high temperatures and it is awful for their life span, this is why your laptop batteries turn to crap after 1-2 years, even if low charge cycles, because they are always hot.
I would not be concerned about anything in the 70C realm, at all.
Alcapone263 said:
There is a bug with faux's kernel that causes the webtop to clock the phone at max speeds until restart.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Experienced this countless times. More with the latest 1.45Ghz, but it did happen on the previous release. When I dopped the mhz with setcpu, it wont scale but stay at max cpu. It even did it a few times without using the webtop.
g2tegg said:
Experienced this countless times. More with the latest 1.45Ghz, but it did happen on the previous release. When I dopped the mhz with setcpu, it wont scale but stay at max cpu. It even did it a few times without using the webtop.
Click to expand...
Click to collapse
So which overclocked kernel is best for webtop? I too have noticed where the CPU hangs at 100% at 1.45Ghz for a while when disconnected but it is always there when im in webtop mode.... How is Faux 1.3Ghz kernel with webtop?
ericemir said:
So which overclocked kernel is best for webtop? I too have noticed where the CPU hangs at 100% at 1.45Ghz for a while when disconnected but it is always there when im in webtop mode.... How is Faux 1.3Ghz kernel with webtop?
Click to expand...
Click to collapse
It will still hang at 1.3ghz, though it's a known bug. I just stick with the 1.0 enhanced, there's no noticeable real-world difference from going over 1.0ghz anyway, it's just a benchmark gimmick. Right now, the software that's out there is optimized to run on existing hardware w/o overclocks. I've run Shadowgun at 1.45ghz and didn't see any difference over the 1.0 enhanced.
Now, if we were trying to run games that were coded specifically or faster-paced chipsets then we'd need overclocking to catch up much like you would in the PC arena. That, however, is not happening in the cell phone market just yet.
treehumper said:
I just stick with the 1.0 enhanced, there's no noticeable real-world difference from going over 1.0ghz anyway, it's just a benchmark gimmick.
Click to expand...
Click to collapse
What's the advantage to running a custom kernel if you're not overclocking? Forgive me if this is a stupid question lol. Still a noob.
cjrhoades said:
What's the advantage to running a custom kernel if you're not overclocking? Forgive me if this is a stupid question lol. Still a noob.
Click to expand...
Click to collapse
Bump.
Anyone?
cjrhoades said:
Bump.
Anyone?
Click to expand...
Click to collapse
Read the history at the following:
http://forum.xda-developers.com/showpost.php?p=15387385&postcount=1
You will see a lot more optimization than just upping the clock speed. One of the reasons the 1.0GHz kernel works much better than the stock kernel. Also, the ability to undervolt saving battery life.
IMO there is no need for 1.3GHz or 1.45GHz in everyday use of a phone. The only benefit is for OC'ing bragging rights. Until we can control phone temperatures better, it's pointless to risk the substantial heat increase on ALL internal components for extended periods of time which results from much increased CPU temperatures.
CaelanT said:
Read the history at the following:
http://forum.xda-developers.com/showpost.php?p=15387385&postcount=1
You will see a lot more optimization than just upping the clock speed. One of the reasons the 1.0GHz kernel works much better than the stock kernel. Also, the ability to undervolt saving battery life.
IMO there is no need for 1.3GHz or 1.45GHz in everyday use of a phone. The only benefit is for OC'ing bragging rights. Until we can control phone temperatures better, it's pointless to risk the substantial heat increase on ALL internal components for extended periods of time which results from much increased CPU temperatures.
Click to expand...
Click to collapse
I see... guess that explains why the phone doesn't really feel any faster when it's overclocked. I'll flash the 1GHz kernel then.
Thanks for the info.
Not sure if this is the same with phones but normally a CPU should stay at 40C idle and 50C load. Maximum would be 60C while benching or something.
If it goes above that I would definitely underclock/undervolt.
cjrhoades said:
what's the advantage to running a custom kernel if you're not overclocking? Forgive me if this is a stupid question lol. Still a noob.
Click to expand...
Click to collapse
also has other fixes besides overclocking you can go read them in the kernel threads
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