Database Users

[GUIDE] Supercharger V6 script for ICS

I'm running this script for a while now on my xperia arc(while running on CM7.2 and GM9) and it works great. Also had this on HC on the tf101 so i tried it yesterday and on ICS and it works great! I made a guide for you all to try it:
First of all: I'm not responsible if you break your tf101!
What do you need:
- A rooted tf101
- Script manager
- The V6 Supercharger U9RC7 script
What to do:
- Place the script somewhere on you tf101 where you can find it
- Start the script manager app, in options celect 'browse as root'
- Browse with script manager to the script and select it, press the SU button and run the script
- Follow the instructions given by the script, after it is finished you can configure the script any way you'll like(i've chosen option 8)
- When finnished do a clean reboot like the script suggest
- If you'll run the script again it will whine about your weak ass launcher because of some problems with ICS
- So go to this website on you device: http://android.mimic.ca
- Upload the services.jar (found in /system/framework)
- Click the CWM option and click on next
- Download the zip file to your device
- Reboot into recovery and flash the zip file
- Restart your device, run the script again and: tada the script works as it should!
I'tested it on revolver 4.0.0 Beta 1.3.1 and it works! Revolver is based on stock so i think this also should work on stock ICS
All credits go out to zeppelinrox for making this awesome script and making it run on ICS! More info about the script is found here

For those who like to know more about this Supercharger V6 script, this is the thread about it.
It advertises itself as a "Complete Memory Management Fix". (ICS OOM Priority Charger)

Euhm why do we want to use this on our tfs and ics ? It makes no sense to me....

gkillerx said:
Euhm why do we want to use this on our tfs and ics ? It makes no sense to me....
Click to expand...
Click to collapse
Here is a qoute from the original thread:
zeppelinrox said:
==================================================================================
What's it do?
It makes your phone FAST... super snappy with better multitasking!
It rearranges and fixes the OOM Groupings and Priorites and lowmemorykiller values.
So basically, it's a COMPLETE MEMORY MANAGEMENT FIX!
It's the ONLY one of it's kind
NO LAUNCHER REDRAWS, faster than ever, multitasking is better... why?
Because it works with the lowmemorykiller and letting it work the way it's meant to work.
Also, because of the rearrangement, it works the same on all roms!
The problem with using minfree tweakers like AMM or AKMO is that it doesn't work the same on all roms.
Secondary apps may be in slot 3 on some roms but in slot 5 in others!
That's why you hear people comment "I tried AKMO but it didn't do anything..."
Most likely it didn't do anything because the apps weren't sitting where they were expected to be.
So fasten your seat belts and enjoy the ride!
==================================================================================
Click to expand...
Click to collapse
More info about the script is found here

Thanks, I was using this on my Droid X.
Will give it a shot with AOKP.

For people running the stock OTA ICS update, in the Transformer theme and app area I've put an updated services.odex which is necessary for full supercharging under ICS. If you're still on Honeycomb you can do it all with the script but ICS changed the way process priorities work and require modifying the services.odex file.
The update is also on the main V6 Supercharger thread along with full instructions on how to update services manually if you so desire.
Sent from my PG41200 using Xparent Purple Tapatalk

On devices with 1gb of RAM, I don't really see the point.

linuques said:
On devices with 1gb of RAM, I don't really see the point.
Click to expand...
Click to collapse
this is what I meant.
I use it on my HTC hero because it has only 192 mb but with 1 GB there is no need for this.

I have error running the script as below:
/sdcard/Download/V6_SuperCharger_for_Android-Update9_RC7.sh[5194]: /256: unexpected '/'
Click to expand...
Click to collapse

ZhenMing said:
I have error running the script as below:
Click to expand...
Click to collapse
which option did you choose?

