yeah that's right, it drains no matter what when display is on and radio is on, but there where issues regarding battery drain even in airplane mode that's why I shared. of course no use when running
thank you so much, im gonna give it a try
edit : a few more questions after i make the new file in init.d, what command should i type from the terminal to know if the script is running as it should? i'm trying the second option you given me, using only the init.d and i deleted the sysctl.conf. many thanks before
"Sysctl -p" runs it
"Syscyl -a" or "sysctl -a | grep vm" checks it
Sent from my ADR6300 using xda premium
I'm really sad that I flashed this MOD. it's been over 24 hours I've flashed this and from that time my phone takes 15 minutes to charge 1% battery. The battery drain is very fast. My phone doesn't charge fully even after 6,7 hours plugging the phone in. I've reflashed the rom with full wipe. Changed my kernel. I've done evrything I could do to sort out this problem but I failed...
Please tell me what should I do? My battery keeps on going down even if I do texting while charging the phone. Even when the phone is turned off it takes so much time to charge. HELP...!!!!
I'm writing while the phone is plugged in and it was 7% and now its 5% battery left. Help me asap.. plz.. I need my phone... How to cancel the effect of this zip file?
I've provided you with maximum details. I'm not near my computer for next 20 days. Not even in a wifi zone... Help me... Suggest me something I can do from phone only...
Sent from my HTC Desire
I'm really sad that I flashed this MOD. it's been over 24 hours I've flashed this and from that time my phone takes 15 minutes to charge 1% battery. The battery drain is very fast. My phone doesn't charge fully even after 6,7 hours plugging the phone in. I've reflashed the rom with full wipe. Changed my kernel. I've done evrything I could do to sort out this problem but I failed...
Please tell me what should I do? My battery keeps on going down even if I do texting while charging the phone. Even when the phone is turned off it takes so much time to charge. HELP...!!!!
I'm writing while the phone is plugged in and it was 7% and now its 5% battery left. Help me asap.. plz.. I need my phone... How to cancel the effect of this zip file?
I've provided you with maximum details. I'm not near my computer for next 20 days. Not even in a wifi zone... Help me... Suggest me something I can do from phone only...
Sent from my HTC Desire
Yep, that looks good.<br />Originally Posted by jimbub<br />
"Sysctl -p" runs it<br />
"Syscyl -a" or "sysctl -a | grep vm" checks it<br />
<br />
Sent from my ADR6300 using xda premium
<br />
Thanks for your response after running those command, here is what i get for the output, is this okay? Thanks in advance<br />
<br />
Sent from my GT-I9100 using xda premium
I would like to say that flashing the zip isn't a good idea, because it makes a folder called 10sysctl and every ROM I've flashed this on has 01sysctl; so it creates two different folders, which I think creates an issue. Also, I recommend the one without the semicolons too because I had issues with it on my Incredible.Well.. flashed yesterday using the zip.. I got the same output as losta... so I guess it's running and so far it's fine
The first thing I noticed is that takes a while longer to drop the percentage... but on heavy tasks such as using wifi or 3g can't really tell the diference so far... but I think i'm getting something out of this.. will know for sure in a couple of days
cheers for the effort.
HTC Desire
I would like to say that flashing the zip isn't a good idea, because it makes a folder called 10sysctl and every ROM I've flashed this on has 01sysctl; so it creates two different folders, which I think creates an issue. Also, I recommend the one without the semicolons too because I had issues with it on my Incredible.
Thanks for your contributions to the community PureMotive--ignore the haters.
What is the correct value. It is set twice!
fs.file-max=165164 or fs.file-max=65535
Depends on how much RAM your device has. Do you know the number?
My galaxy nexus has 1gb so...what value do I change? I just copied it and ran it...idk...maybe better but would compensating for my ram make more battery life?
Anyone?
Sent from my Galaxy Nexus using xda premium
There is a line in the mod called kernel.panic. What this does is set a value (in seconds) at which the kernel will start panic-ing and reboot the device to free memory. Kernel panic only occurs in OOM (out-of-memory) situations. If the value is set to 0 (kernel.panic=0), then the kernel will NOT panic and will continue with its functions.
Oh dear. The above is from your first post.
And here are the facts:
A kernel panic occurs when something goes horribly wrong within the kernel, which OOM doesn't necessarily cause unless vm.panic_on_oom is set to 1. A kernel panic can be caused by various things.
The kernel.panic tunable sets a timeout for an automatic reboot after a panic. It does *not* stop the kernel from panicking! If the kernel is going to panic, it *will* panic, there is nothing you can do to stop it as it is a last resort when there is an unrecoverable error.
So, with your tweak, if the kernel panics due to a hardware problem or a bug, the device will not reboot automatically and would simply be stuck there, frozen solid until the user pulls the battery. How unbelievably useless that is for a mobile telephone! How on *earth* could that be a performance improvement?
Also, seeing as you mention OOM, it happens that OOM is highly unlikely to be invoked on Android as Android has it's own low memory killer driver which kicks in to manage memory usage long before the OOM killer does. I have never seen OOM invoked on Android. OOM is like using a sledgehammer to crack a nut, which is why the Android team wrote their own, more finely grained implementation.
Seriously though, a bit of advice, learn about the tweaks you are doing, the advantages and drawbacks and if it is actually any use at all preferably *before* making yourself 'popular' by releasing it on XDA with a bold claim in the title, otherwise someone like me, *will* come along and debunk the myth that it does anything useful...
I've said my piece now and I won't reply again, because it's become old rather quickly and further replies on my part would be foolish and counter productive, as this one probably is, but what the hell.
The users can make the choice between taking the advice of someone who knows about kernels and maintains several, or someone who has put a bunch of tweaks together in a script and doesn't understand most of them.
Good evening.
Hey uh that's nice. But nobody really cares sorry. This tweak gets results for lots of folks...stop flaming the dev who still should get a lot of credit....wow...a$$h***
Sent from my Galaxy Nexus using xda premium
#sysctl.conf file
fs.nr_open=1053696;
fs.inotify.max_queued_events=32000;
fs.inotify.max_user_instances=256;
fs.inotify.max_user_watches=10240;
fs.lease-break-time=10;
fs.file-max=165164;
kernel.threads-max=525810;
kernel.random.write_wakeup_threshold=256;
kernel.random.read_wakeup_threshold=128;
kernel.sched_compat_yield=1;
kernel.panic=5;
kernel.panic_on_oops=1;
kernel.msgmni=2048;
kernel.msgmax=64000;
kernel.shmmni=4096;
kernel.shmall=2097152;
kernel.shmmax=268435456;
kernel.sem=500 512000 64 2048;
kernel.sched_features=24189;
kernel.hung_task_timeout_secs=30;
kernel.sched_latency_ns=18000000;
kernel.sched_min_granularity_ns=1500000;
kernel.sched_wakeup_granularity_ns=3000000;
kernel.sched_shares_ratelimit=256000;
kernel.sched_child_runs_first=0;
fs.lease-break-time=10;
fs.file-max=65536;
vm.dirty_ratio=90;
vm.dirty_background_ratio=80;
vm.oom_kill_allocating_task=1;
vm.overcommit_memory=1;
vm.page-cluster=3;
vm.drop_caches=3;
vm.min_free_kbytes=4096;
vm.panic_on_oom=0;
vm.dirty_expire_centisecs=1000;
vm.dirty_writeback_centisecs=2000;
vm.oom_kill_allocating_task=0;
vm.vfs_cache_pressure=10;
vm.min_free_order_shift=4;
vm.laptop_mode=0;
vm.block_dump=0;
#sysctl.conf file
fs.nr_open=1053696
fs.inotify.max_queued_events=32000
fs.inotify.max_user_instances=256
fs.inotify.max_user_watches=10240
fs.lease-break-time=10
fs.file-max=165164
kernel.threads-max=525810
kernel.random.write_wakeup_threshold=256
kernel.random.read_wakeup_threshold=128
kernel.sched_compat_yield=1
kernel.panic=5
kernel.panic_on_oops=1
kernel.msgmni=2048
kernel.msgmax=64000
kernel.shmmni=4096
kernel.shmall=2097152
kernel.shmmax=268435456
kernel.sem=500 512000 64 2048
kernel.sched_features=24189
kernel.hung_task_timeout_secs=30
kernel.sched_latency_ns=18000000
kernel.sched_min_granularity_ns=1500000
kernel.sched_wakeup_granularity_ns=3000000
kernel.sched_shares_ratelimit=256000
kernel.sched_child_runs_first=0
fs.lease-break-time=10
fs.file-max=65536
vm.dirty_ratio=90
vm.dirty_background_ratio=80
vm.oom_kill_allocating_task=1
vm.overcommit_memory=1
vm.page-cluster=3
vm.drop_caches=3
vm.min_free_kbytes=4096
vm.panic_on_oom=0
vm.dirty_expire_centisecs=1000
vm.dirty_writeback_centisecs=2000
vm.oom_kill_allocating_task=0
vm.vfs_cache_pressure=10
vm.min_free_order_shift=4
vm.laptop_mode=0
vm.block_dump=0
#!/system/bin/sh
# grep sysctl /etc/init.d/*
# Load /sys/etc/sysctl.conf
sysctl -p
# grep sysctl /etc/init.d/*
# Load /sys/etc/sysctl.conf
#!/system/bin/sh
sysctl -p
#!/system/bin/sh
sysctl -p /system/etc/
Oh dear. The above is from your first post.
And here are the facts:
A kernel panic occurs when something goes horribly wrong within the kernel, which OOM doesn't necessarily cause unless vm.panic_on_oom is set to 1. A kernel panic can be caused by various things.
The kernel.panic tunable sets a timeout for an automatic reboot after a panic. It does *not* stop the kernel from panicking! If the kernel is going to panic, it *will* panic, there is nothing you can do to stop it as it is a last resort when there is an unrecoverable error.
So, with your tweak, if the kernel panics due to a hardware problem or a bug, the device will not reboot automatically and would simply be stuck there, frozen solid until the user pulls the battery. How unbelievably useless that is for a mobile telephone! How on *earth* could that be a performance improvement?
Also, seeing as you mention OOM, it happens that OOM is highly unlikely to be invoked on Android as Android has it's own low memory killer driver which kicks in to manage memory usage long before the OOM killer does. I have never seen OOM invoked on Android. OOM is like using a sledgehammer to crack a nut, which is why the Android team wrote their own, more finely grained implementation.
Seriously though, a bit of advice, learn about the tweaks you are doing, the advantages and drawbacks and if it is actually any use at all preferably *before* making yourself 'popular' by releasing it on XDA with a bold claim in the title, otherwise someone like me, *will* come along and debunk the myth that it does anything useful...
I've said my piece now and I won't reply again, because it's become old rather quickly and further replies on my part would be foolish and counter productive, as this one probably is, but what the hell.
The users can make the choice between taking the advice of someone who knows about kernels and maintains several, or someone who has put a bunch of tweaks together in a script and doesn't understand most of them.
Good evening.
It can't.
There is nothing in there which would increase battery life. You are about as likely to increase battery life by stroking your phone and making a wish.
XDA still doesn't disappoint me with it's random placebo posts.
I used the zip posted on page 12 by kevdliu. I am running an Evervolv ICS 4.0.4 with tiamat kernel and here is what I have found after the third day of use.
Normally after 18 hours of light use I would be down around 20% and be ready for a charge. I just picked up my phone now to check the battery and at 20 hours still at 62% after the same amount of use. So standby time definitely uses less juice in my experience.
Watching videos and heavy screen usages for example games, still blows though battery but is noticeably better. Probably wouldn't make it all day for heavy users.
Every night I walk for about two hours and stream music over slacker radio to a bluetooth headset. (no use of the display mind you) Normally this takes almost 50% of my battery. last night 8%.... holy crap yes only 8%
Thanks for everyone who put effort into this!