[trion23]

Hello fellow Moto Q users. This is my first post on the forum. I've had my Moto Q for three or four weeks now and I'm loving it! Of course, as with most relatively cutting edge technologies, there are compromises and problems with these kinds of devices (especially if you can't leave them "stock" and have to tweak them and load them up with all kinds of software like I do).

Over the weekend, I had a very strange problem with my Moto Q that had me thinking for a little while that I was going to need to have the device replaced (or at least wiped out and restored to factory settings). The first thing I will admit is that I had just (maybe 2 days before) done the registry hack to force the Q to run at higher speeds more of the time ( http://www.everythingq.com/forum/mot...mhz-12075.html ).

I initially followed Pony99CA's suggestion to change the threshold settings to 1,2,3, and 4 as shown. This seemed to actually cause some performance issues on my device, so I modified the settings to 15,20,25,60 respectively(defaults are 40,50,60,85). I was working under the assumption that the 60 and 85 values indicate the CPU usage threshold to "upshift" into the next "gear" (switching from 104MHz to 208MHz to 312MHz). I also figured the 50 and 40 values indicated "downshifts" to the slower CPU speeds. This seemed to work much better for me than the 1,2,3,4 values and appeared to give a performance boost over the stock configuration.

Then, a day or two later, I noticed TCPMP (072RC1) having issues and crashing a couple of times. I had already been having some trouble trying to play videos on the Q smoothly. I haven't quite figured out, while encoding video, the best settings to use to get the maximum picture quality without dropping an excessive number of frames (possibly another post).

Some of the videos TCPMP had trouble playing smoothly now crashed it completely. The video would grind to a halt and then the whole screen would completely "white out" as if every pixel was displaying its maximum brightness output. It did this two or three times, each time I either held the power button down until it finally shut down or I removed the battery (or maybe both). Finally, it happened again and I just let it sit to see if it would eventually recover on its own. I took another look at it after awhile and it had seemed to reset itself and was back at the home screen.

Now the weird part, when I tried to unlock the keys, it prompted me for my PIN, but the DONE soft key was grayed out and a countdown timer was running on the bottom left side of the screen. I would enter my PIN, but then I couldn't hit DONE to make the device accept it. Also, the timer seemed to be irrelevant, as when I tried to let it count down the screen would time out far before the timer would run down to zero. It would then clear out the PIN I had entered and I was no closer to getting access to the Q.

I tried powering the device down (which it would let me do) and restarting - same deal. I tried removing the battery and powering back on - no dice. I even removed the battery and SD card, waited at least half an hour, then rebooted. I got the same thing every time. It would prompt for my PIN, but wouldn't let me hit the button to enter it.

I finally hooked it up to my laptop to see if I could still sync it, and it synced up fine. This meant that it was accepting the cached password from ActiveSync with no problem. So I was sure to make an updated registry backup and data backup, thinking I would probably have to get the darn thing replaced. I powered it down and went to bed.

When I tried it again the next morning, the problem was miraculously gone! It doesn't seem possible to me that it could have "fixed itself" like that, but apparently it did! I uninstalled TCPMP and I have had no more issues with the Q at all. It's running super smooth now. I am missing TCPMP and may try to reinstall it soon (maybe a different version).

I'm posting this to see if anyone has heard of anything like this happening (I searched for this problem the other night and found nothing about it). I want some insight into what was (and maybe still is) going on with my device. I would like to avoid a repeat of this scenario. I also figure if this happened to me it is likely to happen to someone else in the future.

One more note - I was camping when this happened, so I had little to no cell phone signal (no more than one or two bars at the most depending on exactly where I was). I think this may have been a factor because when my signal kept going from none to slight, my phone was doing weird things.

Thanks in advance for any insight, suggestions, and just chit-chat you can provide!

Trion