Related
Hi guys,
Can anyone offer me any advise with Apps to SD?
I have rooted my Hero and installed the RA-HERO-v1.2.3 recovery image.
I have then wiped my SD card and selected the option to partition the card in the recovey menu.
However when i boot up the Apps to SD application it says that my card doesnt seem to be partitioned correctly and wants me to set up the EXT2 partition?
After a bit of Googling i found theres some adb commands that can set this up after partitioning (which i assume is set up correct - any way to tell?) The commands are :-
Code:
adb devices
adb remount
adb shell
cp -a /data/app /system/sd
cp -a /data/app-private /system/sd
rm -r /data/app
rm -r /data/app-private
ln -s /system/sd/app /data/app
ln -s /system/sd/app-private /data/app-private
However i get as far as the cp commands and it says it is an unknown command?
Any help would be much appreciated - was up til past 2am this morning trying to figure this out with no luck
Thanks
Paul
Try this guide, worked perfectly for me.
Thanks for that - it at least let me check everythings partitioned up correcty.
Still Apps 2 SD wont work.
One thing i forgot to mention previously is that i'm using an official HTC rom - does this only work with custom roms? I thought the only requirement was Root access?
Ive spotted 2 versions of Apps2sd on the market
Apps2sd - gives error 'Either an incorrect ROM is installed or your SD card is not formatted correctly'
Apps2sd 2 - gives me the option of creating an EXT2 partition (with a slider)
Cheers
Paul
I'm not a 100% sure(maybe someone else can confirm) but yes I think it only works with custom roms. I rooted my Hero the day I got and have never used the stock rom.
Unless there is a specific reason you need to use a stock rom maybe consider using a custom one? Now that the source code is out I would have though more roms will be coming soon.
here are your solution...
http://forum.xda-developers.com/showthread.php?t=552591&highlight=modaco+Rom
and
http://android.modaco.com/content/htc-hero-hero-modaco-com/292018/23-10-2-8-modaco-custom-rom-core-chinese-with-mck-featuring-wavesecure/
I fixed all my problems with this...
root your phone... than copy the zipped custom ROM in your SD...than update it...
u will find everything in the forums...
Hamo
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
Hello.
I'm facing the infamous problem of "not enough space" when downloading from the market, while I actually have plenty of space. The ultimate solution seems to be moving download cache to the SD card (symbolic link). The problem is that the download cache with ICS and Google Play isn't located in /cache/download anymore, and I have been unable to find where it is located both searching with Google and browsing the filesystem.
Any help?
Look in the market for opda system tuner lite, it'll clean it right up
Go to /data/app/ and delete the Titanium Backup ODEX. If this doesn't work, read the PM I'm about to send you (moda will complain it's illegal (it isn't for this purpose though)).
Sent from my GT-I9100 using XDA
Hello. Thank you both for replying, but you both answered a different question than the question I asked. I have already tried to clean market cache, to no success, and I believe very strongly that the solution is moving download cache to the SD card. I found lots of people with Google having my very same problem and fixing it this way. The problem is that I am now using MIUI ICS with Google Play, and the download cache location is different. Does anyone know where the download cache is located with ICS / Google Play Store?
Just to be 100% sure I also tried okmijnlp solution, and as I was expecting it didn't fix the problem.
Ok, solved the problem myself. The folder I had to link to SD card is /data/data/com.android.providers.downloads/cache. This worked on a MIUI v4 ROM (after rebooting).
Black Antitoon said:
Ok, solved the problem myself. The folder I had to link to SD card is /data/data/com.android.providers.downloads/cache. This worked on a MIUI v4 ROM (after rebooting).
Click to expand...
Click to collapse
Could you please advice how you have changed this, as i am new Android user hence not much aware how do go about it.
Hello.
I have bad news for you: after writing my last post here I realised that the problem wasn't actually solved (it only worked fine for a few hours), so linking that folder to the SD card is not a solution to the problem I was experiencing. However you are likely to need to link some folder to another one on your phone at some time, so I am explaining you these steps anyway.
First, you need to be on a rooted ROM. If you aren't, then have a look on the forum about your device here on xda and good luck for the rooting process.
Afterwards, you need the "Terminal emulator" application. If you don't have it, please download it from the market. Then run it and enter the following command:
Code:
su
This will give root rights to the terminal emulator app.
Now you can run the following commands.This will create the new folder on your SD card:
Code:
mkdir /sdcard/downloads
This should move all the contents of the "cache" directory into the new directory which you have just created:
Code:
mv /data/data/com.android.providers.downloads/cache/* /sdcard/downloads/
This should delete the now empty cache folder:
Code:
rm /data/data/com.android.providers.downloads/cache
This will finally created a symbolic link which has the same name of the old cache folder but points to the new folder on your SD card:
Code:
ln -fs /sdcard/download /data/data/com.android.providers.downloads/cache
I am not a Linux expert and I haven't tested these commands on my phone right now, so I'm not 100% sure that I haven't done any mistakes.
thanks for your reply
the solution didnt work for me as i dont have same .com folder. i tried searching on google and below steps helped in resolving the cache issue
1. You gonna need Android Terminal Simulator or equivalent terminal app. This will also require your Android rooted.
2. Type ’su’ (root permission request will be showned, you need to approve it).
3. Type ‘cd /’
4. Type ‘umount /cache’
5. Type ‘mount -o rw,remount -t rootfs rootfs /’ (to set the folder access to rw – read write)
6. Type ‘rmdir /cache’ (delete cache folder)
7. I personally using root explorer to do point 5-6
8. Type ‘mkdir /sdcard/cache’
9. Type ‘ln -s /sdcard/cache /cache (to link cache folder to /sdcard/cache – which should have bigger partition size)
Now i am able to download 30MB application on my phone from market.
Black Antitoon said:
Ok, solved the problem myself. The folder I had to link to SD card is /data/data/com.android.providers.downloads/cache. This worked on a MIUI v4 ROM (after rebooting).
Click to expand...
Click to collapse
Yes, it works for me using the root explorer under CM10.0. Thanks.
Hi!
I'm having the same trouble with not enough space, and when i run these command, it says operation not permitted. What to do? :/ It says thatsome sd card doesn't allow links?
Have you typed "su"? What happened then?
In any case, let me repeat that the procedure above eventually did NOT solve the download cache problem, if this is what you are looking for. The only solution for me was switching to a different ROM.
It's not need to use the console (Terminal Emulator). Just do the following:
1. Install Root Browser Lite (grand rood permissions if neccessary)
2. Delete the /data/data/com.android.providers.downloads/cache folder
3. Create the /sdcard/cache folder
4. Go to sdcard, select the new created cache folder by long press and choose 'Create shortcut' from list, you will see 2 buttons, 'Create' and 'Cancel'
5. Go to /data/data/com.android.providers.downloads/ and tap 'Create' button below
6. Enjoy!
You can use any other root file manager, of course.
The download cache was also at /data/data/com.android.providers.downloads/cache/ on the 4.2.1 jellybean ROM I'm running right now as well.
Thanks for posting the info!
wilderwind said:
It's not need to use the console (Terminal Emulator). Just do the following:
1. Install Root Browser Lite (grand rood permissions if neccessary)
2. Delete the /data/data/com.android.providers.downloads/cache folder
3. Create the /sdcard/cache folder
4. Go to sdcard, select the new created cache folder by long press and choose 'Create shortcut' from list, you will see 2 buttons, 'Create' and 'Cancel'
5. Go to /data/data/com.android.providers.downloads/ and tap 'Create' button below
6. Enjoy!
You can use any other root file manager, of course.
Click to expand...
Click to collapse
Thank you for your extremely clear explanation!
Nevertheless, despite having resolved the problem of lack of space for downloading apps from the store, with the help of your expertise, now everytime i reboot the device it shows me the message "android.process.media has stopped..."
I know it is related with the shortcut for the cache downloads.
Do you know how can I fix it?
Thank you.
TX a lot
Black Antitoon said:
Ok, solved the problem myself. The folder I had to link to SD card is /data/data/com.android.providers.downloads/cache. This worked on a MIUI v4 ROM (after rebooting).
Click to expand...
Click to collapse
+1000
Guys any idea how to change the default appdata storage...
\data\data\com.google.android.apps.currents
to
sdcard\Android\data\com.google.android.apps.currents
coz currents stores both cache and data to internal mem...which takes a whopping 100-150mb itself
can i change some vaules to make it store in the sdcard instead.....
I dont know why Google does some stupid stuff it does...
and pl dont suggest s2e app2sd, link2sd etc etc...
i already use s2e...w/o data moved ...
i want data on internal only
bump
Just download 1Tap Cache Cleaner and clear your app caches once in a while. All apps accumulate some cached data so you can free space by clearing them. It's much easier this way.
Sent from my Desire HD using xda premium
sashank said:
Just download 1Tap Cache Cleaner and clear your app caches once in a while. All apps accumulate some cached data so you can free space by clearing them. It's much easier this way.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
what a douche ...
what a fool you are...
:rofl:
how im i suppose to read the content after clearing the cache...
so what then waste my mobile data again and again to re sync the same content which was cached earlier...
the caches are not create so that you can have fun deleting them...
and be proud of your achievement
bump
Remap Cache folder to SD card
So the combined size of Currents cache and content is more free than your internal memory? Not a for sure fix, but looks like folks were able to use terminal commands to remap their market cache to SD card, could try modifying the instructions found here, but substituting the folders that apply to your problem with Google Currents.
Check it out here...
http://forum.xda-developers.com/showpost.php?p=19042043&postcount=4
Quoted for anyone else with the problem.
rxwookie said:
That one I think I understand... but, unfortunately the answer is that the Dalvik cache partition (where the market APK's are downloaded to) on many original Samsung devices (i.e. Fascinate) is only about 35 MB in size. Anything larger will get rejected as being too big. Most of the newest devices have a larger download partition.
I've seen a few posts on different forums on remapping the download cache to a different, larger partition... but nothing specific to our devices. I've tried following other posts just to see if it works, but suceeded only in either having no effect or messing it up worse and having to reinstall the ROM (not a big deal, but frustrating).
Until one of the smart people here tells us how to remap **our** cache to a larger partition... I'd do a Google search for the APK of the app you are trying to install. That worked for me to install an app about 40 MB in size.
** edit **
I see that you were able to download the app after deleting everything in the cache folder. I guess your device is lucky enough to have a larger download partition than mine does
Glad to see you got it to work!
** 2nd edit - How to remap your market cache to the SD card **
-- UPDATE -- (Thanks to grickson here at XDA)
Problem: Insufficient Storage Space Available (Android Market)
Possible Solution: Remap cache folder to your SD card
** WARNING **
I am not responsible if you mess up your device doing the following. It manually remaps your market cache to your SD card to give you extra space. The only caveat is that if you remove your SD card (or while the SD card is unmounted) the market will not work. If you are worried about losing market functionality, DON'T try this. If you mistype (or the world suddenly tips over or some other unforeseen consequence), you can ruin your ability to run the Android Market at all. Please remember, you can repeatedly clear your Dalvik cache as often as needed to continue downloading apps. you can also get most larger APK's if you spend a few minutes browsing for them. You have been warned!
** END WARNING **
1.) Download and install a terminal emulator
2.) Open the terminal emulator and type su
3.) Allow the app to always have root access and exit
4.) Restart the terminal emulator and type su, the prompt should change to a #
5.) Type the following commands:
# cd /data/data/com.android.vending
# rm -R cache
# mkdir /sdcard/cache/
# mkdir /sdcard/cache/marketCache
# ln -s /sdcard/cache/marketCache cache
- What these commands do are (in order): change directory to your cache folder, delete the entire cache folder, create a directory on your SD card named cache, create a subdirectory in that one called marketCache, link the phone's market cache to the newly created folder on your SD card
To reverse this process (hopefully):
1.) Open the terminal emulator and type su
2.) Type the following commands:
# cd /sdcard/cache/
# rm -R marketCache
# mkdir /data/data/com.android.vending/cache
# ln -s /data/data/com.android.vending/cache cache
Alternately, (from what I understand) you can just repartition your device and reinstall your ROM of choice using ODIN and your market should be back to the way it was.
Click to expand...
Click to collapse
any more suggestions guys...
vNa5h said:
Guys any idea how to change the default appdata storage...
\data\data\com.google.android.apps.currents
to
sdcard\Android\data\com.google.android.apps.currents
coz currents stores both cache and data to internal mem...which takes a whopping 100-150mb itself
can i change some vaules to make it store in the sdcard instead.....
I dont know why Google does some stupid stuff it does...
Click to expand...
Click to collapse
Hello,
regarding ur following post :
http://forum.xda-developers.com/showthread.php?t=2123131
Have u found any solutions yet ?? if so please share as i'm facing the same problem. The App "New Scientist" stores about 2GB data in /data/data/com.newscientist.blabla folder,, and it takes up almost all of phone's memory.
I want to change this directory to sdcard.,, and as you already mentioned in ur post,, link2sd, foldermount etc are waste of time but don't know why people keep quoting them whenever i ask this.
As you've raised this issue about an year ago,, hopefully you might've fount out a solution/ work around. If so please help. Thank you,
coolvipcandy said:
Hello,
regarding ur following post :
http://forum.xda-developers.com/showthread.php?t=2123131
Have u found any solutions yet ?? if so please share as i'm facing the same problem. The App "New Scientist" stores about 2GB data in /data/data/com.newscientist.blabla folder,, and it takes up almost all of phone's memory.
I want to change this directory to sdcard.,, and as you already mentioned in ur post,, link2sd, foldermount etc are waste of time but don't know why people keep quoting them whenever i ask this.
As you've raised this issue about an year ago,, hopefully you might've fount out a solution/ work around. If so please help. Thank you,
Click to expand...
Click to collapse
I have the same issue. Since this was posted 2 years ago I hope you have solved it. I want app data which gets download internally to be saved in my internal storage.
I have edited the apk so that it gets installed in my internal storage but I can't find a way for app data.
Thanks in advance.
Karandeep Padam said:
I have the same issue. Since this was posted 2 years ago I hope you have solved it. I want app data which gets download internally to be saved in my internal storage.
I have edited the apk so that it gets installed in my internal storage but I can't find a way for app data.
Thanks in advance.
Click to expand...
Click to collapse
sorry for late reply, i didn't find any promising solution and finally got myself a phone with bigger space.
Its 2020 , has anyone found a way to change apps data path ? I thought could fix problem when trying Kali linux on phone even though moved it to sd card . I installed VMOS and moved it but same problem .
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.