I see there is a thread over 4000 posts long, I can't wade through that. I found these (hopefully) easy instructions. a couple of questions...

http://maemo.soup.io/post/67745532/H...our-Nokia-N900

1) will this kill my battery life? It is already questionable as is...
2) anything else I should know that is not in these simple instructions (I don't want to brick my device).

thanks.

Everything you need to know is here

http://talk.maemo.org/showpost.php?p...&postcount=774

It shouldn't kill your battery life.

There is some adjustment going on because of compatibility issues between Fcam drivers and the overclocking kernel. I have a feeling the new overclocking kernel will be released soon. You might want to wait for it.

once the new kernel is released I'm assuming I do overclock now, it is the same method to enable the new kernel?

Your battery will actually be better (I`m using the 900mhz Lehto kernel) because it idles at 125mhz all the time instead of 250.I`ve been running it for the past 6 months...not a single problem!Go for it!

any reason to take the lehto over the titan?

When it's actually idle, it's completely stopped -- 0 MHz; since it takes more total power to compute a given workload at 125MHz than 250MHz, 125MHz idle is likely counterproductive,l and definitely makes the system less responsive.

In fact many of us are running with a 500MHz minimum (again, only when it is actually processing -- it drops to 0 when truly idle), and thinking we get better battery life than the stock 250Mhz. Of course, battery life under real-world use is tough to benchmark, but on the bright side, it doesn't make much difference, no matter who's right.

Of course, either way, you will increase battery life by dialing down the voltage from stock (which has to be stable for all CPUs) to the minimum required for your CPU. Typically, you can run 900MHz or so on the same voltage the stock kernel uses for 600MHz, and when you're running at 600MHz, use substantially less -- this effect is generally bigger than whatever difference there is among minimum frequencies, so you're practically guaranteed increased battery life.


Lehto's does offer improved compatibility with kernel modules built for the stock kernel, but AFAIK the only place this is an issue right now is with fcam, and titan already has a preliminary release for that

I strongly recommend titan's kernel, because you can adjust all these parameters at run time:

• minimum clock
• maximum clock
• and for each clock speed
  • enable/disable (to reduce excessive stepping, or if your hardware has issues at certain frequencies)
  • DSP clock
  • voltage

A complete voltage profile tuned at each step for your specific hardware is basically guaranteed to save power vs. picking the lowest non-crashing from several complete profiles.

Of course, be sure to back up your data before you start -- there's a non-negligible risk of corrupting a filesystem and trashing your system when you're initially tuning voltages (whether by selecting amongst entire profiles, or tuning individual frequencies); once you've established a fully stable profile, no worries.

ok I overclocked (so am I am I a power user now) and tested the reboot. since it was ok I made it permanent using this...

7. If you reboot, the overclock is reset back to default. So you will need to re-enable the overclock. (this is the safest way to avoid a constant reboot upon applying a unstable overclock although titan's kernel now has protection against this ever happening) I recommend you use the Queen Beecon Widget method I mentioned below on this guide.

If you do want to set an overclock profile to auto-load upon boot up, use the following command:

Code:


sudo gainroot
kernel-config load lv
kernel-config limits 250 850
kernel-config save myprofile1
kernel-config default myprofile1

Above is an example where I will load the lv voltage profile, then set the limits to 250-850 and then save it as "myprofile1" and then set it as the default profile at bootup. Now, when you reboot, it will auto-load myprofile1 profile with lv voltages and 250-850 frequencies.

================================================== ===

Some extra notes:
ideal profile avoids 125 and 250Mhz. So loading ideal profile will only go down to 500Mhz as its lowest frequency. This is intentional and is found to make you rn900 more responsive but not use more battery or harm your N900. (due to lower voltages)

My question is (I really want to preserve battery) would I be better off using the "ideal" setting? would this be better on my battery or worse? and if so what exact steps would I do differently in the code in step 7 above?

thanks.

ps I had no idea the difference between 600mhz and 850mhz would be that noticeable, but opening my epub books in fbreader is sooo much faster...

OK, this partially overlaps with my previous post (we were typing at the same time...), but specifically:

ideal is lower voltages than lv, so you'll save battery right off -- if it's stable on your hardware, of course.

There's some dispute about the best minimum clock, but I'm convinced 500MHz is better, and in any case there's minimal difference in power, so IMO go with the 500MHz for better responsiveness regardless.

What you'd do different:

And I'd recommend taking the time to dial in individual voltages, like so:
Now test it -- exercise CPU, GPU, proceed if it's behaving right...
Note the second number -- voltage -- is decreased by 1. Test again, keep going till it goes awry, then add 2 to the last voltage level and write it down. Repeat for each frequency...
Edit the FREQS="..." line with your new voltages, then

The starving profile should use even less power than ideal or lv (low voltage). There is also ulv (ultra low voltage) which should use less than lv.

You can see the different profiles here.

starving isn't there (guess someone forgot to include it on the Wiki).

In short, try starving. If that works and Your happy stay with it. If it crashes, try ideal.