Develop Bugs

Kernel scheduler tweaks (non-BFS)

First, let me say I am deeply sorry to open yet another thread on this subject. But I have made some investigations of my own and would like to make some clarifications which I think should not be buried on page 6 of some long thread....
This thread continues the discussion started by these threads:
http://forum.xda-developers.com/showthread.php?t=689829
http://forum.xda-developers.com/showthread.php?t=785988
From what I gather there about 5 different parameters which are purposed for tweaking:
- NEW_FAIR_SLEEPERS (default ON) - This is about the only parameter which I do feel some difference when disabling it (on Floyo 0.8) and for the worse. Hence currently I intend to leave it on.
- NORMALIZED_SLEEPER (default ON) - I found various recommendations to turn this off. I don't feel much difference but maybe there is a slight improvement. Currently I intend to turn it off.
- sched_latency_ns:
* Targeted preemption latency for CPU-bound tasks:
* (default: 20ms * (1 + ilog(ncpus)), units: nanoseconds)
*
* NOTE: this latency value is not the same as the concept of
* 'timeslice length' - timeslices in CFS are of variable length
* and have no persistent notion like in traditional, time-slice
* based scheduling concepts.
*
* (to see the precise effective timeslice length of your workload,
* run vmstat and monitor the context-switches (cs) field)
- sched_min_granularity_ns -
* Minimal preemption granularity for CPU-bound tasks:
* (default: 4 msec * (1 + ilog(ncpus)), units: nanoseconds)
- sched_wakeup_granularity_ns (not sure if this one was mentioned in previous threads but also related)
* SCHED_OTHER wake-up granularity.
* (default: 5 msec * (1 + ilog(ncpus)), units: nanoseconds)
*
* This option delays the preemption effects of decoupled workloads
* and reduces their over-scheduling. Synchronous workloads will still
* have immediate wakeup/sleep latencies.
Note the descriptions are from the kernel sources and default values are a bit different and also dependent on the init.rc in the ramdisk which is dependent on the ROM.
I tryed to play with the last 3 parameters in a very wide range and did not feel much difference. Based on my experience and searches over these forums and such I currently have these values:
sched_latency_ns 5000000
sched_wakeup_granularity_ns 1000000
sched_min_granularity_ns 1000000
They are somewhat arbitrary and if someone can bring up a scenario where the difference is noticeable I will happy to hear it.
Some technical notes:
- I have seen this "numerical" tweak in multiple places:
kernel.sched_features = 24188
This is not smart using a numerical value, as there are some new backports which I would like to incorporate into my kernel and they actually change the "correct" numerical value here.
The preferred way to tweak these settings was brought by androcheck here. Just a reminder:
Code:
# Step 1: Mount debugfs (which is a virtual filesystem like /proc/ or /sys/)
mount -t debugfs none /sys/kernel/debug
# Step 2 (optional): Display the current scheduler flags
cat /sys/kernel/debug/sched_features
# Step 3: Set the flag NO_NEW_FAIR_SLEEPERS
echo "NO_NEW_FAIR_SLEEPERS" > /sys/kernel/debug/sched_features
# Step 4: Unmount debugfs again
umount /sys/kernel/debug
I would actually skip the unmounting step since it doesn't bother to have it there and then you can play with the different parameters at /sys/kernel/debug directly.
I would like to emphasize my point about the kernel features tweaking, using an example with my current settings (only NORMALIZED_SLEEPER disabled):
Code:
# mount -t debugfs none /sys/kernel/debug
# echo NO_NORMALIZED_SLEEPER > /sys/kernel/debug/sched_features
# cat /sys/kernel/debug/sched_features | sed "s/ /\n/g"
NEW_FAIR_SLEEPERS
NO_NORMALIZED_SLEEPER
WAKEUP_PREEMPT
START_DEBIT
AFFINE_WAKEUPS
CACHE_HOT_BUDDY
SYNC_WAKEUPS
NO_HRTICK
NO_DOUBLE_TICK
ASYM_GRAN
LB_BIAS
LB_WAKEUP_UPDATE
ASYM_EFF_LOAD
NO_WAKEUP_OVERLAP
LAST_BUDDY
# cat /proc/sys/kernel/sched_features
24189
So I would highly recommend tweaking the sched_features only through the /sys/kernel/debug/sched_features where you actually know what you are doing.
Then to make it permanent you can grab the numerical value from /proc/sys/kernel/sched_features and write it, for example, to the sysctl.conf.
- One final technical note: f_padia in his post here detailed nicely how to make the changes permanent using sysctl.conf.
I find sysctl also very useful for temporary tweaking of the values, for example:
Code:
sysctl -w kernel.sched_latency_ns=5000000
sysctl -w kernel.sched_min_granularity_ns=1000000
sysctl -w kernel.sched_wakeup_granularity_ns=1000000
Alternatively you could also write them to the appropriate "file" at /proc/sys/kernel. Both these methods do not require the mount of the debug_fs but neither gives you the literal interface to the kernel features (which the debug_fs does - see above).

