Registry edit to force the CPU to 314 MHz

[Bobby Budnick]

\HKEY_LOCAL_MACHINE\Drivers\BuiltIn\IPM

Change the value in Key "ProfileType" to 0.

Forces the CPU to 314 MHz. Survives a reboot fine. My guess is that IPM is a driver Motorola uses to control hardware power settings, and this directs the driver to stop CPU scaling, thereby defaulting the CPU to it's normal state of full power.

I was not satisfied with the auto CPU scaling so I poked around and eventually made this change. This area will also allow you to tweak the scaling threshold values if that is what you are into.

This edit, combined with changing the shell memory value to 96, and keeping a clean install are the only speed tweaks I use.

[Pony99CA]

That's interesting, but I believe the CPU is actually a 312 MHz processor, not 314. (Yes, it's a nit.) Look at the Threshold208to312 value, for example.

In fact, maybe changing those values can achieve the same effect. I'm guessing the values control when the CPU speeds up or slows down based on CPU usage percentage.

So maybe the following settings would work, too:

• Threshold104to208 -- Change from 60 to 2.
• Threshold208to312 -- Change from 85 to 4.
• Threshold208to104 -- Change from 40 to 1.
• Threshold312to208 -- Change from 50 to 3.

I haven't tried it, though (and probably won't ).

However, remember that any hacks here can hurt battery life (and, like any registry hack, mess up your device). Also, I might be worried about overheating if the CPU isn't designed to run full speed all the time (but I hope Motorola stress tested that).

Steve

[Bobby Budnick]

TCPMP reports the speed as 314. I guess it's the way it does it's calculation.

I think the way the threshold works is it switches to the speed when the cpu load stays at or above (or below for down steppings) the specified load percentage for an (unspecified) amount of time. Changing the threshold values all to 1 works too, but that route made me nervous because I was afraid it would constantly switch the CPU speed back and forth in some situations. I like this way much better.

The heat output is not a worry because the phone actually gets pretty hot anyway when using EVDO in a low signal area. The heat mainly comes from the radio chipset and the battery discharging rapidly. I noticed no increase in heat during normal use.

[TommyT]

Originally Posted by Pony99CA

That's interesting, but I believe the CPU is actually a 312 MHz processor, not 314. (Yes, it's a nit.) Look at the Threshold208to312 value, for example.

In fact, maybe changing those values can achieve the same effect. I'm guessing the values control when the CPU speeds up or slows down based on CPU usage percentage.

So maybe the following settings would work, too:

• Threshold104to208 -- Change from 60 to 2.
• Threshold208to312 -- Change from 85 to 4.
• Threshold208to104 -- Change from 40 to 1.
• Threshold312to208 -- Change from 50 to 3.

I haven't tried it, though (and probably won't ).

However, remember that any hacks here can hurt battery life (and, like any registry hack, mess up your device). Also, I might be worried about overheating if the CPU isn't designed to run full speed all the time (but I hope Motorola stress tested that).

Steve

I just changed my settings to the above and WOW. its fast.. not freezing up yet.

[SingBar]

Originally Posted by TommyT

I just changed my settings to the above and WOW. its fast.. not freezing up yet.

Ok I'm an noob at this stuff so please shed some light. If I do this hack where will I see the biggest difference in speed?

[Bobby Budnick]

Originally Posted by TommyT

I just changed my settings to the above and WOW. its fast.. not freezing up yet.

Be sure to use the first registry edit posted. Don't use the one with the thresholds. Yes it makes a big difference, as you would expect.

[mindfrost82]

Originally Posted by Bobby Budnick

\HKEY_LOCAL_MACHINE\Drivers\BuiltIn\IPM

Change the value in Key "ProfileType" to 0.

Forces the CPU to 314 MHz. Survives a reboot fine. My guess is that IPM is a driver Motorola uses to control hardware power settings, and this directs the driver to stop CPU scaling, thereby defaulting the CPU to it's normal state of full power.

I was not satisfied with the auto CPU scaling so I poked around and eventually made this change. This area will also allow you to tweak the scaling threshold values if that is what you are into.

This edit, combined with changing the shell memory value to 96, and keeping a clean install are the only speed tweaks I use.

Where do you change the shell memory?

[Bobby Budnick]

Originally Posted by mindfrost82

Where do you change the shell memory?

\HKLM\Software\Microsoft\Shell\LowMem\

Key 'ProgramMem' change to value 96.

This lets programs use a little more memory before the OOM killer closes them.

[pyrobling]

Wish I could post a thanks for this...hint hint Chris...since I am on my Q. But yes I have noticed a tremendous improvement. I may do a backup and try Steve's idea after I redownload the Sprite Backup to the Q.

**posted from my Q

[mindfrost82]

Originally Posted by Bobby Budnick

\HKEY_LOCAL_MACHINE\Drivers\BuiltIn\IPM

Change the value in Key "ProfileType" to 0.

Forces the CPU to 314 MHz. Survives a reboot fine. My guess is that IPM is a driver Motorola uses to control hardware power settings, and this directs the driver to stop CPU scaling, thereby defaulting the CPU to it's normal state of full power.

I was not satisfied with the auto CPU scaling so I poked around and eventually made this change. This area will also allow you to tweak the scaling threshold values if that is what you are into.

This edit, combined with changing the shell memory value to 96, and keeping a clean install are the only speed tweaks I use.

This must make a big difference in battery drain. I never actually had any problems with the battery since I'm not a heavy user, and I always have the ability to charge my Q. I did this hack yesterday afternoon and by bedtime I was down to 2 bars whereas I normally have 3-4 still.