[CWM][SCRIPTS][TWEAKS] ThunderBolt! v2.6.1 - 3/5/12 [Major Update Updated!]

[pikachu01]

yeah the vacuum would be a little too much overkill on boot.
zipalign wouldnt be too bad after the first time since an app will be zipaligned only once

Yup. Probably a good idea for zipalign.

well as it stands you already recommend in the OP that zipalign CAN be added to init.d without major slowdowns, so i think the -c idea would just speed up the boot time and not affect performance much
as for optimizing sql i think that should be left up to the user

but here's my recommendation for all of this to make it super simple for users

keep the scripts in /system/etc/bolt_scripts/ (as they are) maybe put them in a subfolder just to separate them, and then make some scripts like this;

S##init_zipalign
calls the actual zipalign script but uses -c

and S##init_sqloptimize
calls the actual sqlite optimize script but uses -c

then suggest users copy those respective files to their init.d folder to run at boot so that if a user has a slower device they dont have to load them (or just load zipalign, however they want to do it) and if they have a faster device they can choose to see if the effects of the potentially laggy first few moments of home screen action are worth the benefit for them individually

only reason i recommend the separate scripts is because i dont know how to launch a script with -c from inside the script itself

anyway that's my 2c

Good idea

Thanks! I'll implement this (and the automount in the next version)

 

[RaymondPJR]

Thunderbolt!

Yes, the LMK settings doesn't work (it works half way) hence you should be better off not flashing it.

Also, Script Manager needs to be updated. The ICS version works well without issues (I tried it).

I can confirm the newer Scriptmanager works fine, although it did take a while to open the first time. I figure that's a dalvik cache issue. I also downloaded and flashed the LMK 50 version replacing the LMK 60, and the difference is like night and day so far. Will report back more tomorrow.

EDIT: I know you said to not use LMK with ICS, but I did this yesterday before your post. So far the 50 value is working fine.

 

[iXNyNe]

Yup. Probably a good idea for zipalign.



Good idea

Thanks! I'll implement this (and the automount in the next version)

for safety i'd also have each install of the main tb! zip remove these init files, and probably remove any existing copies of the scripts in init.d and bolt_scripts folders (if they dont already, i cant remember)

this will make it easier for you to be sure that between releases (or between installs) users are actually putting these items back in place on their own and hopefully this encourages a reminder to check that nothing about these scripts has changed and they should read the changelog

another route would be to provide a zip that simply removes the new init scripts and doesnt touch anything else - this would be handy for someone who somehow gets stuck in an overly lock boot up due to the vacuum or something.

i'd assume anyone who has already installed multiple versions of tb! has (like me) prepped their own separate init.d file to load after tb! scripts so it will overwrite any settings tb! sets that they would like different than tb! sets them out of the box - may be a point of interest to encourage this behavior from users of tb! by adding recommendation (or even guide)
ex: i dont like EVERYTHING the included siyah script does, but i dont like modifying it every time there's a new release of tb! so i load it for most settings and then set one or two things differently in a separate script that loads after the siyah script

 

[pikachu01]

I can confirm the newer Scriptmanager works fine, although it did take a while to open the first time. I figure that's a dalvik cache issue. I also downloaded and flashed the LMK 50 version replacing the LMK 60, and the difference is like night and day so far. Will report back more tomorrow.

EDIT: I know you said to not use LMK with ICS, but I did this yesterday before your post. So far the 50 value is working fine.

It might have more similar values (50MB than 60MB), but I still don't recommend it as the values are mismatching (only part of the values stick). Having all the values stick or none at all is the best choice as it'll either go all the way or remain the default value. Having it halfway creates unexpected conditions sometimes.

for safety i'd also have each install of the main tb! zip remove these init files, and probably remove any existing copies of the scripts in init.d and bolt_scripts folders (if they dont already, i cant remember)

this will make it easier for you to be sure that between releases (or between installs) users are actually putting these items back in place on their own and hopefully this encourages a reminder to check that nothing about these scripts has changed and they should read the changelog

another route would be to provide a zip that simply removes the new init scripts and doesnt touch anything else - this would be handy for someone who somehow gets stuck in an overly lock boot up due to the vacuum or something.

i'd assume anyone who has already installed multiple versions of tb! has (like me) prepped their own separate init.d file to load after tb! scripts so it will overwrite any settings tb! sets that they would like different than tb! sets them out of the box - may be a point of interest to encourage this behavior from users of tb! by adding recommendation (or even guide)
ex: i dont like EVERYTHING the included siyah script does, but i dont like modifying it every time there's a new release of tb! so i load it for most settings and then set one or two things differently in a separate script that loads after the siyah script

I usually have my own scripts too that is derived from the bolt_scripts. I will remove the init.d scripts with every new install That's my plan from the beginning if I do add any new scripts.