View Single Post
Old December 23rd, 2011, 04:04 AM   #10 (permalink)
Hawker
Senior Member
Thread Author (OP)
 
Hawker's Avatar
 
Join Date: Aug 2011
Location: UK
Posts: 3,929
 
Device(s): GT-I9505
Carrier: EE UK (4G)

Thanks: 558
Thanked 1,819 Times in 1,121 Posts
Default

Well most of us on CheckROM on here dont have them Syd, so I guess not overly so.

The Ultimate Kernel Cleaner deletes the following from init.d:
S_volt_scheduler
S70zipalign
S90scheduler
S99finish
89system_tweak
98system_tweak
S89system_tweak
S98system_tweak
S90screenstate_scaling
90screenstate_scaling
98screenstate_scaling
S98screenstate_scaling

Seems like this was developed to clean up a specific kernel in particular perhaps.


The CheckROM scripts are:

02modules
#!/system/bin/sh
# Load MODULES
sleep 1
insmod /system/lib/modules/cifs.ko
echo "+++ EXTRA MODULES activated +++";

This is to do with mounting samba file systems, so probably not needed by most


05module
#!/system/bin/sh
if [ -e /sys/devices/virtual/bdi/179:0/read_ahead_kb ];
then
echo "Modifying read_ahead_kb parameters"
echo "4096" > /sys/devices/virtual/bdi/179:0/read_ahead_kb
else
echo "read_ahead_kb not found"
fi

I've never had any keyboard issues, so probably not important.


90ram-tweaks
#!/system/bin/sh
# Copyrightę 2011 Juwe11
if [ -e /sys/module/lowmemorykiller/parameters/minfree ];
then
echo "2560,4096,6144,12288,14336,18432" > /sys/module/lowmemorykiller/parameters/minfree
fi
if [ -e /proc/sys/vm/swappiness ];
then
echo "50" > /proc/sys/vm/swappiness
fi
if [ -e /proc/sys/vm/vfs_cache_pressure ];
then
echo "10" > /proc/sys/vm/vfs_cache_pressure
fi
if [ -e /proc/sys/vm/dirty_expire_centisecs ];
then
echo "500" > /proc/sys/vm/dirty_expire_centisecs
fi
if [ -e /proc/sys/vm/dirty_writeback_centisecs ];
then
echo "1000" > /proc/sys/vm/dirty_writeback_centisecs
fi
if [ -e /proc/sys/vm/dirty_ratio ];
then
echo "90" > /proc/sys/vm/dirty_ratio
fi
if [ -e /proc/sys/vm/dirty_background_ratio ];
then
echo "5" > /proc/sys/vm/dirty_background_ratio
fi

Seems to have something to do with what the system does when memory gets low


98mounts
#!/system/bin/sh
/system/xbin/busybox
mount -o remount,noatime,barrier=0,nobh,noauto_da_alloc /data
/system/xbin/busybox mount -o remount,noatime,barrier=0,nobh,noauto_da_alloc /system

Not sure about this one. Mounting /data and /system slightly differently to normal but not entirely sure why

99complete
#!/system/bin/sh
busybox mount -o remount,rw -t rootfs /
# sh /system/bin/userinit.sh
sync;
setprop cm.filesystem.ready 1;
setprop dc.filesystem.ready 1;
setprop oxygen.filesystem.ready 1;

No idea what this one does.


S95zipalign
#!/system/bin/sh
# Automatic ZipAlign by Wes Garner
# ZipAlign files in /data that have not been previously ZipAligned (using md5sum)
# Thanks to oknowton for the changes
# Credits to doctorcete from Hyperdroid team for adding system/app and /system/framework
LOG_FILE=/data/zipalign.log
if [ -n $zipalign ] && [ $zipalign = "true" ];
then
busybox mount -o remount,rw /;
busybox mount -o remount,rw -t auto /system;
busybox mount -o remount,rw -t auto /data;
fi;
busybox mount -t tmpfs -o size=70m none /mnt/tmp;
echo "Starting Hyperdroid Automatic ZipAlign " `date` | tee -a $LOG_FILE;
if [ -e $LOG_FILE ];
then
rm $LOG_FILE;
fi;
echo "Starting Automatic ZipAlign $( date +"%m-%d-%Y %H:%M:%S" )" | tee -a $LOG_FILE;
for apk in /data/app/*.apk ;
do
zipalign -c 4 $apk;
ZIPCHECK=$?;
if [ $ZIPCHECK -eq 1 ];
then
echo ZipAligning $(basename $apk) | tee -a $LOG_FILE;
zipalign -f 4 $apk /cache/$(basename $apk);
if [ -e /cache/$(basename $apk) ];
then
cp -f -p /cache/$(basename $apk) $apk | tee -a $LOG_FILE;
rm /cache/$(basename $apk);
else
echo ZipAligning $(basename $apk) Failed | tee -a $LOG_FILE;
fi;
else
echo ZipAlign already completed on $apk | tee -a $LOG_FILE;
fi;
done;
for apk in /system/app/*.apk ;
do
zipalign -c 4 $apk;
ZIPCHECK=$?;
if [ $ZIPCHECK -eq 1 ];
then
echo ZipAligning $(basename $apk) | tee -a $LOG_FILE;
zipalign -f 4 $apk /cache/$(basename $apk);
if [ -e /cache/$(basename $apk) ];
then
cp -f -p /cache/$(basename $apk) $apk | tee -a $LOG_FILE;
rm /cache/$(basename $apk);
else
echo ZipAligning $(basename $apk) Failed | tee -a $LOG_FILE;
fi;
else
echo ZipAlign already completed on $apk | tee -a $LOG_FILE;
fi;
done;
for apk in /system/framework/*.apk ;
do
zipalign -c 4 $apk;
ZIPCHECK=$?;
if [ $ZIPCHECK -eq 1 ];
then
echo ZipAligning $(basename $apk) | tee -a $LOG_FILE;
zipalign -f 4 $apk /cache/$(basename $apk);
if [ -e /cache/$(basename $apk) ];
then
cp -f -p /cache/$(basename $apk) $apk | tee -a $LOG_FILE;
rm /cache/$(basename $apk);
else
echo ZipAligning $(basename $apk) Failed | tee -a $LOG_FILE;
fi;
else
echo ZipAlign already completed on $apk | tee -a $LOG_FILE;
fi;
done;
echo "Automatic ZipAlign finished at $( date +"%m-%d-%Y %H:%M:%S" )" | tee -a $LOG_FILE;

zipaligns the apps in /system/app and /data/app
I think this is only done once on the initial run after the ROM has been flashed, so it shoudlnt be needed after this. This is probably why the first run takes so long.
__________________
My Scripts/Threads
My Web Site
Hawker is offline  
Last edited by Hawker; December 23rd, 2011 at 04:29 AM.
Reply With Quote