Develop Bugs

init.d performance startup script

I've adapted the original performance tweaks by 'hardcore' @ XDA for my overclocked/undervolted Galaxy Tab. The tweaked values are pretty much the same as the ones recommended by the original poster, but my simple init.d/ script allows me to log default system values when pushing new values, which is useful for debugging. The script also contains comments to describe the role of each setting. Note that if you don't have init.d/ support in your kernel / initramfs, you can still run the script manually at each system start (use an app like GScript).
Code:
#!/system/bin/sh
#
# Original tweaks by 'hardcore' @ XDA
# http://forum.xda-developers.com/showthread.php?t=813309
# This is a startup script designed for /system/etc/init.d/.
# Note that "run-parts" support (for init.d/ scripts) is normally provided by custom a initramfs,
# which should bundle busybox in /sbin/. The /sbin/run-parts.sh script should take care of
# running init scripts (by calling /sbin/runparts), and it should subsequently trigger
# the device startup (using "setprop filesystem.ready 1", or similar).
# Note that the recovery mode typically doesn't run /system/etc/init.d/ startup scripts.
# Ensure /sbin/busybox takes precedence.
# Normally this is redundant, because the /init.rc startup script already sets the correct path.
export PATH=/sbin:$PATH
# Logging of old/new sysfs values, useful for double-checking.
logFile=/data/local/tmp/S_perf_tweaks.log
if [ -f $logFile ]
then
rm $logFile
fi
touch $logFile
# This function logs the old value and writes the new value.
echo_()
{
echo '' >> $logFile
echo -n "${2}${3} (${1}): " >> $logFile
#head -1 ${2}${3} >> $logFile
#read $firstLine < ${2}${3}
#echo -n $firstLine >> $logFile
contents=`echo -n $(cat ${2}${3})`
echo -n $contents >> $logFile
echo -n " ---> " >> $logFile
echo $1 > ${2}${3}
contents=`echo -n $(cat ${2}${3})`
echo -n $contents >> $logFile
}
# Note that the settings pushed by VoltageControl.apk
# could also be managed here (this only applies to kernels with clock/frequency tables and undervolt sysfs support):
#echo_ "50 50 50 25 25 25 25 " "/sys/devices/system/cpu/cpu0/cpufreq" "/UV_mV_table"
#echo_ 1400000 "/sys/devices/system/cpu/cpu0/cpufreq" "/scaling_max_freq"
echo "---------" >> $logFile
# Remount all partitions that use relatime with noatime and nodiratime instead.
# Note: atime generates a write-after-every-read, relatime is an optimized version of atime.
for k in $(mount | grep relatime | cut -d " " -f3)
do
echo "mount -o remount,noatime,nodiratime $k" >> $logFile
sync
mount -o remount,noatime $k
done
# Here is a sample test to measure read/write performance on rfs partitions:
### test for write: dd if=/dev/zero of=/data/test count=30000
### test for read: dd if=/data/test of=/dev/zero
echo "---------" >> $logFile
# Log the mount table
mount >> $logFile
echo "---------" >> $logFile
# Optimize the cfq/bfq I/O scheduler for flash memory (defaults are designed for spinning harddisks).
# Lower the idle wait, re-enable the low latency mode, remove the penalty for back-seeks,
# and explicitly tell the kernel that the storage is not a spinning disk.
for i in $(ls -1 /sys/block/stl*) $(ls -1 /sys/block/mmc*) $(ls -1 /sys/block/bml*) $(ls -1 -d /sys/block/tfsr*)
#for i in `ls /sys/block/stl* /sys/block/mmc* /sys/block/bml* /sys/block/tfsr*`;
do
# DEF noop anticipatory deadline cfq [bfq]
echo_ "bfq" $i "/queue/scheduler"
# DEF 1 ?
echo_ "0" $i "/queue/rotational"
# DEF 1 ?
echo_ "1" $i "/queue/iosched/low_latency"
# DEF 2 ?
echo_ "1" $i "/queue/iosched/back_seek_penalty"
# DEF 16384 ?
echo_ "1000000000" $i "/queue/iosched/back_seek_max"
# DEF 6 ?
echo_ "3" $i "/queue/iosched/slice_idle"
sync
done
# Set tendency of kernel to swap to minimum, since swap isn't used anyway.
# (swap = move portions of RAM data to disk partition or file, to free-up RAM)
# (a value of 0 means "do not swap unless out of free RAM", a value of 100 means "swap whenever possible")
# (the default is 60 which is okay for normal Linux installations)
# DEF 60
echo_ "0" "/proc/sys/vm" "/swappiness"
# Lower the amount of unwritten write cache to reduce lags when a huge write is required.
# DEF 20
echo_ "10" "/proc/sys/vm" "/dirty_ratio"
# Increase minimum free memory, in theory this should make the kernel less likely to suddenly run out of memory.
# DEF 3102
echo_ "4096" "/proc/sys/vm" "/min_free_kbytes"
# Increase tendency of kernel to keep block-cache to help with slower RFS filesystem.
# DEF 100
echo_ "1000" "/proc/sys/vm" "/vfs_cache_pressure"
# Increase the write flush timeouts to save some battery life.
# DEF 250
echo_ "2000" "/proc/sys/vm" "/dirty_writeback_centisecs"
# DEF 200
echo_ "1000" "/proc/sys/vm" "/dirty_expire_centisecs"
# Make the task scheduler more 'fair' when multiple tasks are running,
# which improves user-interface and application responsiveness.
# DEF 10000000
echo_ "20000000" "/proc/sys/kernel" "/sched_latency_ns"
# DEF 2000000
echo_ "2000000" "/proc/sys/kernel" "/sched_wakeup_granularity_ns"
# DEF 1000000
echo_ "1000000" "/proc/sys/kernel" "/sched_min_granularity_ns"
sync
# Miscellaneous tweaks
setprop dalvik.vm.startheapsize 8m
#setprop wifi.supplicant_scan_interval 90
echo '' >> $logFile
echo "---------" >> $logFile
#This apply a tweaked deadline scheduler to all RFS (and ext2/3/4, if existent) partitions.
#for i in /sys/block/*
#do
# DEF noop anticipatory deadline cfq [bfq]
#echo deadline > $i/queue/scheduler
#echo 4 > $i/queue/iosched/writes_starved
#echo 1 > $i/queue/iosched/fifo_batch
#echo 256 > $i/queue/nr_requests
#done