kistigun said:
which option did you choose?
Click to expand...
Click to collapse
Before i could choose anything. There was a point paused for Enter. After i pressed Enter, it list out the options and in the end, the script were just stop with the error msg.
zOOM... zOOM...
================================================
|| // #####
|| // # #
|| // # -=SUPERCHARGER=-
|| // #####
||// # #
| / # # Presented by:
|/ ##### -=zeppelinrox=-
================================================
NOTE: BUSYBOX v1.16.2 OR HIGHER IS RECOMMENDED!
================================================
Touch the screen to bring up soft keyboard
================================================
Additional BusyBox Info:
BusyBox v1.19.3 (2011-12-21
14:13:27 CST) multi-call binary.
BE SURE IT'S A COMPLETE VERSION!
You are currently using BusyBox v1.19.3...
...which is fine - if it's COMPLETE!
================================================
Hey Rookie!!
================================================
First Time SuperChargers...
...will make a Pit Stop in...
...Driver Options!
================================================
com.android.launcher is the home launcher!
But verify groupings with the bOOM Stick!
================================================
Press the Enter Key... and Come Get Some!!
================================================
For Help & Info, see /sdcard/!SuperCharger.html
================================================
\\\\ T H E V 6 S U P E R C H A R G E R ////
============================================
\\\\ Driver's Console ////
==============================
1. SuperCharger & Launcher Status {Update 9 RC7}
}
==================== 256 HP ====================
2. UnLedded (Multitasking){8,12,22,24,26,28 MB}
3. Ledded (Balanced){8,12,26,28,30,32 MB}
4. Super UL (Aggressive){8,12,28,30,35,50 MB}
}
==================== 512 HP ====================
5. UnLedded (Multitasking){8,14,40,50,60, 75 MB}
6. Ledded (Balanced){8,14,55,70,85,100 MB}
7. Super UL (Aggressive){8,14,75,90,95,125 MB}
}
=================== 768+ HP ====================
8. Super 768HP(Aggressive){8,16,150,165,180,200}
9. Super 1000HP(Agressive){8,16,200,220,240,275}
}
================================================
10. Quick V6 Cust-OOMizer {Create Or Restore!}
================================================
11. OOM Grouping Fixes + Hard To Kill Launcher }
12. OOM Grouping Fixes + Die-Hard Launcher }
13. OOM Grouping Fixes + BulletProof Launcher }
================================================
14. UnKernelizer {UnDo Kernel/VM Tweaks}
15. UnSuperCharger {Revert Memory Settings}
================================================
16. The bOOM STICK {Verify OOM Groupings}
17. BulletProof Apps {Hit or Miss}
18. Engine Flush {ReCoupe RAM & Kill Lag}
19. Detailing {Vacuum & Reindex SQL DBs}
20. Nitro Lag Nullifier {Experimental}
================================================
21. System Installer {Terminal Usage}
22. Re-SuperCharger {Restore V6 Settings}
23. PowerShifting {Switch Presets FAST!}
================================================
24. Owner's Guide {Open !SuperCharger.html}
25. Help Centre {Open XDA SC Thread}
26. Driver Options {Settings}
27. SuperCharge You {Really!}
28. ReStart Your Engine {Reboot Instantly}
29. SuperClean & ReStart {Wipe Dalvik & Reboot}
30. Eject {Exit}
================================================
\\\\ The One and ONLY OOM Fixer! ////
============================================
So is it working? READ MESSAGES BELOW ;]
================================================
The Next 4 Sections Are Worth 25% Each!!
================================================
Launcher is on ICeS .... so.... weak....
(Assumes that stock ICS ADJs are in effect!)
================================================
SuperCharger ADJ Entries NOT Possible...
================================================
Protect the Launcher via "BulletProof Apps"!
================================================
SuperCharged Launcher is not in effect...
ICS WON'T load values from a prop file
But the other fixes STILL work!
But now you can do it via SERVICES.JAR...
...See the XDA Thread for more info!
================================================
SuperCharger Minfrees NOT FOUND! Run 2 - 10!
================================================
/sdcard/Download/V6_SuperCharger_for_Android-Update9_RC7.sh[5194]: /256: unexpected '/'
Click to expand...
Click to collapse

