Jump to content

speed boost and battery boost as well


Guest fards

Recommended Posts

Read the first post, follow the instructions, change the values to the ones I suggested.

If it works for you then put sysctl -p in /system/bin/run_autorun_test.sh (if it exists)

fwiw :

I wonder if sysctl -p doesn't appear permanent as the ns values are set to default in init.rc on each boot...

I haven't tried commenting then out or changing them yet, but wonder if we could just add the extra lines to init.rc

I'm with fards on the first point, I think people should read the whole thread so they get an understanding of what's going on, maybe it should be summarised when we really are a little clearer on the best settings and general setup.

Regarding init.rc didn't notice ns vals are set in there but don't think commenting them out or modding them will work - pretty sure the file gets restored to initial values on boot as I tried modding it a while back (assuming the bootloader does this). Think they are 'permanent' if set in the autorun test file though as sysctl -a after reboot returns the new values - suggests it is run after init.rc which makes sense.

Link to comment
Share on other sites

Im' using root explorer, there are two files in /system/etc/ called sysctl.conf both with the same text in them:

kernel.shed_features = 24188

kernel.shed_tatency_ns = 6000000

kernel.shed_min_granularity_ns = 2000000

kernel.shed_child_runs_first=1

One size 138 the other 408??

I don't understand how this could be possible bar some sort of file system corruption - are both files identical in name ncluding lower case for all chars in the name? I'd be inclined to delete both and create a new one.

Link to comment
Share on other sites

I don't understand how this could be possible bar some sort of file system corruption - are both files identical in name ncluding lower case for all chars in the name? I'd be inclined to delete both and create a new one.

They must have different names, two files can't exist with the same name in the same folder

Spence you sure one isn't a .bak file?

Link to comment
Share on other sites

Guest spences10
They must have different names, two files can't exist with the same name in the same folder

Spence you sure one isn't a .bak file?

Check it out:

You're right this cant be - but look 0_o

IMG_20100911_094150.jpg

I think i have tried deleting both files - will do it again just to make sure

EDIT:

Jsut did a list of the file system, not seen it displayed like this before - it is showing the two files tho.

G:\AndroidSDK\tools>adb shell

$ su

su

# ls /system/etc

ls /system/etc

