[Samsung Epic 4G Touch] guirae:
To run the init.d script, there're several things that you need to know. That's why I spent lots of time to explain every thing. If you don't understand what you need and how it works, then you need some more time until you understand what you're doing and what is required to do so. I'm sorry to say that but please research before you ask something.

I really want to help you and I'm really willing to. But there's some portion that you have to finish your homework at first.

Let me give you a homework (I'm not trying to offensive but trying to help you in here. I was just like you in 5 months ago).

1. what's the init.d script and how it works?

2. If you are using Script Manger, you need to understand how it works, and how this app make it possible to run the init.d script during the boot. Do you think, you can figure it out? What's the difference running the scripts during the boot or running the app after the boot?[/QUOTE]

I totally understand and I am asking these questions in the midst of my studying(your 2 threads and other miscellaneous threads) and understanding kernels/system settings/ etc. I see XDA as a wonderful community that allows people to dip their feet in the development world. I think relatively tougher Tweaks (i.e. this one) are a great opportunity to extend a hand to those with limited understanding of CS in hopes to broaden the community. If this is strictly meant for advanced developers, I totally understand. But I've read your posts, sensed that your tone and attitude was to some what achieve this sense of community, and started asking questions. (I greatly appreciate your time)

Again, if all of my questioning does not belong in this thread due to my lack of experience and seemingly "laziness" due to the lack of study, I have no problem taking the criticism and not posting in this thread anymore. My main motive [aside from having this awesome tweak on my phone :)] is that my questioning and explaining can assist those who may have a harder time deciphering the CS jargon at hand(aka explain in layman's terms) in hopes that they can experience the hard work you wonderful devs have put in.

I was just wondering if you could clear up the jargon/ideas because it was a bit confusing for me. Please correct me if I am wrong:

0.5. I am running sfhubs Stock FD26 ROM. I have ReActiveDisorder's kernel flashed, therefore having init.d support.

1. init.d. script is what allows certain scripts or commands to occur when a device boots up. Within this context and file, there exists 4 different scripts/commands that tell the phone to(on boot): adjust the CPU speed; change the governor value (conservative, ondeman, lazy, awake, sleep modes, etc.); improve network speed, sdcard, etc.; and a build.prop tweak which, "defines lots of system values related to phone settings". This is the crux of the tweak.

2.Script Manager is the tool/app that executes these scripts. After playing around with it, I've realized that I can navigate to these scripts and give them superuser access, and have them run when the phone boots, hence having the tweak work. So with all of that in mind, I guess that was my question in the previous thread: I was wondering about the "How to test" part. I got lost when you wrote "Running the init.d script from init.rc is,"...Then you have some commands (?).

I understand why 0test needs to be made because /system/etc/init.d scripts do not run automatically during boot.

But after you wrote "Example) Create a file 0test into /system/etc/init.d"

,you have another set of commands(?) that i don't understand how to decipher or execute :

#!/system/bin/sh

touch /data/local/tmp/initd_test.txt

echo "Hello Android" > /data/local/tmp/initd_test.txt

(how do i execute these commands or write these commands on 0test?)

Once i get the 0test file executed via SManager, and the results you have listed come out, then i know that init.d will be executed on boot.