I don't understand what makes it so special.. i mean yeah, its awesome, but what makes it any different from any other folder.. why cant you just manually add a folder to the etc section and name it init.d with the same owner and permissions on a stock kernel?
To use it properly, you have to have a kernel that supports it. You can create it on an unsupported kernel, but nothing will happen. Even if you use Script Manager to run scripts from it, it still won't be like a true init.d, because init.d supports run ordering, and Script Manger doesn't.
The kernel has to know it needs to look for it during the boot process.
ahhh I see.. that makes sense. thanks
I am currently working on a custom rom but I can't get the init.d start up scripts to rewrite the values of certain files and do the thing I want them to do. Anyone have any ideas why?
Sent from my SGH-T839 using XDA Premium App
Busybox? Ask dev.
Depending on which files you are trying to overwrite, it may be writing them before the system sets their values.
if this is the problem any ideas on how i can overwrite the system values AFTER the system sets the values?
i'm currently using the 01insert_file_name_here - 98insert_file_name_here
method and i have it set to 98 so that means that the system should be writing those values last which should mean the values would be overwritten like i wanted but yet NONE of the init.d scripts are running.
hmmm.....
Which kernel are you using?
your kernel from glorious overdose that you said i could use haha
i even also tried switching to a kg2 stock deodex base and doing the same mods and the same result happened.....
i thought that the #filename method in the system/etc/init.d folder was the method used for running startup scripts.....i also gave the ect/init.d folder rwx-rwx-rwx permissions (0777) in the updater-script yet nothing.....
it should be etc/init.d, not sure if you had a typo in your post, or if you're using the wrong folder? I know that init.d scripts work on the KJ2 kernel I made.
sduvick said:
it should be etc/init.d, not sure if you had a typo in your post, or if you're using the wrong folder? I know that init.d scripts work on the KJ2 kernel I made.
Click to expand...
Click to collapse
yeah its the right folder
but does the script have to be named:
98test
or
S98test ?
b/c i noticed in glorious overdoes you put a capital s infront of the script's number and name.....in some other roms though they just use the # then name without the s
-x]Trunks[x- said:
yeah its the right folder
but does the script have to be named:
98test
or
S98test ?
b/c i noticed in glorious overdoes you put a capital s infront of the script's number and name.....in some other roms though they just use the # then name without the s
Click to expand...
Click to collapse
it seems galaxy s phones need the script to start with "S" followed by a number between 01-98 then a file name.....so the 2nd option I posted is correct.
but yet even with using your kernel i can't get the script to set the values i'd like it to for the rom i'm working on.....here's the script i have made (don't worry those who have work that is contributed to that file will be credited when i post the rom w/ this working script)
i've been trying for almost a week with different people's "solutions" yet none work
rom base: kj2 deodex w/ root
modem: kj2
kernel: glorious overdose 2 kernel
hopefully you can figure out the problem
I have been reading up on zipalign and am wondering how to do this myself. I am running stock deodexed so i know I'm not zipaligned. Although i am quite experienced in programming and i could learn how to use Android SDK, i do not have the time to do do. Is there a tool i can use to easily zipalign my apks ok my phone?
Sent from my Nexus S using XDA App
You would need an arm compiled version of zipalign. From there, it's fairly simple to do, as you could look at some of the init.d scripts I've seen for zip aligning dirs for the command needed to do what you want. A basic overview of commands used is:
Code:
zipalign 4 input.apk input-aligned.apk
mv input-aligned.apk input.apk
You can't directly zip align to the same apk name.
imnuts said:
You would need an arm compiled version of zipalign. From there, it's fairly simple to do, as you could look at some of the init.d scripts I've seen for zip aligning dirs for the command needed to do what you want. A basic overview of commands used is:
Code:
zipalign 4 input.apk input-aligned.apk
mv input-aligned.apk input.apk
You can't directly zip align to the same apk name.
Click to expand...
Click to collapse
Sorry that went way over my head i think I'll just stay where i am.
Sent from my Nexus S using XDA App
You really aren't missing much. Zip aligning is one of those things to help with performance that does so little, that you probably aren't going to notice it if it hasn't been done. Does it help? Probably. Will you notice a difference between a zip-aligned and non-aligned ROM? Probably not.
Does the dsixda android kitchen work for making ICS roms, or is it too different from GB to use it?
Sent from my SAMSUNG-SGH-I727 using xda premium
Depends on what you want to do with it. For deodexing, do it by hand or you will be in for a world of hurt. Regarding the kernel, it would behoove you to just use romracer's kernel (or another init.d kernel) and overwrite boot.img in your kitchen folder. Lastly, you should really do the Edify by hand and make sure everything is as you would like it.
I basically only use the kitchen for zipalign and signing because I am lazy. Once you have played with the kitchen enough (and are comfortable with looking through the .sh scripts and Edify scripting) you will know how to do everything by hand (such as adding busybox, bash, etc.).
My 2 cents.
promiseofcake said:
Depends on what you want to do with it. For deodexing, do it by hand or you will be in for a world of hurt. Regarding the kernel, it would behoove you to just use romracer's kernel (or another init.d kernel) and overwrite boot.img in your kitchen folder. Lastly, you should really do the Edify by hand and make sure everything is as you would like it.
I basically only use the kitchen for zipalign and signing because I am lazy. Once you have played with the kitchen enough (and are comfortable with looking through the .sh scripts and Edify scripting) you will know how to do everything by hand (such as adding busybox, bash, etc.).
My 2 cents.
Click to expand...
Click to collapse
Ok that clears things up for me.
that comprehensive overclock guide says : http://forum.xda-developers.com/showthread.php?t=1754114
without init.d support(stock rom).......
with init.d support (custom rom)......
the instruction under "with init.d support" says :
under /system/etc/init.d
but mine is /etc/init.d (but no 00pptimize file)
should I just create 00pptimize file in /etc/init.d instead?
thank you for any helpful replies!
unreallove said:
that comprehensive overclock guide says : http://forum.xda-developers.com/showthread.php?t=1754114
without init.d support(stock rom).......
with init.d support (custom rom)......
the instruction under "with init.d support" says :
under /system/etc/init.d
but mine is /etc/init.d (but no 00pptimize file)
should I just create 00pptimize file in /etc/init.d instead?
thank you for any helpful replies!
Click to expand...
Click to collapse
I would recommend using a pre made ROM with this feature integrated already. Much easier.
Sent from my locked MB865 on Ice Cream Sandwich.
What ROM are you running, let's start there. Some ROMs use different init.d files, but for each they all have the ability to be edited properly. Would have been nice for you to post in the OC thread you listed, rather than creating a new one. Rules o' the Forum, they're good for everyone...
http://forum.xda-developers.com/showthread.php?t=1857631
[GUIDE] How To Be A New Member, Not A NØØB
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
unreallove said:
that comprehensive overclock guide says : http://forum.xda-developers.com/showthread.php?t=1754114
without init.d support(stock rom).......
with init.d support (custom rom)......
the instruction under "with init.d support" says :
under /system/etc/init.d
but mine is /etc/init.d (but no 00pptimize file)
should I just create 00pptimize file in /etc/init.d instead?
thank you for any helpful replies!
Click to expand...
Click to collapse
Those two locations are the same. Don't sweat it. Create a file in one location, the cd to the other and you will see the file you created.
DemosZevasa said:
I would recommend using a pre made ROM with this feature integrated already. Much easier.
Sent from my locked MB865 on Ice Cream Sandwich.
Click to expand...
Click to collapse
I missed to mention it
my rom is stock one
hong kong 2.3.6 stock one
thx!
Apex_Strider said:
What ROM are you running, let's start there. Some ROMs use different init.d files, but for each they all have the ability to be edited properly. Would have been nice for you to post in the OC thread you listed, rather than creating a new one. Rules o' the Forum, they're good for everyone...
http://forum.xda-developers.com/showthread.php?t=1857631
[GUIDE] How To Be A New Member, Not A NØØB
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
Click to expand...
Click to collapse
what's in my mind is.......
where in that thread it says "without init.d(stock rom)"
but I am using stock rom and sees there is a init.d there
just it is located in different location, not in /system folder
so I need to ask for help
thx
and I do think, if I don't ask
then after I cannot succeed, then go into this forum ask for help
it will be troublesome to do so, as it may even become more complicated to solve after I do something wrong
I just wanted to say...
I have searched before ask
I searched google, but don't seem a result answering
and also none
then I ask here
All you have to do is follow the instructions I gave. You'll need to DL the new init.d file and flash in CWM- this will overwrite any existing init.d folders you have. From there, you can choose your OC method (either using Terminal Emulator or Root Explorer file manager) to edit the frequency scaling of the echo table values...
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
new thread?
by seeing your no. of post ..... u r a noob like me
u shud've asked Apex_strider directly in his thread (instead creatin new, but hey ! u r noob so forget it :silly: )
he is strong enough to take ur fone to ur desired frequency
but as far as overclockin is concerned ...... it will SUCK ur battery more !!
u can surely try overclockin n see result urself. All the best :good:
n one thing ..... post some detail abt ur firmware, hardware in next thread so that it will be easy to understand to devs
shardul.phatak said:
by seeing your no. of post ..... u r a noob like me
[snip]
n one thing ..... post some detail abt ur firmware, hardware in next thread so that it will be easy to understand to devs
Click to expand...
Click to collapse
And one more thing, next time please don't use text-messaging speak but instead use complete sentences so that is easy for the devs (and the rest of us) to understand.
troycarpenter said:
And one more thing, next time please don't use text-messaging speak but instead use complete sentences so that is easy for the devs (and the rest of us) to understand.
Click to expand...
Click to collapse
I had no troubles understanding this. Let's not get into worrying over completely innocuous verbiage such as this. It might get have been different had it been an absolutely broken and butchered usage of the English language, so as for is to have to piece that "puzzle" together, but it really wasn't.
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
Apex_Strider said:
All you have to do is follow the instructions I gave. You'll need to DL the new init.d file and flash in CWM- this will overwrite any existing init.d folders you have. From there, you can choose your OC method (either using Terminal Emulator or Root Explorer file manager) to edit the frequency scaling of the echo table values...
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
Click to expand...
Click to collapse
ok, your answer will now make up another 2 questions....... :
1. it seems usually editing init.d may mean changing the kernel....
stock kernel cannot overclock?
2. are there really no shortcuts if I only want to try to overclock?
unreallove said:
ok, your answer will now make up another 2 questions....... :
1. it seems usually editing init.d may mean changing the kernel....
stock kernel cannot overclock?
2. are there really no shortcuts if I only want to try to overclock?
Click to expand...
Click to collapse
ok, your answer will now make up another 2 questions....... :
1. it seems usually editing init.d may mean changing the kernel....
stock kernel cannot overclock?
A) Even with a custom ROM that has 'built-in' over clicked init.d files, it's still using the stock kernel. Because of the locked bootloader on the Atrix 2, we do not have the ability to flash custom kernels. That being so, you have to flash the init.d file through CWM to gain init.d support to overclock.
2. are there really no shortcuts if I only want to try to overclock?
A) I'm not sure what you mean by "shortcut". The methods I outline are fairly easy and have noted success both with the stock Motorola ROM and with custom ones as well.
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
I don't know....
I am new to all this thing
I just don't wanna get too deep into the "bootloader" stuff
but then, I'll have to ask again....
now, actually I have a init.d folder, just in different directory
will your "without init.d support" method create another WHOLE init.d in /system ?
or it just only rewrite everything in my existing /etc/init.d
I'll have to ask is because, there's plenty files there
I am quite afraid if that method rewrite too many files(and even some is lost)
I don't know what will be the consequences
unreallove said:
I don't know....
I am new to all this thing
I just don't wanna get too deep into the "bootloader" stuff
but then, I'll have to ask again....
now, actually I have a init.d folder, just in different directory
will your "without init.d support" method create another WHOLE init.d in /system ?
or it just only rewrite everything in my existing /etc/init.d
I'll have to ask is because, there's plenty files there
I am quite afraid if that method rewrite too many files(and even some is lost)
I don't know what will be the consequences
Click to expand...
Click to collapse
Don't worry yourself about the bootloader, there's nothing you nor myself nor anyone else can do with it/to it. It's locked, and that's that.
When you DL the file in the "prerequisites" section, and flash it, it will overwrite your existing init.d files. It's all spelled out for you there, not sure why this isn't connecting with you.
Make sure you backup via CWM prior to doing anything, just in case. If you can attach a screenshot of what your init.d folder includes, it might be more helpful.
Everything you'll need is in the guide thread I posted, files, instructions for adding the init.d support, and two ways of Overclocking the CPU. I wrote it to be "n00b friendly"... :thumbup:
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
forgive me....
I am so curious that why there is already init.d folder
and still, we still need to see it as "no init.d support"
this is my concern
unreallove said:
forgive me....
I am so curious that why there is already init.d folder
and still, we still need to see it as "no init.d support"
this is my concern
Click to expand...
Click to collapse
You are looking in the wrong place, since you are on 2.3.6 you are looking in /etc which is webtop, not your ROM.
You will need to install a GB ROM with init.d support, if you start trying to do this yourself with not much knowledge of linux or android, it is easy to mess something up. If you install a ROM with init.d support, you can take a look at the rom and see what it is doing.
/etc and /system/etc are two completely different operating systems, so be very carefull, if you decide to try and get init.d working on your own!
unreallove said:
forgive me....
I am so curious that why there is already init.d folder
and still, we still need to see it as "no init.d support"
this is my concern
Click to expand...
Click to collapse
The /etc/init.d is a directory containing initialization and termination scripts for changing init states. These scripts are linked when appropriate to files in the rc?.d directories, where "?" is a single character corresponding to the init state. Every ROM including the stock Moto ROM has an init folder.
The init.d linked in the guide provides and 00pptimze foder, which allows for the editing of the echo table values to modify CPU frequency scaling. This is necessary for overclocking your CPU.
Apex_Strider said:
The /etc/init.d is a directory containing initialization and termination scripts for changing init states. These scripts are linked when appropriate to files in the rc?.d directories, where "?" is a single character corresponding to the init state. Every ROM including the stock Moto ROM has an init folder.
The init.d linked in the guide provides and 00pptimze foder, which allows for the editing of the echo table values to modify CPU frequency scaling. This is necessary for overclocking your CPU.
Click to expand...
Click to collapse
No that is webtop...
/system/etc is the rom.... please be careful... 2.3.6 is not the same as ICS.
jimbridgman said:
No that is webtop...
/system/etc is the rom.... please be careful... 2.3.6 is not the same as ICS.
Click to expand...
Click to collapse
Oops.
Left out the "system/"... My apologies.
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile