these tweaks work very well on the nexus 7, and is this the screen_state scaling necessary with the tweaks added? does it help much with battery at all?
Well do you mean it came from xda?
btw: what does the vm.overcommit_ratio do?
any good suggestions about it then please?
I'm the real Lag Doctor hmph.
I flashed the latest one (that has the remount script for the One S) together with the screenstate scaling addon, but it got stuck on bootanimation. Had to reflash my rom. Any ideas?
But in OP it says that screen state scaling is now compatible with cm10. (init.d script)
Sent from my HTC One S using Tapatalk 2
these tweaks work very well on the nexus 7, and is this the screen_state scaling necessary with the tweaks added? does it help much with battery at all?
Yes, I can attest to some parts of your scripts were indeed copied from XDA (with some remnants belonging to ThunderBolt!)
About vm.overcommit_ratio, it's dependent on how much you're willing to risk triggering the OOM killer. However, since the LMK in Android is set to kill apps incrementally, the problem with an out of controller OOM killer is much less discussed. Having it at 50 is definitely not the most optimized value. This however is very dependent on the apps Android use as well as how much memory is allocated per foreground app. With Android setting a hard limit of 128M for the heap_size, I think you could play around with the setting a bit to make apps less prone to the OOM.
Note that you would need to set overcommit_memory to 2 to use overcommit_ratio.
I'll dig up the code to see what it actually does before commenting more on it. I remember tweaking the overcommit_memory a bit and some things went haywire. If I remember correctly, the OOM killer went nuts.
Do you still want me to continue offering constructive criticism on your script?
Some AOSP based ROMs are still incompatible with the screenstate_scaling due to its older problem of didle code. I'm not sure which of the ones are incompatible, though I know CM10.1 is compatible.
It helps with the battery as it tries to scale the frequency less when the screen is off.
Linux desktop distro has a tweak used from mobile?
I dont see anywhere in xda
which tweaks belongs to thunderbolt?
Tell me and ill give u a credit
I love potatoes
if [ -e *]
fi
Linux has been used for mobile devices even before Android existed. :/
It's not the tweak values, but the format of the tweaks.
The
I was the one that started using it.Code:if [ -e *] fi
The busybox mount /system was devised by a member here which I credited him.
The busybox remount relatime came from ThunderBolt!.
I don't need credits. As long as you recognize that your so called script isn't >90% your own creation and be humble on your creation based on other people's work, I'm fine with it.
Good to know Let me know if you have any issues with it.
If statements ?
So its like youre saying you made the linux kernel?
If statement was used way back even before this forum was created lol
Ill give you credits for the remount btw thanks.
I love sweet potatoes
I said, I was the one that started using it to validate whether or not the sysfs interfaces were valid.
I don't need credits. I only need you to be humble on whatever scripts that you took from the community. It's not your own tweaks, it's what you kanged from whoever devised it first. Know that and don't take other people's hard work for granted.
i have instaleed script of lenarox than can this install? will i have problems?
You will need to remove Lenarox's script in order to install ThunderBolt!.
can i ask you some stupid questions?
1. its is the same script with lenarox or?
2. this is same with sql super launcher script?
3. can you answer me theese^ questions?
thnx a lot, and that mean i will dont have lag into games with your script?It's not the same script as Lenarox's. His script prefers to circumvent the original virtual memory pdflush and prefer's to run a script in the background to drop the caches (only page caches though) that not only drains the battery, it doesn't selectively flush caches (old dirty memory should be freed up first e.g. LRU mechanism that the pdflush is accustomed to).
In his latest script, he attaches minfree/adj tweaks which creates a mismatch between the Android LMK and the Linux LMK further aggravating the problem.
Lenarox's script also doesn't have some parts of ThunderBolt! like remount, sqlite optimization, zipalign, governor scaling with screenstate_scaling, VM scaling and some other optimizations that you can read about in the first post.
About the Super Launcher script, it's basically Supercharger tweak with sqlite optimization.
Edit: Oh wait, it's patched into services.jar. However, with the patched services.jar, there are some problems that makes the LMK half-baked. If you want, you can refer to the Supercharger thread about it. I've explained in detail that includes some source code reference.
thnx a lot, and that mean i will dont have lag into games with your script?
sry for my questions...
you are master!
Try it and let me know
I don't claim you won't have lags, but I do claim that you'll have better performance and battery life.
i know thanks is a small word for your job but i will try to donate you soon as i can...
Hey pikachu!
Which zip setup would you recommend for the galaxy s III with 2gig memory?! And where can I find this super launcher I'm hearing about
Sent from my SPH-L710 using Xparent SkyBlue Tapatalk 2
I'm assuming this doesn't play nicely with v6 supercharger right? And looking at this, combining it with seeder should be all the in it tweaks needed for a smooth experience correct? Because the way my rom is setup now it has a bunch of random tweaks combined into one and the phone is sort of sluggish. I feel like a lot are conflicting and wondering if the latter is a good combo.
---------- Post added at 11:02 PM ---------- Previous post was at 10:53 PM ----------
Currently in my rom. Any interference ya think?
-Many build.prop tweaks for better performance
-Pimp My ROM tweaks
-Seeder Script
-Velocity Tweaks
-AC!D Audio
-xLoud
-KingBeatz
-Many other init.d tweaks
-Bravia Engine
su
sysctl -a | grep vm
dirty_ratio = 30
dirty_background_ratio = 15
vfs_cache_pressure = 50
dirty_ratio = 20
dirty_background_ratio = 10
vfs_cache_pressure = 50
dirty_ratio = 10
dirty_background_ratio = 5
vfs_cache_pressure = 50
echo "200000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
echo "200000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq;
echo "100 100 100" > /sys/class/misc/gpu_clock_control/gpu_control;