yashsingh1/xdaforums huggingface dataset:
[HTC One S] Orical:
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://xdaforums.com/showthread.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.

1. Performance

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.
[HTC One S] v3n3:
As far as I can see, "init.d" Scripts are Tweaks which are dynamicly loaded on each startup by the ROM ( if the said rom Supports it ).

Im pretty new to Android, so Im googling my way thru it right now, but it seems pretty great what you can achieve with those Scripts :-)

EDIT:

Woops, looks like someone was fast with a better explanation ^^

Thank you Orical
[HTC One S] Orical:
Most scripts that you'll find here are specific for their respective devices, the cpu editor is more of an universal tool like others posted in other forums that haven't made their way around the block yet but for the most part you would be hard pressed to find scripts that are meant for anything else on these forums.

Devs are really good about warning users if there is something that might be high risk to use.

You are right about the definition though, good to see some one uses that great friend Google that answers all your questions without asking anything in return.... Google is awesome! lol...
[HTC One S] MadJoe:
Orical, V3n3, thanks for the replies. I had an idea of what it did before, but I'm a lot clearer now. I know I've seen threads that say "ROMs with init.d only" or kernels, whatever, but now I can't find them anywhere.

As for messing with the cores, I'm a little hesitant. But I'm also a little curious. Does that script allow for any overclocking? I'm not looking for much, maybe like an extra 100MHz (just to get back what the 1.84 update took away, really).

Never mind, I'm just going to give it a try, made a nandroid and going for it. Thanks again.
[HTC One S] smokin1337:
Yes you can overclock, check it out the link is in my sig
[HTC One S] Orical:
No problem, this opens up options for all stock rom users now that had to leave stock in order to use script enhancements. I don't want to seem like this is my project here, Smokin1337 is the thinker and finds ways to make everything better for everyone. I merely tested it for our device but I'm sure devs will find this useful everywhere, big thanks to smokin for the find.
[HTC One S] philliman:
How does one apply this? I've flashed it and now what? Thanks for the great work by the way!
[HTC One S] philliman:
Edit: I think I figured it out with terminal emulator.
[HTC One S] Orical:
Now that you have init. d you can install a script that you can use to do anything you want, I would suggest the CPU editor smokin1337 made. Look at his sig, it's designed to help battery life without having to install a custom kernel bit it also works with custom kernels too.

PS yes terminal emulator is how you use it type "SU" then "CPU" and follow the menu from there.
[HTC One S] MadJoe:
I'm using it now, set to battery/performance and already I'm seeing a decent increase in my stand by time. Excellent script!
[HTC One S] Orical:
Yeah he knows his stuff, it's not loaded in gimmicks and it does exactly what it should. More need to try it.
[HTC One S] greengoldmello:
Is it possible to flash this without a custom recovery? Im on a evolte and i need this as a stepping stone to improve my multitasking, but i don't want to HTC unlock for a recovery.
[HTC One S] smokin1337:
If you are rooted follow the manual method in the op

Basically add this line to /system/etc/init.qcom.post_boot.sh

/system/etc/init.d/*

Then create the init.d folder
[HTC One S] jaysins:
Tried this the other night, went to bed without charging my phone and my phone only dipped 1% in eight hours. Definitely a huge improvement on battery and I chose the middle setting. Awesome work.
[HTC One S] Orical:
Its good to see the reports for the CPU editor is worth it for people, I've been using it for a few days and the battery is lasting me 2 days with moderate use but leaning on it watching a 2 hour movie and being on the forum a lot put me to about a day and a half.
[HTC One S] smokin1337:
Yep but can you guys post about the CPU editor in its thread found in my Sig. Tryin

To keep it active. Thanks
[HTC One S] adrien1977:
I just looked a the script and i think there may be a mistake

this is the script

if [ -e /system/etc/init.qcom.post_boot.sh ]; then
echo "/system/etc/init.d/*" >> /system/etc/init.qcom.post_boot.sh
else
[B]echo "/system/etc/init.d/*" > /system/etc/init.post_boot.sh[/B]
fi
if [ -e /system/etc/init.post_boot.sh ]; then
echo "/system/etc/init.d/*" >> /system/etc/init.post_boot.sh
else
echo "/system/etc/init.d/*" > /system/etc/init.post_boot.sh
fi

if [ -e /system/etc/post_boot.sh ]; then
echo "/system/etc/init.d/*" >> /system/etc/post_boot.sh
else
echo "/system/etc/init.d/*" > /system/etc/post_boot.sh
fi

I think it should be

if [ -e /system/etc/init.qcom.post_boot.sh ]; then
echo "/system/etc/init.d/*" >> /system/etc/init.qcom.post_boot.sh
else
[B]echo "/system/etc/init.d/*" > /system/etc/init.qcom.post_boot.sh[/B]
fi
if [ -e /system/etc/init.post_boot.sh ]; then
echo "/system/etc/init.d/*" >> /system/etc/init.post_boot.sh
else
echo "/system/etc/init.d/*" > /system/etc/init.post_boot.sh
fi

if [ -e /system/etc/post_boot.sh ]; then
echo "/system/etc/init.d/*" >> /system/etc/post_boot.sh
else
echo "/system/etc/init.d/*" > /system/etc/post_boot.sh
fi

I think in the original script you end up writting twice /system/etc/init.d/* to init.post_boot.sh
[HTC One S] WCCobra:
Ooo... that looks dangerous

Should be >> as well I think.
[HTC One S] adrien1977:
I like the sarcasm when i was just trying to point out a possible small mistake.

I did not say it was dangerous or anything like that.

I guess i'll just stay quiet next time.

A you are right or thanks would have been enough.

Cheers mate.
[HTC One S] WCCobra:
Haha. I just glanced at what you posted, but I know that a ">" will overwrite the entire /system/etc/init.post_boot.sh with "/system/etc/init.d/*". I'm not sure if that's intended or not. Perhaps the test condition is failing? Could try a -f instead of -e
[HTC One S] adrien1977:
I edited the first file manulally.

Why do you need:
[HTC One S] WCCobra:
You're modified file should probably be

echo "/system/etc/init.d/*" >> /system/etc/init.qcom.post_boot.sh

There is a zipalign init.d script that requires zipalign. On my phone, zipalign was not there, and my guess is it is not included in the ROM by default. Placing the executable in the /system/xbin allows the zipalign init.d script to run properly.
[HTC One S] adrien1977:
ok.

thanks.

Let's see if this has really an impact then.

Rebooting the phone now.
[HTC One S] smokin1337:
It checks for init.post_ boot.sh if it's there it modifies it if not it creates it. Linux by default will load init.post_boot.sh by default that's why each statement will make it of it doesn't exist. I have edit out some stuff in the Init.d script, like zipalign that was for my Rom. Will update it when I get home.
[HTC One S] Orical:
Actually there is a reason it was written that way, there are other devices out there that don't use the prefix "qcom" so in order for this to work equally for all devices he made it so it would look for the file itself which worked for a few people on lower end devices.

It's not dangerous and I can see why your pointing it out but the MT4G doesn't have the file named "qcom.post_boot.sh" it's simply named "post_boot.sh" and other devices have something different in the prefix this way it works by default.

Solved...
[HTC One S] WCCobra:
I understand why it was structured, however overwriting the content that is in post_boot.sh might not be the best idea. Appending to the file is safer.
[HTC One S] smokin1337:
It does append if the file exists. >> appends to the end. If it doesn't exist it gets created by using >. I do see one error though it only writes one line i have to add another line, #! /system/sbin/sh

EDIT: Fixed now in op
[HTC One S] MadJoe:
Should those of us who flashed this before you fixed that flash it again, or its not a big deal?
[HTC One S] smokin1337:
Nah if it works you had the needed file. I just fixed it for those that didn't have the file.
[HTC One S] Elloco305:
Thank you for this.
[HTC One S] unk2009:
I'm going to give this a go after work, will report back later.. Thanx :cool:
[HTC One S] plakers:
First impression after 2days : good improvements in battery life, and even in DualCore de/activation factor! I removed SetCPU : both core were online all the time (some problems with the 3.x versions), and it gaves me some errors with the CPU script.

Now with LeeDroid, LowKernel, and init.d/cpu script (battery saver) : everything seems to be fine, and noticed some improvements in battery life. Phone's very stable, and set the options to be sticky.

Anyway to get an option the set "max freq while screen off" and/or "max freq and 1core active while screen off" ? ;)

Thanks for the job done
[HTC One S] apg5031:
do i just flash it in recovery? and do i have to do anything else with that or this is it?

how do i check if it is working?

whats the deal with the CPU editor?
[HTC One S] unk2009:
This is with moderate -heavy use...

Great job, thank you :cool:
[HTC One S] Orical:
This is how you know it's working, it's all in the stats and proof is always not having to worry if your going to be without battery when you need it most. Good to see that it's helping people as much as it helps me.
[HTC One S] blessup:
i get cpu not found when typing cpu in terminal emulator. Su does enable super user # sign and the boot file does have the correct line at the end of it. Any suggestions?
[HTC One S] Orical:
Sounds like something went wrong while flashing the zip in recovery. Look in init.d and see if there is a file named 00CPUeditor.
[HTC One S] unk2009:
My final battery stats :cool:

Thanks again, donation coming your way after returning from the Dominican Republic (vacation time!
[HTC One S] blessup:
I used twrp will that do it correctly?
[HTC One S] blessup:
Am I doing something wrong? I boot to recovery flash init-d then boot back to sense run terminal emulator type su get super user # then type cpu all lowercase error CPU not found. Flashed with cwm and twrp downloaded twice.

This is the name of my post boot file

init.qcom.post_boot.sh

It says this at the end but 5 times

/system/etc/init.d/*
[HTC One S] plakers:
I'm going to move to AOKP, as it's only "init.d" related stuff, all things may work especially the "cpu" script (if no other init-scripts overrides the "sticky" options), anyone on an AOSP-Rom can confirm ?

Currently with LeeDroid&LowKernel, everything is fine.

EDIT : Installed AOKP 39... And the "cpu-script"' - will feedback soon on battery/perf increase ;)
[HTC One S] Orical:
That is more like what I was waiting to see, at the end of the file there should be one line blank then( /system/etc/init.d/* ) and then hit enter once and save.

If it's there it should work but 5 times might be whats causing it to work wrong, when we first did this I put that line in myself and did the rest by hand an it worked like a charm, so for the by-hand-method do this...

go to: /system/etc/init.qcom.post_boot.sh and clean out what's there after the word ( esac ) so that there's no line after it and hit enter once, then put the line : /system/etc/init.d/* and hit enter again then save.

Now go to system/etc and make a new folder and rename it ( init.d ) and save it, after that you should be all set to install all of the scripts you want, personally I use "Root Explorer" but there are others "RE" is a paid app but it's well worth the money as it's a cleaner UI and it does have the best features.

Hope this works for you.
[HTC One S] LikeaG2root:
Do settings require a reboot to take effect?

Sent from my cm_tenderloin using Xparent Cyan Tapatalk 2
[HTC One S] plakers:
Nope they're taken "on the fly" ! (ondemand factors, governors, freq. settings) - (Even if a reboot can confirm that the sticky is OK)
[HTC One S] Bastaerd:
My Transformer Prime doesn't have any of the boot files but does have a init.goldfish.sh file in /system/etc. If i add /system/etc/init.d/* to that file, will I get init.d support? Thanks in advance.
[HTC One S] smokin1337:
Should work all init files get loaded at boot. Try it with a test file I can post one of you want
[HTC One S] Bastaerd:
I don't have any test files so please do :)
[HTC One S] smokin1337:
Attached to OP just flash it and look for /data/Test.log if its there init.d works.
[HTC One S] Bastaerd:
First of all, thanks for the script to check:)

Added the script to init.d folder, set the right permissions and rebooted. Unfortunately no Test.log in /data.

Adding post_boot.sh, with just the line for init.d in /system/etc also didn't do the trick.

Will look at it some more since having init.d support would be very nice. Now time to sleep ;)
[HTC One S] smokin1337:
Try making init.post_boot.sh with that line. Let me know if it works
[HTC One S] ahac85:
i have the galaxy s3 the test zip doesnt work for me either also adding the file you mentioned above doesnt work either
[HTC One S] Bastaerd:
Just tried it but it also doesn' t work.

Don' t have the time to do some research on the matter due to work =/
[HTC One S] Wetzel402:
Hi,

The zip fails to install on the Acer Iconia A200 with stock ICS. CWM is exiting with an error 0.

Any ideas?

Thanks!
[HTC One S] Big_Den:
Working perfectly on trickdroid v4.3 with mdj's kernel. Frequency's stick after reboot! Many thanks again.
[HTC One S] UtCollector@gmail.com:
I have no "post_boot.sh" ore anything like it. How do i get it created? I do have init.goldfish.sh like the other person. I have a Tom-Tec 7 excellent. Vendor is google. Stock android project build rom..
[HTC One S] smokin1337:
Did you try adding the line to init.goldfish ? Assuming init.goldfish is in /system/etc
[HTC One S] LikeaG2root:
I had this script all set up and allegedly working so I thought.

I had forced dual core and frequencies were showing on both cores for me to choose from. Set my Max frequencies, governors, sticky mode. All was fine.

Now checked it again and frequencies show in only one core and setting a frequency does not stick.

IDk what happened. Everything worked fine yesterday. I reflashed script and still can only see frequencies in one core. Also governor setting is available in one core.

Sent from my HTC One S using Xparent Cyan Tapatalk 2
[HTC One S] LikeaG2root:
I think I found out why. Previously I went to developer options and checked to show on screen CPU settings and then went to terminal and found the frequencies missing. After reflashing this script again and having it working I set the on screen CPU settings again and the same thing happened.

Sent from my HTC One S using Xparent Cyan Tapatalk 2
[HTC One S] remorema:
I'm also with the same exact issue in my ICS tablet.

no post_boot files, only that goldfish one.

adding the line to goldfish doesnt work.

creating post_boot file also doesnt work.

creating init.post_boot also doesnt work.

any other things we can try? would really like to add init.d support to my rom cause unfortunately there isnt a recovery available for my model and init.d will add the ability to preform some tricks and tweaks.

please post back if you find a solution
[HTC One S] Bastaerd:
We can always use scriptmanager to run stuff at boot but native via init.d would be better.

Will look at it some more tomorrow and keep you guys informed.
[HTC One S] smokin1337:
What files are in /system/etc in the way of scripts ? Mainly init files.
[HTC One S] remorema:
the only *.sh file is init.goldfish.sh
[HTC One S] osm0sis:
I'm using ICS Stock IMM76I, which I rooted and installed busybox on, and all /system/etc/ contains for .sh files are init.goldfish.sh and install-recovery.sh; neither seem to work. I'm running franco kernel 196 and I'd really like init.d support without changing from my stock rom. Any ideas?

Edit: Got Script Manager and that works obviously, but I was hoping for a more native solution still.
[HTC One S] garywojdan81:
Finally got fed up with trying to manually enable init.d & flashed your mod. IT WORKED PERFECTLY! Thanks for sharing your work.
[HTC One S] nabil2000:
cwm exit 0

cannot flash it on cwm, get E:Error in ... .zip (status 0) ,,,

Toshiba Thrive AT100-100 did not like this script (tried to re-sign it, same)

what can make the script abort?
[HTC One S] Orical:
Bad download will do that for sure, delete that one and redownload it again it should work.
[HTC One S] nabil2000:
nope

not working... the zip is fine... re-downloaded it just in case... the other test zip installs fine...

also tried to copy init.goldfish.sh to init.antares.sh and put the /system/etc/init.d at the end of both...

also added:

/system/xbin/busybox run-parts /system/etc/init.d

nothing...
[HTC One S] Orical:
The big guy will have too answer that one, I don't have your device.

Edit: Now that he bought the SGS3 I assume it might be a while before he gets back to this, he's working on something over there right now.
[HTC One S] paratox:
i try to get this working on a galaxy tab 7.7 with stock ics.

i also only have the init.goldfish.sh in /system/etc and test scripts did not work.

would be nice if anyone could give me a hint how to get it working.
[HTC One S] WCCobra:
Can you provide a listing of /system/etc?
[HTC One S] paratox:
http://pastebin.com/CpisvEMA
[HTC One S] WCCobra:
Do you have any .sh scripts in /system ? Have you tried putting the lines in /init.rc ?
[HTC One S] paratox:
no, this is the only one. if i edit init.rc all my entries are gone after a reboot.
[HTC One S] WCCobra:
Let me point out that this thread is for the HTC One S running ICS. There are no guarantee that this method will work for other devices or other versions of Android. I would recommend posting in the galaxy tab thread about this topic.

Looking in their section, there appears to be a few ROMs with init.d support. Selecting one of them, I found this:

/system/etc/install-recovery.sh

#!/system/bin/sh

# Task650: enabling init.d support
/system/bin/sysinit

/system/bin/sysinit

#!/system/bin/sh

export PATH=/sbin:/system/sbin:/system/bin:/system/xbin
/system/bin/logwrapper run-parts /system/etc/init.d

Not having the device, I can't tell if there is more to it than that. Seems pointless to split this into two files though...
[HTC One S] dagrim1:
Owning a TF201 myself and couldn't find the post_boot.sh file either... (nor install-recovery.sh).

What I did was add the following lines to the sysinit file in /system/bin

export PATH=/sbin:/system/sbin:/system/bin:/system/xbin

/system/bin/logwrapper run-parts /system/etc/init.d

Now init.d scripts get executed at boot :)
[HTC One S] -iNCEPTiON-:
I am trying to flash this on my stock (Galaxy Ace) and it says error , i have CMW recovery installed btw :( any suggestions?
[HTC One S] Orical:
He has stopped with this version, its going to be rereleased with the correct modifications. Much better now and sticks after reboot due to new method of install.

He will be posting the new one soon.
[HTC One S] Tikki Pon:
Thank you man,i have a "init.d" but not work properly,and now with this,my init.d tweaks are workin!

Btw, the zip of init.d test, it say that test.log will be in /data,but i find the log,in system/etc/init.d

With the name of "00test" ,i open and it say that init.d its working

Big thanks!
[HTC One S] Wetzel402:
The reason the modifications don't stick is that ICS rewrites the files each boot. The only way to get it to stick is to modify the boot.img ramdisk.
[HTC One S] skorzo:
Hi there...

I have a Galaxy Ace. Stock Rom (KTM), Stock Recovery and Rooted.

I have manually edited my /system/etc/init.qcom.post_boot.sh and after the word esac I added:

/system/etc/init.d/*

I make the /system/etc/init.d folder, then I put the 00test script inside.

Now I reboot.

After boot, the log is not on /data so ... I think that this modification is not working for me :(

Furthermore... I have noticed other init.qcom.post_boot.sh on / (just /init.qcom.post_boot.sh)

Why do I have 2 init.qcom.post_boot.sh ?? One in / and other (now modified) on /system/etc

Should I modify both of them?

Thanks!!!
[HTC One S] abitzsong:
The link is dead. How could I get a copy of it?

Anybody has a mirror?
[HTC One S] WCCobra:
You really don't need a mirror... just add the one line to the file mentioned in the OP. Also, the OP link still works for me.
[HTC One S] arunsai123:
the link is dead now.

in my rom I cannot find post_boot.sh in system/etc/ folder.

it contains init.post_boot.sh.

I use links2sd.

so,link2sd script changed it?

what to do?

(using sense 3.5 rom.)
[HTC One S] lennis:
+1

Enviado desde mi HTC One S Kingdroid_V1.0
[HTC One S] G3CUA19:
Cant download the link is dead some one post a new link please

Sent from my HTC One S
[HTC One S] interaser:
here you go
[HTC One S] lennis:
Thanks

Enviado desde mi HTC One S Kingdroid_V1.0
[HTC One S] jamesst20:
Thanks man
[HTC One S] Klyentel:
didn't work

I flashed the Easy Init.d zip and everything seemed fine. I rebooted and flashed the test zip, but did not have a test.log file in /data :(

So I attached my post_boot.sh file

Edit: Nevermind, opened the /system/etc/init.d folder, and found the 00test file, opened it and it read that everything is working fine, Thanks! This MOD rocks.
[HTC One S] tsunamixtreme:
update the links plz
[HTC One S] thebrainkafka:
IS this working on Xperia U?

I cannot find a file named post_boot.sh in system/etc ??

Thx
[HTC One S] bigknowz:
FIle not found

Is there another link for ezinitd.zip?
[HTC One S] Orical:
Someone posted a link a few pages back.
[HTC One S] carl1961:
Easy_InitD_1.1

Easy_InitD_1.1.zip
[HTC One S] dharvey4651:
Goo link in op is down. Anyone have this zip?

EDIT:: Me=stupid. Posted before reading last post.
[HTC One S] faria:
The file that needs to be edited in the Samsung galaxy s 3 mini is : init.goldfish.sh

I don't know whats names samsung uses in the other models, but it easy to find out, in most Samsung there is 2 .sh files in the ETC folder ,one of them is XXX_modem.sh ,so yours must be the other.

ps;

you may find the install-recovery.sh file in there too,ignore it.

Thanks for the mod!
[HTC One S] KronicSkillz:
can anyone verify if this mod works in cyanogenmod 10.. /system/etc folder contains these SH files

init.goldfish.sh

init.qcom.mdm_links.sh

init.qcom.modem_links.sh

init.qcom.post_boot.sh

i would imaging the last of the 4th files is the post_boot.sh as its in the name but i would love it if someone could verify 2 things

will this work on cm10: y/n

if unsure, is it safe to just try, or can this cause potential damage if the filenames are wrong or incomp.