Thanks for the info/reports.Yes, it ran as root. There is swapon, swapoff, swapit files in /system/xbin. If I'm not mistaken, the mount command should be this, right?
BTW, I set TE to runCode:mount -o remount,rw /system
automatically each time I open TE. So I actually dunno why I have those errors. I'm using busybox 1.21.1-jb bionic if it matters. Maybe I should try another busybox? Oh yeah, the swapon command did not return any invalid argument error. I'll try v4 but you'll have to wait a few hours because I'm going out soon.Code:su mount -o remount,rw /system
Edit: I tried v4, no more read only file system errors, but there is still the invalid arguments error.
Does the invalid argument affect anything? Because overall I'm actually noticing a definite increase in performance.Code:Please wait while I create the swap file and boot script according to your specifications. It could take 1-5 minutes. swapoff: /storage/emulated/legacy/swapfile: Invalid argument 360+0 records in 360+0 records out 377487360 bytes transferred in 40.941 secs (9220276 bytes/sec) Setting up swapspace version 1, size = 377483264 bytes UUID=861e05f3-9419-49df-93cd-644256fe4600 swapon: /storage/emulated/legacy/swapfile: Invalid argument
Sent from my GT-P7500 using Tapatalk HD
Both remount commands are valid, but I guess some devices only like certain variations of the command…guess which one mine likes, lol. At any rate at least this problem is solved.
Regard the invalid argument: I am thoroughly bewildered
Code:
<command> <location of a file or directory>
Code:
swapon $storage/swapfile
and
swapoff $storage/swapfile
The fact that you’re getting invalid argument errors for these two commands will result in two things: (1) the very first time you ran “swapit_v4” swap was NOT turned on in that session unless you did that swapon command in the same session [but for all subsequent sessions (i.e. after all future reboots) it WILL/should be turned on being that if you look at the init.d script it should contain the long version of the swapon command that seems to work for you…check with the --free-- command you should see swap being used]; and (2) if you run “swapit” in future sessions you probably will NOT be able to change the swapfile size because if swap is not turned off you cannot delete the swapfile…if you want to change the swapfile size you’ll probably have to do this command
Code:
swapoff /storage/emulated/legacy/swapfile
I will continue looking in to this problem, but thus far my research is drawing blanks. I doubt it is busybox related since the mkswap command does not return an error, but I suppose it is possible for whatever reason the swapon and swapoff applets in your busybox don’t like variables…you could try the one from the V6 starter kit, it’s the one I use.
I’m sorry this is beyond my knowledge, I feel bad such a cool user is having problems :crying:. I attached a custom version that uses the long versions of the commands for swapon and swapoff, which should give the script 100% functionality for you :good:…it’s flashable since I see you’re using that option.
Attachments
-
594.5 KB Views: 1,067
Last edited: