Related
Is it possible to overclock the HTC Hero's processor to past 528 mhZ? I've heard that it is slightly sluggish and i thought if it is possible, then this might solve the issue
First of all, its sluggish, when many applications an widgets run at the same time, thats ok for a MOBILE PHONE, Mobile phones do not have to be multitasking pros.
But yeah, i asked this myself too yesterday and googled about that, but found no real answer.
So, if theres a way to overclock the Magic's or Dream's CPU it should also be possible for the HERO! MY Hero in a few days in germany
the processor maxes out a 528
if u get it past that ur just damaging it...
just like overclocking a computer
the higher u go the more cooler power u need
mobile phones are not cooling geniuses lol
That doesnt exclude the possibility to overclock a mobile cpu, many people overclocked their HTC Herald CPU, like me from 198MHZ to 250MHZ, and it was perfekt.
Rotkaeqpchen said:
That doesnt exclude the possibility to overclock a mobile cpu, many people overclocked their HTC Herald CPU, like me from 198MHZ to 250MHZ, and it was perfekt.
Click to expand...
Click to collapse
But if I remember correctly, just like the Dream/Magic, the Hero CPU runs the same MSM7200a proc. as the Dream/Magic which maxes out at 528Mhz. However, HTC has, for whatever the reason, underclocked them. It runs at 328Mhz max typically on the Dream (& i'm assuming this is the same on Magic).
We Dream/Magic users aren't really overclocking the CPU as much as just clocking it. I forget the exact parameter but in the beginning we just used a terminal command to set the cpu_scaling_freq (or something like that) to the max 528Mhz. Once root is gained on the Hero this should be easily accomplished there from the terminal or an app as well.
Rotkaeqpchen said:
That doesnt exclude the possibility to overclock a mobile cpu, many people overclocked their HTC Herald CPU, like me from 198MHZ to 250MHZ, and it was perfekt.
Click to expand...
Click to collapse
The Herald just as my old Hermes ran OMAP processors, pretty easily tweaked.
No one has as of yet discovered a way to overclock a Qualcomm , and they have been round a good year or 2 now.
p.s.. Processors dont max out as such, they just overheat and burn!!!
Fact is, that before trying to do stuff like this you first need to gain root on the Hero.
And indeed like said before: The G1/Magic _underclock_ their CPU to save battery. Only in a few situations will it do it's job at 528mhz, otherwise it's 320-something mhz.
So when a G1/Magic user is telling they 'overclocked' their CPU, they just removed the underclock and it's running at the normal 528mhz for the MS7200.
Really _over_clocking it, by running it at like 650mhz or higher, I didn't see before.
PS: The slugginess is more a RAM and disk i/o thing than directly cpu-related.
thanks for all the info guys. so should i be worried about getting the phone, or do u think it won't be that bad?
No you shouldnt, i am waiting too for my hero to arrive. So can anyone tell, what it means to "root" android? why should i root my hero when i have it and what does it affect? thanks in advice.
Rotkaeqpchen said:
So can anyone tell, what it means to "root" android? why should i root my hero when i have it and what does it affect? thanks in advice.
Click to expand...
Click to collapse
you become a superuser with more privileges and total control.
Thank you, now i understand. So how can we set the clockspeed to 528mhz permanentely?
Rotkaeqpchen said:
Thank you, now i understand. So how can we set the clockspeed to 528mhz permanentely?
Click to expand...
Click to collapse
First off, we don't know if it's even needed. Maybe it's running on 528mhz already.
Second: You can't. Until the Hero is rooted nothing like this is possible, so getting 'root' access if first step in ANY kind of tweaking.
Ok, thanks. so lets wait till we hold our heroes in our hands to see at what speed it runs and hopefully be able to root the phone.
Have been using my Hero for a few days now - and don't really notice any speed issues that concern me.
Seconded.
I have a Hero and have for a couple of days on Orange, and have no qualms about the speed whatsoever.
HTC say the processor dynamically clocks up to the maximum 528MHz when needed, so unless you want to push it out of spec (if its even possible) - there's no need to set the clock. Leave it be
thats sounds reasuring, thank u for letting me know
to be honest i just bought mine yesterday
and its not terribly slow
ive read bout it and be careful we are talking bout reviewers and most review websites dont know a lot bout half of what the say
slow no
unresponsive no
a bit laggy yes
this phone is brilliant
and is quite speedy considering how much things you got on desktop
for anyone worried about the slow speed of the Hero, the firmware update fixes this. its soooooooooo much faster.
Bump, what spped is hero running on? I have mcr 3.1 installed and since we have root now............
AFAIK, the Hero runs at 528MHz when in use, but underclocks to ~300 when not in use (ie. screen off etc.) Really, in MCR3.1, you shouldn't be needing to overclock- it really flies. If not, did you do a wipe before install?
If not, I strongly recommend you do (back up data first!), as it made mine a lot faster and was worth the hassle!
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've run my E3D stock at 1.2 Ghz and I've run it overclocked under temp root at 1.7 Ghz. Sure my benchmarks are higher @ 1.7, but as a practical matter, do I notice the phone working any faster?
Not really.
It is like driving 150 vs 120. 150 is faster but does it really seem that much faster? (I've driven both speeds and I can tell you it doesn't). At some point our phones are "fast enough" for the software we throw at them. Now I admit I'm not a phone gamer so I cannot comment on the effect of overclocking on games, but just day-to-day desktop stuff, nah, no difference as far as I can tell.
Add to this that it is likely that additional speed is chewing through more battery faster and it hardly seems worth it. Without upping the voltage, your phone will likely be more unstable overclocked and with more voltage will likely have a shorter life or get cooked altogether.
For me, I'll probably just leave the speed stock.
I'm not saying I am "right" about this. Just my opinion at this point in time. YMMV.
Thoughts?
This is agreed up to a point. Sooner or later they will be creating apps and OS' that will truly utilize the full dual cores potential within the phone. I personally believe that up until that point the OP is 100% right on. But once this does happen, these apps will become more and more processor heavy. And once that happens, I believe we'll be back in the same boat as before and 1.2 vs. 1.7 will actually make a bit of a difference to the typical end user (and not just by benchmark enthusiasts).
The only reason I believe this to be true is look at how PCs and laptops evolved. We got dual core processors and apps weren't quite using the full potential, then as time went on and programmers started utilizing the full processing capabilities of dual/quad cores (& as these processors became more and more common) the differences began to matter again. That's just my 2 cents & I could be completely wrong, but just wanted to share my thoughts. Good topic though
Sent from my badass HTC EVO 3D... Get in our dimension!
mitchellvii said:
I've run my E3D stock at 1.2 Ghz and I've run it overclocked under temp root at 1.7 Ghz. Sure my benchmarks are higher @ 1.7, but as a practical matter, do I notice the phone working any faster?
Not really.
It is like driving 150 vs 120. 150 is faster but does it really seem that much faster? (I've driven both speeds and I can tell you it doesn't). At some point our phones are "fast enough" for the software we throw at them. Now I admit I'm not a phone gamer so I cannot comment on the effect of overclocking on games, but just day-to-day desktop stuff, nah, no difference as far as I can tell.
Add to this that it is likely that additional speed is chewing through more battery faster and it hardly seems worth it. Without upping the voltage, your phone will likely be more unstable overclocked and with more voltage will likely have a shorter life or get cooked altogether.
For me, I'll probably just leave the speed stock.
I'm not saying I am "right" about this. Just my opinion at this point in time. YMMV.
Thoughts?
* UPDATE *
Ooops!
Thought I was putting this in the Q & A section. My bad. Mods please move this.
Everyone else please don't flame me - just goofed
Click to expand...
Click to collapse
lol i did this once gotta love having multiple tabs and think you clicked on the right one ya? least thats what happend to me when i did it
I agree with you. Even in the games i play there is almost no difference, except that the battery gets drained faster because of the higher voltage.
P.s. wrong section, rable, rable, rable
I kinda agree with you in the matter of it not making a HUGE difference. But when I'm overclocked to 1.7, I do notice that it seems to scroll smoother. But that's the only difference I can see.
Sent from my PG86100 using XDA Premium App
I'm comin from a heroc running 768 so 1.2g MORE than enough for me. Besides any faster an yer batterys gonna last w couple hours.
Sent from 3D A.W.E.S.O.M-O
Hi Mitch! You're right, no real need for OC.
From a SuperCharged Evo4g!!!
motoelliot said:
I'm comin from a heroc running 768 so 1.2g MORE than enough for me. Besides any faster an yer batterys gonna last w couple hours.
Sent from 3D A.W.E.S.O.M-O
Click to expand...
Click to collapse
This would be my philosophy. A 1.2 GHz Dual Core is absolutely insane compared to what us Hero users used to have to deal with. My phone couldn't even handle 768, it was stable at 691.
LiquidSolstice said:
This would be my philosophy. A 1.2 GHz Dual Core is absolutely insane compared to what us Hero users used to have to deal with. My phone couldn't even handle 768, it was stable at 691.
Click to expand...
Click to collapse
Yeah... My poor heros still mad at me.
Sent from 3D A.W.E.S.O.M-O
I have my 3D oc'ed to 1.5 and ever so slightly undervolt to 1175000 (too many zeroes?)
Totally stable for me. Battery doesn't seem effected much.
Of course I haven't done heavy gaming yet. So. I dunno. I'm still in the honeymoon phase of just being Able to overclock, ya know. Lol.
Sent from my PG86100 using Tapatalk
Delete post
felacio said:
I have my 3D oc'ed to 1.5 and ever so slightly undervolt to 1175000 (too many zeroes?)
Totally stable for me. Battery doesn't seem effected much.
Of course I haven't done heavy gaming yet. So. I dunno. I'm still in the honeymoon phase of just being Able to overclock, ya know. Lol.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
I dont know what the stock voltage is, but wouldnt this essentially balance out the extra battery draw from running a slightly higher clock?
Faster, Stronger .. make it so.
Sent from my PG86100 using Tapatalk
I've overclocked mine a few days, now I'm at stock 1.2 almost no difference. Running the script for overclock is nice though because it allows the use of apps like setcpu. That way profiles can be set for temperature and battery charge level.
As for overclocking because its awesome fast... No need, sweet the way it is.
mitchellvii said:
I've run my E3D stock at 1.2 Ghz and I've run it overclocked under temp root at 1.7 Ghz. Sure my benchmarks are higher @ 1.7, but as a practical matter, do I notice the phone working any faster?
Not really.
It is like driving 150 vs 120. 150 is faster but does it really seem that much faster? (I've driven both speeds and I can tell you it doesn't). At some point our phones are "fast enough" for the software we throw at them. Now I admit I'm not a phone gamer so I cannot comment on the effect of overclocking on games, but just day-to-day desktop stuff, nah, no difference as far as I can tell.
Add to this that it is likely that additional speed is chewing through more battery faster and it hardly seems worth it. Without upping the voltage, your phone will likely be more unstable overclocked and with more voltage will likely have a shorter life or get cooked altogether.
For me, I'll probably just leave the speed stock.
I'm not saying I am "right" about this. Just my opinion at this point in time. YMMV.
Thoughts?
* UPDATE *
Ooops!
Thought I was putting this in the Q & A section. My bad. Mods please move this.
Everyone else please don't flame me - just goofed
Click to expand...
Click to collapse
I agree. It doesn't feel much if any faster and is probably needlessly using excess battey.
On the otherhand, I find there to be a pretty big difference between driving 120, 150, or even 170 mph.
mitchellvii said:
I've run my E3D stock at 1.2 Ghz and I've run it overclocked under temp root at 1.7 Ghz. Sure my benchmarks are higher @ 1.7, but as a practical matter, do I notice the phone working any faster?
Not really.
It is like driving 150 vs 120. 150 is faster but does it really seem that much faster? (I've driven both speeds and I can tell you it doesn't). At some point our phones are "fast enough" for the software we throw at them. Now I admit I'm not a phone gamer so I cannot comment on the effect of overclocking on games, but just day-to-day desktop stuff, nah, no difference as far as I can tell.
Add to this that it is likely that additional speed is chewing through more battery faster and it hardly seems worth it. Without upping the voltage, your phone will likely be more unstable overclocked and with more voltage will likely have a shorter life or get cooked altogether.
For me, I'll probably just leave the speed stock.
I'm not saying I am "right" about this. Just my opinion at this point in time. YMMV.
Thoughts?
* UPDATE *
Ooops!
Thought I was putting this in the Q & A section. My bad. Mods please move this.
Everyone else please don't flame me - just goofed
Click to expand...
Click to collapse
I overclock because it makes my friends with lame iPhones jealous.
bavman said:
I agree with you. Even in the games i play there is almost no difference, except that the battery gets drained faster because of the higher voltage.
P.s. wrong section, rable, rable, rable
Click to expand...
Click to collapse
You goto KU?
Nice internet speeds, dorm/campus internet sucked when I was there
Once there's permanent root and htc releases the kernel source, will our phones be able to be over clocked higher then 1.7?
Sent from my PG86100 using Tapatalk
braggin' rights
Buff McBigstuff said:
I overclock because it makes my friends with lame iPhones jealous.
Click to expand...
Click to collapse
+1
10Characters
So I installed SetCPU today. Been testing the kernels ability to work underclocked at the max of 918mhz. Also set the scaling to conservative. After a days use it's been as good as normal full speed, 1512mhz
The battery lasted throughout the day, compared to my first two days of stock settings with only 6 hours of good use.
I'll keep playing. Still want to do some testing and benchmarks to make sure it's not under performing. But at least at the user level it seems to react the same.no lag.
I did confirm the clock speed out side of SetCPU using system panel.
Sent from my rezound.
Don't bother using benchmarks to rate a phones performance that is a fatal error there. Benchmarks never effectively rate a phones performance. I just go by how smooth the phone runs and it does it run everything I throw at it. If so gg pz end of story.
zetsumeikuro said:
Don't bother using benchmarks to rate a phones performance that is a fatal error there. Benchmarks never effectively rate a phones performance. I just go by how smooth the phone runs and it does it run everything I throw at it. If so gg pz end of story.
Click to expand...
Click to collapse
True, but people still like to get the general idea. There are many factors.hence why I said the over all feel seems the same. Im going to use antutu, and quadrant. 5 times each to get a range.=-)
Sent from my rezound.
Izeltokatl said:
True, but people still like to get the general idea. There are many factors.hence why I said the over all feel seems the same. Im going to use antutu, and quadrant. 5 times each to get a range.=-)
Sent from my rezound.
Click to expand...
Click to collapse
Well whatever works for you. Just saying Quadrant is a poor tool to use to bench for many reasons which I won't go over. Antutu is nice for SD speed testing I think, oter than that meh. Benches are just for numbers for people to flex their epeens with. They just really don't truly gauge a devices performance.
zetsumeikuro said:
Well whatever works for you. Just saying Quadrant is a poor tool to use to bench for many reasons which I won't go over. Antutu is nice for SD speed testing I think, oter than that meh. Benches are just for numbers for people to flex their epeens with. They just really don't truly gauge a devices performance.
Click to expand...
Click to collapse
Benchmarks do have a some good uses... while comparing different phone models with benchmarks can be iffy, it can give an overall insight, (things like graphics capabilities with very GPU extensive games) but in the end user experience and daily use are the real judges.
Where benchmarks can be of the most use, is when comparing changes to the same phone model.
E.G. Comparing performance impacts of AOSP vs Sense, overclocking and under-clocking, and de-sensing/bloat removal.
When used for these reasons, you can get a really good feel for how changes are affecting your device overall. Even then, benchmarks are not the be all end all, and user experience is still important. As you may introduce lag or other performance issues that do not show up in benchmarks.
Which temp root method are you using? Mine isn't staying rooted long enough for me to justify using setCPU at all...
The new version and the one that comes with the newest clean tool stays until reboot.
Marine6680 said:
The new version and the one that comes with the newest clean tool stays until reboot.
Click to expand...
Click to collapse
Thx for the info, guess I must still be using the outdated method. I'll run the latest version of Scott's Clean tool and give it a shot.
Izeltokatl said:
So I installed SetCPU today. Been testing the kernels ability to work underclocked at the max of 918mhz. Also set the scaling to conservative. After a days use it's been as good as normal full speed, 1512mhz
The battery lasted throughout the day, compared to my first two days of stock settings with only 6 hours of good use.
I'll keep playing. Still want to do some testing and benchmarks to make sure it's not under performing. But at least at the user level it seems to react the same.no lag.
I did confirm the clock speed out side of SetCPU using system panel.
Sent from my rezound.
Click to expand...
Click to collapse
Please let us know what settings you use that work for you.
I generally stay temprooted unless I'm going to be away from a charger for a bit and need BT (since you can't turn BT back on after temproot). I wouldn't have SetCPU autostart on boot (since it won't ever be able to get root access immediately after boot).
Meanwhile, I also set it to conservative and will see what that accomplishes.
A kernel needs to support setcpu, stock kernels do not. You need to flash a custom kernel, so you need a development phone or s-off.
Sent from my ADR6400L using XDA App
This kernel apparently does work with SetCPU. I've confirmed using other cpu monitoring apps that the clock speed changes are capped.
I own 7 android phones, and have been rooting, overclocking, undervolting each and every single one of them (well one I still cant get rooted). I know when the cpu is under clocked and when it is not. Been doing these tweaks for 4 years now. If you use a tool like System Panel, at stock settings you can see the max cpu around 1500 on our little bad boy. When it peaks out the clock speed is shown. When you under clock it, then check again it won't go beyond the max cpu set in my testing I put a ceiling at 918mhz. System Panel reported full CPU usage (100%) at clock speed 918mhz. Typically with stock kernels, your absolutely right, changes to SetCPU do nothing at all to the real cpu. Which is confirmed, when I reboot and dont have root, if I attempt to use SetCPU and make the changes, System Panel reports 1500mhz (roughly) at full load regardless of what I set it to in SetCPU. If I did this to any of my other phones with stock kernels, you are correct it makes no difference as SystemPanel reports the stock max setting.
No I'm not being mean or aggressive, just saying. =-) And no don't believe me, but test it yourself and confirm or prove me wrong some other way and I admit error. Either way, half the fun is messing with the phone and trying to get it to do things it should not do.
Grnlantern79 said:
A kernel needs to support setcpu, stock kernels do not. You need to flash a custom kernel, so you need a development phone or s-off.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Sent from my rezound.
Izeltokatl said:
No I'm not being mean or aggressive, just saying. =-) And no don't believe me, but test it yourself and confirm or prove me wrong some other way and I admit error. Either way, half the fun is messing with the phone and trying to get it to do things it should not do.
Click to expand...
Click to collapse
Or I would say, "half the fun is messing with the phone and trying to get it to do things it should have always been allowed to do...." Just sayin'.
Are you using the profiles at all? Im interested to know what seems to be working out the best for you.
Izeltokatl said:
True, but people still like to get the general idea. There are many factors.hence why I said the over all feel seems the same. Im going to use antutu, and quadrant. 5 times each to get a range.=-)
Sent from my rezound.
Click to expand...
Click to collapse
In my view, the "benchmarks" would be an OK measurement if you were comparing apples to apples.
I tried running both Linpack and Quadrant on the very recently and dearly departed Incredible right after a fresh reboot and having charged the battery overnight...when the thing should have been at it's freshest.
I got wildly different scores each time I ran it after a reboot...knowing that on both programs the scores would improve the more times you ran the test.
It didn't seem to me that either program was a reliable indicator of what my phone was capable of. I didn't even trust them to tell me whether something I'd done...cleared cache or deleted bloatware...had any real effect.
It simply boils down to how the phone feels. That's not scientific, but it works for me.
douger1957 said:
In my view, the "benchmarks" would be an OK measurement if you were comparing apples to apples.
I tried running both Linpack and Quadrant on the very recently and dearly departed Incredible right after a fresh reboot and having charged the battery overnight...when the thing should have been at it's freshest.
I got wildly different scores each time I ran it after a reboot...knowing that on both programs the scores would improve the more times you ran the test.
It didn't seem to me that either program was a reliable indicator of what my phone was capable of. I didn't even trust them to tell me whether something I'd done...cleared cache or deleted bloatware...had any real effect.
It simply boils down to how the phone feels. That's not scientific, but it works for me.
Click to expand...
Click to collapse
Linpack and Quadrant are not reliable benchmarks. TBH I don't take any of the benchmarks seriously, they are more for entertainment for me. But to each their own right?
Yeah some of the benchmark apps are a bit unreliable to say the least...
If I use one, I try to use ones that Anandtech uses. I trust them to find the better benchmark tools.
Hello I own the Samsung Vibrant for two years now and even though I was a bit reluctant to overclock the phone at first as new phones were coming out in the market and its (Vibrant's) performance deficit was becoming all the more significant (in comparison to newer phones) I "succumbed to the temptation". At first by a little margin (no more than 20% overclock) but eventually -as I was seeing my phone to be capable for it- for even greater ones. There was a time that I was using my phone at 50% over-the-stock clocks.... those were the days
Eventually -it seemed- as if it somehow starting becoming less and less capable holding the clocks so I started lowering my clock thresholds eventually killing the overclock altogether. Mind you the grand total of the time(s) that I had my phone overclocked (up until then) was not that great...
But then ICS came out with all its fancy tools and the "temptation" overcame me again and as if from a miracle I was able to maintain 50% overclocks like the good ole days (1512Mhz to be exact). To be sure -that time around- that that is a stable clock I devised a slew of different test from extensive software decoding, to 3D and CPU rendering. My phone was rock solid. To address the battery issue I bought an extended battery and all was well in "Vibrant-Ville"...
To my dismay though even though my phone seemed rock solid I seemingly starting losing my overclocking capacity (once again) as I migrated into Jelly Bean, so I said to myself "oh no, no, I'm not going through this again, I'd choose a moderate overclock and I'll leave at that". So I disabled Live-OC, custom voltages, hell even deleted NSTools and used the standard 1.2GHz setting, my battery was better, my phone was rock solid once again and thanks to jelly bean my phone was still fast enough...
Two days ago -though- the ghosts of the past reared their ugly head once again, out of the blue my phone lost its stability. Anytime I was trying to do anything remotely complex and it would reboot (BTW I'm using Helly-Bean right now, using the "Smooth" setting, Smartass governor @ 1.2ghz, pretty standard stuff).
I love this phone but I feel it's nearing its death-bed, what's your opinion guys?
I'll prolly remove the oc altogether but I fear it won't be enough, I fear that instability would start encroaching the 1ghz setting as well one of the days and then it would be game over. I want to avoid this fate at all costs, so anything you could recommend I would try, even changing my rom.
Also to those who used overclocks in the long term what was your own experience?
Thanks for your attention
No response(s)?
Sorry for the bump but I take it none of you guys ever have/had any of the problems I'm describing. Hmm, that means that I was unlucky with my piece of hardware it seems... pity :/
More than likely an aging chip is the case. Personally my phone runs smooth at 1GHz, so I don't see the need to unnecessarily overwork the CPU. After reading your original post, one line stuck out to me in particular. You mentioned that you ran the CPU at 150% for a time, and to me that sets off a red flag. Setting the CPU at 1.5GHz is risky and can cause some major wear on the CPU. Not to say I've never overclocked that high, but I usually only set it that high when playing a high graphics game. Even then, 1.5GHz is not recommended if you wish to use your device long-term. Even 1.4GHz is considerably pushing it. Although our devices can handle it, eventually, they're going to tire out. Now some phones may be able to last longer than others, it depends on the amount of iron in the sand used to make the silicon processors or other minuscule things could play a role. Essentially, it's random. No two chips will be exactly identical nor run exactly the same. So in your case, that may be the case. Perhaps your device really is nearing the its end. Considering that your phone was made to last only a few years at stock speeds, you should still be pleased with how long it's lasted. However, it is understandable if you're upset with this. The only thing I can suggest is to not overclock anymore and to try and keep its temperature low. Perhaps try undervolting? But if you want your phone to last, don't overclock (if your phone's processor is already starting to fail at 1.2GHz, when it used to run rock solid at 1.4 or 1.5GHz, then you definitely need to stop overclocking entirely). More than likely you won't hear other Vibrant users discuss similar problems because they've already moved on to new devices, before the long-term effects of high overclocking began to take its toll. But if you do a little research, you'll find other users on other devices having similar problems to what you are having.
Wish you the best in your efforts, and hopefully you'll get a year or two more out of the device... Hopefully someone will come forward with a better recommendation/solution to your problem. Since I pretty much stated what you probably already knew.
I'm not for overclocking, nor have i overclocked my vibrant.
With that being said, i have never had any performance issues, and I'm having difficulty recalling any issues with stability either..
I hope you treat your new phone with more respect..
I'm sure it will live you much longer for it.
Sent from my amazingly stable SGH-T959 using SlimICS