Registry edit to force the CPU to 314 MHz

[BIG-D]

Originally Posted by chrischoi

Are you using the big battery? Lol.

nope but it takes a day to kill my battery

[Pony99CA]

Originally Posted by jeremyaz

I don't remember what the original profile type was can anyone tell what the original setting is? I set profile type to 5 cause I saw it mentioned & can't remember the original setting & holy crap is it fast.

The original ProfileType setting is 5.

Steve

[Kid_Icarus]

Well, I've had this 'hack' running for about a week now and have noticed no issues with my phone draining battery any faster or locking up at all. The only time I had battery issues is when I traveled from MI to VA and was in a very mountainy region with little to no coverage. I'm sure that wasn't helping my battery going in & out of roaming & changing networks. During normal use my apps are opening much quicker and run faster also. I'm a happy user now

[iamjames]

I agree. Changing the clock speed to 312 has greatly improved my Q user experience. I'm sure carriers pissed off alot of users in an effort to improve battery life by underclocking to 104mhz because i was one of those that was upset with my Q.

Not only that but underclocking broke the phone: voice recognition would not work. Only after setting it to 312mhz does the voice recognition work properly.

Question: is there a program that will handle the clock speed? I'd love to be able to just select 104, 208 or 312 mhz instead of having to hack the registry.

[Marvelous Merv]

I ran with the ProfileType set at 0 for a week. I saw an increase in the processing speed of apps, but I didn't see an improvement in what I think of as the "switching time" from app to phone use. I also saw a significant decrease in battery life.

I just switched back. It wasn't worth it for me.

[Pony99CA]

Originally Posted by iamjames

I'm sure carriers pissed off alot of users in an effort to improve battery life by underclocking to 104mhz because i was one of those that was upset with my Q.

I think you're making a couple of bad assumptions here.

First, I'm not sure the carriers did anything. Motorola (the OEM) probably chose what power profile to use.

Second, I don't think there's any underclocking going on at all in normal use. These are called "XScale" processors because they're designed to "scale" to meet the demands of the programs running. Programs that don't require a lot of CPU probably only cause the processor to run at 104 MHz (ideally saving battery life with negligible performance degradation from the user's point of view), while programs that are computationally intensive cause the processor to run at the full 312 MHz speed (at the cost of shorter battery life). Programs in the middle can cause the processor to run at 208 MHz.

If the processor were truly underclocked (meaning the system clock was slowed down), I doubt that any simple registry hack would get you to 312 MHz.

Originally Posted by iamjames

Not only that but underclocking broke the phone: voice recognition would not work. Only after setting it to 312mhz does the voice recognition work properly.

Voice recognition generally works pretty well for me using the default power profile, so I wouldn't say that it's "broken" -- with one large exception. The exception is recognizing when I say "Yes" after it asks "Did you say...?" I rarely get the "Yes" recognized, and instead get another "Did you say...?" prompt.

If I decide to ever try this hack, I'll have to check out whether the voice recognition works better, too.

Steve

[Stitch]

Not sure if this applies because I haven't looked at his phone, but my boss has a Sprint Q while I have a Verizon Q. He recently had an update from Motorola that addressed some speed issues (I believe there are some threads in the Spring forum on this update).

Verzon however has not issued an update through motorola for quite some time.

He stated that after the update his phone was way faster then it used to be in terms of daily functions with no decrease in battery life.

I'm just wondering if the Sprint patch increased the threshold settings.

BTW, running the threshold hack on my phone with no issues and a much noticed improvement in speed.

[Kid_Icarus]

Originally Posted by Pony99CA

If I decide to ever try this hack, I'll have to check out whether the voice recognition works better, too.

Steve

Voice recognition doesn't seem to be affected either way for me since I made this hack. The only problem I have is that on occassion my Bluetooth needs to be reset on the phone to get picked up, and since that's when I use VR the most that's when I notice problems...the VR works fine I just have problems getting my phone to recognize my headset

[pkpatel151]

Hello,

First of all, THANK YOU ALL. The posts here are really helpful in speeding up Q 9m.

I tried both, profile as well as threshold. While it helped speed up Q, I was unable to use Activesync. Whenever phone connected to laptop over USB, it always gave me "Unknown Device" error. I did extensive TS to see find resolution, but no luck.

Finally, reset all threshold values and it solved the problem.

From the posts here, no one has experienced this. Any idea what can I do to have both, profile as well as threshold, and still be able to connect to Activesync?

Thanks.

[la fours]

anyone using the at&t q? because the reg edit from the OP is not the same for the at&t q running WM6. i don't have an IPM folder.