[Dieter Bohn]

Original post removed by author's request.

[063_xobx]

will this also work if i were to say clock anywhere from 650-700 area

[2.0t03speed]

it worked great thanks!!

[bigkoont]

finally an easier way. That commandline one had my Pre acting funny in the past. Thanks.

[leathernuts#WP]

Sorry if this is a dumb question, but is the purpose of this patch to speed up the pre?

And my next question is how do you create the .sh file? Copy and paste to notepad and save it as "luna600patch.sh"?

When I open the link, do I copy everything that comes up?

Thanks

[KeeganDoomFire]

Im in the same boat as leathernuts, I saved as a .sh everything that poped up in the new tab and then when I try and send to the /var/home/root I get an error and it doesn't go in. Using the Send to device from the tools menu right? Ill try again tonight and post the actual error.

[Palmzero]

i get unexpected word "in" on line 3

and busy box on the other way posted

[ricebean]

will this be making its way to preware?

[RC46]

Please input thanks.

He just thanked you
Why beg for the thanks button?

BTW, many Pre's will become unstable clocked about 500mhz. Not all but many. Let the bricking begin!

[RC46]

It is still considered dangerous

Now you mention it after all these poor people tried to follow your bad advise.

BTW, "your friends" would not be considered a large enough sample size for alpha testing.

[bigkoont]

I'll try it after Monday.

[anon(4738177)]

No, it can only go up to the maximum of the processor which is 600 MHz

Just a note, the reason we can't go past 600 is because that's the highest setting that is compiled into our kernel. The Motorola Droid, which has the same TI OMAP3430 processor, has been overclocked and run at 1GHz without a problem. It just requires a custom kernel to do so.

[anon(4738177)]

He just thanked you
Why beg for the thanks button?

BTW, many Pre's will become unstable clocked about 500mhz. Not all but many. Let the bricking begin!

What bricking? There's no bricking to be seen here, go look elsewhere. :P

[Maturin]

Will this work for say 575mhz if I wanted to?
Do you think it would be safe to update with this enabled?

[gryn]

I don't think 575 works, inly 600 550 and 500.
btw what's the difference between this and the powersave patches, aside from the smartreflex and cpu scaling?

[2.0t03speed]

Note there are those who think this may shorten the lifetime of your pre

yea i used to maybe think this was possible but after palm has bumped the cpu up to 600mhz while in 3d games i no longer see 600mhz as shortening the life of the pre. If they thought it was going to give them any more warranty claims then they already have i don't think they would of done it but who knows.

[headswim]

caj2008: Would this work if the smartreflex 550 patch is installed? Part of the reason I want to patch is for potential battery savings when the phone is idle, in addition to the speed bump to the cpu. I've had no issue installing the smartreflex 550 patch, it just doesn't actually edit /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed. I'm debating trying either your method with the shell script, or just manually editing the scaling_setspeed file.

[nyczwillz]

this process worked installed it. this is what appears when I check if it was overclocked. can OP confirm it is overclocked and maybe explain the numbers for me? Thank you very much for this quick patch. It was fairly simple and very well written.

[headswim]

Those numbers indicate that your cpu is still spending most of it's time at 500 MHz. I could be wrong, but it looks like your pkill didn't take. Try issuing a reboot command, or resetting the phone and then after using it a bit, cat the time_in_state file again and see what the numbers look like.

[nyczwillz]

Thanks.