Move dalvik-cache to /cache
import /disclaimer.md
Code:
I am not responsible for any damage done to your device/SD card/OTG cable/washing machine etc.
You are responsible for what you do.
If something brakes, it's on you!
This has only been tested on a CM13-based ROM. I have no idea how it will function on other ROMs because of the size of the dalvik-cache directory.
I have found that, on CM13-based ROMs, the dalvik-cache directory is small enough to fit in the /cache partition, giving us several MBs on /data
Current state: Beta
Reason: Not fully tested (on all ROMs)
Comment: Stable enough for daily use
Installation:
Busybox required!
Download the attached zip and flash it in recovery.
Or extract the script from the zip, put it in /system/etc/init.d/ , set the permissions to 755 (rwxr-xr-x) and ownership to 0, 2000 (root, shell).
Uninstallation:
Delete /system/etc/init.d/10dc-linker and /cache/dalvik-cache
To-Do:
Add a size checker
Make suggestions
Bugs:
Found one? Let me know!
Changelog:
v1.0:
First release
Reserved
Didn't work for me on CM13 Xperia SP.
kkumar326 said:
Didn't work for me on CM13 Xperia SP.
Click to expand...
Click to collapse
How much space do you have on /cache?
Also, what exactly is not working?
What is the state of SELinux?
Complete Data
This is what I did:
1) Extracted zip and pasted 10dc-linker in init.d
2) Rebooted phone with twrp recovery
3) Cleared dalvik-cache
4) Rebooted
Result: Nothing happened
Probable cause: Access problem to move/create folders as I couldn't change permissions for /cache , /data and /data/dalvik-cache folders manually using root explorer. It gets reverted back to original. My access was also restricted to root, there was no shell.
Probable fix: Adding script to gain permission to modify/ create in these folders. Plus adding access to both root and shell. I also read somewhere about superuser access to get permission but I couldn't understand.
My cache folder has about 600 MB space and it's completely empty. There is no issue with the space.
Please let me know about your step by step process and probable fixes. Maybe it works.
kkumar326 said:
This is what I did:
1) Extracted zip and pasted 10dc-linker in init.d
2) Rebooted phone with twrp recovery
3) Cleared dalvik-cache
4) Rebooted
Result: Nothing happened
Probable cause: Access problem to move/create folders as I couldn't change permissions for /cache , /data and /data/dalvik-cache folders manually using root explorer. It gets reverted back to original. My access was also restricted to root, there was no shell.
Probable fix: Adding script to gain permission to modify/ create in these folders. Plus adding access to both root and shell. I also read somewhere about superuser access to get permission but I couldn't understand.
My cache folder has about 600 MB space and it's completely empty. There is no issue with the space.
Please let me know about your step by step process and probable fixes. Maybe it works.
Click to expand...
Click to collapse
The script must have 755 or 777 permissions or it won't work.
Also, the zip is flashable. Just flash it in recovery and it will setup everything by itself.
When I flashed it, google-play-services fc like crazy until I restore a backup
Miasaya said:
When I flashed it, google-play-services fc like crazy until I restore a backup
Click to expand...
Click to collapse
What happens if you flash the zip and wipe dalvik-cache?
Does it still fc?
Didn't work with flash
Vagelis1608 said:
The script must have 755 or 777 permissions or it won't work.
Also, the zip is flashable. Just flash it in recovery and it will setup everything by itself.
Click to expand...
Click to collapse
I flashed zip too but nothing happened. No folder was created or moved.
Man use this utility http://forum.xda-developers.com/g2-mini/development/d620-partition-table-tool-t3107664
But choose "optimal" partition layout.
kkumar326 said:
I flashed zip too but nothing happened. No folder was created or moved.
Click to expand...
Click to collapse
Did you wipe dalvik-cache and /cache after flashing?
Lion_Smith said:
Man use this utility http://forum.xda-developers.com/g2-mini/development/d620-partition-table-tool-t3107664
But choose "optimal" partition layout.
Click to expand...
Click to collapse
Sure, go on dev threads and advertise other people's work. That's highly appreciated.
That's why we can't have nice things...
Found the Reason
Vagelis1608 said:
Did you wipe dalvik-cache and /cache after flashing?
Sure, go on dev threads and advertise other people's work. That's highly appreciated.
That's why we can't have nice things...
Click to expand...
Click to collapse
My dalvik-cache is shooting up to 400+ MB, that's why it's not working. I moved /data/dalvik-cache to /cache/dalvik-cache. Then, I used terminal command after su command to link them
Code:
ln -s /cache/dalvik-cache /data/dalvik-cache
It worked but my phone started showing errors with low memory notifications.
1) Is there a way to limit dalvik-cache size?
2) Another approach can be to increase /cache size with with some additional memory e.g. 100 MB, and then following this might work. There will still be a gain of 300+ MB of memory.
Please let me know what's possible.
kkumar326 said:
My dalvik-cache is shooting up to 400+ MB, that's why it's not working. I moved /data/dalvik-cache to /cache/dalvik-cache. Then, I used terminal command after su command to link them
It worked but my phone started showing errors with low memory notifications.
1) Is there a way to limit dalvik-cache size?
2) Another approach can be to increase /cache size with with some additional memory e.g. 100 MB, and then following this might work. There will still be a gain of 300+ MB of memory.
Please let me know what's possible.
Click to expand...
Click to collapse
You can't limit dalvik-cache size, sadly.
If there is enough space for dalvik-cache on /cache, then the script should work.
Also, could you give me the output of this command on a rooted shell?
Code:
ls -l /data/dalvik-cache
It's a small L.
Vagelis1608 said:
You can't limit dalvik-cache size, sadly.
If there is enough space for dalvik-cache on /cache, then the script should work.
Also, could you give me the output of this command on a rooted shell?
Code:
ls -l /data/dalvik-cache
It's a small L.
Click to expand...
Click to collapse
rwxrwxrwx 1 root root [date] [time] /data/dalvik-cache -> /cache/dalvik-cache
kkumar326 said:
rwxrwxrwx 1 root root [date] [time] /data/dalvik-cache -> /cache/dalvik-cache
Click to expand...
Click to collapse
My bad.
I forgot to mention with and without the script installed.
What's the output without the script installed?
Script not working
Vagelis1608 said:
My bad.
I forgot to mention with and without the script installed.
What's the output without the script installed?
Click to expand...
Click to collapse
Script is not doing anything at all as I told earlier. That's why I did it manually.
Lion_Smith said:
Man use this utility http://forum.xda-developers.com/g2-mini/development/d620-partition-table-tool-t3107664
But choose "optimal" partition layout.
Click to expand...
Click to collapse
This is intended to work on a LG G2 Mini, not any other phone.
kkumar326 said:
Script is not doing anything at all as I told earlier. That's why I did it manually.
Click to expand...
Click to collapse
I want the output without it linked.
Related
I update from Cronos Droid Version 1.4 to 1.4.1
In 1.4 rom ，there was about 140M left in my telephone memory
after the update ， there is only 108M left in the telephone memory
then I did this：
adb shell
su
cp -a /data/app /system/sd/
rm -r /data/app
ln -s /system/sd/app /data/app
reboot
there is still 108M left
Then I find the apks exist under data/app also exist under system/sd/app
if i delete the apk under data/app,the same apk will also disappear
WHY
PS after full wipe and I flash the 1.4.1 ,reboot,flash the app2sd.zip ,the phone died,the 1.4.1 means this one :StableCronos_4.1_528_fix_sign.zip
108 sounds about right mate it sounds like before it was moving dalvik cache to sd card as well and now it is not
If you installed some apps from HTC Sync, the copy of the apks could still be on your phone. I can't use adb from work to tell you where it is exactly, but I think it's in /data/local (or something like that, it's in a "local" folder)
Isn't it possible the new rom takes 32mb memerie more than your older rom? I don't know the differences between the roms, but it might be it..
skedone said:
108 sounds about right mate it sounds like before it was moving dalvik cache to sd card as well and now it is not
Click to expand...
Click to collapse
So,how can i move dalvik cache to sd card
kouray said:
If you installed some apps from HTC Sync, the copy of the apks could still be on your phone. I can't use adb from work to tell you where it is exactly, but I think it's in /data/local (or something like that, it's in a "local" folder)
Click to expand...
Click to collapse
yes，you are right
but why the apps in the /data/app??
if you really want to move your Dalvik cache to your sd-card you could flash the latest Ra-Hero recovery image.
it has an option to move Dalvik + apps to your sd-card ( this won't enable apps2sd though )
I dont want to use app2sd as I feel it a bit unnecessary and I really don't need too much more space. I saw WES incorporated moving dalvik cache to the cache partition (cache part is 80 megs that will never get fully used on the slide). I asked in his thread twice but it seems it'll never be seen. Any way, I did some searching and found a script that does exactly what I want. This would also be useful for those like me that just want a few more mb's of internal storage and dont want to use apps2sd. I'm not a developer so I just want to put this here for our devs to mod or give the okay on if this will work on the slide.
I got the script attached from this thread. You can also read in more detail on what exactly it is I'm wanting to do here http://forum.samdroid.net/f9/relocate-dalvik-cache-free-up-space-1117/
I just want to know what has to be done if anything to get this working on the Slide. Thanks
I was able to get dalvik-cache to /cache by going into clockworkmod recovery and accessing from adb:
mv /data/dalvik-cache /cache/dc
ln -s /cache/dc /data/dalvik-cache
After the files are moved and the symlink is created, you should have no problems when rebooting.
However, I came across a problem when I flashed the radio, since it wiped the cache partition. If you are missing all your installed apps in android, it might be that the cache partition was wiped. You need to recreate the /cache/dc folder and reboot.
Thanks for the input. finally someone! ..thats good to know Im going to try it now, I didnt think it would be as simple as a move command.. any reason the radio wipes the cache partition? did dalvik recreate itself after the wipe in /data? and were ALL the apps gone or just the few that took up the memory?
turboyo said:
I didnt think it would be as simple as a move command..
Click to expand...
Click to collapse
Don't forget to make the symbolic link. That is the important command, not the move one.
turboyo said:
Thanks for the input. finally someone! ..thats good to know Im going to try it now, I didnt think it would be as simple as a move command.. any reason the radio wipes the cache partition?
Click to expand...
Click to collapse
I realize I wasn't completely clear. I don't know why the OTA radio update wiped my cache partition. Perhaps someone familiar with the update process (ChiefzReloaded) can explain this.
turboyo said:
did dalvik recreate itself after the wipe in /data?
Click to expand...
Click to collapse
If you wipe only the cache partition, you will need to recreate the dir /cache/dc but not the symlink. If you wipe only the data partition, you will need to recreate the symlink, but not the dir. If you want to clear the dalvik-cache, just delete all the files in /cache/dc (they should be recreated on next boot). If you are accustomed to 'rm -R /data/dalvik-cache' to clear the dalvik-cache, you'll have to re-setup the symlink (and possibly the /cache/dc dir as well).
turboyo said:
and were ALL the apps gone or just the few that took up the memory?
Click to expand...
Click to collapse
None of the apps are 'gone' per se, but since the /data/dalvik-cache dir is just a symlink to a non-existant dir (/cache/dc), the system can't create a dir that already exists (/data/dalvik-cache) and can't write anything to a dir that doesn't exist (/cache/dc), so it won't show any of the apps. It is an easy fix to just recreate the /cache/dc dir and reboot. None of your apps need to be reinstalled, since they are still in the /data/app dir.
reukiodo said:
None of the apps are 'gone' per se, but since the /data/dalvik-cache dir is just a symlink to a non-existant dir (/cache/dc), the system can't create a dir that already exists (/data/dalvik-cache) and can't write anything to a dir that doesn't exist (/cache/dc), so it won't show any of the apps. It is an easy fix to just recreate the /cache/dc dir and reboot. None of your apps need to be reinstalled, since they are still in the /data/app dir.
Click to expand...
Click to collapse
Awesome, that cleared it up. Will be doing this now.
alright bringing this back up, works great but .. Just in case how do we move dalvik back to data with out loosing apps or anything?
turboyo said:
alright bringing this back up, works great but .. Just in case how do we move dalvik back to data with out loosing apps or anything?
Click to expand...
Click to collapse
I'm guessing you can do these in recovery:
rm /data/dalvik-cache
mv /cache/dc /data/dalvik-cache
rm -rf /cache/dc
But I haven't tested it. In theory it should work. The first command removes the symlink, the second moves the existing cache to the original location of dalvik-cache, and the last removes the copy of dalvik-cache on the cache partition.
I have tried this process, but shouldn't I see an increase in internal memory if you go to sdcard / phone storage?
Please advise, I am not totally clear of tthe process.
Can someone help?
I am very interested on this
UnkzDomain said:
I'm guessing you can do these in recovery:
rm /data/dalvik-cache
mv /cache/dc /data/dalvik-cache
rm -rf /cache/dc
But I haven't tested it. In theory it should work. The first command removes the symlink, the second moves the existing cache to the original location of dalvik-cache, and the last removes the copy of dalvik-cache on the cache partition.
Click to expand...
Click to collapse
It's up to you, but I would suggest just letting Android regenerate the cache...
rm /data/dalvik-cache
rm -R /cache/dc
riverajuan said:
I have tried this process, but shouldn't I see an increase in internal memory if you go to sdcard / phone storage?
Please advise, I am not totally clear of the process.
Can someone help?
I am very interested on this
Click to expand...
Click to collapse
It depends on how many applications you have installed, but you should see at least some kind of increase if you move the dalvik-cache off of /data and onto the /cache partition.
reukiodo said:
I was able to get dalvik-cache to /cache by going into clockworkmod recovery and accessing from adb:
mv /data/dalvik-cache /cache/dc
ln -s /cache/dc /data/dalvik-cache
After the files are moved and the symlink is created, you should have no problems when rebooting.
However, I came across a problem when I flashed the radio, since it wiped the cache partition. If you are missing all your installed apps in android, it might be that the cache partition was wiped. You need to recreate the /cache/dc folder and reboot.
Click to expand...
Click to collapse
I've moved dalvik-cache to /cache with a symlink. However, everytime i booted, /cache was 770 and not 771.
To solve this, I just add a little script in /system/etc/init.d
#!/system/bin/sh
#
# Change 770 to 771 /cache to enable dalvik-cache
/system/bin/chmod 0771 /cache
echo "*** cache updated ***"
exit
Name it for ex. 02cache and chmod 755 it.
reboot and the /cache should be 771 now and dalvik-cache should work fine without patching anything (I have a stock rooted froyo rom)
sibere said:
I've moved dalvik-cache to /cache with a symlink. However, everytime i booted, /cache was 770 and not 771.
To solve this, I just add a little script in /system/etc/init.d
#!/system/bin/sh
#
# Change 770 to 771 /cache to enable dalvik-cache
/system/bin/chmod 0771 /cache
echo "*** cache updated ***"
exit
Name it for ex. 02cache and chmod 755 it.
reboot and the /cache should be 771 now and dalvik-cache should work fine without patching anything (I have a stock rooted froyo rom)
Click to expand...
Click to collapse
forgive the newbness but to make that a script file do you just make that script into a .txt file and add it to system/etc/init.d? what exactly are you naming the file?
turboyo said:
forgive the newbness but to make that a script file do you just make that script into a .txt file and add it to system/etc/init.d? what exactly are you naming the file?
Click to expand...
Click to collapse
the init.d is a script. open it up and add those lines to it. then just save (do not change the file name when you save it)
turboyo said:
forgive the newbness but to make that a script file do you just make that script into a .txt file and add it to system/etc/init.d? what exactly are you naming the file?
Click to expand...
Click to collapse
I did it with "vi", a linux text editor.
You can name it whatever you like. the 2 first numbers are for the order of execution if you have more than 1 script in /etc/init.d/
sibere said:
I've moved dalvik-cache to /cache with a symlink. However, everytime i booted, /cache was 770 and not 771.
To solve this, I just add a little script in /system/etc/init.d
#!/system/bin/sh
#
# Change 770 to 771 /cache to enable dalvik-cache
/system/bin/chmod 0771 /cache
echo "*** cache updated ***"
exit
Name it for ex. 02cache and chmod 755 it.
reboot and the /cache should be 771 now and dalvik-cache should work fine without patching anything (I have a stock rooted froyo rom)
Click to expand...
Click to collapse
I have a Motorola Droid running froyo 2.2 FRG83 rooted. I don't have a /system/etc/init.d file, what's the correct permissions for it? And shouldn't the 771 actually be on /cache/dc instead of /cache as all the 771 does vs the 770 is add the execute bit for others so basically it changes from rwxrwx--- to rwxrwx--x.
Also, I am curious what happened before you added the script to change the permissions, were you able to still use the terminal app to get into the shell after booting?
To get /system/etc, you must boot into recovery mode
And I DO confirm to set 771 to /cache because the system rests it to 770 on each boot. For children folders, you can set 777, this will be kept even after a reboot.
Beleive me, that's how it works
Sent from my HTC Desire using XDA App
sibere said:
To get /system/etc, you must boot into recovery mode
And I DO confirm to set 771 to /cache because the system rests it to 770 on each boot. For children folders, you can set 777, this will be kept even after a reboot.
Beleive me, that's how it works
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
There is no need to boot into recovery mode to get to /system/etc which is the same as /etc. All you need to do is use either root explorer app or get the terminal shell prompt and then get into the directory after you mount it as read+write. Besides, how do you get into the /system/etc directory with recovery mode?
I know /cache is set to 770 after boot but since /cache/dc is the directory that you're dealing with and the only difference between 770 and 771 is the 1 adds the execution by others to the permissions so it doesn't give others read+write anyways as that requires another 6 so why wouldn't just setting 771 on /cache/dc work. Before you did the 771 on /cache, are you still able to boot and use the phone and the apps?
Almighty1 said:
There is no need to boot into recovery mode to get to /system/etc which is the same as /etc. All you need to do is use either root explorer app or get the terminal shell prompt and then get into the directory after you mount it as read+write. Besides, how do you get into the /system/etc directory with recovery mode?
I know /cache is set to 770 after boot but since /cache/dc is the directory that you're dealing with and the only difference between 770 and 771 is the 1 adds the execution by others to the permissions so it doesn't give others read+write anyways as that requires another 6 so why wouldn't just setting 771 on /cache/dc work. Before you did the 771 on /cache, are you still able to boot and use the phone and the apps?
Click to expand...
Click to collapse
This would normally be the case, however the slide doesn't have S-off like other phones, so we can't mount with r/w like you would.
Ace42 said:
This would normally be the case, however the slide doesn't have S-off like other phones, so we can't mount with r/w like you would.
Click to expand...
Click to collapse
Interesting. I guess what I'm trying to figure out is what happens if /cache is at 770, will the phone just force close on everything making it a brick at that point?
To get to /system/esltc in recovery, connect your phone to your PC and use adb
If you leave 770 to /cache, dalvik VM will not get access to the directory and will rebuild dalvik-cache in /data.
But man, if you don't trust me, you can always try yourself and make your own experiments
Sent from my HTC Desire using XDA App
I was Just reading about a Triple Swap (Ram) trick on XDA, It Uses Cache and Data and System partition as Swap Space.
Idea
Android devices have got RAM memory and internal eMMC memory. The eMMC is separated into several partitions (e.g. /system, /boot, /data, /cache). In former times of Android, the /cache partition was used for caching. Nowadays, in ICS times, the applications are using the /data partition to save information, libraries and cache data. So /cache is no longer used by the operating system or applications. Therefore, this partitions is empty except 4ext-logfiles, last recovery-log and an obligatory and empty lost+found directory. So we have got another 114 MB of space that can now be used as fast swap space for the kernel.
Also, the /system partition normally is not fully used - depending on the rom, a more or less amount of this area is free and unused.
As these areas all are internal memory, these swaps are faster, than a swap area on the sdcard!
There are also a lot of read/write requests to the /data partition as well and this is in Android “by design”. Furthermore there are devices, that have a preconfigured eMMC-swap space "by design", as for exaple the HTC One V.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
So the Help I need is: To get our device supported for this is are the following things:
To do this, we will need your help. At fist you have to install the script manually to confirm that it's working. In the second step we will need a few details of your phones to modify the Aroma setup. Let's start with the first step:
Installation instructions:
Download the Aroma
Extract the file 98swap_cache_v300 from the folder \swap\cache\50\etc\init.d in the Aroma
What to do:
Enter ES-Explorer and:
Go to ES-Explorer settings/Root settings/check (root explorer ,up to root and mount file as writable).
Copy the script 98swap_cache_v300 to /system/etc/init.d
Don't reboot!
Open a terminal session and get superuser rights with the command: su
Command: cd /system/etc/init.d (now you are in the init.d folder, where the script is)
Command: chmod 775 98swap_cache_v300 (now the script has execution rights)
Reboot
Now:
Open a terminal session and get superuser rights with the command: su
Command: cat /proc/swaps (shall show the new swap file /cache/swap/swap.img)
With ES-Explorer navigate to /data/swap and look into the log file swap_cache.log
Please, sent Me the logfile swap_cache.log via PM!.
If it's working, we have to do the second step:
The second step is, to include your Device in the Aroma; we need the internal device name and the mount point of the file systems. Do the following:
Open a terminal session
Get a superuser shell with the command: su
Now the command:getprop ro.product.device
(that's the internal device name - I will need that name exactly)
Now the command: mount
(we need the mount points from /cache and /data and /system; if you do not find them, just use the command "mount > file" - this will write all output to "file" - then send me "file")
Please, sent above info to Me via PM!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
The Two Files I will send to the developer, Then We can pray that He gets to Work on it..
HJain13 said:
I was Just reading about a Triple Swap (Ram) trick on XDA, It Uses Cache and Data and System partition as Swap Space.
Idea
So the Help I need is: To get our device supported for this is are the following things:
The Two Files I will send to the developer, Then We can pray that He gets to Work on it..
Click to expand...
Click to collapse
U can just skip ur second step by not checking the device
Hmm..... BUT
T3snake said:
U can just skip ur second step by not checking the device
Click to expand...
Click to collapse
Hmm.. but It would be nice if We could use Aroma.. easier to choose amount of swaps and where etc...
HJain13 said:
Hmm.. but It would be nice if We could use Aroma.. easier to choose amount of swaps and where etc...
Click to expand...
Click to collapse
It will be aroma allright...
I meant ur second step (getprop 1) isn't mandatory
Anyway info u need is in build.prop
Sent from my SM-T211 using Tapatalk
DISCLAIMER:
I AM NOT RESPONSIBLE FOR YOUR DEVICE OR ANYTHING THAT MIGHT OCCUR WHILE USING THIS TUTORIAL. TRY AT YOUR OWN RISK!
Credits:
[mbm] for teaching me this dd terminal method.
As we all know, for what ever reason, Samsung decided to release the Tab 3 model tablets with 1 GB of ram. I believe this system needs more ram but unfortunately we cannot upgrade the hardware. What we can do is create virtual memory or a "Swap file" that acts like ram to help our Tab 3's out with multitasking and other memory hogging tasks. Below are the steps to:
1. Create a swap file.
2. Create a script file to run at boot from your /system/etc/init.d directory.
3. Create a android system with 1GB of RAM and 1GB of swap file virtual memory.
*Remember whatever device you are using must have a rom with init.d support and be rooted.
STEP 1: TERMINAL COMMANDS PT.1
Download terminal emulator from the play store if you don't already have it.
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
Open terminal emulator and execute these commands in order:
1. "su"
2. "cd /system"
3. "mount -o rw,remount /system"
4. "dd if=/dev/zero of=swapfile bs=1m count=600" (be patient, this step takes about a minute)
5. "mkswap swapfile"
6. "chmod 755 swapfile"
STEP 2: INIT.D SWAP FILE TEXT CREATION
Now to create a script to execute at boot every time you boot your phone. I used the app QuickEdit from the play store.
https://play.google.com/store/apps/details?id=com.rhmsoft.edit
Now open that up and put the text below in the file:
"mount -o rw,remount /system
swapon /system/swapfile"
Now save that to your sdcard (/sdcard) as "swap" (remember do not save with the .txt)
STEP 3: TERMINAL COMMANDS PT.2
Now go back into terminal and execute these commands:
1. mv /sdcard/swap /system/etc/init.d
2. chmod 755 /system/etc/init.d/swap
I kept my previous terminal session open but if you closed it for what ever reason you might have to execute "su" and then "mount -o rw,remount /system" before the two commands in step 3.
STEP 4:
Reboot and win. :laugh::good::laugh:
To verify that the process has worked, after reboot, bring up terminal emulator and type "free -m". You should see that swap has more than 600M! This will stick after reboot. If for whatever reason you want to get rid of your swap file just delete the "swapfile" file and the "swap" script. Enjoy!
I'm getting "swap file needs to be a least 40kb" after I "mkswap swapfile"
EDIT:I tied it again now and it seemed to work, for some odd reason
Sent from my SM-N910T using Tapatalk
My swap file reads "399" .... it's not more than 600m. What did I do wrong?
vin_001 said:
My swap file reads "399" .... it's not more than 600m. What did I do wrong?
Click to expand...
Click to collapse
Never mind! I found the solution... when typing "1m" into the command line, the m must be capitalized, "M". If anyone else has this issue, this is where u went wrong! Now I have "999" instead of "399"!
AWSOME. It brought some more life into my lagging P5210 running latest cm13 from Nelson. Cool
Thanks, I can finally use chrome on my tab 3
Is it same to wipe the system partition? , bcuz i want to clean install
Sent from my SM-G7102 using Tapatalk
Devel0per95 said:
Is it same to wipe the system partition? , bcuz i want to clean install
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Not sure what you mean, but when you wipe your system folder, you need to make swapfile again.
@ "4." it says: "Read-only file system"
What did I do wrong?
I'm on 13.0-20161121-UNOFFICIAL-santos10wifi
Thanks!
Gesendet von meinem SM-G925F mit Tapatalk
DerLeoLeo said:
@ "4." it says: "Read-only file system"
What did I do wrong?
I'm on 13.0-20161121-UNOFFICIAL-santos10wifi
Thanks!
Gesendet von meinem SM-G925F mit Tapatalk
Click to expand...
Click to collapse
You didn't do number 3 right. That mounts the system read/write
Sent from my SM-N920V using Tapatalk
Thanks! Will try again...
Gesendet von meinem SM-G925F mit Tapatalk
Hi I have still the message...
Any clue?
Thanks a lot
My device is really more usuable with this trick
Added with niels CM custom ROM it is fantastic
Envoyé de mon GT-P5210 en utilisant Tapatalk
I've got to the last step and couldn't move the file as the /system partition is 100% used.
I also notice that the created /system/swap file is only 589M ...
So I guess I could try to use a smaller swap file or clear some /system/** memory? Anyone know the best way to do that? or what i can delete etc?
thanks.
spankycarbowski said:
I've got to the last step and couldn't move the file as the /system partition is 100% used.
I also notice that the created /system/swap file is only 589M ...
So I guess I could try to use a smaller swap file or clear some /system/** memory? Anyone know the best way to do that? or what i can delete etc?
thanks.
Click to expand...
Click to collapse
The last step is where you went wrong, since swap uses space on your system partition. Free up space and redo everything again. You should see 999 ( or more than 600) if you succeeded.
vin_001 said:
The last step is where you went wrong, since swap uses space on your system partition. Free up space and redo everything again. You should see 999 ( or more than 600) if you succeeded.
Click to expand...
Click to collapse
Yes right, I guess I am really asking - what is the best way to clean up the system partition - as i have no idea what i can delete?
spankycarbowski said:
Yes right, I guess I am really asking - what is the best way to clean up the system partition - as i have no idea what i can delete?
Click to expand...
Click to collapse
To free up space in the system partition, try deleting unecessary system apps and bloatware, (I'm guessing you are on stock touchwiz, but it doesn't matter otherwise). You can also find a deodexed rom that you would like. Deodexed roms use less space in your system partition. The last option is to get a download of your rom on a PC and boot into TWRP (3.0.2-0 preferred) and do an advanced wipe as well as your internal storage. Backup everything if needed, then reflash.
Hope any of these helped!
vin_001 said:
To free up space in the system partition, try deleting unecessary system apps and bloatware, (I'm guessing you are on stock touchwiz, but it doesn't matter otherwise). You can also find a deodexed rom that you would like. Deodexed roms use less space in your system partition. The last option is to get a download of your rom on a PC and boot into TWRP (3.0.2-0 preferred) and do an advanced wipe as well as your internal storage. Backup everything if needed, then reflash.
Hope any of these helped!
Click to expand...
Click to collapse
Ahhh. I followed the instructions and installed cm13.0 from nels83 ( https://forum.xda-developers.com/galaxy-tab-3/development-10/rom-cyanogenmod-13-0-t3342017 )
I guess doing this step:
"Wipe -> Advanced Wipe -> Dalvik Cache + System + Cache + Data"
doesn't actually wipe the system partition clean?
spankycarbowski said:
Ahhh. I followed the instructions and installed cm13.0 from nels83 ( https://forum.xda-developers.com/galaxy-tab-3/development-10/rom-cyanogenmod-13-0-t3342017 )
I guess doing this step:
"Wipe -> Advanced Wipe -> Dalvik Cache + System + Cache + Data"
doesn't actually wipe the system partition clean?
Click to expand...
Click to collapse
Ya, that doesn't wipe the tablet clean, wiping all of that and 'internal storage' does the trick. Glad I could help!
I agree with everyone here. This made a big responsiveness change in the tablet. Thank you!
Hello.
I've installed viper4android on my mido. Everything is ok, but there is a background static sound when music is being played. According to the viper FAQ I need to delete /system/lib/soundfx/libbundlewrapper.so. What did I do:
1. Mount system as rw
adb shell
su
mount -o rw,remount,rw /system
2. try to rename that file
cd /system/lib/soundfx
mv libbundlewrapper.so libbudnlewrapper-2.so.bak
3. No success. Trying to create backup in a file manager and than trying to delete it. Still no luck. Changed system to ro and I'll wait for suggestions.
The file is there like I haven't done anything. The uncharted territory of the system partition still awaits for me. What I can do next to get the thing to work?
Rust3dCor3 said:
Hello.
I've installed viper4android on my mido. Everything is ok, but there is a background static sound when music is being played. According to the viper FAQ I need to delete /system/lib/soundfx/libbundlewrapper.so. What did I do:
1. Mount system as rw
adb shell
su
mount -o rw,remount,rw /system
2. try to rename that file
cd /system/lib/soundfx
mv libbundlewrapper.so libbudnlewrapper-2.so.bak
3. No success. Trying to create backup in a file manager and than trying to delete it. Still no luck. Changed system to ro and I'll wait for suggestions.
The file is there like I haven't done anything. The uncharted territory of the system partition still awaits for me. What I can do next to get the thing to work?
Click to expand...
Click to collapse
What rom do you use? Miui or los/aosp? Also do you use, magisk or super su? Plus, please tell how did u Install viper, that is through recovery or by using magisk?.
MyNameIsRage said:
What rom do you use? Miui or los/aosp? Also do you use, magisk or super su? Plus, please tell how did u Install viper, that is through recovery or by using magisk?.
Click to expand...
Click to collapse
I use Official and final RR
The phone uses magisk and viper was flashed by magisk (should I remove the module and flash as non-system app?)
Rust3dCor3 said:
I use Official and final RR
The phone uses magisk and viper was flashed by magisk (should I remove the module and flash as non-system app?)
Click to expand...
Click to collapse
Why don't you use es file manager? I just tried i was able to do it with es.
MyNameIsRage said:
Why don't you use es file manager? I just tried i was able to do it with es.
Click to expand...
Click to collapse
Still does not work. I have no idea what to do. Again.
Renaming the file does not go despite a Toast is visible "Rename Successful" and while deleting there is "Device or resource busy"
Rust3dCor3 said:
Still does not work. I have no idea what to do. Again.
Renaming the file does not go despite a Toast is visible "Rename Successful" and while deleting there is "Device or resource busy"
Click to expand...
Click to collapse
Why don't you try deleting it from twrp.
MyNameIsRage said:
Why don't you try deleting it from twrp.
Click to expand...
Click to collapse
I tried. The funny part is that I can only see /system/usr. No other folder is in /system. Thats why I've posted this topic. I'm just lost.
Rust3dCor3 said:
I tried. The funny part is that I can only see /system/usr. No other folder is in /system. Thats why I've posted this topic. I'm just lost.
Click to expand...
Click to collapse
Nope, you haven't mounted system in twrp, that's the reason you are only seeing /usr
So do this
From main menu, select "mount" and there select System, also make sure that the "system" box is checked and the box saying "mount system partition as read only" is unchecked(I've attached a screenshot for reference). Now you can easily go to /system and it should list the files and folders., And you can delete the file you want. Quote me if you need more help
MyNameIsRage said:
Nope, you haven't mounted system in twrp, that's the reason you are only seeing /usr
So do this
From main menu, select "mount" and there select System, also make sure that the "system" box is checked and the box saying "mount system partition as read only" is unchecked(I've attached a screenshot for reference). Now you can easily go to /system and it should list the files and folders., And you can delete the file you want. Quote me if you need more help
Click to expand...
Click to collapse
I can't believe how stupid I am. Thank You for Your advice.