Thanks for this Daniel - since I know absolutely nothing about anything Android, all I can say is that I have 2 questions
1 - Would this script be any benefit to someone running a custom ROM (Overcome 1.1.3 in my case) and a custom kernel (Richard Trip's 1.4gHz EXT4)? I ask because I don't know if these guys have already including these tweaks or not... but maybe I should ask them instead...
2 - Is there any way you could put that script - in its most efficient, non-debugging form - in to a script file that us speed-freaks can just toss in to init.d and reboot?
Please do forgive me for any newbishness I have displayed here.

So should I put this script in /system/etc/init.d/ ?
UPDATE: Ok, I've done the script(without extension at the back of the file name) and put it in ~/init.d/, it runs well. I comment out the remount and logging function tho Tested it on some games that required load time like gangstar which lags alot previously, now just dnt have any lag time in it! Thanks!
Anyway, im running Overcome rom with richard's kernel, other than voltage script, i saw 2 more script that does the following:
10fixsh does:
"#!/system/bin/sh
busybox mount -o remount,rw /
find /sbin -maxdepth 1 -type l -exec rm {} \;
busybox mount -o remount,ro /
"
99done does:
"#!/system/bin/sh
sync;
setprop mcr.filesystem.ready 1;
"
So I just add your script as userinit since they do not have conflicting calls

Personally thinks that similar tweaks should be included in custom kernels so that those who wish to do more extreme settings can go with it while those who just wants increased performance as it is can still have the boost provided by such init script.

fastcx said:
Personally thinks that similar tweaks should be included in custom kernels so that those who wish to do more extreme settings can go with it while those who just wants increased performance as it is can still have the boost provided by such init script.
Click to expand...
Click to collapse
so basically just copy and paste the whole "code" in the first post, and create it as userinit.sh and put the userinit.sh file in /system/etc/init.d ?
am i right?

kay_kiat88 said:
so basically just copy and paste the whole "code" in the first post, and create it as userinit.sh and put the userinit.sh file in /system/etc/init.d ?
am i right?
Click to expand...
Click to collapse
still need more time to test, after some verification, none of the "/proc/sys/kernel" setting works with any of the kernel i'm using. thats y i need more time to rectify..
used richard's kernel and overcome kernel, both dont do anything now..perhaps wrong command in the script? Cause run-parts.sh does specify where to run script, and init.d does have 2 script in there that runs. So i'll need more time to make sure it works now..
Dont need to have .sh as extension, just a name for your script like the other 2 script that i posted in previous reply. And I did not copy the whole script to run, as the script seems questionable in some part..

fastcx said:
still need more time to test, after some verification, none of the "/proc/sys/kernel" setting works with any of the kernel i'm using. thats y i need more time to rectify..
used richard's kernel and overcome kernel, both dont do anything now..perhaps wrong command in the script? Cause run-parts.sh does specify where to run script, and init.d does have 2 script in there that runs. So i'll need more time to make sure it works now..
Dont need to have .sh as extension, just a name for your script like the other 2 script that i posted in previous reply. And I did not copy the whole script to run, as the script seems questionable in some part..
Click to expand...
Click to collapse
okay.. so basically just copy everything under the "code" and create it as userinit?
edit: hmmm okay thanks for you help. i don't think it's of any use for me now as my tab is quite fast and i don't do any intensive stuff on it. thanks anyway!

kay_kiat88 said:
okay.. so basically just copy everything under the "code" and create it as userinit?
edit: hmmm okay thanks for you help. i don't think it's of any use for me now as my tab is quite fast and i don't do any intensive stuff on it. thanks anyway!
Click to expand...
Click to collapse
Now i'm editing init.rc file instead, but it's not the safest thing to do

Wow all the best.. lol.
Sent from my GT-P1000 using Tapatalk

fastcx said:
Now i'm editing init.rc file instead, but it's not the safest thing to do
Click to expand...
Click to collapse
The init.rc file gets extracted from the initramfs ramdisc (packaged inside the zImage kernel) at each device startup. Changing this file's content is not a good idea. Regards, Dan

fastcx said:
So should I put this script in /system/etc/init.d/ ?
UPDATE: Ok, I've done the script(without extension at the back of the file name) and put it in ~/init.d/, it runs well.
Click to expand...
Click to collapse
Yes, the filename of the startup script must start with "S_" and must not end with ".sh". This is standard Linux stuff.
fastcx said:
find /sbin -maxdepth 1 -type l -exec rm {}
Click to expand...
Click to collapse
Removing the symlinks from "/sbin/" ... why ?
Normally Busybox should be installed properly in "/sbin/" by your kernel provider, you shouldn't have to touch this folder.
fastcx said:
99done does:
"#!/system/bin/sh
sync;
setprop mcr.filesystem.ready 1;
"
Click to expand...
Click to collapse
The "mcr.filesystem.ready" is only relevant if the "init.rc" file in the kernel zImage's initramfs ramdisc responds to a change to the "mcr.filesystem.ready" property (for example, when its value changes from 0 to 1). This is typically used to start the device normally, after *all* of the "/system/etc/init.d/" startup scripts have been executed.
The line of code "setprop mcr.filesystem.ready 1" is therefore typically included in "/sbin/runparts.sh", not in one of the "S_startup_scripts" (as this may trigger the device normal startup prematurely).
It really depends on your kernel, so it should be documented by your kernel provider.

daniel.weck said:
Yes, the filename of the startup script must start with "S_" and must not end with ".sh". This is standard Linux stuff.
It really depends on your kernel, so it should be documented by your kernel provider.
Click to expand...
Click to collapse
Great! thanks for clarifying! Sadly none of the kernel provider states any info on such matter. Will try your script again, as previously running thru gscript not all command works..

Copied your script 100%, put it in init.d with chmod 755, named it S_userinit, doesnt run..i double checked by cat value that I stated to change in the script.
Help? It obviously runs the UV script in init.d tho.
EDIT: Got it to work by editing the UV script, now settings are in! Great! Time to test anyway, nodiratime is not needed, noatime already has it

So how can I use this script - I want to
Hi, Just connected to my galaxy tab running froyo, and went looking in my filesystem for the init.d folder and yeah there isn't one
do i create one? where? and what permissions?
I try to keep this brief and not waste too much of your time.
many thanks for the script
Ttime & effort ++

andytof46 said:
Hi, Just connected to my galaxy tab running froyo, and went looking in my filesystem for the init.d folder and yeah there isn't one
do i create one? where? and what permissions?
I try to keep this brief and not waste too much of your time.
many thanks for the script
Ttime & effort ++
Click to expand...
Click to collapse
you will need a kernel that support init script, after that, /etc/init.d(or /system/etc/init.d) will be created

fastcx said:
Copied your script 100%, put it in init.d with chmod 755, named it S_userinit, doesnt run..i double checked by cat value that I stated to change in the script.
Help? It obviously runs the UV script in init.d tho.
EDIT: Got it to work by editing the UV script, now settings are in! Great! Time to test anyway, nodiratime is not needed, noatime already has it
Click to expand...
Click to collapse
Don't suppose you could post a copy of your trimmed & tweaked version of Daniel's script for us to use?
Cuz I, for example, have no idea what's useful in the original script, and what's not useful. But I at least know how to edit the UV script, heh.

jeebspawnshop said:
Don't suppose you could post a copy of your trimmed & tweaked version of Daniel's script for us to use?
Cuz I, for example, have no idea what's useful in the original script, and what's not useful. But I at least know how to edit the UV script, heh.
Click to expand...
Click to collapse
LOL here it goes
Code:
#!/system/bin/sh
#set UV
echo "0 0 0 0 0 0 0 0 " > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
#select enabled states
echo "0 0 0 0 0 0 0 0 " > /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table
#set scheduler for stl, bml and mmc
for i in `ls /sys/block/stl*` /sys/block/bml* /sys/block/mmcblk*
do
echo "bfq" > $i/queue/scheduler
echo "0" > $i/queue/rotational
echo "1" > $i/queue/iosched/low_latency
echo "1" > $i/queue/iosched/back_seek_penalty
echo "1000000000" > $i/queue/iosched/back_seek_max
echo "3" > $i/queue/iosched/slice_idle
done
# Remount all partitions with noatime
for k in $(busybox mount | grep relatime | cut -d " " -f3)
do
sync
busybox mount -o remount,noatime $k
done
# Tweak kernel VM management
echo "0" > /proc/sys/vm/swappiness
echo "10" > /proc/sys/vm/dirty_ratio
echo "4096" > /proc/sys/vm/min_free_kbytes
# Tweak kernel scheduler, less aggressive settings
echo "18000000" > /proc/sys/kernel/sched_latency_ns
echo "3000000" > /proc/sys/kernel/sched_wakeup_granularity_ns
echo "1500000" > /proc/sys/kernel/sched_min_granularity_ns
# Misc tweaks for battery life
echo "2000" > /proc/sys/vm/dirty_writeback_centisecs
echo "1000" > /proc/sys/vm/dirty_expire_centisecs
# Miscellaneous tweaks
setprop dalvik.vm.startheapsize 8m
done
NOTE: If you change any settings in uv app, u'll revert S_volt_scheduler to ONLY UV settings, so It's recommended to edit your UV setting on this file instead of using uv app from now on if you wants to keep your other settings

Thanks dude!
I hit your Thanks Button too.

jeebspawnshop said:
Thanks dude!
I hit your Thanks Button too.
Click to expand...
Click to collapse
Thanks U should thanks the thread starter too U should just take it as reference, modify any that you feels ok, and perhaps post here as feedback on which makes things better, especially disc scheduler and task scheduler settings.
UPDATE: Made some changes to suggested value by daniel for "fairness", these setting really deals with multitasking better
echo "20000000" > /proc/sys/kernel/sched_latency_ns
echo "2000000" > /proc/sys/kernel/sched_wakeup_granularity_ns
echo "1000000" > /proc/sys/kernel/sched_min_granularity_ns

hey fastcx, i copied and pasted your script in the UV scheduler file in init.d but it seems that it's not working as the values don't apply. any ideas why?

[Q] Modifying Gideonx's OC/UV script

Since my values for the CPU would never stick with System Tuner, I decided to learn how to modify scripts to get the desired effect. I decided that I wanted to modify Gideonx's OC/UV script.
I want to use the GideonX_OC_UV_VM_Tweaked_for_Battery.zip - CPUs @ 384/918Mhz | -75mV | OnDemand | VM tweaked | Not all phones can take -75mV.
Except rather than having a 918Mhz max, I want to use 1.35Ghz max. I heard the script makes your CPU really slow and I'm hoping increasing the max will make it smoother (I don't know too much about this, haha).
I opened up the script with notepad and changed the values from 918000 to 1350000. It now looks like this:
#########################
# GideonX kernel tweaks #
#########################
# Set CPU voltage in microvolts
echo "-75000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
# Set min/max and governor for CPU0
echo 384000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 1350000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
# Set min/max and governor for CPU0
echo 1 > /sys/devices/system/cpu/cpu1/online
echo 384000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
echo 1350000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
echo ondemand > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
# Set kernel dirty data writes. Dirty just means changed data, don't freak out.
# By setting writeout times to be longer, there are less writes which may save more battery for you.
#
# /proc/sys/vm/dirty_expire_centisecs = how old is the data before kernel writes
# /proc/sys/vm/dirty_writeback_centisecs = how often should the kernel check for dirty data
# /proc/sys/vm/dirty_ratio = max memory in percent of data storage
# /proc/sys/vm/dirty_background_ratio = amount of memory in percent for a data writeout to stop
echo "500" > /proc/sys/vm/dirty_expire_centisecs
echo "1000" > /proc/sys/vm/dirty_writeback_centisecs
echo "90" > /proc/sys/vm/dirty_ratio
echo "5" > /proc/sys/vm/dirty_background_ratio
When I zipped it back up and tried to install the zip, however, it crashed and didn't install. What did I do wrong? (Total newbie here)
Link to the script: http://forum.xda-developers.com/showpost.php?p=20946429&postcount=574