on what rom are you? stock?
never mind, the sript should run no matter what rom you're on.
try to redownload the script and try it again.

Downloaded 4 times and same result... direct using the terminal to run the script... same result...

What does the "Aggressive" choice do?
I want something extremely fast and stable BUT NOT dangerous...

I install option 8 on Revolution HD™ 3.1.0 and get random reboot and hank screen on which drain my battery.
I remove and re-install it. Let see is it getting better.

I got an Error
Telling me to re-install Busybox which I did but it still gives me the error over and over!
I tried using Terminal Emulator but I got the same result! :'(

warlord234 said:
I install option 8 on Revolution HD™ 3.1.0 and get random reboot and hank screen on which drain my battery.
I remove and re-install it. Let see is it getting better.
Click to expand...
Click to collapse
Work fine for me on Revolution HD 3.1.0 with option 8.
xMini said:
I got an Error
Telling me to re-install Busybox which I did but it still gives me the error over and over!
I tried using Terminal Emulator but I got the same result! :'(
Click to expand...
Click to collapse
Didn't ask me to re-install Busybox (running RevolutionHD ICS 3.1.0)

I did not do the services.jar thingy but I was able to set it to the option with bulletproof launcher. which option is the best?

bsoplinger said:
For people running the stock OTA ICS update, in the Transformer theme and app area I've put an updated services.odex which is necessary for full supercharging under ICS. If you're still on Honeycomb you can do it all with the script but ICS changed the way process priorities work and require modifying the services.odex file.
The update is also on the main V6 Supercharger thread along with full instructions on how to update services manually if you so desire.
Sent from my PG41200 using Xparent Purple Tapatalk
Click to expand...
Click to collapse
Your services.codex gave be a bootloop.

xuser said:
Your services.codex gave be a bootloop.
Click to expand...
Click to collapse
Running stock US OTA update? There shouldn't be any reason for it to bootloop.
Sent from my HTC Flyer P512 using Xparent Purple Tapatalk

[MOD] Improve your battery life tenfold UPDATE 04/29/2012

Improve your battery life tenfold by PureMotive​
tested and working at: SGS, Xperia Play, HTC Inc S, the battery life has increased significantly
Original link: http://forum.xda-developers.com/showthread.php?t=1621808​http://forum.xda-developers.com/showthread.php?t=1621808
PureMotive said:
Okay guys, I just thought I'd give you 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. Feel free to include it in your own ROM or whatever. 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.
Sysctl.conf - Outdated as of 4/29/2012​
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.panic=5;
kernel.sched_compat_yield=1;
kernel.panic=0;
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;
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;
net.ipv4.tcp_congestion_control=cubic;
net.ipv4.tcp_syncookies=1;
net.ipv4.conf.all.rp_filter=1;
net.ipv4.conf.default.rp_filter=1;
net.ipv4.tcp_synack_retries=2;
net.ipv4.tcp_syn_retries=2;
net.ipv4.tcp_max_syn_backlog=1024;
net.ipv4.tcp_max_tw_buckets=16384;
net.ipv4.icmp_echo_ignore_all=1;
net.ipv4.icmp_ignore_bogus_error_responses=1;
net.ipv4.tcp_no_metrics_save=1;
net.ipv4.tcp_fin_timeout=15;
net.ipv4.tcp_keepalive_intvl=30;
net.ipv4.tcp_keepalive_probes=5;
net.ipv4.tcp_keepalive_time=1800;
net.ipv4.ip_forward=0;
net.ipv4.conf.default.accept_source_route=0 ;
net.ipv4.conf.all.accept_source_route=0;
net.ipv4.conf.all.accept_redirects=0;
net.ipv4.conf.default.accept_redirects=0;
net.ipv4.conf.all.secure_redirects=0;
net.ipv4.conf.default.secure_redirects=0;
net.ipv4.udp_rmem_min=6144;
net.ipv4.udp_wmem_min=6144;
net.ipv4.tcp_rfc1337=1;
net.ipv4.ip_no_pmtu_disc=0;
net.ipv4.tcp_ecn=0;
net.ipv4.route.flush=1;
net.ipv4.tcp_rmem='6144 87380 524288';
net.ipv4.tcp_wmem='6144 87380 524288';
net.ipv6.conf.default.use_tempaddr=2;
net.ipv6.conf.all.use_tempaddr=2;
net.ipv6.conf.all.temp_prefered_lft=3600;
net.ipv6.conf.default.temp_prefered_lft=3600;
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;
PureMotive said:
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.
Click to expand...
Click to collapse
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.panic=5
kernel.sched_compat_yield=1
kernel.panic=0
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
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
net.ipv4.tcp_congestion_control=cubic
net.ipv4.tcp_syncookies=1
net.ipv4.conf.all.rp_filter=1
net.ipv4.conf.default.rp_filter=1
net.ipv4.tcp_synack_retries=2
net.ipv4.tcp_syn_retries=2
net.ipv4.tcp_max_syn_backlog=1024
net.ipv4.tcp_max_tw_buckets=16384
net.ipv4.icmp_echo_ignore_all=1
net.ipv4.icmp_ignore_bogus_error_responses=1
net.ipv4.tcp_no_metrics_save=1
net.ipv4.tcp_fin_timeout=15
net.ipv4.tcp_keepalive_intvl=30
net.ipv4.tcp_keepalive_probes=5
net.ipv4.tcp_keepalive_time=1800
net.ipv4.ip_forward=0
net.ipv4.conf.default.accept_source_route=0
net.ipv4.conf.all.accept_source_route=0
net.ipv4.conf.all.accept_redirects=0
net.ipv4.conf.default.accept_redirects=0
net.ipv4.conf.all.secure_redirects=0
net.ipv4.conf.default.secure_redirects=0
net.ipv4.udp_rmem_min=6144
net.ipv4.udp_wmem_min=6144
net.ipv4.tcp_rfc1337=1
net.ipv4.ip_no_pmtu_disc=0
net.ipv4.tcp_ecn=0
net.ipv4.route.flush=1
net.ipv4.tcp_rmem='6144 87380 524288'
net.ipv4.tcp_wmem='6144 87380 524288'
net.ipv6.conf.default.use_tempaddr=2
net.ipv6.conf.all.use_tempaddr=2
net.ipv6.conf.all.temp_prefered_lft=3600
net.ipv6.conf.default.temp_prefered_lft=3600
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.
Step 5
For operating the script enter the following code in terminal emulator
Code:
su
sysctl -p
is all that is really needed to run the script. So here are some more options:
If you think that init.d is being faulty, enter in terminal emulator
Code:
su
sysctl -p
and then
Code:
sysctl -a| grep vm
What this does is manually start up sysctl.conf and then verify it with the succeeding code.​
OR
Ignore what
Code:
sysctl -a| grep vm
is outputting and just see if you experience better battery life (you should)​
----------- For knowledge -----------​
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.
Click to expand...
Click to collapse

Woah.!!
Sent from my GT-S5830 using Tapatalk

Flashable ZIP
Tenfold huh? should give it a try..
EDIT (updated):
Heres a flashable zip to make things a little easier:
Instructions:
1. Reboot to CWM
2. Mount system
3. Flash
DOES IT WORK?
See for yourself
v2-04/30/2012 [without semi-colons of sysctl.conf (refer Step 2) & removed extra lines of 10sysctl (refer step 3)]

pure AWESOMENESS
Sent from my GT-I9100 using xda premium

Is it working. For ace?????
Sent from my GT-S5830 using Tapatalk 2

Anyone comfirm this working?

added to my future rom

Sure.. after 30min from the first post someone definitely will answer if it extends battery life
Let's see who'll be the first to notice that his bettery last longer

Thanks for sharing this
Is it compatible with CM9?

I installed this on my 2.3.6 based ROM and everything is smooth so far. I also ran the supercharger scripts and all 3 had no errors just in case anyone was wondering if they'd conflict with eachother.

/me Flashed,charging Batt ... ->Start
Testing ...edit with notes follows in 24h ...
Thx 4 sharing
(Edit) for me the battery jumps stopped,its more accurate...but i dont have more battery life.
Verstuurd va men ace via Tapatalk

Installed on 2.3.6 based ROM. Everything went smoothly installing. I ran the V6 turbocharger scripts and it didnt cause any errors to come up in case anyone was wondering.
Sent from my VS910 4G using xda premium

Just installed now, on CM9, Beta 8 by the GalaxyICS team.
Currently charging, and I will show a battery life screenie tomorrow and report on the performance

Downloaded, short term testing looks promising, played angry bird for 30mins, that use to drain like 10% battery, now it's only 6%. Not ten fold but still, improvement from just a file, i'll take that any day, this should come standard on all roms now

Does it works on Lewa rom?

Yes i think it was we need It appears to save battery ... Tomorrow i will do full test with full charge

ok installed 5 minutes back on Lk's I two Rom aka cyanogenmod. no problem but I notified a significant change in speed.. phone feels faster. battery backup dropped two percent in 3 minutes of edge usage. ll update this post after 5 hours.. those who want to install do it without fear its installing no bootloops no errors...
thanks for the share
---------- Post added at 08:01 AM ---------- Previous post was at 07:38 AM ----------
kohrangi said:
Does it works on Lewa rom?
Click to expand...
Click to collapse
Yes it works...

Mmm... testing... im at hospital for 2 days without my charger so... It will come handy if works.
Thanks!
Enviado desde el hospital usando Tapatalk con la mano derecha (soy surdo pero tengo suero)

A question, though: is this version of the mod any different from the original? Because the flashable zip of the original mod is bigger than the one posted here. Just curious. Anyway, I'm going to install the original. I'll come back later with answers.

AlterJack said:
A question, though: is this version of the mod any different from the original? Because the flashable zip of the original mod is bigger than the one posted here. Just curious. Anyway, I'm going to install the original. I'll come back later with answers.
Click to expand...
Click to collapse
Files sysctl.conf are the same. Original sysctl.conf contains one empty line at the end of file - that is all.

[Q] how to finetune minfree for Quarx JB 4.1.1 0923 ?

I recently installed quarx JB 4.1.1 0923 image, everything seems fine. But i see that free ram is very low like 50-60mb .
I hv not installed much apps after JB. With cm7.1, i use to see more after 2-3days use(after reboot, i use to see around 100+m after 2-3day of use, its use to be 150+, same apps as installed on JB ). This minfree can be fined tuned, but it get rest to deafult (53mb ??) everytime i reboot. I used minfreemanager to set it, but after every reboot, its back to defaults. tried set at boot, still the same issue. This app sets these settings
echo "2560,4096,5632,10240,11776,24848" > /sys/module/lowmemorykiller/parameters/minfree;
I uninstalled minfreemanager, then tried these settings and put @ /system/etc/init.d/99memtweaks, still after reboot, mimfree are reset to defaults. Tried enabled sys.initd=1(guess i dont need this) in build.prop, no luck.
Anyways to set minfree, want to know wat others try to finetune minfree ?
#!/system/bin/sh
echo "0,1,2,4,7,15" > /sys/module/lowmemorykiller/parameters/adj;
echo "2560,4096,5632,10240,11776,24848" > /sys/module/lowmemorykiller/parameters/minfree;
/system/xbin/sysctl -w vm.swappiness=20;
/system/xbin/sysctl -w vm.vfs_cache_pressure=70;
/system/xbin/sysctl -w vm.dirty_expire_centisecs=3000;
/system/xbin/sysctl -w vm.dirty_writeback_centisecs=500;
#pwm
/system/xbin/sysctl -w vm.dirty_background_ratio=70;
/system/xbin/sysctl -w vm.dirty_ratio=90;
/system/xbin/sysctl -w vm.drop_caches=3;
/system/xbin/sysctl -w vm.min_free_kbytes=4096;

