Registry edit to force the CPU to 314 MHz

[Bobby Budnick]

Originally Posted by pyrobling

OK...got everything back to 100% the way it should be and this time I am going to test these settings....if doesn't work I'll just Master Reset and use the backup I will make just before I do the hack. I'll let you know how it turns out and if it helps/is neutral/or hurts in any way.

Which method were you using when you had the trouble? Threshold or profile method? Was this on a Q9? For the record, I have only had a lock-up one time ever on my Q. This was because I needed to do the memory edit for Opera which is a known bug.

[pyrobling]

I was using the profile Reg Hack. Now I am trying the Threshold hack and it seems to be really great so now I am just checking my battery.

[pyrobling]

I dunno if this would be the case with everyone....but doing the threshold changes made my Profile setting change to 5.

[Pony99CA]

Originally Posted by Bobby Budnick

I have an Asus A620 Pocket PC and it works much the same way by the way of an Asus utility/driver that sets the CPU speed. Asus was kind enough to provide a front end to that for A620 users. You could set fixed CPU speeds in scales of 100 or set it to automatic scaling. Motorola has done the very same thing but the only front end to be able to edit it's settings is through the registry.

Yes, some Pocket PCs do include settings applets to control the CPU speed. There are also applications (like XCPUScalar and Pocket Hack Master) that allow overclocking your Pocket PC.

I recently played around with Pocket Hack Master on my iPAQ hx2795. It has a 624 MHz processor, but Pocket Hack Master allows boosting the speed up to 728 MHz. I tried my iPAQ at 728 MHz and it ran fine -- except when playing video in fullscreen mode. Running at 663 MHz seemed to work OK in the brief testing that I did.

There's one application that I've heard of to do this on a Smartphone, but I've read that it doesn't work on the Q (probably because it seems to be meant for the TI OMAP).

Steve

[MBK2]

Originally Posted by pyrobling

Problems...
Unlock would not unlock
Programs would open but not show until I restarted
Device locked-up 7 times before Master Reset.

All very similar to issues when overclocking our desktop processors too much, because of overheating.....When I pushed my stock-cooled 2.4 GHz Core2Duo beyond 3.0 GHz (need custom cooling to go beyond), I starting getting those... commands not responding, programs stuck initializing, and outright PC lock-ups...

That's what I was fearing, eventual failure of the Q's CPU if pushed too hard for too long...I think I'll wait until I can learn a bit more about the consequences.
Thanks anyways Bobby and Steve.

[Bobby Budnick]

That does not sound like overheating or processor failure to me. It sounds like software corruption or more unlikely, faulty hardware. As I said before, when the phone is in a low signal area using data, it gets very hot anyway from a combination of the battery discharging and the radio chipset generating heat. This means that a high "case temperature" is normal operation for the phone. Remember, this is a mobile CPU. Designed for extremes. They are also not as sophisticated as a desktop CPU, which is one another reason they can take more heat. Finally, running at full speed all the time will not "stress" the CPU any more than running a desktop CPU at full speed. If this were the case, then there would be occasional stability problems on stock Qs when the software did decide to go to full speed.

[pyrobling]

So I am getting an amazing fast speed thanks to Pony's idea with the thresholds and now I am also using the Profile setting on 0....so now running both and doing great and still battery life is good. Fairly impressed.

**posted from my Q

[Pony99CA]

Originally Posted by pyrobling

So I am getting an amazing fast speed thanks to Pony's idea with the thresholds and now I am also using the Profile setting on 0....so now running both and doing great and still battery life is good.

If profile type 0 is truly running at 312 MHz all the time, I would think it would be mutually exclusive with the thresholds.

I think we need to get somebody here who really knows about Windows Mobile power profiles and what they do. (And, even worse, I recall reading that it's specific to the OEM, so maybe only Motorola knows for sure.)

Steve

[MBK2]

Well I just did both the hacks...profile & threshold.
No issues whatsoever as of yet, will let you guys know how it performs.

[bchill]

I've had my Q for probably around a month and a half to two months and I've never experienced a lock up until this morning. I did the ProfileType hack last night and it's the only thing I can think of that would cause my phone to lock up. I have plenty of other hacks that I put on my phone within the first week of getting it and never had a problem with freezing. My phone froze at the home screen so I did a soft reset and when it loaded back up it didn't show anything but the buttons for the start menu and contacts, and I couldn't load the start menu. Once clicking the contacts, it said something along the lines of the phone not having enough memory to perform the operation. Same error would appear when I would try to place a call - where the number I was dialing wouldn't even show up. I took out my memory card, soft reset the phone and it loaded a default home screen to where I could change the ProfileType back to 0. Not sure what the card had to do with it - only thing that makes me skeptical to blame it on this hack... I'm now using Steve's Threshold hack and the phone seems to be running great and noticeably faster than before. I'll post back if I get another error like that with the threshold hack on the phone.