bump
Anyone have any idea why it's not working?

The way I did it was by using 7zip and notepad++
I didn't unzip the zip file. I juat openes it qith 7zip and draged the file onto my desktop. Then opened it with notepad++ and made the changes I wanted. After that I just draged that file back into the opened zip closed the program ans flashed it. Maybe the way you zipped it back messed up something.
Sent from my SAMSUNG-SGH-T989 using xda premium

[SOLVED]Ondemand tweaks using init.d scripts

I want to tweak these settings for ondemand(found in sys/devices/system/cpu/cpufreq)
up_threshold
sampling_down_factor
sampling_rate
powersave_bias
To these values:
85
2
50000
1
The defaults
90
4
10000
0
Problem is I don't know what the init.d script is missing for it to work, as it shows errors in script manager. Here's what I have so far:
#!/system/bin/sh
echo 85 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo 2 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor
echo 50000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate
echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias
My question is how do I get the script to work so that on every boot the defaults for ondemand change to those?
What do I have add to the script?
I'm using voltage control btw.
This is for my personal use and experimenting purposes.
Just in case you say "search" I did and when I was doing this, here's the guide I followed:
http://forum.xda-developers.com/showthread.php?t=1369817

[Kernel] CoCore-Z r25

CoCore-Z Kernel for Power Users
POST#1 Introduction & Installation & Credits & Source & Mirror Downloads
POST#2 Notes
POST#3 HOW-TO
POST#4 Change-log
Click to expand...
Click to collapse
I'M IN NO WAY RESPONSIBLE OF ANY DAMAGE CAUSED BY USING THIS CUSTOM KERNEL.
Click to expand...
Click to collapse
Devices: Sony Xperia Z1 C6902/L39h/C6903/C6906
ROM: Stock KitKat 4.4.4 14.4.A.0.108 +
Bootloader: *Unlocked*
Click to expand...
Click to collapse
Features:
Based on Sony 14.4.A.0.133 Opensource
Linaro GCC Toolchain 4.9.3
Sony RIC security module disabled
TWRP Recovery 2.8
Philz Recovery 6
Flash-Friendly-Filesystem (F2FS)
Optimized memutils from MOTO-G
Taiko sound control
UHQA(Ultra High Quality Audio) mode
Louder speaker
Color control (thanks Doomlord)
Vibrator intensity control (thanks Kali-)
Vibrator enable control
Thermel temperturing control
Charger current control
Real EOC (End-of-Charging) LED notification
PowerOn key emulator
Auto readahead according to disk-size
2-ways recording support
Sweep2wake wake-up gesture
Fast random (frandom) module
Some kernel patches from Con Kolivas
Kernel scheduler moire avoided
Unaligned memory access for decompressor
Optimized AES and SHA1 routines
zRAM supported
init.d scripts supported
More IO schedulers
More CPU governors
More and Lower CPU frequencies
CPU VDD control
Android logger disabled by default
For more details please check github source below.
Click to expand...
Click to collapse
Installation:
fastboot:
1. Extract boot.img file from zip package into somewhere
2. Use commands below to flash kernel and reboot
Code:
fastboot flash boot boot.img
fastboot reboot
recovery:
1. You need to have a kernel with custom recovery or installed dual recovery mods.
2. Go recovery and flash the zip in download selection.
dd: (*Not recommended*)
1. Put boot.img somewhere you like
2. Open terminal, `cd` to the folder which has kernel, use the command:
Code:
busybox dd if=boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
Click to expand...
Click to collapse
[Download]
[Mirror Download]
Click to expand...
Click to collapse
Credits:
[MENTION]zwliew[/MENTION]
[MENTION]doomlord[/MENTION]
[MENTION]faux123[/MENTION]
[MENTION]fransicofranco[/MENTION]
Sony for opening kernel source
And many developers for their awesome patches
Click to expand...
Click to collapse
Source code: github
Click to expand...
Click to collapse
XDA:DevDB Information
CoCore-Z, Kernel for the Sony Xperia Z1
Contributors
cocafe, cocafe
Source Code: http://github.com/cocafe/c6902_kernel_CoCore-Z
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: r25
Stable Release Date: 2015-02-25
Created 2014-10-01
Last Updated 2015-02-25

Notes
If the kernel crashed (freezed and rebooted), please fetch last_kmsg file after the crash reboot and post in the thread.
Code:
su -c cat /proc/last_kmsg > /sdcard/last_kmsg
Click to expand...
Click to collapse
Why no overclocking?
1. Overclocking makes phone overheated and SoC will be cooled (use lower frequency) down forcely or it will reboot.
2. We have a fast SoC, it can run most of apps/games smoothly. Like GPU OC, it improves several fps only.
3. So what i need is stable and user experience, instead of improving boring benchmark results.
Click to expand...
Click to collapse
If you flashed other custom kernels before, make sure that wifi modules in /system/lib/modules/pronto
and wifi firmware in /system/etc/firmware/wlan/prima are stock. Or WLAN can not be enabled properly.
Click to expand...
Click to collapse
..

