Enabling sysctl.conf/init.d in Stock rom?

le0p · May 3rd, 2012, 01:22 PM

Hi,

I've got a rooted Commando and removing the bloatware and moving stuff around has definitely improved the performance but I'd really like to tweak it a bit further.

I've got Jrummy16's ROM toolbox and I was trying to play around with the sysctl settings when I noticed that nothing took. I then looked into it a bit and realized it might not work with the stock rom. I then started to look into how to enable these features by manually adding files/scripts/tasks, but there hasn't been any commando specific stuff, so I have been hesitant to try it.

Has anyone done this? If you can point me to a guide I can figure it out, I used to a be a 100% linux user until the corporate world got hold of me.. I'm pretty confident in working with the system, I just don't know the ins and outs of working on phones and how the os works in comparison to a standard install.

And I really don't have money to replace a bricked phone..

Thanks!
Leo

paxchristos · May 3rd, 2012, 01:27 PM

Quote:

Originally Posted by le0p

Hi,

I've got a rooted Commando and removing the bloatware and moving stuff around has definitely improved the performance but I'd really like to tweak it a bit further.

I've got Jrummy16's ROM toolbox and I was trying to play around with the sysctl settings when I noticed that nothing took. I then looked into it a bit and realized it might not work with the stock rom. I then started to look into how to enable these features by manually adding files/scripts/tasks, but there hasn't been any commando specific stuff, so I have been hesitant to try it.

Has anyone done this? If you can point me to a guide I can figure it out, I used to a be a 100% linux user until the corporate world got hold of me.. I'm pretty confident in working with the system, I just don't know the ins and outs of working on phones and how the os works in comparison to a standard install.

And I really don't have money to replace a bricked phone..

Thanks!
Leo

init.d & sysctl.conf require a custom kernel. Nobody has gotten one working yet.

le0p · May 3rd, 2012, 01:57 PM

Thanks! I won't bother messing with it then..

By the way, I've read some of your posts about working on a Commando rom, I wish you all the luck. I haven't done any linux development in a long time but if I can be of any help (i.e. testing or whatever), let me know!

paxchristos · May 3rd, 2012, 04:37 PM

Quote:

Originally Posted by le0p

Thanks! I won't bother messing with it then..

By the way, I've read some of your posts about working on a Commando rom, I wish you all the luck. I haven't done any linux development in a long time but if I can be of any help (i.e. testing or whatever), let me know!

The problem is that I haven't gotten around to building a second stage bootloader for the kernel (and I've been busy in xda :P ) I might get back to it after i'm done with this semester.

bigdanmeys13 · May 4th, 2012, 04:22 AM

Look at the V6 Supercharger thread over on XDA. It'll walk you through downloading an app called "Gscripts lite" and a script called "autostarts: enable init.d on stock ROMs". That may help.

paxchristos · May 4th, 2012, 09:01 AM

Quote:

Originally Posted by bigdanmeys13

Look at the V6 Supercharger thread over on XDA. It'll walk you through downloading an app called "Gscripts lite" and a script called "autostarts: enable init.d on stock ROMs". That may help.

Forgot about that one, it's not true init.d, but it functions similar to an init.d script.

le0p · May 4th, 2012, 06:34 PM

Thanks for the v6 supercharger link! I implemented it today and I can see a noticeable difference.