Hi, test supercharger. Its let my jb fly.
Sent from my MB526 using xda premium

[Q] Sim card not found in roms cm9 L3

Hi,
I´m spanish and my sim card of Tuenti Movil don´t be detected for the phone and I haven´t got web but when I introduce the sim card of movistar the phone I have web and detecte it.
When I desactive the pIn code the phone detected the sim and I have got web but I haven´t got 3G.
Help me please.
Sorry for mi bad english.
Here are photos of jellycast V6 that is a rom based on cm9

mjgs17 said:
Hi,
I´m spanish and my sim card of Tuenti Movil don´t be detected for the phone and I haven´t got web but when I introduce the sim card of movistar the phone I have web and detecte it.
When I desactive the pIn code the phone detected the sim and I have got web but I haven´t got 3G.
Help me please.
Sorry for mi bad english.
Here are photos of jellycast V6 that is a rom based on cm9
Click to expand...
Click to collapse
r u using the right baseband (check the version number in about phone eg v10k and confirm it with lg firmware website just google it )if not then U have to flash your home country's or open europe's baseband via Kdz flasher then flash the jellycast...!

Problem
drkingtech said:
r u using the right baseband (check the version number in about phone eg v10k and confirm it with lg firmware website just google it )if not then U have to flash your home country's or open europe's baseband via Kdz flasher then flash the jellycast...!
Click to expand...
Click to collapse
I test many firmwares versions, I test open europe and firmwares of spain and always I have the problem.
The problem is in all roms based on cm9.
Sorry for my bad english

mjgs17 said:
I test many firmwares versions, I test open europe and firmwares of spain and always I have the problem.
The problem is in all roms based on cm9.
Sorry for my bad english
Click to expand...
Click to collapse
seems to be a odd problem did u try crossbreeder?
(this for the 3g btw)
http://forum.xda-developers.com/showthread.php?t=2113150

Problem
drkingtech said:
seems to be a odd problem did u try crossbreeder?
(this for the 3g btw)
http://forum.xda-developers.com/showthread.php?t=2113150
Click to expand...
Click to collapse
Thanks you but I dont understand well that is the crossbreeder my level of english isnt be very well and i dont understand this.