HOW-TO
It's a good idea to use some apps like script manager to put a widget in launcher to execute commands.
Recovery:
When kernel logo displays, PRESS:
- Vol.UP : Philz Recovery
- Vol.DN : TWRP Recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
logger/logcat: If you wanna use logcat, just create a empty file named logger (permission 0777) in /data.
If this file exists, kernel will load logger module during boot.
Click to expand...
Click to collapse
CPU Governors: pegasusq interactive conservative userspace powersave ondemand(default) performance
Click to expand...
Click to collapse
IO schedulers: noop deadline row(default, recommended) cfq bfq fiops sio sioplus zen vr
Click to expand...
Click to collapse
Touch booster:
Our touch booster is implemented in Android level not kernel.
It will lock CPU frequency at 1190MHz and wake up 2 cores when touching.
Disabling it can save battery.
Code:
Edit /system/build.prop and change:
sys.somc.touch_perf_kick=[B]0[/B]
Click to expand...
Click to collapse
Thermal:
On stock kitkat, thermal is using system thermal solution not kernel.
But we can disable it in kernel level, namely, disabling temperature reporting.
Disabling temperature reporting can cause overheated protection (reboot) when SoC is too hot.
Code:
echo 0 > /sys/module/msm8974_tsens/parameters/temp_enable
Click to expand...
Click to collapse
Color control:
Code:
echo R G B > /sys/devices/platform/kcal_ctrl.0/kcal
echo 1 > /sys/devices/platform/kcal_ctrl.0/kcal_ctrl
Or
Code:
echo R G B > /sys/kernel/kcal_color/rgb
echo update > /sys/kernel/kcal_color/rgb
Or
Use compatible kernel app to control the color, or use the system white balance app.
Click to expand...
Click to collapse
POnKey emulator:
Code:
#Using this emulator can simulate power key
#For screen off
echo 10 > /sys/kernel/ponkey/ponkey_emu
#For power menu
echo 600 > /sys/kernel/ponkey/ponkey_emu
Click to expand...
Click to collapse
Taiko sound control:
Headset analog gain:
Code:
#Enable/Disable:
echo on/off > /sys/kernel/wcd9320/hplana_gain
echo on/off > /sys/kernel/wcd9320/hprana_gain
#Gain: Max=0 Default=5 (Lower is louder)
echo 5 > /sys/kernel/wcd9320/hplana_gain
echo 5 > /sys/kernel/wcd9320/hprana_gain
Headset digital gain:
Code:
#Enable/Disable
echo on/off > /sys/kernel/wcd9320/hpldig_gain
echo on/off > /sys/kernel/wcd9320/hprdig_gain
#Gain: Default=0 , Don't set this value too high, 24 is the maximum recommended
echo 16 > /sys/kernel/wcd9320/hpldig_gain
echo 16 > /sys/kernel/wcd9320/hprdig_gain
Speaker on/off:
Code:
#You can turn off speaker only instead of muting all sound in system.
echo off > /sys/kernel/wcd9320/spkdrv
Speaker digital gain:
Code:
#Enable/Disable
echo on/off > /sys/kernel/wcd9320/spkdig_gain
#Do not set this value too high, in order to protect the speaker,
#enabled booster by default
echo 3 > /sys/kernel/wcd9320/spkdig_gain
Headphone UHQA(Ultra High Quality Audio) mode:
UHQA mode allows to have high performance audio, and it's enabled by default.
Have better turn off/on music to switch the amplifier for HPH path.
Code:
#Enable/Disable
echo on/off > /sys/kernel/wcd9320/hph_uhqa
Click to expand...
Click to collapse
Sweep2wake:
This feature allows you to wake up device by sweeping the screen.
But remember, it will keep your device waking, namely, no deep sleep.
Enable/Disable:
Code:
echo on > /sys/kernel/clearpad/sweep2wake
echo off > /sys/kernel/clearpad/sweep2wake
Change wake-up threshold:
Code:
echo threshold_x=??? > /sys/kernel/clearpad/sweep2wake
echo threshold_y=??? > /sys/kernel/clearpad/sweep2wake
S2W LED: (To notice you that S2W is on)
Code:
echo led=0 > /sys/kernel/clearpad/sweep2wake
echo led=1 > /sys/kernel/clearpad/sweep2wake
echo rgb=??? ??? ??? > /sys/kernel/clearpad/sweep2wake
Click to expand...
Click to collapse
Real End-of-Charge notification:
When system UI shows you 100% charged, it might have not been fully charged.
When real EOC reached, charging is actually finished. So let it notice us.
Enable/Disable:
Code:
echo on > /sys/kernel/qpnp-charger/eoc_led
echo off > /sys/kernel/qpnp-charger/eoc_led
Change the color:
Code:
echo led=??? ??? ??? > /sys/kernel/qpnp-charger/eoc_led
Check EOC status (if the LED is changed by other stuffs)
Code:
cat /sys/kernel/qpnp-charger/eoc_led
Click to expand...
Click to collapse
LED Torch:
We can enable and change the torch brightness via sysfs.
Enable/Disable
Code:
echo 2 > /sys/class/misc/pm8941-flash/device/mode
echo 0 > /sys/class/misc/pm8941-flash/device/mode
Change the brightness: (bigger value is brighter)
Code:
echo ?? > /sys/class/misc/pm8941-flash/device/current1
echo ?? > /sys/class/misc/pm8941-flash/device/current2
Click to expand...
Click to collapse
Screen brightness:
We can change the max current of panel to make it night mode or boost the brightness.
Code:
#night mode
echo 1 > /sys/class/leds/wled:backlight/max_current
#boost max brightness
echo 25 > /sys/class/leds/wled:backlight/max_current
Click to expand...
Click to collapse
zRAM:
Using zRAM can compress RAM.
For instance, we compress 600MB RAM here:
Code:
echo $((400 * 1024 * 1024)) > /sys/block/zram0/disksize
mkswap /dev/block/zram0
swapon /dev/block/zram0
Click to expand...
Click to collapse
Vibrator:
Adjust vibrator intensity: ( 0 ~ 31 )
Code:
echo number > /sys/kernel/qpnp-vibrator/vtg_level
Enable/Disable vibrator: ( 0 / 1 )
Code:
echo 0/1 > /sys/kernel/qpnp-vibrator/enable
Click to expand...
Click to collapse
F2FS:
Now userdata partition (/data) supports mounting by F2FS.
F2FS is designed and optimized for nand flash, normally, it is faster than EXT4 filesystem.
A backup in Recovery is recommended!!
Make sure that your SD card has enough space!!
Click to expand...
Click to collapse
Recommended for experienced users, be careful, don't type a wrong partition number.
Click to expand...
Click to collapse
HOW-TO: Make a full backup
Click to expand...
Click to collapse
1. Reboot to recovery, mount external sdcard in mount option. In ADB console:
Code:
[B]
#Mount external sdcard in mount options first
#TWRP external sdcard: /external_sd
#Philz externl sdcard: /storage/sdcard1 [/B]
cd /data
tar -cvf /THE_EXTERNAL_SDCARD_MOUNT_POINT/data-backup.tar *
Be aware that internal storage is in /data, and a TWRP backup of data partition do not include internal storage (/data/media)
Click to expand...
Click to collapse
!!!!Important!!!! Some busybox tar command cannot extract the tarball which is over 2GB.
At least the one in TWRP can not, and I have not replaced it. Recommended covert filesystems in Philz recovery,
Or use the busybox you installed in /system/xbin
Click to expand...
Click to collapse
Anyway, do on your own risk.
Click to expand...
Click to collapse
HOW-TO: EXT4 to F2FS
Click to expand...
Click to collapse
1. Reboot to recovery (I use Philz here), connect to PC, use ADB commands:
2. Mount EXTERNAL SD in mount options, Backup the data partition as a tarball
Code:
cd /data
tar -cvf /storage/sdcard1/data.tar *
3. Now umount /data, we gonna format it (umount all mount points of /dev/block/platform/msm_sdcc.1/by-name/userdata)
Code:
umount /data /sdcard
4. Format the data partition
Code:
cd /dev/block/platform/msm_sdcc.1/by-name
mkfs.f2fs -l userdata userdata
5. Now restore the data tarball
Code:
mount -t f2fs -o rw /dev/block/platform/msm_sdcc.1/by-name/userdata /data
cd /data
tar -xvf /storage/sdcard1/data.tar
umount /data
6. Then reboot system
HOW-TO: F2FS to EXT4
Click to expand...
Click to collapse
1. Reboot to recovery, connect to PC, use ADB commands:
2. Backup the data partition as a tarball
Code:
#[B]Philz recovery cannot mount f2fs automatically, we need to mount it manually[/B]
[B]mount -t f2fs -o rw /dev/block/platform/msm_sdcc.1/by-name/userdata /data[/B]
cd /data
tar -cvf /storage/sdcard1/data.tar *
3. Now umount /data, we gonna format it (umount all mount points of /dev/block/platform/msm_sdcc.1/by-name/userdata)
Code:
umount /data /sdcard
4. Format the userdata partition
Code:
mke2fs -T ext4 -L userdata /dev/block/platform/msm_sdcc.1/by-name/userdata
5. Mount the userdata partition, and restore the data tarball
Code:
mount -t ext4 -o rw /dev/block/platform/msm_sdcc.1/by-name/userdata /data
cd /data
tar -xvf /storage/sdcard1/data.tar
umount /data
6. Reboot system
When kernel logo displays, press camera-shot key to check filesystem manually.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
CPU VDD Control
Click to expand...
Click to collapse
In /sys/kernel/krait_vdd, you can adjust krait voltage table by commands:
Code:
echo +5mV > /sys/kernel/krait_vdd/krait_uV
Code:
echo -5mV > /sys/kernel/krait_vdd/krait_uV
Code:
echo +10mV > /sys/kernel/krait_vdd/krait_uV
Code:
echo -10mV > /sys/kernel/krait_vdd/krait_uV
* The number needs to be multiplier of 5.
* Lower or higher voltage might cause unstable.
* Do it on your own risk.
Click to expand...
Click to collapse

