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!
So I've gotten anywhere between 2.5 to 5.1 MFLOPS using various ROMS and have yet to be able to notice something incredibly different.
710...768...806 - What does it matter? What program other than Linpack shows a sizable difference? Sure, maybe things open quicker? What am I missing here?
I read all this about achieving high MFLOPS and OC Kernels yet I still can't achieve smooth game play on 16 bit emulator on my phone with 5 MFLOPS.
MFLOPS mean jack when there is little way to observe the difference.
Carreno43 said:
So I've gotten anywhere between 2.5 to 5.1 MFLOPS using various ROMS and have yet to be able to notice something incredibly different.
710...768...806 - What does it matter? What program other than Linpack shows a sizable difference? Sure, maybe things open quicker? What am I missing here?
I read all this about achieving high MFLOPS and OC Kernels yet I still can't achieve smooth game play on 16 bit emulator on my phone with 5 MFLOPS.
MFLOPS mean jack when there is little way to observe the difference.
Click to expand...
Click to collapse
Linpack MFLOPS - measures the floating point performance of your phone.
710...768...806 - refers to CPU frequencies
increasing the CPU frequency should equate to better general-case performance, including things opening quicker as you mention, but also other types of general snappiness like moving between screens and so forth.
"I read all this about achieving high MFLOPS and OC Kernels yet I still can't achieve smooth game play on 16 bit emulator on my phone with 5 MFLOPS." - This may have less to do with the performance of your phone and more to do with the emulator itself. Emulation is a surprisingly CPU intensive operation, especially if the emulater isn't well written. Rather than looking a ton into overclocking and JIT, etc, maybe you ought to look for a better piece of software.
Yea,
I've tested most emulators. Wish there was an Atari emulator!
Thanks for the response.
Carreno43 said:
Yea,
I've tested most emulators. Wish there was an Atari emulator!
Thanks for the response.
Click to expand...
Click to collapse
I have run roms with 5.1 MFLOPS and now am running a rom that gets 3. I can honestly say I see no difference.
Spencer_Moore said:
I have run roms with 5.1 MFLOPS and now am running a rom that gets 3. I can honestly say I see no difference.
Click to expand...
Click to collapse
I can see a difference... in battery life! Lolz
g00gl3 said:
I can see a difference... in battery life! Lolz
Click to expand...
Click to collapse
Haha Awesome
it looks like to me that everyone is look at the wrong things.
for example:
I am running a Tom that is getting on a average of 4.9 mflops.
I get smoother screen changes....
streaming videos online is so much faster compared to a 3.0 mflop rom. ...
tubetube and other....... websites.
to me everything I do is faster...
I.don't play game on my phone so I don't know how that is.... but everythng else I do is very much faster.
I love high mflop roms...
I have notice about mflops is that it matters about the kernal that u use.
Isn't it true that the MSM7201 in our phones is already overclocked to get to 528mhz as it is? I see a lot of different places saying Qualcomm chips in general are just not worth overclocking... and since our chip is factory overclocked to begin with... just seems like we're pushing the already-pushed here. But the way this board goes crazy for overclocking... it's contradictory. I don't know what to think, cause I've run Linpack myself and gotten ~4.9 with JIT + OC versus ~2.5 without... but I'm with the OP on this one... only difference I'm seeing is my battery draining faster and my phone getting physically hotter.
xatch said:
Isn't it true that the MSM7201 in our phones is already overclocked to get to 528mhz as it is? I see a lot of different places saying Qualcomm chips in general are just not worth overclocking... and since our chip is factory overclocked to begin with... just seems like we're pushing the already-pushed here. But the way this board goes crazy for overclocking... it's contradictory. I don't know what to think, cause I've run Linpack myself and gotten ~4.9 with JIT + OC versus ~2.5 without... but I'm with the OP on this one... only difference I'm seeing is my battery draining faster and my phone getting physically hotter.
Click to expand...
Click to collapse
I have OC and JIT and getting about 5.1 mflops and haven't had worse battery life or a hotter phone. It could be the battery I'm using but meh (got a replacement one that's 2000 mAh) but I got worse battery life on leak 2.1 than with the rom I'm using now that has OC, JIT, LWP, etc. I can go about 8 hours with heavy texting, moderate internet usage and my lwp's running and it only goes to about 65%
so OC and Jit don't make that big of a difference in gameplay?
Sent from my Eris using the XDA mobile application powered by Tapatalk
What the OP and all the respondents are noting is frankly quite typical of what happens when performance tuning focuses on a single benchmark: the results obtained are essentially meaningless for different kinds of activities on the same device.
That's because there's a whole chain of dependencies that are specific to a given task, any number of which could become the rate-limiting factor; and a different task on the device will have a different set of dependencies and therefore different rate-limiting behaviors.
For instance, let's take writing to an SD card as an example: there's really no way that OC'ing will speed that up in a measurable way - because the CPU isn't the rate limiting factor.
That Linpack benchmark measures floating-point performance using a software library (as the Eris has no hardware FP capability). Most of the apps on the phone do very little FP work at all. But, it's not a bad test of CPU speed, because it performs no I/O. It also may not be very memory bandwidth intensive, either (if the problems it works on stays in the uP cache and there are few page faults).
OTOH, a game emulator needs to write to the graphics display (at a minimum) and possibly also do read I/O from flash.
Different task, different results. Sometimes things can be improved by hardware or firmware; sometimes the software itself needs to be improved.
bftb0
im sorry, but could you just answer in plain english
Sent from my Eris using the XDA mobile application powered by Tapatalk
TheSonicEmerald said:
im sorry, but could you just answer in plain english
Sent from my Eris using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
Lima beans bad.
Pork good.
Slow phone bad.
Fast phone good.
bftb0
Thanks for my laugh of the day on that one.
What I'm trying to get at is -
I should be able to play, at the basic level, Sonic or Mario - Without issues.
At the very least
I prefer roms over market games any day (Sonic, Mario, Zelda, DK-Country) and it cripples the phone, at least in my view, that I cannot enjoy the fruits of old games.
Although, I was able to find some old Atari games - which, thankfully, work without stuttering.
hey all, long time reader, first time poster. i have some questions in regards to overclocking your phone. whats the point? Im not trying to find the forum trolls, nor am I knocking the practice, im genuinely curious about the end result.
im a hardcore PC junkie, so im very familiar with the process, hell my desktop is currently overclocked by a 1ghz (AMD 965 BE @ 4.2ghz).
i have the HTC Evo 3d, best phone ive ever owned, and at first the idea of overclocking it was very interesting, but as i thought about it, the more it didnt make any sence. the phone already get warm when you start pushing it, especially when gaming, i can only imagine how hot it must get when you start upping the voltage to squeeze a extra couple hundred mhz out of it. also how much of a performance increase would you notice? the phone already, runs like butter in my opinion, i cant imagine a extra 100-200mhz would be noticable at all. it just seems like alot of work and risk for a almost a not noticable end result.
if im incorrect in any of my assumption, please correct me, lol even just saying that ive overclocked myr phone is awesome, im just looking for some valid reasons in favor of OCing
no one? lol i guess its not as widely done as i thought it was lol
I don't ever OC my phones for the simple reason that they are battery powered. But I understand why most people do it. Usually it is a good thing to have all the tools at your disposal for whenever you might need it. Most kernels that support OC are usually driven by apps such as SetCPU, which have options to have the CPU constantly OC'd or on-demand basis. If the user was to run a high demand app such as the video camera with a 1080p res, there be more processing power available for the app to accomplish whatever it needs in a less intensive manner.
that makes sense i suppose. having a quick launch app that allow on demand overclocking would be pretty cool. ill have to look into this a little bit further.. thx
The reason is simple - my phone is too slow.
I am using HTC Hero which is 2+ years old. The speed is so slow (528MHz), the machine lags even running the Dolphin browser. I recently root it and install a custom rom, overclock it to 6xx MHz. I feel my Hero has revived and I think it still can be used for a couple of months more.
First I am aware that overclocking is not "safe" and all that kind of stuff
However for some reason I am unable to OC my SGS2 and run the phone on a steady way.
I have tried several ROMs (stock and custom) with different kernels and OCing apps with no avail.
I am not even able to run at 1.4Ghz or 1.6Ghz without having my phone reboot or hard lock on me.
Is there a particular or recommended setting (most successful combination) that anyone out there can suggest me trying?
Sometimes it will hang under heavy gaming but sometimes even browsing app and regular stuff will cause the phone to reboot or lock. If I work with no OCing at all then everything is fine and dandy.
Thanks, you can see my current configuration @ my signature.
Sounds like a very temperamental cpu. Currently I have the same setup you do and have never had issue with 1400mhz or 1600mhz. Though I usually leave mine at 1200mhz. What app are you running when it hangs?
And just as important, do you have alot running in the background? The modified touchwiz launcher unnamed comes with can be enabled to show a red dot next to the apps that have been opened and are in the background.
If you could list the apps with the red dots.
Sent from my páhhōniē
gr8hairy1 said:
The modified touchwiz launcher unnamed comes with can be enabled to show a red dot next to the apps that have been opened and are in the background.
Click to expand...
Click to collapse
It does? That sounds more like one of the themes that includes TW4.5.
Not all CPUs can overclock - there's a reason it was sold as a 1.2 GHz chip.
Well as I've mentioned before, it could even hand when browsing through my apps menu, browsing the gallery, playing a game (non in particular) and the funny part is that the phone is not even hot to touch.
What I know for sure if that if no OC = no hangs, no reboots.
I do have the App monitor widget that comes with the stock ROM and currently using it on UnNamed 1.3.1 and I only have Widget Locker App. However I have try closing it and still will happen.
Not sure if maybe this CPU is somehow having an issue that makes it unstable as soon as I OC it.
Entropy512 said:
Not all CPUs can overclock - there's a reason it was sold as a 1.2 GHz chip.
Click to expand...
Click to collapse
Now that is new to me, I thought that all of them were OCable. Is there anyway to identify which can be or not OCed?
nope.. just by testing. it does have to do a little bit with the kernel and rom. the roms didnt originally have stable OC. i would assume that all of them do now. one thing you might try is giving them a little more voltage (just a little) at the higher clocks, but be careful. if you increase the voltage that means that you will sink more enery through the cpu and it will get hot quick. make sure you watch the temp.
i find that setcpu is less stable than the built in cm7 oc menu but cm7 doesnt have a voltage menu.
but on the same token... why OC? i can and i did but i dont need to... everything is like butter and i didnt see that huge a gain by OCing it anyways
tmckenn2 said:
nope.. just by testing. it does have to do a little bit with the kernel and rom. the roms didnt originally have stable OC. i would assume that all of them do now. one thing you might try is giving them a little more voltage (just a little) at the higher clocks, but be careful. if you increase the voltage that means that you will sink more enery through the cpu and it will get hot quick. make sure you watch the temp.
i find that setcpu is less stable than the built in cm7 oc menu but cm7 doesnt have a voltage menu.
but on the same token... why OC? i can and i did but i dont need to... everything is like butter and i didnt see that huge a gain by OCing it anyways
Click to expand...
Click to collapse
I know, this Exynos processor is the best out there right now, forget about Qualcomm's Snapdragon on the Skyrocket. I am just trying to OC for the fun of it
Guti1977 said:
I know, this Exynos processor is the best out there right now, forget about Qualcomm's Snapdragon on the Skyrocket. I am just trying to OC for the fun of it
Click to expand...
Click to collapse
Although it makes me wonder if the CPU could be having an issue, since it hard locks when attempting to.
Guti1977 said:
Although it makes me wonder if the CPU could be having an issue, since it hard locks when attempting to.
Click to expand...
Click to collapse
have you ever overclocked PC CPUs? if you have spent much time doing that, then you would know that not every chip, even within the same model/family, will clock the same. take 2 CPUs, from the same batch, same model, with identical hardware tied to them. you will probably find that one clocks higher stable speeds than the other.
its very likely the proc in your phone just cannot handle the overclocks that the next person's could.
Like pirate said, no two pieces of hardware are identical. Sort of shows how much variance there can be in a manufacturing process. Id guess theres a few chips that come off the same line that arent stable at 1.2 ghz, but they dont make it to the devices, whereas one that can handle a higher clock will. (No sense tossing one that exceeds minimum requirements, thatd just be throwing good hardware away)
You could try nudgin the voltage up and seeing how it behaves, just use caution.
Sent from my SAMSUNG-SGH-I777 using XDA App
garyd9 said:
It does? That sounds more like one of the themes that includes TW4.5.
Click to expand...
Click to collapse
My bad. You are correct.
Sent from my páhhōniē
To get mine to overclock to 1.4 and 1.6Ghz I had to actually INCREASE the voltage settings via Voltage control app. So my settings are: 1.6Ghz= 1475mV and 1.4Ghz=1325mV
Try those out and see if is better for you. I tried undervolting the higher voltages and would either lockup or reboot instantly until I tried adding voltages. So you may need to play with your settings to get it to work for you.
Sent From My KickAss ATT SGS2 SPORTING CM7
twiggums said:
Like pirate said, no two pieces of hardware are identical. Sort of shows how much variance there can be in a manufacturing process. Id guess theres a few chips that come off the same line that arent stable at 1.2 ghz, but they dont make it to the devices, whereas one that can handle a higher clock will. (No sense tossing one that exceeds minimum requirements, thatd just be throwing good hardware away)
You could try nudgin the voltage up and seeing how it behaves, just use caution.
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Yup, or if they want to sell a "premium" device with a higher clock rate, they will take the parts that test well at 1.4 and sell them as such - meaning parts rated 1.2 will be LESS likely to be overclockable if a device comes out with CPUs rated at 1.4 - like the Galaxy Note did.
Before, anything that could meet the requirements of stable at 1.2 was sold to any Galaxy S II - but now, the premium parts are going into the Note.
RockRatt said:
To get mine to overclock to 1.4 and 1.6Ghz I had to actually INCREASE the voltage settings via Voltage control app. So my settings are: 1.6Ghz= 1475mV and 1.4Ghz=1325mV
Try those out and see if is better for you. I tried undervolting the higher voltages and would either lockup or reboot instantly until I tried adding voltages. So you may need to play with your settings to get it to work for you.
Sent From My KickAss ATT SGS2 SPORTING CM7
Click to expand...
Click to collapse
I am having the same issue as the original poster on my new GS2. I will have to try the settings you mention but would it be possible to do this and also apply /UV to the remaining lower (1000ghz to 200ghz) processor speeds and maintain stability?
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