Removed the part about the OWNER_SPIN, apparently was using an experimental version of my kernel which has an additional OWNER_SPIN sched_feature which makes the numerical value of 24188 incorrect.
Most likely you have no idea what I am talking this was just one epic fail on my side - you can ignore it. Just read the first post it is now updated.

looks nice.. will give it a go

Thanks for your research and additional information to this topic!

this IS excellent work.. on my 2.1 dext these hacks, included in one .sh in init.d then chmod +x, improved a lot speed and I can even think there's a faster boot
you all rule man!

[REF] Startup script speed tweaks

Hi guys,
UPDATE: Over time, I've modified some of these values in my SpeedMod kernel. The values here may not be the best ones.
NOTE: These tweaks are now included in kernels based on sztupy's Universal Lagfix, for example:
http://forum.xda-developers.com/showthread.php?t=822756
But they must be manually activated from the recovery menu.
I've been using Linux kernel tweaks in a startup script to make the phone smoother.
With these tweaks, the phone is quite smooth and fast even without using the filesystem lagfixes.
These settings are only useful for you if you know how to create and modify a startup script. I use the old playlogos hack myself, but I'm sure there are many new ways to do it now.
Code:
# Tweak cfq io scheduler
for i in $(ls -1 /sys/block/stl*) $(ls -1 /sys/block/mmc*) $(ls -1 /sys/block/bml*) $(ls -1 /sys/block/tfsr*)
do 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
EDIT: Explanations:
# Remount all partitions with noatime
atime is a setting where the filesystem updates the access time of a file. This creates a write-after-every-read which slows things down. By default all partitions are mounted with relatime, which is an optimized version of atime. noatime is the fastest, and afaik we don't need atime.
# Tweak cfq io scheduler
Tweaked settings of the disk io scheduler more for flash memory. Defaults are optimized for spinning harddisks. Lowered the idle wait, re-enable the low latency mode of cfq, removed the penalty for back-seeks and explicitly tell the kernel the storage is not a spinning disk.
# Tweak kernel VM management
Set tendency of kernel to swap to minimum, since we don't use swap anyway.
Lower the amount of unwritten write cache to reduce lags when a huge write is required.
Increase tendency of kernel to keep block-cache to help with slower RFS filesystem.
Increase minimum free memory, in theory this should make the kernel less likely to suddenly run out of memory.
# Tweak kernel scheduler
Make the task scheduler more 'fair' when multiple tasks are running. This has a huge effect on UI and App responsiveness. These values (less aggressive settings) are 20% of the Linux defaults, and about half of the Android defaults.
# Miscellaneous tweaks
Increase the write flush timeouts to save some battery life.
___________________________________
EDIT: How to create/use a startup script:
You need root and busybox for this.
This procedure is adapted from the old OCLF which used this method to create a startup script in /system/userinit.sh
Check if the file /system/userinit.sh exists. If it does, u should just edit that file as the startup script and DO NOT do the procedure below.
Here's how to do it manually. Do this only if some other lagfix/patch has not already done the playlogos hack, otherwise u might overwrite the other script!
Create the startup script on your PC. Use adb to push it to /sdcard/userinit.sh
adb push userinit.sh /sdcard/userinit.sh
On your PC, create a file called playlogos1 with this content:
#!/system/bin/sh
sh /data/userinit.sh
playlogosnow
Use adb to push the playlogos1 file to /sdcard/playlogos1
adb push playlogos1 /sdcard/playlogos1
Now use adb shell, su and do this:
busybox mount -o remount,rw /system;
busybox cp /sdcard/userinit.sh /data/userinit.sh;
busybox mv /system/bin/playlogos1 /system/bin/playlogosnow;
busybox cp /sdcard/playlogos1 /system/bin/playlogos1;
chmod 755 /system/bin/playlogos1;
chmod 755 /data/userinit.sh;
The startup script will be /data/userinit.sh
The reason I put the startup script in /data is so that if you mess up the startup script and get stuck during boot, you can do a "clear data" from recovery, and the startup script will be erased.

Could you explain what this actually does for the non linux savvy, also maybe you could make a script/app for this so everyone else can try it ?

