yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Apps and Games] BoominSVX:
...HKLM\Drivers\Display or HKCU\ControlPanel\BackLight. Check there first and let us know what you find in those locations.

We all know we can't please everybody. It just keeps us humble, but two pages guys? Glad that stopped where it did. Thank you both for ending it. Lets get back on topic and see where we go with this. As software goes it's still in it's infancy, and like the weather in Florida, if you don't like it just wait 5 minutes.

:)

How bout that "dispon" key saurabh88?
[Windows Mobile Apps and Games] saurabh88:
only three folder in hklm..driver..display...active,gpe &mdde

and on other side so much values but no disp key..(:
[Windows Mobile Apps and Games] cmd512:
Interesting that you're not getting in-call SODs even with the setting at 1... more evidence that this setting might have very little to do with in call SODs at all.

And agreed, especially given our devices' CPUs are constantly changing states, it will be really hard to pinpoint all state change scenarios from one device to another. If you recall back to when the first round of mortscripts that were posted, the script originator felt it was necessary to downclock on phone calls as he was seeing call SODs... even though many people were already using his script without call related SODs and it wasn't even downclocking on calls properly because of that whole registry "Status" issue! That case alone goes to show the elusiveness of these state changes and how timing differences from one device to another can give these SODs enough of a window to show up.

I do have to say though, given the frequency I cycle sleep/suspend states as I don't use a lockscreen, the rare SODs I'd get from coming out of sleep with the Mortscripts have completely gone away with SetCpuSpeed. So, bravo to the author of SetCpuSpeed for sure.

**EDIT**: Found this thread of interest, apparently there are several registry values that must be considered to actually turn off sleep during calls. Check it out: http://xdaforums.com/showthread.php?p=2767033

Agreed. The topic originally posted: The one registry tweak posted previously does not resolve in-call related SODs. If you are not getting SODs in-call with the setting, chances are, you won't get SODs even if it is set to 1/enabled.
[Windows Mobile Apps and Games] smithisize:
Nvm. Should've read first. Disregard this!
[Windows Mobile Apps and Games] manbat:
Working Perfectly Since July 25

================

I've been using this combo since July 25.....Works perfectly....NO SOD ever!! Currently OCed to 710MHz, but is stable higher!! It works...so I haven't tried any other method.
[Windows Mobile Apps and Games] cmd512:
Yeah, I'm considering going back to the Mortscripts myself. After having the proper binds to the power key, I stopped getting SODs from power cycles and never had issues with the in-call SOD's. Decisions, decisions...
[Windows Mobile Apps and Games] SpinalRemains:
I also have been no SOD since July. I have been using OC Auto2 for prolly about a month now. (No button mapping tho) I have been solid stable at 748. The only hiccup I did have was when after a phone call a week ago, I noticed the OC reverted back to 528. I have no idea why. I simply reset and it's never done it again. I have made and received many many calls both with me hanging up first and vice versa and have not had SOD. I think the scripts work very very well. It seems that they have had the most success thus far when using the Rhodium (TP2). No GPS issues at all either as some mentioned with Blackstone devices. If the phone wasn't snappier, I wouldn't even know the script were there actually. I never reboot my device since no SOD so I don't mind the 2 minute boot time. I have been really loving the results thus far.
[Windows Mobile Apps and Games] Doo Doo:
i was using oc auto2 for awhile 2 but upgraded to oc auto4.1 with gui & have had no sod's either

Bold = Agrees 100% :D:D:D
[Windows Mobile Apps and Games] cmd512:
Just reinstalled the StartUp script + power key bound scripts. Will use this for a week to see if I get SOD free as well. :)
[Windows Mobile Apps and Games] Doo Doo:
why do you use the power key bound scripts?

i just use the oc auto4.1 w/gui script & it works just fine i been using the 1 script method since nayr1482 made the first 1 & upgrade everytime he makes a new 1 & never had 1 single sod :D
[Windows Mobile Apps and Games] derride8:
hi Doo Doo.

