Originally Posted by INGINE (Post 726654)

To O/C, download the following from the application manager:

-rootsh
-Enhanced Linux kernel for power users
-Enhanced Linux kernel for power users (settings)

Reboot, go to xterm and type this:

sudo kernel-config load ideal

This will O/C to 500-850MHz, to get back to the default clock:

sudo kernel-config load default

To overclock more:

sudo kernel-config limits XXX YYY

were XXX is your min clock and YYY is your max clock (e.g. 500 950), for more info, look at the links in my post above, cheers.

Originally Posted by geneven (Post 728590)

What's best for you is not completely subjective. If you crash, that's bad.

It sounds like you don't understand the basic theory of overclocking, correct me if I'm wrong. CPUs are not identical, so you can't count on a description of what is best for the typical user. Most people seem to be able to run Ideal, but lots of people can't.

Since you spontaneously reboot with Ideal, Ideal isn't best for you. Since you don't have time for extensive testing (and most of us don't have time to tweak ad infinitum -- I know I don't), you should try one of the other major settings.

The reason you are seeing more specifications than reasoning in the docs is that overclocking is not based mainly on reasoning; it's mainly based on experimentation.

I would suggest that you try a speed of 800 mHz and a voltage setting of XLV. If that doesn't work for you (if you continue to spontaneouly reboot), try a voltage setting of ULV. If you continue to spontaneously reboot, try a voltage setting of LV.

If you spontaneously reboot with any overclocking setting, you are one of the rare possessors of a CPU that shouldn't be overclocked.

Originally Posted by jmc8501 (Post 730128)

Unfortunately, I am one of the few whose phone reboots after loading ideal... Is there anything I can do?

Originally Posted by DrWilken (Post 716611)

I'm using Fecn's dbus scripts to automatically adjust the clock speed according to temperature:

http://wiki.maemo.org/Overclocking#U..._.28by_Fecn.29

Works great, and this way the CPU is never cooked... ;)

Originally Posted by Crashdamage (Post 730420)

Use one of the more conservative voltage profiles, like 'ulv' (more conservative than 'ideal' i.e. uses higher voltage) or 'lv' (even more conservative). Or don't change the factory stock settings at all other than clock speed. I don't. Couldn't really tell a significant difference in battery life with various voltage profiles and I want max stability. So now the only thing I do is:

kernel-config limits 250 850

Gives a nice improvement and the phone will run for weeks.

Originally Posted by jmc8501 (Post 733477)

Thanks for the advice, I tried it out and was happily waiting for a reboot and... nothing, it ran nicely! Almost.

Almost. After about15 minutes, the status bar/clock area started flashing between completely gray and normal and a smattering of status icons also flashing. After closing several apps and not being able to stop the flashing, I rebooted anyway...

I really hope there is yet another more conservative approach for me - has anyone experienced this problem? Should I just de-install?

Originally Posted by YoDude (Post 730153)

Not rare at all... I have been running @800 since March IIRC using this method >> http://my.opera.com/yodude/blog/how-...-safe-r-800mhz

However since then, I understand it was discovered that once a call is made the clock is rolled back permanently and that method must be reapplied.
As I posted, I don't make calls and never experienced this roll back, so I rock on. :cool:

However, I have always wanted to post an update as this method of having the image on your phone should you find the need to roll back and re-apply, for whatever reason, when you are in the field was/is dang handy.

The Kernel Power app showed promise, however when "Ideal" wasn't ideal... I moved on.
Trying another major setting with out clearly knowing why is my problem now more so than time. The time constraint was in regard to weeding through all the "discussion" and ambiguity found in the threads and Wiki :)



Theory is not the problem... The fact that the clock is set OEM suggests to me that the following quote may not be the case:

.

Nokia did as OEM but apparently was more conservative then was necessary in order to maximize the devices useful service life.

I'm asking for the same consideration in an OC rate and method that an average user can apply if they choose to be more aggressive than Nokia was in this regard to useful service life.

In my mind the 33% increase that MHz provides seemed to be the "sweet spot" for many who do not need or care for other kernel enhancements.

A simple method to do this taking into consideration what is now better known about how the device reacts OEM, would also be the most elegant method, IMHO.