same... does it feel a little bit less responsive??

that extra 100mhz makes a noticeable difference

I assume your talking about the 800mhz ULV.
I tried that but found it a little bizarre and by that I mean slow, I'm not too sure why But it just made my N900 feel all funny in its tummy.

I've updated to Titans ULV Kernel and running the clock at 900mhz with no problems at all so far. Very happy with it all to tell the truth.

@titan, I ran Titan 900 Mhz not ulv or lv, and got the following warning from dmesg:
[38316.211791] WARNING: at /home/builder2/maemo-fremantle-armel-extras-devel/work/kernel-maemo-2.6.28/arch/arm/mach-omap2/clock34xx.c:443 omap3_noncore_dpll_set_rate+0x28c/0x2dc()
[38328.399444] WARNING: at /home/builder2/maemo-fremantle-armel-extras-devel/work/kernel-maemo-2.6.28/arch/arm/mach-omap2/clock34xx.c:443 omap3_noncore_dpll_set_rate+0x28c/0x2dc()
[38330.228790] WARNING: at /home/builder2/maemo-fremantle-armel-extras-devel/work/kernel-maemo-2.6.28/arch/arm/mach-omap2/clock34xx.c:443 omap3_noncore_dpll_set_rate+0x28c/0x2dc()

Is it normal?
Thanks for your help.

@titan: Hi, I'm using your ulv kernel 2.6.28-maemo_20 and just now I happened to come across which I guess is a bug. I tried to use screen calibration app from settings but as soon as I tap the first point it closes automatically. Before with other Lehto's kernels it never occured but now it happening all the time(In 810MHz and restarted device which set it to 600 but still the problem persists). Can anyone else confirm this as well plz.. other than this haven't encountered any and of course loving the ability to change frequencies at runtime.. thanks

I can confirm the same symptom with titan's ulv kernel.

I think titan already mentioned that calibration didn't work. This happened to me and I remembered something like that.

I just had a scary moment. I was running titan's latest from apps-testing earlier today. Suddenly, I rebooted, first time that had happened. No warning or indication that anything funny was going on. I was running at something like 810 mHz, because 800 wasn't available.

I couldn't get back in, had to reflash the kernel with an earlier 800 mHz kernel.

Now I'm back in, but a bit scared.

Edit: I flashed again with the ulv version back on i think page 203. I couldn't run it this time, had to reflash again. I had successfully run it before...

i am currently using titans ulv kernels... so far no problem...even when my pmconfig is 800Mhz my cat shows 810... so i just went to my pmconfig to change.. and the 124999 for the min...

tried angry birds no prob....

but i dont find the sys class power supply thingy....

how do you do the PI calculation??

now at 900 with bounce video playing.. no prob...

The calibration problem is a known bug in the calibration app, not in the kernel.
It's mentioned in the kernel package description and is due to additional evdev (joystick,mouse) support.
Just calibrate once with the stock kernel before you install the fully featured kernel.

@psrkn: The warning in dmesg is only expected for kernels other then the ULV kernel.
So far only the ULV kernel has 810MHz but I'm just rebuilding the LV and the normal voltage kernel with it.

@ahmadamaj: performance should be independent of voltage.

@psrkn: you dont need to uninstall the previous kernel. the new one will just overwrite it.

ULV should improve battery life and reduce CPU damage but it may be less stable.

For the new battery module you need to "modprobe bq27x00_battery" first.

current low voltage kernels:
http://talk.maemo.org/showpost.php?p...postcount=2004