I also use core cell v3 for my t-mobile touch pro 2. Can use share the .cab you used to overclock my phone successfully.

Thank in advances...:D
[Windows Mobile Apps and Games] Doo Doo:
this is what i been using to overclock my phone no cab though just follow the directions at the bottom of the post

http://xdaforums.com/showpost.php?p=7471088&postcount=1147
[Windows Mobile Apps and Games] cmd512:
Because I don't use a lockscreen and power cycle almost exclusively to "lock screen," which means I do a lot more power cycles via the power button. This is why I saw SODs with the power button depression when others didn't during the "mortscript era."

So, it's more like a precaution for me, especially since I use the power button so much.
[Windows Mobile Apps and Games] o.k.:
Does the combination Msm7kCpuSpeed + SetCpuSpeed work on battery powered Blackstone?

Strangely enough, I have read the posts confirming the same, but in my case the device freezes right after starting SetCpuSpeed.exe whatever I write in the registry (on battery)...

I can assume it is ROM dependant. Does anyone has experience with ROM kwbr 3.5 (WM 6.5 com2 + sense 2.5)?

Thanks in advance.
[Windows Mobile Apps and Games] SpinalRemains:
I don't use a lockscreen either and the SOD is never there without buttom map to power key. I use the power button an awful lot and I don't think it's needed at all really. On an average day I might induce sleep and turn on about 60 to 100 times. Maybe our phones are different, but I just figured if you don't have to use the button remap, why bother then? It adds lag to the power key.
[Windows Mobile Apps and Games] SpinalRemains:
I just discovered something new concerning using Nayr's scripts with cleanRAM config. In order to prevent SOD if you use cleanRAM, you must leave your advanced/GUI on "disabled". I just tried changing it to TouchFlo 3D and after reboot and then a sleep my phone SOD. I changed it back to "disabled" and script is working fine again. It seems that the cleanRAM GUI options definitely interfere with how the script works. I don't know why, but i am just throwing found data into said pot. Perhaps some with SOD and script are using cleanRAM selected GUI?
[Windows Mobile Apps and Games] gpshemi:
Is there still an effort into a V3 or a nice simple one stop cab for this?

I run MightyRom 6/20 and had this installed and was seeing SOD to the point of making it un-usable. Even after I uninstalled it left my phone buggy. Reinstalled MR and now I'm back to square one, but I swear I'm not as stable as I was once.
[Windows Mobile Apps and Games] SpinalRemains:
your phone doesn't run the same after uninstalling NetRipper's OC app? That's weird. What's the device doing differently now?
[Windows Mobile Apps and Games] RoboWang:
Everyone's system is different.

I use the script and have had ZERO SOD's in 5-6 days. And I use Clear Ram 2x a day.

Have been using the scripts since mid July, 2-3 SOD's at max.

My phone runs 748 clean. Not a hiccup or even a slowdown with NRG MaxSense w/Buuf theme. And it FLIES! page to page, tab to tab, app to app. Smooth and fast.

I won't go back to cookie.

Lately, I restart/sleep a lot because I am still adding the Buuf to my phone.

But, I read about others with similar phones (Tilt 2) that are having fits with this.

As with any OC system, luck of the draw. Or timing issues in the software that I don't use, but others, do.

I have a feeling that I could get stability at higher clocks, since it's so stable, now, but I think I will stop here.

SO FAR, it's all good.
[Windows Mobile Apps and Games] cmd512:
There is 0 lag to the power key, I use it all the time so I'd know if there was.

And again, what we've proven is that SODs that don't show up on one system may very well show up on another. (Read back to my previous post about how the originator of the mortscripts put in downclock for phone calls because he saw SODs... even though plenty of folks never get phone call SODs without downclocking!) To put it plainly:

1) Comes down to which software set you're running... ROM, background apps, etc.

2) How those apps affect the timing of your processor changing states going in and coming out of sleep mode.

3) Depending on that timing, it can either increase or decrease the chance of SODs.

4) Of course, if you power cycle more with the power button, you're just increase the change of hitting that timing cycle just right, but ultimately, that comes down to how big of a window you have.

Another way to look at this... the main StartUp mortscript is basically an infinite while loop (see the while(0) command). Basically, at a given iteration of time (I'm thinking 200~1000 ms), it will run the loop, check the state of the phone, change the CPU speed accordingly, or do nothing (sleep (1000)). This is in essence what the script does.

If you understand that much, then imagine the following scenario: Right when you go to press the power button to put the phone to sleep, your phone starts changing all the states (display, processor, etc) to put it to sleep. However, what if after you depressed the power button but before the sleep states have been fully registered, the while (0) loop processes one more time. And because the sleep states haven't been fully registered, it still keeps the boost speed OC. And, when your phone suddenly changes states, chance of SOD.

I hope this addresses the "why do you have SODs when I don't" discussion... it has nothing with an unstable overclock and everything to do with timing. This is why SetCpuSpeed was the correct solution to the power cycle SODs and why I never got sleep SODs with it: it actually waits for the sleep state event to be called, downclocks accordingly, and only after that does it allow the sleep state to occur. Unfortunately, mortscript has no way to catch sleep state calls.

BTW, it's interesting to note, after binding the forced downclock to both before AND after power button cycle to sleep, it stopped the power button induced sleep SODs... which does fall in line with my theory. If it hasn't happened to you, great, maybe with the software config you're running, that window is so tiny you'll never see it come to fruition. But, that does NOT mean SODs can't occur. (I mean, even with the power button binds, there is still a chance of it happening, but I've just reduced it even further.) Ultimately, if you understand how the script works and how it relies on an infinite loop, you'll understand why SODs are still possible, and why some folks do still see them.
[Windows Mobile Apps and Games] SpinalRemains:
@ Robowang,

Oh ok. Just out of curiosity though, which GUI/shell do you use with cleanRAM?
[Windows Mobile Apps and Games] RoboWang:
To be honest, I don't know what you mean. I have only used one version of this app, and it works well for me.

Here is a zip with cab and info.
[Windows Mobile Apps and Games] pf:
Looks great! Thanks for your work on this!
[Windows Mobile Apps and Games] Gyokumen_Koushu:
Failed ---> Changing clock speed on battery

Works --> Changing clock speed on AC

My Experiment

===========

Clock to 710MHz

Works superb

Unplug AC

Check clock speed --> Remains at 710MHz

Play Quake

Play Tony Hawk

After like 40 minutes mark, games play become lag.

Recheck clock speed dropped to default clock.

RAWR. Hopefully you can identify what makes WM to reset clock while on battery juice. Thanks NetRipper. Cool app!!!
[Windows Mobile Apps and Games] 3x4d:
This is not the driver problem !?! :mad:

I am with XPERIA X1i:

Radio version 1.16.25.48

CPU 7200A

Win: Valkyrie FireStorm v6.x - I can’t remember exactly the version

and I have this problem:

Then I decided to try with other ROMs:

1. Valkyrie XPERIO v6.3.21898

2. Valkyrie XPERIO v6.3.25010

3. Energy.XPERIA.23569.Titanium.Jul.14

4. Christian_WWE_5610_Clean

5. GENERIC UK R3AA010 with Radio version 1.14.25.55 – the original ROM

