[MOD][TWEAKS] ThunderBolt! v3.3.0 5/15/16 [Performance+Battery Life Mods & Tweaks]

Search This thread

pikachu01

Senior Member
Feb 2, 2011
7,314
4,482
Penang
Back to report on 1.7.2. Got extreme lag sixteen hours after flashing, when I woke up. Rebooted at about 10:00 am, now 10:22 pm, and no lag. The 3g addon really works! I'll wait to see what 1.7.3 turns out to be as this is perfect so far. Don't mind rebooting once a day.

Sent from my GT-I9000 using xda premium
Yup, 1.7.2 has a very unaggressive LMK that will cause lags. 1.7.3 has buffed up the LMK a little bit, but you will still face a little bit of lag as the Hidden App is at 36MB right now.
 

geokilla

Senior Member
Jun 5, 2010
3,479
383
Toronto
I pmed Xcal asking him if he can reorient Semaphore or maybe teach me how to reorient. Also asked him if he can update Voodoo colour and sound in his own kernel. Hopefully he'll be able to help the devs.

I feel like a dev haha. But in reality, I'm just a tester ^^
 

rmean

Senior Member
Feb 14, 2011
695
102
35
Wuppertal
www.youtube.com
Just wanted to report, I'm still on 1.7 and it's running awesome since a week without a single reboot. I'm on semaphore, no oc, uv activated, smartassV2 governor & SIO scheduler. Battery lasting about 1.5 - 2 days

I don't dare trying 1.7.x because i have a perfect system right now and don't want to break it maybe :D maybe when 1.8 is there :)

Regards


Sent from my GT-I9000 using Tapatalk
 

Rebel2k

Senior Member
May 19, 2007
1,338
283
Here is my report:

- I'm running Semaphore on my side, so it can bring a new level of detail over geokilla tests
- I flashed 1.7.3 yesterday. Everything was fine until this morning. Now, autoclose again. Can't stand it!!!!
- Nothing has changed for me between 1.7.2 and 1.7.3.
- Here are lines in logcat which show what happens:
11-03 07:46:39.089 I/ActivityManager(1399): Process com.android.mms (pid 1770) has died.
11-03 07:46:39.089 I/ActivityManager(1399): Low Memory: No more background processes.
11-03 07:46:39.433 I/ActivityManager(1399): Process android.process.acore (pid 1765) has died.
11-03 07:46:39.433 I/ActivityManager(1399): Low Memory: No more background processes.
11-03 07:46:39.468 I/ActivityManager(1399): Start proc android.process.acore for content provider com.android.providers.contacts/.ContactsProvider2: pid=1795 uid=10000 gids={3003, 3002, 1015, 1001}
11-03 07:46:40.156 I/ActivityManager(1399): Starting: Intent { act=android.intent.action.MAIN typ=vnd.android-dir/mms-sms flg=0x10000000 cmp=com.jb.gosms/.ui.mainscreen.GoSmsMainActivity } from pid 4375
11-03 07:46:41.011 I/ActivityManager(1399): Process android.process.acore (pid 1795) has died.
11-03 07:46:41.011 I/ActivityManager(1399): Low Memory: No more background processes.
11-03 07:46:41.136 I/ActivityManager(1399): Start proc android.process.acore for content provider com.android.providers.contacts/.ContactsProvider2: pid=1806 uid=10000 gids={3003, 3002, 1015, 1001}
11-03 07:46:42.496 I/ActivityManager(1399): Process android.process.acore (pid 1806) has died.
11-03 07:46:42.500 I/ActivityManager(1399): Low Memory: No more background processes.
11-03 07:46:42.570 I/ActivityManager(1399): Start proc android.process.acore for content provider com.android.providers.contacts/.ContactsProvider2: pid=1817 uid=10000 gids={3003, 3002, 1015, 1001}
11-03 07:46:42.933 I/ActivityManager(1399): Starting: Intent { dat=content://mms-sms/conversations/1 cmp=com.jb.gosms/.ui.ComposeMessageActivity (has extras) } from pid 1651
11-03 07:46:42.945 W/ActivityManager(1399): Trying to launch com.jb.gosms/.ui.ComposeMessageActivity
11-03 07:46:44.464 I/ActivityManager(1399): Displayed com.jb.gosms/.ui.ComposeMessageActivity: +1s521ms
11-03 07:46:44.738 I/ActivityManager(1399): Process android.process.acore (pid 1817) has died.
11-03 07:46:44.738 I/ActivityManager(1399): Low Memory: No more background processes.

11-03 07:46:44.753 I/ActivityManager(1399): Start proc android.process.acore for content provider com.android.providers.contacts/.ContactsProvider2: pid=1831 uid=10000 gids={3003, 3002, 1015, 1001}
11-03 07:46:46.218 I/ActivityManager(1399): Process android.process.acore (pid 1831) has died.
11-03 07:46:46.218 I/ActivityManager(1399): Low Memory: No more background processes.
11-03 07:46:46.234 I/ActivityManager(1399): Start proc android.process.acore for content provider com.android.providers.contacts/.ContactsProvider2: pid=1841 uid=10000 gids={3003, 3002, 1015, 1001}
11-03 07:46:47.109 I/ActivityManager(1399): moveTaskToBack: 69
11-03 07:46:48.531 I/ActivityManager(1399): Process android.process.acore (pid 1841) has died.
11-03 07:46:48.535 I/ActivityManager(1399): Low Memory: No more background processes.
11-03 07:46:48.542 I/ActivityManager(1399): Start proc android.process.acore for content provider com.android.providers.contacts/.ContactsProvider2: pid=1854 uid=10000 gids={3003, 3002, 1015, 1001}
11-03 07:46:49.828 I/ActivityManager(1399): Process android.process.acore (pid 1854) has died.
11-03 07:46:49.832 I/ActivityManager(1399): Low Memory: No more background processes.
11-03 07:46:58.343 I/ActivityManager(1399): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.nolanlawson.logcat/.LogcatActivity } from pid 4375
11-03 07:46:58.441 I/ActivityManager(1399): Start proc com.nolanlawson.logcat for activity com.nolanlawson.logcat/.LogcatActivity: pid=1865 uid=10214 gids={1007, 1015}
11-03 07:46:58.871 I/ActivityManager(1399): Displayed com.nolanlawson.logcat/.LogcatActivity: +453ms
11-03 07:47:00.304 I/ActivityManager(1399): Start proc com.anddoes.fancywidgets for service com.anddoes.fancywidgets/.UpdateService: pid=1876 uid=10193 gids={3003, 1015}
11-03 07:47:00.949 I/ActivityManager(1399): Start proc com.google.android.apps.maps:LocationFriendService for service com.google.android.apps.maps/com.google.googlenav.friend.android.LocationFriendService: pid=1886 uid=10033 gids={3003, 1015}
11-03 07:47:01.988 I/ActivityManager(1399): Process com.anddoes.fancywidgets (pid 1876) has died.
11-03 07:47:01.992 I/ActivityManager(1399): Low Memory: No more background processes.
11-03 07:47:13.609 I/ActivityManager(1399): Process com.google.android.apps.maps:LocationFriendService (pid 1886) has died.
11-03 07:47:13.609 I/ActivityManager(1399): Low Memory: No more background processes.
11-03 07:48:00.468 I/ActivityManager(1399): Start proc com.anddoes.fancywidgets for service com.anddoes.fancywidgets/.UpdateService: pid=1913 uid=10193 gids={3003, 1015}
11-03 07:48:01.656 I/ActivityManager(1399): Start proc com.google.android.apps.maps:LocationFriendService for service com.google.android.apps.maps/com.google.googlenav.friend.android.LocationFriendService: pid=1923 uid=10033 gids={3003, 1015}
11-03 07:48:02.628 I/ActivityManager(1399): Process com.anddoes.fancywidgets (pid 1913) has died.
11-03 07:48:02.632 I/ActivityManager(1399): Low Memory: No more background processes.