Change-log
For more, please check github commits history.
2015-02-25 - r25
- Adjusted ondemand governor to fix heating issue
- Built with Linaro 2015.01 toolchain
Click to expand...
Click to collapse
2015-02-14 - r24
- Added, optimized CPU governors
- Allowed to set all CPU governors during start-up
- Added CPU VDD control
- Under clocked 192MHz
- Adjusted CPU frequency table
Click to expand...
Click to collapse
2015-01-13 - r20
- F2FS
- Add Philz recovery
- BFQ v7r7
- Reduced Krait CPU retention voltage
- Optimzed Low memory allocator
Click to expand...
Click to collapse
2014-11-02 - r16
- Applied upstream patches for wcd9320
- Taiko control r02
- Disabled low power mode for headphone path
- Enabled UHQA mode for headphone
- Some fixes about writeback
- Disabled 268MHz (as it can make audio choppy), undervolted 300MHz 25mV
- Updated BFQ io scheduler
- And some other patches about network and memory management
Click to expand...
Click to collapse
2014-10-08 - r14
- Removed memutils
- Fixed Android logger
- Added more cpufreq steps
Click to expand...
Click to collapse
2014-10-01 - r12
Initial release
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Reserved

I just say Wow..
Any plans for CM support?

What does the power button emulation do? And does threshold adjust the length of sweep?
Awesome work, man, good to see new development for the Z1!

Awesome. So much detail put into this. Good work!

abbychauhan said:
I just say Wow..
Any plans for CM support?
Click to expand...
Click to collapse
Maybe in the future, currently, i am using stock rom.
AnrgKrshn said:
What does the power button emulation do? And does threshold adjust the length of sweep?
Awesome work, man, good to see new development for the Z1!
Click to expand...
Click to collapse
Emulator allows you to turn off screen and get power menu by tapping the script widget on the launcher.
As we know, the power key is the most busiest hardware key of our device. I wanna save its life.
Yep, threshold adjust the range of waking up.
LeParkour012 said:
Awesome. So much detail put into this. Good work!
Click to expand...
Click to collapse
Thanks.

@cocafe thanks for your work
Possibility to add gamma control or contrast control on you kernel?

Is Fauxclock compatible with this kernel? Or something else? Terminal/init is unconfortable when I wanna change some settings.

cocafe said:
For more, please check github commits history.
Click to expand...
Click to collapse
Is this kernel performance or battery tuned?

How can I set sound control setting on boot? init.d can't.

RyTekk said:
Is Fauxclock compatible with this kernel? Or something else? Terminal/init is unconfortable when I wanna change some settings.
Click to expand...
Click to collapse
Dunno, never used such stuff, i liking writing shell scripts and putting them in launcher.
Destroyedbeauty said:
Is this kernel performance or battery tuned?
Click to expand...
Click to collapse
In fact, i have restarted the kernel. Several months ago i added some battery saving mods, like 268Mhz and UV...
But removed now, will test and add later.
RyTekk said:
How can I set sound control setting on boot? init.d can't.
Click to expand...
Click to collapse
Init.d is supported. Check /system/etc/init.d (this folder exists?) and scripts permissions

cocafe said:
Dunno, never used such stuff, i liking writing shell scripts and putting them in launcher.
Init.d is supported. Check /system/etc/init.d (this folder exists?) and scripts permissions
Click to expand...
Click to collapse
init.d is supported, yes, but I wrote an init.d scripts and set 755 perm but it can't set. Am I wrong?
#!/system/bin/sh
#Headset analog gain:
#Enable/Disable:
echo on > /sys/kernel/wcd9320/hplanagain
echo on > /sys/kernel/wcd9320/hpranagain
#Gain: Max=5 Default=0
echo 5 > /sys/kernel/wcd9320/hplanagain
echo 5 > /sys/kernel/wcd9320/hpranagain
#Headset digital gain:
#Enable/Disable
echo on > /sys/kernel/wcd9320/hpldiggain
echo on > /sys/kernel/wcd9320/hprdiggain
#Gain: Default=0 , Don't set this value too high, 24 is the maximum recommended
echo 8 > /sys/kernel/wcd9320/hpldiggain
echo 8 > /sys/kernel/wcd9320/hprdiggain
#Speaker on/off:
#You can turn off speaker only instead of muting all sound in system.
#echo off > /sys/kernel/wcd9320/spkdrv
#Speaker digital gain:
#Enable/Disable
echo on > /sys/kernel/wcd9320/spkdiggain
#Do not set this value too high, in order to protect the speaker,
#enabled booster by default
echo 2 > /sys/kernel/wcd9320/spkdiggain
Click to expand...
Click to collapse

RyTekk said:
init.d is supported, yes, but I wrote an init.d scripts and set 755 perm but it can't set. Am I wrong?
[QUOTE#!/system/bin/sh
#Headset analog gain:
#Enable/Disable:
echo on > /sys/kernel/wcd9320/hplanagain
echo on > /sys/kernel/wcd9320/hpranagain
#Gain: Max=5 Default=0
echo 5 > /sys/kernel/wcd9320/hplanagain
echo 5 > /sys/kernel/wcd9320/hpranagain
#Headset digital gain:
#Enable/Disable
echo on > /sys/kernel/wcd9320/hpldiggain
echo on > /sys/kernel/wcd9320/hprdiggain
#Gain: Default=0 , Don't set this value too high, 24 is the maximum recommended
echo 8 > /sys/kernel/wcd9320/hpldiggain
echo 8 > /sys/kernel/wcd9320/hprdiggain
#Speaker on/off:
#You can turn off speaker only instead of muting all sound in system.
#echo off > /sys/kernel/wcd9320/spkdrv
#Speaker digital gain:
#Enable/Disable
echo on > /sys/kernel/wcd9320/spkdiggain
#Do not set this value too high, in order to protect the speaker,
#enabled booster by default
echo 2 > /sys/kernel/wcd9320/spkdiggain
]
Click to expand...
Click to collapse
[/QUOTE]
You should execute the script in terminal to debug...
su
cd /etc/init.d
sh YOUR_SCRIPT
See what will terminal say

cocafe said:
You should execute the script in terminal to debug...
su
cd /etc/init.d
sh YOUR_SCRIPT
See what will terminal say
Click to expand...
Click to collapse

RyTekk said:
Click to expand...
Click to collapse
I can not check your pic clearly.
And excuse me, my Z1 is not available now... (i am unable to use it until several days later)

cocafe said:
I can not check your pic clearly.
And excuse me, my Z1 is not available now... (i am unable to use it until several days later)
Click to expand...
Click to collapse
Sr, I have reuploaded the full-size photo that you can check clearly.

Sorry, but where is the download link

Skinny Pro Custom Boot Images

