[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Only echo eh? So it's more just for cpu0 scripts and whatnot...which are sometimes awesome, sure, but still severely limited when you consider converting an init.d script to ktweaker. Also, hypothetically, a lot of echo stuff I've seen in some init.d scripts can be done without it, such as build.prop tweaks and stuff - the actual guts of some real complex scripts are not echo commands :P

For anybody using Dead by April v2.2 (great battery profile) here's the accompanying script:

#Cpu1
echo "conservative" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor

echo "25" > /sys/devices/system/cpu/cpufreq/conservative/down_threshold

echo "15" > /sys/devices/system/cpu/cpufreq/conservative/freq_step

echo "3" > /sys/devices/system/cpu/cpufreq/conservative/sampling_down_factor

echo "55" > /sys/devices/system/cpu/cpufreq/conservative/up_threshold

Just save it as "Dead by April V2.2 Script" with no extension and put it in your internal storage>KTweaker>scripts folder and load it up in the app. What this script does is different than the old asswax cpu1 scripts, the difference is that cpu0->1st core, what is controlled with ktweaker and cpu1->2nd core, just uses same settings as the first by default. With this script, your ktweaker settings stick for the 2nd core however when you are doing most things, that don't require much juice, as long as you stay on the 1st core it will be running the same settings you have in the profile except for governor, those settings you can see above. The difference between this and "asswax" scripts is simple, it doesn't use ktweaker to set cpu0 settings like usual and the script is what controls the otherwise inactive files; it's the opposite, it uses ktweaker to set cpu0+cpu1 by default, then loads a different cpu0 gov and settings for it and takes over, not allowing the profile's gov settings to take hold unless you start using the 2nd core.

Don't know why it wasn't included when the original batch of "ports" came thru, this script specifically is not aimed at quad-core devices as it only targets the 2nd core. The values themselves have not been changed, nothing has been added or removed, and all credits go to the creator (Luigi?) :)

Okay I guess the difference between the S4 script and the hypothetical S3 script and reason this script wasn't ported was that the difference may not be that dramatic on the S3 as it is the S4 with the same numbers in the script and they need to be tweaked, thresholds for example. Turning an S3 into a single core phone (that utilizes the 2nd only when needed)e means getting rid of 1 core but an S4 to a single core phone is dropping 3 cores unless needed......so maybe this script and profile with the GS4 is a more extreme version of what we can achieve on the S3? I'll read up on the settings and see if anything should maybe be tweaked to make for a better script on the GS3. For the profile, there are a few things I like to add that many profile creators don't really change much but I do have a preference because of prior experience:

CPU Underclock of -125 is enough at the moment, but I also -50 the GPU across the board (900, 1000, 1100).

Extras->Screen Off Profile Mhz 702 -> 594 MHz

Extras->Vibration Strength 20 -> 70 come on!!

Extras->GPU Governor ondemand ->simple (this is a big one!)

Extras->Congestion Contol cubic->westwood (only one I know, from quantum kernel. There has been like 8 of these added in the last month)

That's it for profile changes! Some small changes that I prefer and I think you will to. I'm just now going to start using this in conjunction with the script and see if anything should be tweaked. I also wanted to mention there is also a Balanced Bull script but made for 4 CPU's controlled individually, not 2 - so I need to port it by only deciding which 1/2 of the freakin' original is more important! I'll get a clue by comparing the profiles themselves, I'll see which govs Perseus decided to keep.....take care yall you'll hear from me again soon.