As you can see, phone keeps telling that "No more background processes." are there to be killed, so it's killing foreground apps. Many times "android.process.acore" is killed and there, you can see exactly what I'm complaining about for a while: autoclose when opening GoSMS (bold line). I was wondering if it could come from GoSMS precisely, and in fact, I opened the native stock SMS/MMS app to see, same behaviour (as you can see the first line tells "com.android.mms" has died). That drives me crazy!!!! And the samedi happens with the dialer...

I'm more and more believing that the Android Memory system is not reliable!

P.S.: I need to precise that my phone reports I have 60 Mb free in RAM through OS Monitor or the Internal Task Manager.
 

pikachu01

Senior Member
Feb 2, 2011
7,314
4,482
Penang
Here is my report:

- I'm running Semaphore on my side, so it can bring a new level of detail over geokilla tests
- I flashed 1.7.3 yesterday. Everything was fine until this morning. Now, autoclose again. Can't stand it!!!!
- Nothing has changed for me between 1.7.2 and 1.7.3.
- Here are lines in logcat which show what happens:


As you can see, phone keeps telling that "No more background processes." are there to be killed, so it's killing foreground apps. Many times "android.process.acore" is killed and there, you can see exactly what I'm complaining about for a while: autoclose when opening GoSMS (bold line). I was wondering if it could come from GoSMS precisely, and in fact, I opened the native stock SMS/MMS app to see, same behaviour (as you can see the first line tells "com.android.mms" has died). That drives me crazy!!!! And the samedi happens with the dialer...

I'm more and more believing that the Android Memory system is not reliable!

P.S.: I need to precise that my phone reports I have 60 Mb free in RAM through OS Monitor or the Internal Task Manager.
You're absolutely sure that without ThunderBolt!, you won't get autoclose?

How about this, try installing Supercharger on top of ThunderBolt!.
 

Rebel2k

Senior Member
May 19, 2007
1,338
283
Oh no!Precisely without Thunderbolt that's the same! I'm not saying Thunderbolt is making things worst!Actually that makes things better... But still not perfect! :(

Sent from my GT-I9000 using Tapatalk
 

Blondasisko

Senior Member
Jan 15, 2011
196
31
Krakow
smartass in Thunderbolt?

Hi,
I wonder whether how does the screenstate_scaling script work with smartassV2 in Semaphore 1.8.1, does it switch between smartass and conservative, or does not work at all? And how does it cooperate with LMK settings in Semaphore Script Manager, where you can change them? Which has a priority for example after flashing TB 1.7.3?
 

pikachu01

Senior Member
Feb 2, 2011
7,314
4,482
Penang
Oh no!Precisely without Thunderbolt that's the same! I'm not saying Thunderbolt is making things worst!Actually that makes things better... But still not perfect! :(

Sent from my GT-I9000 using Tapatalk

Ahh, I see now. :)

Ok, now I know what's happening. I think your Go SMS database is corrupted and/or are allocating too much memory for the messages.

Try this (doing this on ADB is easier, as you have a keyboard to type). Be sure to have a backup of your SMSes beforehand in Titanium Backup.

Code:
1. Run adb shell/ Terminal Emulator
2. cd to /dbdata/databases/com.android.providers.telephony/
2. echo .dump | sqlite3 mmssms.db > mmssms.sql
‪2.‬ mv mmssms.db mmssms.db.bak
‪3.‬sqlite3 -init mmssms.sql mmssms.db

If that doesn't work, try deleting sms/mms that you don't want to keep to keep the size small.

Now I can focus the LMK on solving the lags rather than auto-closing as auto-closing is not caused by the aggressive LMK settings :)

Hi,
I wonder whether how does the screenstate_scaling script work with smartassV2 in Semaphore 1.8.1, does it switch between smartass and conservative, or does not work at all? And how does it cooperate with LMK settings in Semaphore Script Manager, where you can change them? Which has a priority for example after flashing TB 1.7.3?

It works, you just have to edit the screenstate_scaling script and comment out ondemand and uncomment smartassV2.

Before:
Code:
#AWAKE_GOVERNOR="conservative"
AWAKE_GOVERNOR="ondemand" # [no additional settings required, tweaking done in kernel-source]
#AWAKE_GOVERNOR="ondemandX"
#AWAKE_GOVERNOR="interactive"
#AWAKE_GOVERNOR="interactiveX"
#AWAKE_GOVERNOR="smartass"
#AWAKE_GOVERNOR="smartassV2

After:
Code:
#AWAKE_GOVERNOR="conservative"
#AWAKE_GOVERNOR="ondemand" # [no additional settings required, tweaking done in kernel-source]
#AWAKE_GOVERNOR="ondemandX"
#AWAKE_GOVERNOR="interactive"
#AWAKE_GOVERNOR="interactiveX"
#AWAKE_GOVERNOR="smartass"
AWAKE_GOVERNOR="smartassV2

It doesn't cooperate with Semaphore's LMK/OOM settings. It overwrites/overrides it with ThunderBolt!'s. I changed them in /data/local.prop and /data/SuperCharger* files.
 

MajinkenSword

Senior Member
Nov 2, 2008
250
35
Just my 2 cents worth, ram.conf should be deleted.

I tried doing this and havent experienced any autoclose. keeping my fingers crossed :)

Sent using Tapatalk
 

pikachu01

Senior Member
Feb 2, 2011
7,314
4,482
Penang
Just my 2 cents worth, ram.conf should be deleted.

I tried doing this and havent experienced any autoclose. keeping my fingers crossed :)

Sent using Tapatalk
Did you experience autoclose just by flashing ThunderBolt!?

Removing ram.conf just makes the LMK/OOM go back to Talon's default which is an extremely unaggressive LMK/OOM.

Did you try 1.7.3 Beta?
 

s30ckf

Senior Member
Jul 6, 2011
454
48
Kuala Lumpur
Pika, since v1.4 until now, every version/beta version that you released, I have flashed them. I didn't facing any auto close at any opened apps, I do facing apps which reside in memory is killed/closed after opening big apps like angry bird...etc

Looking forward to see ThunderBolt can increase the smoothness (as still facing micro lag when open apps, switching homescreen...etc) and better battery consumption.
 