mjgs17 said:
Thanks you but I dont understand well that is the crossbreeder my level of english isnt be very well and i dont understand this.
Click to expand...
Click to collapse
just download cross breeder installer
http://forum.xda-developers.com/attachment.php?attachmentid=2086051&d=1372770386
crossbreeder uninstaller
http://forum.xda-developers.com/attachment.php?attachmentid=2086052&d=1372770386
copy them to the sdcard
go cwm wipe cache/dalvik cache install from sdcard-select the CrossBreeder_7.2.13.zip and flash it
reboot device
open the terminal emulator and type and check the codes given on the page
1. VALIDATION and TROUBLESHOOTING:
You can check your DNS boost functionality by running the following command:
Code:
getprop net.dns1
It should report 0.0.0.0
Then to verify Adblock you can select any one host from the blocked hosts file using the command:
Code:
tail /etc/CrossBreeder/dnrd_root/master
Pick one from there and browse to it in your browser. You should get a blank space
If you're experiencing any issues with your tethering, then you can first try and disable the tethering using:
Code:
su -c /system/etc/CrossBreeder/REMOVE_TETHER_BOOST
and rebooting.
You can re-enable it with:
Code:
su -c /system/etc/CrossBreeder/INSTALL_TETHER_BOOST
and rebooting.
Similarly if you're getting any issues with browser not reaching pages etc. then you can try and disable the entire DNS speedup functionality using:
Code:
su -c /system/etc/CrossBreeder/REMOVE_DNS_CLIENT
and rebooting.
You can re-enable it with:
Code:
su -c /system/etc/CrossBreeder/INSTALL_DNS_CLIENT
and rebooting.
Also of note is the Adblock feature. CrossBreeder now uses it's own Adblock file in /etc/CrossBreeder/dnrd_root/master ( NOTE - CHANGED FROM PREVIOUS VERSION). It also serves up these blocks in a clean blank format so you don't get an ugly 'Page not found' error instead of every ad. This is quite unique. If you want to disable Adblock to save around 3 MB of RAM on low end devices, you can run the command:
Code:
su -c /system/etc/CrossBreeder/DISABLE_ADBLOCK
You can re-enable it with:
Code:
su -c /system/etc/CrossBreeder/ENABLE_ADBLOCK
The biggest improvements are in general usability of apps, both local and network based.
2. You can check your entropy values with this tool:
http://play.google.com/store/apps/de...ndentropyavail
or use this method for more fine grained graphs: http://forum.xda-developers.com/show...php?p=38509664
You should get values moving to 4000 regularly with this mod.
Also of some use is this Lag Test app: Lag Test http://db.tt/eBHYJWYn ( Thanks MW86 ). This is for generally testing the CPU based GUI rendering functionality. The aim is to approach 60 fps, but there isn't a guaranteed correlation with CrossBreeder and your FPS result as of now. It is mostly related to your Governor but CrossBreeder certainly helps.
2. If for some reason, your entropy values aren't hovering around 4096 then the app most probably didn't start automatically. You can try and run it manually using:
Code:
su -c "/system/etc/CrossBreeder/zzCrossBreeder FORCE"
If the entropy values go up to around 4096 and stay there, it's working. CrossBreeder is now in it's separate directory and not dependent on your init.d support. You can make it run automatically on boot using an app like SManager from the Play store, just remember to check both 'BOOT' and 'ROOT' for the execution.
3. If you're still getting issues, you can run the collection script:
Code:
su -c /system/etc/CrossBreeder/CHECK_PROCS
(if it hangs you can close the window and run it again) and post the resultant /data/cb_CHECK_PROCS.log file here in this thread or anywhere else and post here pointing to it please. I will try to find a solution or post a bugfix soon.
You can also disable CrossBreeder if you have any problems using:
Code:
su -c /system/etc/CrossBreeder/DISABLE_CROSSBREEDER
4. If you tried (2) and (3) above and it still doesn't work for you or you would still like to uninstall the mod, then please flash the CrossBreeder_Uninstall.zip.
Click to expand...
Click to collapse
Hope u understand...cant get clearer than this lol..!

Problem
drkingtech said:
just download cross breeder installer
http://forum.xda-developers.com/attachment.php?attachmentid=2086051&d=1372770386
crossbreeder uninstaller
http://forum.xda-developers.com/attachment.php?attachmentid=2086052&d=1372770386
copy them to the sdcard
go cwm wipe cache/dalvik cache install from sdcard-select the CrossBreeder_7.2.13.zip and flash it
reboot device
open the terminal emulator and type and check the codes given on the page
Hope u understand...cant get clearer than this lol..!
Click to expand...
Click to collapse
Thank you I understand this

Random reboot with Redmi 2 [ Custom ROM ]

Hi
I rooted my Redmi 2 and installed CWM recovery then install [ CM 13 ]
it worked with me but had an annoying problem :silly:
the system reboot itself randomly ! every few minutes.
I tried to install another ROM [ Resurrection Remix ] using and didn't work
I tried two different recovery [CWM] and [TWRP] and the problem still happening
What you advise me to do
Please help me
Regards

