|
||||
Interesting... that is an xscale cpu - and it does run at 520mhz native
So, "Performance" at 520 should do nothing. Weird. Placebo speedboost. |
|
||||
does the htc performance scaler actually work on the ppc6700? I have tried the xpuscalur 3.03 and when i put it on 624 it locks right up. i tried this htc performance cab and when i put the settings on 624..no lock ups. whats the difference? if i am over clocking i am overclocking right?
|
|
||||
Whatever HTC Performance is doing, it's *not* cranking the CPU clock up, no matter what the radio buttons on the app say
So yeah, it won't lock up, or drain your battery - because it may not be doing anything at all even on the 6700. It just feels faster when you check that button off |
|
||||
What this thread lacks is some hard numbers. I've run some TCPMP benchmarks on a clip that I normally use to benchmark.
I'm running DCD's clean ROM v1.4.5, all radios OFF. Without performance CAB, after reboot: Clip throughput is 1.0Mbit/s. WITH performance CAB @"624"MHz, after reboot: Clip throughput is 1.0Mbit/s Change: 0.0 Mbit/s. It does somehow, I don't know why, seem a bit snappier. Perhaps something was changed OS-wise, but NOTHING has changed as far as CPU performance. I have it set to "624" MHz. Let's see why nothing has changed: If this CAB is designed for an XScale CPU, the PXA270, which runs at 416MHz, there is no way in hell that a completely different processor, compatible ONLY because it belongs to the same ARM11 classification, will exhibit changes. The PXA270 is a unicore processor with Intel's power management and dynamic speed scaling built in. The MSM7500 has a Qualcomm ARM11 implementation with an ARM9 second core for phone functions. Remember, ARM sells intellectual property, not processors. Intel (well, now Freescale since they sold their XScale processor division) and Qualcomm have their own take on the processors, their ultimate power management, and speed stepping. They adhere to the ARM instruction set architecture. Therefore, these are completely different chipsets, though they in part share an instruction set architecture, and for that same reason, the CAB will do nothing for MSM7500. The benchmarks prove it. Now, can we PLEASE set this to rest? |
|
||||
well since we r on the subject of the unoverclockable 6800/ i accidently downloaded this program thinking it was for the 6800 but it turns out to be for a completely different phone/ BUT the thing is that there is no change in the processor speed when this is applied / but i noticed a big change in the response from the 6800/ i like it , it never has frooze the phone and
makes it open and close apps real quick/ i have set as 1 of the soft keys and u could look at it like a turbo button/ anyways since overclocking is nothing more than some well made reg hacks/ what the heck / anyways i post it for any of u guys who care to check it out it has NEVER frooze my phone so i take no responsibility if it has a different outcome for someone else. i saved this as a rar but u can only up load zip files so i changed the file extension from rar to zip but it should open for u anyways Last edited by bunvilla; 11-15-2007 at 12:54 PM. Reason: forgot to add file |
|
||||
This is getting silly now
The JS Overclock app is for an old (2002 ish) ipaq running a strongarm cpu. It tops out in the low 200s for speed. All the various xscale overclockers are pushing a few bytes into the appropriate cpu registers to change the dynamic frequency scaling settings - forcing a different high and/or low freg, or freq table, or disabling dynamic scaling, or enabling it, mucking with bus and cpu multipliers, etc... As others have pointed out, the mogul doesn't even use an xscale cpu - it has the funky (er, uber-cool) dual core cpu, running at 400/180mhz or something like that. None of the xscale overclockers are going to do anything good to that cpu by pushing random bits into some memory locations/registers... |
|
|
|