Database Info

Lock / Home screen "fizzes" out. Phone issue or rom issue?

Hey guys, searched for a quite a while and havnt been able to find a similiar problem. Heres what i did
Got the phone 3 days ago and proceeded to root it. It had the perfect SPL so i took the long route and made a goldcard and went to the 2005 SPL.
After phone was flashed i did the "daredevil" way of reverting back to 32b and flashed an appropriate rom to it (cynogens 4.1.8 is on there now)
It seems about %70 of the time when you hit the menu button to get the screen to turn on you can see it flash some lines on the screen like its "charging" the lcd than it just fizzes out, no picture what so ever is visible just weird fuzzy tv looking things than they go away. Trying again usually does the same thing. I have to try probably 5-6 times just to get the screen to turn on and work like normal.
So my question is, is this a PHONE issue, or is this something that could be rom / radio / spl related.
If this is a phone issue i need to take this to unroot and take to the tmobile store asap and get it replaced with another under warranty.

I got the same thing in my G1... send to HTC warranty, they changed the main board. Got it back and it happened again. Then I rooted and installed cyanogen mod, now I never see it again. So I thought it was a hardware issue, but after ROM upgrade I never see it again, so now I really don't know...

The issue is being worked on in this thread and it seems to be related to specific kernels: http://forum.xda-developers.com/showthread.php?t=554612

notxel21 said:
The issue is being worked on in this thread and it seems to be related to specific kernels: http://forum.xda-developers.com/showthread.php?t=554612
Click to expand...
Click to collapse
ok so this could possibly be both rooted / non rooted boards? Thanks for that link i appreciate it, i'll put my few good words in there. I dont think i can use this phone for business with it doing this.

This is mainly an issue with CPU clocking. Download the CPU clock widget for free and set it at no greater than 245mhz as a starting value. You can clock all the way up to 528 safely but if the phone tries to turn the screen on at 384mhz or greater you will get this fuzzy screen issue repeatedly! I was having this problem lots over the last few days and once I turned my cpu clock down to a range of 245mhz to 528mhz instead of what I was running of 384mhz to 528mhz the problem is gone. Some roms do this clocking automatically so even a fresh flash of a rom can cause this issue but if you download an app that allows you to change the cpu clock *you do have to be rooted* then you can solve this issue.
Give it a shot and post your results here so others may know this works too!
P.S.
The thread: http://forum.xda-developers.com/showthread.php?t=554612&page=25 refering to the "blurry screen issue" is not what this topic is about. The origonal post is refering to the screen fizzing with some distorted lines across it when you turn the screen on and then it looks blank or is backlit but has nothing on the screen. After about 5 tries though the screen will come back on as normal and operate as normal until the next time you turn your screen off and back on. The other thread mentioned is for problems with certain roms looking normal after first boot and then going blurry, like when you get a confirmation on the screen and the background blurs, except it happens to the entire screen and does not go away. If you are having this blurred screen problem, please go to the other thread. If you are having a fuzzy screen where sometimes it comes back on and sometimes just goes blank, then please clock your cpu down to 245mhz and let it clock up gradually to whatever higher cpu setting you want.

Apollo_316 said:
This is mainly an issue with CPU clocking. Download the CPU clock widget for free and set it at no greater than 245mhz as a starting value. You can clock all the way up to 528 safely but if the phone tries to turn the screen on at 384mhz or greater you will get this fuzzy screen issue repeatedly! I was having this problem lots over the last few days and once I turned my cpu clock down to a range of 245mhz to 528mhz instead of what I was running of 384mhz to 528mhz the problem is gone. Some roms do this clocking automatically so even a fresh flash of a rom can cause this issue but if you download an app that allows you to change the cpu clock *you do have to be rooted* then you can solve this issue.
Give it a shot and post your results here so others may know this works too!
P.S.
The thread: http://forum.xda-developers.com/showthread.php?t=554612&page=25 refering to the "blurry screen issue" is not what this topic is about. The origonal post is refering to the screen fizzing with some distorted lines across it when you turn the screen on and then it looks blank or is backlit but has nothing on the screen. After about 5 tries though the screen will come back on as normal and operate as normal until the next time you turn your screen off and back on. The other thread mentioned is for problems with certain roms looking normal after first boot and then going blurry, like when you get a confirmation on the screen and the background blurs, except it happens to the entire screen and does not go away. If you are having this blurred screen problem, please go to the other thread. If you are having a fuzzy screen where sometimes it comes back on and sometimes just goes blank, then please clock your cpu down to 245mhz and let it clock up gradually to whatever higher cpu setting you want.
Click to expand...
Click to collapse
That's what were refering to the screen wake issue. Same problem just called different things. I will try to set my phone at or below 245MHZ for my low and post results!!
Because I've came across both issues depending on the rom. Some give me blur, and some give me the screen wake issue, and some give me both, but I will try you're suggestion.
Thank you for this.

Yeah the JacX hero rom is the only hero rom I have found for the *well at least my* MyTouch3g that *does not* give me the blurry screen issue so that's what I'm running. Then last night I played with my clock settings and went to bed, only to find that my screen was now having this distorted/not waking up issue not like the blur issue of other roms and when I retraced my steps and clocked the processor back down the screen not waking up issue went the way of the dinosaur! I really wish the blurry screen issue could get solved already because I want to try some other hero roms and especially cyanogens experimental rom really bad but I need my phone to work too lol...well I have spare phones so that's not entirely true but I just love my android so much lol!
And you're welcome! I figure that I've learned so much from this forum over the years and had so many helpful and friendly people that it's the least I can do to provide help back!
I'd still love to know if this works for you *I'm confident it will* if you wouldn't mind posting your results as well!

I just updated to 4.1.8 and it hasnt did it in quite some time now. Didnt get the overclock widget yet but im going to wait till it does this again to see if thats the issue. Which more then likely it is.

Not as much of an issue with wake screen on 4.1.9.2 but its still there.
Guess i'll try the overclock widget also.

Yeah the devs (most anyway) are now incorporating built-in cpu clocking settings in the user.conf file for their roms and this allows the rom to do dynamic cpu clocking from the stock rom, which also allows them to push the speeds of the phones the roms are installed on without additional software. The downside to this is when the clock starts above what it's default is, or at least above 245mhz the screen has a tendacy to not wake up properly. If the clock is started at 245mhz and then gradually moved up to 528mhz based on demand on the cpu then the problem goes away. The cpu widget is free and works great to allow you to control the cpu clocks, not the rom. There's another one I'd recommend called SetCPU on the market but it costs like $2 or $3 which also works nicely but doesn't really add anything over the free widget available other than some profile options for low battery and such.
*I'm still learning alot every day about all this android modding stuff so if I've stated anything incorrectly please PM me or let me know here and I'll edit my posts acordingly*
~*Apollo*~

still no dice
im running 4.1.10.1 and it is still not waking up properly. Even with the overclock widget installed and working. Im not sure what else to do. Im updating to 4.1.11.1 right now but i have a feeling this isnt going to fix anything.

I haven't seen this.
This issue has been addressed more thoroughly in the Dream section. Follow up with stories and details there. Otherwise, I haven't seen this problem in any of the most recent ROM ports.
Everyone's device is different regardless of matching statistics. Lol.
Best of luck to you fellas.

Battery problem on Touch Pro - possible cause

Hi all,
My father bought an HTC Touch Pro some time ago; I think it was in 2008, as he needed a good phone, with the organization capability that WM has to offer.
The phone is in MINT conditions, really. It still has the original screen protector and no scratches can be found on it. He uses it a lot, but always has it in the leather case, and in a small pocket, which sometimes results in lost calls, as no one can really hear it ring . The battery is always fully charged, and after some testing I think it is still in good conditions.
The problem that he started getting is that after I installed some programs like GPS Tomtom and AGEPhone for SIP calling that he never uses (hehe), he started noticing the battery was discharging faster and that it would not last even 1 day, when before it would last about 3-4 days.
I uninstalled the programs, and the problem persists. Brightness is on 50%, wifi and any internet connection is turned off. No programs running in background, unless it's active sync that sometimes turns on itself.
POSSIBLE CAUSE - We noticed is that he has a lot of reminders, so the phone is constantly waking up. The problem is that it does not go to sleep afterwards. The touch screen is locked, so when a reminder pops up, the screen stays turned on, even if the backlight is not on, and just drains the battery completely.
Is there anything we can do, so that it (the reminders of meetings, birthdays and other stuff) would not wake the device up, or if it did, the phone would go to sleep after some seconds, so that it would not overheat and drain the battery in 1 day?
It is a quite annoying having to constantly look at the phone, dismissing reminders and turning the screen off, so the battery can last a bit longer.
I need to solve this problem, but my father will not agree with a custom ROM flash. Maximum I can do with it is upgrade it through the HTC tool, but I am not sure if it is worth it.
Here are the information:
Version de ROM: 1.90.406.5 FRE
Date de ROM: 08/20/08
Version de radio: 1.02.25.19
Version de protocole: 52.33.25.17W
The device was bought in Luxemburg and has a French windows mobile 6.1 on it, and an AZERTY keyboard.
Please help me with this issue.

Get tBattery and check to see the current draw under stead, idle conditions. With the backlight at 5, it should draw about 110 mA (there may be some spiking). Use the log feature, say for 10 min @ a time, with power-save options unchecked so the screen doesn't dim and it doesn't go to sleep. If the drain is high (constantly above 200 mA, let's say), then get a good task manager (hint: new dotfred's 3.3) and start killing processes, and see if that helps. If not, then try stopping some of ther services.

Thanks Farmer Ted for the reply, but I think I found the cause of the problem. I don't know why but after it wakes up, because of an appointment, it will not turn the screen off, even after 10 minutes and I have the power management set 30 sec off if not being used.
As the screen is locked, the appointment will not be dismissed by accident or pressed so it just stays like that, until the battery is dead.
Is there a hidden option to make the phone go back to sleep, or to prevent it from waking up, just making the led blink, as when you get new SMS messages and the screen is off, or when you get a missed call?
If there was I think it would solve the problem completely.
Thank you all for your help.

yes the problem is the screen it drains it faster than a hobo with a bottle of wiskey,
what you have to do it click on batter icon and get into the battery menu select advanced and elect turn back light off if device is not used for and select 10 second, then turn off device if not used for and slected 1 minute (its reffering to the screen)
then i use a program called touch pro tweak (its cooked into all energy roms) and there is a setting to wake up on call or text or notification and disable it by wake up it refers to turing the screen on

I have a simmilar problem.. I discovered what causes it... When I install certian programs, it changes the power settings.. namely, the power off when not plugged in setting... So, check out those settings... I have had this happen 3 or 4 times in as many months... then I notice the same issues with my battery.. after I go change the settigns back (for the 100th time) it goes back to pastign 2-3 days for me... (instead of less than 1)

Hi people, sorry to bring up this topic again, but I see no point in creating a new one.
I would like to ask if any of you would recommend me a good French ROM (as it comes with AZERTY keyboard) for this device that has good battery life?
Is it possible that a cooked WM 6.5 would use less battery then stock WM 6.1?
I have another problem, is there a way to turn up the ringing volume of the phone, in order to hear it even if it is in a small bag? It's already on max, but my father complaints the ringing volume is too low and he can not hear it.
And last but not least, how much does this battery normally last? Wifi off, bluetooth off, calling about 15 min a day, some SMS and a lot of reminders.
It can not go a day, max two days without recharging. It is always turned off when he goes to sleep, because if not, he will wake up with a dead device.

Overclocking Our Touch Pro