ObadaKh said:
Hi
I rooted my Redmi 2 and installed CWM recovery then install [ CM 13 ]
it worked with me but had an annoying problem :silly:
the system reboot itself randomly ! every few minutes.
I tried to install another ROM [ Resurrection Remix ] using and didn't work
I tried two different recovery [CWM] and [TWRP] and the problem still happening
What you advise me to do
Please help me
Regards
Click to expand...
Click to collapse
I'm facing a problem almost like that.
Searched a bit, downloaded the kernel log and found that is a kernel panic caused by the modem crashing (Whenever a turn on the mobile data of the SIM card operator X) (No, doesn't matter if it is on slot 1 or 2)
So every time I reboot I gotta quickly disable the mobile data and disable the kernel panic so I can use the phone normally
With your super user terminal
try {
sysctl -w vm.panic_on_oom=0
sysctl -w kernel.panic_on_oops=0
sysctl -w kernel.panic=0
}

Lennoard said:
I'm facing a problem almost like that.
Searched a bit, downloaded the kernel log and found that is a kernel panic caused by the modem crashing (Whenever a turn on the mobile data of the SIM card operator X) (No, doesn't matter if it is on slot 1 or 2)
So every time I reboot I gotta quickly disable the mobile data and disable the kernel panic so I can use the phone normally
With your super user terminal
try {
sysctl -w vm.panic_on_oom=0
sysctl -w kernel.panic_on_oops=0
sysctl -w kernel.panic=0
}
Click to expand...
Click to collapse
Could you please explain how to disable the mobile data and disable the kernel panic ?

ObadaKh said:
Could you please explain how to disable the mobile data and disable the kernel panic ?
Click to expand...
Click to collapse
I'm disabling the mobile data just because it is causing the kernel panic
Soooooo, in order to enable the mobile data safely, I must disable the kernel panic (Which actually does the reboot)
To do so:
Install a terminal emulator (Play Store)
Open it, type su hit enter
Grant root
Type these lines in sequence and hit enter in every
sysctl -w vm.panic_on_oom=0 hit enter
sysctl -w kernel.panic_on_oops=0 hit enter
sysctl -w kernel.panic=0 hit enter
You don't need to reboot.

ObadaKh said:
Could you please explain how to disable the mobile data and disable the kernel panic ?
Click to expand...
Click to collapse
Much simpler method
Download L speed app from playstore
And complete the tutorial
In the tutorial tick advanced options
On the first page u will find disable kernel panic option enable it and done.

My wife's one year old Redmi 2 Prime seems to have developed the same problem as OP's. It reboots randomly. Tried different ROMs numerous times as well as Fastboot flashing clearing everything. Didn't help. Then found this thread and tried L Speed with "disable kernel panic" option enabled. Phone keeps rebooting.
Wife noticed several times that back of the phone got quite hot with no clear reason. She never plays games etc. Just browses the internet on wifi/4G and messaging. I wonder if it's a hardware problem and it's only good for trash bin. Or maybe something can be done with it.

Not found
Lennoard said:
I'm disabling the mobile data just because it is causing the kernel panic
Soooooo, in order to enable the mobile data safely, I must disable the kernel panic (Which actually does the reboot)
To do so:
Install a terminal emulator (Play Store)
Open it, type su hit enter
Grant root
Type these lines in sequence and hit enter in every
sysctl -w vm.panic_on_oom=0 hit enter
sysctl -w kernel.panic_on_oops=0 hit enter
sysctl -w kernel.panic=0 hit enter
You don't need to reboot.
Click to expand...
Click to collapse
Command returns not found each time

Vikasthedevil said:
Command returns not found each time
Click to expand...
Click to collapse
You dont have busybox installed

Install AICP ROM with Gapps arm/7.1/pico

Lennoard said:
I'm disabling the mobile data just because it is causing the kernel panic
Soooooo, in order to enable the mobile data safely, I must disable the kernel panic (Which actually does the reboot)
To do so:
Install a terminal emulator (Play Store)
Open it, type su hit enter
Grant root
Type these lines in sequence and hit enter in every
sysctl -w vm.panic_on_oom=0 hit enter
sysctl -w kernel.panic_on_oops=0 hit enter
sysctl -w kernel.panic=0 hit enter
You don't need to reboot.
Click to expand...
Click to collapse
I tried your method, but the problem still persists. Have flashed many ROMS but same prob.
This Redmi 2 is my daily driver and my only working phone. Pls help me.
Im currently on AEX 3.2
UPDATE: The terminal returned "not found", fixed by installing busybox.
I have entered the commands via adb shell,hope this works
UPDATE: Do I need to repeat same process everytime I reboot? Cos the phone rebooted again today