My question is,,, Is it possible to hack my 6700 to run like my "old" red logo 6700 had had. Meaning when i worked it at 728mhz. the thing , ran great , now with my "new" yellow logo, it only runs stzble at 520 and under. which is pretty bad.

It seems to be pretty hit or miss. Some 6700s work at those higher clock speeds, some don't. There still isn't an overclocking solution that runs at a low level (doesn't show up as a running program, doesn't use up system resources).
I loved the one I used with my G1000, XscaleCntl, unfortunately it doesn't work with WM5. Every time the phone sleeps, the overclock settings revert to normal. I've been trying to contact the developer since Oct. '05, no luck.

ia there a hack that will make all 6700 created equal? is the chip ot processor different on my lder 6700?

My original red logo 6700 acts fine at 520 but would get a bit quirky at 624. Never tried 700+ on it.

I don't even bother with overclocking now, the new roms have solved most of my lagging problems.

which one are paople using for 724? Doe xcpuscalar have this? Or is Pocket hack master better? Are there any others? Mine works great at 624 and I'd like to try higher. Mine is an early one from Nov 2005.

xcpuscalar does have the option to clock at a higher value than 624.

[quote=toneii]which one are paople using for 724? Doe xcpuscalar have this? Or is Pocket hack master better? Are there any others? Mine works great at 624 and I'd like to try higher. Mine is an early one from Nov 2005.[/QUOT



YOU HAVE THE same phone i use to have you can go up too 728 np

XCPUScalar does have an option where you can show frequencies above 624 MHz. If you select that option, you have two additional choices above 624: 663 and 728.

My yellow-logo 6700 is set to 624 all day long using the seidio 3200 mAh battery with no problems whatsoever. However, if I try 663, the screen flickers and it works for maybe five seconds before locking up. If I select 728, the device locks up immediately.

I am fine with 624, but if someone has a way for the 6700 to successfully run at a higher speed, I'd give it a shot.

The over clocking to those speeds has little to do with software and a lot more to do with hardware (i.e. the XScale processor itself). When Intel or others sell processors they test them, see at what clock rate they lock up, give a margin of safety, and sell the processors at that speed. It's a luck of the draw on how much you can overclock these processors.

what do u mean safty?

a margin of safety to ensure the processor will run reliably at the rated speed. Theoretically lets say they test a processor and it locks up at 805 MHz. they are not going to try to sell it as an 804 MHz chip because they may have a warranty on this processor and will very likely come back when this chip starts having problems running at that speed, which may happen over time.

Xcpuscalar and PHM are the two main ones.
There are mayby one or two homemade at xdev site, but they are vaey limited.

I have both.
PHM is slightly faster at same overclocked speed, and has much more advanced settings.
XCPUScalar is more safe for those that are noobs.
On our 6700 units, the BUS SPEED setting is more important than the speed.
With increased BUS setting, I had a 520Mhz speed running faster than stock 624Mhz setting.
This was all accomplished with PHM (pocket hack master).

But all that is in the past now...
Running of "Wideawake" 2.2Beta2 rom, my PPC6700 is running faster and much more efficient than before with either overclocked software.
The new 3.3 roms are even faster!
Just have to watch out with old cabs from your ExtRom that have been found to need delete in order to run well.
Just need to read up much info about new roms and cooking them in PPCGeeks site..

It's a matter of many many things whether or not you can reliably overclock. In my experience, they are (in order of importance):

1. The average CPU usage your applications are using.
2. Random factors inherent in mass production such as how out of tolerance oscilators, capacitors, resistors, etc are, how well thermal-conductive compound was applied between your CPU and mini-heatsink inside, microscopic variations in the positioning of surface-mount chips.
3. The batch your CPU came out of.

Lockups with an overclocked unit are going to mostly be a function of how much average CPU time your programs are using. I can overclock my unit to 624MHz and have it run all day just fine, if all I'm doing is normal stuff. If I run TCPMP and put it into benchmark mode, though, it will lock up in five minutes.

When you are just doing regular things on your device, your CPU is working in short sprints. Every time you tap, the CPU ramps up and performs the current action, then ramps down again. Even playing music or a video doesn't tax the CPU to 100% (unless it's a video that the player has to scale in real-time).

I do things, though, like run an Amiga emulator, or Atari ST emulator. Those activities ramp the CPU up to 100%, and at 624MHz, locks up my CPU in a few minutes. I've found that 520MHz is stable at 100% CPU usage indefinitely.

If all the planets aligned nicely when your unit was manufactured - if you happened to get components whos values are dead on spec, if they were soldered at just the right positions to avoid bad harmonics, if that tiny-fingered Taiwanese woman who usually spends 1/4 of a second to affix a heatsink actually spent 1/2 a second on your unit and got the thermal-conductive compound distributed particularly evenly, then maybe your unit will do better than mine.