If you're considering the X2, this is a must read!!!!

[zeppelinrox]

Yes.

Worth also noting that sysctl isn't anywhere on my system

Running ls -R */sysctl from / as su returns nothing.

Me too...
But..
ls -R /system/*/sysctl
...does


Sent from my Milestone using Tapatalk

 

[vvildcard]

So there is no hack to enable boot scripts?

I could run the script at boot with Script Manager... but wouldn't that be too late in the boot process? I'm actually not sure when/how Script Manager implements that.

I know we don't have /etc/init.d, but there must be some other place where boot scripts are loaded.

 

[vvildcard]

#ls -R /system/*/sysctl
/system/*/sysctl: No such file or directory

 

[zeppelinrox]

Damn... so you did try navigating to /system/xbin to confirm it I guess... ?

Its fine for SM to load the script on boot as the settings can be changed on the fly...
Btw SM loads scripts after you see the desktop

Sent from my Milestone using Tapatalk

 

[vvildcard]

Yeah, I confirmed by navigating first... the ls -R stuff was just to be sure it wasn't hiding somewhere else.

Would it work if I just copied it to /system/xbin and referenced it directly in the script?


sysctl is listed as one of the options in BusyBox... could we just use that?

 

[zeppelinrox]

A workaround would be to manually echo what sysctl would do.
Do you have these folders...
/proc/sys/vm
/proc/sys/kernel
/proc/sys/net

Sent from my Milestone using Tapatalk

 

[vvildcard]

Yes, yes and yes. I'm going to work on it tonight and see if I can't get it to run with BusyBox... it looks like it will work without much trouble, as the following worked when I ran it in terminal emulator:

busybox sysctl -w kernel.panic=0

 

[zeppelinrox]

I just realized that sysctl is part of busybox... what version are you using?
I think 1.16.* ensures compatiblilty

 

[vvildcard]

I have 1.14.3, which I believe came with my version of Titanium Backup.

So far, everything appears to be working with a simple addition of busybox before each sysctl call.

I'm working on the script portions now and will have some questions about it soon, I'm sure.

 

[zeppelinrox]

Oh ok so I can just add busybox to the beginning of each sysctl command...
Thank god it's an easy fix on that one...

But the noop scheduler not taking effect could be a hassle

Try busybox 1.16.2.. it may at least get rid of the "cut" error near the end...

 

[vvildcard]

Actually, it looks like the noop part is taking hold... I just ran the script again and now it's showing [noop] for all scheduler files that had noop as an option (the others show 'none').

I will do some benchmarking later to see if there's any kind of noticeable difference.

So the only thing I think I'm having trouble with is this:

for i in $(ls -d /sys/block/*);
do	
	echo "0" > $i/queue/rotational;
	echo "1" > $i/queue/iosched/low_latency;
	echo "1" > $i/queue/iosched/back_seek_penalty;
	echo "1000000000" > $i/queue/iosched/back_seek_max;
	echo "0" > $i/queue/iosched/slice_idle;
	echo "512" > $i/queue/nr_requests;
	echo "1" > $i/queue/iosched/fifo_batch;
	echo "16" > $i/queue/iosched/quantum;
done;

For whatever reason, we don't have some of files you're changing.

 cannot create /sys/block/dm-X/queue/iosched/fifo_batch: directory nonexistent
 cannot create /sys/block/loopX/queue/iosched/low_latency: directory nonexistent
 cannot create /sys/block/loopX/queue/iosched/back_seek_penalty: directory nonexistent
 cannot create /sys/block/loopX/queue/iosched/back_seek_max: directory nonexistent
 cannot create /sys/block/loopX/queue/iosched/slice_idle: directory nonexistent
 cannot create /sys/block/loopX/queue/iosched/fifo_batch: directory nonexistent
 cannot create /sys/block/loopX/queue/iosched/quantum: directory nonexistent
 cannot create /sys/block/mmcblkX/queue/iosched/fifo_batch: directory nonexistent

(There are 7 of each dm-X and loopX directories and two for mmcblkX)

 

[zeppelinrox]

How did you get noop to work?
Did you change anything apart from adding busybox to the sysctl commands?

Those errors are ok.
The main thing is that it gets applied to mtdblock*

Edit: oh it should apply to mmc...
Did you run the entire script or just that section?

That's why I have cfq first - to create all possible files to ensure noop can be applied later to as many items as possible

Sent from my Milestone using Tapatalk

 

[vvildcard]

I honestly don't know for sure... I think the first time was a fluke because I don't remember doing anything different.

I've been running benchmarks all night with different combinations of scripts and overall, haven't seen a big difference in them. Oddly enough, even when the scripts are completely disabled, the benchmarks are slightly better, on average. Of course, that doesn't speak to the dramatic increase in stabily introduced by the scripts.

Sent from my DROID X2 using DroidForums

 

[zeppelinrox]

Which benchmarks did you try?

I searched market last night and a few test sd access and io stuff but haven't tried any yet.
Passmark is one that I remember being pretty good on PCs and was surprised to see an android version

Sent from my Milestone using Tapatalk

 

[zeppelinrox]

I forgot to ask, does it fix the audio popping problem?

Sent from my Milestone using Tapatalk