I just put tazz 14 on and set my Max at 768... is that too much... I have read so much on what clock speeds to set but I still don't know what's best.. also... what is Eris stock clocks?
Notxok said:
I just put tazz 14 on and set my Max at 768... is that too much... I have read so much on what clock speeds to set but I still don't know what's best.. also... what is Eris stock clocks?
Click to expand...
Click to collapse
If your phone is running ok and getting too hot then 768 should be fine, many of us run 806 without a problem. I think stock CPU is set at 528 (maybe lower, I don't remember)
BTW this should probably be in Q&A board
Sent from my nonsensikal froyo
I run 768 with no problems.
SikYou said:
If your phone is running ok and getting too hot then 768 should be fine, many of us run 806 without a problem. I think stock CPU is set at 528 (maybe lower, I don't remember)
BTW this should probably be in Q&A board
Sent from my nonsensikal froyo
Click to expand...
Click to collapse
806 are you ****ting me?... is it set to performance?
Notxok said:
806 are you ****ting me?... is it set to performance?
Click to expand...
Click to collapse
Interactive
Sent from my nonsensikal froyo
Hmmm. I'm trying 806 now.
SikYou said:
Interactive
Sent from my nonsensikal froyo
Click to expand...
Click to collapse
806 in interactive rebooted for me.. I might have to reflash a ROM now LOL... lucky I wish I could run 806 efficiently
You should never try clock speeds without disabling "Start on boot" or you can really screw yourself over....
Anyway, 768 is a very common speed for people to be able to hit. I personally become unstable at 806 (especially with JIT on) and I stick to 787.
Hungry Man said:
You should never try clock speeds without disabling "Start on boot" or you can really screw yourself over....
Anyway, 768 is a very common speed for people to be able to hit. I personally become unstable at 806 (especially with JIT on) and I stick to 787.
Click to expand...
Click to collapse
Your 486 Makes me Envious.. Would you mind PMing m your set-up ( ROM Set CPU info and current task killer? )
My 486 was a while ago and doesn't really reflect the overall performance of my phone; as in my phone is currently faster but I get lower quadrant scores (440-450)
I was on Tazz V6 I believe, clocked to 768mhz performance, with BFS V2 or V3. After rebooting and flashing the kernel I was getting high 470's and mid 480's so I took a picture with my girlfriend's Incredible.
JIT was at 16m and I'd just switched from 24 to 16 and wiped dalvik. This is significant because anytime you switch your dalvik heapsize and reboot your quadrant scores will be at their highest, not sure why, probably has to do with RAM allocation.
Hungry Man said:
My 486 was a while ago and doesn't really reflect the overall performance of my phone; as in my phone is currently faster but I get lower quadrant scores (440-450)
I was on Tazz V6 I believe, clocked to 768mhz performance, with BFS V2 or V3. After rebooting and flashing the kernel I was getting high 470's and mid 480's so I took a picture with my girlfriend's Incredible.
JIT was at 16m and I'd just switched from 24 to 16 and wiped dalvik. This is significant because anytime you switch your dalvik heapsize and reboot your quadrant scores will be at their highest, not sure why, probably has to do with RAM allocation.
Click to expand...
Click to collapse
I don't get above a 415-420 really.. any suggestions or help?
Notxok said:
806 in interactive rebooted for me.. I might have to reflash a ROM now LOL... lucky I wish I could run 806 efficiently
Click to expand...
Click to collapse
806 seems to be running a fraction faster but to me it is hardly noticeable coming from 768.
Notxok said:
I don't get above a 415-420 really.. any suggestions or help?
Click to expand...
Click to collapse
Don't read too much in the benchmarks . I usually run happily around 430.
I use SetCPU (interactive 768 / 245)
I don't run any task killers, in my experience they are more trouble than they are worth.
The other thing IMHO if you don't use an app, get rid of it.
Task killers are in fact more trouble than they're worth, especially automatic ones. I use advanced task killer and I only ever kill tasks right after my phone has started up/ when my phone is plugged in. Task killers hurt battery life and performance.
Hungry Man said:
Task killers are in fact more trouble than they're worth, especially automatic ones. I use advanced task killer and I only ever kill tasks right after my phone has started up/ when my phone is plugged in. Task killers hurt battery life and performance.
Click to expand...
Click to collapse
Thanks Guys... Ill keep that in mind.. I was using auto memory killer
Notxok said:
I just put tazz 14 on and set my Max at 768... is that too much... I have read so much on what clock speeds to set but I still don't know what's best.. also... what is Eris stock clocks?
Click to expand...
Click to collapse
In my personal experience, I would disable set on boot in SetCPU and start gradually bumping the speed up. Usually at 787 my phone runs best (fastest and most stable). Then, I'd go back and bump it to 806. It WOULD run but after about 5 minutes of playing with my phone it typically causes it to lock. 825 Causes an immediate lock. So I typically leave it at 787 and all Froyo roms seem to run fine at that for me. I don't even test anymore...just restore SetCPU app and data with Titanium on initial boot of a new rom. So far, no problems.
Sent from my ERIS using XDA App
What's the best setting? Ondemand? Interactive? Prefermance..etc
Sent from my VANILLA TAZZ using XDA App
806 no problem using the Collins script.
Anything higher than 710 on my phone locks it up.
Related
Is it possible for me to install the VillianROM on my HTC Droid Eris or am I going to brick my phone?
are you rooted?
not heard of the villianrom. is it a eris rom? if it is not and not ported, prob just give you an endless boot....its pretty hard to brick your phone once you have the recovery image.
droidkevlar said:
not heard of the villianrom. is it a eris rom? if it is not and not ported, prob just give you an endless boot....its pretty hard to brick your phone once you have the recovery image.
Click to expand...
Click to collapse
I'm pretty sure its a g2/hero Rom.
droidkevlar said:
not heard of the villianrom. is it a eris rom? if it is not and not ported, prob just give you an endless boot....its pretty hard to brick your phone once you have the recovery image.
Click to expand...
Click to collapse
Evil Eris = Ported Villian Rom ;P
1. I am rooted and running:
- Eris_Official 0.81T2
- Senseless patch
- Nexus One patch
- Nexus Launcher w/LWPs
It's nice, but more laggy than I'd like. Is Evil Eris really the ported VillianRom?
After downloading SetCPU, I've been able to set my processor at a higher normal frequency and am experiencing better performance.
Turnyface said:
After downloading SetCPU, I've been able to set my processor at a higher normal frequency and am experiencing better performance.
Click to expand...
Click to collapse
what settings are you using?
droidfreak said:
what settings are you using?
Click to expand...
Click to collapse
I'm utilizing different profiles.
Normal:
Max = 528 mhz
Min = 245 mhz
Sleep/Standby
Max = 245 mhz
Min = 160 mhz
Battery temp > 50 C
Max = 160 mhz
Min = 160 mhz
Someone told me to do this because we actually can't overclock yet:
...fire up a adb shell and do a cat /proc/cpuinfo while it's over clocked were just curious to see if the program is in fact over clocking the cpu
Click to expand...
Click to collapse
when I did that, it came up with 526 which is not overclocking... funny thing was when I used a different profile to slow it down, it still said 526...
The highest frequency the Eris can attain at this time is 528 mhz. We're not overclocking, just simply setting the running frequency to a constant number. I don't think you're going to see a difference between 528 and 526. 2 mhz is such a minute amount.
right it is minute, but my point was that 528 is what the eris can do... but maybe youre right that set cpu keeps it at a constant... set it lower and run what I said and it probably still will say the 528... thats what I did not understand and never got an answer... it did not seem as though setcpu had throttled it back at all... I saved the app though waiting til we can get over 528..
Turnyface said:
1. I am rooted and running:
- Eris_Official 0.81T2
- Senseless patch
- Nexus One patch
- Nexus Launcher w/LWPs
It's nice, but more laggy than I'd like. Is Evil Eris really the ported VillianRom?
Click to expand...
Click to collapse
I'm runnning that exact same config, and I haven't noticed any lag.
It has been getting better as the night has gone on. The one issues I'm consistently having is the Nexus One Launcher force closes from time to time, making my phone useless and forcing me to pull the battery and start again. Maybe I'm doing something wrong?
Framework43 said:
Evil Eris = Ported Villian Rom ;P
Click to expand...
Click to collapse
really?
they dont act the same.
i have a friend who has the Villian Rom and well u kno i ran the Evil Eris and it was seemingly 2 totally different devices. even tho u say its the same thing?
What is the best overclock app for a rooted Eris running Froyo 2.2?
What is the best min/max setting too for performance?
I use SetCPU. It really depends on what you want.
I want the best performance possible, without overheating my phone
No matter what you're going to heat up when overclocking. If you use setcpu don't use the widget.
What's the safest maximum performance setting then?
What about overclock widget app (free)? I'm using that now. It seems ok, not sure though compared to setcpu.
ChadZ said:
What's the safest maximum performance setting then?
What about overclock widget app (free)? I'm using that now. It seems ok, not sure though compared to setcpu.
Click to expand...
Click to collapse
that widget app sucks. it's nothing compared to setcpu. I run 768max 19 min, and I have a full day of battery life, using it fairly regularly every day. I rarely have lag, and it's fast too.
using kayosfroyo btw.
Every processor is different. Some people get get to 844mhz, some people can't push past 710mhz. You need to find what's right for you.
I personally get up to 787mhz.
I run 806 all day no problem. But faster is a reboot. All phones seem to be different on their safe max w/o crash. I use setcpu myself. It's free on this fourm for members.
Sent from my Cyno Tazz 3.0 using XDA App
Yes, SetCPU is best. I can clock mine to about 806 and I get about 48 hours of battery... every phone is not the same, remember that!
using setcpu here as well. 825mhz no issues
Im using set cpu as well at 768 max and 245 min. Make sure u dont have set on boot if ur going to test the limit of ur phone, I did and was able to go 806 and past rat my phone locks up and on every reboot the same so I had to uninstall in using command prmpt from pc
Sent from my FroyoEris using XDA App
SicNside, were did you find the info for OCing? I don't quite get the whole "minute" thing. Can you point me in the right direction, as in a guide with explanations and recommended settings? Every post I find about OCing the Eris is old, and says "hasn't been done"
Sent from my FroyoEris using XDA App
Yeah ill type out what my settings r to give u an idea, later when I get home to access a computer.. what I meant for min= minimum
Sent from my FroyoEris using XDA App
Read this page http://forum.xda-developers.com/showthread.php?t=761940 and it will give you a little understanding on setting up for performence and setting up for performence With Higher battery life. This is the place i liked the best only because i needed increse speed with out loosing to much battery power due to not being in a place to set phone on the charger like i work 9 hours a day and i like to listen to music and fiddle on my phone on breaks.. Plus honestly my phone does not seem to be performing any slower than it was with a high performence setup i used to be 480 min with a 787 max, and somtimes higher but 245 min with 748 or 19 min with 748 i still have not noticed anything being slower than when i had it set at 480 min 787 max..
But i cant stress enough that dont have it set on boot when u are trying to find ur phones limits because if u do have it set and find ur phones limits u will have to adb that crap to uninstall it. find the settings u want for your phone before you set on boot
Edit: And i have also been seing people post that after testing they have not found there Eris being any faster than 710 just that higher decreses there battery life. Which is Maybe why kaosfroyo has it alrdy clocked at 710 but i dont know, you cant quote me on that.. I hope i was of some help
does this app work on Streak?
I tried out and nope, it don´t work how it should. It says the Streak is running with 998 Mhz and you can´t overclock it. Waiting for update...
crazy cat said:
I tried out and nope, it don´t work how it should. It says the Streak is running with 998 Mhz and you can´t overclock it. Waiting for update...
Click to expand...
Click to collapse
998Mhz is the limit for the kernel. you need a kernel that can be overclocked for that option....
it works fine. at this moment in time you can not overclock but it auto detects settings just fine and you can set screen off speed/battery low speed to extend your battery life.
crazy cat said:
I tried out and nope, it don´t work how it should. It says the Streak is running with 998 Mhz and you can´t overclock it. Waiting for update...
Click to expand...
Click to collapse
Wait, u know there are three levels of clocking, right? one is under clock, one is clocked and one is over clock. There are two frequencies when u turn on the setcpu, one is max and one is min...but i would like to know if u r able to make the max and min both up to 998mhz so that it can run at full speed at all times
zgmf-x322a said:
Wait, u know there are three levels of clocking, right? one is under clock, one is clocked and one is over clock. There are two frequencies when u turn on the setcpu, one is max and one is min...but i would like to know if u r able to make the max and min both up to 998mhz so that it can run at full speed at all times
Click to expand...
Click to collapse
yes you can bro. both max & min are customizable from 24500Mhz upto 99800Mhz. however, ive found that having the streak running totally max when the screen on will simply drain your battery, there are no real speed improvements to be seen. a good compromise to combat lag would to be to set screen on: 76800 - 99800Mhz.
i completely downscale mine when the screen is off and although the battery life on the streak is good, doing this makes it even better. no lag when switching screen on either (frequency change)
Works great for me too! I don't see any need for overclocking a phone (unless you don't use it as a phone..)
I unplugged mine from the charger about 1.5 hours ago, still 100% battery..
thanks guys for the reply, appreciated it alot!
it does and very well
to get interactive setting you must at least have performance fix and it will let you overclock and add interacting setting i just did perf. fix and setcpu settings and now quadrant score of 1700+
Works great for me. Flash smokku and fard's djsteve kernal perfmod using clockwork or streak mod and then you can overclock using setcpu. Look at my signature line below.
Dell Streak, 2.2 froyo (318), custom kernel, OC to 1.2ghz, quadrant 2002, hspda signal mod,
Hey TB Users....
Was wondering who is rooted and using set CPU?
Also what profile set ups is everyone using and what are the outomes you are seeing.
Another thing i noticed is that the TB is auto set to 1024000 CPU instead of 998000. not sure if that is normal, but hey just my 2 cents.....
Anyway lets hear what everyone is set to
Franzie3 said:
Hey TB Users....
Was wondering who is rooted and using set CPU?
Also what profile set ups is everyone using and what are the outomes you are seeing.
Another thing i noticed is that the TB is auto set to 1024000 CPU instead of 998000. not sure if that is normal, but hey just my 2 cents.....
Anyway lets hear what everyone is set to
Click to expand...
Click to collapse
i think you have to wait for the source code for the kernal to be released and tinkered with to get anything useful from all that...but who knows
Yup. About all you can use it for right now is throttling (which isn't bad... the CPU is plenty fast already). It'll help save battery, at least.
Odinist said:
Yup. About all you can use it for right now is throttling (which isn't bad... the CPU is plenty fast already). It'll help save battery, at least.
Click to expand...
Click to collapse
Agreed. That's all I use it for now.
I have it set to the following:
Screen off = 245 max
Charging = 1024 max
Battery < 10% = 245 max
Battery less than 25% = 768 max
All other istances = 1024 max
It will do for now until we get custom kernels.
SuperFly03 said:
Agreed. That's all I use it for now.
I have it set to the following:
Screen off = 245 max
Charging = 1024 max
Battery < 10% = 245 max
Battery less than 25% = 768 max
All other istances = 1024 max
It will do for now until we get custom kernels.
Click to expand...
Click to collapse
pretty much what I did, minus everything but the screen off
I always set the screen off on my evo 4g to 245 max, and will probably do the same here. Kinda waiting for kernal source code to be released so I can use the smartass governor. I always liked that one.
Franzie3 said:
Hey TB Users....
Was wondering who is rooted and using set CPU?
Also what profile set ups is everyone using and what are the outomes you are seeing.
Another thing i noticed is that the TB is auto set to 1024000 CPU instead of 998000. not sure if that is normal, but hey just my 2 cents.....
Anyway lets hear what everyone is set to
Click to expand...
Click to collapse
I downloaded Quadrant immediately after rooting w/o installing SetCPU & first run pulled off a 1926...second run a 2000 flat! So I installed SetCPU & set it to performance & the most I got was mid 1800's which is what I was pulling off before I rooted.
I remember on my droid playing around with the up threshold & it would speed things up & so I did but still stayed at consistent 1800's. Uninstalled & I'm running 1900's consistent, only hit 2000 once lol.
I cannot wait to tinker once HTC releases the kernel source!
mthorn79 said:
I downloaded Quadrant immediately after rooting w/o installing SetCPU & first run pulled off a 1926...second run a 2000 flat! So I installed SetCPU & set it to performance & the most I got was mid 1800's which is what I was pulling off before I rooted.
I remember on my droid playing around with the up threshold & it would speed things up & so I did but still stayed at consistent 1800's. Uninstalled & I'm running 1900's consistent, only hit 2000 once lol.
Click to expand...
Click to collapse
quadrant scores don't mean everything. If you installed SetCPU and noticed a speed decrease then there would be a reason to not want it, but just because you get a lower score in quadrant?
*EDIT* just thought I'd say, I just ran Quadrant with SetCPU on performance, and got a 1978 score. So I DK what you are talking about.
HTC really needs to release the source code. To my understanding it should be out sooner than later? I sure hope so...
nosympathy said:
quadrant scores don't mean everything. If you installed SetCPU and noticed a speed decrease then there would be a reason to not want it, but just because you get a lower score in quadrant?
*EDIT* just thought I'd say, I just ran Quadrant with SetCPU on performance, and got a 1978 score. So I DK what you are talking about.
Click to expand...
Click to collapse
Ok I'm not an idiot, I know quadrant scores don't mean anything but some people use it as a gauge to get an idea on how their phone is. (If u feel it does nothing for you then don't use it if u don't want to no one asked you to)
If you know anything about phones you know certain people's will vary in speeds, I'm just posting my experience...this IS afterall a "Post Your SetCPU Settings' thread, so don't be getting all uppity.
Sent from my ADR6400L using Tapatalk
Jimmy058910 said:
HTC really needs to release the source code. To my understanding it should be out sooner than later? I sure hope so...
Click to expand...
Click to collapse
Yes. I think they releases it within 45 days or something like that. It will most certainly be here soon.
Sent from my ADR6400L using Tapatalk
Any incoming call issues with Screen Off set at 245?
Steeler86 said:
Any incoming call issues with Screen Off set at 245?
Click to expand...
Click to collapse
no and their shouldn't be, unless you down the road, since you couldn't do it now, use one of the governors like Conservative which tend to really slow the phone down. On my Evo 4G it used to take a good 30 seconds to unlock the screen is I used that with screen off at 245Mhz.
1570 for me on stock rom.
I got 2000+ quadrants on stock ROM. SA for setCPU, I can't get my CPU to clock down by force with any app. I think the kernel source is going to be needed. Probably have perflock on like they did on my inc. Let me know if setCPU works please.
SetCPU works, you just have to hit the menu button and click "disable perflock"
1376 on VirusRom but it is soooo snapppy
Seems to be working for me. 39% battery after 12+ hours. Just with the "screen off: max245" setting.
Sent from my ADR6400L using XDA App
We finally got the source code!
Do I need to flash this to overclock
http://forum.xda-developers.com/showthread.php?t=1016916
or can I wait for SetCPU to update?
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