hello..
I'm using xperia active and I want to configure the zRam..
I currently on stock ICS rom. I use Diskinfo apps to check ram swap and it shows i have 60mb ram swap for default. but i didn't apply any zRam or swap script yet. So use this script to configure the zRam
#!/system/bin/sh
sysctl -w vm.swappiness=60
echo '1' > /sys/block/zram0/reset
echo $((30*1024*1024)) > /sys/block/zram0/disksize
mkswap /dev/block/zram0
swapon /dev/block/zram0
and set it in init.d (i have activate the init.d). I try to set lower value than 60mb which is 30mb but I can't see any changes when I check back at Diskinfo apps..I also check it using terminal emulator by typing "free" but it still same as shown Diskinfo.. Is there any other method can I use to configure the zRam?
p/s : sorry for bad english
pojhe said:
hello..
I'm using xperia active and I want to configure the zRam..
I currently on stock ICS rom. I use Diskinfo apps to check ram swap and it shows i have 60mb ram swap for default. but i didn't apply any zRam or swap script yet. So use this script to configure the zRam
#!/system/bin/sh
sysctl -w vm.swappiness=60
echo '1' > /sys/block/zram0/reset
echo $((30*1024*1024)) > /sys/block/zram0/disksize
mkswap /dev/block/zram0
swapon /dev/block/zram0
and set it in init.d (i have activate the init.d). I try to set lower value than 60mb which is 30mb but I can't see any changes when I check back at Diskinfo apps..I also check it using terminal emulator by typing "free" but it still same as shown Diskinfo.. Is there any other method can I use to configure the zRam?
p/s : sorry for bad english
Click to expand...
Click to collapse
Try running the script in ScriptManager or in Terminal (will need to be run as su). Any errors you see will also be occurring when the init.d script runs. If there aren't any errors and you reset your swap space then maybe your init.d isn't set up correctly. If you lose your new settings during a reboot, then something in the kernel or ROM is setting these values after init.d runs.
This is really weird, i got the same problem with stock kernel. Before, i thought swap wasn't even supported, but it's set in stock kernel, i can't modify it either, but i'm glad i have it on my locked bl, i thought it was impossible.
justmpm said:
Try running the script in ScriptManager or in Terminal (will need to be run as su). Any errors you see will also be occurring when the init.d script runs. If there aren't any errors and you reset your swap space then maybe your init.d isn't set up correctly. If you lose your new settings during a reboot, then something in the kernel or ROM is setting these values after init.d runs.
Click to expand...
Click to collapse
I found it.. the default zRam script actually located at /system/bin/zram_start.sh. So I just edit this script to adjust the desired value of zRam.. Thanks mate!
pojhe said:
I found it.. the default zRam script actually located at /system/bin/zram_start.sh. So I just edit this script to adjust the desired value of zRam.. Thanks mate!
Click to expand...
Click to collapse
Nice, what did you edit? I want to set it to 128
Related
I'm trying get get an init.d script working to set one of the Smartassv2 governor parameters.
This is the script:
Code:
#!/system/bin/sh
echo "100000" > /sys/devices/system/cpu/cpufreq/smartass2/sleep_ideal_freq
When I run the script with Script Manager, the value is written.
When I place the file in the /system/etc/init.d folder (I named the script 99SA2), the value is not written after a reboot (I have set permissions and owner on the file).
I'm running CM7.2-RC1 with Glitch 13.1 and using Voltage Control
Is Glitch recreating values each boot? Is Voltage Control interfering? What else could be interfering??
As a test, add
echo "changing a smartass parameter"
to the script, reboot, and search your Logcat for said message, or search Logcat for the name of the script. If it's not running, Logcat might be able to start helping.
Also, before you reboot, try running
chmod 0755 /system/etc/init.d/*
before rebooting.
Sent from my HTC Sensation Z710e using Tapatalk
I was able to get it working by adding "sleep 60" to the script. It seems that the init.d script was running before the governor was set.
How can i enable or disable zram on nightelf kernel??????
And how do i know if it is enabled or not now??
ALI 9 said:
How can i enable or disable zram on nightelf kernel??????
And how do i know if it is enabled or not now??
Click to expand...
Click to collapse
Search first or use google !!!!
Sent from my Neo V with Supercharged ICS 4.0.4
How to make simple ZRAM init.d script
1. Using Root Explorer, got to /sytem/etc/
init.d/
2. press Menu then create new file
3. paste these in it
#!/system/bin/sh
sysctl -w vm.swappiness=40
echo "1" > /sys/block/zram0/reset
echo $((50*1024*1024)) > /sys/block/zram0/disksize
mkswap /dev/block/zram0
swapon /dev/block/zram0
4. close and save it as 60ZRAM
5. set permission to 777 or "rwxrwxrwx" (tick
all)
6. take note: 50 *1024*1024 = 50MB zram
disksize. if you want to set 30MB, change 50
to 30.
To check download terminal emulator and type
su
free
if you see swap memory, that means thats activated
Source:
http://forum.xda-developers.com/showthread.php?t=1630532
F.A.I.S.A.L said:
How to make simple ZRAM init.d script
1. Using Root Explorer, got to /sytem/etc/
init.d/
2. press Menu then create new file
3. paste these in it
#!/system/bin/sh
sysctl -w vm.swappiness=40
echo "1" > /sys/block/zram0/reset
echo $((50*1024*1024)) > /sys/block/zram0/disksize
mkswap /dev/block/zram0
swapon /dev/block/zram0
4. close and save it as 60ZRAM
5. set permission to 777 or "rwxrwxrwx" (tick
all)
6. take note: 50 *1024*1024 = 50MB zram
disksize. if you want to set 30MB, change 50
to 30.
To check download terminal emulator and type
su
free
if you see swap memory, that means thats activated
Source:
http://forum.xda-developers.com/showthread.php?t=1630532
Click to expand...
Click to collapse
i did all but when i enter
su
free
on terminal it says nt found.. using nightelf 1.5 . any suggestion ?
Then try SetXperia.
No need for scripting.
Just choose "Make swap on boot", set your method in "Edit", e.g. ZRAM, set your size (e.g. 64MB, all above is not recommended), set swappiness (40), reboot, done! :good:
c1ph4 said:
Then try SetXperia.
No need for scripting.
Just choose "Make swap on boot", set your method in "Edit", e.g. ZRAM, set your size (e.g. 64MB, all above is not recommended), set swappiness (40), reboot, done! :good:
Click to expand...
Click to collapse
i hv got a 50 mb swapfile on system ... How to use it? Will it give me more free ram?
@Suranjan16049:
No, RAM is from the manufacturer of the phone. Should be 512MB in Xperia Neo V. Not upgradeable.
Swap will be used if RAM is full. It's Linux-specific. Not needed with modern kernels though.
It seems that all Xperia Kernels that stem back to the DoomLord kernel start the init.d execution twice. While you may think "better twice than never" the nearly parallel execution of scripts can create problems if they concurrently manipulate CPU related tables - or fail to do so due to security mechanisms built in. I was hunting the problem that cpu-clock manipulation from init.d did not work for the scripts generated by System Tuner - finally resulting in this finding.
I checked for sirkay 587c and 587d and for fly-kernel 0.8 as the latest of their breed, quite sure nobody has ever cared about this quirk.
The duplicate execution could be tracked back to the init.rc entries:
Code:
[COLOR=SeaGreen]#DooMLoRD: init.d scripts support
start sysinitsupport
class_start core
class_start main
#DooMLoRD: new init.d scripts support
service sysinitsupport /sbin/sysinitsupport.sh
class main
disabled
oneshot[/COLOR]
Which does:
Code:
#!/sbin/sh
# DooMLoRD: init.d support script (v1)
# [START] setting up
echo "[START] remounting system" > /data/local/tmp/sysinitsupportlog.txt
/sbin/busybox mount -o remount,rw /system >> /data/local/tmp/sysinitsupportlog.txt
# make init.d directory
echo "
[*] make init.d directory" >> /data/local/tmp/sysinitsupportlog.txt
/sbin/busybox mkdir -p /system/etc/init.d >> /data/local/tmp/sysinitsupportlog.txt
# correcting permissions of files in init.d directory
echo "
[*] correcting permissions of files in init.d directory" >> /data/local/tmp/sysinitsupportlog.txt
/sbin/busybox chmod 777 /system/etc/init.d/*
# [COLOR=DarkOrchid]make [/COLOR]init.d directory
echo "
[*] [COLOR=DarkOrchid]make [/COLOR]init.d directory" >> /data/local/tmp/sysinitsupportlog.txt
[COLOR=Red]/system/bin/logwrapper /sbin/busybox run-parts /system/etc/init.d[/COLOR]
# [DONE] all done exiting
echo "[DONE] all done exiting" >> /data/local/tmp/sysinitsupportlog.txt
And later also in init.rc:
Code:
[COLOR=SeaGreen]#DooMLoRD: run my mods
service mymods /sbin/execute_mods.sh
class main
oneshot[/COLOR]
Which then does:
Code:
#!/sbin/sh
# starting
echo "[ START ]" > /data/local/tmp/log_doom-mods.log
echo "" >> /data/local/tmp/log_doom-mods.log
[COLOR=Red]# execute tweaks
/system/bin/logwrapper /sbin/busybox run-parts /etc/init.d[/COLOR]
# execute FPS limit remove
/sbin/mount -t debugfs debugfs /sys/kernel/debug
/sbin/echo '0' > /sys/kernel/debug/msm_fb/0/vsync_enable
/sbin/umount /sys/kernel/debug
echo "FPS limit successfully removed " >> /data/local/tmp/log_doom-mods.log
# DONE
echo "" >> /data/local/tmp/log_doom-mods.log
echo "[ DONE ]" >> /data/local/tmp/log_doom-mods.log
You see that the execution of
Code:
[COLOR=Red]/system/bin/logwrapper /sbin/busybox run-parts /etc/init.d[/COLOR]
is actually done twice - from sysinitsupport.sh first and then again from execute_mods.sh
Also mind that the log-entry in the first is leading in the wrong direction (copy error from above). It should better read "execute init.d directory"
The related logs are found in \data\local\tmp.
You can check yourself with this little script in \etc\init.d:
Code:
#!/system/bin/sh
echo [] > /data/local/tmp/$PPID-exec-done
echo $PPID "init.d executed" >> /data/local/tmp/$PPID-exec-done
date >> /data/local/tmp/$PPID-exec-done
Mind the $PPID which is the parent PID of the executing command (the busybox "run-parts"). Per boot you should just get 1 file <PPID>-exec-done containing the timestamp if you get 2 then you know why...
I have attached the script wrapped in a zip file. Unpack it, copy to \etc\init.d (or if not sym-linked to \system\etc\init.d) and change attributes to "777". Reboot and look what you get in \data\local\tmp.
Once you know, remove the script again and delete the created files in \data\local\tmp.
Mind that the scripts referenced from init.rc are copied over again from the kernel part so any change of the scripts in the \system\sbin folder is useless. The kernel has to fix that, no way out here.
I've been looking into this issue as well with the help of dk_zero_cool (mounts2sd amongst other things) as no matter what I tried I could not get m2sd to run in anything other than Safe Mode because init.d was being run as a service and not being executed in full before the init continued. So far I have edited init.rc to remove the second instance you quote above, and edited the first instance to:
Code:
exec /sbin/sysinitsupport.sh
so it executes rather than running a service. I then edited sysinitsupport.sh to contain just this:
Code:
#!/system/bin/sh
export PATH=/sbin:/system/sbin:/system/bin:/system/xbin
/system/bin/logwrapper busybox run-parts /system/etc/init.d
and also removed the line in execute_mods.sh that relates to init.d, so now theoretically the only thing that should happen in relation to init.d is that the exec command runs sysinitsupport.sh which in turn runs the init.d scripts before anything else in init.rc happens. IN THEORY!!! Because even with all of that done (and I have searched through the whole ramdisk, plus looked at the git for the init binary used in the Lupus ICS kernel I am using to make sure I haven't missed anything) the m2sd init.d script is still running in Safe Mode because it is detecting /system/bin/servicemanager running at the point it tries to execute. So something somewhere is still starting before the execution of init.d. I even tried with the init binary from the latest CM9 build for the Ray to rule out something wrong in there too.
I have sent all my files to dk_zero_cool to see if he can shed any further light on what else may be wrong. I have checked four different Ray kernels and they all use the same DoomLord methods so I doubt whether there are any Ray kernels that are running init.d correctly. It would be great to find a fix for this. Hope more people chip in!
Thanks for opening the discussion
As I understood, you have made some changes in the kernel assembly (not the code) to circumvent the effects you have outlined. I admit that I have not fully understood YOUR concern - but for my double execution of the "run-parts" the deactivation of the relevant line in either of the 2 scripts should do it, or not?
Is your concern related to the situation that init.d cannot do "everything" at the time it is executing and so it cannot achieve what some scripts intend to?
I am far too little educated in the details of kernel execution privileges so cannot further comment on that
Yeah, pretty much - to avoid possible issues with the m2sd script moving stuff around while something else is trying to make use of it the first thing it does is check if servicemanager is running, and if it is it disables the ability to move things like /data and dalvik-cache to sd-ext. The changes that we made in the scripts SHOULD have changed the init.d implementation from it running as a service whilst the rest of the init process carried on, to being executed as a command allowing any init.d scripts to be executed prior to any other service being started - as I understand it this is how init.d was intended to be used (ie the user scripts in /etc/init.d are run fully before anything else). However as I said, even with these changes and everything else relating to init.d having been removed something is still starting servicemanager, and until the source of that can be isolated scripts like m2sd cannot run fully/safely.
I guess the strategy to check on servicemanager is not right here. This is a process that starts several services and should not depend on anything in the init.d. So if you say that the boot sequence would have init.d completed BEFORE any service is started via servicemanager - THEN this could be a flaw in the kernel.
However is that really true? Is there no option to check if certain "dangerous" (for your move purposes) services are active already instead of checking on the servicemanager? I had found a nice overview on the Linux boot process here and I think that somewhere as part of the various init.x excuted scripts the servicemanager simply MUST be started - init.d is just a part of init - and for sure not the first part of it.
Off Topic:
I wonder where I can get some more insight in the Xperia Kernels and how they are assembled - especially which trace of that is noticeable in the filesystem. I noticed that the ICS Kernel have roughly 340MB for the user space while the JB Kernel has 360MB. Device should have 512 MB RAM, then some MB go away for radio and possibly video buffer, but his should be the same for all (accross ICS/JB). So what kind of memory tweaking makes this 20MB difference? I have not found a good place to discuss this - where could I go to?
tobbbie said:
It seems that all Xperia Kernels that stem back to the DoomLord kernel start the init.d execution twice. While you may think "better twice than never" the nearly parallel execution of scripts can create problems if they concurrently manipulate CPU related tables - or fail to do so due to security mechanisms built in. I was hunting the problem that cpu-clock manipulation from init.d did not work for the scripts generated by System Tuner - finally resulting in this finding.
Click to expand...
Click to collapse
How about Radeon kernel? Is there an issue like you said?
Sent from my ST18i using Tapatalk 2
frogerra said:
How about Radeon kernel? Is there an issue like you said?
Sent from my ST18i using Tapatalk 2
Click to expand...
Click to collapse
Just try out (see the guide on 01test.zip) - nothing you can harm doing that.
kernel behaviour trick
I noticed some kernels (GB and ICS) do overwrite settings from /etc/init.d ....
So if you make an init.d script with specific cpu values, or VM settings...some kernel overwrite these with their compiled/preferred values "after" init.d scripts are executed. This way it looks as if your script is not completely accepted by the rom...but the truth is that the kernel applies its own preferred values afterwards.
Thats why my init.d script contains a wait of 60 seconds in the beginning of the scripts......how ? add:
sleep 60
So your script looks like this (example):
#!/system/bin/sh
# this init.d script is for when you apply doomlord kernel supplied with repack 2013
sleep 60
That will run your init.d goodies after one minute.
As you see I'm working on a revived repack4pda 2013 (GB) , which will be released soon in repack4pda thread.
Br.
Michel
I guess that these kernels may be doing the same what you are proposing - just sleep the shell process before action starts. So you need to lookup the call tree from the init process along the various init.*.rc scripts if this is the case. For duplicate execution of init.d content any timed scripts willl not help - the duplicate execution will just happen later as the same script will pause the same amount of time.
Not sure if the init process script execution is synchronous or not - so if you create scripts which sleep, the final signal for "boot completed" may just also delay and the whole boot process may take longer by that sleep time. As well would you just stack the delays after each other and so nothing is gained finally. Synchronous execution would make it impossible that a part of the init process could postpone beyond boot completed.
It may differ if you run the scripts via the "exec" command or let it execute via the servicemanager. I guess the latter may run them asynchronously - not sure here as well.
Hey everyone,
I've been failing miserably to get init.d support on the MIUI 7 developer roms for the Redmi Note 2 and tried every possible thing from this thread on XDA: http://forum.xda-developers.com/showthread.php?t=1933849. I found a couple of posts regarding init.d support on en.miui.com as well, but they are all targeted at MIUI 5/6. Is there anyone who can help me out with this? I would love to get the support to prevent data from leaking at boot (firewall).
Thanks!
Edit 24/01: Flashed Namaless' MIUI Speed MOD which enabled init.d support. Scripts are being executed correctly on boot.
Smiui ?
Have you tried the smiui rom ? http://www.smiui.net/
It works OK on my Redmi Note 2 Prime and claims to have init.d support although I haven't used this feature yet.
Discussed here
http://forum.xda-developers.com/redmi-note-2/development/rom-smiui-rom-kitchen-major-xiaomi-t3225567
I'm using Miui 7 5.11.19
elaurens said:
Hey everyone,
I've been failing miserably to get init.d support on the MIUI 7 developer roms for the Redmi Note 2 and tried every possible thing from this thread on XDA: http://forum.xda-developers.com/showthread.php?t=1933849. I found a couple of posts regarding init.d support on en.miui.com as well, but they are all targeted at MIUI 5/6. Is there anyone who can help me out with this? I would love to get the support to prevent data from leaking at boot (firewall).
Thanks!
Click to expand...
Click to collapse
Pal, this 'switcher' made the magic for me, https://play.google.com/store/apps/details?id=com.broodplank.initdtoggler&hl=it
Redmi Note 2 Prime Dev EU 5.11.1 here
fourlans said:
Have you tried the smiui rom ? http://www.smiui.net/
It works OK on my Redmi Note 2 Prime and claims to have init.d support although I haven't used this feature yet.
Discussed here
http://forum.xda-developers.com/redmi-note-2/development/rom-smiui-rom-kitchen-major-xiaomi-t3225567
I'm using Miui 7 5.11.19
Click to expand...
Click to collapse
Thanks for the tip. Gonna use that as a last resort as I'd rather just run the Chinese developer rom + init.d support (don't really need any of the other features which smiui offers).
oldslowdiver said:
Pal, this 'switcher' made the magic for me, https://play.google.com/store/apps/details?id=com.broodplank.initdtoggler&hl=it
Redmi Note 2 Prime Dev EU 5.11.1 here
Click to expand...
Click to collapse
Installed on 5.11.19 and enabled AfWall+ data leaking fix (script on startup), but it's still not running. Can you tell me which script you managed to get running after enabling init.d through the toggler app?
Thx.
elaurens said:
Installed on 5.11.19 and enabled AfWall+ data leaking fix (script on startup), but it's still not running. Can you tell me which script you managed to get running after enabling init.d through the toggler app?
Thx.
Click to expand...
Click to collapse
These ones:
Strict min free
echo "2048,3072,6144,15360,17920,20480" > /sys/module/lowmemorykiller/parameters/minfree
VM Management
echo "4096" > /proc/sys/vm/min_free_kbytes
echo "0" > /proc/sys/vm/oom_kill_allocating_task;
echo "0" > /proc/sys/vm/panic_on_oom;
echo "0" > /proc/sys/vm/laptop_mode;
echo "0" > /proc/sys/vm/swappiness
echo "50" > /proc/sys/vm/vfs_cache_pressure
echo "90" > /proc/sys/vm/dirty_ratio
echo "70" > /proc/sys/vm/dirty_background_ratio
Normalize Sleeper
mount -t debugfs none /sys/kernel/debug
echo NO_NORMALIZED_SLEEPER > /sys/kernel/debug/sched_features
---------- Post added at 06:17 PM ---------- Previous post was at 06:12 PM ----------
oldslowdiver said:
These ones:
Strict min free
echo "2048,3072,6144,15360,17920,20480" > /sys/module/lowmemorykiller/parameters/minfree
VM Management
echo "4096" > /proc/sys/vm/min_free_kbytes
echo "0" > /proc/sys/vm/oom_kill_allocating_task;
echo "0" > /proc/sys/vm/panic_on_oom;
echo "0" > /proc/sys/vm/laptop_mode;
echo "0" > /proc/sys/vm/swappiness
echo "50" > /proc/sys/vm/vfs_cache_pressure
echo "90" > /proc/sys/vm/dirty_ratio
echo "70" > /proc/sys/vm/dirty_background_ratio
Normalize Sleeper
mount -t debugfs none /sys/kernel/debug
echo NO_NORMALIZED_SLEEPER > /sys/kernel/debug/sched_features
Click to expand...
Click to collapse
You know what.. they actually won't work! I was sure they did, I just checked, and they actually don't. Still, Init.d is enabled.. wtf?
oldslowdiver said:
These ones:
Strict min free
echo "2048,3072,6144,15360,17920,20480" > /sys/module/lowmemorykiller/parameters/minfree
VM Management
echo "4096" > /proc/sys/vm/min_free_kbytes
echo "0" > /proc/sys/vm/oom_kill_allocating_task;
echo "0" > /proc/sys/vm/panic_on_oom;
echo "0" > /proc/sys/vm/laptop_mode;
echo "0" > /proc/sys/vm/swappiness
echo "50" > /proc/sys/vm/vfs_cache_pressure
echo "90" > /proc/sys/vm/dirty_ratio
echo "70" > /proc/sys/vm/dirty_background_ratio
Normalize Sleeper
mount -t debugfs none /sys/kernel/debug
echo NO_NORMALIZED_SLEEPER > /sys/kernel/debug/sched_features
---------- Post added at 06:17 PM ---------- Previous post was at 06:12 PM ----------
You know what.. they actually won't work! I was sure they did, I just checked, and they actually don't. Still, Init.d is enabled.. wtf?
Click to expand...
Click to collapse
Yeah see.. that's my problem with it I can't find the thread back on en.miui.com's forum, but I read earlier today that MIUI uses another way to launch scripts on startup. No further explanation was given though. Weird, maybe I should try the sMIUI ROM and see what it gives.
Enable Init.d on Redmi Note 2
elaurens said:
Yeah see.. that's my problem with it I can't find the thread back on en.miui.com's forum, but I read earlier today that MIUI uses another way to launch scripts on startup. No further explanation was given though. Weird, maybe I should try the sMIUI ROM and see what it gives.
Click to expand...
Click to collapse
Okay, I found the thread you mentioned on MIUI's website (http://en.miui.com/thread-129336-1-1.html), but you need to correct the path as it follows in Terminal Emulator:
Type :
su
sh /storage/sdcard1/term-init.sh
You have to place the term-init.sh inside the internal SD card in this case, download file here https://www.androidfilehost.com/?w=...5e497fa2bc98ce82437cb8cbfbdb4e56c73c1dd621ead
Anyway, if it works, it should create a Test.log file in /data, but it won't
Try your luck
oldslowdiver said:
Okay, I found the thread you mentioned on MIUI's website (http://en.miui.com/thread-129336-1-1.html), but you need to correct the path as it follows in Terminal Emulator:
Type :
su
sh /storage/sdcard1/term-init.sh
You have to place the term-init.sh inside the internal SD card in this case, download file here https://www.androidfilehost.com/?w=...5e497fa2bc98ce82437cb8cbfbdb4e56c73c1dd621ead
Anyway, if it works, it should create a Test.log file in /data, but it won't
Try your luck
Click to expand...
Click to collapse
Cool of you to follow this up The term-init.sh script actually comes from XDA and this is its original thread: http://forum.xda-developers.com/showthread.php?t=1933849. I copied the script to the internal SD card and executed it (with different versions of busybox), the script ran successfully (/system/etc/init.d and other files are created, permissions set correctly), but that Test.log file isn't being created in /data after a reboot. Of course, when I run the following command manually from a terminal, it does create the Test.log file: /system/xbin/busybox run-parts /system/etc/init.d. So for some reasons, the scripts in /system/etc/init.d/ aren't being executed at boot (and my knowledge is too restricted to troubleshoot this further :/)
elaurens said:
Cool of you to follow this up The term-init.sh script actually comes from XDA and this is its original thread: http://forum.xda-developers.com/showthread.php?t=1933849. I copied the script to the internal SD card and executed it (with different versions of busybox), the script ran successfully (/system/etc/init.d and other files are created, permissions set correctly), but that Test.log file isn't being created in /data after a reboot. Of course, when I run the following command manually from a terminal, it does create the Test.log file: /system/xbin/busybox run-parts /system/etc/init.d. So for some reasons, the scripts in /system/etc/init.d/ aren't being executed at boot (and my knowledge is too restricted to troubleshoot this further :/)
Click to expand...
Click to collapse
Exactly. And I found here http://en.miui.com/thread-99174-1-1.html you may edit Build.prop and add
sys.initd = 1
to enable Init.d scripts at boot, but, again, it won't work. So, if anyone finds a solution, please, share.
oldslowdiver said:
Exactly. And I found here http://en.miui.com/thread-99174-1-1.html you may edit Build.prop and add
sys.initd = 1
to enable Init.d scripts at boot, but, again, it won't work. So, if anyone finds a solution, please, share.
Click to expand...
Click to collapse
Haha. Are you oldmyself on the official MIUI forum who gave me the exact same reply in this thread?
elaurens said:
Haha. Are you oldmyself on the official MIUI forum who gave me the exact same reply in this thread?
Click to expand...
Click to collapse
heheheheh small world, it's me.
oldslowdiver said:
heheheheh small world, it's me.
Click to expand...
Click to collapse
Just so you know, I've got init.d support and scripts being executed on boot thanks to @Namaless' MIUI speed mod. I'm currently running the latest version (v.1.19) and AfWall's firewall rules are being applied on boot. Big thanks to him for that
I have a Kata Box 2 with s905 SoC with 1GB of ram
My current ZRAM value is set at 500MB with a swappiness of 60%
I can disable zram or change the swappiness of my ZRAM but I cant seem to change the disk size.
I tried this in the terminal with su
swapoff /dev/block/zram0
echo 1 > /sys/block/zram0/reset
busybox echo 157286400 > /sys/block/zram0/disksize <- I want to lower it from 500mb to 150mb
mkswap /dev/block/zram0
swapon /dev/block/zram0
I checked the value of /sys/block/zram0/disksize and its still set at 500mb or nothing has changed.
I tried to edit the manually but its not saving at all.