
Originally Posted by
slider112

Originally Posted by
metalspring
well, i got everything worked out (i hope) so im gonna post my build.prop and sysctl file up if anyone wants to help test them out...but just to be safe BACK UP YOUR ROM
*note* unless you are on simply stunning rom 5.4 please modify the build.prop to match up with your rom
**note 2** just delete the .txt extension on all these files before use
***note 3*** the build.prop contains an lcd density mod, just either download/use spare parts and uncheck run in compatibility mode OR change the lcd density value to the stock 240
****note 4**** enjoy

Just so I’m sure I have this right:
build.prop
To apply the build.prop edits I simply add the new lines into my build prop in the correct location within my file, keeping everything else the same? Reboot and done? I’ve essentially opened up my build prop and your edited build prop with the extra lines of code next to each other and was just going to do a copy/paste?
sysctl
I just need to rename the 01sysctl.txt file to 01sysctl (no .txt extension) and copy this into the /etc/init.d folder, then change permissions to rwxr-x--- , then reboot and good to go? What exactly does this file do?
For what it’s worth I’m on a D1, Froyo 2.2 through and older Sapphire build. I’ve already Supercharged and added the 3G hack… and am flying... just looking for any other little speed boosts where I can get em
Thanks in advance!
Yeah, use the 01sysctl file (minus the. Txt extension) into etc/init.d -you might need to change the number on it so it doesn't clash with anything else in there, the number basically refers to what order everything is loaded but just having any number 01-98 in front will still load it during boot....and what does it do? It optimizes the way the kernel manages memory allowing for more efficiency (better speed, stability and battery life)
For instance one part Zeppelin had I used oom allocating task I think, it's default is a 1 which means whenever you're running short of memory it will kill the app/process that pushed it over the edge, however changing to 0 makes the kernel kill the biggest memory hog instead
Say game is running in the background just eating up tons of memory and you open browser and then run low on memory a setting of 1 would kill the browser process (even if it isn't really taking up lots of memory itself) but a value of 0 will make the kernel realize that its actually the game that's hogging memory and it will kill the game instead...which of course makes more sense lol...
Sent from my Droid using DroidForums
Edit - btw I was tired when posting the files and accidentally put the systcl.config file in my first post use the 01sysctl from the second post...its more detailed and effective