The problem still is same …. :(

Any ideas haw to solve it :confused:
[Windows Mobile Apps and Games] Qzytor:
See this post no.1191 in this thread, try it out,it might help you.
[Windows Mobile Apps and Games] 3x4d:
:eek:

Now when I starting the MSM7kCpuSpeed, it change speed non stop from 672 on 528 and again 672 ....
[Windows Mobile Apps and Games] prboy1969:
Hey has anyone heard from NetRipper ? Where is he :confused: ? Creates awesome app then ... What's up NetRipper ? Let us know your ok . When's the next version of Msm7CpuSpeed due ?

BTW been a while now since I've had an SOD :D .
[Windows Mobile Apps and Games] miked79928:
Curious

What is the highest speed everyone has clocked thier GSM Rhodium to? I am using the T-Mobile TP2 version with the ROM in my signature and can get as high as 787.2, but the device hangs eventually. Anything higher results in an instant freeze. Luckily I am stable and fast at 768 :cool:
[Windows Mobile Apps and Games] maan1976:
that is exactly what Iam getting onCDMA TP2

768 no freeze

787 freeze
[Windows Mobile Apps and Games] b0z0k:
Touch Pro Running 768Mhz

TP100 Using TAEL v5 (6.5.5 -23569)

Succesfuly OC'ed to Max 787Mhz, Using Guide from post 1191 :

@ 806, TP always reboot or instafreeze

@ 787, sometimes i got the instafreeze

@ 768, generally works fine, with couple of bugs :

1. @ any speed (from 32-633Mhz to 40-768Mhz) CorePlayer & WMP always hangs when playing video.

2. @ any speed (from 32-633Mhz to 40-768Mhz), Teeter works until i got to next level & it freezes

2. @ any speed (from 32-633Mhz to 40-768Mhz) When i receive SMS, and i tried to open/close it, It freezes

3. @ any speed (from 32-633Mhz to 40-768Mhz) Using phone dialer, @ any speed My TP freeze.

Before today i only installed the Msm7kCpuSpeed V.2, it can't OC using battery (always return to 528 even when i click 604 Mhz) I tried in my charger (using not the original TP charger but with the sampe voltage & Ma) but still no-go. (maybe because i dont use original packed charger)

I tried using USB port (with original USB cable) & OC works up till 806 when connected to Laptop & can only be unplugged in 604 Mhz freq.

Using the instruction above (post #1191 i can OC even on battery) but with the bugs mentioned above.

thx 4 NetRipper & all other that support this app ^^
[Windows Mobile Apps and Games] eXceed:
787mhz on rhodium T7373 (touch pro 2) for nearly 2 weeks now. Currently using OC_Auto4.1 seems the most stable for no SOD for me. setcpuspeed stopped working in eliminating SOD for me so was happy when simply changing to OC_Auto seemed to work for me.
[Windows Mobile Apps and Games] saurabh88:
me too at748mhz
[Windows Mobile Apps and Games] Kaspa Lekouy:
This one is working fine on my Topaz too, with a 6.5 official rom.

Many thanks dude !

:)
[Windows Mobile Apps and Games] FL5:
Max Stable Speed

I guess I'm one of the lucky ones for being able to run stable @ 806.4 (Tilt2). Using v2 & setcpuspeed1.0d along with changing the reg key to keep the phone from sleeping during a call, I'm still averaging 1-2 SOD's a day, but it is so incredibly worth it. I am running Sense 2.5 with Co0kie's home tab (rather stripped down, but still nice) and it is not totally always without lag, but it's still very nice and usable.

So who else has been able to run steady @ 806.4? Has anyone been running stable at anything higher?
[Windows Mobile Apps and Games] cmd512:
Now that I've switched back to Mortscript instead of using SetCpuSpeed (btw, no SODs yet!), another big difference I've noticed:

SetCpuSpeed seemed to induce pretty significant battery drain while there is almost no difference between OC and non-OC battery life when using the Mortscripts. At same OC and non-OC clock settings (729/604), SetCpuSpeed would leave my device gasping for juice after a day. In fact, there was one evening where the phone completely died on me mid conference call... which has never happened since I've owned this phone. Now that I'm back on Mortscript, I still had a very healthy 45% battery life remaining even after a very heavy day of use.

Now, this makes absolutely no sense to me given SetCpuSpeed waits for sleep state calls to activate while the Mortscript is continuously running an infinite while loop. Logically, one would expect the Mortscript to induce more battery drain, but it's actually the other way around! So, I thought maybe one of you script/code guru's can shine a bit of light on this discovery...

=========================

Also, for anyone who might care to, I've added the script pack I'm currently using that seems to have resolved the in-call SODs I experienced with SetCpuSpeed. Setup is simple...

1) Have to have Msm7kCpuSpeed v2 installed of course.