pikachu01

Senior Member
Feb 2, 2011
7,314
4,482
Penang
Updated 1.7.4. Two issues here that are mainly reported:
- Autoclosing of SMS app. This is not caused by ThunderBolt!. I've asked a tester to implement an experimental fix on this. WIP on results.
- Lagging after > 24hours. This new LMK/OOM would prevent lagging that you felt on 1.7.3 and 1.7.2. This was because the last two versions focused on people who complained about their apps closing. 1.7.4 should prevent lagginess.

Changelog:
11/3/2011 (1.7.4) - Made LMK/OOM aggressive again. Should not face lags/microlags anymore.

Added this known issue:
The LMK/OOM is on the aggressive side. Some apps that you've hidden behind other visible processes SHOULD be killed to make way for bigger apps. This is to ensure your Angry Birds or Fruit Ninja doesn't LAG LIKE HELL after some time.
 

zeppelinrox

Senior Member
Dec 21, 2010
9,374
21,590
IN THE FREAKIN' OP
You would think so.
But I think it's LESS likely to kill background tasks - since they won't be as starved for memory.

I remember that I was testing it at droidforums and results were best with it at 1 on the low ram OG Droid
 

ReasonablyRooted

Senior Member
Mar 22, 2011
183
51
I don't know if it's still helpful, but I finally was able to test for 24 hours on 1.7.2. I can report that I have no noticeable difference from when I first booted. I have performance, smoothness, and great battery life. :D
 

zeppelinrox

Senior Member
Dec 21, 2010
9,374
21,590
IN THE FREAKIN' OP
Heh... seems I did personally test/benchmark it after all...
I didn't post benchmark results but...

http://www.droidforums.net/forum/dr...s-fix-memory-all-androids-60.html#post1583609
metalspring said:
Btw whenever you're on Zeppelin, could you confirm one of the settings I made? The overcommit memory setting? Its supposed to have one of three values...it seems the default is 1 which runs checks but overcommits memory automatically no matter what...2 means it runs checks but never overcommits but I set it to 0 where it runs checks but only overcommits when needed...its something along those lines, I figured it would be optimal to only overcommit when needed
http://www.droidforums.net/forum/dr...s-fix-memory-all-androids-62.html#post1585182
zeppelinrox said:
Tested overcommit settings.
Set at 2, the phone gets stuck at M logo
Set to 0, apps close while using them and angry birds doesn't run, smatbench gives high scores but the graphic test's graphics are diminished.
So only a setting of 1 would be universally acceptable.
http://www.droidforums.net/forum/dr...s-fix-memory-all-androids-62.html#post1585437
metalspring said:
Yeah, I noticed apps closing/force closing now that I'm trying out muiu roms...I think simply stunning was just good enough that I didn't see much of that...its hard to test some of what works and what doesn't on my phone...its just a beast and will handle about anything lol...

So basically I went with the one that works... LOL

Edit: Oh hey... hadn't users in this thread reported some apps closing while using them?
 

pikachu01

Senior Member
Feb 2, 2011
7,314
4,482
Penang
Heh... seems I did personally test/benchmark it after all...
I didn't post benchmark results but...

http://www.droidforums.net/forum/dr...s-fix-memory-all-androids-60.html#post1583609

http://www.droidforums.net/forum/dr...s-fix-memory-all-androids-62.html#post1585182

http://www.droidforums.net/forum/dr...s-fix-memory-all-androids-62.html#post1585437


So basically I went with the one that works... LOL

Edit: Oh hey... hadn't users in this thread reported some apps closing while using them?
Yeah, some people reported that actually, but it wasn't really caused by ThunderBolt!, although earlier versions of ThunderBolt! did have a really aggressive LMK (more aggressive than Supercharger :O) that some people were facing auto-closing.

After 1.6.x, the LMK/OOM became better (after your advise/discussion with you). Auto-closing was only faced by some people. They found out that auto-closing will be experienced even without ThunderBolt! :/

Let me try overcommitting memory and see :p
 