What is Skinny Pro?
This is not for NOOBS - it breaks functionality in Xiaomi apps that try to communicate back to head office. This is an intentional feature and is for people who are not interested in being part of the Xiaomi ecosphere. LEAVE NOW if you have, or intend to log on to Xiaomi and use their services!!!!
Skinny does not magically fix poor choice of ROMs, Apps or lack of knowledge.
It is not a custom Kernel - it is a custom boot.img containing modified initialization scripts for the stock kernel.
There are 2 distinct versions:
Based on 7.1.4.0 - Use for 7.1.xx to 7.3.20 (MIUI7) Support discontinued since V7 (O.P no longer applies to this version)
Based on MIUI8 - use for MIUI7.5.x and MIUI8
Design Brief:
No Placebos
To overcome the limitations of Stock MIUI being:
Poor battery life
Poor performance
Chronic invasion of privacy
Boot.img mods:
Disable starting of non-present devices and services
Disable stock recovery overwriting TWRP
Disable OTA services (no use on a modified ROM)
Disable starting of invasive (spying) services
Disable fingerprint sensor infrastructure (not for our device)
Disable find device infrastructure
Disable second space infrastructure
Build in init.d support
Enable zram swap creation (disable conflicting "mcd" service infrastructure)
Mass Storage Device mode added for external SDCard
Improved TCP Buffer values
Reconfigured internal SDCard suppport to remove uneccessary symlinks
Reduce cpu scheduler, foreground and background tasks deadtime (throttling)
Add some Android 6.0 TCP tweaks
Expose LMK and HPS settings for user configuration
What you will see:
Faster boot
Less background activity at idle
Less RAM usage
Less spying/reporting activity
Better battery life
Better Performance
More reliable and faster data speeds
Install your chosen ROM and get it past the first setup screens before flashing a Skinny Boot image.
If you really must install Xposed, install this after the Skinny boot image.
Do not install "kernel" tweaking apps - they will conflict with the inherent settings in Skinny!
No wipes are necessary after installing the boot.img
What else do I need to do?
First, an explanation as to why we need to set everything the way it is:
The cpu is controlled by 4 separate mechanisms:
1. Thermal throttling - will limit frequencies and shut down cores to stay within safe operating temperatures - will override all other mechanisms. Settings available: High Performance (less strict) or Balanced (default)
2. Performance Server - will temporarily boost freqs and cores depending on detected conditions such as screen touch, screen update or rotate, app open. Limited settings available via /etc/perfservscntbl.txt
3. Hotplugging Service - will add or remove cpu cores as load requires. Some settings are accessible through /proc/hps/
4. Interactive Governor - will throttle freqs up and down based on load and add or remove cores also. Some settings are accessible through /sys/devices/system/cpu/cpufreq/interactive/
You will notice there are competing and often contradicting mechanisms. The factory defaults essentially disable the Interactive governor as being the primary source of initial boosting cpu freqs. The "boost" setting normally found in the governor is non-functional - instead, the Perf Server will boost to 2 cores @ 1183MHz when a potential demand for processing power is detected apart from a simple screen touch. The interactive governor will take over scaling the freq and number of cores after the perf server boost period expires or load demands more cpu power than the boost caters for.
Since the Performance Server tends to over-react, setting 2 cores @ 1183MHz for the smallest of events, we disable it completely by manually editing the existing line in /system/build.prop from:
ro.mtk_perfservice_support=1 to ro.mtk_perfservice_support=0
You must do this yourself - this is vital since all further Governor and Hotplug settings rely upon it being disabled.
Editing /etc/perfservscntbl.txt is not required since this file will no longer be processed.
The settings for the Interactive Governor and Hotplug are modified from factory default to correct a couple of serious problems:
1. The cpu will not reliably throttle back to idle at 403MHz. This has a huge impact on battery.
This is caused by the timer_rate setting being too short allowing transient background activities to trigger scaling the freq up. Increasing the time effectively averages out the transient load spikes so the cpu will not break idle unnecessarily.
2. The cpu does not respond to increasing or decreasing load fast enough creating micro-lags and consuming battery. Reducing the min_sample_time will shorten the time taken for the cpu to lower in freq when load drops off. Reducing the above_hispeed_delay will reduce the response time to increase the cpu freq in response to a load. Both of these settings also compensate for the longer than standard timer_rate that introduces some sluggishness by necessity.
All other values are set to encourage the frequency and number of cores to rapidly and reliably return to idle to save battery while still providing sufficient responsiveness to sudden load demands.
Create an init.d script exactly as follows: (premade file 01_init also available to download)
Code:
#!/system/bin/sh
### CPU freqs standard RN2: 403000, 806000, 1183000, 1326000, 1469000, 1625000, 1781000, 1950000
### CPU freqs PRIME RN2: 403000, 806000, 1183000, 1326000, 1482000, 1664000, 1885000, 2158000
### GPU freqs standard RN2: 253500, 299000, 390000, 442000, 546000
### GPU freqs PRIME RN2: 253500, 338000, 390000, 546000, 676000
# Stop running boot-time services (enable the lines for services you want to stop)
#stop sn # USB serial number allocation
#stop wifi2agps # WiFi assisted GPS (for fine location)
#stop agpsd # Mobile Network assisted GPS (for fine locastion)
#stop emsvr_user # Engineering Mode server
#stop PPLAgent # Privacy Protection Lock
#stop mtkbt # MTK Bluetooth
#stop batterywarning # Battery warning service
#stop debuggerd64 # debug logging
#stop debuggerd # debug logging
#stop logd # logging
#stop autokd # autotune for WiFi
#Set to permissive (enable this line if SE permissive mode is required)
# setenforce 0
# Tweak Interactive Governor (now set in boot.img - enable here to override values)
#echo 403000 > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq # factory default 1183000
#echo 99 > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load # factory default 99
#echo 99 > /sys/devices/system/cpu/cpufreq/interactive/target_loads # factory default 90
#echo 25000 > /sys/devices/system/cpu/cpufreq/interactive/timer_rate # factory default 20000
#echo 10000 > /sys/devices/system/cpu/cpufreq/interactive/min_sample_time # factory default 20000
#echo 5000 > /sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay # factory default 20000
#echo 40000 > /sys/devices/system/cpu/cpufreq/interactive/timer_slack # factory default 80000
# Limit CPU max freqs (To limit the maximum cpu freq, enable both of these lines. Select a valid freq for your device from table at start)
#echo 1781000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
#echo 1781000 > /proc/cpufreq/cpufreq_limited_max_freq_by_user
# Limit foreground CPU cores (set in boot.img - enable here to override values) 0-1 min, 0-7 max Example shows 5 cores (also needs to be set in Hotplug)
#echo 0-4 > /dev/cpuset/foreground/cpus
# Hotplug settings (set in boot.img - enable here to override values) Note: num_limit values are 1-8
#echo 5 > /proc/hps/num_limit_low_battery # factory default 8
#echo 5 > /proc/hps/num_limit_power_serv # factory default 8
#echo 5 > /proc/hps/num_limit_thermal # factory default 8
#echo 5 > /proc/hps/num_limit_ultra_power_saving # factory default 8
#echo 99 > /proc/hps/up_threshold # factory default 95
#echo 87 > /proc/hps/down_threshold # factory default 85
#echo 0 > /proc/hps/rush_boost_enabled # factory default 1
#echo 0 > /proc/hps/input_boost_enabled # factory default 1
# Tweak GPU Settings (Look in /proc/gpufreq/gpufreq_power_dump for power usage at different freqs)
# To disable GPU touch boost:
#echo 0 > /proc/gpufreq/gpufreq_input_boost # factory default 1 (enabled)
# To limit max GPU freq: (Select a valid freq for your device from table at start)
#echo 442000 > /proc/gpufreq/gpufreq_opp_max_freq # factory default 0 (disabled)
# Tweak VM (set in boot.img - enable here to override values)
#echo 300 > /proc/sys/vm/dirty_expire_centisecs # factory default 200
#echo 500 > /proc/sys/vm/dirty_writeback_centisecs # factory default 300
# Tweak LMK (set in boot.img - enable here to override values) 18 37 56 75 93 112MB # factory default 72 90 108 126 219 317MB (MB x 256 = value)
#echo 4608,9472,14336,19200,23808,28672 > /sys/module/lowmemorykiller/parameters/minfree
#Enable zram (no zram set by default, enable first 4 lines if 1 zram required, all 7 lines if 2 zram required)
#echo 40 > /proc/sys/vm/swappiness
#echo 268435456 > /sys/block/zram0/disksize # for single zram: 536870912 = 512MB (for non-prime version) 1073741824=1GB (for prime version)
#/system/xbin/busybox mkswap /dev/block/zram0
#/system/xbin/busybox swapon /dev/block/zram0
#echo 268435456 > /sys/block/zram1/disksize # for 2 zrams: 268435456 = 256MB (for non-prime version) 536870912 = 512MB (for prime version)
#/system/xbin/busybox mkswap /dev/block/zram1
#/system/xbin/busybox swapon /dev/block/zram1
# Tweak IO Scheduler (set in boot.img - enable here to override values)
#echo deadline > /sys/block/mmcblk0/queue/scheduler # factory default cfq (choice: noop deadline cfq)
#echo 128 > /sys/block/mmcblk0/queue/read_ahead_kb # factory default 128 Choose between 128, 256, 512, 1024, 2048
#echo 0 > /sys/block/mmcblk0/queue/add_random # factory default 1
#echo 0 > /sys/block/mmcblk0/queue/iostats # factory default 1
#echo deadline > /sys/block/mmcblk1/queue/scheduler # for ext sdcard (sdcard1)
#echo 2048 > /sys/block/mmcblk1/queue/read_ahead_kb # for ext sdcard (sdcard1)
#echo 0 > /sys/block/mmcblk1/queue/add_random # for ext sdcard (sdcard1)
#echo 0 > /sys/block/mmcblk1/queue/iostats # for ext sdcard (sdcard1)
#Tweak Entropy (set in boot.img - enable here to override values)
#echo 384 > /proc/sys/kernel/random/read_wakeup_threshold # factory default 64
#echo 448 > /proc/sys/kernel/random/write_wakeup_threshold # factory default 128
#Tweak for wifi router connection issues
#echo 1 > /proc/sys/net/ipv6/conf/wlan0/disable_ipv6
# Disable debugging on some modules (set in boot.img - enable here to override values)
#echo 0 > /sys/module/alarm_dev/parameters/debug_mask;
#echo 0 > /sys/module/alarmtimer/parameters/debug_mask;
#echo 0 > /sys/module/binder/parameters/debug_mask;
#echo 0 > /sys/module/earlysuspend/parameters/debug_mask;
#echo 0 > /sys/module/sbsuspend/parameters/sbsuspend_debug_mask;
#echo 0 > /sys/module/snd/parameters/debug;
#echo 0 > /sys/module/pvrsrvkm/parameters/gPVRDebugLevel;
#echo 0 > /sys/module/musb_hdrc/parameters/debug_level;
#echo 0 > /sys/module/lowmemorykiller/parameters/debug_level;
#FSTRIM
busybox fstrim /data
busybox fstrim /system
busybox fstrim /cache
Update BusyBox to version 1.25.1-1 (available to download)
Reduce the number of apps and services needlessly starting automatically at boot. Uninstall or freeze bloat apps. Replace "noisy" apps with better written ones.
Use BetterBatteryStats, WakelockDetector Root or similar to understand what invisible activities are consuming battery.
Use SDMaid, DisableServices, MyAndroidTools or similar to disable autostarts (receivers)and app related services. Use with caution.
To see what boot services are running, type getprop in Terminal. You will see a bunch of entries like [init.svc.66xx_launcher]: [running]
These service must remain running do not stop!:
Code:
[init.svc.66xx_launcher]: [running]
[init.svc.MtkCodecService]: [running]
[init.svc.NvRAMAgent]: [running]
[init.svc.aal]: [running]
[init.svc.ccci_fsd]: [running]
[init.svc.ccci_mdinit]: [running]
[init.svc.drm]: [running]
[init.svc.fuelgauged]: [running]
[init.svc.gsm0710muxd]: [running]
[init.svc.guiext-server]: [running]
[init.svc.healthd]: [running]
[init.svc.installd]: [running]
[init.svc.keystore]: [running]
[init.svc.lmkd]: [running]
[init.svc.media]: [running]
[init.svc.mnld]: [running]
[init.svc.netd]: [running]
[init.svc.ril-daemon-mtk]: [running]
[init.svc.sdcard]: [running]
[init.svc.servicemanager]: [running]
[init.svc.shelld]: [running]
[init.svc.surfaceflinger]: [running]
[init.svc.thermal]: [running]
[init.svc.thermald]: [running]
[init.svc.ueventd]: [running]
[init.svc.vold]: [running]
[init.svc.zygote]: [running]
[init.svc.zygote_secondary]: [running]
[init.svc.bmi160d]: [running]
If you only have 1 SIM, it is highly recommended to go into single SIM mode to turn off the second modem service. Edit build.prop existing line from:
persist.radio.multisim.config=dsds to persist.radio.multisim.config=ss
Turn off Developer Options/Memory Optimization and MIUI Optimization. This is a legacy of the mcd service zram configuration that is disabled.
Removal of Apps that are created by symlinks: (Updated information for any ROM version can be found in ROM \META-INF\com\google\android\updater-script)
Uninstall the app where possible and then delete the leftover libs if they exist.
Code:
[B]MAB[/B]
/system/lib/libDToken.so
/system/lib/libNative.so
/system/lib/libShopSigned.so
/system/lib/libentryexpro.so
/system/lib/libsecuritysdk-3.1.27.so
[B]Jeejen[/B]
/system/lib/libJeejenAisound.so
/system/lib/libbspatch.so
/system/lib/libfamily_jni.so
/system/lib/libgetuiext.so
/system/lib/libjeejenmsc.so
[B]MIUI Video[/B]
/system/lib/libDecRes_sdk.so
/system/lib/libminivenus.so
/system/lib/libmresearch.so
/system/lib/libsecurities_sdk.so
[B]Cleanmaster[/B]
/system/lib/libTmsdk-2.0.9-mfr.so
/system/lib64/libTmsdk-2.0.9-mfr.so
/system/lib/libdce-1.1.14-mfr.so
/system/lib64/libdce-1.1.14-mfr.so
/system/lib/libkcmutil.so
/system/lib/libkcmutilex.so
/system/lib/libsic_helper.so
[B]SecondSpace[/B]
/system/lib/libspaces_jni.so
[B]Sogou Input[/B]
/system/lib/libwebp.so
/system/lib/libweibosdkcore_sogou.so
[B]AMAP Network Location[/B]
/system/lib64/libapssdk.so
[B]YellowPage[/B]
/system/lib64/libdidi_secure.so
[B]XMPass[/B]
/system/lib64/libxmpass_sdk_patcher.so
/system/lib64/xmpass_libweibosdkcore.so
[B]PicoTTS[/B]
/system/lib64/libttscompat.so
/system/lib64/libttspico.so
[B]Miui Gallery[/B]
/system/lib64/libwrapnexpcmcalbody.so
/system/lib64/libnexralbody_audio.so
/system/lib64/libnexcralbody_mc_jb.so
/system/lib64/libnexeditorsdk.so
/system/lib64/libPinguoImageSDK.so
/system/lib64/libMiuiGalleryNSGIF.so
/system/lib/libMiuiGalleryNSGIF.so
/system/lib64/libDexHelper.so
[B]MIUI Scanner[/B]
/system/lib64/libQuadrangleRecognizer.so
/system/lib64/libhw_instanttrans.so
/system/lib64/libhwocr_cntools_shared.so
/system/lib64/libsgmain.so
/system/lib64/libsgmainso-5.1.2011.so
/system/lib64/libtbdecode.so
Remove inbuilt virus scanner(s)
Remove GuardProvider.apk and SecurityAdd.apk plus:
Code:
/system/lib64/libams-1.1.7-m-mfr.so
/system/lib64/libams-1.1.7-mfr.so
/system/lib64/libavast-utils.so
/system/lib64/libavast-vps-interface.so
/system/lib64/libavlasys.so
/system/lib64/libavlm.so
/system/lib64/libavlurl.so
Extra libs that can be removed: (if associated apps are removed)
Code:
[B]Lib:[/B]
libfdpp.so Find Device
libfdpp_jni.so Find Device
libffmpeg-miplayer.so Music / MIUIVideo
libhotknot.so
libhotknot_vendor.so
libnfc_ndef.so
libpatcher_game_jni.so
libpatcher_jni.so
libvoicerecognition.so Voice Extensions
libvoicerecognition_jni.so Voice Extensions
libwhetstone_jni.so
libwhetstone_sdk.so
libxiaomimediaplayer.so Music / MIUIVideo
libxiaomiplayerwrapper.so Music / MIUIVideo
[B]Lib64:[/B]
libBaiduMapSDK_base_v4_0_0.so
libBaiduMapSDK_search_v4_0_0.so
libBaiduMapSDK_util_v4_0_0.so
libBankCardRecognizer.so
libduokantext.so
libfdpp.so Find Device
libfdpp_jni.so Find Device
libhotknot.so
libhotknot_vendor.so
libidcardquality_v1.0.3.so
libjni_latinimegoogle.so Google Keyboard
libjni_pacprocessor.so
libjni_unbundled_latinimegoogle.so Stock Keyboard
libnfc_ndef.so
libpatcher_game_jni.so
libpatcher_jni.so
libprintspooler_jni.so Print Spooler
libtbtv3312.so
libTrafficRadar.so
libttscompat.so Pico TTS
libttspico.so Pico TTS
libunipaychsec.so
libweibosdkcore.so
libwhetstone_jni.so
libwhetstone_sdk.so
[B]/vendor/lib64:[/B]
libcom_fingerprints_productiontestmanager.so
libcom_fingerprints_sensor.so
Skinny Pro All versions:
https://drive.google.com/folderview?id=0BwdRTuyj12_yRk9Kcm1pZkxuZzg&usp=sharing
Enjoy

