I'm running the awesome das BAMF ROM 2.0-5 with the MR2 radio. The camera on this ROM runs much smoother when max CPU frequency is set at 1.4 ghz. Is it generally safe to leave my phone overclocked at 1.4 GHz indefinitely? Particularly for a daily driver/ primary and only phone? It seems to run this so far, but I don't know enough about long term effects of overclocking. Thanks everyone.
I overclocked my Eris for over a year. 1.4 ghz is safe as a general rule because it can run stable up to 1.8. If you use SetCPU you can set profiles to underclock when the screen is off, below a certain battery level, etc. Just remember that if you flashed imoseyon's kernel, you need to run the speedtweak.sh script in a terminal emulator and run option 13 if you are using SetCPU after selecting voltage options.
Sent from my ADR6400L using XDA App
I'm thinking I'll stick to whatever kernel is in the das bamf 2.0-5 ROM. Easy drop down menus
Also, if a kernel runs stable at a certain frequency (say 1.8 ghz), does it follow that the processor hardware itself will also be OK? In other words, if I can run at 1.8 ghz stable and deal with the battery life associated with it, will my phone last through my two-year contract or will I wake up one morning a year from now and find the phone has turned into a marshmallow?
Well obviously there is risk involved, but a processor either runs fine, or it wont run at all. Personally I run at 1.6 Max right now, only because its not worth the risk, with the minimal gains to run it at 1.8. In terms of the longevity, well sometimes you gotta just take the plunge bud, that's the fun in android.
Sent from my ADR6400L using XDA App
You won't really notice any performance difference with anything over 1.4 ghz.
I have been running imoseyon's kernels at 1.4 max & 245 min ever since he implemented speedtweak. No overheating, reboots or other weirdness. Ymmv, each phone has different tolerances. But as long as you don't o/c the min frequency (i.e., you're not constantly at 1.9 or 1.4 ghz) you will probably be fine.
Sent from my ADR6400L using XDA App
sublimaze said:
I have been running imoseyon's kernels at 1.4 max & 245 min ever since he implemented speedtweak. No overheating, reboots or other weirdness. Ymmv, each phone has different tolerances. But as long as you don't o/c the min frequency (i.e., you're not constantly at 1.9 or 1.4 ghz) you will probably be fine.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
same here, imo's kernels have made this phone what it should be. it has incredible battery life compared to stock.
but to answer the OP's question, i can't see why leaving it o/c'ed to 1.4 indefinitely will harm anything. like sublimaze mentioned, as long as you don't bump up the min freq, your phone won't be running at 1.4 the whole time. it only gets up that high when an app or system function needs the processing power.
on a side note, even if you did put your min freq at 1.4, i still don't think it would hurt anything, it would just murder your battery quickly
Related
You should share what speed and voltages you are running at, I figured it would be helpful to give other people ideas of where to begin trying their voltages at for undervolting purposes. So, what's your lowest voltages at the highest clock speeds?
I'm using SetCPU's standard voltages. 1.8/.38 normal, .87/.38 screen off and over 130F, 1.2/.38 battery less than 50%, 1.8/1.2 plugged in. Getting 4-5 more hours per charge!
Sent from my PG86100 using XDA Premium App
Here's the values I've currently got in my Permatemp Root .bat file (thanks Eugene!): scpll_l_val=24 vdd_uv=1060000
That gives me 1.296 ghz at 1.06 volts. I know 1.3 ghz isn't much of an overclock, but this phone is already so fast (especially compared to my old Hero, lol) that I'm not really craving any more speed ... what I'm most interested in is undervolting for max battery life. From what I've read the stock voltage at 1.2 ghz is 1.18 volts, so I'm a little under that right now. I tried 1.00 and 1.03 volts and got reboots every time, but 1.06 volts runs rock-solid reliable for me at 1.3 ghz.
is that really even noticable? the LCD draw most of the power typically
oldjackbob said:
Here's the values I've currently got in my Permatemp Root .bat file (thanks Eugene!): scpll_l_val=24 vdd_uv=1060000
That gives me 1.296 ghz at 1.06 volts. I know 1.3 ghz isn't much of an overclock, but this phone is already so fast (especially compared to my old Hero, lol) that I'm not really craving any more speed ... what I'm most interested in is undervolting for max battery life. From what I've read the stock voltage at 1.2 ghz is 1.18 volts, so I'm a little under that right now. I tried 1.00 and 1.03 volts and got reboots every time, but 1.06 volts runs rock-solid reliable for me at 1.3 ghz.
Click to expand...
Click to collapse
Someone in the OC topic was asking about UV at stock speeds. You're close enough to stock that you should qualify. You should go post your results in that thread too. They'd be happy to see them.
I'm running @ 1.78GHz with a vdd of 1300000. I'm going to try and go lower... maybe 12800000.
I have it overclock to 1728mhz but dint know where to adjust the voltage. Does setcpu does this or i need a different program to read voltage/change voltage?
Sent from my PG86100 using XDA App
eduardmc said:
I have it overclock to 1728mhz but dint know where to adjust the voltage. Does setcpu does this or i need a different program to read voltage/change voltage?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
You adjust the voltage when you type the ADB command to OC. If you're using a script that does it for you, you will need to edit that script and look for the vdd_uv= line.
bitslizer said:
is that really even noticable? the LCD draw most of the power typically
Click to expand...
Click to collapse
What do you mean by "is that really even noticable"? It's certainly calculatable ... it's an 11.3 percent improvement in battery usage by the CPU. If you're saying that's not very much, well, it's all relative. If you're saying you're not interested in saving a little battery when it won't cost you anything to do so, that's fine with me. If you're saying that no power-saving effort is worth any consideration because the LCD is the biggest power draw of all and that's the only one that matters, then why did Qualcomm bother to develop asynchronous cores and low-power audio modules and low-power GPS modules? I mean, hey, the screen is all that matters, right?
Or did I misread your statement?
Edit: Sorry for coming across as so argumentative, I just don't understand why you're taking the position you are.
oldjackbob said:
What do you mean by "is that really even noticable"? It's certainly calculatable ... it's an 11.3 percent improvement in battery usage by the CPU. If you're saying that's not very much, well, it's all relative. If you're saying you're not interested in saving a little battery when it won't cost you anything to do so, that's fine with me. If you're saying that no power-saving effort is worth any consideration because the LCD is the biggest power draw of all and that's the only one that matters, then why did Qualcomm bother to develop asynchronous cores and low-power audio modules and low-power GPS modules? I mean, hey, the screen is all that matters, right?
Or did I misread your statement?
Edit: Sorry for coming across as so argumentative, I just don't understand why you're taking the position you are.
Click to expand...
Click to collapse
+1! Would have thanked you, except I'm at my limit.
I'm at 35 @1450000. I know I can go lower, but if I overclock, I want stability not battery life
On another note: I can't wait until we have source, custom kernels, and I finish up the viperMOD app to get support for the E3D. Will be one awesome beast undervolted!
I'm at 1.56ghz and 120000 voltage.
Runs stable, get a nice speed boost without killing my battery. Am going to try a lower voltage. I've read the could will default to stock speed if you go too low though. Guess I'll find out.
Sent from my PG86100 using Tapatalk
felacio said:
I'm at 1.56ghz and 120000 voltage.
Runs stable, get a nice speed boost without killing my battery. Am going to try a lower voltage. I've read the could will default to stock speed if you go too low though. Guess I'll find out.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
No, if your voltage is too low, your phone will freeze or instanly reboot on you.
-viperboy- said:
No, if your voltage is too low, your phone will freeze or instanly reboot on you.
Click to expand...
Click to collapse
Well. I can handle that. Lol. Guess I'm going lower! Wish me luck!
Sent from my PG86100 using Tapatalk
I am currently testing scpll_l_val=22 vdd_uv=1010000 for undervolting purposes, 1000000 caused a reboot, 1010000 has been holding up well under stress tests..
If one of you guys who are overclocking could test this video clip and either diceplayer or the diceplayer free trial in the market - I would appreciate it:
http://www.movie-list.com/forum/showthread.php?t=27232
Supposedly - the Samsung Galaxy S2 can play 1080P + AC3 MKV's smoothly. But the Evo3D and Sensation lag a bit according to the developer. I tested this file with my evo3D and it looked like my Evo3D stuttered every 3 seconds or so. I'm just wondering if an overclock would smooth out playback - but I haven't installed temproot.
For those of you overclocking just for battery savings, I am currently testing
adb shell insmod /data/local/tmp/8x60_oc.ko scpll_l_val=22 vdd_uv=1003100 and have been stable so far, this is the absolute lowest I can push it at 1.2Ghz on my phone, can anyone else match this or go lower? I think it will be helpful to start establishing these values now so kernel makers will have some ideas of how far they can push our phones.
P0ll0L0c0 said:
If one of you guys who are overclocking could test this video clip and either diceplayer or the diceplayer free trial in the market - I would appreciate it:
http://www.movie-list.com/forum/showthread.php?t=27232
Supposedly - the Samsung Galaxy S2 can play 1080P + AC3 MKV's smoothly. But the Evo3D and Sensation lag a bit according to the developer. I tested this file with my evo3D and it looked like my Evo3D stuttered every 3 seconds or so. I'm just wondering if an overclock would smooth out playback - but I haven't installed temproot.
Click to expand...
Click to collapse
Speed = 1.5GHz.
The default gallery player plays it perfectly, but there's no sound.
RockPlayer plays it very choppily, but has sound.
Dice player plays somewhat smoothly and has sound, but there are lag moments every 3-6 seconds as you said.
It's a software issue.
PaulB007 said:
For those of you overclocking just for battery savings, I am currently testing
adb shell insmod /data/local/tmp/8x60_oc.ko scpll_l_val=22 vdd_uv=1003100 and have been stable so far, this is the absolute lowest I can push it at 1.2Ghz on my phone, can anyone else match this or go lower? I think it will be helpful to start establishing these values now so kernel makers will have some ideas of how far they can push our phones.
Click to expand...
Click to collapse
Right noe I'm sitting at 29 (1.56ghz) with a UV of 1170000. Tried 1150000 but phone immediately restarted. And 1160000 restarted after a while. This seems stable so far. Haven't totally stressed it yet though.
Sent from my PG86100 using Tapatalk
nabbed said:
Speed = 1.5GHz.
The default gallery player plays it perfectly, but there's no sound.
RockPlayer plays it very choppily, but has sound.
Dice player plays somewhat smoothly and has sound, but there are lag moments every 3-6 seconds as you said.
It's a software issue.
Click to expand...
Click to collapse
Thanks for the check! I was wondering if there would still be lag with an overclock - that's disappointing. Supposedly the SGS2 handles files like it with no problem.
OC Script
Here is a batch file I created to make it easier to OC. Basically just the Rooting script with a menu to select the speed with delays built in.
Rename from oc.txt to oc.bat if you wish to run the file.
You will most likely need to change the voltages to match your phone. My phone has been very OC friendly.
Currently running 1188mhz @ .97 Volts with no issues. I have been able to OC up to 1890mhz @ 1.32 volts.
Have not tried to go lower on the voltage at 1188mhz yet...
JDC4429
Im running Cm7 withh Imoseyon's kernal. Every time i oc to 1.9 phone will freeze almost instantly any suggestions to fix this
Sent from my ADR6400L using Tapatalk
Yep, slow the overclock to 1.5 your phone can't handle it, neither can mine. Some can and some can't but other than running a nice CPU test to show off to your buddies you don't want to push your TB like that on a daily basis. I have mine set to 368/1.02 and happy as can be with the extra battery life I get from my phone.
If I helped you in any way please use the thank you button
Alrighty i have mine set to 1.4 extremely undervolted and i get 9-10 hours battery life with heavy use thank you
Sent from my ADR6400L using Tapatalk
Hello,
I have a few issues with IMO's lean kernel that someone might can help with. 1) Extreme settings 2 and 4 cause instant phone freeze and reboot. 2) Option 3 works for the first minute or two after boot but then freezes (CPU spy shows 1.92 GHz runs smooth through boot). I believe it to be caused by the ramp up/down of the governor or possibly a script/setting messing with my system.
I am able to run very stably and smooth with a top CPU speed of 1.6 GHZ( 1.593 GHz on A05P). Any ideas on what I can do to increase the CPU speed so that the system stays stable? Your input is much appreciated. Thank you again for helping this poor noob.
Veltar said:
Hello,
I have a few issues with IMO's lean kernel that someone might can help with. 1) Extreme settings 2 and 4 cause instant phone freeze and reboot. 2) Option 3 works for the first minute or two after boot but then freezes (CPU spy shows 1.92 GHz runs smooth through boot). I believe it to be caused by the ramp up/down of the governor or possibly a script/setting messing with my system.
I am able to run very stably and smooth with a top CPU speed of 1.6 GHZ( 1.593 GHz on A05P). Any ideas on what I can do to increase the CPU speed so that the system stays stable? Your input is much appreciated. Thank you again for helping this poor noob.
Click to expand...
Click to collapse
Don't OC that high, simple as that. There is no need to run the phone constantly at 1.9ghz.
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
Honestly, I'm down to 1512. A notch above that proved unstable as far as I can tell. I can run benchmarks fine upwards of ~1800, but I'll get random force closes and boot loops if left for any extended period of time. Also have issues with display not coming back on (menu lights and led backlight work, but no image). The stability test app is pretty much worthless too. Let it run for 6 hrs no errors. When I turned it off, BAM restart.
So what is your max, truly stable, OC?
Sent from my PG86100 using XDA App
edit: just for archival's sake, using Anthrax-CDMA-Sense (v1216) with Scott's 2.08.651.2 Stock Rooted ROM.
That's interesting...
I'm using the same Kernel with Scott's 'senseless' ROM and I have my clock set to 1.836 with no issues.
I'm no expert but have you tried using a super wipe (or just manually wiping everything including system) and reflashing?
Sent from my PG86100 using XDA App
My first 3D was pretty stable at 1.94 but when it started getting the black screen of death I got it replaced through sprint. The Refurbed one they gave me (the one I have now) freezes if I go to 1.6..
I used to do 1.94 but it gave me random reboots (nothing fatal)
I stick to 1.5 smartass when the battery is greater than 50%, then 1.2 smartass, and .8 conservative at 15%.
On charge it's 1.7GHz lagfree
Depends on your CPU, they all arn't created equal. I'm stable at 1.9 GHz with no reboots. I'd say that 1.5 is a good mark, seeing as the HTC Rezound has the exact same CPU as the Evo 3D, just clocked to 1.5 instead of 1.2.
Akasa Fox said:
Depends on your CPU, they all arn't created equal. I'm stable at 1.9 GHz with no reboots. I'd say that 1.5 is a good mark, seeing as the HTC Rezound has the exact same CPU as the Evo 3D, just clocked to 1.5 instead of 1.2.
Click to expand...
Click to collapse
This is interesting. I bet the CPUs, while manufacturing wise are identical, are chosen based on thier bin level for the different devices.
After writing this post I cleared Dalvik cache and switched my kernel to RCmix-evo3d-v7. I ran it at 1.62 or something like that while I was running around Christmas shopping, so it had heavy use. Google nav, lots of phone calls, texts, Pandora, etc with zero issues (especially that display issue I mentioned is gone, thank god). After getting home I was so impressed with it that i stepped it up to 1.782, and we'll see about that, although I'm not holding my breath.
Basically I learned that your overclocking potential (or maybe more accurately system stability regardless of overclocking) is greatly influenced by your kernel.
Akasa Fox, mind sharing your kernel version, ROM and version, and hboot and any other potentially relevant information I may be forgetting? I'm impressed with your performance.
Sent from my PG86100 using XDA App
zadias said:
I used to do 1.94 but it gave me random reboots (nothing fatal)
I stick to 1.5 smartass when the battery is greater than 50%, then 1.2 smartass, and .8 conservative at 15%.
On charge it's 1.7GHz lagfree
Click to expand...
Click to collapse
I like this approach of different clocks and governers based on bat level. Is this a pro feature of the Antutu app?
Sent from my PG86100 using XDA App
bleaktrotter said:
This is interesting. I bet the CPUs, while manufacturing wise are identical, are chosen based on thier bin level for the different devices.
After writing this post I cleared Dalvik cache and switched my kernel to RCmix-evo3d-v7. I ran it at 1.62 or something like that while I was running around Christmas shopping, so it had heavy use. Google nav, lots of phone calls, texts, Pandora, etc with zero issues (especially that display issue I mentioned is gone, thank god). After getting home I was so impressed with it that i stepped it up to 1.782, and we'll see about that, although I'm not holding my breath.
Basically I learned that your overclocking potential (or maybe more accurately system stability regardless of overclocking) is greatly influenced by your kernel.
Akasa Fox, mind sharing your kernel version, ROM and version, and hboot and any other potentially relevant information I may be forgetting? I'm impressed with your performance.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
The kernel does have a decent bit to do with your max OC, but it also has to do with the CPU you have and if it was made on a good day at the foundry or not and how good a section of the silicon it came from.
I used to run RC Mix kernels before Chad was around, but those kernels always ran MUCH hotter. When playing a game my phone would literally be almost too hot to touch. Chad's Anthrax kernels have always been cool and after playing a game for a while (same game, same amount of time) the phone is just a bit warm. So you may be able to go farther with an OC on RC Mix kernels, but your phone's lifetime for its processor is going to be a whole lot less. At the temp it was hitting id bet it is well above its max rated temperature level and degrading the processor substantially.
Some people may not be able to OC far, but how far can you undervolt? Many times those who cannot OC very high can undervolt like crazy (me included) and those who can OC much higher than most also cannot run really low voltage levels. My phone is 100% stable @ 192MHz on only 700mv. Thats the lowest Chad allows, Id love to see if I can be stable even lower. I am also 100% stable @ 1188MHz (HTC Stock) with only 987.5mv. But the most I have ever been able to overclock stably (even with RC Mix kernel) was 1.6GHz, with the max benchable being 1.72GHz. Any higher and the phone insta locks up and reboots. No matter what voltage.
Hm, that's a good point. I'd like to push the undervolt limits as well to see what its got. That anthrax kernel I mentioned in the first post was terribly unstable for me, but maybe I should give it another shot after researching the super wipe method mentioned a few posts up. Is there a version of his kernel that everyone is having good luck with? Or is the latest one the best?
Also, I don't see voltage options in the antutu program. What are you using for your oc/uv utility?
Thanks.
Sent from my PG86100 using XDA App
bleaktrotter said:
I like this approach of different clocks and governers based on bat level. Is this a pro feature of the Antutu app?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Just profile settings for SetCPU.
bleaktrotter said:
Hm, that's a good point. I'd like to push the undervolt limits as well to see what its got. That anthrax kernel I mentioned in the first post was terribly unstable for me, but maybe I should give it another shot after researching the super wipe method mentioned a few posts up. Is there a version of his kernel that everyone is having good luck with? Or is the latest one the best?
Also, I don't see voltage options in the antutu program. What are you using for your oc/uv utility?
Thanks.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
His latest 100% Qualcomm based kernel is incredibly smooth. 100% stable for me. I'm giving this kernel a lot of praise considering I used to have crazy reboots and lockups on the older anthrax kernels.
Sent from my PG86100 using Tapatalk
Weird. Well, I will give it another shot before writing him off. I'm a noob so its entirely possible and probable that I did something wrong.
I found setcpu last night, but I didn't see any uv options. Does rcmix not allow for it?
Thanks.
Sent from my PG86100 using XDA App
Just leave it at the default settings... It's fast enough as it is.
Sent from my PG86100 using xda premium
1782mhz. I stay at stock though.
My Blog: knowledgexswag.tumblr.com
Twitter: @knowledge561
Coriolis3ffect said:
Just leave it at the default settings... It's fast enough as it is.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Noted.
Sent from my PG86100 using XDA App
My phone won't overclock for ****. At first it would do good and I could get around 1.7-1.8, now when I try anything after superwipe and wiping through nand, I can't get the thing to post at 1.5 and remain stable without lockups/freezing and slowdowns. The phone even has trouble at stock now. I haven't traded it in for obvious no s off reason.
1.78 GHz. I can do 1.83 but not very stable.
1.782 runs all day locked at that speed but I usually run bcblend kernel @ 1.512 max 194 min. Ondemand.
Sent from my PG86100 using Tapatalk
bleaktrotter said:
Akasa Fox, mind sharing your kernel version, ROM and version, and hboot and any other potentially relevant information I may be forgetting? I'm impressed with your performance.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I know it was Virus' InfectedROM (Before the nightly), Software 2.08.651.2, HBoot 1.5 (HTC Unlock.) [Edit]: I'm almost certain the Kernel I used was Tiamat, hard to remember though, seeing as I traded out performance for battery life by switching to viper ages ago. (And that i'm a flashaholic )
im @ 49 hours uptime on RLS4 of my new kenel @ 1.94GHz IntelliAnthrax
..no RLS4 is not public yet -- testers will have it in 1-2 days
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