Thk u.
I make mine in this way too but no luck.
Which ROM and Kernel are u using?
Sent from my E10i using xda premium
[MOD] Improve your battery life
- Thread starter Hero
- Start date
- Status
Thk u.
I make mine in this way too but no luck.
Which ROM and Kernel are u using?
Sent from my E10i using xda premium
What is the output from terminal when the script is working when you run sysctl -p?
Sent from my ADR6300 using XDA
Sent from my ADR6300 using XDA
Does anyone have a controlled, repeated test to see if this is any good?
If not, I may do one later on myself and post the results here. I just would like to know if this will work with CM7 and Incredikernel 2.6.38.8?
If not, I may do one later on myself and post the results here. I just would like to know if this will work with CM7 and Incredikernel 2.6.38.8?
$ export PATH=/data/local/bin:$PATH
$ su
# sysctl -p
sysctl: short write
# sysctl -a| grep vm
vm.overcommit_memory = 1
vm.panic_on_oom = 0
vm.oom_kill_allocating_task = 0
vm.oom_dump_tasks = 1
vm.overcommit_ratio = 50
vm.page-cluster = 3
vm.dirty_background_ratio = 5
vm.dirty_background_bytes = 0
vm.dirty_ratio = 20
vm.dirty_bytes = 0
vm.dirty_writeback_centisecs = 500
vm.dirty_expire_centisecs = 200
vm.nr_pdflush_threads = 0
vm.swappiness = 60
vm.lowmem_reserve_ratio = 32
vm.drop_caches = 0
vm.min_free_kbytes = 2618
vm.min_free_order_shift = 4
vm.percpu_pagelist_fraction = 0
vm.max_map_count = 65530
vm.laptop_mode = 0
vm.block_dump = 0
vm.vfs_cache_pressure = 100
vm.mmap_min_addr = 32768
vm.scan_unevictable_pages = 0
sysctl: error reading key 'net.ipv4.route.flush': Permission denied
sysctl: error reading key 'net.ipv6.route.flush': Permission denied
#
What to do now?
$ su
# sysctl -p
sysctl: short write
# sysctl -a| grep vm
vm.overcommit_memory = 1
vm.panic_on_oom = 0
vm.oom_kill_allocating_task = 0
vm.oom_dump_tasks = 1
vm.overcommit_ratio = 50
vm.page-cluster = 3
vm.dirty_background_ratio = 5
vm.dirty_background_bytes = 0
vm.dirty_ratio = 20
vm.dirty_bytes = 0
vm.dirty_writeback_centisecs = 500
vm.dirty_expire_centisecs = 200
vm.nr_pdflush_threads = 0
vm.swappiness = 60
vm.lowmem_reserve_ratio = 32
vm.drop_caches = 0
vm.min_free_kbytes = 2618
vm.min_free_order_shift = 4
vm.percpu_pagelist_fraction = 0
vm.max_map_count = 65530
vm.laptop_mode = 0
vm.block_dump = 0
vm.vfs_cache_pressure = 100
vm.mmap_min_addr = 32768
vm.scan_unevictable_pages = 0
sysctl: error reading key 'net.ipv4.route.flush': Permission denied
sysctl: error reading key 'net.ipv6.route.flush': Permission denied
#
What to do now?
After using Tinys config file I still get the permission denied, I'm on a Thunderbolt by the way. So is the rest working?? 
Sent from my Infected Eternity Thunderbolt using Tapatalk 2.
Sent from my Infected Eternity Thunderbolt using Tapatalk 2.
Yeah that should be fine. Its just the couple settings that fail.
Sent from my Galaxy Nexus using Tapatalk 2
So is mines working now even tho those bottom values failed? So the "mod" is running?
I always checked the output of dirty_ratio and it should be 90 based on the mod. Yours was 20. The short write means that sysctl -p probably failed. Try my sysctl file a few pages back. It just doesn't have the net tweaks in it.
Sent from my Galaxy Nexus using Tapatalk 2
Tiny's config applied without the short write error and the phone is working fine. But for some reason the dialer is really chomping on battery now, whereas before the mod it rarely showed up in the stats.
I updated the OP with a new code (Thanks to Tiny). I just removed the semicolons. Use this version if the other does not work for you.
So will the .zip work at all or is it like a 50/50 of actually helping?
Sent from my ADR6300 using XDA
Sent from my ADR6300 using XDA
I've switched to the non semi colon ending version and here is the output. Is this what I should see?
$ export PATH=/data/local/bin:$PATH
$ su
# sysctl -p
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.panic = 5
kernel.sched_compat_yield = 1
kernel.panic = 0
kernel.panic_on_oops = 1
sysctl: error: 'kernel.msgmni' is an unknown key
sysctl: error: 'kernel.msgmax' is an unknown key
sysctl: error: 'kernel.shmmni' is an unknown key
sysctl: error: 'kernel.shmall' is an unknown key
sysctl: error: 'kernel.shmmax' is an unknown key
sysctl: error: 'kernel.sem' is an unknown key
sysctl: error: 'kernel.sched_features' is an unknown key
sysctl: error: 'kernel.hung_task_timeout_secs' is an unknown key
sysctl: error: 'kernel.sched_latency_ns' is an unknown key
sysctl: error: 'kernel.sched_min_granularity_ns' is an unknown key
sysctl: error: 'kernel.sched_wakeup_granularity_ns' is an unknown key
sysctl: error: 'kernel.sched_shares_ratelimit' is an unknown key
kernel.sched_child_runs_first = 0
fs.lease-break-time = 10
fs.file-max = 65536
net.core.wmem_max = 524288
net.core.rmem_max = 524288
net.core.rmem_default = 262144
net.core.wmem_default = 262144
net.core.optmem_max = 20480
net.unix.max_dgram_qlen = 50
net.ipv4.tcp_keepalive_time = 900
net.ipv4.tcp_keepalive_probes = 5
net.ipv4.tcp_keepalive_intvl = 156
net.ipv4.tcp_timestamps = 0
net.ipv4.tcp_sack = 1
net.ipv4.tcp_fack = 1
net.ipv4.tcp_window_scaling = 1
net.ipv4.tcp_tw_recycle = 1
net.ipv4.tcp_tw_reuse = 1
sysctl: short write
#
Sent from my ADR6300 using XDA
$ export PATH=/data/local/bin:$PATH
$ su
# sysctl -p
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.panic = 5
kernel.sched_compat_yield = 1
kernel.panic = 0
kernel.panic_on_oops = 1
sysctl: error: 'kernel.msgmni' is an unknown key
sysctl: error: 'kernel.msgmax' is an unknown key
sysctl: error: 'kernel.shmmni' is an unknown key
sysctl: error: 'kernel.shmall' is an unknown key
sysctl: error: 'kernel.shmmax' is an unknown key
sysctl: error: 'kernel.sem' is an unknown key
sysctl: error: 'kernel.sched_features' is an unknown key
sysctl: error: 'kernel.hung_task_timeout_secs' is an unknown key
sysctl: error: 'kernel.sched_latency_ns' is an unknown key
sysctl: error: 'kernel.sched_min_granularity_ns' is an unknown key
sysctl: error: 'kernel.sched_wakeup_granularity_ns' is an unknown key
sysctl: error: 'kernel.sched_shares_ratelimit' is an unknown key
kernel.sched_child_runs_first = 0
fs.lease-break-time = 10
fs.file-max = 65536
net.core.wmem_max = 524288
net.core.rmem_max = 524288
net.core.rmem_default = 262144
net.core.wmem_default = 262144
net.core.optmem_max = 20480
net.unix.max_dgram_qlen = 50
net.ipv4.tcp_keepalive_time = 900
net.ipv4.tcp_keepalive_probes = 5
net.ipv4.tcp_keepalive_intvl = 156
net.ipv4.tcp_timestamps = 0
net.ipv4.tcp_sack = 1
net.ipv4.tcp_fack = 1
net.ipv4.tcp_window_scaling = 1
net.ipv4.tcp_tw_recycle = 1
net.ipv4.tcp_tw_reuse = 1
sysctl: short write
#
Sent from my ADR6300 using XDA
You need to do "sysctl -a| grep vm" (without quotes). "sysctl -p" just initializes sysctl.conf
Will this mod work for the Galaxy Nexus CDMA? As you all know, the GNex desperately needs increased battery life lol
EDIT: Okay, just tried it and everything boots up. Don't know yet if it helps battery but will report back. Also, when I put that command in emulator to see if it works, I get some permission denied reading as: "systctl: error reading key 'kernel.cad_pid'"
"systctl: error reading key 'kernel.usermodhelper.inheritable'"
"systctl: error reading key 'kernel.usermodhelper.bset'"
"systctl: error reading key 'vm.compact_memory'"
"systctl: error reading key 'net.ipv4.route.flush'"
"systctl: error reading key 'net.ipv6.route.flush'"
Everything else checks fine except those. Could it have something to do with me using V6 Supercharger?
EDIT: Okay, just tried it and everything boots up. Don't know yet if it helps battery but will report back. Also, when I put that command in emulator to see if it works, I get some permission denied reading as: "systctl: error reading key 'kernel.cad_pid'"
"systctl: error reading key 'kernel.usermodhelper.inheritable'"
"systctl: error reading key 'kernel.usermodhelper.bset'"
"systctl: error reading key 'vm.compact_memory'"
"systctl: error reading key 'net.ipv4.route.flush'"
"systctl: error reading key 'net.ipv6.route.flush'"
Everything else checks fine except those. Could it have something to do with me using V6 Supercharger?
Last edited:
Using the sysctl.conf from the first page (either with or without semicolons) doesn't work for me - get the 'short write' message in terminal when trying to execute sysctl -p. Using the file Tiny uploaded seems to work, will give that a try. Just an fyi.
i just removed everything net.* and worked fine thereafter. i guess one of the net.* is causing the shortwrite and halting everything after it
- Status
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
99
Before we get to the mod, I want to get a little personal. I make these mods so that your Android experience will be enhanced. If you find something wrong with the mod then provide constructive criticism. Don't just sit there behind your computer and degrade the effects based on what you see in the code, especially if you are even unwilling to try the mod in the first place. That irritates the hell out of me and unfortunately, I can't help you with your issues...so do yourself and others a favor and either use the mod and provide constructive criticism such as results (positive or negative) or ways to improve it or don't use it at all. That being said, these tweaks work in conjunction with each other, they are not each meant to increase your battery life.
This is my mod for achieving good-great battery life. This is the mod I use in Anthem™ which has given me 50+ hours on a single charge. The increase in battery life may not be "tenfold" for you, but it does increase, which is still better than not increasing. Contact me before including it in your own ROM (that you plan on publicly releasing). I will allow you to use it, just ask first. Please give credit or thanks or both
First: Here is a flashable .zip of the mod that may or may not work with your ROM. I'd still advise doing it manually.Requirements:
Sysctl.conf - Updated May 3, 2012
- HTC Incredible (preferably)
- Kernel with zram swap (for swappiness)
- Kernel with init.d support
Currently working on:
- HTC Incredible - Anthem, Clutch, AOKP, ICSenseless
- HTC Amaze 4G
Step 1
Open up your ROM.zip (or whatever it's called) in 7zip (Windows) or Betterzip (OSX) and locate
sysctl.conf in /system/etc
If it's not in this directory, create it.
Step 2
In your sysctl.conf file, paste the following code and save it.
Code:#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;
If the above code does not work for you, try this one. It has the semi-colons removed. Thanks Tiny
Code:#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
Step 3
Now we need to enable it. So, navigate to /system/etc/init.d and create a file with the following code:
Code:#!/system/bin/sh # grep sysctl /etc/init.d/* # Load /sys/etc/sysctl.conf sysctl -p
sysctl -p is what initializes the code.
Just FYI: You don't actually need these lines:
Code:# grep sysctl /etc/init.d/*Code:# Load /sys/etc/sysctl.conf
So this would have just sufficed.
Code:#!/system/bin/sh sysctl -p
If the above code does not work for any reason, try this:
Code:#!/system/bin/sh sysctl -p /system/etc/
Name your file something like this 10sysctl
Save your file.
NOTE: Your ROM must support init.d. You can do this by using dsixda's android kitchen
Step 4
Save your ROM and install it via recovery
OR
you could just push the files into your current ROM and try them out.
Credits to imoseyon for portions of the info
Ok, so what exactly is sysctl.conf?
The sysctl.conf is a configuration file for "sysctl" which is an interface for dynamically changing kernel parameters in the Linux OS. The configuration file contains the following elements, vm.min_free_kbytes, vm.dirty_ratio, vm.dirty_backgroud_ratio, vm.vfs_cache_pressure, vm.oom_kill_allocating_task. There are many other elements within the file, but we will be primarily focusing on these specifically (the vm prefix stands for virtual memory). The sysctl.conf file should be located in /etc (/system/etc) by default. To enable it you need your ROM to execute "sysctl -p" somewhere during the boot process (or shortly afterward). We will also be discussing how to enable it if it is not already done so. You can also run sysctl -p manually to enable it any time after the OS is started.
Now, let’s get down to what sysctl.conf does and how it works.
min free kbytes (vm.min_free_kbytes)
This is used to force the Linux VM to keep a minimum number of kilobytes free. The VM uses this number to compute a pages_min value for each lowmem zone in the system. Each lowmem zone gets a number of reserved free pages based proportionally on its size. Default is 2048kb.
dirty ratio (vm.dirty_ratio) and dirty background ratio (vm.dirty_background_ratio)
This controls how often the kernel writes data to "disk" (in our case the internal microSD system card, not the removable microSD card). When your apps write data to disk, Linux actually doesn't write the data out to the disk right away, it actually writes the stuff to system memory and the kernel handles when and how the data is actually going to be flushed to the disk. These values represent a percentage, the higher the percentage, the longer it waits to flush, the lower the percentage, the more often flushes will occur. Now remember, we are dealing with solid state storage, not the traditional disk platter and spindle. So we are actually able to delay flushes a little longer with solid state versus a traditional hard drive disk.
VFS Cache Pressure (vm.vfs_cache_pressure)
Now here is where it gets interesting! File system cache (dentry/inode) is really more important than the block cache above in dirty ratio and dirty background ratio, so we really want the kernel to use up much more of the RAM for file system cache, this will increas the performance of the system without sacrificing performance at the application level. The default value is 100, as a percentage, and what you want to do is lower the value to tell the kernel to favor the file system cache and not drop them aggressively.
oom allocating task (vm.oom_kill_allocating_task)(enable or disable, generally in Linux this value is either a "1" or a "0," representing as on or off.)
This enables or disables killing the OOM-triggering task in out-of-memory (oom) situations. If this is set to zero, or disabled, the OOM killer will scan through the entire task list and select a task based on heuristics to kill. This normally selects a rogue memory-hogging task that frees up a large amount of memory when killed. If this is set to non-zero, or enabled, the OOM killer simply kills the task that triggered the out-of-memory condition. This avoids the expensive task list scan, which can take mass amounts of time and "hang" or freeze the system.
block_dump (vm.block_dump)
This enables block I/O debugging when set to a nonzero value. If you want to find out which process caused the disk to spin up (see /proc/sys/vm/laptop_mode), you can gather information by setting the flag.
When this flag is set, Linux reports all disk read and write operations that take place, and all block dirtyings done to files. This makes it possible to debug why a disk needs to spin up, and to increase battery life even more. The output of block_dump is written to the kernel output, and it can be retrieved using "dmesg". When you use block_dump and your kernel logging level also includes kernel debugging messages, you probably want to turn off klogd, otherwise the output of block_dump will be logged, causing disk activity that is not normally there.
overcommit_memory (vm.overcommit_memory)
This controls overcommit of system memory, possibly allowing processes to allocate (but not use) more memory than is actually available.
0 - Heuristic overcommit handling. Obvious overcommits of address space are refused. Used for a typical system. It ensures a seriously wild allocation fails while allowing overcommit to reduce swap usage. root is allowed to allocate slighly more memory in this mode. This is the default.
1 - Always overcommit. Appropriate for some scientific applications.
2 - Don't overcommit. The total address space commit for the system is not permitted to exceed swap plus a configurable percentage (default is 50) of physical RAM. Depending on the percentage you use, in most situations this means a process will not be killed while attempting to use already-allocated memory but will receive errors on memory allocation as appropriate.
page-cluster (vm.page-cluster)
This controls the number of pages which are written to swap in a single attempt. The swap I/O size.
It is a logarithmic value - setting it to zero means "1 page", setting it to 1 means "2 pages", setting it to 2 means "4 pages", etc.
The default value is three (eight pages at a time). There may be some small benefits in tuning this to a different value if your workload is swap-intensive.
panic_on_oom (vm.panic_on_oom)
This enables or disables panic on out-of-memory feature. If this is set to 1, the kernel panics when out-of-memory happens. If this is set to 0, the kernel will kill some rogue process, by calling oom_kill().
Usually, oom_killer can kill rogue processes and system will survive. If you want to panic the system rather than killing rogue processes, set this to 1.
The default value is 0.
Panic is a system error that is detected by the kernel.
dirty_expire_centisecs (vm.dirty_expire_centisecs)
How old "dirty" data should be before the kernel considers it old enough to be written to disk. It is expressed in 100ths of a second.
dirty_writeback_centisecs (vm.dirty_writeback_centisecs)
This is the interval of when the writeback daemons periodically wake up and write "old" data out to disk. It is expressed in 100ths of a second.5
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 premium4i created a flashable zip of everything except the net.* tweaks as that was causing problems for me.
download is here: http://www.mediafire.com/?j3gdgdcawj9imcq
havent tested it yet and its not guaranteed to install on every phone as there are different mount points for /system4It 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.
Why don't you try it first before posting?
This line in particular "vm.vfs_cache_pressure=10" is important because we want the kernel to favor retaining the file system cache as opposed to trying to reclaim it. In essence, a low vfs_cache_pressure slows things down, saving battery life. This works in conjunction with your ROM's swappiness level (which should be 1,0, or close to 0) so that the Linux kernel no longer attempts to enlarge the cache by paging applications out (keeping the system fast).
Sent from my Incredible using Tapatalk3
I updated the OP with a new .zip that might have the same effects as the one posted on page 12. Dunno for sure, but if anyone wants to try it out, let me know how it works
