Originally Posted by Droidificator
And now that I've got init.d, I feel better, but I'm not really sure what I can do with it...
Sent from my H1S using XDA Premium.
Maybe I should explain my last post, I'm running Stock official release rooted, many people believed that init.d support couldn't be used for Stock builds but this allows you to be able to run scripts like this one I'm running "CLICK THIS LINK TO THE RIGHT, IT"S WORTH IT!!!" (http://forum.xda-developers.com/show....php?t=1584508
This is the CPU editor which allows you to change cpu settings on a stock kernel and custom kernels as well. The One S has an amazing stock kernel but you can tweak it to control when the second core picks up and drops off, the cpu editor changes those settings depending on how you want it to perform for you by profile.
2. Performance and Battery saver
3. Battery saver
My pic above shows the first day of testing with moderate to heavy use using battery saver (#3) leaving the Min and Max at their original settings 384 and 1512 but telling the cores to work in a different way, instead of the second core picking up at 90% of the first core it picks up at 10% till it makes it to 100% of the first cores process making it snappy but when it reaches 100% the second core drops off and stops running.
When you put it in sleep mode it drops the first core to min settings and holds it there till it's needed. I had to have the init.d script in order to use this script because I like stock for the time being, personally I'm a MIUI fan but Sense 4 has a good hold on me at the moment.
Init.d allows these types of scripts to run on a device which in the past had to be a community developed rom, now it's possible to use a stock device rooted and still have the benefits of developed scripts like multitasking script, supercharger v6, OC daemon (Virtuous) etc...
Hope this clears things up for you.
Device #1 Tmo Galaxy S4