So I applied the voodoo color settings from this thread here: http://forum.xda-developers.com/showthread.php?t=1401759
But they don't stick after reboot. Can anyone tell me how I can get them to stay when I reboot my Nexus?
You can always make an init.d script if your ROM supports it
Here's an example of how it should look, you can change the values to whatever you like
#! /sys/bin/sh
echo 2863311680 >/sys/class/misc/voodoo_color/red_multiplier
echo 3336681600 >/sys/class/misc/voodoo_color/green_multiplier
echo 3925507840 >/sys/class/misc/voodoo_color/blue_multiplier
echo -33 >/sys/class/misc/voodoo_color/blue_v1_offset
echo -26 >/sys/class/misc/voodoo_color/red_v1_offset
echo -30 >/sys/class/misc/voodoo_color/green_v1_offset
Or you can use an app called ROM Toolbox and use the "Scripter" to run this at boot
Sent from my Nexus S 4G using Tapatalk 2
Thanks! It's working great! However, I do notice that it sometimes makes my phone reboot on bootup about two times before it applies. But better than trying to remember my screen's values in Voodoo.
Update: I removed the ds files and corrected the powersaver script...
First of all... I would like to give credits to all the owner of this tweaks... This tweaks are not mine... I just compiled them
This tweak never fixes battery drain, it can or may improve your battery life
Let me first advice you that this mod worked for me, and would not fully guarantee that it would also work for you.. I'm using CM9 Alpha 4 with xxkpu as based...
With this mod... Battery life has increased by 25%... I can use the phone for browsing (connected with WiFi) and little gaming for 12 hours of semi-continuous use, it means that I lock the phone from time to time and resume my browsing (background apps still connects to the internet when sleeping) or gaming...
This is a Sysctl tweak with optimized Conservative mod... I have also attached the same tweak but with current Gingerbread system tweaks (I am currently using this, no problems so far)
Use Conservative governor as default after flashing this mod
Downloads:
see attachments
Other Tweaks to Improve Battery Life
I've been reading a lot lately... And here's what I've found out...
Disable Surface Dithering (This just fixed my overheating problem, and games runs more smoothly now)
Always use Conservative Governor
Disabling fast dormancy may improve our battery life (untested but I'm currently using this) To disable fast dormancy, just add this to you build.prop:
ro.ril.fast.dormancy.rule=0
Click to expand...
Click to collapse
Reloaded ICS
By the way, I also included Reloaded ICS... I tested it on our device and works very well... Reloaded ICS allows you to perform additional tweaking of the status bar and many more... Full details here
All credits goes to rob43
I've also attached the latest working version of Reloaded ICS...
To undo this Mod, Just delete this files:
/system/etc/init.d/10sysctl
/system/etc/init.d/01confpowersaver
/system/etc/init.d/95tweaks
/system/etc/sysctl.conf
Click to expand...
Click to collapse
Please post you feedbacks and suggestions
Thanks! Will try
Cheers
Sent from my GT-i9003 powered by Stable and Smooth CyanogenMod 9!
landono5 said:
First of all... I would like to give credits to all the owner of this tweaks... This tweaks are not mine... I just compiled them
This tweak never fixes battery drain, it can or may improve your battery life
Let me first advice you that this mod worked for me, and would not fully guarantee that it would also work for you.. I'm using CM9 Alpha 4 with xxkpu as based...
With this mod... Battery life has increased by 25%... I can use the phone for browsing (connected with WiFi) and little gaming for 12 hours of semi-continuous use, it means that I lock the phone from time to time and resume my browsing (background apps still connects to the internet when sleeping) or gaming...
This is a Sysctl tweak with optimized Conservative mod... I have also attached the same tweak but with current Gingerbread system tweaks (I am currently using this, no problems so far)
Use Conservative governor as default after flashing this mod
Downloads:
see attachments
Other Tweaks to Improve Battery Life
I've been reading a lot lately... And here's what I've found out...
Disable Surface Dithering (This just fixed my overheating problem, and games runs more smoothly now)
Always use Conservative Governor
Disabling fast dormancy may improve our battery life (untested but I'm currently using this) To disable fast dormancy, just add this to you build.prop:
Reloaded ICS
By the way, I also included Reloaded ICS... I tested it on our device and works very well... Reloaded ICS allows you to perform additional tweaking of the status bar and many more... Full details here
All credits goes to rob43
I've also attached the latest working version of Reloaded ICS...
Please post you feedbacks and suggestions
Click to expand...
Click to collapse
can use in MIUI???
How to get back to original settting
After all these tweaks if I had to get back to original configuration ?
How to do that.?
I just gave a quick look, nothing more.
01confpowersave has an error.
Right after
Code:
#scheduler cfq
there should be an "if". Or you add an if (I don't know what) or you remove fi; from here:
Code:
for i in $(ls -1 /sys/block/stl*) $(ls -1 /sys/block/mmc*)
do
echo "cfq" > $i/queue/scheduler
done
[COLOR="RED"]fi;[/COLOR]
EDIT: I think 95tweaks makes the boot slow because it wipes the dalvik-cache on every boot (and weirdly it creates a database of the zipaligned files, but it doesn't use it) (and FYI some of the tweaks there are already avaible in CWM Tweaks). The last part of the script is useless (read the last part of this: http://forum.xda-developers.com/showthread.php?t=1587553)
And please Mac OS X users, don't include .DS_Store and ._.SD_Store in your zips.
loSconosciuto said:
I just gave a quick look, nothing more.
01confpowersave has an error.
Right after
Code:
#scheduler cfq
there should be an "if". Or you add an if (I don't know what) or you remove fi; from here:
Code:
for i in $(ls -1 /sys/block/stl*) $(ls -1 /sys/block/mmc*)
do
echo "cfq" > $i/queue/scheduler
done
[COLOR="RED"]fi;[/COLOR]
I think 95tweaks makes the boot slow because it wipes the dalvik-cache on every boot (and weirdly it creates a database of the zipaligned files, but it doesn't use it) (and FYI some of the tweaks there are already avaible in CWM Tweaks). The last part of the script is useless (read the last part of this: http://forum.xda-developers.com/showthread.php?t=1587553)
And please Mac OS X users, don't include .DS_Store and ._.SD_Store in your zips.
Click to expand...
Click to collapse
Soo should I flash it?
Cheers
Sent from my GT-i9003 powered by Stable and Smooth CyanogenMod 9!
shail139 said:
After all these tweaks if I had to get back to original configuration ?
How to do that.?
Click to expand...
Click to collapse
You need to remove
Code:
/system/etc/01confpowersaver
/system/etc/95tweaks
/system/etc/init.d/10sysctl
/system/etc/sysctl.conf
while it's a little bit more problematic for "update-reloaded-1.9b4-cm9-050712.zip" because it replaces the original SystemUI.apk.
bscraze said:
Soo should I flash it?
Click to expand...
Click to collapse
Well, 'conservative' is not tweaked because of the 'if' problem, but there's no problem in flashing it, you still have all the sysctl.conf tweaks. Probably it's better to wait a flashable zip without all the Mac trash files, or manually remove them from the zip.
EDIT:
and I was wrong regarding the slow boot, I didn't read the script well enough.
I'll try to fix these... These mods aren't mine actually.. Thank you for your support...
I was wondering how the Mac files got there, I'm even using Windows...
Edit:
Got it, the mac files are from the original zips...
And the Fi; line should remain there... Well, according to the dev I've talked to, that is a needed command, I have really no idea what it does... But I'll guarantee that it works... Governors changed on boot...
The Fi is for stopping an if command...
if
<command>
else
<command>
fi
landono5 said:
And the Fi; line should remain there... Well, according to the dev I've talked to, that is a needed command, I have really no idea what it does... But I'll guarantee that it works... Governors changed on boot...
The Fi is for stopping an if command...
if
<command>
else
<command>
fi
Click to expand...
Click to collapse
Yes, I know, but, where is the if?
Code:
#!/system/bin/sh
#cpu
echo "300000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "1000000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "conservative" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
#scheduler cfq
for i in $(ls -1 /sys/block/stl*) $(ls -1 /sys/block/mmc*)
do
echo "cfq" > $i/queue/scheduler
done
fi;
#Conservative settings for saver mode.
echo "95" > /sys/devices/system/cpu/cpufreq/conservative/up_threshold
echo "120000" > /sys/devices/system/cpu/cpufreq/conservative/sampling_rate
echo "1" > /sys/devices/system/cpu/cpufreq/conservative/sampling_down_factor
echo "40" > /sys/devices/system/cpu/cpufreq/conservative/down_threshold
echo "10" > /sys/devices/system/cpu/cpufreq/conservative/freq_step
Edit:
And yes, you are right, the governor is changed. The problem is that scripts are not compiled, so errors come at runtime and the execution stops when an error is found.
The error is after the line that changes the governor. As I said, the problem is that conservative is not tweaked (the part after the fi).
Blue and not transparent status bar looks horrible, how to do it to look like before?
rascal0pl said:
Blue and not transparent status bar looks horrible, how to do it to look like before?
Click to expand...
Click to collapse
You can turn off Themes in Color Setting
loSconosciuto said:
Yes, I know, but, where is the if?
Code:
#!/system/bin/sh
#cpu
echo "300000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "1000000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "conservative" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
#scheduler cfq
for i in $(ls -1 /sys/block/stl*) $(ls -1 /sys/block/mmc*)
do
echo "cfq" > $i/queue/scheduler
done
fi;
#Conservative settings for saver mode.
echo "95" > /sys/devices/system/cpu/cpufreq/conservative/up_threshold
echo "120000" > /sys/devices/system/cpu/cpufreq/conservative/sampling_rate
echo "1" > /sys/devices/system/cpu/cpufreq/conservative/sampling_down_factor
echo "40" > /sys/devices/system/cpu/cpufreq/conservative/down_threshold
echo "10" > /sys/devices/system/cpu/cpufreq/conservative/freq_step
Edit:
And yes, you are right, the governor is changed. The problem is that scripts are not compiled, so errors come at runtime and the execution stops when an error is found.
The error is after the line that changes the governor. As I said, the problem is that conservative is not tweaked (the part after the fi).
Click to expand...
Click to collapse
I'm really confused... I know very little regarding android yet... What should I change regarding the script so that it will run smoothly...
Isn't this .zip can be flash straight away in cwm then is work just by that? I mean we don't have to adjust anything after flash it
Sent from my GT-I9003 using XDA
Just flash the zip and it'll be fine...
landono5 said:
I'm really confused... I know very little regarding android yet... What should I change regarding the script so that it will run smoothly...
Click to expand...
Click to collapse
It's Linux. Just change the file to:
Code:
#!/system/bin/sh
#cpu
echo "300000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "1000000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "conservative" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
#scheduler cfq
for i in $(ls -1 /sys/block/stl*) $(ls -1 /sys/block/mmc*)
do
echo "cfq" > $i/queue/scheduler
done
# fi;
#Conservative settings for saver mode.
echo "95" > /sys/devices/system/cpu/cpufreq/conservative/up_threshold
echo "120000" > /sys/devices/system/cpu/cpufreq/conservative/sampling_rate
echo "1" > /sys/devices/system/cpu/cpufreq/conservative/sampling_down_factor
echo "40" > /sys/devices/system/cpu/cpufreq/conservative/down_threshold
echo "10" > /sys/devices/system/cpu/cpufreq/conservative/freq_step
and you'll be done. Don't know what that fi was for, anyway, we want to reduce power drain and then the tricks have to be applied for that.
It will work on any galaxy devices ? Just a question
nooooooooooo, don't do it
he ported it for our device
Did anyone test this ?
I m using Remics rom, so can i flash this script...
Sent from my GT-I9003 using xda premium
vijaypalmanit said:
I m using Remics rom, so can i flash this script...
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
+1 and which Zip we have to flash? Which update? In tapatalk i can see this...
Hello Guys & Gals of XDA, I Bring to You My Custom Script That I dident Place in this Thread as things Get DeBumped Pretty Quick So i Placed it in Xperia Play Android Development,
This Script is Aimed to Get ridd of Laggs not Increase your FPS! - Also might not show Performance on Good Roms and Or Roms with Good Scripts,
Also a little Note:
Use the Universal Version if You Dont have 512 Mb Of Ram (Universal Removes LMK Settings)
Thread is Located Here:
http://forum.xda-developers.com/showthread.php?t=2319774
Can I run this on linaro slim beanz is the starter script fixed
ss beanz T989
hatememarkz said:
Can I run this on linaro slim beanz is the starter script fixed
ss beanz T989
Click to expand...
Click to collapse
Yea, Everything works, But use the Universal Version , Also make a backup as i dont have a remover and if the starter dosent work copy this into your build.prop:
# Pro-Tuned ADJ 1.2 by LENAROX
ro.FOREGROUND_APP_ADJ=0
ro.VISIBLE_APP_ADJ=4
ro.PERCEPTIBLE_APP_ADJ=3
ro.HEAVY_WEIGHT_APP_ADJ=2
ro.SECONDARY_SERVER_ADJ=15
ro.BACKUP_APP_ADJ=5
ro.HOME_APP_ADJ=6
ro.HIDDEN_APP_MIN_ADJ=3
ro.EMPTY_APP_ADJ=15
# Kernel Stabalizer;
dalvik.vm.checkjni=false
debug.kill_allocating_task=0
# Nitro Lagg Nullifier;
ENFORCE_PROCESS_LIMIT=false
MAX_SERVICE_INACTIVITY=false
MIN_HIDDEN_APPS=false
MAX_HIDDEN_APPS=false
CONTENT_APP_IDLE_OFFSET=false
EMPTY_APP_IDLE_OFFSET=false
MAX_ACTIVITIES=false
ACTIVITY_INACTIVE_RESET_TIME=false
MAX_RECENT_TASKS=false
MIN_RECENT_TASKS=false
APP_SWITCH_DELAY_TIME=false
MAX_PROCESSES=false
PROC_START_TIMEOUT=false
CPU_MIN_CHECK_DURATION=false
GC_TIMEOUT=false
SERVICE_TIMEOUT=false
MIN_CRASH_INTERVAL=false
Hi there, you might have seen my name, you might not, but it doesn't matter...but I come here in peace, wanting to get things clarified...
Regarding your Starter Kit, all it does is setprop, so why is
Code:
sleep 60
needed? Users will see a "jammed" screen for a minute...and another thing, to add lines to build.prop, setprop is not sufficient as most of the values will be reset after a reboot...you should have done this:
Code:
echo "ro.FOREGROUND_APP_ADJ=0" >> /system/build.prop
or something similar...
Now for your main Lagg_Nullifier_Gen_2.sh.pdf, I still see a lot of sleep commands being used....whereas the script can be completed within seconds...not every command requires you to wait that long...this is essential especially when you request users to convert this into an init.d script...it extends boot time and possible initial lags right after a reboot...and certain parts of the script contains unused lines which does nothing, like this:
Code:
while true; do
FREEMEM=`free | awk '{ print $4 }' | sed -n 2p`
FREEMEMMB=$(($FREEMEM/1024))
MFK=`cat /proc/sys/vm/min_free_kbytes`
MFKMB=$(($MFK/1024))
MFKMB1=$(($MFKMB+16))
MFKMB2=$(($MFKMB+32))
if [ "$FREEMEMMB" -lt $MFKMB1 ]
then
echo "done!"
It is just to calculate your free RAM...and if FREEMEMMB is lesser than MFKMB1, it just prints out "done!"...and nothing else...or I should say you have not integrated the script fully...another example is the drop cache lines...that is only needed after the system cache has accumulated after a certain period of usage, then it will be cleared...that was the initial purpose...so if you want users to use this script at boot, the drop cache part is not needed...
My suggestion is that your script generates another script in init.d, like V6 Supercharger to avoid conflicts...
Ryuinferno said:
Hi there, you might have seen my name, you might not, but it doesn't matter...but I come here in peace, wanting to get things clarified...
Regarding your Starter Kit, all it does is setprop, so why is
Code:
sleep 60
needed? Users will see a "jammed" screen for a minute...and another thing, to add lines to build.prop, setprop is not sufficient as most of the values will be reset after a reboot...you should have done this:
Code:
echo "ro.FOREGROUND_APP_ADJ=0" >> /system/build.prop
or something similar...
Now for your main Lagg_Nullifier_Gen_2.sh.pdf, I still see a lot of sleep commands being used....whereas the script can be completed within seconds...not every command requires you to wait that long...this is essential especially when you request users to convert this into an init.d script...it extends boot time and possible initial lags right after a reboot...and certain parts of the script contains unused lines which does nothing, like this:
Code:
while true; do
FREEMEM=`free | awk '{ print $4 }' | sed -n 2p`
FREEMEMMB=$(($FREEMEM/1024))
MFK=`cat /proc/sys/vm/min_free_kbytes`
MFKMB=$(($MFK/1024))
MFKMB1=$(($MFKMB+16))
MFKMB2=$(($MFKMB+32))
if [ "$FREEMEMMB" -lt $MFKMB1 ]
then
echo "done!"
It is just to calculate your free RAM...and if FREEMEMMB is lesser than MFKMB1, it just prints out "done!"...and nothing else...or I should say you have not integrated the script fully...another example is the drop cache lines...that is only needed after the system cache has accumulated after a certain period of usage, then it will be cleared...that was the initial purpose...so if you want users to use this script at boot, the drop cache part is not needed...
My suggestion is that your script generates another script in init.d, like V6 Supercharger to avoid conflicts...
Click to expand...
Click to collapse
Code:
FREEMEM=`free | awk '{ print $4 }' | sed -n 2p`
FREEMEMMB=$(($FREEMEM/1024))
MFK=`cat /proc/sys/vm/min_free_kbytes`
MFKMB=$(($MFK/1024))
MFKMB1=$(($MFKMB+16))
MFKMB2=$(($MFKMB+32))
this part happens to be(and it was mine) in my first version of mpengine script..just saying
Oh.. and 'ro.' means do not change value when its property was set ONCE.
Hello I want to share some of my old tweaks, credits to the author of tweaks and of the flashable zip.
Flash it in recovery then reboot, you will get more speed and more fps, so more smooth.
to restore stock settings reflash rom without wipe
What exactly this mod do? It's related to kernel? Overclock? Please, explain more details.
Pavamarea said:
What exactly this mod do? It's related to kernel? Overclock? Please, explain more details.
Click to expand...
Click to collapse
Some tweaks in build.prop
#!/sbin/sh
echo "persist.sys.dalvik.hyperthreading=true" >> /system/build.prop
echo "# System Properties" >> /system/build.prop
echo "cpu.fps=auto" >> /system/build.prop
echo "gpu.fps=auto" >> /system/build.prop
echo "# CPU & GPU Properties" >> /system/build.prop
echo "ro.sys.cpu.defaultfreq=auto" >> /system/build.prop
echo "ro.sys.gpu.defaultfreq=auto" >> /system/build.prop
Click to expand...
Click to collapse
Hi all,
Unfortunatelly, I'm not allowed to reply to developer posts anymore.
I have to admit that I was inactive quite a while, but I hope someone can reuse my quick fix
and maybe someone could move this post to it's right place.
First of all, thanks to Ryuinferno for the init.d enable script.
[MOD][APK+SCRIPT+ZIP] Enable Init.d for Any Phones w/o Need of Custom Kernels!!!
Finally it works for me very good !!!
The problem was:
/system/bin/sysinit couldn't find run-parts,
so I added the path to the PATH export, and :good:
I modified the downloaded term-init.sh just a little bit.
Changed (line 108 & line 121, line 109 & line 122 optional)
Code:
echo "export PATH=/sbin:/system/sbin:/system/bin:/system/xbin" >> /system/bin/sysinit
echo "run-parts /system/etc/init.d" >> /system/bin/sysinit
To
Code:
echo "export PATH=/su/xbin:/sbin:/system/sbin:/system/bin:/system/xbin" >> /system/bin/sysinit
echo "logwrapper run-parts /system/etc/init.d" >> /system/bin/sysinit
Have fun...
It is better to change the script before you run it,
otherwise you have to change the file /system/bin/sysinit afterwards.
kind regards
Gerry