So TiBu just added an option to integrate the system dalvik cache to the ROM. Does this move it to /system or what? Because I don't want to integrate this and lose what little space is left on /system.
Sent from my Xoom using xda premium
d3athsd00r said:
So TiBu just added an option to integrate the system dalvik cache to the ROM. Does this move it to /system or what? Because I don't want to integrate this and lose what little space is left on /system.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
I wouldn't do it.
d3athsd00r said:
So TiBu just added an option to integrate the system dalvik cache to the ROM. Does this move it to /system or what? Because I don't want to integrate this and lose what little space is left on /system.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Hi, same question here. What does that mean. anyone?
I run script in etc/ init.d to move dalvik cache to cache folder.
I have all the permission checked.
#!/system/bin/sh
echo "++++ DALVIK 2 CACHE STARTING ++++"
if [ ! -d /cache/dalvik-cache ]
then
mkdir /cache/dalvik-cache
chown 1000:1000 /cache/dalvik-cache
chmod 775 /cache/dalvik-cache
fi
if [ -L /data/dalvik-cache ]
then
rm -f /data/dalvik-cache
mkdir /data/dalvik-cache
chown 1000:1000 /data/dalvik-cache
chmod 775 /data/dalvik-cache
elif [ ! -d /data/dalvik-cache ]
then
mkdir /data/dalvik-cache
chown 1000:1000 /data/dalvik-cache
chmod 775 /data/dalvik-cache
elif [ -d /data/dalvik-cache ]
then
for filename in /data/dalvik-cache/*
do
if [ -L $filename ]
then
rm -f $filename
fi
done
mv /data/dalvik-cache/* /cache/dalvik-cache/
fi
mount -o bind /cache/dalvik-cache/ /data/dalvik-cache/
Yeah I'm reviving thks thread because I'm shocked at the responses given to a legit question. No one ever tried to explain and instead took their time to say "don't try it". It shouldn't hurt anything trying it out as long as you have a back up . in fact on my G2 of happily go do it without a backup.
I'm not 100% what it does but a quick search where people without complexes answers should give you the answer. There must be a purpose behind it as it's still an option to this very day. In thinking it moves dalvik to either /system or somewhere else off the top of my head. I used to know but moving dalvik hasn't been an issue really anymore. Here to got dog slap the naysayers I'll click the option before refresingy memory and tell ya where it's moved to. Well yell others since this is the first search result to show on google when searching the topic so even though it's dear question is still relevant. See, back in the day when we ran on tiny amounts of storage space a lot of is moved /data/dalvik-cache elsewhere and left a symlink there so apps could find it and so we could free more space up for apps.
People need to learn that xda posts are often the top Google search results and need to act accordingly and professional (well as professional as fun loving devs get ). Let me integrate for everyone and I'll report back with the the exact location. Now his advice though on not doing is sound because of you don't know what you're doing or yow to undo it then you need to do more researching but a real answer should have acompanied it. If i was up (which in won't do) I know how to fix the issue in a heartbeat.
Edit: Appears to move certain apks into /system/app toake use or all the space there. I move 76 files and no issues. In the day there were many horror stories but nothing that had. Just missing apks from what was moved since not all apks liked being system apps.
Solution is to find apks in /system/app and delete (or use command line uninstall feature) and reinstall. Undoing the integration within TA might also work, but these newer phones arent as bad. Least not the G2 as all my apps are there. Each their own
Odex for more space, not really.
This thread may have been born dead, but for the same reasons as the last post, needs more input:
The Titanium Backup option to integrate system dalvik into ROM will free some space on your internal sd storage partition, but use disproportionally more space on the system partition. As far as total internal storage it is a loss, but the common ailment of legacy devices is to run out of internal sd space as apps are installed.
Example: I started with 108 MB of free space on my system, and 2.1 GB of free space on my internal storage. TiBk offered 94 integrable files totaling 71 MB. After integration, I only have 37 MB free space on the system, and 2.15 GB free space on the internal storage. So even though I gained 41 MB for user apps, I actually lost 30 MB in total to odexing on my system.
A more efficient method for gaining internal sd space would be to conversely shrink the system partition while enlarging the internal data/media partition. But this isn't always possible or too extreme a measure for many users.
In addition to moving data from one internal partition to the other, all the newly integrated ROM files will be odexed. This will speed up the the first boot and boot after clearing dalvik cache, as the odexed apps are already optimized to the ROM. In addition, the odexed apps will launch a little faster and technically have a performance edge, though commonly reported as 'not noticeable'.
After integrating the system Dalvik into the ROM, it can just as easily be deintegrated with the next settings option in TiBk. This is necessary before applying certain themes and mods requiring deodexed apks. Then you would ideally integrate and odex again.
MidnightHarvester said:
Undoing the integration within TA
Click to expand...
Click to collapse
Did you mean TB
I have used this on my S4...I have 1.2gb of free space in my system/Rom partition so it would be rude not to.. I moved around 500mb from internal SD card... All worked fine...
But now using a different custom rom, Kernel and different version of TB... It won't integrate the dalvik any more... Just says 278 item failed to integrate.... Im guessing TB can't write to the system/rom partition for some reason?? I think I may have been on a kit kat Rom when it worked for me..
Related
I just installed it and did a backup, wiped my G1 and went and restored each app. Now on the market it still says free which I dont have a problem. My concern is will I get notifcations for updates for the apps still even tho it says free for that app installed.
Well the first time I tried restoring my apps after a flash all of my apps said "Update available"... I started using that to get it to say "Installed" and then for no appearant reason they all said "Free". So I assume so... however I could be mistaken because my apps are stored to sd so I never have to technically restore my apps.
Binary100100 said:
Well the first time I tried restoring my apps after a flash all of my apps said "Update available"... I started using that to get it to say "Installed" and then for no appearant reason they all said "Free". So I assume so... however I could be mistaken because my apps are stored to sd so I never have to technically restore my apps.
Click to expand...
Click to collapse
Wait hold on...
If apps are stored to the SD card than we dont have to reinstall or back up our apps?
Lets say I have my apps installed to SD. Than I do Alt W wipe. My apps will still be there? I usally reformat my ext2 partition before I do an alt w wipe.
Sistum Id said:
Wait hold on...
If apps are stored to the SD card than we dont have to reinstall or back up our apps?
Lets say I have my apps installed to SD. Than I do Alt W wipe. My apps will still be there? I usally reformat my ext2 partition before I do an alt w wipe.
Click to expand...
Click to collapse
Not sure why you would need to reformate your ext2 partition.
I just follow the steps to restore the apps to sd.
I have all the .sh files stored to my sdcard and use gscript.
Here's is the script itself that I use...
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm -r /data/app
ln -s /system/sd/app /data/app
rm -r /data/app-private
ln -s /system/sd/app-private /data/app-private
reboot
Click to expand...
Click to collapse
and it restores all of my apps automatically.
The only thing is that i have to go back to market and install them again from market so that it won't say "update available" or "free" even though I have them installed already.
You can also check this out here. VERY USEFUL! All you need to do is plug in the directory of your adb.exe and the location of your apps that are backed up onto your computer and it installs the rest. Obviously you need to already have the apps to sd mod running before you do it.
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm -r /data/app
ln -s /system/sd/app /data/app
rm -r /data/app-private
ln -s /system/sd/app-private /data/app-private
reboot
Click to expand...
Click to collapse
That doesnt seem to be working for me. After I reboot I just get stuck in the endless flashing droid on statup.
Sistum Id said:
That doesnt seem to be working for me. After I reboot I just get stuck in the endless flashing droid on statup.
Click to expand...
Click to collapse
It may flash for a while. I noticed that mine flashed for about 2 or 3 minutes.
Binary100100 said:
It may flash for a while. I noticed that mine flashed for about 2 or 3 minutes.
Click to expand...
Click to collapse
LOL maybe that was it. I dunno, doesnt matter right now, my phone wont stay on longer than a few minutes before rebooting even after reflashing back to RC29. Having a new one sent out for replacment.
I am using the Switchrom script with CY recovery. I have successfully made backups and switched between roms using the script. Now I want to try the new Drizzy Hero rom. To install the rom I will have to wipe the ext3 partition. My question is, If I wipe the ext3 partition, will I loose the script? If yes, can I copy the script in system/sd later on for it to work again?
PS: Before someone posts "search the thread" answer, I tried doing it and couldn't find anything.
Thanks
bole_to said:
I am using the Switchrom script with CY recovery. I have successfully made backups and switched between roms using the script. Now I want to try the new Drizzy Hero rom. To install the rom I will have to wipe the ext3 partition. My question is, If I wipe the ext3 partition, will I loose the script? If yes, can I copy the script in system/sd later on for it to work again?
PS: Before someone posts "search the thread" answer, I tried doing it and couldn't find anything.
Thanks
Click to expand...
Click to collapse
The only thing that is stored on your ext3 partition is your apps. So when you clear that only your apps will get cleared.
supremeteam256 said:
The only thing that is stored on your ext3 partition is your apps. So when you clear that only your apps will get cleared.
Click to expand...
Click to collapse
Thanks man. Wiping now.
To clear this up for other reader who might stumble on this thread, the above comment is not true. If you wipe you ext 2/3 you might end up wiping more stuff than just apps. I realized it the hard way lol. However you can push back switchrom.sh in /system/sd and you will be good to go. The alternate method to do this is to delete just the following folders:
mount /dev/block/mmcblk0p2 /system/sd
rm -rf /system/sd/app*
rm -rf /system/sd/dalv*
bole_to said:
To clear this up for other reader who might stumble on this thread, the above comment is not true. If you wipe you ext 2/3 you might end up wiping more stuff than just apps. I realized it the hard way lol. However you can push back switchrom.sh in /system/sd and you will be good to go. The alternate method to do this is to delete just the following folders:
Code:
mount /dev/block/mmcblk0p2 /system/sd
rm -rf /system/sd/app*
rm -rf /system/sd/dalv*[/QUOTE]
You can do that or you can wipe buy doing this
Code:
mount /system/sd
mount /sdcard
rm -rf /system/sd/*
cp /sdcard/switchrom.sh /system/sd/switchrom.sh
That's how i've been doing it. And I like to do it this way to make sure the my EXT2/3 is completely clean. I've had problems where doing a partial wipe gives me issues. But yes if you wipe your EXT2/3 drive it will get rid of everything (including the switchrom.sh)
Click to expand...
Click to collapse
when you wipe your internal phone memory and ext3 you will lose the script. once you get the rom you flashed up and running again, just repush switchrom.sh and you are good to go again. wiping the ext 3 or the internal memory WILL NOT wipe out your backups. when i use switchrom i dont even wipe all of ext3...
this is what i do... flash a new rom. get it setup the way i want. install all apps and extra settings i want. reboot into recovery, run switchrom.sh and let it do its thing. now when you have created your back up and want to flash a NEW ROM, not one of your backups, wipe internal memory of course but instead of wiping all of ext 3 drop down to recovery console and do the following
Code:
# mount /system/sd
# rm -rf /system/sd/app*
# rm -rf /system/sd/dalv*
this will prepare your ext3 for a new install of a new rom. when you are going back and forth between your backups you do not need to wipe ext3 at all. the script takes care of all of that. if you have any more questions PM me or hit me up on gtalk - palosjr
NOTE- this script is case sensitive as i found out the hard way... when bookmarking and tagging ROMs be sure to use all lowercase. if you use uppercase the script will fail. hope this helps bro.
thanks guys, i got it to work.
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.
hey guys
wazzzzzzzup
so, I'm on CM7 and wanna download Pocket legends from the Market but it says that I don't have sufficient space. I've tried deleting dalvik cashe and no good.
the game size is 28mb.
Any Ideas???
themohd said:
Any Ideas???
Click to expand...
Click to collapse
Delete the files /cache/download*apk in order to get some more space for the downloads. Maybe that's sufficient. If not you can move the cache to a virtual disk. Try searching in the forum.
It's a market 3.* problem. The downloads shouldn't go to /cache and should also be cleaned up after succesful installation.
Thnx for the rep.
deleting downloadfile.apk wasn't enough, I remeber using a virtual cache didn't work for me before, imma try that again .
thanx again dude
Do this in CWM (recovery):
- wipe cache partition
- wipe dalvik cache
If it doesn't work and you have very little internal space left, uninstall 2 or 3 bigger games so that there's enough space again.
How much free space do you have in /datadata? (Use Root Explorer to check, etc.)
If it's less than 28mb (or however big the game is), you need to either: 1) delete some apps, or 2) move apps to sdcard.
Thanx guys,
But I solved the problem without deletin' anything, by moving the cache to /Data/Cache
if anyone need it, here is it how:
in the terminator write this:
mkdir /data/cache
busybox rm -rf /cache
busybox ln -s /data/cache /cache
and thats all
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