Not sure if anyone notices this, but on RedPill, sometimes it doesn't go to deep sleep >.<

Actually it's the first time I got it. Might be related to the device not restarting after some time. Weird thing is, some people on Siyah and Redpill forum also posted about this as well. I'm now trying Siyah again and will try not to restart. See if it gets the same issue.

Should be more than 48 hours at least. I remember that I didn't restart it over the weekend.

Just found out a piece of knowledge. Limiting frequency on screen off really does wonders for your battery. Hence why I was able to last a few days when using lulzactive (as I was limiting it to 200MHz). And now with ondemand for Siyah (which is actually ondemandX with all the goodness of ondemand and intellidemand), I find that I'm getting the same good battery life as well.

Nope, limit with governors like lulzactive or ondemandX. You can limit with ThunderBolt! as well actually.

Both are ok to a certain extent. Just switch to any when you feel that it is laggy. For me, I'm currently using OndemandX (which is ondemand on Siyah).

Siyah's ondemand already limits it to 200MHz actually. No need to do anything from there.

Maybe it's not 200MHz but 500MHz. I forgot. Lulzactive needs to be tuned for that. It's the screen off min step (which is tuned in ThunderBolt! to be 200MHz or 500MHz, I forgot).

You can tweak from ThunderBolt!'s script

Battery Monitor Widget?
Yes

Having a suspend frequency of 500MHz is alright. 200MHz might be too low causing devices to keep being awake for a longer time when doing a task.

-e means if the file exists. I added that so that the script won't generate errors if the file is missing (as in the case the user chooses some other governors.).

If you just stick it without the if, it will run for ondemand governor, however it will error out (skipped) for other governors.

The indent is something I need to fix (some are inconsistent).

Posting here just in case

News
Updated ThunderBolt! to v2.6.0 with major changes to the RAM as well as governor settings as well as moved everything to /system partition. This means /sdcard/bolt_scripts is now in /system/etc/bolt_scripts. Removed kernel panic related settings (use kernel defaults instead).Also updated LMK to only use the /system partition. Moved zipalign script to bolt_scripts as first boot will slow down if a lot of APKs are not zipaligned. Zipalign manually or move it to init.d if you want to.

Updated ThunderBolt! to v2.6.1 with fixes to the main CWM updater script as well as moved S98bolt_siyah to bolt_scripts. Move it to init.d if you want to use ThunderBolt!'s hotplug/cpuidle/brightness settings for SGSII kernels.

Changelog:
3/5/2012 (2.6.1)
- Fixed updater script for main CWM. Just removing obsolete lines (no feature impact)
- Moved S98bolt_siyah to /etc/bolt_scripts as Siyah currently has a tweak app called ExtTweak by xan In order for it not to be override it. you can move this file to the init.d or run it with Script Manager if you want ThunderBolt!'s settings to override it.
3/4/2012 (2.6.0, screenstate_scaling 1.6.0, LMK 1.0.6, Restore 1.1.0)
- Less aggressive RAM tuned at screen on. Same aggressiveness when screen is off.
- More battery centric governors at sleep (with 99 up_threshold on most of the governors at screen off).
- Ondemand is at 95 up_threshold if io_is_busy is set.
- Removed kernel panic settings. Leave it at kernel defaults (whatever that is)
- Updated LMK to not use /data/local.prop. Instead it uses /system/default.prop
- Updated main CWM to not use /sdcard. bolt_scripts is now located at /system/etc/bolt_scripts. Be sure to point your Script Manager settings there now.
- Moved the zipalign script to bolt_scripts to ensure first time boot is faster. First time boot for some people might be slow as they might have a lot of unzipaligned APKs. You can move the script to init.d and give it rwx-rwx-rwx permissions if you want to.

There are updates for the addons too

Yup. You can do that too

You found a typo.

Thanks. Corrected it.

The vfs,dirty_* has been changed. I updated it in the first post. The _ADJ is stock it seems. You didn't flash the LMK?

The error is kernel dependent. It's ok.

The 90/75/1 is when screen is off. Screen on is 80/40/10.

Same explanation above.

Check the sysctl again?

Paste the screen on and screen off. Make sure that you installed LMK for the _ADJ values.

You can remove the init.d if you did the Script Manager one.

I made a mistake here. Reuploading the fix. Sorry about that.