yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Apps and Games] 5318008:
Anybody else with an X2 that can confirm it stably OCs higher than the Rhodium?

If so, maybe I'm using the wrong phone... X2 for Rhodium, anyone? :rolleyes:
[Windows Mobile Apps and Games] kain144000:
Here's what works for me, and I'm at 768 MHz, 604 MHz sleep, and no SoDs...

1. download Msm7kCpuSpeed v2 here

2. download the original SetCpuSpeed v1.0 here

3. make the following regedit ...

[HKEY_CURRENT_USER\ControlPanel\Phone]
"Sleep"=dword:00000000

4. here's my registry entry for Msm7kCpuSpeed/SetCpuSpeed (values are HEX)

[HKEY_LOCAL_MACHINE\SOFTWARE\Msm7kCpuSpeed]
"BootTime"=dword:00007530 (DEC:120000; 2 minutes)
"CheckTime"=dword:000000c8 (DEC:200)
"Command"=dword:00000000
"PerformanceLevel"=dword:00000028 (DEC:40)
"ScreenOffPerformanceLevel"=dword:0000001f (DEC:31)
"SettlingTime"=dword:0000000a (DEC:10)

If you'd like your device to overclock at boot, add a shortcut to SetCpuSpeed to \Windows\Startup, and for a wait time for SetCpuSpeed to start, add the /boot argument. The "BootTime" entry I've shown gives me a 2:00 window before SetCpuSpeed starts; ample time for me to boot android with Gen.Y DualBOOT. So, if you don't use the program, you can leave that value as-is on install. Or, you can change it to mine as a safety precaution, or whatever. Now, you may need to do some testing to see what your device OCs to stably, as you may have to lower my value, or, if you're an UBER–F*&%IN'–LUCKY SCHMUCK‼, you may be able to increase the value. I, personally, lock up after 768 MHz, but at 768 MHz, I'm cool as a cucumber.
[Windows Mobile Apps and Games] Lagz0ne:
work with whitestone :D
[Windows Mobile Apps and Games] tsalta:
Blackstone Overclock

Thanks to Netripper, oruam57 and Qzytor for providing his tut how to overclock Blackstone on Battery.

I try the methood and its seems that work perfect for me.. i overclock befor 2 hrs and till now all seems super. The phone is alot more faster, fast responsive and no need time apps to load... also i do not notice any heat of the device when i make calls or do anything other, i do a benchmark and this is the results

My results are :

SKTools Benchmark at 672 MHz

Integer 420.1011

Floating point 9.633

Note when i do the Bench i forgot ON my WiFi but the result is still GOOD and i can see faster UI and everything.

Edit: The side effect is after the Overclock my Battery is Eating like hell... very very fast so i think if i need to run on 672 Mhz i need to recharge my device every 12 hrs or maximum 24 hrs depends from the usage.. normaly without the Overclock my battery is very well

