Database Develop

SOLVED - Cyanogen 4.1.6 - Compcache Disabled - Still taking up RAM - How to free?

SOLVED: Compcache makes AVAILABLE the section specified by your ROM or userinit. It doesn't reserve the space or partition it. Like what you see below, my TOTAL Mem stayed the same, but the Swap total went up with compcache enabled. Then when I enabled the linux-swap partition, the amount of swap jumped to 56000. Finally, when I disabled compcache the total amount of RAM didn't 'go down' because the space wasn't reserved...it was just available. Thanks to ccyrowski for the help.
Hello Everyone,
First, I did search. That is how I figured out how to disable compcache and enable the swap. It's working great, however since I am no longer using compcache, I would like to make available the RAM that it is using. Here are my free commands:
BEFORE:
# free
free
total used free shared buffers
Mem: 97928 96356 1572 0 8164
Swap: 24476 15516 8960
Total: 122404 111872 10532
AFTER:
# free
free
total used free shared buffers
Mem: 97928 96416 1512 0 300
Swap: 31768 3092 28676
Total: 129696 99508 30188
Notice that the Physical Memory is still the same number, despite compcache being disabled (well, atleast swapoff'd) Here is my userinit and you can see that it's just enabling the swap.
#!/system/bin/sh
##adb push userinit.sh /system/sd/
uname_r=`uname -r`
moddir=`find /system/modules -type d -name $uname_r`
#insmod=/system/bin/insmod
#$insmod $moddir/compcache/xvmalloc.ko;
#$insmod $moddir/compcache/ramzswap.ko disksize_kb=32768;
#$insmod $moddir/compcache/ramzswap.ko backing_swap=/dev/block/mmcblk0p3;
#mknod /dev/ramzswap0 b 253 0;
echo 20 > /proc/sys/vm/swappiness;
# Experimental settings
#echo 1 > /proc/sys/vm/page-cluster; # default: 3 Changes Page clustering from 8 to 2.
#echo 5 > /proc/sys/vm/laptop_mode; # default: 0 Helps keep SSD from getting worn.
#echo 5000 > /proc/sys/vm/dirty_expire_centisecs; # default: 3000
#echo 800 > /proc/sys/vm/dirty_writeback_centisecs; # default: 500
#echo 10 > /proc/sys/vm/dirty_background_ratio; # default: 5
#echo 16 > /proc/sys/vm/dirty_ratio; # default: 10
#
#swapon /dev/ramzswap0;
swapon /dev/block/mmcblk0p3;
#Over Clock CPU when in use, puts at lower freq when idol. # if you don't want it.
#echo 128000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq;
#echo 528000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
QUESTION: Is there any way to re-allocate the compcache section of my physical RAM to be used again? There is that 24476b that I cannot use, as I'm using a swap.
Thanks for your time.
UPDATE:
ccyrowski said:
hahaha, compcache doesn't take up your physical RAM.
Click to expand...
Click to collapse
Ok, so where is it taking from? I understood that compcache is a Compression Swap that runs in RAM. Is that incorrect?

[Q] Overclock Milestone with Cyanogen custom ROM

Does anyone know how to (if at all possible) overclock a Milestone running the CyanogenMod ROM? I've tried Milestone overclock but it only works with the original ROM and reboots my phone instantly after applying changes.
I've also tried using G.O.T. OpenRecovery from Recovery mode to overclock it, and it says it applied successfully, but after booting the phone back into Cyanogen it says it's still at a sad 550MHz.
Any suggestions or apps would be greatly appreciated!!
Thanks

First of all you must be Rooted. (Just mentioning it, I guess you are.. )
Now, with Androidiani Recovery you get a set of Pre-fixed Overclocked sets up to 1.1GHz.
With GOT Recovery you choose the MHz and vsel you want to use.
One time I was flashing a newer ROM, did the Overclock through GOT, it said "Applied successfully" but It didn't work. Problem was I forgot to Root again the phone. So don't forget that.

/system/etc/init.d/10overclock
here is OC, edit it with root explorer

Thanks Babis_ECE... So after overclocking it with GOT I have to ROOT the phone a second time? If so I will try it, but could you explain why?

petyo.tsanov said:
/system/etc/init.d/10overclock
here is OC, edit it with root explorer
Click to expand...
Click to collapse
Found the file with Root Explorer but it won't actually open the file. Also, you say to edit it, is it as simple and changing the MHz or is it more complex than that?

Babis_ECE said:
First of all you must be Rooted. (Just mentioning it, I guess you are.. )
Now, with Androidiani Recovery you get a set of Pre-fixed Overclocked sets up to 1.1GHz.
With GOT Recovery you choose the MHz and vsel you want to use.
One time I was flashing a newer ROM, did the Overclock through GOT, it said "Applied successfully" but It didn't work. Problem was I forgot to Root again the phone. So don't forget that.
Click to expand...
Click to collapse
Thanks Babis_ECE... So after overclocking it with GOT I have to ROOT the phone a second time? If so I will try it, but could you explain why?

You didn't get what I meant. I am just saying, Root again your phone through Recovery (GOT, Androidiani, etc) and then try again to Overclock. I believe it will do the trick.

you say your are running cyanogen already? then dont use GOT open recovery. use androidiani open recovery.
i believe from androidiani you can change overclocks, but normally i just do it myself.
what you do is find that file in root explorer, make root explorer read/write ("R/W"button in the top right), long press the file, open in text editor, and change the values.
you're going to see a part of the file that looks like this:
Code:
echo 58 > /proc/overclock/max_vsel <-change this
echo 900000 > /proc/overclock/max_rate <-change this
#echo "5 900000000 60" > /proc/overclock/mpu_opps
echo "4 700000000 48" > /proc/overclock/mpu_opps <-change this
echo "3 550000000 42" > /proc/overclock/mpu_opps <-change this
echo "2 250000000 30" > /proc/overclock/mpu_opps <-change this
#echo "1 125000000 32" > /proc/overclock/mpu_opps
#echo "0 900000" > /proc/overclock/freq_table
echo "1 700000" > /proc/overclock/freq_table <-change this
echo "2 550000" > /proc/overclock/freq_table <-change this
echo "3 250000" > /proc/overclock/freq_table <-change this

milestonefail said:
you say your are running cyanogen already? then dont use GOT open recovery. use androidiani open recovery.
i believe from androidiani you can change overclocks, but normally i just do it myself.
what you do is find that file in root explorer, make root explorer read/write ("R/W"button in the top right), long press the file, open in text editor, and change the values.
you're going to see a part of the file that looks like this:
Code:
echo 58 > /proc/overclock/max_vsel <-change this
echo 900000 > /proc/overclock/max_rate <-change this
#echo "5 900000000 60" > /proc/overclock/mpu_opps
echo "4 700000000 48" > /proc/overclock/mpu_opps <-change this
echo "3 550000000 42" > /proc/overclock/mpu_opps <-change this
echo "2 250000000 30" > /proc/overclock/mpu_opps <-change this
#echo "1 125000000 32" > /proc/overclock/mpu_opps
#echo "0 900000" > /proc/overclock/freq_table
echo "1 700000" > /proc/overclock/freq_table <-change this
echo "2 550000" > /proc/overclock/freq_table <-change this
echo "3 250000" > /proc/overclock/freq_table <-change this
Click to expand...
Click to collapse
Thanks for the specific details, but I am still missing something. What do I change those values to? Obviously it'll depend on what I want to overclock the phone to, but it's not written as simple as 600MHz or 1GHz. I just don't want to start putting #'s in assuming that I'm doing it right. Sorry to be a pain, but I want to make sure I don't screw up my phone.

gingalls said:
Thanks for the specific details, but I am still missing something. What do I change those values to? Obviously it'll depend on what I want to overclock the phone to, but it's not written as simple as 600MHz or 1GHz. I just don't want to start putting #'s in assuming that I'm doing it right. Sorry to be a pain, but I want to make sure I don't screw up my phone.
Click to expand...
Click to collapse
900000 = 900000 kHz = 900 MHz = .9 GHz
therefore, 600MHz = 600000
1 GHz = 1000000
etc.
the other numbers (60, 48, 42 etc) are the vsel aka the voltage. fyi, stock is 56. you probably dont want to set these too high (like higher than 64, 68 maybe). experiment to see what is stable for your phone. people on this forum gotten pretty low
there's an overclocking thread you can read for more info. just dont try to follow any outdated instructions.

milestonefail said:
900000 = 900000 kHz = 900 MHz = .9 GHz
therefore, 600MHz = 600000
1 GHz = 1000000
etc.
the other numbers (60, 48, 42 etc) are the vsel aka the voltage. fyi, stock is 56. you probably dont want to set these too high (like higher than 64, 68 maybe). experiment to see what is stable for your phone. people on this forum gotten pretty low
there's an overclocking thread you can read for more info. just dont try to follow any outdated instructions.
Click to expand...
Click to collapse
OK, so the fact that the echo has a # in front of it means the overclocking will not reach 900MHz, but the 3 options below it will fluctuate based on what the phone is trying to do? In other words my phone will actually over and under clock itself on the fly anywhere between echo 700000000 (700MHz), 550000000 (550MHz) and 250000000 (250MHz)? So if I change all 3 of those #'s to say 800000000 (800MHz) then it will stay at 800MHz constantly? If I'm right I'm assuming I'll have to change the 700000, 550000 and 250000 #'s all to 800000 as well?

gingalls said:
OK, so the fact that the echo has a # in front of it means the overclocking will not reach 900MHz, but the 3 options below it will fluctuate based on what the phone is trying to do? In other words my phone will actually over and under clock itself on the fly anywhere between echo 700000000 (700MHz), 550000000 (550MHz) and 250000000 (250MHz)? So if I change all 3 of those #'s to say 800000000 (800MHz) then it will stay at 800MHz constantly? If I'm right I'm assuming I'll have to change the 700000, 550000 and 250000 #'s all to 800000 as well?
Click to expand...
Click to collapse
those first two lines (with the 900000 and 58 in my case) are counted as well. so there are 4 levels. for me they are 900 MHz, 700, 550, and 250. you might want to install the SetCPU app as well so you can see and manage the steps. also, if you change the first one to 800000, it wont stay at 800 constantly. it will ramp up to that frequency when needed, but it will lower itself to one of the lower frequencies when you dont need that much processing power.
just so you know, every line that starts with # is a commented out line (doesnt affect the code)

Babis_ECE said:
You didn't get what I meant. I am just saying, Root again your phone through Recovery (GOT, Androidiani, etc) and then try again to Overclock. I believe it will do the trick.
Click to expand...
Click to collapse
Unfortunately this did not work

gingalls said:
Unfortunately this did not work
Click to expand...
Click to collapse
its not going to work because you cant use GOT open recovery with cyanogen mod

[Root][Guide][MT6795] Improve the responsiveness and battery life on your X9

Update : Aug 8th 2017
These settings should benefit any helio X10 device maybe even other mediatek octa core devices.
The idea behind these settings is to keep the CPU in the lower frequency states and prevent unnecessary power drain when performing simple tasks.
to apply these settings I used Kernel Aduitor.
First Up Interactive Governor Settings
Code:
[SIZE="3"]Above hispeed delay - 20000 1326000:30000 1469000:40000 1781000:10000
Bootpulse duration - 0
hispeed freq - 1183000
boost - 0
go hispeed load - 70
io is busy - 0
min sample time - 20000
target loads - 60 1183000:80 1326000:90 1469000:97 1625000:99
timer rate - 25000
timer slack - 35000[/SIZE]
Limit you CPU to 1781MHz To save some battery all 1.9GHz does is produce heat and the performance isn't worth it.
Also you must disable touch-boost by editing the build prop line; ro.mtk_perfservice_support=1 to ro.mtk_perfservice_support=0
This will save a lot of battery life as the CPU won't jump to high frequencies when you touch the screen.
Also in Virtual Memory settings set the folowing
dirty ratio - 90
dirty background ratio - 80
dirty expire centisecs - 1000
dirty writeback centisecs - 2000
swappiness - 40
vfs cache pressure - 10
Z-RAM disksize - 300MB
Next up....... RAM management so the HTC X9 RAM management is good but it can be made better by going into the low memory killer tab in Kernel Auditor and tapping on the light option.
and that is it. we can't do much without a custom Kernel......... Also you can increase entropy by changing it's read value to 1664 and write value to 2048. I don't know if this is needed on marshmallow but I did it anyway.
Even more battery Savings
You will need Tasker for the following.............
Note: This Will limit your CPU to 5 cores and reduce unecessary CPU Scaling also will disable some bug checks
Make a new 'device boot' profile and add the following as tasks
1. Wait 30s
2.Run Shell:
Code:
[SIZE="3"]
su
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/pvrsrvkm/parameters/gPVRDebugLevel
echo "0" > /sys/module/musb_hdrc/parameters/debug_level
echo "0" > /sys/module/lowmemorykiller/parameters/debug_level
echo "5" > /proc/hps/num_limit_low_battery
echo "5" > /proc/hps/num_limit_power_serv
echo "5" > /proc/hps/num_limit_thermal
echo "5" > /proc/hps/num_limit_ultra_power_saving
echo "99" > /proc/hps/up_threshold
echo "90" > /proc/hps/down_threshold
echo "0" > /proc/hps/rush_boost_enabled
echo "0" > /proc/hps/input_boost_enabled
echo "1781000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "1781000" > /proc/cpufreq/cpufreq_limited_max_freq_by_user
echo "0" > /proc/gpufreq/gpufreq_input_boost
echo "0-4" > /dev/cpuset/foreground/cpus
[/SIZE]
Make Another tasker Profile 'on device unlock'
1.Run Shell;
Code:
[SIZE="3"]
su
echo "99" > /proc/hps/up_threshold
echo "90" > /proc/hps/down_threshold
echo "0" > /proc/hps/rush_boost_enabled
echo "0" > /proc/hps/input_boost_enabled
[/SIZE]
Credits;
jajk - Learned a lot from his Skinny Custom Boot thread.

I haven't noticed any freezing on my device. Everything runs smoothly all the time.
I will test your settings if it starts annoying me.
I guess the x9 isn't the most popular phone for rooters.

m3johan said:
I haven't noticed any freezing on my device. Everything runs smoothly all the time.
I will test your settings if it starts annoying me.
I guess the x9 isn't the most popular phone for rooters.
Click to expand...
Click to collapse
nope

thx.methods u said work on my htc x9.but like the 'Even more battery Savings' i not done yet

Htc one x9
Hello, am new here. I came on here cos I need help with my HTC One X9. You have to forgive me if I ask dumb questions cos like I said earlier, am new to everything here. So please be patient with me.
While in use, my fone drops from say 90% to zero and then shuts down. After a while when I turn it on, battery returns to 90%. At other times, while in use it shuts down even when charging....in this state it reboots several times and gets very hot.
Please what can I do? Thank you.

Lord Dre said:
Hello, am new here. I came on here cos I need help with my HTC One X9. You have to forgive me if I ask dumb questions cos like I said earlier, am new to everything here. So please be patient with me.
While in use, my fone drops from say 90% to zero and then shuts down. After a while when I turn it on, battery returns to 90%. At other times, while in use it shuts down even when charging....in this state it reboots several times and gets very hot.
Please what can I do? Thank you.
Click to expand...
Click to collapse
It's battery problem, Chagne it

[HMP/EAS] 8-12hr SOT Artisan governor tweaks

THIS GOVERNOR HAS STANDED THE TEST OF TIME
AND IS RELIABLE WITH SPEED AND BATTERY LIFE
SOT IS AROUND 8-12 HRS REGULARLY BUT RESULTS MAY VARY BASED ON USAGE AND USERSPACE
Edit-
In a short amount of time we accomplished a lot, 12hr to 14+ hr SOT runs without compromising performance thru being efficient (check OP and thread for screenshots).
For best results I encourage everyone who wants to use this mod to make sure you install these files in the correct path with permissions, and those paths changes depending upon if you have init.d support thru system/etc/init.d or thru su.d or thru magisk/.core/post-fs-data.d (note: for magisk install you can only find correct path thru enabling show hidden files in ESBowser)
Furthermore; I found that using Deeznuts with my modified init.sony.cpu_parameter.sh installed to be the best setup in terms of this mod but try it out and switch it up if need be, I appreciate everyone's time and gratitude.
Want to support my work? Please feel free to buy me a coffee
https://PayPal.me/smacsmack206
NEWEST DEVELOPMENT:
Working on a new DEEZNUTS that will work with EAS. I got a test version working with all the necessary coded trimmed
And all applicable values still within the script.
This is great for me, hope everyone is as excited as I am.
S/O to _LLJY for making EAS on the XZ, a first of many.
DISCLAIMER: (YOU CAN ONLY USE THESE ON A EAS ROM.
https://forum.xda-developers.com/xp...ect-energy-aware-scheduler-xperia-xz-t3639515)
Alright I got a special release for y'all
I updated DEEZNUTS9-EAS and releasing for the first time DEEZNUTS9-EAS_ULTRA.
And for the first time these are TWRP flashable!!
so no longer will you have to worry about install instructions, just flash and done.
DEEZNUTS9-EAS: Uses Energy aware scheduling SCHEDUTIL CPU governor with my custom algorithms, schedtune/Powerhal Vox configs, and applicable miscellaneous optimizations from DEEZNUTS9. Also contains special thermal config to increase stock throttling points for less throttling
DEEZNUTS9-EAS_ULTRA: Uses Energy aware scheduling PWRUTILX CPU governor with my custom algorithms, schedtune/Powerhal Vox configs, and applicable miscellaneous optimizations from DEEZNUTS9.
Also contains special thermal config to increase stock throttling points for less throttling
(NOTE: YOU CAN ONLY USE EAS_ULTRA IF THE YOU HAVE PWRUTILX AVAILABLE AS A GOVERNOR ALREADY ON EAS ROM, ONLY SOME VERSIONS HAVE THIS.)
Download:
DEEZNUTS9-EAS
https://drive.google.com/file/d/0B2bXgjj9jECcTEJYMkJMUi1fZzg/view?usp=drivesdk
DEEZNUTS9-EAS_ULTRA
https://drive.google.com/file/d/0B2bXgjj9jECcSGdGT1NtcUdtLXM/view?usp=drivesdk
*The Best Recommended EAS Version* = DEEZNUTS9-EAS_ULTRA
PORTS:
By request i have been expanding my script and changing it to work on other SOC's and Devices, i'm currently working on a few devices port so the thread lately has been flooded with back and forth regarding this. if you want me to make a version of DEEZNUTS for your device, let me know in the thread and ill let you know what i need to get started, however i do not own the devices you will inquire about so know it wont ever be as good as my 12hr SOT Xperia XZ version.
Going to start posting links to new threads I'll be creating for other devices here to the original, will work on creating more threads later on
Galaxy S5 DEEZNUTS Port thread :
https://forum.xda-developers.com/galaxy-s5/development/artisan-interactive-governor-port-t3624316
DEEZNUTS7-SE PERFORMANCE SCREENRECORD:
*The Best Recommended HMP Version* = DEEZNUTS8-SE
DEEZNUTS8-SE Changelog:
Added Wifi sleeper
Added Disable Fast dormancy
Re-Introduced LMK with new values
Added Kill GMS/Gapps
Added Kill Common Services
Added Network GMS Kill
Added DEEZNUTSSecretSauce
QuickBoot and changed Timer_rate
More but forgotten most the stuff I did in the last week
These screenshots are from my test group members
This is the best version of DEEZNUTS yet highly advised to update to latest Special Edition 8
DOWNLOAD:
https://github.com/Smacksmack206/Sony-Xperia-XZ/blob/master/DEEZNUTS8-SE
#Go_Team_Duality
SPECIAL THANKS TO @NYCHitman1 & @Alcolawl
As they are the original creators of Drunksauce Governor on the Nexus 5X and also helped me with getting a port established for our Sony Xperia XZ (depreciated gov use deeznuts now)
@_LLJY as he's my duality teamate, he's contributed lazyplug and adreno idler values
In DEEZNUTS3, and I been using them ever since,
He even baked an edit of DEEZNUTS in his rom :good:
And he just recently contributed Hi Performance Audio DAC custom voltages in DEEZNUTS8
DOWNLOAD:
Original DEEZNUTS w/ android version check included (depreciated)
https://github.com/Smacksmack206/Sony-Xperia-XZ/blob/readme-edits/Deeznuts
DEEZNUTS
-VERSION 2-
Deeznuts is now on Version 2, cleaned up code better battery and performance
-VERSION 3 CHANGELOG-
Recent update on DEEZNUTS a few weeks ago with the help of @_LLJY
Adreno idler
Lazyplug
Added Pdesire's kernel values
Added partial EAS Support
Removed Overclocking for EAS
Trimmed code improved execution speed by 50%
-DEEZNUTS (XZ version 4) CHANGELOG -
Reconfigured thermal settings to values I'm using currently on my device, I've noticed frequencies are more stable and heavy loads speeds have improved.
Also re-added GPU values and changed to simple_ondemand
And added lines of code to remove InputBoost
Coming in next update: I'll be re-adding Android version check to auto apply best settings like in original Deeznuts before version 3
-DEEZNUTS (XZ version 4.a) CHANGELOG -
Spent a couple hours while I had free time at work testing new target loads and above speed delays while using a frequency overlay opening apps and doing my usual task and executing my script thru EXKM to retest without rebooting to achieve a greater efficiency without compromising performance, Snapchat now opens and runs smoother than ever, idle is better than ever staying at 307mhz like how I wanted. Scrolling is at I would believe a more optimal freq but probably nominal. It's a great feeling having your phone run the way you want
-DEEZNUTS (XZ version 5) CHANGELOG -
Updated above speed delays
Most of the same settings I updated a few days ago from DEEZNUTS 4.D
Reintroduced Android Version Checker
Deeznuts 6 &-SE to Deeznuts7-SE major update Changelog:
Changed sampling time, timer rate, above speed delay, targetloads to have increased performance and responsiveness
All thermals disabled to fix charging stutters
Added GPU command for setting new max frequency
GPU running at 560 as of deeznuts7
Added Memory read ahead commands to 2048 kb
FS-Trim for data system and cache
G-Services fix
Licenced GNU GPL
Updated memory values added a few new ones
Disabled all system wakelocks
Added new HMP scheduler values while keeping code to send more jobs to big cluster
New ZRAM ramdisk config
Changed Go_hispeed_loads on big/litle cluster for better scaling
Uncapped all freqencies on big/little cluster for full power
Download:
https://github.com/Smacksmack206/Sony-Xperia-XZ/blob/master/DEEZNUTS7-SE
DEEZNUTS 7-SE TO DEEZNUTS8 CHANGELOG
*Lowered scaling while keeping performance from 7-SE*
*Entropy values added*
-write_wakeup_threshold
-Read_wakeup_threshold
*Disabled additional wakelock*
-pwr_dbg
*Low Power Modes for little/big
(cpu0-cpu3)*
lpm_levels/system/pwr/cpu0/fpc-def/idle_enabled
lpm_levels/parameters/sleep_disabled
lpm_levels/parameters/sleep_disabled
*Turn off L2 GDHS (LowPowerMode)*
gdhs/idle_enabled
*Enable dynamic memory bus latency
mem_latency = soc:qcom,memlat-cpu2/governor
soc:qcom,memlat-cpu2/polling_interval
Cpu-freq = soc:qcom,mincpubw/governor
* Enabled Hi performance audio thru DAC *
Added @_LLJY New voltage values for improving power consumption using high performance audio
DOWNLOAD:
https://github.com/Smacksmack206/Sony-Xperia-XZ/blob/master/DEEZNUTS8
Definitely worth the update is it better than your favorite Version of DEEZNUTS so far? You decide
DOWNLOAD FROM GITHUB TUTORIAL:
USING SAVE AS FROM RAW TAB, WHICH IS NEXT TO BLAME TAB AND HISTORY TAB
INSTALLATION FOR NOUGAT USERS / NON MAGISK USERS:
1. ENABLE INIT.D SUPPORT
(Thanks to @Ryuinferno work you can use this app to quickly enable init.d support for your phone with root.
PS: Visit his thread to download his app and leave a thanks if his work helped)
https://forum.xda-developers.com/showthread.php?t=1933849
2. NAVIGATE TO SYSTEM/ETC/INIT.D
PLACE DEEZNUTS SCRIPT IN FOLDER
***CHECK IF SCRIPT HAS A TXT FILE EXTENSION AND REMOVE .TXT BY RENAMING FILE***
3. SET PERMISSIONS TO 777 (RWX-RWX-RWX)
4. REBOOT and your done :good:

Well I'm sure this can go over the SOT I had in the title of this post, but here is some results I've collected over the weeks of testing and porting this Governor.
The best I got so far is around 12hrs SOT which isn't surprising given the fact OnePlus3/3T has a Governor said to hit up to 14 hrs and we use the same chipset SD820 as you know. And HTC 10 also has similar Governors getting great results as well.
Let me know if you tried this how it goes for you cuz I'm sure results will vary for everyone.
***EDIT***
I Will be working on making this more Streamlined so there's better results across the board. my next Commit ill be making over the next course of days will have a better version that will give you that same battery life with more performance. Stay Toned.:good:

Smacksmack206 said:
THIS GOVERNOR HAS STANDED THE TEST OF TIME
ADDITIONAL POTENTIAL BATTERY SAVINGS OPPERTUNITY:
Use a root explorer and go to system/ECT and find the init.qcom.post_boot.sh open file in text editor and scroll all the way to the bottom of the big file. And at theses lines
echo 'N' > /sys/module/msm_thermal/parameters/enabled echo '1' > /sys/module/msm_thermal/vdd_restriction/enabled echo '0' > /proc/sys/vm/laptop_mode echo '60' > /proc/sys/vm/overcommit_ratio echo '70' > /proc/sys/vm/vfs_cache_pressure echo '20' > /proc/sys/vm/dirty_ratio echo '10' > /proc/sys/vm/dirty_background_ratio echo '2000' > /proc/sys/vm/dirty_expire_centisecs echo '3000' > /proc/sys/vm/dirty_writeback_centisecs
.
Click to expand...
Click to collapse
What are we supposed to do with those lines? add them? it's hard to understand.

Rtester said:
What are we supposed to do with those lines? add them? it's hard to understand.
Click to expand...
Click to collapse
Yeah, those are additional and completely optional lines to add to the script. The formatting or line endings just got screwed up. Should read like this:
Code:
echo 'N' > /sys/module/msm_thermal/parameters/enabled
echo '1' > /sys/module/msm_thermal/vdd_restriction/enabled
echo '0' > /proc/sys/vm/laptop_mode
echo '60' > /proc/sys/vm/overcommit_ratio
echo '70' > /proc/sys/vm/vfs_cache_pressure
echo '20' > /proc/sys/vm/dirty_ratio
echo '10' > /proc/sys/vm/dirty_background_ratio
echo '2000' > /proc/sys/vm/dirty_expire_centisecs
echo '3000' > /proc/sys/vm/dirty_writeback_centisecs

Working but phone decrease in speed
Some lagg when sweetching between app

Alcolawl said:
Yeah, those are additional and completely optional lines to add to the script. The formatting or line endings just got screwed up. Should read like this:
Code:
echo 'N' > /sys/module/msm_thermal/parameters/enabled
echo '1' > /sys/module/msm_thermal/vdd_restriction/enabled
echo '0' > /proc/sys/vm/laptop_mode
echo '60' > /proc/sys/vm/overcommit_ratio
echo '70' > /proc/sys/vm/vfs_cache_pressure
echo '20' > /proc/sys/vm/dirty_ratio
echo '10' > /proc/sys/vm/dirty_background_ratio
echo '2000' > /proc/sys/vm/dirty_expire_centisecs
echo '3000' > /proc/sys/vm/dirty_writeback_centisecs
Click to expand...
Click to collapse
Thank you I totally didn't notice that lol I updated the OP. I appreciate you man

karrouma said:
Working but phone decrease in speed
Some lagg when sweetching between app
Click to expand...
Click to collapse
ill work on it to make it a little more streamlined. on my phone it hasn't reduced in speed but theres been something ive been wanting to incorporate into this script that will make it even more better on battery. ill start working on it tonight when I get home from work

Smacksmack206 said:
ill work on it to make it a little more streamlined. on my phone it hasn't reduced in speed but theres been something ive been wanting to incorporate into this script that will make it even more better on battery. ill start working on it tonight when I get home from work
Click to expand...
Click to collapse
Ok.
I have 1 hr increasing in SOT
For exemple album takes more time to load pictures or to open picture clearly. Chrome when adding some tabs also have some laggs. But overall it is working well and have more sot.
Thank you

Confirmed more than 5hrs sot with 60% display
Confirmed more than 5hrs sot with 60% display

Another usage example, i've been using Spotify all day with the screen on at work at 50% brightness also Spotify on extreme streaming quality uses a lot of LTE at the same time, gonna get well over 5hr SOT today. Also using an edited​ version of my port so this new update coming soon is gonna be snapper on performance without sacrificing battery. Stay tuned

karrouma said:
Confirmed more than 5hrs sot with 60% display
Click to expand...
Click to collapse
How did you make chrome take 60%...?

Rtester said:
How did you make chrome take 60%...?
Click to expand...
Click to collapse
All time browsing

karrouma said:
All time browsing
Click to expand...
Click to collapse
I'm browsing all time and I get scared if it gets over 15% after a long day.

Check out my new update its blazing fast and has way better SOT
https://github.com/Smacksmack206/Sony-Xperia-XZ/blob/readme-edits/deeznuts.txt
Remove the .Txt in the file name
Everything else is the same as far as installation goes in the OP

Smacksmack206 said:
Check out my new update its blazing fast and has way better SOT
https://github.com/Smacksmack206/Sony-Xperia-XZ/blob/readme-edits/deeznuts.txt
Remove the .Txt in the file name
Everything else is the same as far as installation goes in the OP
Click to expand...
Click to collapse
Renaming - editing deeznuts.txt to deeznuts
It works without laggs after deleting the 99governor file.
99gov do some laggs

karrouma said:
Renaming - editing deeznuts.txt to deeznuts
It works without laggs after deleting the 99governor file.
99gov do some laggs
Click to expand...
Click to collapse
That's correct, only use one script at a time. Ultimately Deeznuts is the one you want to be using. Because drunksauce was designed originally for the sd808/810 and those chipset were more exponential as clock speeds increase, but our sd820 is very different as clock speeds increases it's more liner, so Deeznuts is more optimized for our sd820 and more performance oriented while saving battery. #cheers

Smacksmack206 said:
That's correct, only use one script at a time. Ultimately Deeznuts is the one you want to be using. Because drunksauce was designed originally for the sd808/810 and those chipset were more exponential as clock speeds increase, but our sd820 is very different as clock speeds increases it's more liner, so Deeznuts is more optimized for our sd820 and more performance oriented while saving battery. #cheers
Click to expand...
Click to collapse
Yes
Now it is working fine

I'm glad it's working properly on your end as well. show me what your battery life is like now with all that added performance when you can. :good:

karrouma said:
Yes
Now it is working fine
Click to expand...
Click to collapse
If you're running my ROM please do not use this tweak, they will conflict, if u want i can make a special version for my ROM (for the people who want to use it) if the op allows
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
Smacksmack206 said:
THIS
ADDITIONAL POTENTIAL BATTERY SAVINGS OPPERTUNITY:
Use a root explorer and go to system/ECT and find the init.qcom.post_boot.sh open file in text editor and scroll all the way to the bottom of the big file. And add theses lines to the file
echo 'N' > /sys/module/msm_thermal/parameters/enabled
echo '1' > /sys/module/msm_thermal/vdd_restriction/enabled
echo '0' > /proc/sys/vm/laptop_mode
echo '60' > /proc/sys/vm/overcommit_ratio
echo '70' > /proc/sys/vm/vfs_cache_pressure
echo '20' > /proc/sys/vm/dirty_ratio
echo '10' > /proc/sys/vm/dirty_background_ratio
echo '2000' > /proc/sys/vm/dirty_expire_centisecs
echo '3000' > /proc/sys/vm/dirty_writeback_centisecs
And reboot, it should help save you a ton of battery as Sony messed up the nougat update memory settings. This with the init scripts in this forum or other sd820 device's / greenify / herb optimizer / and nap time should do wonders for your battery .
Click to expand...
Click to collapse
echo '0' > /proc/sys/vm/laptop_mode
echo '60' > /proc/sys/vm/overcommit_ratio
echo '70' > /proc/sys/vm/vfs_cache_pressure
echo '20' > /proc/sys/vm/dirty_ratio
echo '10' > /proc/sys/vm/dirty_background_ratio
echo '2000' > /proc/sys/vm/dirty_expire_centisecs
echo '3000' > /proc/sys/vm/dirty_writeback_centisecs
Removed a couple of values, they cause CPU frequency to be unstable. Also, i have a ZHANA based governor, would you like to add it to your op?

_LLJY said:
If you're running my ROM please do not use this tweak, they will conflict, if u want i can make a special version for my ROM (for the people who want to use it) if the op allows
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
echo '0' > /proc/sys/vm/laptop_mode
echo '60' > /proc/sys/vm/overcommit_ratio
echo '70' > /proc/sys/vm/vfs_cache_pressure
echo '20' > /proc/sys/vm/dirty_ratio
echo '10' > /proc/sys/vm/dirty_background_ratio
echo '2000' > /proc/sys/vm/dirty_expire_centisecs
echo '3000' > /proc/sys/vm/dirty_writeback_centisecs
Removed a couple of values, they cause CPU frequency to be unstable. Also, i have a ZHANA based governor, would you like to add it to your op?
Click to expand...
Click to collapse
I use the Deeznuts gov I created recently it's based of Xana extreme with my revisions I put I op already. Don't think our govs can be too much different, and probably won't make to much of a difference if people use it on your ROM or not. I would encourage users to test but keep a backup because who knows it's might be better using my governor with your ROM vs xlisten that I was just using. I havent tried your rom yet but I hear it's good I'm in the process of trying it out I'll let you know what I think, hopefully if I'm right than your ROM is a better base to apply my tweak to, so if I got 12hrs close to 13 on the other ROM, it could be more on yours IMO

Scene slider for media device volume control?

Hi,
i need help to create a slider in a scene to control some things on my Sony Android TV or Onkyo AV Receiver.
Onkyo: Master Volume Control
I can send an eISCP command via shell > echo > nc to the Onkyo in hex format like:
For absolute master volume of 25 > MVL19 (in hex format):
Code:
echo -e 'ISCP\x00\x00\x00\x10\x00\x00\x00\x08\x01\x00\x00\x00!1MVL19\x0D' | nc 192.168.10.6 60128
For up & down master volume (if a command has more then 5 letters then x08 needs changed to x0A):
Code:
echo -e 'ISCP\x00\x00\x00\x10\x00\x00\x00\x08\x01\x00\x00\x00!1MVLUP\x0D' | nc 192.168.10.6 60128
Code:
echo -e 'ISCP\x00\x00\x00\x10\x00\x00\x00\x0A\x01\x00\x00\x00!1MVLDOWN\x0D' | nc 192.168.10.6 60128
It is also possible to stack commands with an " , ".
I can send a status question for the master volume to the Onkyo (but didn't know yet how to get this into Tasker ):
Code:
echo -e 'ISCP\x00\x00\x00\x10\x00\x00\x00\x0A\x01\x00\x00\x00!1MVLQSTN\x0D' | nc 192.168.10.6 60128
Maybe anyone can help here a bit to polish my Tasker Media Remote Scene.
Hoping also for a Tasker update to set a scene as a widget!