@jajk Awesome work! Do you intend to work on the aosp boot.img much or are you more invested in the miui one (or is it mostly the same project with not many differences between the two types)?

@Sleepy_Augie There is little difference between the 2 flavors so it is easy to keep them in sync
All,
I cannot possibly know what customization other devs are adding to their boot.imgs and whether or not that will make their ROMs incompatible with my boot.imgs. I will try to keep the AOSP version up with current developments while still keeping it "Generic".

Could you include Selinux: Permissive? Zram is better than swap built-in miui ?

@efr07 The beauty of not embedding tweaks - you can choose to be permissive or enforcing in your init.d script rather than me dictating it to all.
setenforce=0 or 1
and to answer the second part....
MIUI uses what could be called a "dynamic swap" system utilizing 4 zram swaps of variable size. The system prioritizes what gets access to that extra memory and what doesn't. No surprises - Xiaomi apps get priority over your own apps. The complexity of this system is so great, it would negate any performance advantage completely but it does make the Xiaomi apps more tenacious than other apps.

@jajk
First things first thank you so much for the effort you have done improving Redmi Note 2,
But I have some question if you please,
I have Miui 7.2.2.0 Lite on my Redmi Note 2 Prime (2.2 ghz) (Rom Link http://en.miui.com/thread-244684-1-1.html)
I have flashed the file as img to boot, and I have done as you said until the int.d thing, I went to #/system/bin/ and I found sh file and opened it in text editor, deleted everything in it and paste what you mentioned, till now we are ok with the device.
I did not find the files that you said I should delete from /vendor/lib, so I went to /vendor/lib64 and deleted the first file, After I deleted it suddenly Root Explorer shut off and whenever I open it again I cant find anything, just blank screen with its symbol and name above and nothing else. Tried to delete Root Explorer and install again and nothing new. Please help, Have I done everything okay? and what should I do to fix this thing and continue deleting the remaining files?
Thank you.

@jajk delete folder /system/etc/radv <- do you mean radvd?

@aghr11 I think that you did not understand the method to create the init.d script and modified an important file instead. You will have to replace that script file you blanked with the original or restore from a good backup and try again. The list of files for deletion is only if they exist in the location as described. If you have enabled any fingerprint settings for some obscure reason, you will probably get locked out of your phone.
Now to creating the script.
Using a text editor, create a file named 01tweaks in /system/etc/init.d folder.
Paste the text (including the first line #!/system/bin/sh) into this file. Leave a blank line at the bottom of the file and make sure your editor is set to Unix end-of-line characters (not Windows)
Save the file and give it 0755 permissions (rwxr-xr-x)
@tonydeli7 Yes, typo I will fix..... done It is a folder to receive advertising pushed to your phone courtesy of Xiaomi!!!!

jajk said:
@tonydeli7 Yes, typo I will fix..... done It is a folder to receive advertising pushed to your phone courtesy of Xiaomi!!!!
Click to expand...
Click to collapse
Yeap, just saw the conf file... WTF are they doing?!
By the way, thanks a lot for this kernel! Nice work!:good::good:
UPDATE:
I edited the latest Multirom Stable (7.2.1.0) and added your kernel&tweaks,deleted the files and everything works great!
I only changed the touchboost value to 806000

jajk, many thanks for this brilliant work!
IIRC, your personal preference for a base ROM with the best behavior and performance with these tweaks was v7.1.4.0 (or was it 7.1.3.0). Is this so or has anything changed? My RN2p is long overdue for an update, still on dev 5.10.29!

If a have a weekly miui based on Miui V 7.3 beta, will it work?

@tonydeli7 Did you give it some time on touchboost 403? I find it does not contribute to lags perceptibly.
@algida79 The most bug free ROM I have come across is MR7.2.30 ID (ported from reno3). I think I had a link to that in the Skinny thread.
Don't load the preloader, uboot or logo from this ROM - edit the updater-script to remove flashing of these. You will need to do an intermediate flash of 7.1.3 or 7.1.4 using SP Flash tool to get all the partitions the way they need to be if coming from an ancient ROM.
@Dnxss Yes it will still work.

@jajk Half an hour I think. I had no lag,just my preference
The phone usage is mostly surfing,facebook,twitter,music playback etc etc with no gaming.
GPS SYNC 3G all on..
Installed app count is around 120..
Includes six reboots while testing ZRAM(disabled it), and if it's good to deactivate Whetstone app.
I also used the app Autostarts to disable useless receivers for many apps like FB etc,and disabled Mail,Voice Unlock,PicoTTS.
I am satisfied..[emoji14]
Sent from my Redmi Note 2 using Tapatalk

@tonydeli7 Whetstone app is a source of a lot of spyware but is not a straight forward removal but you will find that out...
can then also delete:
/etc/WhetstonePermission folder
/system/lib
libwhetstone_jni.so
libwhetstone_sdk.so
/system/lib64
libwhetstone_jni.so
libwhetstone_sdk.so

Yeap, I searched a bit. I am using the Multirom Stable and after flashing the kernel,Whetstone crashes sometimes.
Didn't notice anything weird after freezing it..
This rom doesn't have the line
persist.sys.whetstone.level=2
in the build.prop for some reason.
Sent from my Redmi Note 2 using Tapatalk

@tonydeli7 Whetstone is linked to the mcd service to make things harder to unravel as in all Xiaomi apps. The boot.img disables mcd which is why you will see Whetsone having a fit sometimes. Completely removing Whetstone is a very good thing to do - it may give you an FC on Battery app, delete that too - it chews battery and does not affect normal operation!!!
Anyone wanting to increase their privacy, rename /system/xbin/tunman to tunmanbak. This is the Xunlei data saver/spyware tunneling manager. It is disabled from starting in the boot.img but will still run if called upon like all of the disabled services - they still exist, but not started by default. Make sure it is disabled in the Download Manager Settings
There is another service /sbin/mdbd that appears to be a method of tunneling over usb connections to gain access to a network and on to P.R.C. It is disabled in the boot.img already but I will rename this one in a next revision to be doubly sure it will not start.

Discovered an issue of some apps not recognizing internal sdcard so new versions posted to fix this plus rename /sbin/mdbd to mdbdbak to prevent it from being started after boot. See previous post for the reason.
Back up your internal sdcard contents if you flashed the original images - you will loose everything on sdcard0.
No action needs to be taken if this is a first-time flash.

@jajk How come this version doesn't just dump sd to folder 0? What was merged between miui and pro boot images?

@Sleepy_Augie It is a very complex issue how Android provides a virtual filesystem for SDCards. I thought I could implement it in a simpler fashion as per Android 5.1 which worked well except apps like the stock Contacts are stuck in the dark ages and are hard-coded to still look for the emulated/0 folder for the internal sdcard - not storage/sdcard0.
So going from stock to my original mod leaves an orphaned folder which becomes named 0 because it belonged to user 0. Going back the other way the folder representing access to sdcard0 simply disappears.
The real location of files that appear on the internal emulated sdcard is always /data/media. All other folders that appear to be the same thing are only symlinks to this. Make sense:silly:

Hey @jajk ,
Thanks for the reply, but I have done exactly everything you said and followed all of your steps, but after one day using it, I do not notice any change on battery life, it is still so bad, I have tried everyrom (and every way that was suggested from other users on XDA and MIUI forums including every battery calibration thing) I came across since I bought my RN2p and the maximum battery life I got is nearly 4:30 hours on screen!! After I flashed the boot.img I noticed a slightly more speed booting up the device, the performance is the same (which is good because am all satisfied about the performance except for the battery life).
I have flashed smiui today and it's slightly better consuming energy than the previous ones...
Maybe I have done something wrong doing the 01tweaks thing, if you can upload me yours so I can try paste it in /system/etc/int.d folder, if that will work, then I will be so thankful to you. And if you have any suggestions that I could do to improve and enhance the crazy energy draining then I will be more thankful.