As we know, overclocking MSM is possible now. Just check :
http://forum.xda-developers.com/showthread.php?t=725290
Click to expand...
Click to collapse
But the thread is over 1400 post & most of them are about blackstone, Rhodium, etc.. I think it's about time we make a thread about overclocking our Touch Pro(s)
I use GSM unbranded TP100 & TAEL v.5 ROM.
I'll start with my experience :
What Works
Click to expand...
Click to collapse
1. grab the v.2 file from the thread above. (1st page)
2. Install it to phone Memory.
3. Open the Msm7kCpuSpeed & You can see the current CPU speed in Real Time.
4. Whatever speed you select when on Battery Power, it will revert back to 528Mhz because of the Windows component that make sure the clock speed is 528 Mhz every (xx) second.
5. The only way you can overclock is when u plug your USB to Laptop / Stock Charger. Only then you can move the slider to any speed supported by your device.
6. Every device's speed are varied from the ROM used & quality of the MSM in your device. Try what speed are the best speed in your phone before it locks up. I use TAEL v.5 & I can achieve 768 Mhz in AC (original Charger / USB in Laptop/PC) on 787 i get random lockup
7. If you unplug your Raph from USB / Charger on ANY freq other than 604.8 Mhz, your raph will LOCK UP. So, when unplugging / pressing power button make sure u change the freq to 604 Mhz first. (604 Mhz is special Freq that don't Lockup our device)
8. A couple of seconds after we unplug our Raph in 604 Mhz freq it will revert back to 528 Mhz freq.
What almost works
Click to expand...
Click to collapse
From the explanation above we can use Overclock in Our Raph, but only when plugged into a charger / laptop / PC.
In this
PHP:
http://forum.xda-developers.com/showthread.php?t=725290&page=120
thread Qzytor in post 1191 found a way to overclock our MSM devices when using battery power. But in my experience, it ALWAYS lockup a few seconds after opening the phone dialer, coreplayer (playing video for a few second the lockup), SMS messaging, and Teeter (lockup when level up)
I'll write my experince using above method :
The method is : (Credit goes to Qzytor)
Code:
Install NetRippers Msm7kCpuSpeed V.2 App. in your Device
Install SetCpuSpeed v1.0d on SD card. --get it @ http://forum.xda-developers.com/showpost.php?p=7426966&postcount=1000 --
Take SD card out and soft reset the phone.
Open registry.
Go to HKLM\Software\Msm7kCpuSpeed.
Edit the values as below:
BootTime = 90000 (This is important. This value gives enough time for the
phone to fully boot up. The phone has to fully boot up
before the OC kicks in)
CheckTime = 20 (Stable at 20, otherwise yoyos between base and OCed
cpu speed)
Command = 0
PerfomanceLevel = 35 (This speed is stable for me without SOD)
ScreenOffPerfomanceLevel = 27
SettlingTime = 10
Close Registry editor, insert SD card in the phone and soft reset the phone.
Once the phone has fully boot up, give it a minute before opening NetRippers Msm7kCpuSpeed and you should see your OCed cpu speed.
If your OC cpu speed isnt stable then take your SD card out,soft reset the phone and registry edit PerfomanceLevel to a lower value.
To restore back to phone default speed:
Open File Explorer.
Go to Windows\Startup folder and delete SetCpuSpeed.
Soft reset the phone and phone default speed will be restored.
Before deleting SetCpuSpeed from Windows\Startup folder , save it in Documents folder so if you want to overclock again, copy and paste it from Documents folder to Windows\Startup folder.
1. Performance Level 35 is overclocking @ 672 Mhz
2. Add 1 level means add 19.2 Mhz in clock speed
3. The best speed i reach in AC power (USB / Laptop) is 768 Mhz = performance level 40
4. I change my performance level into 40 & I can see in MSM7kCpuSpeed that i'm running 768 Mhz after 90 seconds from the bootup as written above.
5. a few programs can run ok in 768 Mhz or any speed in that matter, but most causes lockup. This does NOT happen in Blackstone / Rhodium
6. Even on performance level = 35 (672 Mhz) or even in Performance level = 27 i still got a lockup opening phone, SMS, coreplayer, teeter, & FPSECE (only when exiting). they work fine on AC power.
7. I dont know if it's because of my ROM (TAEL v.5) or if all RAPH experience the same Issue.
I hope we can continue to improve overclocking our RAPH to the point it can perfectly works ^^

Another OC program
There is also this Overclock Tool:
http://forum.xda-developers.com/showpost.php?p=7463284&postcount=162
I haven't tried it yet, but it should work with our Raphael, and also on battery power.

I'm using touchpro and newest energy cookie rom.
Tried the method mentioned by b0z0k. Set level 35 for the 1st trial
Apps tried list:
Youtube
Opera
text message
File explorer
excel mobile
google mpas
teeter
window media player (not the music tab in sense)
lockup when playing teeter and music (the sense one). However, for other programs, it was just working brilliantly.
Really hope my experience can help.
After turning it to level 35, the device looks quite stable but i haven't tried any levels upper than that.

zai_hkman said:
I'm using touchpro and newest energy cookie rom.
Tried the method mentioned by b0z0k. Set level 35 for the 1st trial
Apps tried list:
Youtube
Opera
text message
File explorer
excel mobile
google mpas
teeter
window media player (not the music tab in sense)
lockup when playing teeter and music (the sense one). However, for other programs, it was just working brilliantly.
Really hope my experience can help.
After turning it to level 35, the device looks quite stable but i haven't tried any levels upper than that.
Click to expand...
Click to collapse
Yes, i just tried Energy ROM 1-2 days & Overclock works like a charm. Don't hestitate to use higher freq.. i found out that the best stable freq in my device are @ 748.8. 787 will instantly freeze my TP, 768 works but many apps crashing, 748.8 works very well with FpseCE
What i did, is try the newest energy ROM (rel. 23673, GTX, dinik version) & it all work like a charm. Sure, i still got occasional SOD but it's waaaaaaayyyyyy better than having to OC in Laptiop USB only..
So i think the issue i had earlier is definitely with the ROM (I think TAEL rom has some kind of energy saving script that keeps telling the CPU what clock it's running -- even when setCPUspeed already installed)
After i change to Energy Rom rel. 23673, on battery power, MSM7kCPUspeed+setCPUspeed v1.0d runs just as smoothly as AC power. I get occasional SOD only when exiting Fpsece (it makes the CPu drop to 384 Mhz then it froze). Using WMP, TCPMP, & other apps that usually crashes on TAEL v5 did NOT give me the "freeze"
@ 748.8 Mhz FPSEce gives me 5-8 fps boost with no frameskip , with frameskip i can play Final Fantasy Tactics @ 50 fps with no noticable errors (about 29 fps in landscape no frame skip)
And that makes me...
--> very happy TP owner
p.s. a little trick when having a non OC applicable ROM is to use your GPS programs (garmin, sygic, etc), minimize them, & run MSM7kcpuspeed to OC your device. this usually works ok.. Just a very bad battery consumption
& dont forget to change back to 604 Mhz before shutting down your GPS program & then u can power off the screen -- or else u get the SOD.

An update on usage:
I've just flashed to the updated rom for energy(Aug18 Cookie 23678)
After that, I overclock the device by the previous method.
I found that the device freezes everytime when i receive calls. Therefore,I have to remove the setcpu.ink in the window to stop overclocking. Anyone has figured out why the device freezes on some program but behave normal for the most of the time?

zai_hkman said:
An update on usage:
I've just flashed to the updated rom for energy(Aug18 Cookie 23678)
After that, I overclock the device by the previous method.
I found that the device freezes everytime when i receive calls. Therefore,I have to remove the setcpu.ink in the window to stop overclocking. Anyone has figured out why the device freezes on some program but behave normal for the most of the time?
Click to expand...
Click to collapse
This is the biggest problem I have. Theres certain parts of the day while working that I use my phone a lot, and the SOD's with phone can cause me to miss calls or be unable to place a call (SOD while dialing).
Im still waiting for some sort of option to totally disable itself when a named program is run.

hartleyshc said:
This is the biggest problem I have. Theres certain parts of the day while working that I use my phone a lot, and the SOD's with phone can cause me to miss calls or be unable to place a call (SOD while dialing).
Im still waiting for some sort of option to totally disable itself when a named program is run.
Click to expand...
Click to collapse
Just about 2-3 days now i have SOD while dialing too.. I don't know what's causing it, but i can confirm that after a fresh ROM flash (energy build 23673) i CAN dial in my phone while overclocked @ 768 Mhz.. After a lot of install, trial, etc now i have SOD EVERYTIME i dial in phone dialer.
p.s. before SOD's occured i just set up my GPRS/3G connection for my carrier.. i wonder if this is the cause?

b0z0k said:
Just about 2-3 days now i have SOD while dialing too.. I don't know what's causing it, but i can confirm that after a fresh ROM flash (energy build 23673) i CAN dial in my phone while overclocked @ 768 Mhz.. After a lot of install, trial, etc now i have SOD EVERYTIME i dial in phone dialer.
p.s. before SOD's occured i just set up my GPRS/3G connection for my carrier.. i wonder if this is the cause?
Click to expand...
Click to collapse
Maybe.. I do the carrier auto-setup once i boot a new rom. (AT&T USA). It might be some settings in there messing with it.
The test I do to see if it freezes is this: Call my voicemail (google voice) and just keep hitting "7" a bunch of times and see if it freezes.
Ive also tried various phone canvases. Have tried the new one currently being cooked into NRG roms (aug 18th) before it was cooked in, will try again now to see if anything has changed.
edit: I have also been following and trying all versions of iwfratz's overclock tool, and compatibility actually seems to get worse with each new release. the original version would crash after a while at the stock 650, which on my TP its much more stable at 633. But with current versions (1.5) it crashes immediately after setting the overclock, a version or two ago it would run, but would still crash when using the phone app.

i use nrg rom 21914 and overclock with msm7kcpu speed +setup cpu 1.0d.
4 "bugs/[email protected],6Mhz":
-phone works great, untill i receve a call, than the phone hangs.
-also the phone hangs, when i will use nitrogen 1.1 to listen to music.
-and the phone hangs, when my alert goes on and i have the lockscreen activatet.
-when i receve a mms and downloaded it, the phone hangs also
after the hang, i need to put the batterie out of the tp to restart....
@ ~746 the phone starts but sense restarts again and again...but in the 6.august of nrg rom, i thought this speed works also ...
maybe someone know an answere.
I love the speed i wouldn't miss it...i already sold my Acer s200, because it is crap

New Method, No Freeze in Phone dialer, but battery more inefficient
New Method, No Freeze in Phone dialer, but battery more inefficient
I have tried SetCPUspeed v1.0d & it made the Overclock working BUT i dont know why every time I open dialer screen or an SMS came, it always freezes.
I think it has to do with the fact that WinMo in our TP consistantly checking the speed/ frequency of our MSM.
The only way we can bypass this :
1. When we connect to our laptop (activesync) -- when we connect Raph to PC & it starts sync-ing in activesync, the speed/ freq check disabled, this is an exploit that we can use to overclock safely. BUT..
We do need our laptop / PC to do this (we can't overclock when we're traveling & want to play FpseCE in full speed ^^)
2. THE NEW METHOD -- more battery draining though.. We can bypass the freq check using GPS module. When the GPS is ON, the speed check is disabled. This way, even when we're traveling, we can still Overclock our Raph safely (wont freeze when opening dialer / receivinf SMS.
But, it's still opening GPS module, it's a battery drainer. In my experience it's about 20% faster draining the battery. Use HTC GPS tool & choose "open port"
What i do is :
when the phone is not used (deep sleep), i don't use the Overclock. When i want to use something in my phone & i want to boost it's speed i will turn on HTC GPS tool & overclock my phone to 729,6 (the most stable for me). When i'm done & want to put my phone to sleep, i made my MSM7kCPUSpeed to 604 Mhz (safe speed, wont freeze) & i turn off the GPStool.
When i press the power button the freq will change to 528 Mhz again & the battery consumption became normal again. ^^
It's a turn around from the problem we're facing.. but Hey, i got to play Final Fantasy Tactics @ nearly full speed ^^

After a little testing, no freezes anymore.^^
However, if we disable the frequency check, we are not able to stablize the frequency.
What I mean is that sometimes after a call or running some programs, the frequency will drop to about 355 and I have to open MSM7kcpuspeed again to adjust the frequency.
Anyway, this is really a breakthough for overclocking out TP.

still got bugs
I love the increase of speed, when the device is overclocked.
But i got still bugs.
When i want to listen to music, it hangs after about 1-2 secounds. i don't know why.
Maybe you can help me with this problem, because i dont want to have only 527mhz.
my settings:
my BootTime = 90000
CheckTime = 20
Command = 0
PerfomanceLevel = 38
ScreenOffPerfomanceLevel = 27
SettlingTime = 10
best regards

i know it's an old thread, but is any new way public to overclock the touch pro?
atm i need to use it @ normal speed, because it is really buggy @ overclocked=/

[UPG] Overclocking Our Raph is available.. need tweaking though..

As we know, overclocking MSM is possible now. Just check :
http://forum.xda-developers.com/showthread.php?t=725290
Click to expand...
Click to collapse
But the thread is over 1400 post & most of them are about blackstone, Rhodium, etc.. I think it's about time we make a thread about overclocking our Touch Pro(s)
I use GSM unbranded TP100 & TAEL v.5 ROM.
I'll start with my experience :
What Works
Click to expand...
Click to collapse
1. grab the v.2 file from the thread above. (1st page)
2. Install it to phone Memory.
3. Open the Msm7kCpuSpeed & You can see the current CPU speed in Real Time.
4. Whatever speed you select when on Battery Power, it will revert back to 528Mhz because of the Windows component that make sure the clock speed is 528 Mhz every (xx) second.
5. The only way you can overclock is when u plug your USB to Laptop / Stock Charger. Only then you can move the slider to any speed supported by your device.
6. Every device's speed are varied from the ROM used & quality of the MSM in your device. Try what speed are the best speed in your phone before it locks up. I use TAEL v.5 & I can achieve 768 Mhz in AC (original Charger / USB in Laptop/PC) on 787 i get random lockup
7. If you unplug your Raph from USB / Charger on ANY freq other than 604.8 Mhz, your raph will LOCK UP. So, when unplugging / pressing power button make sure u change the freq to 604 Mhz first. (604 Mhz is special Freq that don't Lockup our device)
8. A couple of seconds after we unplug our Raph in 604 Mhz freq it will revert back to 528 Mhz freq.
What almost works
Click to expand...
Click to collapse
From the explanation above we can use Overclock in Our Raph, but only when plugged into a charger / laptop / PC.
In this
PHP:
http://forum.xda-developers.com/showthread.php?t=725290&page=120
thread Qzytor in post 1191 found a way to overclock our MSM devices when using battery power. But in my experience, it ALWAYS lockup a few seconds after opening the phone dialer, coreplayer (playing video for a few second the lockup), SMS messaging, and Teeter (lockup when level up)
I'll write my experince using above method :
The method is : (Credit goes to Qzytor)
Code:
Install NetRippers Msm7kCpuSpeed V.2 App. in your Device
Install SetCpuSpeed v1.0d on SD card. --get it @ http://forum.xda-developers.com/showpost.php?p=7426966&postcount=1000 --
Take SD card out and soft reset the phone.
Open registry.
Go to HKLM\Software\Msm7kCpuSpeed.
Edit the values as below:
BootTime = 90000 (This is important. This value gives enough time for the
phone to fully boot up. The phone has to fully boot up
before the OC kicks in)
CheckTime = 20 (Stable at 20, otherwise yoyos between base and OCed
cpu speed)
Command = 0
PerfomanceLevel = 35 (This speed is stable for me without SOD)
ScreenOffPerfomanceLevel = 27
SettlingTime = 10
Close Registry editor, insert SD card in the phone and soft reset the phone.
Once the phone has fully boot up, give it a minute before opening NetRippers Msm7kCpuSpeed and you should see your OCed cpu speed.
If your OC cpu speed isnt stable then take your SD card out,soft reset the phone and registry edit PerfomanceLevel to a lower value.
To restore back to phone default speed:
Open File Explorer.
Go to Windows\Startup folder and delete SetCpuSpeed.
Soft reset the phone and phone default speed will be restored.
Before deleting SetCpuSpeed from Windows\Startup folder , save it in Documents folder so if you want to overclock again, copy and paste it from Documents folder to Windows\Startup folder.
1. Performance Level 35 is overclocking @ 672 Mhz
2. Add 1 level means add 19.2 Mhz in clock speed
3. The best speed i reach in AC power (USB / Laptop) is 768 Mhz = performance level 40
4. I change my performance level into 40 & I can see in MSM7kCpuSpeed that i'm running 768 Mhz after 90 seconds from the bootup as written above.
5. a few programs can run ok in 768 Mhz or any speed in that matter, but most causes lockup. This does NOT happen in Rhodium (Touch Pro 2)
6. Even on performance level = 35 (672 Mhz) or even in Performance level = 27 i still got a lockup opening phone, SMS, coreplayer, teeter, & FPSECE (only when exiting). they work fine on AC power.
7. I dont know if it's because of my ROM (TAEL v.5) or if all RAPH experience the same Issue.
I hope we can continue to improve overclocking our RAPH to the point it can perfectly works ^^

Im happy that there are people that want to work on oc project for touch pro..I want to help even i dont know much..

I dont get the disconnect ac issues at all, but definitely get the freezing on the phone app, but apparently other phones do as well.
Im waiting for somesort of blacklist option that can actually close the overclock *and not just revert back to 528*.
Have done tests with netrippers app, setcpuspeed 1.0d, iwfratz oc tool, and oc auto 4.1 (this doesn't work with mine, I use the latest Energy rom, and Im part of the "1%" that doesn't have certain registry settings, and it doesn't work by adding them.)

hartleyshc said:
I dont get the disconnect ac issues at all, but definitely get the freezing on the phone app, but apparently other phones do as well.
Im waiting for somesort of blacklist option that can actually close the overclock *and not just revert back to 528*.
Have done tests with netrippers app, setcpuspeed 1.0d, iwfratz oc tool, and oc auto 4.1 (this doesn't work with mine, I use the latest Energy rom, and Im part of the "1%" that doesn't have certain registry settings, and it doesn't work by adding them.)
Click to expand...
Click to collapse
Yes, I agree, Iwfratz's OC tool are NOT WORKING on other device other than RHODIUM. So the best option i have is NetRipper's App + SetCPUspeed 1.0d. Can't work OC auto for some reason (no key binding App to bind mortscript down.mscr to power button).
What i did, is try the newest energy ROM (rel. 23673, GTX, dinik version) & it all work like a charm. Sure, i still got occasional SOD but it's waaaaaaayyyyyy better than having to OC in Laptiop USB only..
So i think the issue i had earlier is definitely with the ROM (I think TAEL rom has some kind of energy saving script that keeps telling the CPU what clock it's running -- even when setCPUspeed already installed)
After i change to Energy Rom rel. 23673, on battery power, MSM7kCPUspeed+setCPUspeed v1.0d runs just as smoothly as AC power. I get occasional SOD only when exiting Fpsece (it makes the CPu drop to 384 Mhz then it froze). Using WMP, TCPMP, & other apps that usually crashes on TAEL v5 did NOT give me the "freeze"
@ 748.8 Mhz FPSEce gives me 5-8 fps boost with no frameskip , with frameskip i can play Final Fantasy Tactics @ 50 fps with no noticable errors (about 29 fps in landscape no frame skip)
And that makes me...
--> very happy TP owner
p.s. a little trick when having a non OC applicable ROM is to use your GPS programs (garmin, sygic, etc), minimize them, & run MSM7kcpuspeed to OC your device. this usually works ok.. Just a very bad battery consumption
& dont forget to change back to 604 Mhz before shutting down your GPS program & then u can power off the screen -- or else u get the SOD.

b0z0k said:
Yes, I agree, Iwfratz's OC tool are NOT WORKING on other device other than RHODIUM. So the best option i have is NetRipper's App + SetCPUspeed 1.0d. Can't work OC auto for some reason (no key binding App to bind mortscript down.mscr to power button).
What i did, is try the newest energy ROM (rel. 23673, GTX, dinik version) & it all work like a charm. Sure, i still got occasional SOD but it's waaaaaaayyyyyy better than having to OC in Laptiop USB only..
talled)
After i change to Energy Rom rel. 23673, on battery power, MSM7kCPUspeed+setCPUspeed v1.0d runs just as smoothly as AC power. I get occasional SOD only when exiting Fpsece (it makes the CPu drop to 384 Mhz then it froze). Using WMP, TCPMP, & other apps that usually crashes on TAEL v5 did NOT give me the "freeze"
@ 748.8 Mhz FPSEce gives me 5-8 fps boost with no frameskip , with frameskip i can play Final Fantasy Tactics @ 50 fps with no noticable errors (about 29 fps in landscape no frame skip)
Click to expand...
Click to collapse
Im getting with the newest nrg rom the same problems..new calls or sms and the phone needs reset..

The best trick of all its just to overclock your phone to max mhz your phone can stand unlagged and move the shortcut from startup to start menu..So you can use it from start menu only for the programms you want to use..When you finish you make a reset..And everything goes to normal again..In my "normal mode" im using nuedynamicclock for max performance of cpu..From "Battery life" side - nuedynamicclock(max performance)+timolols rom it stands <> 2 days..

New Method, No Freeze in Phone dialer, but battery more inefficient
New Method, No Freeze in Phone dialer, but battery more inefficient
I have tried SetCPUspeed v1.0d & it made the Overclock working BUT i dont know why every time I open dialer screen or an SMS came, it always freezes.
I think it has to do with the fact that WinMo in our TP consistantly checking the speed/ frequency of our MSM.
The only way we can bypass this :
1. When we connect to our laptop (activesync) -- when we connect Raph to PC & it starts sync-ing in activesync, the speed/ freq check disabled, this is an exploit that we can use to overclock safely. BUT..
We do need our laptop / PC to do this (we can't overclock when we're traveling & want to play FpseCE in full speed ^^)
2. THE NEW METHOD -- more battery draining though.. We can bypass the freq check using GPS module. When the GPS is ON, the speed check is disabled. This way, even when we're traveling, we can still Overclock our Raph safely (wont freeze when opening dialer / receivinf SMS.
But, it's still opening GPS module, it's a battery drainer. In my experience it's about 20% faster draining the battery. Use HTC GPS tool & choose "open port"
What i do is :
when the phone is not used (deep sleep), i don't use the Overclock. When i want to use something in my phone & i want to boost it's speed i will turn on HTC GPS tool & overclock my phone to 729,6 (the most stable for me). When i'm done & want to put my phone to sleep, i made my MSM7kCPUSpeed to 604 Mhz (safe speed, wont freeze) & i turn off the GPStool.
When i press the power button the freq will change to 528 Mhz again & the battery consumption became normal again. ^^
It's a turn around from the problem we're facing.. but Hey, i got to play Final Fantasy Tactics @ nearly full speed ^^

b0z0k said:
2. THE NEW METHOD -- more battery draining though.. We can bypass the freq check using GPS module. When the GPS is ON, the speed check is disabled. This way, even when we're traveling, we can still Overclock our Raph safely (wont freeze when opening dialer / receivinf SMS.
But, it's still opening GPS module, it's a battery drainer. In my experience it's about 20% faster draining the battery. Use HTC GPS tool & choose "open port"
What i do is :
when the phone is not used (deep sleep), i don't use the Overclock. When i want to use something in my phone & i want to boost it's speed i will turn on HTC GPS tool & overclock my phone to 729,6 (the most stable for me). When i'm done & want to put my phone to sleep, i made my MSM7kCPUSpeed to 604 Mhz (safe speed, wont freeze) & i turn off the GPStool.
When i press the power button the freq will change to 528 Mhz again & the battery consumption became normal again. ^^
It's a turn around from the problem we're facing.. but Hey, i got to play Final Fantasy Tactics @ nearly full speed ^^
Click to expand...
Click to collapse
Ive played around with the gps issue before. Silly me forgot about simply opening the port in gpstool. I was using google maps till the gps would time out on me.
Without the constant cpu checking, I can safely go up to a much higher speed now! (710. 729 makes sense start to crash occasionally)
Now a few questions I will probably answer myself in the next few hours. Will the gps port ever turn itself off? even when going to sleep? Is there a way to open the gps port at start up? will setcpuspeed work better with this? (turn the check time up to 500, or 1000, not 20 like we were working with earlier?
And the big one.. can we use mortscript to enable/disable the gps port? we could just use our own script to overclock our phones. will look more into mortscript later.
edit: this makes me begin to think this might be a rom issue. what is causing the cpu checks? can anything be done to disable it? i know the blackstone users have a similar issue to us with the cpu checking. any chefs/programmers want to shed some light on this?

Screen Wont Stay On ??? Please help.

I am having a problem with my screen staying on long enough to unlock it. It also happens when in a call and I need to push a number. When I push power to unlock the screen, it only stays on for a fraction of a second then goes out. The bottom row of buttons stays light and will vibrate if i push them but nothing happens. It will do this over and over until finally it lets me unlock the phone. Also when I am on a call and remove the phone from my ear the screen does the same exact thing. Stays on only for a fraction of a second and so on........... This is my third G2X and my first one did this as well. I don't use any kind of lock screen app such as widget locker and when I do try it, it still does the same thing. Anyone have any Ideas???

Are you using SetCPU? I had a similar issue when I set my "screen off profile" in SetCPU to 216 max and 216 min with a priority of 100. I changed it to 312 max 216 min. Now no issues.
Battery seems about the same.

jcbofkc said:
Are you using SetCPU? I had a similar issue when I set my "screen off profile" in SetCPU to 216 max and 216 min with a priority of 100. I changed it to 312 max 216 min. Now no issues.
Battery seems about the same.
Click to expand...
Click to collapse
I do, and I use the same profile you mentioned. I am going to switch it now and try that. Thanks for your quick help!!
(Edit) Yes, that seems to be the culprit. I froze SetCPU for now and problem solved. Now I will change the settings to 312-216. Thanks Again

Happy to help. I am new to this android stuff, but I am beginning to figure things out through trial and error.