I'm on stock JB.
I noticed the /preload/symlink/system/app/ is full of APKs, some of them I removed from my system partition as I don't need them.
Is it safe to remove all APKs from /preload ?
What's it used for anyway? They are not really symlinks as the path would suggest.
emwu_ said:
I'm on stock JB.
I noticed the /preload/symlink/system/app/ is full of APKs, some of them I removed from my system partition as I don't need them.
Is it safe to remove all APKs from /preload ?
What's it used for anyway? They are not really symlinks as the path would suggest.
Click to expand...
Click to collapse
You can always flash stock Firmware with Odin and get all those back. That what yuo removed from system partition was shortcuts to the apps in preload partition (not all of it, but the ones that are present in preload).
Related
I've search the forum and find different ways to move dalvik-cache from data partition to cache partition, from creating links or mounting, to a2sd command, but none of them worked for me. In all cases after reboot another dalvik-cache with system access will created along the dalvik-cache the method created in data partition. so I have two dalvik-cache folders (that one of them is link) and system will use the real one that will waste my data partition size.
this is how it look like:
Code:
drwxrwx--x system system 2010-10-23 12:30 dalvik-cache
drwxrwxrwx root shell 2010-10-23 11:41 dalvik-cache
I am struggling to find a way to free some memory on /data partition, as I rooted without unlocking the boot loader, I couldn't be able to resize the data system and cache partitions, (booted into fastboot mode, used fastboot command to erase system but it couldn't be erased with a access denied error).
Anybody can you please help?
I am on stock Froyo 2.2.1 and rooted without unlocking bootloader.
bohlool said:
I've search the forum and find different ways to move dalvik-cache from data partition to cache partition, from creating links or mounting, to a2sd command, but none of them worked for me. In all cases after reboot another dalvik-cache with system access will created along the dalvik-cache the method created in data partition. so I have two dalvik-cache folders (that one of them is link) and system will use the real one that will waste my data partition size.
this is how it look like:
Code:
drwxrwx--x system system 2010-10-23 12:30 dalvik-cache
drwxrwxrwx root shell 2010-10-23 11:41 dalvik-cache
I am struggling to find a way to free some memory on /data partition, as I rooted without unlocking the boot loader, I couldn't be able to resize the data system and cache partitions, (booted into fastboot mode, used fastboot command to erase system but it couldn't be erased with a access denied error).
Anybody can you please help?
I am on stock Froyo 2.2.1 and rooted without unlocking bootloader.
Click to expand...
Click to collapse
I think the stock kernel re-establishes the file system on boot and does not support moving anything.
I think you'll need a custom rom and kernel with apps2ext support to do what you're wanting.
Try the latest test release of my rom (in my sig), has everything you need.
djmcnz said:
I think the stock kernel re-establishes the file system on boot and does not support moving anything.
I think you'll need a custom rom and kernel with apps2ext support to do what you're wanting.
Try the latest test release of my rom (in my sig), has everything you need.
Click to expand...
Click to collapse
Is there any other way? e.g. Changing something, or Install something to make it no re-establishment? Or any way to change the partition sizes on Stock ROM (rooted but without unlocking boot loader)
bohlool said:
Is there any other way? e.g. Changing something, or Install something to make it no re-establishment? Or any way to change the partition sizes on Stock ROM (rooted but without unlocking boot loader)
Click to expand...
Click to collapse
Nope.
Root and be done with it, that's why people get the Nexus...
Edit: Hang on... I didn't read properly...
But the answer's still no... Just load a custom rom/kernel, you're already rooted.
Edit 2: Even with a custom rom you can not change partition sizes.
Hi, I've been putting some of my apps apks in /system/app, so that I have more free space in /data.
Mostly I just put apps there that I know I will never need to uninstall, like TiBackup, LauncherPro etc. When those apps update, I just manually move the newer apk into /system/app.
Question: Is it wrong to fill up /system to almost-full?
I know it's mounted read-only during normal use, so nothing else can write to it anyway.
Yup, I'd like to know tha answer to this question too!
I have heard of it being done quite abit. So it can't be that bad.
Yeah, it can't be that bad. But what if you filled it to 100%, is that bad?
Cache and data are housed in separate partitions as far as I know. So, I believe it's ok to fill it up completely, since most other things don't need write access to /system partition anyway. If it's not being written to during normal operation, then any free space on /system is basically wasted.
But I'd still like to hear from someone more knowledgeable if it is indeed fine to fill up the /system partition. Or if it's better to leave a certain amount of space, and how much space is recommended.
It depends on the ROM. If you're using CM, apps in the /system partition stores it's dalvik-cache in the /cache partition. So, if I am correct, more apps in the /system means less /cache space.
I tried putting LauncherPro in /system/apps and then removing it from /data/apps, but with no luck - it kept force closing on launch not ideal for a launcher! I haven't yet figured out why it wouldn't work, but I'm sure I'll get there in the end.
SF
geevee11 said:
It depends on the ROM. If you're using CM, apps in the /system partition stores it's dalvik-cache in the /cache partition. So, if I am correct, more apps in the /system means less /cache space.
Click to expand...
Click to collapse
On CM6, /cache is a different partition than /system, so it shouldn't affect cache space.
I'll observe the free space for a few days without adding additional apps on /system. Right now, I have 15MB free on /system, and 39MB free on /cache. I'll report back in a while.
r8dhex said:
On CM6, /cache is a different partition than /system, so it shouldn't affect cache space.
I'll observe the free space for a few days without adding additional apps on /system. Right now, I have 15MB free on /system, and 39MB free on /cache. I'll report back in a while.
Click to expand...
Click to collapse
I was talking about the dalvik-cache. Even if you install apps in the /system partition, it'll still have the dex files. So the more apps you put in your /system partition, the more your /cache will fill up = less ram.
I found out that apps in /system couldn't be updated through the market.
For instance: the facebook app that comes installed with google apps package of CM6 is installed in the /system dir of the phone. When I tried to update it through market it would fail every time. Once I deleted the app from /system and rebooted the phone, updating (installing) the app from market went fine.
Some of you suggested using the cache partition for app cache - but when I use 'df' in Terminal Emulator it states that only 13604K of my 108544K cache partition are free.
When 'ls'-ing the /cache partition it lists files named "downloadfile.apk" to "downloadfile-34.apk".
Is this some OTA update?
That'd be strange, since the last (2.2.1) update came via PC only and i wiped everything that could be wiped via the recovery menu.
Furthermore the the creation dates of the .apks range from may to a few days ago.
But when I try to open them using Root Explorer it says "Error parsing package" and opening them via "View" gives me a blank screen.
Please enlighten me.
Thanks in advance
Those are temporary downloads from the market. Updates etc.
Does it only remove them on demand?
So I can remove them savely to make room for my appcache?
Once they're installed you can safely remove the apks in /cache
I was able to gain some space by wiping the dalvik cache so I'm gonna delay trying to use /cache
But I have one more question: several sources claim that using /cache for app-cache incompatible with App2SD - is that true?
I'm afraid I need some more clarification so I'm gonna push this thread...
I checked the sizes of my dalvik cache folder and /cache partition
df states that /cache has a total size of 108544K, 93793K used by .apk files I cannot open with Root Explorer and 13364K free
In my /data/dalvik-cache folder theres files summing up to 100956K
So they would barely fit in /cache if I delete all the .apks
I'm not sure if that would be a good idea...
Any suggestions?
GuYWith a deodexed and de-bloated Samsung Rom we have 500mb plus of free space on System partition which is wasted space.
I just tried something to free up some space for shared data/sdcard partition by moving Dalvik Cache from /data to /system then creating a folder link back in data to keep original location settings.
Took 30 seconds and freed up 260mb! This is what you do:
1. Using root explorer or similar. Go to /Data.
2. Navigate to "Dalvik-Cache" directory. Long press on it and select "move".
3. Navigate back to root directory and then to /System.
4. Paste the directory you must select rw first top right hand corner. It will take a minute to copy.
5. Now long press on the moved Dalvik-Cache directory in /System and select "Link to this folder" option.
6. Navigate back to /Data and paste the link.
7. Done! You now have moved the Dalvik-Cache location to unused space on System partition and left a sym-linked directory so Android thinks nothing has changed!
Note!: If you wipe Dalvik Cache from recovery a new directory will be recreated in Data and your moved directory in System will no longer be used it will just sit in System taking up space.
AFTER A DALVIK CACHE WIPE FROM RECOVERY YOU MUST DELETE THE DIRECTORY YOU CREATED IN SYSTEM AS IT IS NO LONGER USED. SIMPLY REPEAT THE ABOVE STEPS TO ACTIVATE THE MOD AGAIN.
Good luck. A REAL Dev could you please turn this into a CMW zip with the reverse undo counterpart to be flashed before a Rom upgrade.
UPDATE: looking at the link posted by a helpful person below (thanks!) I think we need to make /system mount as rw for this to work. Please help develop this idea more if anyone can help thanks
Sent from my GT-I9300 using xda premium
Is it work on cm10? I have over 1gb free on system partition
jnr21 said:
Is it work on cm10? I have over 1gb free on system partition
Click to expand...
Click to collapse
I'M not sure haven't used cm10 yet but it should do. Just discovered a Dalvik Cache wipe from recovery recreates the directory in Data to the MOD needs to be repeated after this... makes it very safe to try on cm10!
I'm hoping a real Dev can take this idea and bake it into to custom Rom's and find more data we can move to free up more space
Sent from my GT-I9300 using xda premium
Hi,
Maybe it's possible to do this via init.d script? It will be more convenient.
It's possible via init.d script to move dalvik-cache to /cache for example... so...
Just a thought or simply move it to /cache.
EDIT:found this: http://petermolnar.eu/linux-tech-coding/how-to-move-dalvik-cache-to-system-partition-in-android/
Is this similar to the function "Integrate sys Dalvik into ROM" from Titanium Backup?
[email protected] said:
Is this similar to the function "Integrate sys Dalvik into ROM" from Titanium Backup?
Click to expand...
Click to collapse
Yeah I guess it is but if you do it through titanium the Dalvik Cache files are put with their apk files so wipe Dalvik Cache in recovery no longer works... Not 100% sure this is right tho
Sent from my GT-I9300 using xda premium
viking37 said:
Hi,
Maybe it's possible to do this via init.d script? It will be more convenient.
It's possible via init.d script to move dalvik-cache to /cache for example... so...
Just a thought or simply move it to /cache.
EDIT:found this: http://petermolnar.eu/linux-tech-coding/how-to-move-dalvik-cache-to-system-partition-in-android/
Click to expand...
Click to collapse
Yeah should be possible. I think a CWM zip would be best along with an undo version. I now have /Data/app directory moved so before a Rom update or nandroid backup it will be necessary to undo the move. I'll see if I can work out how to do this. Hopefully someone could help out. I'M not code literate yet lol!
Sent from my GT-I9300 using xda premium
if u wanna free up the /data partition, it is a good and proper way to move the dalvik-cache elsewhere. but IMHO, the /system partition is not a good place to move to since by design the system partition is not suppose to have any frequent or unnecessary read write and thus it is ro by default. the other reason is its importance since it is the core part of the system. you can afford to pay for a corrupted data or cache partition but not the system partition since as long as the system files are save the whole system can be rebuilt in case of data loss etc
i am not against this trick and i only want to tell you my opinions. so if possible i would recommend u to put the dalvik cache somewhere else like the cache partition
ykk_five said:
if u wanna free up the /data partition, it is a good and proper way to move the dalvik-cache elsewhere. but IMHO, the /system partition is not a good place to move to since by design the system partition is not suppose to have any frequent or unnecessary read write and thus it is ro by default. the other reason is its importance since it is the core part of the system. you can afford to pay for a corrupted data or cache partition but not the system partition since as long as the system files are save the whole system can be rebuilt in case of data loss etc
i am not against this trick and i only want to tell you my opinions. so if possible i would recommend u to put the dalvik cache somewhere else like the cache partition
Click to expand...
Click to collapse
Yes I've discovered that it's prob not a good idea to leave System rw.... all that wasted space tho
Sent from my GT-I9300 using xda premium
rlorange said:
Yes I've discovered that it's prob not a good idea to leave System rw.... all that wasted space tho
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
u can resize the system partition, and then reassign the disk space freed up to other partitions
NOTE: this is risky and may brick your phone
if you r interested, you can get some more info in my blog posts (based on I9000)
Free more available disk space from NAND - PART I
Free more available disk space from NAND - PART II
freeNANDmod - get more space from NAND - PART III
freeNANDmod - get more space from NAND - PART IV
- symbolic linked dalvik-cache directory may cause issues in some application, use the bind mount instead of this
- titanium backup feature (integrate dalvik-cache to rom) is not mean what you think. it is not for moving dalvik-cache to the system partition
edit: i writed a script what can do exactly what we need.
auto check the dalvik-cache already moved to the cache directory, if yes bind mount the directory. if not, moved the cache then bind mount
you can adjust the cache and the data partition in the beginning of the file, dont touch anything else! default is defined for the SGS3
log file is /cache/dalvik_mover.log
after a full cache wipe the script will be move the dalvik cache after the next reboot
just unzip and put this file to the /system/etc/init.d/ folder
then set the permission to 0755
reboot
this script is not using the system partition, so no need to remount the system as r/w. its used the cache partition what have more free space anyway and always writeable.
and the bind mount method is compatible with everything.
rlorange said:
GuYWith a deodexed and de-bloated Samsung Rom we have 500mb plus of free space on System partition which is wasted space.
I just tried something to free up some space for shared data/sdcard partition by moving Dalvik Cache from /data to /system then creating a folder link back in data to keep original location settings.
Took 30 seconds and freed up 260mb! This is what you do:
1. Using root explorer or similar. Go to /Data.
2. Navigate to "Dalvik-Cache" directory. Long press on it and select "move".
3. Navigate back to root directory and then to /System.
4. Paste the directory you must select rw first top right hand corner. It will take a minute to copy.
5. Now long press on the moved Dalvik-Cache directory in /System and select "Link to this folder" option.
6. Navigate back to /Data and paste the link.
7. Done! You now have moved the Dalvik-Cache location to unused space on System partition and left a sym-linked directory so Android thinks nothing has changed!
Note!: If you wipe Dalvik Cache from recovery a new directory will be recreated in Data and your moved directory in System will no longer be used it will just sit in System taking up space.
AFTER A DALVIK CACHE WIPE FROM RECOVERY YOU MUST DELETE THE DIRECTORY YOU CREATED IN SYSTEM AS IT IS NO LONGER USED. SIMPLY REPEAT THE ABOVE STEPS TO ACTIVATE THE MOD AGAIN.
Good luck. A REAL Dev could you please turn this into a CMW zip with the reverse undo counterpart to be flashed before a Rom upgrade.
UPDATE: looking at the link posted by a helpful person below (thanks!) I think we need to make /system mount as rw for this to work. Please help develop this idea more if anyone can help thanks
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Yes, to get this working you need a system mounted Always in r/w.
So i suggest you to move dalvik on cache partition.
And it's better to do the mod inside ramdisk
vadonka said:
- symbolic linked dalvik-cache directory may cause issues in some application, use the bind mount instead of this
- titanium backup feature (integrate dalvik-cache to rom) is not mean what you think. it is not for moving dalvik-cache to the system partition
edit: i writed a script what can do exactly what we need.
auto check the dalvik-cache already moved to the cache directory, if yes bind mount the directory. if not, moved the cache then bind mount
you can adjust the cache and the data partition in the beginning of the file, dont touch anything else! default is defined for the SGS3
log file is /cache/dalvik_mover.log
after a full cache wipe the script will be move the dalvik cache after the next reboot
just unzip and put this file to the /system/etc/init.d/ folder
then set the permission to 0755
reboot
this script is not using the system partition, so no need to remount the system as r/w. its used the cache partition what have more free space anyway and always writeable.
and the bind mount method is compatible with everything.
Click to expand...
Click to collapse
thank you very much works perfect
On the stock GB ROM, Link2SD requires a FAT32 partition to move the App and DalvikCache to the SD.
EDIT: Actually requires FAT32 OR EXT2 for stock...
Titanium backup requires an ext2/3/4 partition to use the Data2SD feature.
Is it possible to do both of these on a stock rom? Or use some other method to get the App, DalvikCache and app data to the SD without flashing another ROM?
I will be doing this for 3 of my family's phones and would much prefer to not have to flash ROMS and them have to put in extra effort afterwards.
I promise I've searched so apologies if this has been answered elsewhere, the closest I could find was http://forum.xda-developers.com/showthread.php?t=1605006 which didn't answer the question...
Thanks in advance!
Tim
I have created two partitions, one FAT32 and one EXT2 using MiniTool Partition Wizard
Link2SD is correctly setup and working.
Titanium Backup has this to say:
The supported mount points for the ext2/3/4 partition are:
/system/sd/ (“classic” sd-ext)
/sd-ext/ (“Cyanogen” sd-ext)
/data/sd/ (“MIUI” sd-ext)
However none of these mount points are present (it appears to mount under /data/sdext2/) so I'm unable to use the Data2SD functionality as yet.
So the question now becomes, can I create multiple mount points for a single EXT2 partition on a Stock ROM (ideally easily!).
Install a custom kernel with init.d support.
Cf-root is the most common since it's based on stock, and preserves baseband.
After that, there's many choices:
-link2sd as you've beeb using
-cronmod or amarullz scripts (int2ext+) which mount sd partition as extention to internal memory (every app on internal gets installed to the partition).
-s2e has the option to also move data to the partition.
Keep in mind that having data on the partition will lower performance and smoothness as compared to having data on internal.
dxppxd said:
Install a custom kernel with init.d support.
...
...
Keep in mind that having data on the partition will lower performance and smoothness as compared to having data on internal.
Click to expand...
Click to collapse
Thanks for the advice.
I have a class 10 card that I was hoping would help mitigate the problem, am I just being naive?
I was hoping I'd be able to avoid a custom Kernel (haven't researched them enough yet)
I will try and find an S5830 Stock + init.d kernel tomorrow and see how that goes, I'm still planning on Titanium Backup to do the Data2SD.
Does this init.d script mount the partition somewhere that Titanium Backup can get hold of it then?
KingTimus said:
Does this init.d script mount the partition somewhere that Titanium Backup can get hold of it then?
Click to expand...
Click to collapse
I really can't say about titanium backups' data2sd function since i've never used it before.
The init.d script (i found cronmods' int2ext to be the most convenient) mounts the sd partition as part of /data. When making backups of apps+data titanium backup had 0 problems finding and backing up all apps. The problem might arise if the data2sd function tries to move /data (in which the partition is already mounted) to the partition.
Someone in the forum might know more details. You can always make a nandroid backup and see what happens. Good luk.