So now the phone work on 672 MHz without a problem, i think that this overclocking is very dangerous and bad for our devices? or not at all? I don`t know tha answer for this reason im asking you here guys. So what can heppand if i use my device at 672 MHz for everyday use for example.. or this is not so big diference and will not harm the Proccesor?

Also my question is if i want to go back to default what i should do? step by step.

1st to take out the SD card and reset the phone, then edit the regs back to default and uninstall the Msm7CpuSpeed from the phone, then softreset and after the phone load inser in the SD card then uninstall the SetCpuSpeed 1.0d cab and again soft reset.. is that corect? and after a reset the phone will be back to default settings?!

Thanks in advance
[Windows Mobile Apps and Games] BikerBoy030:
1. Overclocking COULD damage your hardware...

2. Of course, overclocked Hardware has got less lifetime than normal clocked hardware, but i think no one will use his touch pro / hd etc more than 6 years, so you will not feel the different in lifetime.

I overclocked my QTEK S200 for a long time and after 5 years of usage (overclocked about 4 1/2 years) it also works fine.

Also my overclocked Hardware in my PC or in my laptop...works fine after years of usage.

So you have the danger, that the hardware COULD be damaged or the lifetime is decreased...but i think you will not see a different in lifetime..because you will buy another device, before your hd will be destroyed;)

So you can overclock your device if you like the speed.

For my Touch Pro:

I love the speed, wich can reach with this software (710Mhz @AC) but i can not overclock my device without AC, maybe someone can fix this problem, so i can sell my Acer S200 and can go back to my Touch Pro (because i love the Hardware Keyboard) :)
[Windows Mobile Apps and Games] hartleyshc:
Anyway to close the app/scripts when another app is running?

My phone app locks up when either overclocking program is running. Even if Im running at stock speed.

Running the latest energy rom aug6th on my TP. IIRC its the leo phone canvas. Does anyone know if switching phone canvases will fix this?

Other than the phone app, it works flawlessly except when I need to make or receive a call.

@bikerboy look at the reg edits for blackstone. we need to set the check time down to at least 35ms (set at 20 in the notes) to prevent the constant back and forth clock speeds on our TP. Then you can run on ac or battery. also note that the iwfratz version does not have this back and forth problem. But as my problem listed above, its all good till I use my phone as a... phone.
[Windows Mobile Apps and Games] ZaxXx:
My Blackstone is stable at 691,2 MHz :) You deserve a HUGE THANK YOU!
[Windows Mobile Apps and Games] Alcibiade:
So his phone will never go to sleep, correct ?
[Windows Mobile Apps and Games] eXceed:
I have an old AMD Opteron 175 overclocked about 40% on watercooling that has been running nearly non stop since the CPU was released. Can't even remember how long that was ago so I'm not especially worried about damage from overclocking :)
[Windows Mobile Apps and Games] Alcibiade:
X2 is more recent than Blackstone. It's very likely the producing process of teh processors we are using ahs been improved and it's easier to overclock them
[Windows Mobile Apps and Games] hartleyshc:
correct. the screen will still turn off, but the phone wont go to sleep while using the phone app.

exactly. not to mention these chips are only tested at the 528 speed. a low quality chip can still handle 528 fine and be shipped out on a phone. (explaining lower overclocks for some)

as for my phone app problem. Ive located it to how often the app checks on the clock. if i set it too low, the phone app freezes, if i set it too high, I get the constant back and forth of the overclock and stock. looking to remedy this problem. I think I could fix this is i could change the checktime to 1000ms for 528 and then 20-150ms for when its overclocked. But then again, it would be overclocked while on, and would still freeze the phone app. Again, I think I might have to close the scripts/apps when the phone app is used, and resume after phone calls.
[Windows Mobile Apps and Games] MrBeOTP2:
quick quest from noob :D

HAVE any damages from OVERLOCK on device ??? ??? ??? ??? ??? ??? ???
[Windows Mobile Apps and Games] cmd512:
Confirmed this registry does not help the phone call SOD issue. Sometimes after a phone call, my phone still needs a reset.

I've noticed I never have this problem after speakerphone calls and only regular "phone-to-ear" calls. So, I'm almost 100% sure the SOD occurs after the phone call hangs up but before the screen comes back on from the proximity sensor.

To get around this, I'm going to try and make sure the screen is on before I hang up. Let's see if this gets rid of the phone call SOD's.
[Windows Mobile Apps and Games] Vbeaucher:
As anyone noticed that the green phone button on the TP2 no longer seems to work since having installed SetClockSpeed? Actually, I think it put the phone in Silent mode, since you have to use the slider in the screen to answer. Any thoughts?
[Windows Mobile Apps and Games] 5318008:
Try it and find out.
[Windows Mobile Apps and Games] buru898:
I don't use NetRipper's anymore, it seems that iwfratz's program is getting more done. For one thing he already has dymanic clocking finished lol and no SoDs ever. Only thing is it only works for TP2's that have the msm7200, not msm7600 chipsets.

But where is Netripper anyway :/?
[Windows Mobile Apps and Games] Doo Doo:
yeah but how high can you overclock on iwfratz's program?

isn't it set to only overclock to like 652mhz?
[Windows Mobile Apps and Games] detule:
Unless I am mistaken, this is only partially correct - this registry tweak prevents the phone from "going to sleep" in the midst of a phone call.

My CDMA TP2 does not suffer from the issue you describe - SetCpuSpeed(1.0d) in conjunction with the registry tweak has completely resolved all and any SOD issues. (Though I will grant you that, it is possible I have yet to encounter the specific scenario you describe.)

I have played it relatively safe though, keeping my phone at 729. For a few days now, phone is blazing fast and rock solid - even during phone calls of various lengths.

Running Vin's 8/5 Pluto CHT.
[Windows Mobile Apps and Games] detule:
Just tried to replicate the scenario you describe. Perhaps the following info will help you debug your problem: In my case, as soon as the phone call ended (other party hung up) the screen automatically came back on, regardless of the fact that the proximity sensor was covered. This I am sure is a feature of the Phone, the proximity sensor is inactive unless there is a phone call in progress.

Hope this helps.
[Windows Mobile Apps and Games] cmd512:
Yes, I know this feature exists. But you need to understand that oftentimes during business calls, when there are multiple parts on the call, people will hang up before others. And, if the phone is still pressed up against my face, it won't turn on from time to time.

Actively tracking when to remove the phone and check to get the screen to come on is not the fix.

And BTW guys, it's inaccurate to say this registry setting completely solves the phone sleep SOD issue because it clearly doesn't. Plus, just because a few folks says it does doesn't make it so... all it takes is 1 SOD to prove this. And, I have had a few SOD's after phone calls where I only used the phone so I KNOW this is not a real fix. Let's move on from "oh, I don't get SOD's" to let's find a real solution to this problem.
[Windows Mobile Apps and Games] buru898:
Yeah for now, he released a new version today letting you underclock as low as you please... don't know why he just doesn't remove the cap already? But he released a readme that allows you to make use of dll and make your own program that runs off it so you could remove the cap yourself... but I'll just wait until he decides to do it lol.
[Windows Mobile Apps and Games] oruam57:
Do not do that, you would only lose time, limit is hardcoded in the dll.
[Windows Mobile Apps and Games] buru898:
Oh aww haha alright thanks for clearing that up oruam :).
[Windows Mobile Apps and Games] unxguyjr:
I am running with the latest OC_Auto for over a week at 710 with no SOD. But I wanted to see if anyone has had the issues as me...When I run google maps of Sprints Navigation I can not get the GPS to work but if I exit and switch the CPU down to 604 via GUI I can run GPS fine (this is all on battery have not tried w/power)...again just curious...its kind of a pain while driving to do all the switching so I can figure out where I need to go.
[Windows Mobile Apps and Games] 5318008:
Yeah, like buru88 says, he plans on removing the cap further down the testing timeline. Not soon enough for me though, I like the 768 I can get with NetRipper's, though ATM I'm still using iwfratz's. Sorry to be off-topic a bit, I know this thread is primarily for NetRipper's app.
[Windows Mobile Apps and Games] detule:
Yes, this is clearly the scenario you described in your original post - and the same scenario I tested on my device: the other party hangs up before you do and then you uncover the proximity sensor. You can try and write it down one more time, but I feel like it won't change much from one post to the next.

Of course not, when I replicated the scenario above I had my finger on the proximity sensor for the full 2 minutes of the duration of the call (sleep setting on my device is 1 minute,) and the screen remained off. As described previously, when the other party hung up screen came back just fine.

You should not get so upset when other people report success on their devices, where your device fails - if it works for them (us), then let us report our findings without hindrance. Besides, I just invested some time trying to reconstruct your scenario on my device and came up blank. So no need to blast the method until you can demonstrate the failure repeatedly.

Incorrect, all it takes is a sequence of steps that cause a failure that manifests on multiple devices. Until then, it could be something specific to your handset, or a product of instability due to over-clocking too high.

And I have had no SOD's after phone calls on the Rhodium so I KNOW this is a real fix - you see where silly statements like that are headed right?
[Windows Mobile Apps and Games] cmd512:
Wow, clearly you're one of those "let's argue on the internet cuz it's cool!" people. So, I'm not going to divulge you.

All I need to say is, I used the mortscript routine running the same OC speed before SetCpuSpeed and with the in-call downclock, I never had a phone call SOD. I do now, that's proof enough this isn't fixed with the registry setting.

You can spout on about all the goofy tests you did to prove it's fixed, but it's not. I know, it is really upsetting that I don't agree with you, and you'll probably lose sleep over on how to best respond with an essay addressing every one of my sentences. But hey, you gotta get your kicks somewhere, right?
[Windows Mobile Apps and Games] detule:
Ha, fine, don't divulge me.

Sigh, again, no it's not.

Hey buddy, no need for the hostility. If you want to have monologues, perhaps you should not post online. When you do, other people will scrutinize what you post, and when you post non sequiturs, you should expect other people to say something. It's nothing personal, it's part of the learning process.
[Windows Mobile Apps and Games] cmd512:
You're so wrong you have no idea. No, not all issues are repeatable, especially when you're talking about clocks, frequencies, and sleep states. If you don't think intermittent issues exist in the electronic world, then you clearly have no clue. Just like sleep SODs were intermittent when scripts didn't address them completely (yes, sleep didn't cause SOD every single time), same with the phone call issue. I have gotten them with SetCpuSpeed, but very rarely at that. With that said, am I going back to scripts which seemed to not have this issue? No, because I don't fully believe scripts address the sleep SOD that SetCpuSpeed has 100% resolved. For me, having a bit of control on the phone state by ensuring screen's on before I end a call vs not knowing when your phone might come out of sleep makes that an easy decision.

And you're right, this isn't about monologues, if you want to discuss this, let's discuss. But don't bother posting any more feedback if you're convinced this issue is fixed, because if your mind is made up, what's the point? In the world of failure analysis, 1000 passes doesn't mean an issue is fixed, but 1 failure definitely means the issue isn't fixed. That's just the way it is, feel free to dissect and disagree all you want.
[Windows Mobile Apps and Games] detule:
Fine, all I said is, don't get upset when other people (like me) report no problems one way or another. Also keep your cool when people perform "goofy tests" trying to help you out and "sprout on" about their findings (how ungrateful.) Claiming you KNOW the issue is not resolved, when you seem to be an outlier with the problem you are describing lacks all logical foundation. There are other ways to convince people to look into the problem your device is experiencing, other than convincing experts (not me) that there is some underlying issue that everyone needs to consider ASAP.

You do realize that this reasoning is very flawed right - I mean you can't possibly believe what you've posted right?
[Windows Mobile Apps and Games] Alcibiade:
Exactly... And that's why it's the first thing he should have mentioned him... When posting a regedit as an advice to a beginner, that has this kind of implications (potential reduced battery life, heating of the device, etc...) I think this should be explained... Anyway...
[Windows Mobile Apps and Games] cmd512:
You clearly are not from the world of failure analysis or technical troubleshooting. You have no idea the number of times I've dealt with intermittent PCI bus issues that required a bus analyzer to pinpoint down because our customers were claiming failures such as systems won't boot, screen distortion, etc, but no number of duplication efforts could reproduce it. In the end, it turned out because a particular command that was issued when a bus cycle was either up or down caused the issue, but unless that timing was perfect, you would never see it.

I could have gone back and said "you're crazy, the issue doesn't exist because I've run 1000 test cycles and it doesn't happen." That's not how electronics troubleshooting works.

Same with the call or sleep state SODs... these are timing dependent. On your system, you might have a certain program running in the background that's causing your clock cycles/states to be completely different than those on mine. But, the fact that my setup produces SODs after calls (albeit rarely) doesn't mean the failure is caused by my setup or system. Why? Because when I'm not overclocking or when I was downclocking with mortscript during calls, phone calls never caused SODs. So, the failure is not my setup or config, the failure is still directly related to the screen off/call event. Getting it now?

Seriously, if you understood clocks, sleep states, electronic intermittent issues, this would be easier for you to comprehend. You don't, so we'll just leave it at that.
[Windows Mobile Apps and Games] Alcibiade:
Exact. The solution is here

http://xdaforums.com/showthread.php?t=698374

But I ma sure you already know that. A few more adjustments and the soft will be perfect )no SOD for me so far, but it doesn't allow to overclock high enough)
[Windows Mobile Apps and Games] detule:
Rather than spray about my credentials as a top notch technician (really? you are so proud of this that you need to share?) let me just ask you this - do you think all processors that come out of the Qualcomm assembly line pass quality control? And when you answer "No, some of them fail, maybe even one in a thousand", ask yourself, is this indicative of some sort of an underlying problem that all processors suffer from, because this is what you are saying in this quote

I see. You have disarmed me with your intellectual barrage so I will vacate this discussion - I don't want you to bruise my ego some more.
[Windows Mobile Apps and Games] detule:
Wow, it seems people have a vested interest in pushing one solution over another but this paltry bounty can't really be it, right?

At any rate, I want to thank all the developers who have put their time and effort in making over-clocking not only work, but work seamlessly. In all honesty, it has rejuvenated my TP2 to the point where I find myself pulling it out of my pocket just so I can enjoy how smooth the sense (and CHT) interface is, and/or how fast apps load.

I am sure there will be more issues down the road, but even if development stopped right now I feel like we are deep in the gravy zone.
[Windows Mobile Apps and Games] cmd512:
Agreed, this tool is fantastic, and I'd say we're 90% there. I've had probably 3 or 4 SODs from phone calls since I've started using SetCpuSpeed, which is pretty amazing given I use my phone extensively for business. So, it's not that big of a concern.

Even more important, I do use the power button to sleep the phone instead of using a lockscreen, so the fact that SetCpuSpeed got rid of sleep SODs completely was the biggest hurdle!
[Windows Mobile Apps and Games] cmd512:
Lol, what? Quality control has nothing to do with failure analysis. You really are clueless, I don't even know why I tried.

QC: Controlling processes to ensure you minimize chance of failure. QC is not the absence of failure.

Failure analysis: Finding root cause of failure, which means you can adequately prove that no states will result in failure. You have not done this, and I have proved even with the registry setting on my device, phone calls and only phone calls will cause SOD.

This issue has nothing to do with quality control, thanks for trying though.
[Windows Mobile Apps and Games] detule:
Dang, I just can't let you get away with this.

Perhaps not, but it was a perfect counter example to the claim you were making "1 in a 1000 means there is an unresolved issue." Would you like me to write you a few more lines on the topic or can you connect the dots on your own? I don't want to put you through too many more uncomfortable arguments.

You are very welcome.
[Windows Mobile Apps and Games] cmd512:
Uncomfortable? Not at all, I just thought I could teach you a thing or two. But clearly, these concepts are WAY over your head. Your last try at comparing an intermittent phone call SOD to quality control on a chip manufacturing line pretty much sealed the deal I'm afraid. :D
[Windows Mobile Apps and Games] detule:
No need to be afraid, we are all here to learn something, even you.

When you decide you want to seriously defend your statement rather than play straw man arguments, only then we can pick this up again. Until then, even I have to draw the boundary at certain childish discussions lacking basic etiquette.

On top of all this, you still don't understand that claiming other people's work is dysfunctional just because you encountered an issue you can't even replicate is disrespectful at the very least (I have a few more adjectives I could use here.)

Good luck with fixing your problem.
[Windows Mobile Apps and Games] cmd512:
I don't need to defend my statement, anyone who understands how this tool works would understand where these SODs might be coming from. Plus, I like how you completely ignored my technical discussion on clock and bus states, that is proof enough you have no idea what is actually going on with your hardware at the lower level, which means I shouldn't have wasted my time trying to explain this to you.

Seriously though, I have no problems with the phone call SODs, I'm certainly not going to stop using the tool. I only said the registry change doesn't fix the issue 100%, and that's the truth, which you seem unable to handle.

Wow, because I said the fix isn't 100%, now I'm claiming other people's work is dysfunctional? Meds, time to get back on those meds, lol.
[Windows Mobile Apps and Games] detule:
We're done here friend (read "You got me lolz...")
[Windows Mobile Apps and Games] orangegator:
nooooooooooo..... This was just getting good. I just made popcorn. lol :p
[Windows Mobile Apps and Games] saurabh88:
anyone using cosmic debris rom for rhodium and have succeed in oc?when i run ocauto4.1 scriptss it says backlight dips not found...

till now no problem for energy@748mhz
[Windows Mobile Apps and Games] BoominSVX:
Sounds like your "dispon" key isn't in the default location. (happens on some roms).

Search the registry for the dispon key, and if found, you may be able to edit the script for proper use. This script believes those keys are located in HKLM\Drivers\Display or HKCU\ControlPanel\BackLight. Check there first and let us know what you find in those locations.
[Windows Mobile Apps and Games] saurabh88:
tried using resco and total commander..but nothing found
[Windows Mobile Apps and Games] nayr1482:
@ cmd512 & detule

WOW - that is all I have to say!

and for the record...I agree none of the "fixes" that have been rolled out yet fix SOD 100%. Although, I have never had a single SOD (and no - I dont use the suggested registry fix).