2) Startup.mscr goes to \Storage Card, down.mscr & down2.mscr goes to device root (\).

3) Create a shortcut to Startup.mscr in your \Windows\Startup folder

4) down.mscr & down2.mscr are bound to the power button via Rhodium Keyboard Config v1.4 using a down.mscr -> default action -> down2.mscr sequence. To bind the scripts, choose "Run application", select mortscript.exe in your \Windows folder, and do "\down.mscr" for before the default action and "\down2.mscr" for after the default action. Oh, and make sure you check "Emulate key press" when you select "Default Action."

This will effectively OC your device to 729MHz and throttle to 604MHz during calls or sleep (power button and timeout).
[Windows Mobile Apps and Games] timjarsky:
step 4

Hi cmd512,

I don't know how to follow step 4 of your instructions. How do i access Keyboard Config? Is that the same as button control?

I was running setcpuspeed with MSM.... and got too many sod's on phone calls. Editing the registry to prevent sleeping stopped this issue but i got the impression that the battery was being drained significantly more quickly.

Thanks.
[Windows Mobile Apps and Games] cmd512:
**You need to be using a Touch Pro2/Rhodium for this to work**

Hope this helps:

1) Download & install v1.4 of this: http://xdaforums.com/showthread.php?t=554240

2) Check out these 2 threads on finding out how to bind actions before and after a power key default click:

http://xdaforums.com/showpost.php?p=7324282&postcount=509

http://ip208-100-42-21.static.xda-developers.com/showpost.php?p=7364186&postcount=659

**IMPORTANT**: Make sure to select "Default Action" for any other power key behaviors as you don't want to lose those (long press, 2 click, 3 click). Also, whenever you choose "Default Action," make sure you check the "Emulate key press" box.
[Windows Mobile Apps and Games] prboy1969:
Well now that proves your point about these devises having a lot of variables . I got the opposite results with scipts :confused: . For the most part , no SOD's . But I'd say about 25% of the time I would get SOD's after the device went to sleep . If I pressed the power button after a long sleep also . Now that I'm using Msm7CpuSpeed & SetCpuSpeed.10d , it has been well over a week with no SOD's :D . :confused::confused::confused: . But I guess you just have to find what works for your particular application .
[Windows Mobile Apps and Games] jdogg4000:
I have done this on my Xperia X1 with the X2 Ported Rom Overclocked to 672 Mhz. Froze when I tried 692Mhz. Everything seems to be working smoothly still have to check GPS and Wifi but so far its good!

Thanks!
[Windows Mobile Apps and Games] NetRipper:
Well, obviously you didn't read _all_ notes, as there were some benchmark results posted already.

If you hadn't noticed yet, that exe you find in that thread, was also made by me.
[Windows Mobile Apps and Games] Maxx134:
Hey quick comment.

I noticed after overclock set, that if I exit program and let unit fall asleep I get SOD on battery, BUT...

If I leave your program running in background WITHOUT closing, the "error notification" message I get about your app crashing STOPS my unit from SOD!

:)

In case it is helpful, the "Argument Exception" details in this "error notification" says:

at

Microsoft.AGL.Common.MISC.HandleAr(PAL_ERROR ar)

at

System.Windows.Forms.Trackbar._SetInfo(AGL_TRACKBARINFO& tbinfo)

at

System.Windows.Forms.TrackBar.set_Value(Int32 value)

at

Msm7kClockGui.MainForm.UpdateCpuFrequency()

at

Msm7kClockGui.MainForm.timerCpuFreq_Tick(Object sender, EventArgs e)

at

System.Windows.Forms.Timer._WnProc(WM wm, Int32 wPparam, Int32 IParam)

at

System.Windows.Forms.ApplicationThreadContext._InternalContextMessages(WM wm, Int32 wParam, Int32 IParam)

at

Microsoft.AGL.Forms.EVL.EnterMainLoop(IntPtr hwnMain)

at

System.Windows.Forms.Application.Run(Form fm)

at

Msm7kClockGui.Program.Main()
[Windows Mobile Apps and Games] Alcibiade:
When do we get a new app allowing us to crank a few notches higher ? :)

I doubt even one more will be stable but I can't wait to try
[Windows Mobile Apps and Games] Maxx134:
Hey netRipper, I found a way to stop the SOD, but it is not a cure, just a bandage.

Will post a cab of the reg-fix in a few after I make shure it works! lol

EDIT:

Reg worked but now not sticking.. will pm results instead.
[Windows Mobile Apps and Games] kroniced:
the TP2 and the rest of these devices that have this CPU don't have a GPU I belive. It is using the main CPU for everything. So if anything that guy joking about needing glasses to soldier in more RAM would have made more sense if he said solider in a GPU. Also RAM runs at a certain frequency and can be changed on some systems. That is overclocking RAM, adding RAM is just increasing the amount.
[Windows Mobile Apps and Games] vorob:
Ye, i was wrong, after my device go sleep, clock is back on its default value, on battery.
[Windows Mobile Apps and Games] vorob:
Tested in FpseCE 0.10 (psone emul) from battery,

in wipeout on stock clock there was 26fps, and on 710 it was 36 fps :)

So, i can officialy confirm that this application (msm7kcpuspeed) works on HTC Diamond II
[Windows Mobile Apps and Games] deveb:
The same. Tested on most popular ROMs (Energy, EVO, Cloudy, BlackSTONEhenge etc.) and on radios 1.14/1.17, HSPL 1.56
[Windows Mobile Apps and Games] Maxx134:
If you guys are willing to take a chance AND not blame me for losing anything, I will post you the 3 regkeys to delete to see if that solves your issues.

Currently testing and having good results for SOD which I believe is related to your problems.
[Windows Mobile Apps and Games] deveb:
Okay, no problem, I can try it ;)
[Windows Mobile Apps and Games] Alcibiade:
There is a GPU. The issue with HTC is they didnt provide 3d driver and most of graphics are rendered by the CPU (However you can fin custom made drivers on xda)

As far as memory is concerned I d love to speed it up. it s often easier to overclock than procesors, can yield very good rsults with very little power consumption impact

But it's another debate for another software
[Windows Mobile Apps and Games] Alcibiade:
What do they do (or control) ?
[Windows Mobile Apps and Games] syncronizer:
Bad news for me..overclock on AC mode..more than normal freq bring my blackstone to SOD.. Spec : Stock ROM 1.56.00 wm6.1. Any solution to solved this?
[Windows Mobile Apps and Games] matt12eagles:
This is amazing guys. The developers on XDA and PPCgeeks are always amazing. I've been wishing for this app for almost a year and it finally comes to bring new life into all of our devices. Thank you so much for all your time and effort into this app. Right now i experience the SOD issue almost always.. but i hope intime it will be fixed for my Verizon TP2. Thanks so much!!!
[Windows Mobile Apps and Games] toadlife:
Please share! You can PM me the keys if you like.
[Windows Mobile Apps and Games] Maxx134:
My results are no longer conclusive, but I am still working in the area in registry in:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power
[Windows Mobile Apps and Games] shaolin95:
PM me the keys please I will try it.