Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Thread Closed

[MOD] Improve your battery life

OP Hero

6th May 2012, 10:52 PM   |  #281  
Senior Member
Thanks Meter: 319
 
1,556 posts
Join Date:Joined: Mar 2011
Quote:
Originally Posted by s197

I don't see it as flaming, he's refuting his claims with well reasoned arguments. Not everyone wishes to follow like blind sheep, I for one am glad to hear an opposing argument when it is well presented as his.

I guess. Great mod still

Sent from my Galaxy Nexus using xda premium
6th May 2012, 11:17 PM   |  #282  
KennyG123's Avatar
RC-RT Committee / Senior Moderator / Spider-Mod
Flag Right behind you!
Thanks Meter: 27,327
 
28,988 posts
Join Date:Joined: Nov 2010
Donate to Me
More
Let's remember that the OP is trying to help users. As every phone is different, it might not help all. But let's keep it kind and friendly and offer constructive criticisms at most, help at best. Thanks for making XDA the best!
FNM
The Following 3 Users Say Thank You to KennyG123 For This Useful Post: [ View ]
7th May 2012, 12:19 AM   |  #283  
That Baker Guy's Avatar
Senior Member
Flag Tobie Town
Thanks Meter: 32
 
261 posts
Join Date:Joined: Dec 2011
More
Quote:
Originally Posted by _thalamus

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.

peace* FTFY
7th May 2012, 03:22 AM   |  #284  
Gfrt94yn's Avatar
Senior Member
Thanks Meter: 13
 
121 posts
Join Date:Joined: Aug 2011
More
interesting find... i installed the zip provided, except i think now its out of date ( i don't think i was working anyway...) now whenever i flash the updated zip (as of may 3) and i get the abort (0) bad error or whatever, which probably meant a corrupted file. Anyway I used terminal emulator to check and make sure everything stuck and i believe it did, but my phone was messing up so i performed a CLEAN wipe and got it all started back again. This time, however, I manually pushed the script (overwrite sysctl.conf and there was already a 10sysctl file in the init.d directory of /system/ect). Except the strange part is now when i manually try to enable or even just check to see if everything stuck, terminal doesn't even recognize the commands:
"sysctl -p" or "sysctl -a| grep vm" anymore... any ideas on how to fix?
Oh also i'm on a SGS2 Skyrocket running seans ICS (leaked)
7th May 2012, 07:56 AM   |  #285  
cmlusco's Avatar
Senior Member
Flag Michigan City, IN
Thanks Meter: 932
 
3,146 posts
Join Date:Joined: Nov 2010
Donate to Me
More
Since this mod came out, and actually way before, i have been doing some heavy research on sysctl tweaking. In my research and testing i have found that messing with most of these settings only cause issues and performance drops. I have found a combination of settings which seem to work best for me. The phone seems snappier and battery life slightly better. I have created a flashable zip with these settings if anyone else would like to try them. I make no guarantees or inflated claims, just that this is what works best for me running a mostly stock rom on the incredible with the latest gingertiny kernel and also v6 supercharger. This flashable should also fix the issue some are having with the sysctl -p and sysctl grep commands not working thru the terminal emulator, or activating sysctl.

http://dinc.does-it.net/Mods/sysctl_...072012_001.zip
The Following 2 Users Say Thank You to cmlusco For This Useful Post: [ View ]
7th May 2012, 09:28 AM   |  #286  
pk2018's Avatar
Member
cchina
Thanks Meter: 3
 
66 posts
Join Date:Joined: Feb 2011
in the sysctl_conf.zip from 1 floor

kernel.random.write_wakeup_threshold=256
kernel.random.read_wakeup_threshold=128
kernel.panic=5
kernel.sched_compat_yield=1
kernel.panic=0
kernel.panic_on_oops=1


?????
7th May 2012, 10:06 AM   |  #287  
Hero's Avatar
OP Recognized Developer
West Hollywood
Thanks Meter: 4,817
 
1,286 posts
Join Date:Joined: Oct 2010
Donate to Me
Quote:
Originally Posted by pk2018

in the sysctl_conf.zip from 1 floor

kernel.random.write_wakeup_threshold=256
kernel.random.read_wakeup_threshold=128
kernel.panic=5
kernel.sched_compat_yield=1
kernel.panic=0
kernel.panic_on_oops=1


?????

Use kernel.panic=0
The Following User Says Thank You to Hero For This Useful Post: [ View ]
7th May 2012, 01:37 PM   |  #288  
Recognized Developer
Thanks Meter: 4,366
 
8,138 posts
Join Date:Joined: Jan 2011
More
Fyi

Kernel.panic=0 will prevent a reboot on a kernel panic instead it will freeze and a battery pull is needed to recover it. The default on Android is 5. I don't like this setting of 0 mainly as it will make diagnosing a kernel reboot more difficult as it won't produce a reboot and last_kmsg.

I've only looked into this one setting so I won't comment on anything else.

It does not prevent a kernel panic at all. Kernel.panic=0 is the default on Linux but its not really suited for mobile devices.

Sent from my Galaxy Nexus using Tapatalk 2
The Following 2 Users Say Thank You to tiny4579 For This Useful Post: [ View ]
7th May 2012, 03:34 PM   |  #289  
Senior Member
Flag Greifswald
Thanks Meter: 212
 
484 posts
Join Date:Joined: Feb 2012
More
Wow, it's always great to see how people can use full quotes just to write some lame fck u under posts they don't like. Congrats Mr Baker Guy, you are the greatest ten year old in this forum.
The Following User Says Thank You to muellersmattes For This Useful Post: [ View ]
7th May 2012, 04:31 PM   |  #290  
Senior Member
Thanks Meter: 100
 
305 posts
Join Date:Joined: Oct 2010
A new record for me. This is with the stock battery no less.





-xdadevelopers-user
Attached Thumbnails
Click image for larger version

Name:	2012-05-07_08-24-56.jpg
Views:	2186
Size:	29.7 KB
ID:	1046563   Click image for larger version

Name:	2012-05-07_08-25-01.jpg
Views:	2185
Size:	24.4 KB
ID:	1046564  

Thread Closed Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes