Registry edit to force the CPU to 314 MHz - Page 5 - Motorola Q Forum

pyrobling · 09-27-2007, 04:12 PM

I had one brief lock up this morning so I changed the Profile hack back and am having no problem now. You said you are running the Threshold hack too......did you change the Profile back before you did this and if so did it change to 5 after doing the Threshold hack as mine did?

**posted from my Q

bchill · 09-27-2007, 04:25 PM

Quote:

Originally Posted by pyrobling

I had one brief lock up this morning so I changed the Profile hack back and am having no problem now. You said you are running the Threshold hack too......did you change the Profile back before you did this and if so did it change to 5 after doing the Threshold hack as mine did?

**posted from my Q

Not sure if this was directed at me, but in case it was... I changed the ProfileType back to 5 and then I did the threshold hack and it's been running smooth so far today. The thing most noticeable to me, speed-wise at least, is the startup screen. It's usually very inconsistent as far as how long it takes to load once it gets to the sprint screen, but I did a few test resets and so far it's been much quicker than it was before the threshold hack. My ProfileType is on 5 at the moment.

pyrobling · 09-27-2007, 04:31 PM

bchill--

yeah it was directed atat you. Interesting enough the origianl Profile was set to 5 so I wonder if the settings that Steve posted are set up to Profile 5 automatic and don't require the actual Thresholds to be changed and do it on automatically.

Like you said though I am getting great performance now and am having no problems.

**posted from my Q

Bobby Budnick · 09-27-2007, 05:03 PM

Very surprised to see any lockups coming from this. I have done this edit to two Qs now with no problem. I have to stress that any lockups almost certainly are coming from buggy 3rd party software or defective hardware. For example, Mundu IM, the most recommended AIM client around here, is terribly buggy and will crash the Q completely. I would imagine there is more buggy 3rd party software out there than stable software. Pyrobling, I noticed you said you had a "brief" lockup? Exactly what does that mean? I'm sure you are all aware, but if the CPU really did lockup because it was stressed too hard or whatever, you would need to pull the battery and put it back in. If you did not do this, then your CPU did not lockup. The "off" button still requires software interaction, so if you were able to use that to power off, you CPU did not lock up!

MBK2 · 09-27-2007, 05:21 PM

Well I ran it with both hacks and then eventually with only the threshhold hack, ....didn't have any issues from either. However.....neither gave me nothing resembling the kind of performance gains that are really noticeable. Internet browsing seemed a tad bit quicker and changing from screen to screen had a minimal speed increase, but nothing from this warrants possibly shortening the life of the CPU for. Just my 2 cents...

Bobby Budnick · 09-27-2007, 05:38 PM

I can't argue with that. The faster the CPU runs the more likely it is to die. Personally, I am only likely to have the phone until my contract is up though. Also, since this is a mobile device, I am likely to break it in some other way and get a replacement. I already broke my first Qs screen. With my RAZR I broke the screen about every 6 months, and I think I am on the same track with this one

pyrobling · 09-27-2007, 06:22 PM

Quote:

Originally Posted by Bobby Budnick

Very surprised to see any lockups coming from this. I have done this edit to two Qs now with no problem. I have to stress that any lockups almost certainly are coming from buggy 3rd party software or defective hardware. For example, Mundu IM, the most recommended AIM client around here, is terribly buggy and will crash the Q completely. I would imagine there is more buggy 3rd party software out there than stable software. Pyrobling, I noticed you said you had a "brief" lockup? Exactly what does that mean? I'm sure you are all aware, but if the CPU really did lockup because it was stressed too hard or whatever, you would need to pull the battery and put it back in. If you did not do this, then your CPU did not lockup. The "off" button still requires software interaction, so if you were able to use that to power off, you CPU did not lock up!

Thanks for CPU's 101....jk.

The reason I said brief lockup is becuase I experienced 7 lockups where I had to pull battery before I fixed it and bout a dozen minor ones that were just lags.

This time I only had 1 lock up....battery was pulled so it was probably like I thought and is related to this hack. I said brief because soon as it happened I realized what was going on and pulled battery...hopped back in and while driving fixed the reg hack (have photographic memory for directions and such so I wasn't super dangerous on road since knew where it was lol).

As soon as I just had the Threshold hack and the Profile back to 5 everything was great and I have had zero problems since.

irfan · 09-27-2007, 11:16 PM

I tried this out.. changed profile to 0 from 5... some apps felt quicker.. but the battery died after only 8 hours of basic usage (email polls every hour, 10min of internet, no calls, checked for messages every now and then). Usually I can get thru a day or more. I'll change it back tonite to see how it runs tomorrow.. if its back to normal i'll try the 0 again to confirm.

Also i plugged it in to charge when i got home at 6, checked it 5 hours later.. just pulled it off the charger and its saying the battery is just about dead.... does the Q not trickle charge constantly? Once it hits max does it stop charging and start using battery?

Bobby Budnick · 09-27-2007, 11:30 PM

To pyrobling - Thanks for your feedback. I asked before, but you did not answer: was it a Q9 that was locking up? If so, I wonder if there is something different about the Q9 that causes problems with this.

To irfan - Your battery life seems about right if you have a stock battery and were using the phone moderately. Keeping the screen off, not running apps with runaway CPU usage, and staying in a good signal area are keys to good battery life with this phone.

Your charging issue seems like it may be caused by a bad connection with the charger.

irfan · 09-28-2007, 04:04 PM

Quote:

Originally Posted by Bobby Budnick

To irfan - Your battery life seems about right if you have a stock battery and were using the phone moderately. Keeping the screen off, not running apps with runaway CPU usage, and staying in a good signal area are keys to good battery life with this phone.

Your charging issue seems like it may be caused by a bad connection with the charger.

Seems like it. I have it back to normal.. after 8 hours im still on 3 bars with typical usage. The charging issue did not appear today

Welcome to Everything Q!