Top Liked Posts

  • There are no posts matching your filters.
  • 358
    [MOD][TWEAKS] ThunderBolt! v3.3.0 5/15/16 [Performance+Battery Life Mods & Tweaks]

    News
    Fixed to be compatible with Android L and M.

    Introduction
    ThunderBolt! is a script package by me, pikachu01 that combines a few notable tweaks shamelessly modified to the max as well as hacks and scripts that I came up on my own(and added tonnes of things over the months of development and testing). Without further delay, please read the rest of the OP :)

    Benefits
    • Better performance, better battery life through Linux kernel tweaks catered for Android OS and flash memory.
    • Faster disk access through remount script (noatime, disable barrier etc)

    Minimum Requirements
    • Android Gingerbread 2.3.x
    • At least 3MB free on /system (Delete unused ringtones or useless apps like Aldiko/Allshare etc).
    • Root.
    • Script Manager
    • Busybox
    • Ext4 filesystem if you want to use the remount script.

    Addons
    • remount script in remounts the partitions in your phone to optimize its performance at the expense of some risk of corruption.
    • drop script in /etc/bolt_scripts to drop caches.

    Known Issues
    • If you're using a custom MP3/Wav file as a ringtone, flashing ThunderBolt! might erase that setting causing your ringtone to be silent. Be sure to restore the ringtone again.
    • All scripts have to be launched using script manager

    Instructions
    1. Extract scripts to your sdcard/internal memory.
    2. Open up Script Manager and launch the scripts that you want as Root (The skull icon) and as Boot (The wheel icon).
    3. ????
    4. PROFIT


    Reverting/Undoing ThunderBolt!
    • To revert ThunderBolt!, just delete the scripts from your sdcard/internal memory and reboot.

    Repackaging
    • Repackaging ThunderBolt! into custom ROMs is allowable as long as it is included as a feature of the ROM as well as proper credits are included.
    • Please reply into the thread if you would like to include it as its just a nice thing to do :)
    • You are free to modify the contents of the scripts, but please make it known that you've modified it and also briefly include the modifications you've done.

    How to find out if it works
    Use File Expert/ Root Explorer/Root Browser, and navigate here:
    To enter superuser mode:
    Code:
    su
    Then:

    Code:
    sysctl -a | grep vm
    You will get values like this (for 512MB RAM devices or below):
    Code:
    dirty_ratio = 30
    dirty_background_ratio = 15
    vfs_cache_pressure = 50

    You will get values like this (for 1GB RAM devices or below):
    Code:
    dirty_ratio = 20
    dirty_background_ratio = 10
    vfs_cache_pressure = 50

    You will get values like this (for >1GB RAM devices):
    Code:
    dirty_ratio = 10
    dirty_background_ratio = 5
    vfs_cache_pressure = 50

    Credits
    • Zacharias.maladroit
    • XDA's devs for some reference of some tweaks in Zach's scripts


    Confirmed working devices
    Any unlocked and rooted Android L or Android M phone.
    102
    Script Details
    WARNING:
    Other scripts that tweaks the same VM,I/O,Readahead, etc settings with different values(check the scripts and compare) and what not should not be running together with these Thunderbolt!. It'll ruin the harmony of the settings causing decrease in performance/battery life.

    The system_tweak file will tweak these:
    • VM settings (tweaked to offer more battery life and performance with the RAM, a faster memory being used more often than NAND writes)
    • Misc tweaks (you can look at the script itself, google will tell you what it does)
    • Readahead tweaks. Optimizes different memory devices readahead values. It's not 1024/2048 for all devices. It won't work well that way.

    Disclaimer
    This won't brick your phone or cause it to go haywire. If it does, I will not be responsible for it. Do some research before attempting to use it (as always).

    remount Script
    I created a post-boot script that you could remount your partitions to:
    • Disable barriers for /data
    • Noatime for every mount point (Using atime for mount points will decrease the life of the disk as writes are performed everytime a file is accessed for the access time)
    • Increased commit time to 60 seconds as opposed to 5 seconds. By default, journaling will commit to disk every 5 seconds. That means, if you changed something more than a time span of 5 seconds, your files are not likely to get corrupted on power loss. By adjusting this to 60seconds, the risk is slightly higher, but it's a risk I'm willing to take, and an informed decision that you should make if you choose to use this script. This increases performance by a lot! 59 seconds of the time, you will not face lags stemming from journaling. It's like having journaling only 1/12th of the time.
    How-To
    1. Wait till Android finishes loading everything.
    2. Install Script Manager from Market
    3. Point script manager to the script you placed in the sdcard.
    4. Run as root.
    5. Do this at every boot.
    6. You can add a widget to your home screen for the script so that you can
      activate it easily.

    Disclaimer
    I am not responsible for data corruption or data loss from using this remount script. You should know its risks after reading the information from this guide. If you haven't, you should read the whole guide and make an informed decision.

    drop Script
    Drop script perform a cache drop operation to provide more free memory to the user. Use it when you feel that memory is lacking.

    Changelog:
    • 5/15/2016 (3.4.0)
      - Updated for Android 5/6. Removed a lot of junk code as they are not necessary to be tweaked in later Android versions (yes, Android finally coded them to be default values).
    • 3/17/2014 (3.3.0)
      - Added universal remount script. Use that script instead of device specific remounts
      - Fixed the updater_script to be much more compatible
    • 3/8/2014 (libsqlite addons 3.1.0, screenstate_scaling 3.1, clean uninstall 3.1.0)
      - Revamped libsqlite addons to only install libsqlite.so (not libsqlite_jni.so)
      - Revamped screenstate_scaling script to become much cleaner and automatically target correct paths
      - Revamped clean uninstall to be compatible to current ThunderBolt! versions.
    • 3/3/2014 (3.20)
      - Added support to sqlite3 for JB 4.3 and KK 4.4
    • 3/25/2013 (3.11)
      - Added Xperia S and Xperia Arc S remounts
    • 3/12/2013 (3.10)
      - Added ROW scheduler tweaks. Take note that the ROW scheduler is buggy as one of it's sysfs interface is broken. Suggest using SIO instead.
      - Added Nexus4 remount
      - Enabled nomerges flag to "1". Let me know if you're facing any performance hits.
    • 2/13/2013 (main CWM 3.05 and libsqlite 3.0.2)
      -Added CM10/10.1 fullext4 remount.
      - Added LG Mytouch4G remount.
      - Added JB 4.1 libsqlite and added support for 4.2.2 for JB 4.2 libsqlite.
    • 2/11/2013 (3.04)
      - Added GNex YAFFS remount.
      - Removed loop* from being tweaked by the I/O tweaks. It bootloops Galaxy S Gingerbread.
    • 2/5/2013 (3.03)
      - Fixed zipalign directory to xbin. Thanks to ggogolewski!
    • 2/5/2013 (main CWM 3.02 and libsqlite 3.0)
      - Added SQLITE_NO_SYNC compiled libsqlite libraries that disables sync (fdatasync/fsync) which increases sqlite transactions by 10-20%. You can use RL Benchmark to test for this.
      - Added loop* and ram* block to be tweaked by ThunderBolt!'s I/O tweaks.
      - Changed write_starved to 4.
    • 2/3/2013 (3.01)
      - Added Sony Xperia U remount.
      - Changed windowsmgr.max_events_per_sec to 90.
    • 2/3/2013 (3.0 and LMK addon 3.0)
      - Added an intelligent backup/restore updater_script on every CWM zip ThunderBolt! has. Thanks to Tungstwenty for his post here.
      - Added a restore CWM zip that restores the backup and deletes Thunderbolt!.
      - libsqlite addon won't install in ICS/JB. It will warn you if you're installing on the wrong OS.
      - LMK addon now backs up the build.prop (or restores the build.prop before modifying it). Hence now you can change LMK settings without doing any build.prop modification/moving/copying. The CWM takes care of it for you.
      - Main CWM is smart enough not to replace zipalign and sqlite3 if it's already in your ROM. My policy is "try not to mess around too much as I will tweak only in the right places".
      - Added LMK 80MB Alt that follows AOSP ICS LMK for 512MB devices and above.
    • 1/6/2013 (2.9.3)
      - Added HTC One S/XL/Sensation 4G remount script. Use remountHTC_Alt.
    • 1/2/2013 (2.9.2)
      - Added HTC One X remount script.
    • 12/30/2012 (main CWM 2.9.1 and screenstate_scaling 2.4.0)
      - Fixed screenstate_scaling to be AOSP ROM compatible
      - Fixed zipalign script to determine whether there are any errors on zipalign before committing.
      - Fixed sqlite3 extraction to certain JB ROMs (like 4.2)
    • 12/24/2012 (LMK addons 2.1)
      - Revamped how LMK works. Added 120MB LMK.
      - The LMK now incorporates knowledge from reading the ActivityManagerServices source code. It should correctly make your apps handle its own memory more efficiently based on how memory is evaluated in the Android OOM. Apologies for this as the previous implementation actually broke some degree of how LRUs/Memory trimmings for apps are calculated.
    • 12/3/2012 (2.9.0 and screenstate_scaling 2.3.0)
      - Fixes to screenstate_scaling script. Minor typo that prevents some busybox versions from running it.
      - Added kernel.shm* tweaks that is calculated based on your available memory.
      - Upped vfs_cache_pressure to 50 on screen on, and 100 on screen off so that free memory is still kept fair, but performance on caches vs disk is still balanced.
      - Disable /system/app/*.apk zipalign as this causes some Cyanogenmod devices's Google Apps to disappear.
      - Lowered dirty_ratio/dirty_background_ratio for < 512MB a bit based on more recent benchmarks.
    • 11/13/2012 (2.8.0 and screenstate_scaling 2.1.1)
      - Added VM dirty* values according to the amount of RAM that you have (< 512MB, < 1GB and more than 1 GB). I've tested write speed for the disks on /data on a few phones and come to a conclusion that VM scaling is most optimized depending on total amount of RAM. This is because the I/O can only write that much dirty data up to an amount at an interval so that I/O doesn't become the bottleneck.
      - Commented out some shm* tweaks. Will need to make this scale with amount of RAM also, but need floating point arithmetic support for bash in Android phones. No "bc" command!
      - Fixed zipalign script that corrupts Google* APKs by removing already aligned APKs in /data/local. Might still be a problem with some APKs like BetterBatteryStats (what I found to be problematic so far).
      - Fixed sqlite3 binary for Jelly Bean. The updater_script will check your build.prop and extract the appropriate sqlite3 binary for you :)
      - Minor pegasusq updates in screenstate_scaling and main CWM.
      - Some general fixes on the script (settings applying more than once)
      - Might not affect >90% of people but I signed the zip files ;)
    • 8/1/2012 (100MB LMK)
      - Added 100MB LMK. Increases performance and a bit more multitasking at the expense of background inactive tasks/apps getting killed.
    • 6/17/2012 (2.7.7, screenstate_scaling 2.02)
      - Added I9300 Samsung Galaxy SIII remount script
      - Moved noatime remount procedure to the remount scripts
      - Fixed a minor typo in screenstate_scaling script (Thanks Tungstwenty).
    • 6/13/2012(LMK 2.0.0 and restore packs 1.2.0)
      - Updated LMK to use build.prop method. Older build.prop will be backed up in /system/build.prop.thunderbolt.
      - To apply the LMK changes, you'll need to restart twice. Once to modify the build.prop, another to load the modified build.prop
      - To restore the build.prop, just copy over build.prop.thunderbolt to build.prop
      - Updated restore packs with automounter by iXNyNe.
    • 5/30/2012(2.7.6, screenstate_scaling 2.0.1)
      - Updated script asserts on mounts. Detects whether partitions are mounted before installing. Credits to iXNyNe.
      - Updated governor parameters to have a lower up_threshold (higher performance) because of visible lags due to the change in the previous version,
    • 5/24/2012(2.7.5, screenstate_scaling 2.0.0)
      - Updated all governors to skew towards more battery life.
      - Updated pegasusq to correct typo in some of the settings as well as scale better.
    • 5/18/2012 (2.7.4, Screenstate_scaling 1.9.0)
      - Updated both main script and screenstate_scaling script to support tweaking abyssplug and pegasusq governors for better performance + battery life when screen is off.
      - Removed CFS from executed by default. Use Script Manager to navigate to /etc/bolt_scripts/CFS to manually run it. s98CFS is the default one.
      - Removed lulzactive tuning on the pump_up_step as Siyah introduced 18steps of frequency. This needs to be manually set.
      - Removed io_is_busy from being set. You can edit the script to set it if you feel performance is lagging.
    • 5/5/2012 (2.7.3)
      - Changed write starvation for MTD to be 2:1. Added Hydrogenics I9100 restore pack.
    • 4/25/2012 (2.7.2)
      - Changed NAND memory to have 2:1 writes starved as read speed is higher than write speed. SD memory still has 1:1 writes starved. Removed TCP buffers from S98system_tweak. Moved it to /etc/bolt_scripts/S98TCPbuffers as it causes hang at boot for CM7/9 ROMS.
    • 4/20/2012 (2.7.1)
      - Changed CFQ I/O scheduler slice_idle for better latency vs throughput.
      - Enabled TCP buffer tweaks to improve network throughput (credits to gokhanmoral for the values).
      - Changed sched_mc to 0 in bolt_siyah script and commented out some lines. Uncomment them to enable its usage.
    • 4/19/2012 (2.7.0, LMK 1.10)
      - Added an autoremount option, no need to mount /system or whatever partitions again before installing.
      - Tweaked the I/O scheduler a bit to be a bit more balanced between latency and throughput.
      - Moved touchscreen tweaks back to bolt_scripts. Move to init.d if you're using I9000 or use Script Manager to launch the script at boot.
      - Reverted the LMK to /data/local.prop. Seems to be the most reliable way for Gingerbread phones.
    • 3/5/2012 (LMK 1.0.7)
      - Fixed the positioning of default.prop (there was a mess in placement of the default.prop inside /etc in some of the LMK zip files. I forgot which, hence I'm refreshing all the LMKs up a version with the placement fixed for those that are broken. Please redownload.
    • 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.
    • 2/13/2012 (2.5.1)
      - A small fix to cpugputune by commenting out the if/fi between the UV_MV_Table tweak so that people can run the script fine even without any edits.
    • 2/9/2012 (2.5.0 and screenstate_scaling 1.5.2)
      - Added a CPU/GPU tune file (/etc/bolt_scripts/cpugputune) that contains:
      * Siyah GPU frequency/voltage tuning (with my own settings for a balanced performance/battery saving proflie).
      * CPU undervolting (similar to Voltage Control, but doesn't have the limitation of Voltage Control's limits. You can set it however you want till it hits the limits that is set in your kernel itself. (Note: You will require a kernel that supports undervolting for this to work)
      - To run this script, follow the same instructions as the remount script.
      - I've commented out the voltage settings for CPU/GPU because each phone will have its own threshold for each (too low and it hangs). Before uncommenting, be sure to change the UV_mV_table to your own stable settings.
      - To know how to undervolt, play a MKV file in software decoding using MX Video Player for 10minutes while limiting the frequency's voltage that you want to tune. Slowly decrease it (by editing it and then running the file on Script Manager) until it hangs. Then add +50mV to get a stable voltage.
      - To limit a frequency, add these lines to the script:
      Code:
      echo "200000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
      echo "200000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq;
      This limits it to 200MHz (example).
      - To undervolt the GPU frequency, use Nenamark as a benchmark. To limit a frequency for GPU, set all 3 frequencies to be the same. E.g.:
      Code:
      echo "100 100 100" > /sys/class/misc/gpu_clock_control/gpu_control;
      This will limit it to 100. Then run the script in Script Manager and run Nenamark. If Nenamark cuts to black and phone fails to respond, calm down first. Press the home key and wait for it to get to your homescreen, then reboot from there.
      - NOTE: Be sure to disable the remount script (untick the wheel icon in Script Manager and then reboot) before proceeding to undervolt your phone as the remount script will increase the likelihood of corruption after a phone hang.
      - Also tuned the conservative and smartassV2 governor to have a threshold difference of 10 instead of 5.
    • 2/3/2012 (2.4.1 and screenstate_scaling 1.5.1)
      - Mostly comment cleaning
      - Changed TCP Syncookis to false. Most kernels won't even support it. Hence its a useless change, but change it in case some kernels do support it and nope TalonDev and Siyah doesn't support it. Can't enable/disable it.
    • 1/26/2012 (2.4 and screenstate_scaling 1.5)
      - Changed zipalign script to reroute to /data/local dir instead of sdcard.
      - Updated screenstate_scaling sample rates to 100k for sleep and 20k for awake.
    • 1/23/2012 (2.3.131)
      - Bugfix update by removing one line before s98system_tweak.
    • 1/21/2012 (2.3.13, screenstate_scaling 1.4.14)
      - Disabled down_differential. Too battery draining for some people.
      - Tweaked smartassV2 and conservative to be more battery friendly.
    • 1/19/2012 (2.3.12, screenstate_scaling 1.4.13)
      - Fixed max_events_per_sec not tuned correctly.
      - Added down_differential (only for kernels that supports this) tuning to ondemand governors that will reduce lags by a little bit.
    • 1/15/2012 (2.3.11, screenstate_Scaling 1.4.12)
      - Fixed a bug on ondemand sleep scaling. Thanks ::Crack::
      - Enabled MTD block tweaking. Thanks ::Crack::
      - Made all sleeping governors have 90k sample rate. Good for battery life.
    • 1/13/2012 (2.3.10, screenstate_scaling 1.4.11)
      - Tuned sampling_down_factor of ondemand, ondemandX, conservative. This should resolve the issue of getting stuck 500MHz and above (I think). Siyah tweaked the sampling_down_factor to 4 and sampling rate of 120k. Since I tuned the sampling_rate to 10k, I'll need to tuned sampling_down_factor as well.
      - Tuned interactive based governors (lulzactive, smartassV2) to have a more aggressive sleep.
    • 1/12/2012 (2.3.9, screenstate_scaling 1.4.10)
      - Tuned the ondemand, ondemandX and lulzactive to have up_threshold of 85.
      - Tuned hotplugging in SGSII to be performance oriented a little bit.
      - Tuned smooth_* to be performance oriented a bit.
    • 1/12/2012 (2.3.8, screenstate_scaling 1.4.9)
      - Fixed SOD/deadsleeping for SGSII kernels by disabling deepsleeplevel tweaking. Some phones can't handle it.
      - Tuned ondemand,ondemandX, smartassV2, lulzactive governors again. Tuned hotplug settings again also (based on the governor tweaks). Added conservative governor tweaking.
    • 1/10/2012 (2.3.7, screenstate_scaling 1.4.8, LMK 1.0.3, 3G 1.0.5, bin files 1.1.2)
      - Updated main CWM to 2.3.7 with some cosmetic cleanup of the script and also enabled a default sampling_rate of 10,000 for ondemand/ondemandX.
      - Updated screenstate_scaling to 1.4.8 fixing a typo bug in lulzactive. Also updated screenstate_scaling to 1.4.9 with cosmetic cleanup.
      - Updated LMK, 3G, bin files with newer updater_binary.
    • 1/7/2012 (2.3.6, screenstate_scaling 1.4.6, restore pack 1.0.3)
      - Updated restore pack to remove bolt_siyah script and update updater binary.
      - Fixed Siyah v2.6.5 lockup due to Siyah having hung tasks. ThunderBolt! enabled the lockup detection. I disabled this pending fix from gokhanmoral.
      - Fixed some typo errors in system_tweak (kernel.sem, dirty_writeback_centisecs)
      - Made windowmgr events to have a minimum of 60.
      - Increased screenstate_scaling ondemand threshold to 95 if io_is_busy is enabled.
    • 1/4/2012 (2.3.5, screenstate_scaling 1.4.5)
      - Decreased the up_threshold for lulzactive, ondemand, ondemandx, smartassV2 for faster scaling.
      - Disabled smooth_target/smooth_step/smooth_offset. Brings stutters to ondemand/ondemandX.
      - Fixed iostats bug - Thanks PedroMRP.
    • 1/2/2012 (2.3.4, screenstate_scaling 1.4.4, graphics 1.0.3)
      - Fixed OndemandX, lulzactive, ondemand governor suspend_freq, pump_up_step respectively and sampling_rate (for all governors).
      - Commented out graphic voltage settings
      - Set deepsleep levels 1 level higher, prevents SOD.
      - Fixed S98graphics, save as unix file.
    • 1/1/2012 (2.3.3, screenstate_scaling 1.4.3)
      - Updated lulzactive governor to check for minimum/maximum frequency so that it can scale properly
      - Updated ondemandX governor to check for minimum frequency so that it can be the suspend frequency, in which previously it was set to 200MHz by default.
    • 12/31/2011 (2.3.2, screenstate_scaling 1.4.2)
      - Fixed ondemand tweaking for certain kernels(some kernels have the path to be /cpufreq/cpu0/* rather than /cpufreq/*)
      - Added OndemandX tweaking as well in screenstate_scaling.
      - Added sample rate tweaking in screenstate_scaling. This will make all tweaked governors (ondemand/ondemandX/lulzactive/smartass perform faster and sleep better using screenstate_scaling.
      - Tweaked lulzactive/smartass/ondemand/ondemandX to have 20,000 sample rate when screen is on. 10,000 seems a bit too much.
      - Tweaked all governors to have a sample rate of 100,000 when sleeping. Battery friendly.
    • 12/31/2011 (2.3.1, screenstate_scaling 1.4.1)
      - Moved SGSII tweaks onto another file (S98bolt_siyah)
      - Made heap_size tweak to be 64MB by default or 80MB if greater than 64MB (in build.prop). 48MB or 64MB doesn't really make a difference. Haven't seen an app consume more than 32MB of heap yet.
      - Commented out max window events. Each phone is different. Defaulting this to 60 seems wrong.
      - Used an if/else on the idle_sleeping_frequency for smartassV2.
      - Commented out sampling_down_factor. Some phones can't take it.
      - Finally figured out why touchscreen tweaks aren't working :S I saved it using the wrong format! It should be UTF-8 [unix] instead of UTF-8[windows]. Facepalm!
    • 12/30/2011 (2.3.0, screenstate_scaling 1.4.0)
      - Updated 2.3.0 with minor editiing of sdcard tweak arrangement, smartassV2 and lulzactive governor tweaking, and SGSII tunables (hotplugging, bus frequencies etc).
      - Added i9100 restore pack
      - Used newest updater_binary. All the older CWM zips are not using the newer binary. Just update it with the file I've uploaded in the 2nd post.
      - Forgot to add this: Enabled sampling_down_factor of 2 while screen is on. Might cause reboots/hangs if you've undervolted your top frequency (e.g. 1GHz) extensively. Recommend to add 25mV if you're facing issues.
    • 12/17/2011 (2.2.0, screenstate_scaling 1.3.1)
      - Updated 2.2.0 with CFSK as the default CFS. CFSK is still the fastest based on some feedback.
      - Updated 1.3.1 for screenstate_scaling. Disabled sampling_down_factor as it makes the phone unstable when sampling rate is too low. If you're still getting reboots, please add 25mV to 1GHz.
    • 12/13/2011 (2.1.9, screenstate_scaling 1.30, restore packs 1.0.2, all others)
      - Updated main CWM to v2.1.9 with CFS 1.9.4 as the default due to popular demand.
      - Renamed all the CFS scripts that have extensions. init.d can't load CFS's that have extensions (I tried using 1.9.4 and it didn't work when it had the .9.4 extension)
      - Added io_is_busy and sampling_down_factor to ondemand. Will increase the performance while awake as sampling rate will be faster, and frequencies will stay very flexible when near 1GHz. io_is_busy will ensure that I/O operations utilizes high frequencies ~400-1GHz rather than being 100Hz when CPU is mostly idle. Will prevent microlags.
      - Changed the screenstate_scaling ondemand up_threshold to 95 while awake and 98 while asleep to increase battery savings since microlags are eliminated almost completely from the above setting.
      - Updated all addons' updater_script to ensure installation of consecutive CWM zips are correct.
    • 12/10/2011 (graphics 1.0.1)
      - Used the wrong updater_script for the graphics addon. Corrected this mistake.
    • 12/10/2011 (2.1.7)
      - Removed sleep_mode setting. Could be the culprit of sleep-deaths and/or reboots/instabilities.
      - Separated the graphics acceleration tweaks to an addon. Might not work with some phones or it can cause instabilities. Please test it out for me.
      - Discontinued the L version as CFS might not be the culprit for sleep-deaths/instabilities.
    • 12/7/2011 (2.1.6L)
      - Tuned down the CFS aggressiveness in the v2.1.6L after a few complaints about devices that can't wake up received.
    • 12/5/2011 (2.1.6)
      - Updated updater_script to remove bolt_scripts. I moved the directory hierarchy a bit in the last version (forgot to add that). Hence, removing it so that people will realize the scripts are in a different position already.
      - Users have to manually readd remount scripts in Script Manager because of the above change.
      - Added remountCM7MIUI-fullext4. A variation of CM7/MIUI that doesn't use yaffs2. Renamed the original remountCM7MIUI to remountCM7MIUI-yaffs.
      - I just noticed that CFSK is actually the wrong CFS I wanted to use. Edited CFSK with the correct values. Should feel much smoother.
      - Revamped most of the echo tweaks to use sysctl instead. Might make it compatible with ICS.
      - Increased Dalvik heapsize to 48MB (another 16MB won't hurt much).
    • 12/3/2011 (2.1.5)
      - Added N7000 remounts.
    • 12/2/2011 (2.1.4)
      - Integrated some MintBolt! tweaks, notably the noda_auto_alloc and build.prop. The build.prop shouldn't change anything much but the noda_auto_alloc should make I/O transaction a little faster at the expense of corruption risk, which is small by the way.
      - Fixed the sqlite_optimize by using busybox find instead. If you can't do busybox find, it means your busybox symlinks are broken. Contact your kernel/ROM developer for a fix.
    • 11/27/2011 (2.1.3/Screenstate_scaling 1.2.3/80MB + 60MB 1.0.3/3G 1.0.3)
      - Fix for 3G CM7/MIUI (I think) by removing some settings that doesn't do anything.
      - 80MB/60MB LMK modified to be better at performance but sacrifices a bit of multitasking.
      - ChainFire's touchscreen tweak integrated. Touchscreen more sensitive.
      - Screenstate_scaling edited to be a bit more battery saving.
      - CFS moved to another file (CFS experiments moved to bolt_scripts. If you would like to use another CFS, delete the one in init.d and copy the one you like back to init.d)
      - sqlite_optimize and darky_zipalign improved to support Script Manager that doesn't symlink xbin/sbin automatically.
      - Added SGSII remount
      - Reduced readahead for phone mounts (non-sdcard mounts) to 256. This would reduce Quadrant I/O score by a significant value, as higher readahead boosts Quadrant scores. Quadrant is USELESS!!!!!1111 Link. Sdcard readhead is still 1024.
    • 11/25/2011 (LMK 1.0.2)
      - Fixed the Talon swappiness/ZRAM size typo
      - Fixed the 80MB LMK typo
    44
    [CWM][SCRIPTS][TWEAKS] ThunderBolt! v2.6.1 - 3/5/12 [Major Update Updated!]

    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.

    Introduction
    ThunderBolt! is a script package by me, pikachu01 that combines a few notable tweaks shamelessly modified to the max as well as hacks and scripts that I came up on my own(and added tonnes of things over the months of development and testing). Without further delay, please read the rest of the OP :)

    Features
    • Zach's modified system_tweak (I/O Sched, Readahead, VM, TCP, 3G, BFS/CFS tweaks)
    • Zach's modified screenstate_scaling script - VM Scaling
    • Darky's Zipalign script that actually works (modified it a bit to get it actually working. It was broken as is before this.)
    • Patched libsqlite that disables the need to fsync. Extremely fast database writes.
    • app_process from Fugutweaks and system_server from Honeycomb 3.2
    • Quasi-charged! - Only using Supercharger's script but with ThunderBolt!'s own LMK/ADJ/OOM. Supercharger Update9 RC3.2.
    • zipalign binary
    • sqlite3 binary
    • remount script - Included in /sdcard/bolt_scripts/
    • sqlite_optimize script - Included in /sdcard/bolt_scripts/

    Benefits
    • Better performance, better battery life through Linux kernel tweaks catered for Android OS and flash memory.
    • Better battery life and performance through usage of screenstate_scaling whereby it switches governors/thresholds/VM depending on your screen state.
    • Better performance and battery life for database writes as fsync is not utilized anymore.
    • Better network throughput from TCP tweaks and 3G tweaks
    • Less RAM usage through zipalign. I found that market apps like Viber and PlantsVsZombies aren't zipaligned. Oh and Swype too. Surprised? Me too.
    • Reduced /dbdata, /data, /sdcard usage of *.db files and faster database access through defragmentization of sqlite db files (a lot of apps use Database to store data like Swype dictionaries, Game saves etc)
    • Faster disk access through remount script (noatime, disable barrier etc)
    • Less lags through Quasi-charger, with mutltasking (e.g. NFS shift + Opera mobile with 5 tabs fully opened and no lags)

    Minimum Requirements
    • Android Gingerbread 2.3.x
    • At least 2MB free on /system (Delete unused ringtones or useless apps like Aldiko/Allshare etc).
    • Root
    • Kernel that supports init.d
    • Ext4 lagfix if you want to use the remount script

    Downloads and changelogs are in the:
    Original ThunderBolt! thread

    Any support for SGSII must be placed here rather than the original thread.
    A few SGSII owners kindly asked me to post here so that the goodness of ThunderBolt! is shared to the masses. They have been thoroughly tested by a significant number of SGSII owners, hence no problems should arise. I've gotten myself an SGSII and using ThunderBolt! without problems.

    Warning: 3G addon is only compatible with i9000

    Note: You need to manually mount the /sdcard (or emmc) in recovery aside from mounting /system and /data. If you can't mount /sdcard or emmc, copy the bolt_scripts manually to your internal sdcard.

    Currently working devices
    Samsung Galaxy S i9000
    Samsung Galaxy S II i9100
    Samsung Captivate
    Samsung Vibrant
    Samsung Galaxy S 4G
    Samsung Galaxy S Plus i9001
    Samsung Galaxy Note
    Samsung Infuse 4G
    Samsung Galaxy Tab
    Samsung Galaxy S Plus i9001
    Samsung Galaxy SL i9003
    Samsung Galaxy SII AT&T i777
    Samsung Galaxy Nexus
    41
    [CWM][SCRIPTS][TWEAKS] ThunderBolt! v2.6.1 - 3/5/12 [Major Update Updated!]

    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.

    Introduction
    ThunderBolt! is a script package by me, pikachu01 that combines a few notable tweaks shamelessly modified to the max as well as hacks and scripts that I came up on my own(and added tonnes of things over the months of development and testing). Without further delay, please read the rest of the OP :)

    Features
    • Zach's modified system_tweak (I/O Sched, Readahead, VM, TCP, 3G, BFS/CFS tweaks)
    • Zach's modified screenstate_scaling script - VM Scaling
    • Darky's Zipalign script that actually works (modified it a bit to get it actually working. It was broken as is before this.)
    • Patched libsqlite that disables the need to fsync. Extremely fast database writes.
    • app_process from Fugutweaks and system_server from Honeycomb 3.2
    • Quasi-charged! - Only using Supercharger's script but with ThunderBolt!'s own LMK/ADJ/OOM. Supercharger Update9 RC3.2.
    • zipalign binary
    • sqlite3 binary
    • remount script - Included in /sdcard/bolt_scripts/
    • sqlite_optimize script - Included in /sdcard/bolt_scripts/

    Benefits
    • Better performance, better battery life through Linux kernel tweaks catered for Android OS and flash memory.
    • Better battery life and performance through usage of screenstate_scaling whereby it switches governors/thresholds/VM depending on your screen state.
    • Better performance and battery life for database writes as fsync is not utilized anymore.
    • Better network throughput from TCP tweaks and 3G tweaks
    • Less RAM usage through zipalign. I found that market apps like Viber and PlantsVsZombies aren't zipaligned. Oh and Swype too. Surprised? Me too.
    • Reduced /dbdata, /data, /sdcard usage of *.db files and faster database access through defragmentization of sqlite db files (a lot of apps use Database to store data like Swype dictionaries, Game saves etc)
    • Faster disk access through remount script (noatime, disable barrier etc)
    • Less lags through Quasi-charger, with mutltasking (e.g. NFS shift + Opera mobile with 5 tabs fully opened and no lags)

    Minimum Requirements
    • Android Gingerbread 2.3.x
    • At least 2MB free on /system (Delete unused ringtones or useless apps like Aldiko/Allshare etc).
    • Root
    • Kernel that supports init.d
    • Ext4 lagfix if you want to use the remount script

    Downloads and changelogs are in the:
    Original ThunderBolt! thread

    Any support for Galaxy Note must be placed here rather than the original thread.
    Quite a lot Galaxy Note owners kindly asked me to post here so that the goodness of ThunderBolt! is shared to the masses. They have been thoroughly tested by a few Galaxy Note owners.

    Note: If you found that your status bar is missing, a reboot will bring it back.

    Warning: 3G addon is only compatible with i9000

    Note: You need to manually mount the /sdcard (or emmc) in recovery aside from mounting /system and /data. If you can't mount /sdcard or emmc, copy the bolt_scripts manually to your internal sdcard.

    Note: For a successful flash, you have to toggle Signature Verification ON -OFF and Script Assets ON -OFF, then flash it from internal storage. It works every time. - From mdalacu


    Currently working devices
    Samsung Galaxy S i9000
    Samsung Galaxy S II i9100
    Samsung Captivate
    Samsung Vibrant
    Samsung Galaxy S 4G
    Samsung Galaxy S Plus i9001
    Samsung Galaxy Note
    Samsung Infuse 4G
    Samsung Galaxy Tab
    Samsung Galaxy S Plus i9001
    Samsung Galaxy SL i9003
    Samsung Galaxy SII AT&T i777
    Samsung Galaxy Nexus
    25
    [CWM][SCRIPTS][TWEAKS] ThunderBolt! v2.6.1 - 3/5/12 [Major Update Updated!]

    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.

    Introduction
    ThunderBolt! is a script package by me, pikachu01 that combines a few notable tweaks shamelessly modified to the max as well as hacks and scripts that I came up on my own(and added tonnes of things over the months of development and testing). Without further delay, please read the rest of the OP :)

    Features
    • Zach's modified system_tweak (I/O Sched, Readahead, VM, TCP, 3G, BFS/CFS tweaks)
    • Zach's modified screenstate_scaling script - VM Scaling
    • Darky's Zipalign script that actually works (modified it a bit to get it actually working. It was broken as is before this.)
    • Patched libsqlite that disables the need to fsync. Extremely fast database writes.
    • app_process from Fugutweaks and system_server from Honeycomb 3.2
    • Quasi-charged! - Only using Supercharger's script but with ThunderBolt!'s own LMK/ADJ/OOM. Supercharger Update9 RC3.2.
    • zipalign binary
    • sqlite3 binary
    • remount script - Included in /sdcard/bolt_scripts/
    • sqlite_optimize script - Included in /sdcard/bolt_scripts/

    Benefits
    • Better performance, better battery life through Linux kernel tweaks catered for Android OS and flash memory.
    • Better battery life and performance through usage of screenstate_scaling whereby it switches governors/thresholds/VM depending on your screen state.
    • Better performance and battery life for database writes as fsync is not utilized anymore.
    • Better network throughput from TCP tweaks and 3G tweaks
    • Less RAM usage through zipalign. I found that market apps like Viber and PlantsVsZombies aren't zipaligned. Oh and Swype too. Surprised? Me too.
    • Reduced /dbdata, /data, /sdcard usage of *.db files and faster database access through defragmentization of sqlite db files (a lot of apps use Database to store data like Swype dictionaries, Game saves etc)
    • Faster disk access through remount script (noatime, disable barrier etc)
    • Less lags through Quasi-charger, with mutltasking (e.g. NFS shift + Opera mobile with 5 tabs fully opened and no lags)

    Minimum Requirements
    • Android Gingerbread 2.3.x
    • At least 2MB free on /system (Delete unused ringtones or useless apps like Aldiko/Allshare etc).
    • Root
    • Kernel that supports init.d
    • Ext4 lagfix if you want to use the remount script

    Downloads and changelogs are in the:
    Original ThunderBolt! thread

    Any support for Captivate must be placed here rather than the original thread.
    Quite a lot Captivate owners kindly asked me to post here so that the goodness of ThunderBolt! is shared to the masses. They have been thoroughly tested by a few Captivate owners.

    Note: remounti9000 can be used for Captivate.

    Warning: 3G addon is only compatible with i9000

    Note: You need to manually mount the /sdcard (or emmc) in recovery aside from mounting /system and /data. If you can't mount /sdcard or emmc, copy the bolt_scripts manually to your internal sdcard.

    Currently working devices
    Samsung Galaxy S i9000
    Samsung Galaxy S II i9100
    Samsung Captivate
    Samsung Vibrant
    Samsung Galaxy S 4G
    Samsung Galaxy S Plus i9001
    Samsung Galaxy Note
    Samsung Infuse 4G
    Samsung Galaxy Tab
    Samsung Galaxy S Plus i9001
    Samsung Galaxy SL i9003
    Samsung Galaxy SII AT&T i777
    Samsung Galaxy Nexus