hardcore said:
Hi guys,
I've been using Linux kernel tweaks in a startup script to make the phone smoother.
With these tweaks, the phone is quite smooth and fast even without using the filesystem lagfixes.
These settings are only useful for you if you know how to create and modify a startup script. I use the old playlogos hack myself, but I'm sure there are many new ways to do it now.
Code:
# Remount all partitions with noatime
for k in $(mount | cut -d " " -f3)
do
sync
mount -o remount,noatime $k
done
# Tweak cfq io scheduler
for i in $(ls -1 /sys/block/stl*) $(ls -1 /sys/block/mmc*) $(ls -1 /sys/block/bml*) $(ls -1 /sys/block/tfsr*)
do 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
# Tweak kernel VM management
echo "0" > /proc/sys/vm/swappiness
echo "10" > /proc/sys/vm/dirty_ratio
echo "1000" > /proc/sys/vm/vfs_cache_pressure
echo "4096" > /proc/sys/vm/min_free_kbytes
# Tweak kernel scheduler
echo "2000000" > /proc/sys/kernel/sched_latency_ns
echo "500000" > /proc/sys/kernel/sched_wakeup_granularity_ns
echo "400000" > /proc/sys/kernel/sched_min_granularity_ns
# Miscellaneous tweaks
setprop dalvik.vm.startheapsize 8m
setprop wifi.supplicant_scan_interval 90
setprop windowsmgr.max_events_per_sec 68
Click to expand...
Click to collapse
VERY interesting

EarlZ said:
you could make a script/app for this so everyone else can try it ?
Click to expand...
Click to collapse
+1, pretty plz, also, is this compatible with voodoo?

INeedYourHelp said:
+1, pretty plz, also, is this compatible with voodoo?
Click to expand...
Click to collapse
Should be compatible, although u need to know how to add it into voodoo's startup script.

Hello
Values description for each one and why is welcome

supercurio said:
Hello
Values description for each one and why is welcome
Click to expand...
Click to collapse
Hey supercurio! Great job on Voodoo, I am particularly keen on the Sharpness, Video and future Sound fixes. I think its very cool that you found out how to modify the sharpness (S-AMOLED's PenTile matrix software algorithms?).
Edited the starting post with explanations. Most of them should be documented somewhere in the Linux sources / documents.
I've been using them for a while, tweaking values here n there. I think I've finally reached a stage where I'm confident enough to recommend them to others to try. There could be more optimum values with further testing, but these work well for me with Froyo.

hardcore said:
Hey supercurio! Great job on Voodoo, I am particularly keen on the Sharpness, Video and future Sound fixes. I think its very cool that you found out how to modify the sharpness (S-AMOLED's PenTile matrix software algorithms?).
Edited the starting post with explanations. Most of them should be documented somewhere in the Linux sources / documents.
I've been using them for a while, tweaking values here n there. I think I've finally reached a stage where I'm confident enough to recommend them to others to try. There could be more optimum values with further testing, but these work good for me so far with Froyo.
Click to expand...
Click to collapse
Yeah thank you so much for taking the time and sharing, i'll integrate them after a bit of testing
About the sharpness filter yes this is the main difference between S-AMOLED and AMOLED panel wise.
It's a hardware sharpness filter which is here to fight the fuzziness introduced by the pentile pattern but.. they overdid it a bit.
The "perfect" values are of course closer than the one with the same radius that the one of the blur introduced itself with the pixel pattern.
I feel it can maybe be improved a hair
I'll soon publish a version that allow write to the mDNIe register so you'll be able to play *live* with it too

Nice, could these be modified post-startup? like I go adb and copy paste some of them for testing?
I've tested setprop windowsmgr.max_events_per_sec 68, no difference. Set it to
setprop windowsmgr.max_events_per_sec 10 and still, no difference.

xan said:
Nice, could these be modified post-startup? like I go adb and copy paste some of them for testing?
I've tested setprop windowsmgr.max_events_per_sec 68, no difference. Set it to
setprop windowsmgr.max_events_per_sec 10 and still, no difference.
Click to expand...
Click to collapse
hey xan, you made me remember to add run-parts support.
i'll do that and you'll be able to set it without special hack very soon with voodoo

xan said:
Nice, could these be modified post-startup? like I go adb and copy paste some of them for testing?
I've tested setprop windowsmgr.max_events_per_sec 68, no difference. Set it to
setprop windowsmgr.max_events_per_sec 10 and still, no difference.
Click to expand...
Click to collapse
I don't think the setprop values can be modified post-startup. You can check if the value was modified by doing a getprop. (The default value for that prop is 55.)
The rest of them can be modified post-startup though.

Excuse my noobiness on Android, I would like an explanation on this command:
hardcore said:
# Tweak kernel VM management
echo "0" > /proc/sys/vm/swappiness
Click to expand...
Click to collapse
On my GNU/Linux system I've set vm.swappiness to 10, because I've got plenty MiB of RAM and I don't want my system to swap a lot. Is this swappiness the same as Linux? Because that would mean having the system to use more RAM, and since we don't have much of that available by default, I'm just surprised you didn't set a higher value. (I'm not saying you don't know what you're doing, I just want to learn how it works!)
By the way, this script is going to be a must-have, I think you've put an excellent effort on i9000 Android development! Thanks for sharing!

xan said:
Nice, could these be modified post-startup? like I go adb and copy paste some of them for testing?
I've tested setprop windowsmgr.max_events_per_sec 68, no difference. Set it to
setprop windowsmgr.max_events_per_sec 10 and still, no difference.
Click to expand...
Click to collapse
The aosp windowmanager (android framework) ignores values <35. (Samsung could have changed something here, but that is very unlikely).
That value does not affect the framerate, but how many touch events are reported to the apps; this saves some cpu if the user keeps touching the screen.

Fr4gg0r said:
The aosp windowmanager (android framework) ignores values <35. (Samsung could have changed something here, but that is very unlikely).
That value does not effect the framerate, but how many touch events are reported to the apps; this saves some cpu if the user keeps touching the screen.
Click to expand...
Click to collapse
Yes, i tried on Eclair to set it to 56fps (real fps is 55.5555555555555) but touch scrolling were not smoother.
I hope it can be improved in some way!

Fr4gg0r said:
The aosp windowmanager (android framework) ignores values <35. (Samsung could have changed something here, but that is very unlikely).
That value does not affect the framerate, but how many touch events are reported to the apps; this saves some cpu if the user keeps touching the screen.
Click to expand...
Click to collapse
Thanks for the info. Looks like default settings are best unless we can actually change the refresh rate.

supercurio said:
Yeah thank you so much for taking the time and sharing, i'll integrate them after a bit of testing
Click to expand...
Click to collapse
We are eagerly waiting for it =) I don't know when you manage to sleep since you have so many things to do in voodoo =)

hardcore said:
Hi guys,
I've been using Linux kernel tweaks in a startup script to make the phone smoother.
With these tweaks, the phone is quite smooth and fast even without using the filesystem lagfixes.
These settings are only useful for you if you know how to create and modify a startup script. I use the old playlogos hack myself, but I'm sure there are many new ways to do it now.
Code:
# Remount all partitions with noatime
for k in $(mount | cut -d " " -f3)
do
sync
mount -o remount,noatime $k
done
# Tweak cfq io scheduler
for i in $(ls -1 /sys/block/stl*) $(ls -1 /sys/block/mmc*) $(ls -1 /sys/block/bml*) $(ls -1 /sys/block/tfsr*)
do 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
# Tweak kernel VM management
echo "0" > /proc/sys/vm/swappiness
echo "10" > /proc/sys/vm/dirty_ratio
echo "1000" > /proc/sys/vm/vfs_cache_pressure
echo "4096" > /proc/sys/vm/min_free_kbytes
# Tweak kernel scheduler
echo "2000000" > /proc/sys/kernel/sched_latency_ns
echo "500000" > /proc/sys/kernel/sched_wakeup_granularity_ns
echo "400000" > /proc/sys/kernel/sched_min_granularity_ns
# Miscellaneous tweaks
setprop dalvik.vm.startheapsize 8m
setprop wifi.supplicant_scan_interval 90
EDIT: Explanations:
# Remount all partitions with noatime
atime is a setting where the filesystem updates the access time of a file. This creates a write-after-every-read which slows things down. By default all partitions are mounted with relatime, which is an optimized version of atime. noatime is the fastest, and afaik we don't need atime.
# Tweak cfq io scheduler
Tweaked settings of the disk io scheduler more for flash memory. Defaults are optimized for spinning harddisks. Lowered the idle wait, re-enable the low latency mode of cfq, removed the penalty for back-seeks and explicitly tell the kernel the storage is not a spinning disk.
# Tweak kernel VM management
Set tendency of kernel to swap to minimum, since we don't use swap anyway.
Lower the amount of unwritten write cache to reduce lags when a huge write is required.
Increase tendency of kernel to keep block-cache to help with slower RFS filesystem.
Increase minimum free memory, in theory this should make the kernel less likely to suddenly run out of memory.
# Tweak kernel scheduler
Make the task scheduler more 'fair' when multiple tasks are running. This has a huge effect on UI and App responsiveness. These values are 10% of the Linux defaults, and about half of the Android defaults.
# Miscellaneous tweaks
Manually set the starting dalvik heap size.
Increase wifi scanning gap to reduce battery usage.
Click to expand...
Click to collapse
I'm interested in doing this but I'm not sure where should I put the file. I checked playlogos1 from /system/bin but it's a binary file.. Tried to find playlogos hack on the forum but can't really find anything...

i have a jpm with voodoo, and i have copy this code into /voodoo/scripts/init.sh
just simplely add to the end of it, of course, before the last line.
the system reboot is ok, but i havent see the effects yet.

btw, "ls -1 /sys/block/mmc*" in adb give us:
Code:
ls -1 /sys/block/mmc*
-1: No such file or directory
/sys/block/mmcblk0
/sys/block/mmcblk1
so, "-1" key is useless

[kab] said:
btw, "ls -1 /sys/block/mmc*" in adb give us:
Code:
ls -1 /sys/block/mmc*
-1: No such file or directory
/sys/block/mmcblk0
/sys/block/mmcblk1
so, "-1" key is useless
Click to expand...
Click to collapse
it should be -l, not one

[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

Control your Ascend P6 through Init.d

Control your Ascend P6 through Init.d
In this Thread i will provide you Guys an small Init.d Package, that will let you control the important stuff on your Device without using Third Party Applications. I created this Zip for private use, but i like to share it with you.
This is mainly for advanced Users, so if you're not confirmed with Scripts etc., please DON'T touch the Scripts!
I only tested on Stock Firmware!
I take no Credits for the Tweaks contained in the Zip. They goes out to all the Tweakers here @ xDa!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Installation
! PLEASE MAKE AN NANDROID IN RECOVERY, BEVORE YOU FLASH THE ZIP !
! YOU'LL FLASH THIS @ YOUR OWN RISK !
I suggest you Guys to use TWRP by Surdu Petru, because it has Init.d Support by default.
Reboot in Recovery
Backup your Rom
Flash the Ascend_P6_Init.d_Control.zip
Wipe Cache & Dalvik Cache
Reboot
The Logger
I added an Logging System into the Zip, that will check and show you, if the Tweaks applied sucessfully and give you an positive (+) or negative (-) output. That way you don't have to check them manually.
You'll find it in /data/00_init.d_control_log
It should give you an Output like this
(Which also is an Overview about the Stuff you can handle with this ZIP)
>>> SetPerm
+ Init.d Permissions set to 755
@ 01-22-2014 00:55:36
>>> FileSystem
+ EXT4 Partitions present
+ Cache Partition optimized
+ Cust Partition optimized
+ Data Partition optimized
+ System Partition optimized
+ Remount Done
Please check the Remount.log! If this Script works, you'll see most of your Mounts being Noatime
+ Logger removed
+ File System cleaned
@ 01-22-2014 00:55:39
>>> SQLite -48 Hour Delay-
+ Wifi Sleep is active
+ SQLite Database VACUUM and REINDEX finished
Check the Sqlit.log to see, if SQLite was successful
@ 01-22-2014 00:57:13
>>> DarkyZipalign & Zipalign -48 Hour Delay-
+ DarkyZipalign applied
Check the DarkyZipalign.log to see, if everything was aligned
+ Zipalign finished
Check the Zipalign.log to see, if everything was completed
@ 01-22-2014 00:57:39
>>> Entropy
+ Haveged Binary is active
+ Entropy is active
@ 01-22-2014 00:57:40
>>> Alternative Scheduler & Governor by Surdu_Petru
+ SIO Scheduler present
+ SIOPLUS Scheduler present
+ VR Scheduler present
+ ZEN Scheduler present
+ MINMAX Governor present
@ 01-22-2014 00:57:41
>>> CPUconfig
+ Governor is set to k3hotplug
+ I/O Scheduler is set to zen
+ I/O Settings active
+ SD Cache is set to 2048 kb
+ MIN Frequency is set to 200000 mhz
+ MAX Frequency is set to 1500000 mhz
+ CPU Frequency locked @ 0
+ MIN CORES set to 1
+ MAX CORES set to 4
+ Active Cores locked @ 0
+ MIN GPU Frequency is set to 58000
+ MAX GPU Frequency is set to 480000
+ GPU Frequency locked @ 0
+ MIN DDR Frequency is set to 58000
+ MAX DDR Frequency is set to 450000
+ DDR Frequency locked @ 0
@ 01-22-2014 00:57:54
>>> SCREEN ON / OFF Profile
+ Screen On / Off Profile active
@ 01-22-2014 00:57:54
>>> Kernel
+ Kernel Values applied
+ VM Values applied
@ 01-22-2014 00:57:56
>>> Lowmemorykiller
+ Minfree Adj Values applied
+ Minfree Cost Values applied
+ Minfree Debug_Level Values applied
+ Minfree Values applied
@ 01-22-2014 00:57:57
The CPU Script
Probaply the most interessting Script 4 us is the 60CPUconfig - Script. It will let you:
Set CPU Governor
Set I/O Scheduler
Set SDCache
Set MIN/MAX CPU Frequencys
Lock active CPU Frequency
Set MIN/MAX abvailable Cores
Lock active Cores
Set MIN/MAX GPU Frequencys
Lock active GPU Frequency
Set MIN/MAX DDR Frequencys
Lock active DDR Frequency
Set Screen ON / OFF Profiles
I tried to keep it easy to handle, so all you have to do, is to set your Values on Top (one time for Screen On & one time for Screen Off)!
#---------------------------------------------#
# Configure your SCREEN ON Values #
#---------------------------------------------#
# Set Scaling Governor
# k3hotplug minmax ondemand performance
GOVERNOR=k3hotplug
#---------------------------------------------#
# Set I/O Scheduler
# cfq deadline noop sio sioplus vr zen
SCHEDULER=cfq
#---------------------------------------------#
# SDCache
# 128 256 512 1024 2048 4096
READ_AHEAD_KB=2048
#---------------------------------------------#
# Set MIN/MAX CPU Frequency
# 200000 400000 600000 800000 1000000 1200000 1399000 1400000 1500000
CPU_MIN=200000
CPU_MAX=1500000
#---------------------------------------------#
# Lock CPU Frequency
# 200000 400000 600000 800000 1000000 1200000 1399000 1400000 1500000
# Stock 0
CPU_FREQ=0
#---------------------------------------------#
# Set MIN/MAX available Cores
# 1-4
CORE_MIN=1
CORE_MAX=4
#---------------------------------------------#
# Lock active CPU Cores
# 0 - 4
# Stock 0
CORE_LOCK=0
#---------------------------------------------#
# Set MIN/MAX GPU Frequency
# 58000 120000 240000 360000 480000
GPU_MIN=58000
GPU_MAX=480000
#---------------------------------------------#
# Lock GPU Frequency
# 58000 120000 240000 360000 480000
# Stock 0
GPU_FREQ=0
#---------------------------------------------#
# Set MIN/MAX DDR Frequency
# 58000 120000 360000 450000
DDR_MIN=58000
DDR_MAX=450000
#---------------------------------------------#
# Lock DDR Frequency
# 58000 120000 360000 450000
# Stock 0
DDR_FREQ=0
#---------------------------------------------#
# Configure your SCREEN OFF Values #
#---------------------------------------------#
# Set Scaling Governor
# k3hotplug minmax ondemand performance
SLEEP_GOVERNOR=ondemand
#---------------------------------------------#
# Set I/O Scheduler
# cfq deadline noop sio sioplus vr zen
SLEEP_SCHEDULER=noop
#---------------------------------------------#
# Set MIN/MAX CPU Frequency
# 200000 400000 600000 800000 1000000 1200000 1399000 1400000 1500000
SLEEP_CPU_MIN=200000
SLEEP_CPU_MAX=600000
#---------------------------------------------#
# Lock CPU Frequency
# 200000 400000 600000 800000 1000000 1200000 1399000 1400000 1500000
# Stock 0
SLEEP_CPU_FREQ=0
#---------------------------------------------#
# Set Min/Max available Cores
# 1-4
SLEEP_CORE_MIN=1
SLEEP_CORE_MAX=1
#---------------------------------------------#
# Lock active CPU Cores
# 0 - 4
# Stock 0
SLEEP_CORE_LOCK=0
#---------------------------------------------#
# Set MIN/MAX GPU Frequency
# 58000 120000 240000 360000 480000
SLEEP_GPU_MIN=58000
SLEEP_GPU_MAX=120000
#---------------------------------------------#
# Lock GPU Frequency
# 58000 120000 240000 360000 480000
# Stock 0
SLEEP_GPU_FREQ=0
#---------------------------------------------#
# Set MIN/MAX DDR Frequency
# 58000 120000 360000 450000
SLEEP_DDR_MIN=58000
SLEEP_DDR_MAX=120000
#---------------------------------------------#
# Lock DDR Frequency
# 58000 120000 360000 450000
# Stock 0
SLEEP_DDR_FREQ=0
If you're not sure, that your Values are stable, let your modified Script run through SManager without the on Boot option for at least 24 Hours. After that you can add it back into the /system/etc/init.d - Folder.
I'll take care about the right Permissions, if you forgot to set them.
Uninstallation
The Zip contains an Uninstaller, so to get back to Stock you simply have to type this commands in the included Terminal Emulator
su [enter]
uninstall [enter]
and confirm your choice.
With v1.1 i added 3 CPU Profiles, that can be applied with the Terminal Emulator.
Simply type
su [enter]
battery, game or default[enter]
to switch between them. Of course you can edit them, to fit your needs. You'll find them in
/system/bin/
Alright, that's it for now. I'll edit this Post as soon as i got more Time.
Feel free to play around with the Scripts / Values and share your experience with us.
If you notice any Errors, let me know.
DOWNLOAD [ Official Huawei FW ]
DOWNLOAD [ Official Huawei FW + [URL="http://forum.xda-developers.com/showthread.php?t=2620421"]HA P6 Custom Kernel ][/URL]
DOWNLOAD [CM10 ]
​

Hallo HSD-Pilot,
I install yesterday the one for the CLEANROM_V1 from Petru.
Now the Software run very smooth. The Systemstart is very fast now!
But i have no possibility to start in to the Twrp-Recovery.
Need help.

Clean Rom replaces the Stock Recovery with TWRP. So to boot into Recovery you have to hold both Vol. Keys while Power on your Device. Just like you usually flash Stock Firmwares out of the dload Folder.
Gesendet von meinem HUAWEI P6-U06 mit Tapatalk

HSD-Pilot said:
Clean Rom replaces the Stock Recovery with TWRP. So to boot into Recovery you have to hold both Vol. Keys while Power on your Device. Just like you usually flash Stock Firmwares out of the dload Folder.
Gesendet von meinem HUAWEI P6-U06 mit Tapatalk
Click to expand...
Click to collapse
No! After Script install it don't do it.
But i have a solution.
Install ROM Manager v.5.5.3.4. Of course it is primay for cwm but there is the option "reboot into recovery system".
This function is a way to start into twrp.

The Zip shouldn't effect the Recovery Partition, so TWRP should boot. There's nothing contained, that touches the Recovery. You tried to uninstall the Pack (su > uninstall) ?
Gesendet von meinem HUAWEI P6-U06 mit Tapatalk

so I see it setsbthe freeq of the cpu. what willbhapen if I use setcpu now?
can you please provide us the coding of the scripts? I would like to paste them manualy in my inid.t folder. please

benna said:
so I see it setsbthe freeq of the cpu. what willbhapen if I use setcpu now?
can you please provide us the coding of the scripts? I would like to paste them manualy in my inid.t folder. please
Click to expand...
Click to collapse
SetCPU usually kicks in after the init. d Scripts, so it will overwrite the Values.
The Zip contains an Script called 80SetCPU, this will do the same like the App.
#!/system/bin/sh
LOG_FILE=/data/00_init.d_control_log/01Init.d_Control.log
echo ">>> SetCPU" | tee -a $LOG_FILE;
#---------------------------------------------#
# Configure your Values #
#---------------------------------------------#
# Set Scaling Governor
# k3hotplug minmax ondemand performance
GOVERNOR="k3hotplug"
#---------------------------------------------#
# Set IO Scheduler
# cfq deadline noop sio sioplus vr zen
SCHEDULER="zen"
#---------------------------------------------#
# Set Min & Max Frequency
# 200000 400000 600000 800000 1000000 1200000 1399000 1400000 1500000
CPU_MIN=200000
CPU_MAX=1500000
#---------------------------------------------#
# Apply Configuration #
#---------------------------------------------#
#Set CPU Governor
if [ -e /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ]; then
echo $GOVERNOR > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor; else
echo "- Unable to set CPU Governor. File NOT found!" | tee -a $LOG_FILE;
fi;
if [ -e /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor ]; then
echo $GOVERNOR > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor;
fi;
if [ -e /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor ]; then
echo $GOVERNOR > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor;
fi;
if [ -e /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor ]; then
echo $GOVERNOR > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor;
fi;
sleep 1
if [ /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor=$GOVERNOR ]; then
echo "+ $GOVERNOR Governor is running" | tee -a $LOG_FILE; else
echo "- $GOVERNOR Governor is NOT running" | tee -a $LOG_FILE;
fi;
#---------------------------------------------#
# Set Scheduler
dm=/sys/block/dm-*
loop=/sys/block/loop*
mmc=/sys/block/mmc*
mtd=/sys/block/mtd*
nbd=/sys/block/nbd*
ram=/sys/block/ram*
zram=/sys/block/zram*
for a in $dm $loop $mmc $mtd $nbd $ram $zram; do
if [ -e ${a}/queue ]; then
echo $SCHEDULER >> ${a}/queue/scheduler;
fi; done
sleep 1
if [ /sys/block/mmcblk0/queue/scheduler=$SCHEDULER ]; then
echo "+ $SCHEDULER Scheduler is running" | tee -a $LOG_FILE; else
echo "- $SCHEDULER Scheduler is NOT running" | tee -a $LOG_FILE;
fi;
#---------------------------------------------#
# Set MIN/MAX Frequency
if [ -e /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq ]; then
echo $CPU_MIN > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq; else
echo "- Unable to set MIN Frequency. File NOT found!" | tee -a $LOG_FILE;
fi;
if [ -e /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq ]; then
echo $CPU_MIN > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq;
fi;
if [ -e /sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq ]; then
echo $CPU_MIN > /sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq;
fi;
if [ -e /sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq ]; then
echo $CPU_MIN > /sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq;
fi;
if [ -e /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq ]; then
echo $CPU_MAX > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq; else
echo "- Unable to set MAX Frequency. File NOT found!" | tee -a $LOG_FILE;
fi;
if [ -e /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq ]; then
echo $CPU_MAX > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq;
fi;
if [ -e /sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq ]; then
echo $CPU_MAX > /sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq;
fi;
if [ -e /sys/devices/system/cpu/cpu3/cpufreq/scaling_max_freq ]; then
echo $CPU_MAX > /sys/devices/system/cpu/cpu3/cpufreq/scaling_max_freq;
fi;
sleep 1
if [ /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq=$CPU_MIN ]; then
echo "+ MIN Frequency is set to $CPU_MIN mhz" | tee -a $LOG_FILE; else
echo "- MIN Frequency is NOT set to $CPU_MIN mhz" | tee -a $LOG_FILE;
fi;
if [ /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq=$CPU_MAX ]; then
echo "+ MAX Frequency is set to $CPU_MAX mhz" | tee -a $LOG_FILE; else
echo "- MAX Frequency is NOT set to $CPU_MAX mhz" | tee -a $LOG_FILE;
fi;
#---------------------------------------------#
echo "@ $( date +"%m-%d-%Y %H:%M:%S" )" | tee -a $LOG_FILE;
echo " " | tee -a $LOG_FILE;
Just set your Values on top and reboot :thumbup:
Gesendet von meinem HUAWEI P6-U06 mit Tapatalk

Works flawlessly!!!
HUAWEIAscendP6

Uploaded an small Update
- cleaned some scripts
- added CPU / GPU LOCK Script
- rearranged the Build.prop Tweaks
- replaced Bootanimation (Nexus)
Use the uninstaller to revert back to Stock! It will handle everything 4 ya (incl. restore Stock Bootanimation).
Gesendet von meinem HUAWEI P6-U06 mit Tapatalk

HSD-Pilot said:
Uploaded an small Update
- cleaned some scripts
- added CPU / GPU LOCK Script
- rearranged the Build.prop Tweaks
- replaced Bootanimation (Nexus)
Use the uninstaller to revert back to Stock! It will handle everything 4 ya (incl. restore Stock Bootanimation).
Gesendet von meinem HUAWEI P6-U06 mit Tapatalk
Click to expand...
Click to collapse
hi
which app works best with this script

nARDOs said:
hi
which app works best with this script
Click to expand...
Click to collapse
What do you mean with "which App"¿
The meaning of this package is to avoid 3rd Party Apps.
To Edit the Scripts you can use any Root Explorer that contains an Text Editor and on an PC use Notepad++
Btw. I will release an Update as soon as i got time. I noticed, that the Max GPU / DDR frequencys and DDR lock are gettin overwritten by the system to the default values. I added an lil workaround to avoid that.
Also i added 3 CPU/GPU Profiles (Battery, Game & Default) that can easily gettin activated via Terminal Emulator.
Gesendet von meinem HUAWEI P6-U06 mit Tapatalk

HSD-Pilot said:
What do you mean with "which App"¿
The meaning of this package is to avoid 3rd Party Apps.
To Edit the Scripts you can use any Root Explorer that contains an Text Editor and on an PC use Notepad++
Btw. I will release an Update as soon as i got time. I noticed, that the Max GPU / DDR frequencys and DDR lock are gettin overwritten by the system to the default values. I added an lil workaround to avoid that.
Also i added 3 CPU/GPU Profiles (Battery, Game & Default) that can easily gettin activated via Terminal Emulator.
Gesendet von meinem HUAWEI P6-U06 mit Tapatalk
Click to expand...
Click to collapse
This package improves game performance significantly must i see. Big Thanks. :good:
Adding preset profiles will help alot
Question:
MIN/MAX GPU DDR frequency is higher than ur output on my phone. Is this because of the overwritting u mentioned ?

Nope, that's an typo. Max DDR should be 450000, it's already fixed in the next Update.
I guess i'm back @ home tomorrow, to upload it.
Edit: About the Min GPU & DDR Frequencys
They usually set to 360000 by default and we can't lower them through Scripts. The only way to lower the Min Freq is to lower the Max Freq! I couldn't find another solution :thumbdown:
So, when you set min 240000 & max 360000, min will always be 360000.
To set it lower you have to set min 240000 & max 240000.
The workaround i'm currently using is to make the max 240000 stick (by default it will not go/stick below 360000).
Gesendet von meinem HUAWEI P6-U06 mit Tapatalk

HSD-Pilot said:
Nope, that's an typo. Max DDR should be 450000, it's already fixed in the next Update.
I guess i'm back @ home tomorrow, to upload it.
Gesendet von meinem HUAWEI P6-U06 mit Tapatalk
Click to expand...
Click to collapse
Waiting for the update :fingers-crossed:

Me too!
Sent from my P6-U06

Update is up. Let me know how it works 4 ya :highfive:

HSD-Pilot said:
Update is up. Let me know how it works 4 ya :highfive:
Click to expand...
Click to collapse
can we just flash it over the previous version or do we need to unistall the previous one ?
will give feedback after installing it.

Just flash om top, the Update-Script will do everything 4 ya :good:
Btw: I finally had the time to switch to Surdu's Stock CM Version and will add an CM Edition after the Testflash of the Uploaded Zip :good:
And remember, to get back to Stock always use the uninstaller. After that your Device will reboot, like you had never flashed this Mod.

HSD-Pilot said:
Update is up. Let me know how it works 4 ya :highfive:
Click to expand...
Click to collapse
Many thanks, work good!
But I have a question.
I use smanager widget app.
How can I make a script that the toast notification list the set values like smanager?
Sorry for my bad english...
Sent from my P6-U06

Creating an Toast Notification out of an Script is not that easy, if even possible. As far as i know it needs some Java Stuff to create toasts.
Gesendet von meinem P6-U06 mit Tapatalk 2