• XDA Forums have been migrated to XenForo. We are aware of several issues including missing threads, logins not working, and more. To discuss, use this thread.

[KERNEL][4.4.3] ★☆ Kangaroo Kernel ☆★ 21 OCT | v072 | 3.4.104

Status
Not open for further replies.

CamoGeko

Forum Moderator
Staff member
Dec 10, 2010
15,943
8,317
0
Establishing Battlefield Control... Standby!
I wish :thumbup:
It's on some previous page in this thread mate. Just to bored to search for it so I uploaded it again.

Swiftkeyed from my Renovated HTC One
Hahaha, I read the last few pages.. must have missed it thought.

I'm flashing Renovate r84 tonight so will flash the test kernel straight after.

Thanks for the heads up mate! I have been on ElementalX since getting my HTC One so it will be nice to run another kernel for a while and see the difference.
 
  • Like
Reactions: DanteGR

Headless96

New member
Nov 4, 2012
1,055
2,099
0
Cardiff
Kangaroo Kernel Kontrol :p
@Headless_monkeyhunta96 would be nice to have undervolting options in the script too if possible but probably would be too much work. Something like flar has in his installation script.

Sent from my baked potato with blue cheese
Undervolting options are in the script already mate, check the second last line ;)

But it's not currently supported yet, I'm guessing poondog's gonna add it in a later version so I left the option in there

Sent from my HTC One using XDA Premium 4 mobile app
 

CamoGeko

Forum Moderator
Staff member
Dec 10, 2010
15,943
8,317
0
Establishing Battlefield Control... Standby!
Undervolting options are in the script already mate, check the second last line ;)

But it's not currently supported yet, I'm guessing poondog's gonna add it in a later version so I left the option in there

Sent from my HTC One using XDA Premium 4 mobile app
Ah I see it now mate, forgive my mistake. :(

I hope he adds it sooner rather than later, the UV and Thermal options are the ones that I really miss in this kernel.
 

DanteGR

Well-known member
Dec 14, 2010
3,771
1,389
113
Thessaloniki
www.facebook.com
Ah I see it now mate, forgive my mistake. :(

I hope he adds it sooner rather than later, the UV and Thermal options are the ones that I really miss in this kernel.
But theoretically speaking have u seen a noticeable improvement in battery life by undervolting? I think it's a placebo myself. Underclocking the same.

Swiftkeyed from my Renovated HTC One
 

CamoGeko

Forum Moderator
Staff member
Dec 10, 2010
15,943
8,317
0
Establishing Battlefield Control... Standby!
But theoretically speaking have u seen a noticeable improvement in battery life by undervolting? I think it's a placebo myself. Underclocking the same.

Swiftkeyed from my Renovated HTC One
Not sure if there was any positive improvement as I haven't run kangaroo kernel for long enough.

However I like to overclock + undervolt because I can get more speed out of the SOC while keeping battery drain down. Then again it all depends on how much a user can undervolt their CPU by.

Anyways, I'm running the test kernel now so will see how it goes. :)

PS. Are you running renovate as well mate?


Sent from my baked potato with blue cheese
 
Last edited:
  • Like
Reactions: DanteGR

Rad ryan

New member
Jan 22, 2011
502
239
0
Sorry I wasn't here, did you need tissues?



Smartmax is pretty good, on this device especially with mpdec because it will boost itself. But, mpdec will boost to one freq and smartmax will be ideal at another, so its not an ideal situation.. Since ondemand and mpdec were made for each other

LOL :D

Huh? Mpdecision will boost cpu? And it will do this despite the governor settings?
Sure would be nice if the option to control mpdecision was an option ;) :D



Got a bit bored so decided to complete Poondog's script as much as I could and made it flashable! .. All you have to do now is download it and flash it, I'm sure even the 'noobs' can manage that ;)

Right here's what's going on anyway:
Code:
#!/system/bin/sh

### KANGAROO CONTROL SCRIPT ###
### By Poondog ###

# Enable Force Fast Charge:
echo 0 > /sys/kernel/fast_charge/force_fast_charge

# Enable BLN 
echo 0 > /sys/class/leds/button-backlight/blink_buttons

# Vibration Control (General)
echo 2700 > /sys/class/timed_output/vibrator/voltage_level

# Enable Sweep2Wake: 0=None, 1=Both, 2=S2S
echo 1 > /sys/android_touch/sweep2wake

# Enable SweepUp2Wake: (Swipe from Logo upwards)
echo 1 > /sys/android_touch/sweepup2wake

# Enable Logo2Menu:
echo 1 > /sys/android_touch/logo2menu

# Enable Double Tap To Wake: 0=Off, 1=Bottom only, 2=Fullscreen
echo 2 > /sys/android_touch/doubletap2wake

# Enable Logo2Wake:
echo 0 > /sys/android_touch/logo2wake

# Vibration Control (Wake Up Controls) - 0=No Vibration, Default=20
#echo 0 > /sys/android_touch/vib_strength

