[Q] sched_rt_period_us and sched_rt_runtime_us effective? - Android Q&A, Help & Troubleshooting

I use the following commands in a terminal app.
sysctl -w kernel.sched_rt_runtime_us=-1;
sysctl -w kernel.sched_rt_period_us=100000;
sysctl -w kernel.sched_rt_runtime_us=50000;
I verified the values are really updated by using root explorer.
The phone should be slowed down, but I get similar cpu marks in antutu as before.
Are these parameter really effective?
What is the correct way to apply them?
Thanks!!

Related

[MOD]Sick Speed Tweaks~Get the most out of your ROM !!

Does NOT work with aosp roms, sorry...
This is what i use in my rom and it works great. I have tried these script with a few other roms and the work with them too.
They make the roms snappy and very fast. Also give a boost in quandrant scores.
Some roms adjust some of the settings in these scripts too but i havent had ant errors with any roms i have tried. Please post if you have any issues with anything.
Devs feel free to add to your roms just leave the #smokin1337 in the scripts if ya dont mind.
Lowered the dalvik heap, will add more later ...
Just flash the zip in recovery to install
EDIT:
v1.1
Since a few people won't use this without basic info here it is:
This script will work with any 2.3.4 rom and afaik aosp or sense but i don't use aosp so i can't say for sure.
The scripts include:
Kernel tweaks
VM tweaks (swappiness, minfree, adj, etc.)
Optimized mounts
Cache Cleanup
SDCard read ahead to 3072
Dalvik Heap to 32 soon to be 48
SQLite Vacuum
tcp tweaks
IO scheduler set to deadline
Chmod User Log Files that go to HTC
Setprop Tweaks are:
VM Props
GUI Tweaks
Video/Pic enhancements
Disable HTC Checkin Service
LCD Density
Disable debug icon
Increase WiFi scan interval to 120 sec.
The Scripts
02sicktweaks
Code:
#!/system/bin/sh
#Sick Tweaks
#smokin1337
rm -f /cache/*.apk
rm -f /cache/*.tmp
rm -f /data/dalvik-cache/*.apk
rm -f /data/dalvik-cache/*.tmp
busybox rm -f /data/system/userbehavior.db
busybox chmod 400 /data/system/usagestats/
busybox chmod 400 /data/system/appusagestats/
busybox mount -o remount,rw,noatime,noauto_da_alloc,nodiratime,barrier=0,nobh /system
busybox mount -o remount,noatime,noauto_da_alloc,nodiratime,nodev,barrier=0,nobh /data
busybox mount -o remount,noatime,noauto_da_alloc,nodiratime,nodev,barrier=0,nobh /cache
export sampling_rate=10000
export up_threshold=65
export READ_AHEAD_KB=3072
if [ -n ${up_threshold} ];
then echo ${up_threshold} > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold
fi
if [ -n ${sampling_rate} ];
then echo ${sampling_rate} > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate
fi
if [ -e /sys/module/lowmemorykiller/parameters/adj ]; then
echo "0,1,2,4,7,15" > /sys/module/lowmemorykiller/parameters/adj
fi
if [ -e /sys/module/lowmemorykiller/parameters/minfree ]; then
echo "2560,4096,6144,12288,14336,18432" > /sys/module/lowmemorykiller/parameters/minfree
fi
if [ -e /sys/devices/virtual/bdi/179:0/read_ahead_kb ]; then
echo "3072" > /sys/devices/virtual/bdi/179:0/read_ahead_kb
fi
# Set io scheduler tweaks for mmc
echo "deadline" > /sys/block/mmcblk0/queue/scheduler
echo "0" > /sys/block/mmcblk0/queue/rotational
echo "2048" > /sys/block/mmcblk0/queue/nr_requests
echo ${READ_AHEAD_KB} > /sys/block/mmcblk0/queue/read_ahead_kb
echo "deadline" > /sys/block/mmcblk1/queue/scheduler
echo "0" > /sys/block/mmcblk1/queue/rotational
echo "2048" > /sys/block/mmcblk1/queue/nr_requests
echo ${READ_AHEAD_KB} > /sys/block/mmcblk1/queue/read_ahead_kb
for i in \ `find /data -iname "*.db"` do \ sqlite3
$i 'VACUUM;'
done
echo "6144 87380 524288" > /proc/sys/net/ipv4/tcp_wmem
echo "6144 87380 524288" > /proc/sys/net/ipv4/tcp_rmem
06sysctl
Code:
#!/system/bin/sh
#sysctl/setprop stuff
#smokin1337
sync
sysctl -w vm.oom_kill_allocating_task=0
sysctl -w fs.nr_open=1053696
sysctl -w fs.inotify.max_queued_events=32000
sysctl -w fs.inotify.max_user_instances=256
sysctl -w fs.inotify.max_user_watches=10240
sysctl -w fs.lease-break-time=10
sysctl -w fs.file-max=165164
sysctl -w vm.swappiness=0
sysctl -w vm.overcommit_memory=1
sysctl -w vm.page-cluster=3
sysctl -w vm.drop_caches=3
sysctl -w vm.min_free_kbytes=4096
sysctl -w vm.dirty_ratio=15
sysctl -w vm.dirty_background_ratio=4
sysctl -w vm.vfs_cache_pressure=10
sysctl -w vm.panic_on_oom=0
sysctl -w vm.dirty_expire_centisecs=200
sysctl -w vm.dirty_writeback_centisecs=500
sysctl -w kernel.sem=500,512000,64,2048
sysctl -w kernel.msgmax=64000
sysctl -w kernel.msgmni=64000
sysctl -w kernel.threads-max=525810
sysctl -w kernel.random.write_wakeup_threshold=256
sysctl -w kernel.random.read_wakeup_threshold=128
sysctl -w kernel.panic=5
sysctl -w kernel.shmall=16777216
sysctl -w kernel.shmmax=268435456
sysctl -w kernel.sched_latency_ns=10000000
sysctl -w kernel.sched_min_granularity_ns=2000000
sysctl -w kernel.sched_wakeup_granularity_ns=0
sysctl -w kernel.sched_compat_yield=1
sysctl -w net.ipv6.conf.default.use_tempaddr=2
sysctl -w net.ipv6.conf.all.use_tempaddr=2
sysctl -w net.ipv6.conf.all.temp_prefered_lft=3600
sysctl -w net.ipv6.conf.default.temp_prefered_lft=3600
setprop cm.filesystem.ready 1
setprop dc.filesystem.ready 1
setprop oxygen.filesystem.ready 1
setprop ro.telephony.call_ring.delay 0
setprop ring.delay 0
setprop windowsmgr.max_events_per_sec 150
setprop windowsmgr.support_rotation_270 true
setprop ro.HOME_APP_ADJ 1
setprop ro.HOME_APP_MEM 2048
setprop dalvik.vm.heapsize 48m
setprop dalvik.vm.stack-trace-file=/data/anr/traces.txt
setprop dalvik.vm.lockprof.threshold=500
setprop dalvik.vm.verify-bytecode=false
setprop dalvik.vm.jniopts=warnonly
setprop ro.ril.hsxpa=3
setprop ro.ril.hsdpa.category =28
setprop ro.ril.gprsclass=12
setprop ro.ril.hep=1
setprop ro.ril.enable.dtm=1
setprop ro.ril.enable.a53=1
setprop ro.ril.htcmaskw1.bitmask=4294967295
setprop ro.ril.htcmaskw1=14449
setprop ro.ril.hsupa.category=9
setprop ro.ril.def.agps.mode=2
setprop ro.ril.def.agps.feature=1
setprop ro.ril.enable.sdr=1
setprop ro.ril.enable.gea3=1
setprop ro.ril.enable.fd.plmn.prefix=23402,23410,23411
setprop ro.ril.disable.power.collapse=0
setprop ro.media.enc.jpeg.quality=100
setprop ro.media.dec.jpeg.memcap=8000000
setprop ro.media.enc.hprof.vid.bps=8000000
setprop pm.sleep_mode=1
setprop persist.adb.notify=0
setprop ro.config.htc.nocheckin=1
setprop ro.config.nocheckin=1
setprop wifi.supplicant_scan_interval=120
setprop ro.sf.lcd_density=240
Hope that helps...
V1.1 has more tweaks, so i'll leave the original in case you dont want the extra ones the ones in code above is from v1.1
Post some results here...
smokin1337 said:
This is what i use in my rom and it works great. I have tried these script with a few other roms and the work with them too.
They make the roms snappy and very fast. Also give a boost in quandrant scores.
Some roms adjust some of the settings in these scripts too but i havent had ant errors with any roms i have tried. Please post if you have any issues with anything.
Devs feel free to add to your roms just leave the #smokin1337 in the scripts if ya dont mind.
Just flash the zip in recovery to install
Post some results here...
Click to expand...
Click to collapse
Thank you sir!
hTc Evo [3D]
What exactly does this script do? this is like giving me a pill and just telling me it will cure cancer with no explanation
Thaxx said:
What exactly does this script do? this is like giving me a pill and just telling me it will cure cancer with no explanation
Click to expand...
Click to collapse
If you open the zip and read the scripts you'd see.
It basically changes a bunch of settings on your phone, dalvik heap to 72mb for example, readahead speed increase on the sdcard, a bunch of other stuff.
This is safe for sense and aosp roms?
Sent from my PG06100 using Tapatalk
It's basically all the speed tweaks out and some i found doing some research. It changes quite a few things as the previous poster said check out the scripts and see what they do, which is good practice to do all the time. I edited the values for speed on my rom but it should work with any existing rom.
stinkdified said:
This is safe for sense and aosp roms?
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Should be its all android system edits.
A dalvik of 72 is a terrible, terrible idea, man. (No offense, I'm sure you put a lot of work into this script)
LiquidSolstice said:
A dalvik of 72 is a terrible, terrible idea, man. (No offense, I'm sure you put a lot of work into this script)
Click to expand...
Click to collapse
Whats a good setting ? Seemed ok to me i read some that said higher is better and some said lower is better. Neither seemed to make much difference so i left it high.
smokin1337 said:
Whats a good setting ? Seemed ok to me i read some that said higher is better and some said lower is better. Neither seemed to make much difference so i left it high.
Click to expand...
Click to collapse
It'll be smooth for a while, but the problem with that is that it will take way too long for the garbage collector to come and clean up after the process. There's a better way of explaining it, unfortunately, I'm not sure how to.
smokin1337 said:
It's basically all the speed tweaks out and some i found doing some research. It changes quite a few things as the previous poster said check out the scripts and see what they do, which is good practice to do all the time..
Click to expand...
Click to collapse
how to "check out the scripts and see what they do"?
directions say to just flash it
theres no written explanation of all the tweaks somewhere?
Going to try this now, Thanks bro
SayWhat10 said:
how to "check out the scripts and see what they do"?
directions say to just flash it
theres no written explanation of all the tweaks somewhere?
Click to expand...
Click to collapse
Nah not really i looked them up on google, i adjusted them back and forth to see what helped and what didn't. I'm gonna lower the dalvik heap with the advice of liquid solstice to 32 just to be safe.
Good stuff man, will report back with results.
Thx..
Sent from my PG86100 using xda premium
question smokin what does this do?
busybox mount -o remount,rw,noatime,noauto_da_alloc,nodiratime,barrier=0,nobh /system
busybox mount -o remount,noatime,noauto_da_alloc,nodiratime,nodev,barrier=0,nobh /data
busybox mount -o remount,noatime,noauto_da_alloc,nodiratime,nodev,barrier=0,nobh /cache
i sort of get it but not really
smokin1337 said:
Nah not really i looked them up on google, i adjusted them back and forth to see what helped and what didn't. I'm gonna lower the dalvik heap with the advice of liquid solstice to 32 just to be safe.
Click to expand...
Click to collapse
I would do 64M, gives everything enough room to breathe and it's sort of the 'standard', I guess. Amything more is no bueno as LS pointed out and anything less is limiting our phones. Just my thoughts.
empiire said:
I would do 64M, gives everything enough room to breathe and it's sort of the 'standard', I guess. Amything more is no bueno as LS pointed out and anything less is limiting our phones. Just my thoughts.
Click to expand...
Click to collapse
i thinks 32 is best HTC Put it there for a reason
SayWhat10 said:
how to "check out the scripts and see what they do"?
directions say to just flash it
theres no written explanation of all the tweaks somewhere?
Click to expand...
Click to collapse
I'm sure you can.extract the zip file and inside you'll find text files with the tweaks or such.
Sent from my PG86100 using Tapatalk
Hmmmm....curious...
#SWAG!!!
@ dalvik tweaks
I see a lot of different settings people either go with 32 or 64. On my ROMS I run 48 and am happy with that. I may give 64 a go and see what it does.
@OP - Good job!
smokin1337 said:
Whats a good setting ? Seemed ok to me i read some that said higher is better and some said lower is better. Neither seemed to make much difference so i left it high.
Click to expand...
Click to collapse
The best setting is about 48MB. If it is too big then it takes a long time for the garbage collector to do its thing and the cache can grow to really large levels after you have been running the phone for a while. 48 is a good balance because it allows more space to be used for apps, but isnt so large that the cache's grow crazy big.

Sharing good sysctl settings

Starting this thread to share experiences with any good sysctl settings for the flyer.
What is sysctl?
Sysctl is an interface for examining and dynamically changing parameters in the Linux operating systems.
What is sysctl.conf?
sysctl.conf is a simple file containing sysctl values to be read in and set by sysctl command. The syntax is simply as follows:
# comment
; comment
token = value
Note that blank lines are ignored, and whitespace before and after a token or value is ignored, although a value can contain whitespace within. Lines which begin with a # or ; are considered comments and ignored.
Where is sysctl.conf located?
sysctl.conf is located in /system/etc/ directory on your tablet.
Changing sysctl values
You could pull the file /system/etc/sysctl.conf from your phone, edit the data, push the modified file back to your phone.
However, it is easier (provided that you have init.d) to use a script in /system/etc/init.d/ which is ran at boot time to change the values:
Example via init.d script
You could have a file, e.g. /system/etc/init.d/84sysctl
#!/system/bin/sh
sysctl -w net.ipv4.tcp_fin_timeout=30
(this would change socket FIN timing)
Advantage of doing like this is that you don't have to modify your original /system/etc/sysctl.conf file.
So far I have been using:
sysctl -w vm.dirty_ratio=90
sysctl -w vm.dirty_background_ratio=55
sysctl -w vm.vfs_cache_pressure=10
sysctl -w vm.swappiness=0
sysctl -w vm.panic_on_oom=1
sysctl -w net.core.wmem_max=1048576
sysctl -w net.core.rmem_max=1048576
There are two import settings which control the kernel behaviour with regard to dirty pages in memory. They are:
vm.dirty_background_ratio
vm.dirty_ratio
The first of the two (vm.dirty_background_ratio) defines the percentage of memory that can become dirty before a background flushing of the pages to disk starts. Until this percentage is reached no pages are flushed to disk. However when the flushing starts, then it's done in the background without disrupting any of the running processes in the foreground.
Now the second of the two parameters (vm.dirty_ratio) defines the percentage of memory which can be occupied by dirty pages before a forced flush starts. If the percentage of dirty pages reaches this number, then all processes become synchronous, they are not allowed to continue until the io operation they have requested is actually performed and the data is on disk. In case of high performance I/O machines, this causes a problem as the data caching is cut away and all of the processes doing I/O (the important ones in dCache pool) become blocked to wait for io. This will cause a big number of hanging processes, which leads to high load, which leads to unstable system and crappy performance.
vm.swappiness=0
We don't swap ... so no need.
sysctl -w net.core.wmem_max=1048576
sysctl -w net.core.rmem_max=1048576
Increase the max size of TCP/IP send/receive buffers.
sysctl -w vm.panic_on_oom=1
This enables or disables panic on out-of-memory feature. If this is set to 1, the kernel panics when out-of-memory happens. If this is set to 0, the kernel will kill some rogue process, by calling oom_kill(). Usually, oom_killer can kill rogue processes and system will survive. If you want to panic the system rather than killing rogue processes, set this to 1.
vm.vfs_cache_pressure=10
This is more interesting. File system cache (dentry/inode) is really more important than the block cache above, so we really want the kernel to use up much of the RAM for them. The default value is 100, and what you want to do is lower that value to tell the kernel to favor the file system cache and not drop them aggressively.
i like!!! but how would you change a build.prop property? cause at first i thought sysctl was for changing build prop stuff =X

sched_rt_period_us and sched_rt_runtime_us effective?

I use the following commands in a terminal app.
sysctl -w kernel.sched_rt_runtime_us=-1;
sysctl -w kernel.sched_rt_period_us=100000;
sysctl -w kernel.sched_rt_runtime_us=50000;
I verified the values are really updated by using root explorer.
The phone should be slowed down, but I get similar cpu marks in antutu as before.
Are these parameter really effective?
What is the correct way to apply them?
Thanks!!

[MOD]Data Tweak [ICS/JB][Wifi/3g/4g]

This is a known LINUX Speed Tweak, and i found it on the epic 4g thread that was started by marcusant. So, i'm really just sharing the info with the Xperian community, but I truly think it is quite valuable info, and will likely work on any Android based device since as stated earlier it is a Linux tweak. This has only been tested on ICS, and JB, but I'm pretty sure results will be the same with our XPERIAs...
v2-Changelogs- Completely Rebuild+AROMA INSTALLER (beta)
-CPU Tweaks included
-System Tweaks
-Net Tweaks Updated
-& lots :laugh:More
This is what i did, and for those of you that want to add it yourself, just add this code...
Code:
[SIZE="4"][FONT="Courier New"]
############################
# CPU tweaks #
############################
# Queue size modifications
sysctl -w net.core.optmem_max=20480;
sysctl -w net.unix.max_dgram_qlen=50;
# Net Core Settings
# Location: /proc/sys/net/core
sysctl -w net.core.wmem_max=524288;
sysctl -w net.core.rmem_max=524288;
sysctl -w net.core.rmem_default=256960;
sysctl -w net.core.wmem_default=256960;
############################
# VM & Filesystem tweaks #
############################
sysctl -w fs.lease-break-time=10;
sysctl -w fs.file-max=65536;
sysctl -w vm.overcommit_memory=1;
sysctl -w vm.min_free_order_shift=4;
sysctl -w vm.block_dump=0;
sysctl -w vm.oom_dump_tasks=1;
sysctl -w vm.page-cluster=3;
############################
# Net Speed tweaks #
############################
# UnderUtilized Networking Tweaks below as recommended by avgjoemomma (from XDA)
sysctl -w net.ipv4.tcp_congestion_control=cubic;
# Hardening the TCP/IP stack to SYN attacks
sysctl -w net.ipv4.tcp_syncookies=1;
sysctl -w net.ipv4.conf.all.rp_filter=1;
sysctl -w net.ipv4.conf.default.rp_filter=1;
sysctl -w net.ipv4.tcp_synack_retries=2;
sysctl -w net.ipv4.tcp_syn_retries=2;
sysctl -w net.ipv4.tcp_max_syn_backlog=1024;
sysctl -w net.ipv4.tcp_max_tw_buckets=16384;
sysctl -w net.ipv4.icmp_echo_ignore_all=1;
sysctl -w net.ipv4.icmp_ignore_bogus_error_responses=1;
sysctl -w net.ipv4.tcp_no_metrics_save=1;
sysctl -w net.ipv4.tcp_fin_timeout=15;
sysctl -w net.ipv4.tcp_keepalive_time=1800;
sysctl -w net.ipv4.ip_forward=0;
sysctl -w net.ipv4.tcp_moderate_rcvbuf=1;
sysctl -w net.ipv4.route.flush=1;
sysctl -w net.ipv4.udp_rmem_min=6144;
sysctl -w net.ipv4.udp_wmem_min=6144;
sysctl -w net.ipv4.tcp_rfc1337=1;
sysctl -w net.ipv4.ip_no_pmtu_disc=0;
sysctl -w net.ipv4.tcp_ecn=0;
sysctl -w net.ipv4.tcp_sack=1;
sysctl -w net.ipv4.tcp_fack=1;
[/FONT]
[/SIZE]
AND Lotz More
to a file sysctl.conf (you can use root explorer to make a **NEW** file, or whatever file manager tool you like) then using root explorer copy the file and navigate to /system/etc/ mount as r/w and rename the original sysctl.conf file to sysctl.conf.bak, then paste the one you originally copied (you can add the lines of code to the original file if you are using a edited one already). Then change ownership to root/root, and permissions to rw/r/r, then mount back to r/o, and exit root explorer, and reboot. If it works you should notice your browser opening pages faster, the market much faster, and of course speed test will be faster.
This is highly unlikely, but if this somehow breaks your device I am in no way responsible...
OR SIMPLY-
EXTRACT ZIP ON YOUR SD CARD MOVE sysctl.cfg TO system/etc WITH RW-R--R-- AND
REBOOT
ENJOY FASTESTTTTTTTT.......INTERNET SPEED:angel:
LIKED MY POST PRESS **THANKS**:laugh:​
man !
just i flash it with CMW?
Installation aborted
Waelhh90 said:
man !
just i flash it with CMW?
Click to expand...
Click to collapse
Hi,
installation has been aborted by installing via CWM.
SXP, JB Moonbreaker 3.0, Phantom kernel 1.1.0a, 4.2.A.1.100.
it seems to work. i made a test before with speednet app and it showed like 6-7 mb speed. After tweak 8-8,3
How?
minello09 said:
it seems to work. i made a test before with speednet app and it showed like 6-7 mb speed. After tweak 8-8,3
Click to expand...
Click to collapse
How did you do it? CWM? I even can't find the sysctl.conf file at the system/etc way...
Could you give a detailed explanation?
Waelhh90 said:
man !
just i flash it with CMW?
Click to expand...
Click to collapse
yup or you could move it to system/etc with rw-r--r-- permissions
Dmitry Budnikov said:
Hi,
installation has been aborted by installing via CWM.
SXP, JB Moonbreaker 3.0, Phantom kernel 1.1.0a, 4.2.A.1.100.
Click to expand...
Click to collapse
hmm seems error in creating in zip sry for it
other method is you can extract zip an move sysctl.cfg to system/etc with correct permissions:good:
minello09 said:
it seems to work. i made a test before with speednet app and it showed like 6-7 mb speed. After tweak 8-8,3
Click to expand...
Click to collapse
thxx:good::laugh:
.:S!NA:. said:
Could you give a detailed explanation?
Click to expand...
Click to collapse
you just need to extract the zip n place sysctl.cfg to system/etc with corect permisions n njoy fastest internet
@C00ldUdE8655
Can you use edit button and do you know what i mean?
You spam man, 4 replies after eachother is spam ! You can use cut and copy
:::[ Pandemic ..:: JB MoonBreakers 4 Ever :.
Sent From My Xperia P !! Which Old Dinky Toy Device Else !!
workeed for me from 6.8 mbps to 7.6 mbps
yipeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
keep it up
Pandemic said:
@C00ldUdE8655
Can you use edit button and do you know what i mean?
You spam man, 4 replies after eachother is spam ! You can use cut and copy
:::[ Pandemic ..:: JB MoonBreakers 4 Ever :.
Sent From My Xperia P !! Which Old Dinky Toy Device Else !!
Click to expand...
Click to collapse
You take so much of your free time to moderate those forums, please ask to be in that list, so that it will be official.:good:
https://docs.google.com/document/d/1lK5rP103OL3StU3q9iqwX9LU_k8XABeSQIAT3EHCqgM/edit?hl=en_GB&authkey=CIWz1JkM#
lebartman said:
You take so much of your free time to moderate those forums, please ask to be in that list, so that it will be official.:good:
https://docs.google.com/document/d/...eSQIAT3EHCqgM/edit?hl=en_GB&authkey=CIWz1JkM#
Click to expand...
Click to collapse
Yeah indeed @lebartman
but im not an RC anymore so i have no chance
Good tasted
Sent From C6603 Using xda premium
why 2 threads with kinda same thing??
http://forum.xda-developers.com/showthread.php?t=2334492
xperia arc s can use or not?
Anybody plz
can i use it on Xperia ARC S
LockedBL and
using XPeria T ICS 7.2.0 ROM
Pandemic said:
why 2 threads with kinda same thing??
http://forum.xda-developers.com/showthread.php?t=2334492
Click to expand...
Click to collapse
previous 1 didn't. optimizes like did 1. dis is massive 1 hehe bro try dis one itz amazing
it should b working on all xperiasss try it n post ur review [MENTION]@wasim9283[MENTION]
C00ldUdE8655 said:
it should b working on all xperiasss try it n post ur review [MENTION]@wasim9283[MENTION]
Click to expand...
Click to collapse
yup previous 1 was nt gus as this

Sysctl.conf not working on boot, xiaomi MI8

I put a script in the folder,
/magisk/.core/service.d
but not working.
Code:
#!/system/bin/sh
# grep sysctl /etc/init.d/*
# Load /sys/etc/sysctl.conf
sysctl -p /system/etc/sysctl.conf
sysctl.conf
Code:
vm.panic_on_oom=0
kernel.panic_on_oops=0
kernel.panic=0
#fix
vm.swappiness=90
vm.swap_ratio_enable=1
Who can give me a hand? I have no idea about this problem.
Thanks.
neil78 said:
vm.swappiness=100
Click to expand...
Click to collapse
I guss this value has been locked, no way change it on boot.

Categories

Resources