←[0;0m01_qcomm_omx.cfg←[0m	←[0;0mgps.conf←[0m			←[1;34msecurity←[0m

←[0;0mDualMicControl.txt←[0m  ←[0;0mhosts←[0m			   ←[1;32msysctl.conf←[

0m

←[0m0mNOTICE.html.gz←[0m	  ←[1;34minit.d←[0m			  ←[0;0msysctl.conf

←[0;0mQisdaAudioBTID.csv←[0m  ←[1;32minit.goldfish.sh←[0m	←[0;0msysctl.conf.b

ak←[0m

←[0;0mapns-conf.xml←[0m	   ←[0;0minit.qcom.bt.sh←[0m	 ←[1;34mterminfo←[0m

←[1;34mbluez←[0m			   ←[0;0minit.qcom.coex.sh←[0m   ←[0;0mvoicemail-con

f.xml←[0m

←[0;0mbookmarks.xml←[0m	   ←[0;0minit.qcom.fm.sh←[0m	 ←[0;0mvold.conf←[0m

←[1;34mbt←[0m				  ←[0;0minit.qcom.sdio.sh←[0m   ←[1;34mwifi←[0m

←[0;0mdbus.conf←[0m		   ←[0;0mloc_parameter.ini←[0m   ←[0;0mwiperconfig.xm

l←[0m

←[1;34mdhcpcd←[0m			  ←[1;34mpermissions←[0m		 ←[1;34mwlan←[0m

←[0;0mevent-log-tags←[0m	  ←[1;34mppp←[0m

←[1;34mfirmware←[0m			←[0;0mpvplayer.cfg←[0m

# ls /system/etc

Edited by spences10
Link to comment
Share on other sites

Guest spences10

Ok, have just deleted both files and done the whole opperation via terminal emulator.

Take a look at the screen print.

How is this possible? am i being really nooby about this?

CAP201009111140.jpg

Link to comment
Share on other sites

Guest mrmrmrmr

interesting; I am using original 1.6 firmware Dell Streak

when I copy the sysctl.conf file with the values proposed here, and give the "sysctl -p" command ,I get folowing error for all 4 keys:

"sysctl: error: 'kernel....' is an unknown key"

why ?

Link to comment
Share on other sites

Guest spences10
interesting; I am using original 1.6 firmware Dell Streak

when I copy the sysctl.conf file with the values proposed here, and give the "sysctl -p" command ,I get folowing error for all 4 keys:

"sysctl: error: 'kernel....' is an unknown key"

why ?

I think you need to read the whole thread chap, you need busybox installed

Link to comment
Share on other sites

Guest mrmrmrmr
I think you need to read the whole thread chap, you need busybox installed

well, actually I had the busybox installed but I didn't run busybox prior to these commands.

anyway now it's working.

but I have another question:

I prepared 2 sh scripts:

changeperm.sh:

#!/system/bin/sh

su

mount -o remount,rw /dev/block/mtdblock6 /system

echo 'kernel.sched_latency_ns=600000' >> /etc/sysctl.conf

echo 'kernel.sched_min_granularity_ns=400000' >> /etc/sysctl.conf

echo 'kernel.sched_features=24188' >> /etc/sysctl.conf

echo 'kernel.sched_child_runs_first=1' >> /etc/sysctl.conf

mount -o remount,ro /dev/block/mtdblock6 /system

sysctl -p


changeback.sh:

#!/system/bin/sh

su

mount -o remount,rw /system

rm /etc/sysctl.conf

mount -o remount,ro /system

sysctl -p

exit

but they don't work.

first mount command says : mount: file not found.

why ?

Link to comment
Share on other sites

Guest spences10
well, actually I had the busybox installed but I didn't run busybox prior to these commands.

anyway now it's working.

but I have another question:

I prepared 2 sh scripts:

changeperm.sh:

#!/system/bin/sh

su

mount -o remount,rw /dev/block/mtdblock6 /system

echo 'kernel.sched_latency_ns=600000' >> /etc/sysctl.conf

echo 'kernel.sched_min_granularity_ns=400000' >> /etc/sysctl.conf

echo 'kernel.sched_features=24188' >> /etc/sysctl.conf

echo 'kernel.sched_child_runs_first=1' >> /etc/sysctl.conf

mount -o remount,ro /dev/block/mtdblock6 /system

sysctl -p


changeback.sh:

#!/system/bin/sh

su

mount -o remount,rw /system

rm /etc/sysctl.conf

mount -o remount,ro /system

sysctl -p

exit

but they don't work.

first mount command says : mount: file not found.

why ?

Sorry I am a total noob on the scripting side of things so cant really help.

How are you finding it now you have changed the perameters? I get a Quadrant score of 850 with these settings

kernel.shed_features = 24188

kernel.shed_tatency_ns = 6000000

kernel.shed_min_granularity_ns = 2000000

kernel.shed_child_runs_first=1

Link to comment
Share on other sites

Guest mrmrmrmr
Unsafe? This isn't like overclocking is it?

well it's not but these parameters are directly managing kernel. that's why I chose to use the values in OP.

your values are way too high. How did youcome to these numbers ?

Link to comment
Share on other sites

Guest spences10

Tha values are taken from the OP

EDIT

after experimenting quite a bit,

** to try experimenting with these tweaks you need root and busybox.. **

I reckon kernel.sched_features = 24188 is the most important, the NS I'm running at

kernel.sched_latency_ns = 6000000

kernel.sched_min_granularity_ns = 2000000

oops, that was from an earlier test.

Actually using your last suggestion for ns:

kernel.sched_latency_ns = 6000000

kernel.sched_min_granularity_ns = 2000000

Fair amount of usage on the phone today including sat nav, battery at 70% after 12hours

Link to comment
Share on other sites

I am using the values from the OP.

you have very high values (6M and 2M) , are you sure that's safe ?

If you read the thread I found the values I posted quoted from that other site causes some lagging, as the kernel seems to panic a bit too often.

the values I chose are around half the stock settings, ( i also posted those so blame dell if you think they are too high) they work for me.. :P

as to your shell issues, does giving su that way work?

I would consider it a security risk if it did.

Edited by fards
Link to comment
Share on other sites

When I try and run the first mount command I get a message back

"Usage : mount " and some other stuff

What am I doing wrong?

how are you trying to do it ?

do you have root and latest busybox installed and setup??

Link to comment
Share on other sites

Guest andycqos
how are you trying to do it ?

do you have root and latest busybox installed and setup??

The phone is rooted and IVe got USB debugging turned on. Connected to the PC I can use adb to get into shell, if I do "ls" I can see the folders on the phone, but the mount command didnt work.

I dont have busybox installed, I guess thats the problem

edited to add - when I tried to install busybox I get a message to say my phone is not nand unlocked

Edited by andycqos
Link to comment
Share on other sites

Ok, have just deleted both files and done the whole opperation via terminal emulator.

Take a look at the screen print.

How is this possible? am i being really nooby about this?

The 2 files have different permissions - they may contain different characters that ls cannot see.

Run 'ls /etc/sysctl.conf | od -c' and see if this shows different characters.

The best way to fix this is to delete both/all files using a wild card, e.g 'rm sysctl*' (obviously check there are no other files named with this pattern before deleting)

Link to comment
Share on other sites

The phone is rooted and IVe got USB debugging turned on. Connected to the PC I can use adb to get into shell, if I do "ls" I can see the folders on the phone, but the mount command didnt work.

I dont have busybox installed, I guess thats the problem

edited to add - when I tried to install busybox I get a message to say my phone is not nand unlocked

Sounds like your phone is not rooted properly - how have you rooted it?

Link to comment
Share on other sites

Guest andycqos
Sounds like your phone is not rooted properly - how have you rooted it?

I havent. Its the 8105 O2 release, which I thought was pre-rooted. It seems to run apps that require root access anyway.

Link to comment
Share on other sites

I havent. Its the 8105 O2 release, which I thought was pre-rooted. It seems to run apps that require root access anyway.

I installed/ran universal androot as well (it's dead easy)

Works fine on the 8105 build...

Details here:

http://android.modaco.com/content/dell-str...one-click-root/

After doing that you should be able to run adb fine :P

Link to comment
Share on other sites

Guest spences10
The 2 files have different permissions - they may contain different characters that ls cannot see.

Run 'ls /etc/sysctl.conf | od -c' and see if this shows different characters.

The best way to fix this is to delete both/all files using a wild card, e.g 'rm sysctl*' (obviously check there are no other files named with this pattern before deleting)

Good idea, i have just done a search cam up with 6 files five of which are sysctl.conf the other is just sysctl

locations:

/ect/sysctl.conf

/ect/sysctl.conf

/sdcard/sysctl_conf/sysctl.conf

/system/ect/sysctl.conf

/system/ect/sysctl.conf

/system/xbin/sysctl

I wll check them all to see if there are any differences.

[EDIT] They all looked like files i have created, deleted them all - they all reapreared in the same locations this time with the right variables.

Just run a quadrant = 742

Edited by spences10
Link to comment
Share on other sites

Guest andycqos
Cool. Ill give it a go

Cheers :)

Still the same :(

Rooted it succesfully with Universal Androot - although I got an error trying to install superuser - and installed Busybox, but still get the same "usage" error after doing the first line

edited to add - ok, ignore that got it working.

The problem was with the spacing in the command, and I put the device serial number into the mount.

O ...M and actual G - my phone is on fire! The transition between screens and opening and closing apps is much much quicker. If it improves my battery life too (it was seriously bad since upgrading to 2.1) I might even have to hunt down and kiss the OP :P

Thanks to everyone else for their help too

Edited by andycqos
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.