# Enable Pocket Detection:
echo 1 > /sys/android_touch/pocket_detect

# IO Scheduler: (In lower case)
echo fiops > /sys/block/mmcblk0/queue/scheduler;

# IO Readahead:
echo 512 > /sys/block/mmcblk0/queue/read_ahead_kb;

# Min/Max CPUs online: Should stick
chmod 666 /sys/power/pnpmgr/hotplug/mp_min_cpus
echo 1 > /sys/power/pnpmgr/hotplug/mp_min_cpus
chmod 444 /sys/power/pnpmgr/hotplug/mp_min_cpus
chmod 666 /sys/power/pnpmgr/hotplug/mp_max_cpus
echo 4 > /sys/power/pnpmgr/hotplug/mp_max_cpus
chmod 444 /sys/power/pnpmgr/hotplug/mp_max_cpus

# Multicore Power Saving: 0=Off, 1=Medium, 2=Aggressive
echo 0 > /sys/devices/system/cpu/sched_mc_power_savings

# Max GPU clock:
chmod 666 /sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/max_gpuclk
echo 400000000 > sys/power/pnpmgr/sysinfo/gpu_max_clk
chmod 444 /sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/max_gpuclk

# Powersaver:
echo 0 > sys/power/powersave

# Voltage control: not supported currently
#echo "800 800 800 825 875 900 960" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

# Disable pnpmgr
#mv /system/bin/pnpmgr /system/bin/pnpmgr.bak
Everything from poondog's previous script is here but I've also added:
  1. BLN Control
  2. Vibration Control (General)
  3. Vibration Control (Wake Up Controls)
  4. Multicore Power Saving Control
  5. Fixed Min/Max HP Cores
  6. Fixed GPU Freq Command - Can change max GPU frequency to 400, 320, 200 and 128mhz!
  7. Disable Pnpmgr - This option isn't going to happen unless you enable it (delete the # before the 'mv /system.....')
  8. Sweep Up 2 Wake - I don't think poondog made this public but he has the code for it, simply swipe up from the logo and it should turn the screen on! (Logo2Menu must be enabled) ... It's kinda buggy atm, takes 2 tries for me but the options there :p
  9. Deletes ElementalX scripts - I think the reason some of you have certain things disabled when they shouldn't be is because you have scipts and stuff left over from ElementalX, so I added in the updater-script to delete these files

Also the principal still stands:

  • 1 to enable a function and 0 to disable unless stated otherwise :)
  • And a # before a line means that line is disabled, to enable that line, delete the #, save file and flash!

Final thing: The values that are enabled/disabled in the init.d script already are like that when flashing the kangaroo kernel. Basically when this script is flashed, you'll notice nothing else enabled that already wasn't, it's up to you to decide which ones you want! :)

Final thing 2: If you have no idea what is going on here and would like to maybe learn a few things before you flash the zip, check out my guide on init.d scripts ...
It's got some general info and could teach you a few things ;)

Enjoy!



AWESOME JOB MATE! :) You did some things I was trying but you did it better :) , I'm gonna head over to your init.d thread and give it a look. I was having gov for individual cpu's changing at random for whatever reason and I tried to fix with init.d but didn't think about chmod 444 bc I've seen it but not sure what it does exactly. Here's the the script I WAS currently working on. I'll probably just cut n paste to your script what I have that's not in yours :) , would you mind looking it over and fixing anything wrong or things that could be better that aren't already in your script, if you don't mind? The gov settings are just something I'm experimenting with and haven't had a chance to try permission locks to make them stick. I'll paste it in the quote box below :)
#!/system/bin/sh

# Fast Charge

echo 1 /sys/kernel/fast_charge/force_fast_charge

# Sweep2Sleep

echo 0 /sys/android_touch/sweep2wake

# Enable Logo2Menu

echo 1 /sys/android_touch/logo2menu

# Double Tap To Wake 1=bottom screen 2=full

echo 1 /sys/android_touch/doubletap2wake

# Logo2Wake

echo 0 /sys/android_touch/logo2wake

# Pocket Detection

echo 0 /sys/android_touch/pocket_detect

# Set Vibratorstrength

echo 1700 /sys/class/timed_output/vibrator/voltage_level

# Set Button Backlight notification

echo 0 /sys/class/leds/button-backlight/blink_buttons

# Set Multicorepowersavings

echo 0 /sys/devices/system/cpu/sched_mc_power_savings

# UnderVolt

#echo 750 800 800 825 850 862 887 912 938 962 1000 1025 1062 1088 /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

# Set Scaling Governor

if [ -e /data/local/cpu_protection ] ; then
echo failed > /data/local/cpu_failed
chmod 777 /data/local/cpu_failed
exit
fi

echo applied > /data/local/cpu_protection
chmod 777 /data/local/cpu_protection
chmod 666 /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chmod 666 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "1674000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chmod 666 /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "384000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

chmod 666 /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
echo "ondemand " > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
chmod 666 /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
echo "1674000" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
chmod 666 /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
echo "384000" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq

chmod 666 /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
echo "ondemand" > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
chmod 666 /sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq
echo "1674000" > /sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq
chmod 666 /sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq
echo "384000" > /sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq

chmod 666 /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor
echo "ondemand" > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor
chmod 666 /sys/devices/system/cpu/cpu3/cpufreq/scaling_max_freq
echo "1674000" > /sys/devices/system/cpu/cpu3/cpufreq/scaling_max_freq
chmod 666 /sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq
echo "384000" > /sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq

echo 4 > /sys/devices/system/cpu/cpufreq/ondemand/down_differential
echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/enable_boost_cpu
echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/ignore_nice_load
echo 1026000,1026000,810000,810000 > /sys/devices/system/cpu/cpufreq/ondemand/input_event_min_freq
echo 0 > /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy
echo 918000 > /sys/devices/system/cpu/cpufreq/ondemand/optimal_freq
echo 0 > /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias
echo 3 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor
echo 20000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate
echo 10000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate_min
echo 594000 > /sys/devices/system/cpu/cpufreq/ondemand/sync_freq
echo 20000 > /sys/devices/system/cpu/cpufreq/ondemand/ui_sampling_rate
echo 80 > /sys/devices/system/cpu/cpufreq/ondemand/ui_timeout
echo 90 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo 80 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_any_cpu_load
echo 70 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_multi_core

#GOVERNOR="ondemand"

#echo GOVERNOR /sys/devices/system/cpu/#cpu0/cpufreq/scaling_governor
#echo GOVERNOR /sys/devices/system/cpu/#cpu1/cpufreq/scaling_governor
#echo GOVERNOR /sys/devices/system/cpu/#cpu2/cpufreq/scaling_governor
#echo GOVERNOR /sys/devices/system/cpu/#cpu3/cpufreq/scaling_governor

# Set IO Sheduler

SHEDULER="bfq"

echo SHEDULER /sys/block/mmcblk0/queue/scheduler

# Set IO read ahead

echo 512 /sys/block/mmcblk0/queue/read_ahead_kb

But theoretically speaking have u seen a noticeable improvement in battery life by undervolting? I think it's a placebo myself. Underclocking the same.

Swiftkeyed from my Renovated HTC One
Undervolting = slight benefit only if done right, underclocking can/will DEFINITELY save battery AT THE COST OF PERFORMANCE/SMOOTHNESS. See this thread for great and myth busting info :)
http://forum.xda-developers.com/showthread.php?t=1639689

The linked thread is bedalus compendium and has tons of awesome info gotten from very controlled and fairly scientific testing. I think the thread I'm talking about is the battery drain benchmarks. Just click on it from the main compendium thread.

Happy Reading :D

Sent from my HTC One using Tapatalk
 
Last edited:
  • Like
Reactions: jpfinne and DanteGR

poondog

Inactive Recognized Contributor
Dec 11, 2011
14,998
12,950
113
Melbourne
i just has random reboot on v40 test version , using viper and used it always whit your kernel is it someting or am i thinking about it too much :)
Logs or it didn't happen :)





@poondog are you planing to add MLG?

Gesendet von meinem HTC One mit Tapatalk
Yeah soon when they're all worked out.. flars doing a great job




I doubt it's one of his priorities.

Btw @poondog, been running 040 today and I love how smooth it is. Thanks for all your work on this kernel so far, you're definitely heading in the right direction.




Kangaroo Kernel Kontrol :p
@Headless_monkeyhunta96 would be nice to have undervolting options in the script too if possible but probably would be too much work. Something like flar has in his installation script.


Sent from my baked potato with blue cheese
Thanks :)
Voltage control? I said earlier it would come with governors when the kernel is mature enough
I've started testing new version :)


Ah I see it now mate, forgive my mistake. :(

I hope he adds it sooner rather than later, the UV and Thermal options are the ones that I really miss in this kernel.
I hope so too :) thermal to me though is way more important than mpdec replacement.. I'd like to control thermal but mpdec is great as it is
Especially now we can control max cores




LOL :D

Huh? Mpdecision will boost cpu? And it will do this despite the governor settings?
Sure would be nice if the option to control mpdecision was an option ;) :D

Undervolting = slight benefit only if done right, underclocking can/will DEFINITELY save battery AT THE COST OF PERFORMANCE/SMOOTHNESS. See this thread for great and myth busting info :)
http://forum.xda-developers.com/showthread.php?t=1639689

The linked thread is bedalus compendium and has tons of awesome info gotten from very controlled and fairly scientific testing. I think the thread I'm talking about is the battery drain benchmarks. Just click on it from the main compendium thread.

Happy Reading :D

Sent from my HTC One using Tapatalk
Yes mpdec and pnpmgr are responsible for boosting cpu too. Tbh I don't see a need for mpdec replacement, it's more of a buzzword than anything as there's nothing wrong with stock. Control is overrated too
Look how the kernel was for the past releases, up until now I've basically controlled all your options besides wake :p now with the script you have more control.

Yeah undervolting can do a bit.. best for heat I reckon. I boosted L2 already but not bus yet iirc.. seems good though :p

Max cpu freq will keep being reset by pnpmgr and mpdec. It keeps fluctuating. So you need to remove pnpmgr in the script, then you can control freqs easily I believe

I think soon the kernel is mature. I will add versions for 1.5ghz max cap too :)

Sent from my HTC One using XDA Premium 4 mobile app
 
Last edited:
  • Like
Reactions: Asselalf

dsymbol

New member
May 2, 2009
1,054
159
0
I think that's because you used another custom kernel before and you've some files remaining from those kernel
Yes you are correct. I had ElementalX for a couple of hours then decided to flash this kernel.

Before i flashed kk040, i wiped cache ( TWRP / Advance )
The new kernel should stick right?
Should i fastboot erase cache again?

Today is the first day with kk040, its been 9hours & im very happy with the new kernel so far.
Im out side, using 3G, opening up all kinda apps to abuse it but the battery drain is hoovering around 2.8% per hour.
 

poondog

Inactive Recognized Contributor
Dec 11, 2011
14,998
12,950
113
Melbourne
Yes you are correct. I had ElementalX for a couple of hours then decided to flash this kernel.

Before i flashed kk040, i wiped cache ( TWRP / Advance )
The new kernel should stick right?
Should i fastboot erase cache again?

Today is the first day with kk040, its been 9hours & im very happy with the new kernel so far.
Im out side, using 3G, opening up all kinda apps to abuse it but the battery drain is hoovering around 2.8% per hour.
Nah you don't really need to wipe caches. I just recommend doing it every now and then
I ran it dual core all day (new test kernel) and I'm sitting at 65% at the end. I do a lot of music streaming with Bluetooth in my car

seems im pretend to be never happened :D, thanks for being so good for noobs like me :)
Okay, if it happens again make sure you get a log, or at least see if there's correlation between the issues :)
 
  • Like
Reactions: dsymbol

Headless96

New member
Nov 4, 2012
1,055
2,099
0
Cardiff
AWESOME JOB MATE! :) You did some things I was trying but you did it better :) , I'm gonna head over to your init.d thread and give it a look. I was having gov for individual cpu's changing at random for whatever reason and I tried to fix with init.d but didn't think about chmod 444 bc I've seen it but not sure what it does exactly. Here's the the script I WAS currently working on. I'll probably just cut n paste to your script what I have that's not in yours :) , would you mind looking it over and fixing anything wrong or things that could be better that aren't already in your script, if you don't mind? The gov settings are just something I'm experimenting with and haven't had a chance to try permission locks to make them stick. I'll paste it in the quote box below :)

Sent from my HTC One using Tapatalk
Wow that is one messy script.... :silly:

Firstly none of the lines from '#Fast Charge' all the way to '#MultiCorePowersavings' will apply, you've made the same error on all of them haha. Basically I'll take the fast charge one for example, you've written:
Code:
echo 1 /sys/kernel/fast_charge/force_fast_charge
... And what you should've written is:
Code:
echo 1 [B]>[/B] /sys/kernel/fast_charge/force_fast_charge
You forgot to put in the '>' .. Very important as otherwise none of them will apply, fix that on all the lines before the cpu stuff and they'll work. Also if you actually want Sweep2Sleep then the value is 2 not 0.

Now the cpu stuff... (This is gonna be long, so I hid it to prevent a stupidly long post :p)



You've written:
Code:
if [ -e /data/local/cpu_protection ] ; then
echo failed > /data/local/cpu_failed
chmod 777 /data/local/cpu_failed
exit
fi
I don't know where you found this but we don't have a file called cpu_protection in that directory so this command is useless (get rid of it)

Now the next bit:
Code:
echo applied > /data/local/cpu_protection
chmod 777 /data/local/cpu_protection
chmod 666 /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chmod 666 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "1674000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chmod 666 /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "384000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
Change this to:

Code:
chmod 666 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chmod 444 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chmod 666 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1674000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chmod 444 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chmod 666 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 384000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
chmod 444 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
Changes:
  • Deleted cpu protection lines
  • Added chmod 444 lines
  • Fixed chmod lines (put a > in the command)
  • Took out quotation marks on things like 'ondemand' as they are unneeded

Repeat this exact procedure (copy and paste) for cpu1, cpu2 and cpu3. So for example:

Code:
chmod 666 > /sys/devices/system/cpu/cpu[COLOR="Red"]1[/COLOR]/cpufreq/scaling_governor
echo ondemand > /sys/devices/system/cpu/cpu[COLOR="red"]1[/COLOR]/cpufreq/scaling_governor
chmod 444 > /sys/devices/system/cpu/cpu[COLOR="red"]1[/COLOR]/cpufreq/scaling_governor
And so on....

Note: Not 100% sure how long these will apply for, since pnpmgr is still in play, guess that's down to you to test. Theoretically it should work though

Next bit:
Code:
echo 4 > /sys/devices/system/cpu/cpufreq/ondemand/down_differential
echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/enable_boost_cpu
echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/ignore_nice_load
echo 1026000,1026000,810000,810000 > /sys/devices/system/cpu/cpufreq/ondemand/input_event_min_freq
echo 0 > /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy
echo 918000 > /sys/devices/system/cpu/cpufreq/ondemand/optimal_freq
echo 0 > /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias
echo 3 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor
echo 20000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate
echo 10000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate_min
echo 594000 > /sys/devices/system/cpu/cpufreq/ondemand/sync_freq
echo 20000 > /sys/devices/system/cpu/cpufreq/ondemand/ui_sampling_rate
echo 80 > /sys/devices/system/cpu/cpufreq/ondemand/ui_timeout
echo 90 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo 80 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_any_cpu_load
echo 70 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_multi_core
This should stay applied even without chmod'ing every file but imo you shouldn't change these. The stock ondemand values have the perfect balance between performance and battery.

Moving on....
Code:
#GOVERNOR="ondemand"

#echo GOVERNOR /sys/devices/system/cpu/#cpu0/cpufreq/scaling_governor
#echo GOVERNOR /sys/devices/system/cpu/#cpu1/cpufreq/scaling_governor
#echo GOVERNOR /sys/devices/system/cpu/#cpu2/cpufreq/scaling_governor
#echo GOVERNOR /sys/devices/system/cpu/#cpu3/cpufreq/scaling_governor
Completely irrelevant since cpu governor has already been applied previously. Plus as you said without chmod 444'ing the relevant files, the governor's reset to stock values.

Code:
# Set IO Sheduler

SHEDULER="bfq"

echo SHEDULER /sys/block/mmcblk0/queue/scheduler
This'll work once you've fixed the command (forgot the > again) but if you want to shorten the script and make it easier to read, change to:
Code:
echo bfq > /sys/block/mmcblk0/queue/scheduler
And lastly the IO r/a line you need the '>' again.


In case you get completely stuck I made your script but completely fixed up for a reference point:

#!/system/bin/sh

# Fast Charge

echo 1 > /sys/kernel/fast_charge/force_fast_charge

# Sweep2Sleep:

echo 2 > /sys/android_touch/sweep2wake

# Enable Logo2Menu

echo 1 > /sys/android_touch/logo2menu

# Double Tap To Wake 1=bottom screen 2=full

echo 1 > /sys/android_touch/doubletap2wake

# Logo2Wake

echo 0 > /sys/android_touch/logo2wake

# Pocket Detection

echo 0 > /sys/android_touch/pocket_detect

# Set Vibratorstrength

echo 1700 > /sys/class/timed_output/vibrator/voltage_level

# Set Button Backlight notification

echo 0 > /sys/class/leds/button-backlight/blink_buttons

# Set Multicorepowersavings

echo 0 > /sys/devices/system/cpu/sched_mc_power_savings

# UnderVolt

#echo "750 800 800 825 850 862 887 912 938 962 1000 1025 1062 1088" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

# Set Scaling Governor

chmod 666 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chmod 444 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chmod 666 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1674000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chmod 444 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chmod 666 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 384000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
chmod 444 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

chmod 666 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
echo ondemand > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
chmod 444 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
chmod 666 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
echo 1674000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
chmod 444 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
chmod 666 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
echo 384000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
chmod 444 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq

chmod 666 > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
echo ondemand > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
chmod 444 > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
chmod 666 > /sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq
echo 1674000 > /sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq
chmod 444 > /sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq
chmod 666 > /sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq
echo 384000 > /sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq
chmod 444 > /sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq

chmod 666 > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor
echo ondemand > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor
chmod 444 > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor
chmod 666 > /sys/devices/system/cpu/cpu3/cpufreq/scaling_max_freq
echo 1674000 > /sys/devices/system/cpu/cpu3/cpufreq/scaling_max_freq
chmod 444 > /sys/devices/system/cpu/cpu3/cpufreq/scaling_max_freq
chmod 666 > /sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq
echo 384000 > /sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq
chmod 444 > /sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq

echo 4 > /sys/devices/system/cpu/cpufreq/ondemand/down_differential
echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/enable_boost_cpu
echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/ignore_nice_load
echo 1026000,1026000,810000,810000 > /sys/devices/system/cpu/cpufreq/ondemand/input_event_min_freq
echo 0 > /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy
echo 918000 > /sys/devices/system/cpu/cpufreq/ondemand/optimal_freq
echo 0 > /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias
echo 3 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor
echo 20000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate
echo 10000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate_min
echo 594000 > /sys/devices/system/cpu/cpufreq/ondemand/sync_freq
echo 20000 > /sys/devices/system/cpu/cpufreq/ondemand/ui_sampling_rate
echo 80 > /sys/devices/system/cpu/cpufreq/ondemand/ui_timeout
echo 90 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo 80 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_any_cpu_load
echo 70 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_multi_core

# Set IO Sheduler

echo bfq > /sys/block/mmcblk0/queue/scheduler

# Set IO read ahead

echo 512 > /sys/block/mmcblk0/queue/read_ahead_kb
Wow that took me way longer than I thought.. :laugh:
 

poondog

Inactive Recognized Contributor
Dec 11, 2011
14,998
12,950
113
Melbourne
Wow that is one messy script.... :silly:

Firstly none of the lines from '#Fast Charge' all the way to '#MultiCorePowersavings' will apply, you've made the same error on all of them haha. Basically I'll take the fast charge one for example, you've written:
Code:
echo 1 /sys/kernel/fast_charge/force_fast_charge
... And what you should've written is:
Code:
echo 1 [B]>[/B] /sys/kernel/fast_charge/force_fast_charge
You forgot to put in the '>' .. Very important as otherwise none of them will apply, fix that on all the lines before the cpu stuff and they'll work. Also if you actually want Sweep2Sleep then the value is 2 not 0.

Now the cpu stuff... (This is gonna be long, so I hid it to prevent a stupidly long post :p)



You've written:
Code:
if [ -e /data/local/cpu_protection ] ; then
echo failed > /data/local/cpu_failed
chmod 777 /data/local/cpu_failed
exit
fi
I don't know where you found this but we don't have a file called cpu_protection in that directory so this command is useless (get rid of it)

Now the next bit:
Code:
echo applied > /data/local/cpu_protection
chmod 777 /data/local/cpu_protection
chmod 666 /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chmod 666 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "1674000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chmod 666 /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "384000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
Change this to:

Code:
chmod 666 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chmod 444 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chmod 666 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1674000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chmod 444 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chmod 666 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 384000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
chmod 444 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
Changes:
  • Deleted cpu protection lines
  • Added chmod 444 lines
  • Fixed chmod lines (put a > in the command)
  • Took out quotation marks on things like 'ondemand' as they are unneeded

Repeat this exact procedure (copy and paste) for cpu1, cpu2 and cpu3. So for example:

Code:
chmod 666 > /sys/devices/system/cpu/cpu[COLOR="Red"]1[/COLOR]/cpufreq/scaling_governor
echo ondemand > /sys/devices/system/cpu/cpu[COLOR="red"]1[/COLOR]/cpufreq/scaling_governor
chmod 444 > /sys/devices/system/cpu/cpu[COLOR="red"]1[/COLOR]/cpufreq/scaling_governor
And so on....

Note: Not 100% sure how long these will apply for, since pnpmgr is still in play, guess that's down to you to test. Theoretically it should work though

Next bit:
Code:
echo 4 > /sys/devices/system/cpu/cpufreq/ondemand/down_differential
echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/enable_boost_cpu
echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/ignore_nice_load
echo 1026000,1026000,810000,810000 > /sys/devices/system/cpu/cpufreq/ondemand/input_event_min_freq
echo 0 > /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy
echo 918000 > /sys/devices/system/cpu/cpufreq/ondemand/optimal_freq
echo 0 > /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias
echo 3 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor
echo 20000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate
echo 10000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate_min
echo 594000 > /sys/devices/system/cpu/cpufreq/ondemand/sync_freq
echo 20000 > /sys/devices/system/cpu/cpufreq/ondemand/ui_sampling_rate
echo 80 > /sys/devices/system/cpu/cpufreq/ondemand/ui_timeout
echo 90 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo 80 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_any_cpu_load
echo 70 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_multi_core
This should stay applied even without chmod'ing every file but imo you shouldn't change these. The stock ondemand values have the perfect balance between performance and battery.

Moving on....
Code:
#GOVERNOR="ondemand"

#echo GOVERNOR /sys/devices/system/cpu/#cpu0/cpufreq/scaling_governor
#echo GOVERNOR /sys/devices/system/cpu/#cpu1/cpufreq/scaling_governor
#echo GOVERNOR /sys/devices/system/cpu/#cpu2/cpufreq/scaling_governor
#echo GOVERNOR /sys/devices/system/cpu/#cpu3/cpufreq/scaling_governor
Completely irrelevant since cpu governor has already been applied previously. Plus as you said without chmod 444'ing the relevant files, the governor's reset to stock values.

Code:
# Set IO Sheduler

SHEDULER="bfq"

echo SHEDULER /sys/block/mmcblk0/queue/scheduler
This'll work once you've fixed the command (forgot the > again) but if you want to shorten the script and make it easier to read, change to:
Code:
echo bfq > /sys/block/mmcblk0/queue/scheduler
And lastly the IO r/a line you need the '>' again.


In case you get completely stuck I made your script but completely fixed up for a reference point:



Wow that took me way longer than I thought.. :laugh:
Ryan,

 

Headless96

New member
Nov 4, 2012
1,055
2,099
0
Cardiff
Guys if anyone's been missing Elemental's mpdecision tweaks or wanted to try them out on this kernel but couldn't, your prayers have been answered! :laugh:

I've created a couple of zips to enable either the MP Decision battery or performance values that Flar has in his aroma installer. I've also thrown in the stock values for good measure (if you want to go back)

The zip includes an init.d script which means the values will persist on boot. Also I've included in the updater-script to delete the other mpdecision scripts meaning if you've flashed one of them previously, it'll get rid of it so there's no overlap

Obviously full credits go to @flar2, I just took the values and packaged it up for you guys

Instructions:
  • Download the zip of your choice
  • Flash through recovery
  • Have a dump
  • Profit :D
.

Edit: @poondog I could update the main script with these if you want? .. I'll leave them disabled but they could be enabled if anyone wants to, up to you :)
 
Last edited:

poondog

Inactive Recognized Contributor
Dec 11, 2011
14,998
12,950
113
Melbourne
Guys if anyone's been missing Elemental's mpdecision tweaks or wanted to try them out on this kernel but couldn't, your prayers have been answered! :laugh:

I've created a couple of zips to enable either the MP Decision battery or performance values that Flar has in his aroma installer. I've also thrown in the stock values for good measure (if you want to go back)

The zip includes an init.d script which means the values will persist on boot. Also I've included in the updater-script to delete the other mpdecision scripts meaning if you've flashed one of them previously, it'll get rid of it so there's no overlap

Obviously full credits go to @flar2, I just took the values and packaged it up for you guys

Instructions:
  • Download the zip of your choice
  • Flash through recovery
  • Have a dump
  • Profit :D
.

Edit: @poondog I could update the main script with these if you want? .. I'll leave them disabled but they could be enabled if anyone wants to, up to you :)
Thanks dude
I think it might be better to keep this stuff separate. Since its less kernel related :) they're welcome here, but it would be great if they're in a separate script imo
 

dsymbol

New member
May 2, 2009
1,054
159
0
Nah you don't really need to wipe caches. I just recommend doing it every now and then
I ran it dual core all day (new test kernel) and I'm sitting at 65% at the end. I do a lot of music streaming with Bluetooth in my car
thanks man!

I'm hoping that your development wont get into all kind of motion gestures frenzy, but stay with good performance & excellent battery life.
I can forfeit a bit of performance (since the m7 is damn fast already) to take much better SOT.

I've been out all day today, 90% of time on 3G & after 19hours of usage, i have 4 hours of SOT.
I'm quite happy with that.

Cant wait to play with the phone tomorrow.
Thank you for your great work.
 

mitas35

New member
Aug 2, 2011
1,046
147
0
Paphos
thanks man!

I'm hoping that your development wont get into all kind of motion gestures frenzy, but stay with good performance & excellent battery life.
I can forfeit a bit of performance (since the m7 is damn fast already) to take much better SOT.

I've been out all day today, 90% of time on 3G & after 19hours of usage, i have 4 hours of SOT.
I'm quite happy with that.

Cant wait to play with the phone tomorrow.
Thank you for your great work.
I wish i could do that to :(, mine is getting hot during calls and i lose 12-10% every hour without touching the phone ,dont know how to fix it ,i am on IC 2.5 kk40.:confused:
 

Rad ryan

New member
Jan 22, 2011
502
239
0
Wow that is one messy script.... :silly:

Firstly none of the lines from '#Fast Charge' all the way to '#MultiCorePowersavings' will apply, you've made the same error on all of them haha. Basically I'll take the fast charge one for example, you've written:
Code:
echo 1 /sys/kernel/fast_charge/force_fast_charge
... And what you should've written is:
Code:
echo 1 [B]>[/B] /sys/kernel/fast_charge/force_fast_charge
You forgot to put in the '>' .. Very important as otherwise none of them will apply, fix that on all the lines before the cpu stuff and they'll work. Also if you actually want Sweep2Sleep then the value is 2 not 0.

Now the cpu stuff... (This is gonna be long, so I hid it to prevent a stupidly long post :p)



You've written:
Code:
if [ -e /data/local/cpu_protection ] ; then
echo failed > /data/local/cpu_failed
chmod 777 /data/local/cpu_failed
exit
fi
I don't know where you found this but we don't have a file called cpu_protection in that directory so this command is useless (get rid of it)

Now the next bit:
Code:
echo applied > /data/local/cpu_protection
chmod 777 /data/local/cpu_protection
chmod 666 /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chmod 666 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "1674000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chmod 666 /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "384000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
Change this to:

Code:
chmod 666 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chmod 444 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chmod 666 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1674000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chmod 444 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chmod 666 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 384000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
chmod 444 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
Changes:
  • Deleted cpu protection lines
  • Added chmod 444 lines
  • Fixed chmod lines (put a > in the command)
  • Took out quotation marks on things like 'ondemand' as they are unneeded

Repeat this exact procedure (copy and paste) for cpu1, cpu2 and cpu3. So for example:

Code:
chmod 666 > /sys/devices/system/cpu/cpu[COLOR="Red"]1[/COLOR]/cpufreq/scaling_governor
echo ondemand > /sys/devices/system/cpu/cpu[COLOR="red"]1[/COLOR]/cpufreq/scaling_governor
chmod 444 > /sys/devices/system/cpu/cpu[COLOR="red"]1[/COLOR]/cpufreq/scaling_governor
And so on....

Note: Not 100% sure how long these will apply for, since pnpmgr is still in play, guess that's down to you to test. Theoretically it should work though

Next bit:
Code:
echo 4 > /sys/devices/system/cpu/cpufreq/ondemand/down_differential
echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/enable_boost_cpu
echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/ignore_nice_load
echo 1026000,1026000,810000,810000 > /sys/devices/system/cpu/cpufreq/ondemand/input_event_min_freq
echo 0 > /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy
echo 918000 > /sys/devices/system/cpu/cpufreq/ondemand/optimal_freq
echo 0 > /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias
echo 3 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor
echo 20000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate
echo 10000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate_min
echo 594000 > /sys/devices/system/cpu/cpufreq/ondemand/sync_freq
echo 20000 > /sys/devices/system/cpu/cpufreq/ondemand/ui_sampling_rate
echo 80 > /sys/devices/system/cpu/cpufreq/ondemand/ui_timeout
echo 90 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo 80 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_any_cpu_load
echo 70 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_multi_core
This should stay applied even without chmod'ing every file but imo you shouldn't change these. The stock ondemand values have the perfect balance between performance and battery.

Moving on....
Code:
#GOVERNOR="ondemand"

#echo GOVERNOR /sys/devices/system/cpu/#cpu0/cpufreq/scaling_governor
#echo GOVERNOR /sys/devices/system/cpu/#cpu1/cpufreq/scaling_governor
#echo GOVERNOR /sys/devices/system/cpu/#cpu2/cpufreq/scaling_governor
#echo GOVERNOR /sys/devices/system/cpu/#cpu3/cpufreq/scaling_governor
Completely irrelevant since cpu governor has already been applied previously. Plus as you said without chmod 444'ing the relevant files, the governor's reset to stock values.

Code:
# Set IO Sheduler

SHEDULER="bfq"

echo SHEDULER /sys/block/mmcblk0/queue/scheduler
This'll work once you've fixed the command (forgot the > again) but if you want to shorten the script and make it easier to read, change to:
Code:
echo bfq > /sys/block/mmcblk0/queue/scheduler
And lastly the IO r/a line you need the '>' again.


In case you get completely stuck I made your script but completely fixed up for a reference point:



Wow that took me way longer than I thought.. :laugh:

Oops, I forgot the > :eek: Linux scripting/workings is still a learning process for me right now. Yes, it is quite messy :) I hadn't taken time to clean it up or take out unused stuff like the repetitive governor set, lazy me.

Wow! :eek: I bet that did take a while :D Thanks a lot for that!

Yeah, those settings turned out to be a little to slow, as I said it was a test of sorts. Although I do disagree with the stock governor settings being perfect balance for everyone bc

it depends on how you use your phone. Here's an example of what I mean: I use A LOT of cpu intensive apps and games, so for me they are not ideal bc if I start a moderately heavy game the cpu will jump to max and stay there when it could run the game at the needed fps at a lower freq and thereby save much battery. This follows suit for cpu intensive apps and in game screens when you are not actively moving character, etc. The first screenshot is the cpu times of stock settings on a heavy 3d game, the second is the same game with some modified Gov settings. In both cases the game ran without any lags or slow downs and I used less battery while playing it. I don't want to UC, so I use the Gov settings to make it scale how I want if possible :)



For most people's everyday use I believe that you are correct that the stock settings are best balance of battery/performance. And thanks for the help with my horribly disarray script :)


I can't :( , I'm immortal :D

Also, I wouldn't want the world to morn. And on top of that, how ever would you manage without my extensive knowledge of Linux to help you along :D

PS ya could've at least threw in a smiley face :)


Guys if anyone's been missing Elemental's mpdecision tweaks or wanted to try them out on this kernel but couldn't, your prayers have been answered! :laugh:

I've created a couple of zips to enable either the MP Decision battery or performance values that Flar has in his aroma installer. I've also thrown in the stock values for good measure (if you want to go back)

The zip includes an init.d script which means the values will persist on boot. Also I've included in the updater-script to delete the other mpdecision scripts meaning if you've flashed one of them previously, it'll get rid of it so there's no overlap

Obviously full credits go to @flar2, I just took the values and packaged it up for you guys

Instructions:
  • Download the zip of your choice
  • Flash through recovery
  • Have a dump
  • Profit :D
.

Edit: @poondog I could update the main script with these if you want? .. I'll leave them disabled but they could be enabled if anyone wants to, up to you :)
Thanks x 2 :)

Sent from my HTC One using Tapatalk
 
Last edited:
Status
Not open for further replies.