Hi!
While playing around with my hero more and more I've been experimenting with different roms, kernels and cpu clock speeds. While doing that I've been trying to keep below 710MHz, but after a while i thought "what the hell..." and kept it at 710MHz for a long time. At 710MHz my hero seems to work fine, a little faster then it used to be, and a little more battery consuming. My noob question is since most of the post in here says " be careful going all the way up to 710MHz" almost no one suggest trying anything above, am I doing something wrong? Is the increased performance and the decreased battery life all in my head? I'm using setcpu 2.24, been tested on most roms here, both flykernel 12 and 13 and LV 5.0 and LX 6.2 ++++, and of course i always give it SU.
also, if i'm doing this right, my phone does not get particularly hot at 710MHz, so could i go even higher?
There are differences in devices. Mine for example freezes totally at 710.
I have been using my overclocked hero for a year now, running at 730mhz with no problems, my maximum is 748mhz but approximately after 20 minutes of runing at so high freq the hero was doing really some weird things..730mhz is my ok freq where I can run it without freezing up or any errors, the back cover gets little hot only when doing hards tasks..oh and, dont enable auto apply overclock on boot when testing the highest overclock, did that you dont want to be there when hero freezes up I just pulled out the battery...
I can overcloking my Hero with no problem upto 748.8mHz. If i use 760mHz my Hero are freeze...
Overclocked to 729, it works fine but eats battery like anything. Speeds above 614 are too much for our Heros poor battery.
I'm overclocking to 691, cause it freezes at 710.
If the cpu is really running at 691 for a while it goes upto 40°C. Just use a temperature profile in setcpu.
691 Mhz - 176 Mhz too, moderately stable.
Mine is stable up to 729 MHz
Mine freezes at 710MHz. For everyday use i have 614/352 Screen On settings
172-691Mhz Smartass is good idea. My hero is freeze at 729Mhz.
I am not that aggressive, 352 - 633 MHz. So far very stable.
690 is optimal for me, it does not freeze at 710 but it becames slower if I do a benchmark.
264-633 smartassv2 works perfectly for me. I found at 710 it was a little faster/smoother, but my battery lasted less than a day - using gps at 710 would also cause my phone to reboot.
Mine works till 691, at 710 freezes after few minutes.
Related
I suppose that this is a well known fact, but anyway: the StrTrk can be overclocked just like the HTC Wizard (with omapclock).
I'm running mine now at stable 240MHz (instead of 180).
Makes quite a difference.
Cheers
hrb
It will revert back to 180Mhz after you close the phone after a few minutes.
Has anyone figured out how to make the changes stick
is overclocking too risky for a smartphone? does cpu burn or just freeze when overclocked to its limit?
I'm using 252mhz when playing 3D games (no java, they are working nice at 180 mhz anyway) then down to 180mhz.
thx
Im using my startrek with WM6.1 Pro with the battery status plugin now Homescreen ++. I have it underclocking to 143mhz 180mhz is nominal 260 is my high setpoint and 273 is my temporary boost. Its dynamic based on cpu load. Works like a champ get about 3 days charge with my extended battery. Dont know about stock battery time. Besides the phone getting a little warm its fine to overclock. Just make sure its stable at whatever speed you set it at. It will lock up immediately if its not stable 240-252 is safe and stable for most on this phone for continuous use. When underclocking you may notice scale lines appearing on the screen like it has a reduced refresh rate.
My3125 also can keep @252mhz...
haha
Hi guys!For the last few days(that I have my Hero rooted that is) I'm using VillainRom 10 as my everyday ROM and have tried some others.Anyway,that's not the point!
Being one of the lucky ones whose Hero can happily overclock to 768 I came to use RaduG's extremekernel and ben39's no-bfs no-whining kernel.With the second,while configuring OverclockWidget I saw that it gives a 848MHz option with auto-detect frequencies.Is it possible?I'm not asking about stable daily use,but even for some minutes for benchmarking?Has anyone achieved it?Without making their phone catch on fire that is!
And secondly,why are we all using linux 2.6.29(for total newbies I mean the kernel) while there is 2.6.32-33-34?Can't a newer kernel be compiled for use with the Hero?Newer kernels would provide native ext4 support and would probably prove to be better overall.
Oh,forgot one more!I am currently running on minimum 176MHz-maximum 749MHz(after I got a couple reboots with 768 I abandoned 19MHz for stability) with screen on and minimum 123MHz-maximum 384MHz with screen off.Should I give it a higher minimum frequency?Sometimes it lags when waking up,the screen turns on but shows nothing but black and turns off again or it turns on and everything is distorted,colors are completely distorted,background is upside down and some other unnormal things,but everything is alright when turning the screen off and back on again.Does it have to do anything with the frequencies I am using?I am running on VillainRom 10.3.
Now I have set the minimums to 160 and 190 MHz to see what happens!
Thanks in advance!
About the high MHz... I have done it with over 800 but don't max it out at 848 or your phone will freeze but anything below works And that screen **** I've also had and it has something to do with the high MHz (don't know why) but it helped me to set the MHz lower when the phone sleeps in SetCPU And at last about the kernel... It runs on the old one on Android 2.1 but in 2.2 it will be upgraded to ....33 or ....32 don't remember which...
-------------------------------------
Sent via the XDA Tapatalk App
Thanks for your reply C0mpu13rFr34k!
I know Eclair is running on the old kernel.I just would like to know if it is possible to compile a newer kernel for it.
As for the frequencies...Are my settings alright?Some too high or too low?The way I see it there is a big gap between maximum and minimum frequencies when screen on which results on the CPU working at low frequencies most of the time,thus sacrificing performance.But it helps with battery life and presumably this and the screen-off underclocking reduce the overall damage caused to the CPU by the overclocking,which is said to reduce the CPU's total lifetime by 50% or more,depending on how much you overclock it.Working at 749 I sometimes get a nice 43 degrees Celsius while charging,but that's only when charging.Average temperatures are 30 for standby and 37 with screen on(average,can be lower or higher).
And one more question.At 800+ how hot does it get?Will it be stable for some minutes to do some basic benchmarking or nah..?
Thanks!
tolis626 said:
Thanks for your reply C0mpu13rFr34k!
I know Eclair is running on the old kernel.I just would like to know if it is possible to compile a newer kernel for it.
As for the frequencies...Are my settings alright?Some too high or too low?The way I see it there is a big gap between maximum and minimum frequencies when screen on which results on the CPU working at low frequencies most of the time,thus sacrificing performance.But it helps with battery life and presumably this and the screen-off underclocking reduce the overall damage caused to the CPU by the overclocking,which is said to reduce the CPU's total lifetime by 50% or more,depending on how much you overclock it.Working at 749 I sometimes get a nice 43 degrees Celsius while charging,but that's only when charging.Average temperatures are 30 for standby and 37 with screen on(average,can be lower or higher).
And one more question.At 800+ how hot does it get?Will it be stable for some minutes to do some basic benchmarking or nah..?
Thanks!
Click to expand...
Click to collapse
If your phone is stable your settings are just fine even though your phone might have problems waking up if the low freq is under 246MHz (something like that) Also if you want better performance you might want to test some other freqs and then benchmark... Sometimes it makes a BIG difference if your phone is running at 691MHz or 710MHz For me my phone works like **** if it runs at 749MHz but it works like a dream at 729MHz (I think the difference was 0.5-0.8MFLOPS) Im also pretty sure your temp is fine (OC shouldn't make your phone that much hotter since the voltages in all ROMs are adjustet). If you should compile a newer kernel you would first of all need a .32 (.33?) from HTC because of hardware capabilities and im sure there's is A LOT more things devs need to compile such a kernel but i don't know to much about kernels I don't really know that much about 800+ because I only did it once and benchmarked it (MFLOPS was **** and i couldn't get them high at all) actually it slowed down my phone but you should test it. Maybe your very lucky and your phone can take it
Well,I have set it to 653min-749max with screen on and 160min-352max with screen off.Testing only!But it runs like a dream if we don't take into account a small lagging when I turn the screen on and it has to change frequencies!But it's great so far.Will see how battery life goes!By the way,tried 800,806 and 848MHz,but none worked.It didn't crash or something,it just wouldn't change to it and stayed at lower frequencies(low as 246).
Thanks for your time anyway!
And a small question...How bad does overclocking affect the CPU's life?I asked around and was told that the maximum overclock for desktop PCs is 20-25%,depending on the CPU,while needing special cooling systems,and that it can reduce the CPU's life up to 50%.Given that we overclock over 40%,how bad do we damage our CPUs?
tolis626 said:
Well,I have set it to 653min-749max with screen on and 160min-352max with screen off.Testing only!But it runs like a dream if we don't take into account a small lagging when I turn the screen on and it has to change frequencies!But it's great so far.Will see how battery life goes!By the way,tried 800,806 and 848MHz,but none worked.It didn't crash or something,it just wouldn't change to it and stayed at lower frequencies(low as 246).
Thanks for your time anyway!
And a small question...How bad does overclocking affect the CPU's life?I asked around and was told that the maximum overclock for desktop PCs is 20-25%,depending on the CPU,while needing special cooling systems,and that it can reduce the CPU's life up to 50%.Given that we overclock over 40%,how bad do we damage our CPUs?
Click to expand...
Click to collapse
I haven't heard to much about that actually but from what I've heard it shouldn't damage the CPU at all because of the voltage adjustments but i find that very hard to believe... Talking from personal experience my phone runs as smooth now as it did when i bought it so my CPU has probably taken minamal- or no damage at all and I got it when it had just come out here in Denmark (Europe) which is about 8+ months i think? So I wouldn't care to much about the lifetime since It's probably like 1-2 years and by that time I don't think people are using the Hero anymore Keep up the good work with optimizing and your welcome
I just wanted to know what everyones eris is oc to. I am currently overlocked at 806mhz, i cant go any higher than that.
Mines at 768 anything over that it overheats
mines at 768. I can go up to 806 if I wanted to but it sometimes causes issues so its better to stay at 768 to be safe at least for my eris and my fiances as well.
ive seen some ppl overclocked to 825mhz fine
3.5 Ghz
ten chars
wow thats some eris you got there
mine is very stable at 787, it can go to 806 but s**t starts to force close. I use cpuboost on smartass governor with minimum 787 maximum 787 with no sleep profile and surprisingly it doesnt get hot or get horrible battery life and im on it pretty much all day (except when im with my chick she will throw my phone out the window) lol
710. I haven't even tried going higher, my battery's reached 105-110F just at 710 (yeah I know just the battery, but still) so I'm too worried to try anything higher.
710 does me well.
On both my old and new Eris, I can go up to 806 but I set the max at 768.
Mine shutters and self destructs if I set it higher than 710
Edit: just for giggles I tried again. As soon as I touched 787 it restarted and would not restart till I flashed it again. ;-) oh well. I have liked this phone but can't wait till the Thunderbolt launches.
Sent from my Eris using XDA App
two eris at 768 no issues here...
linpack average of 5.178 on Koas gingerbread V8 rom
Downloads 860kbit/s and upload 1740kbit/s Max after enabling autokiller
Radio 2.42.02.10.29 See http://forum.xda-developers.com/showthread.php?p=10748354&posted=1#post10748354
768 max is the highest it will go. Used to run it at 710 though recently I have found it is much happier at 768 on Smartass.
Autokiller: Ultimate
Linpack: 5.30 is the norm on Froyshedyo 10 w/ cfs v9
It ran about as smooth when I started running KaosFroyo back at about V34 at 710 max, though with Kaos busy with Gingerbread I hopped to a different rom until GB is a little more operational.
It does get a tad warm, though nothing I would fret about.
I just stick to 710-245 smartass
806 with colin's battery tweak.
CCCP4ever said:
I just stick to 710-245 smartass
Click to expand...
Click to collapse
Word.
There was a fellow over on Androidforums.com that liked the way his Eris ran at 806. That phone was dead within one week of his commencement of overclocking. (He may have set min=max, rather than mess with governors, I don't know all of the details).
When electronics break down, they do so for two reasons:
(1) intrinsic chemical processes such as corrosion, electromigration, whisker formation, etc. - these are all accelerated by heat.
(2) mechanical ruptures caused by prolonged mechanical strain or thermal cycling - both caused by heat.
In both cases, heat is the principal enemy.
Your Eris has no fan inside - just sayin.
While we're at it, have a look at the VDD_6 versus VDD_7 supply voltage definitions in this kernel code
If the voltage ramping is the same as in the note in the code (see "MSM7201A") a processor supply step-up occurs in the frequency table like this:
F >= 787 --> Vdd = 1.325 V
120 <= F <= 767 --> Vdd = 1.2V
Because the power dissipation per clock is proportional to Vdd^2, and the power rate is proportional to the clock frequency, the expected power dissipation ratio of 806 versus 710 is
(806/710)*(1.325/1.2)^2 = 1.384
You are burning up nearly 40% more power at 806 than at 710 - for a performance benefit of only (806/710) = 1.135 .... 14%
bftb0
bftb0 said:
Word.
There was a fellow over on Androidforums.com that liked the way his Eris ran at 806. That phone was dead within one week of his commencement of overclocking. (He may have set min=max, rather than mess with governors, I don't know all of the details).
When electronics break down, they do so for two reasons:
(1) intrinsic chemical processes such as corrosion, electromigration, whisker formation, etc. - these are all accelerated by heat.
(2) mechanical ruptures caused by prolonged mechanical strain or thermal cycling - both caused by heat.
In both cases, heat is the principal enemy.
Your Eris has no fan inside - just sayin.
While we're at it, have a look at the VDD_6 versus VDD_7 supply voltage definitions in this kernel code
If the voltage ramping is the same as in the note in the code (see "MSM7201A") a processor supply step-up occurs in the frequency table like this:
F >= 787 --> Vdd = 1.325 V
120 <= F <= 767 --> Vdd = 1.2V
Because the power dissipation per clock is proportional to Vdd^2, and the power rate is proportional to the clock frequency, the expected power dissipation ratio of 806 versus 710 is
(806/710)*(1.325/1.2)^2 = 1.384
You are burning up nearly 40% more power at 806 than at 710 - for a performance benefit of only (806/710) = 1.135 .... 14%
bftb0
Click to expand...
Click to collapse
bftb, I don't think I've ever seen you post something that I haven't learned something from. Very interesting to see how little you gain going up to 806.
I usually stick around 710 too, but I bump up the min to 480 cause at 245 my phone takes too long to wake up when I get a call.
I decided to set my max at 528 today just for kicks, and I was surprised to see that it actually still felt kinda snappy. Not quite as smooth as with 710, but definitely usable for me.
first of all I dont feel 14% is a small amount when pushing the envelope as we are trying to do with the eris. In any hobby I've been in people go thru great lengths and spend all kinds of money and time for 10% improvements much less 14%. Actually more than I expected and makes me feel alot better about going from stock 528 to 768.
Now having made that argument I'm going to turn around and rubuke myself because even if there is an actual verifiable 30%+ improvement going from 528 to 786 it means nothing to me if I cant feel any difference in the contexts of a phone and I just cant tell much difference. Its not like a car in which it may feel the same to you but you win a race you would have lost before. With a phone subjective improvements experienced by the user is all that really matters. Many a time I've flashed, forgot to set OC and later THOUGHT I was overclocked or overclocked higher only to realize I've been using the phone without doing so. Never ONCE has it been because I thought "man this is slow, maybe I forgot to overclock". Always the other way: "man I thought this thing was overclocked and I'm running stock speeds". that alone tells me what I need to know about overclocking (yet I overclock to my phones stable max of 768 anyway. go figure).
i keep it at 710/245. its not a noticeable difference to me when i clock it above 710. however, when i put it back down to 528 it is noticeably more sluggish (the only exception to this being KGB or vanilla 2.1).
710 here. I can go up to 767 with a certain set up...
I seem to have one of the weaker Eris'. But 710 is fine for me!
Am on Froshedyo Vanilla + Green minimal theme and was wondering does the min CPU of 245mhz and 19mhz eat up the amount of battery? Do they run the same voltage? Any of you guys see a difference as far battery life running 19? I know it makes the phone take a little longer to wake up when a call is coming in. Thoughts?
Currently I have it 528/245 Smartass with a charging profile
I always had problems with lag when I clocked down to 19. I never really felt that it provided any extra battery life, but others feel that it does.
+1 on the lag. We run 245 and its smooth.
Sent from my FroyoEris using Tapatalk
+1
There have been occasions, possibly the particular combination of ROM, the apps installed, and what app or method I'm using to overclock which have resulted in 19 working fine sometimes, but most of the time at least 160 or 210 (?) would be a necessary happy medium so that waking the screen or answering calls wouldn't be downright excruciating, so my short answer is yes, at least 210 or 245. I forget and am too lazy to look if 210 was an option, and I'm tired. LOL.
FroShedYo runs Conap's CFS kernel, and, IIRC, it was made quite clear in that thread that the kernel runs best at a minimum of 245 MHz.
I'll say this - last month I spent a lot of time going back and forth between xtrSENSE and xtrROM, both running at 604.8 max and as low as 19.2 min (I tried all steps from 245 down to 19.2), and CELB, running at 710 max and 245 min, and I get much better battery life with CELB. In fact, with xtrROM I had to set some of my update times for apps that I use to longer intervals just to get through the end of the day with 20% battery life left. With CELB I never finish the day with less than 40%, and it's often over 50%.
It may be different for you, but that's what happens on my phone.
I use 19.2.
122 and 19.2 both use the same voltage though I believe. I only use 19.2 because it keeps the average down.
I listen to pandora with 19.2 min 480max smartass with no lag.
I'm running subpsyke's CM7 port on my u8160, and have overclocked the CPU to 691mhz using the the smartass governor. The processor runs at 600 by default. Any higher than 691 and it immediately locks and restarts. At this speed it doesn't reset any more often than at default, something this phone did every couple of days even before I flashed the ROM, and it never locks up.
So my question is: at what battery temperature should I start getting worried? During browsing it gets up to around 25 to 28C, but when plugged in and being used I've seen it at 36C occasionally. I have a feeling that's pretty high.
Watchtower isn't showing me any processes eating up runtime erroneously either.
I'd really like to keep the higher speed, it's just enough to view higher quality video on this toy.
EDIT: The battery temp sensor is the only thermometer on board, I think. AndroSensor picks up another one but its forever 'waiting for event' so I don't think it's really there.