Registry edit to force the CPU to 314 MHz

[Bobby Budnick]

I think it depends on how hard you use it usually. I use it pretty hard all the time anyway, so normally the CPU would be at a high clock at least part of the time. If all you do usually is idle the phone and wait for calls, this may not be for you. I always have 4-6 applications running. I have to mention that I leave it plugged in always when I am home, and I have a 1500 mA/h battery which makes a big difference for me. When your on battery, it goes without saying to lock the phone to keep the screen off too.

[BIGD]

my battery is still alive , but i've been using really heavy

[Pony99CA]

Be sure to use the first registry edit posted. Don't use the one with the thresholds.

Why not? I prefer making hacks where I have some idea how they work. The threshold version seems pretty obvious how it works, unlike the profile type version.

Granted, the profile type hack is easier, but tell me what profiles 1-4 do, please.

My suggestion is to try both and go with the one that makes more sense to you.

NOTE: I haven't tried either hack, so I don't know if my suggestion would even work. It's just speculation based on the value names, but it apparently does work.

Steve

[Bobby Budnick]

I see what you're saying. I have tried both ways and neither resulted in a spontaneous meltdown, so people are safe to try either way. I had the threshold method going for a while with all values set to 1, but I just wanted to find a cleaner method. It seems like the driver could still be fiddling with the CPU in certain circumstances when using the threshold method. I am 99% sure the profile method keeps the CPU at max constantly. Though, like you, I do wonder what the other profile levels do. Maybe for some kind of debugging?

[Pony99CA]

Though, like you, I do wonder what the other profile levels do. Maybe for some kind of debugging?

Does changing the profile type also change the thresholds? (As I said, I haven't tried either hack.)

I'm guessing the other profiles are things like:

• Always run at 104 MHz to save battery life.
• Always run at 208 MHz as a compromise.

But I'm at a loss to figure out what the other two could do unless they just use different threshold values.

Steve

[MBK2]

I overclock my Core2Duo on my desktop, but am extremely careful about the temps so as not to 'kill' my processor in the long-term.....Do you guys know if these 'hacks' are or aren't raising the CPU temps and may inevitably shorten it's life??? Because we all know that heat is the fatal enemy of processors, right?

Just asking since the Q is soooooo compact already.

[Pony99CA]

I overclock my Core2Duo on my desktop, but am extremely careful about the temps so as not to 'kill' my processor in the long-term.....Do you guys know if these 'hacks' are or aren't raising the CPU temps and may inevitably shorten it's life?

Did you read the thread? Specifically the second post where I raised the issue of heat and the third post where Bobby answered my concern?

Steve

[MBK2]

Did you read the thread? Specifically the second post where I raised the issue of heat and the third post where Bobby answered my concern?

Steve

Not 'noticing' any increase in overall heat and actually 'knowing' the CPU's temp running this hack are two pretty different standards. The fact that the phone does get hot to begin with makes me concerned of any potential increase in heat to the processor.....

Thus I asked does anyone know for sure if the actual CPU temps 'are or aren't ' rising???

If you don't know for sure, then that is what I want to know....if you do know for sure, let me know how...

[Pony99CA]

Not 'noticing' any increase in overall heat and actually 'knowing' the CPU's temp running this hack are two pretty different standards. The fact that the phone does get hot to begin with makes me concerned of any potential increase in heat to the processor....

Which is why I asked the question in the first place.

Thus I asked does anyone know for sure if the actual CPU temps 'are or aren't ' rising?

Of course it's raising the temperature -- it's running full speed all the time instead of slowing down sometimes. The real question is whether it's raising the temperature above the design limits of the processor.

I would hope Intel/Motorola at least allow the processor to run full speed indefinitely in their design guidelines, but I'm not sure anybody outside of Motroola and/or Intel can definitively answer the question (unless their Q bursts into flame).

This is one of those hacks you do at your own risk.

Steve

[MBK2]

Better wording of the question is whether the CPU runs at a detrimental temp while trying to run full board thru-out...

Another thing is, how would the CPU run at full processor speeds when not needed?? Can't possibly be running at the full 312 MHz without processes and Apps running, can it??