Related
I downloaded the leaked google music app from ICS, and it works great.
My only caveat is that when I choose to make something available offline, it goes straight to my internal storage (Motorola Atrix).
I have a 32gb microSD card with a dedicated folder for music. Is there a way I can get the offline songs onto there?
I currently use PlayerPro from the market, and I wanted to use the Google cloud for "wirelessly syncing" my music.
Any ideas?
Nobody was able to figure it out?
Does any other music player sync with google?
Wouldn't it be possible to somehow mount a folder that is located on the sd-card and link it to /sdcard/Android/data/com.android.music/cache just like it is done with the apps2ext hacks on low memory devices?
Would the file system of the sd-card then have to be ext instead of fat32?
Maybe someone who has more practical knowledge of the matter could look into this. I can only theoretically assume how it might work
I did some further research and found this post.
It describes how to mount an external sdcard to to /sdcard instead of sdcard. But would this also work with a subfolder of /sdcard?
I fiddled around myself a bit.
So here is what I did:
format sdcard as ext2
manually mount sdcard since it won't automatically when ext:
Code:
mkdir /Removable/MicroSD
mount -r -w -t ext2 /dev/block/vold/179\:9 /Removable/MicroSD
mkdir /Removable/MicroSD/GoogleMusicData
Then move all data from /sdcard/Android/data/com.google.android.music/cache to /Removable/MicroSD/GoogleMusicData/cache
I did this with root explorer since I'm not too much of a terminal h4xx0r.
Delete the folder /sdcard/Android/data/com.google.android.music/
Link the new Folder on external MicroSD Card to the original location via this terminal command:
Code:
ln -s /Removable/MicroSD/GoogleMusicData /data/media/Android/data/com.google.android.music
Since /sdcard is already a link like the one we are setting up here, it is not possible to link to this linked location (/sdcard/Android/data/com.google.android.music).
Instead we have to link to the origninal destination of /sdcard which is /data/media.
Now the microSD card is accessible for root explorer. It shows read and write access.
But google music won't find it. It says that it doesn't have enough space to stream music so I figure that it somehow doesn't have access to the sd card.
What could be the issue here?
Also instead of 28GB free memory root explorer shows me only 364,44MB free memory. the command "df" in terminal however confirms 28GB of free memory.
Help please?
EDIT:
I thought that a reboot might do it. But it doesn't. Instead it gets rid of all the hacking I've done in terminal. So I guess I would have to place a script in /etc/init.d for the link to be set everytime I reboot, right?
Another Fix (no sdcard formatting needed)
This is a fix i figured out piecing together other peoples attempts.
Use this as a script
mount -o bind sdcard2/android/data/com.google.android.music sdcard/android/data/com.google.android.music
Alternately you can change the first location to the location of your choosing as long as it resides on the external as card.
Ex.
Mount -o bind sdcard2/music sdcard/Android/data/com.google.Android.music
will bind:
sdcard/Android/data/com.google.Android.music (google's forced save location)
to
sdcard2/music
Go to google music (play music now) settings and clear any music that is currently saved to your device.
this only applies to music made available offline. If you do not clear it before running the script the music will exist on your internal sdcard but not be accessible.
open script manager and find the script you made
Select it and make sure to click set on boot and superuser
Run Your script.
That is it now your default save location for google music is bound to the location on the external sdcard. the device will see the location as its default but really be saving to the external sdcard.
You can check this by going to google music. Selecting "make available offline" and look at the free space. It should shoe the space available on your external sdcard.
TLR Version (noob version)
I was getting a lot of questions about the preliminary steps here (i.e. rooting, writing script, etc) so i decided to attach the noob version in case anyone needs verification on how to accomplish these steps.
HOW DO I ROOT?
So, Rooting gives you full access and control over your phone. instructions for how to root are device specific. so i would start by searching XDA for "YOUR DEVICE one click root"
ex. samsung galaxy s2 one one click root
some devices are easier to root than others. i cannot provide steps for your particular device, but through XDA, and google you CAN find everything you need.
some devices have one click root tools, some do not, so the rooting process is more in depth for those devices.
rooting instructions are so device specific i could not find a generic set of instructions, and don't want to mislead anyone by linking them to a set of instructions not compatible with their device.
There is a risk of bricking your device (making it inoperable) while rooting, although the risk is minimal... almost non existent if you carefully follow instructions. I have rooted 5 seperate devices without bricking any, and, in most cases even if bricked the device can still be restored.
there are additional benefits to rooting, such as overclocking
for example my Galaxy S2 normally runs at 1.5 GHZ, i have increased the speed to 1.8GHZ
(NOTE** Without XDA DEVELOPERS i would have rooted 0 devices, and probably bricked at least one, so thank you to all of you out there who have helped me, I hope this method will help some of you in return.)
NOW THAT YOU ARE ROOTED...
INSTALL SCRIPT MANAGER..
First, to install script manager just go to google market (Play Store) and search for script manager
INSTALL ES FILE EXPLORER..
To make a script go to google market (Play Store) and find ES File Explorer
WRITE SCRIPT..
Open es file explorer when install completes.
in es file explorer click the menu button, and select "new"
when prompted select "File"
name your file something you'll remember
Ex.MusicScript
Click your new file
when prompted select "Text"
type this EXACTLY how you see it
Mount -o bind sdcard2/music sdcard/Android/data/com.google.Android.music
press back and when prompted to save click yes
MAKE DESTINATION FOLDER..
now on es file explorer click "Favorites" (the star)
a new menu will pop up, at the top you willsee a picture of a phone with "/" underneath it click the phone
this will take you to the root directory
click the folder Sdcard2
click the menu button, and select "new"
when prompted select "Folder"
Name the folder music
Your script and destination music location are created
EXECUTE SCRIPT..
now open script manager
find your script which should be located in the directory /mnt/sdcard and the file name you chose earlier
select the script
open as script/executable
make sure script is selected not executable
click the buttons for "Su" and "Boot"
click save
Go to google music (play music now) settings and clear any music that is currently saved to your device.
this only applies to music made available offline. If you do not clear it before running the script the music will exist on your internal Sdcard but not be accessible.
now reboot the script will run at boot a prompt will appear asking for superuser rights, click yes and remember this selection (it may say something different than remember this selection whichever option resembles remember needs to be selected.)
YOU'RE DONE!!!
your music should now save to sdcard2/music but the device will still think it is saving to the default sdcard/Android/data/com.google.Android.music
You can check this by going to google music. Selecting "make available offline" and look at the free space. It should shoe the space available on your external sdcard.
So try your hardest to figure out how to root using google, and if your not confident enough to attempt it this fix may not be for you.
if you have tried everything you can and are still stuck message me back, including what device you have, and i will see if i can find a link to the rooting instructions for your particular device.
I assume no responsibility if you damage your device... These steps do work, and if followed will fix your music issues as well as introducing you to a world of additional benefits of being a rooted user.
Hey FuzzyMeep Two! Thanks for the great tutorial.
It worked, with some minor adaptions:
1.) The script should read "mount -o ...". Note that there's no space between '-' and 'o'. You got that right in the first script though
2.) On GalaxyS2 with JellyBean/4.1.1 the correct paths are storage/sdcard1 (external) and storage/sdcard0 (internal).
regards,
Patrick
Thank you
I just received my new 32gb SD card, and am wondering how to ensure that my ext3 partition is also copied over, not just the fat32 files. I have found some other threads regarding this process but I still have some unanswered questions.
FYI, I am using MIUI 1.11.4 on a rooted Acer Liquid E (and malez-recovery, which is based on CM).
1. The general consensus seems to be to do a nandroid backup, partition the new card with gparted, and restore that backup (and obviously copy the fat32 files to my computer and then transfer back). I'd just like someone to tell me I'm correct before I try it.
2. On every single one of the threads I found, it always says to do a nandroid backup. Do they really mean a nandroid+ext backup?! Will the basic nandroid backup do the trick (I don't see how)? I'm concerned about this because I always get errors when I attempt a nandroid+ext backup. I plan to run nandroid-mobile.sh -b -e via adb once my file transfer is complete (stupid slow old sd card + computer), but I'm not confident that it'll work. If it doesn't, what options do I have for accessing the ext3 partition? **UPDATE: I ran nandroid-mobile.sh, and it eventually said "--ext2 specified but unable to mount the ext2 partition". I'm still Googling but I haven't figured out a solution yet. Ideas?
3. Every thread recommends using gparted but provides no justification as to why. Since I am using Windows, the whole process seems over-complicated. Can I not just use the "partition sd card" available through recovery? Why is it better to use gparted?
Thanks for any help you can give a semi-n00b!
skittleys said:
1. The general consensus seems to be to do a nandroid backup, partition the new card with gparted, and restore that backup (and obviously copy the fat32 files to my computer and then transfer back). I'd just like someone to tell me I'm correct before I try it.
2. On every single one of the threads I found, it always says to do a nandroid backup. Do they really mean a nandroid+ext backup?! Will the basic nandroid backup do the trick (I don't see how)? I'm concerned about this because I always get errors when I attempt a nandroid+ext backup. I plan to run nandroid-mobile.sh -b -e via adb once my file transfer is complete (stupid slow old sd card + computer), but I'm not confident that it'll work. If it doesn't, what options do I have for accessing the ext3 partition?
3. Every thread recommends using gparted but provides no justification as to why. Since I am using Windows, the whole process seems over-complicated. Can I not just use the "partition sd card" available through recovery? Why is it better to use gparted?
Thanks for any help you can give a semi-n00b!
Click to expand...
Click to collapse
1. Do that (just do it ; in case anything goes wrong, you can restore the nandroid backup and have your device up and running easily). If you don't create one (make sure you do) you will have a hard time getting your device to work again (and depending on your device, it may not be fixable).
2. Just make a nandroid backup. Some roms have it enabled by default (access to the partition). See here: http://forum.cyanogenmod.com/topic/19160-modhow-to-apps2ext-for-cm7-updated-03312011/.
3. Using GParted is the easiest method (which is why it is recommended): http://gparted.sourceforge.net/.
Theonew said:
3. Using GParted is the easiest method (which is why it is recommended): .
Click to expand...
Click to collapse
Easier than 3 multiple-choice questions in a recovery I've already installed???
Theonew said:
2. Just make a nandroid backup. Some roms have it enabled by default (access to the partition). See here:.
Click to expand...
Click to collapse
I doubt that my ROM does an ext backup by default.... I have now run nandroid-mobile.sh and eventually got the following message: "Warning: --ext2 specified but unable to mount the ext2 partition". I'm still Googling but I haven't yet figured out a solution for this. In the meantime, I have copied /sd-ext to my computer, which might end up being a decent workaround...but I'd still love to know what's going on!
**UPDATE: Something I've noticed...:
If I access the phone after a "normal" reboot, /sd-ext definitely exists (I can see it using simply ls, and also mount and df), but no scripts are available in /sbin.
When I go into recovery, /sbin contains all the scripts (so I can now run nandroid), but /sd-ext doesn't appear!
I've a strong suspicion this is why the partition can't be mounted during the nandroid backup.
So how do I fix this?!
skittleys said:
Easier than 3 multiple-choice questions in a recovery I've already installed???
Click to expand...
Click to collapse
According to others, yes .
skittleys said:
**UPDATE: Something I've noticed...:
If I access the phone after a "normal" reboot, /sd-ext definitely exists (I can see it using simply ls, and also mount and df), but no scripts are available in /sbin.
When I go into recovery, /sbin contains all the scripts (so I can now run nandroid), but /sd-ext doesn't appear!
I've a strong suspicion this is why the partition can't be mounted during the nandroid backup.
So how do I fix this?!
Click to expand...
Click to collapse
You cannot "fix" it. That is one reason but it also really depends on your device. For example: http://www.jayceooi.com/2011/01/12/...tition-on-sd-card-with-clockworkmod-recovery/ - This device is able to do it from recovery and it is easier than the GParted method (at least on that device).
Theonew said:
You cannot "fix" it. That is one reason but it also really depends on your device. For example: - This device is able to do it from recovery and it is easier than the GParted method (at least on that device).
Click to expand...
Click to collapse
I think we're mixing up 2 different issues now.
Forget the partitioning method, I'll just use gparted.
But now there's a major issue: I can't make a nandroid+ext backup. I've used adb to copy everything from my current ext partition and can load it onto the new card's partition, but that might not be an effective solution -- will it break all the symlinks? I'm trying to figure out whether symlinks ultimately store a path (therefore links won't break because the directory structure is still the same) or an address (which will break the links if I'm just copying + pasting). I'm finding conflicting answers.
So now I'm asking about what this error means (why won't it mount), whether the behaviour I described in the "update" above is normal (no sbin in normal mode, no sd-ext in recovery), and what alternatives I have! (Oh, and also my symlinks Qs) Plenty of people using the same recovery have created nandroid+ext backups without problems, and all the posts I'm finding about the issue relate to older versions of AmonRa.
skittleys said:
I think we're mixing up 2 different issues now.
Forget the partitioning method, I'll just use gparted.
But now there's a major issue: I can't make a nandroid+ext backup. I've used adb to copy everything from my current ext partition and can load it onto the new card's partition, but that might not be an effective solution -- will it break all the symlinks? I'm trying to figure out whether symlinks ultimately store a path (therefore links won't break because the directory structure is still the same) or an address (which will break the links if I'm just copying + pasting). I'm finding conflicting answers.
Click to expand...
Click to collapse
It's quite likely that it will break the symlinks (just like .android_secure issues). Are you able to make a nandroid-only backup?
skittleys said:
So now I'm asking about what this error means (why won't it mount), whether the behaviour I described in the "update" above is normal (no sbin in normal mode, no sd-ext in recovery), and what alternatives I have! (Oh, and also my symlinks Qs) Plenty of people using the same recovery have created nandroid+ext backups without problems, and all the posts I'm finding about the issue relate to older versions of AmonRa.
Click to expand...
Click to collapse
What recovery are you using (include version)? It is a known problem for some recovery not being able to have access to the SD-ext partition (e.g. ClockworkMod Recovery 3.0.0.5 on some if not all devices). So you should be able to access the SD-ext partition in recovery, and you should be able to access sbin normally.
Theonew said:
It's quite likely that it will break the symlinks (just like .android_secure issues). Are you able to make a nandroid-only backup?
Click to expand...
Click to collapse
Yes, I can do a nandroid backup of the internal partitions. Also not sure what issues you're referring to. I did some research on symlinks and posted on a linux forum and concluded that it shouldn't break....
Theonew said:
What recovery are you using (include version)? It is a known problem for some recovery not being able to have access to the SD-ext partition (e.g. ClockworkMod Recovery 3.0.0.5 on some if not all devices). So you should be able to access the SD-ext partition in recovery, and you should be able to access sbin normally.
Click to expand...
Click to collapse
(I don't have enough posts to insert URLs) I am using Malez recovery 0.6.1 (current is 0.6.2, nothing in the changelog suggests any relevant fixes though). I've searched extensively and it seems that I'm the only malez user having this problem.
Also, I can access sbin, but its only contents are adbd and ueventd. /sd-ext just plain doesn't show up in recovery mode.
Question: who is the owner of your /system, /sd-ext, and /system/sd partitions?
And a possibly unrelated question: what's the point of running a command through busybox (e.g., busybox ls instead of just ls)?
skittleys said:
Yes, I can do a nandroid backup of the internal partitions. Also not sure what issues you're referring to. I did some research on symlinks and posted on a linux forum and concluded that it shouldn't break....
Click to expand...
Click to collapse
It shouldn't break, but on some roms it does.
skittleys said:
Question: who is the owner of your /system, /sd-ext, and /system/sd partitions?
Click to expand...
Click to collapse
What do you mean?
skittleys said:
And a possibly unrelated question: what's the point of running a command through busybox (e.g., busybox ls instead of just ls)?
Click to expand...
Click to collapse
Busybox adds additional commands that the normal android command system does not have/understand on it's own (It gives you additional LINUX/UNIX based commands). See here: http://busybox.net/about.html.
Theonew said:
What do you mean?
Click to expand...
Click to collapse
When you run ls -l the 3rd and 4th columns show the 'owner' and 'group', respectively. It'll say things like root, system, etc., or maybe 0, 1000, 500, etc.
Theonew said:
Busybox adds additional commands that the normal android command system does not have/understand on it's own (It gives you additional LINUX/UNIX based commands). See here: http://busybox.net/about.html.
Click to expand...
Click to collapse
So there's no point in running a command like ls through busybox, right?
New question:
All that /system/sd contains is a 0-byte file called 'placeholder'. I can't find much info about this, but it sounds like this is intentional. But I know that this is where the ext partition is supposed to mount to. Does yours look like this (in either normal mode or recovery)? (edit: in recovery mode, the placeholder is gone, replaced with another 0-byte file called 'empty')
Also, do you think you could paste the output of mount when run in recovery?
BTW, A2SD seems to work perfectly otherwise. The only oddity I've noticed is that when I run a2sd forcecheck near the end it tries to unmount the partiton and can't.
Code:
[ ] Launching Apps2SD Start Program with forcecheck
[ ] Starting Darktremor Apps2SD in forcecheck mode
[ ] Creating Force Check Flag File...
[ ] Unmounting /dev/block/mmcblk0p2...
umount: can't umount /sd-ext: Device or resource busy
[ ] Rebooting phone...
Ironic that I can't mount it in recovery yet I can't unmount it normally!
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 .
Hi, I'm using an LG Optimus L9 and running 4.3 bassed PAC-man rom.
The internal memory is 4GB and after installing a few apps, I started getting "Not enough storage space" warnings.
So, I checked the /data folder and found that there's directory called lost+found which is taking up a lot of space (Above 1.5GB).
I tried deleting files using ES Explorer with the data folder mounted as R+W, but it says "error deleting files"
Is it safe to delete the lost+found folder?
And if yes, how can I delete it since I'm unable to delete it with a file explorer app.
It would be really great if could recover thelost internal memory
void00 said:
Hi, I'm using an LG Optimus L9 and running 4.3 bassed PAC-man rom.
The internal memory is 4GB and after installing a few apps, I started getting "Not enough storage space" warnings.
So, I checked the /data folder and found that there's directory called lost+found which is taking up a lot of space (Above 1.5GB).
I tried deleting files using ES Explorer with the data folder mounted as R+W, but it says "error deleting files"
Is it safe to delete the lost+found folder?
And if yes, how can I delete it since I'm unable to delete it with a file explorer app.
It would be really great if could recover thelost internal memory
Click to expand...
Click to collapse
I don't think there is a problem doing that and change the permission to rwx-rwx-r try and report
sangalaxy said:
I don't think there is a problem doing that and change the permission to rwx-rwx-r try and report
Click to expand...
Click to collapse
I tried deleting the folder through adb shell.
Issued following commands:
adb shell
su
# cd /data
# rm -r lost+found
Click to expand...
Click to collapse
The output was "rm failed for lost+found. Operation not permitted"
Also tried this mounting /data as rw but no luck.
Tried chmod 775 on lost+found but no luck either.
Always getting operation not permitted message.
void00 said:
I tried deleting the folder through adb shell.
Issued following commands:
The output was "rm failed for lost+found. Operation not permitted"
Also tried this mounting /data as rw but no luck.
Tried chmod 775 on lost+found but no luck either.
Always getting operation not permitted message.
Click to expand...
Click to collapse
try r+w+x
sangalaxy said:
try r+w+x
Click to expand...
Click to collapse
Still getting the same error. Operation not permitted.
void00 said:
Still getting the same error. Operation not permitted.
Click to expand...
Click to collapse
may be something preventing it
try a reset and simply format the data in cwm do backup first
sangalaxy said:
may be something preventing it
try a reset and simply format the data in cwm do backup first
Click to expand...
Click to collapse
Using TWRP.
If I backup first, it will also back up the lost+found data
And restoring data will bring it back.
I did format data and system before flashing the rom. So I don't know why the lost+found has so large size.
What should I do?
void00 said:
Using TWRP.
If I backup first, it will also back up the lost+found data
And restoring data will bring it back.
I did format data and system before flashing the rom. So I don't know why the lost+found has so large size.
What should I do?
Click to expand...
Click to collapse
ok so don't backup
if anything goes wrong you can still flash the stock right??
sangalaxy said:
ok so don't backup
if anything goes wrong you can still flash the stock right??
Click to expand...
Click to collapse
hmm, i'll try flashing CWM and then do a format of every partition and freshly flash the rom.
Will report back if there's the same problem.
UPDATE:
Formatted all the partitions including /data/media using CWM
Did a fresh install of rom.
I've got my internal memory back
Thanks!
my 2 cents...
my 2 cents... I've opened the lost+found folder with the file manager (this https://play.google.com/store/apps/details?id=com.rhmsoft.fm), after enabling the root explorer functionality, and deleted a bunch of the biggest files, just checking they were at least 2-3 months old. Rebooted to make sure everything is fine and dandy, and now I've got enough free space, sun is chirping, birds are shining, life is beautiful :silly: :victory:
fabiosirigu said:
my 2 cents... I've opened the lost+found folder with the file manager (this *edited original link*), after enabling the root explorer functionality, and deleted a bunch of the biggest files, just checking they were at least 2-3 months old. Rebooted to make sure everything is fine and dandy, and now I've got enough free space, sun is chirping, birds are shining, life is beautiful :silly: :victory:
Click to expand...
Click to collapse
I was having the same problem. My phone is Samsung Galaxy S2 (GT-i9100). I was on stock Jellybean. But it was starting to feel sluggish and slow. So, having heard about the new Android Kitkat's lower memory requirements and smoother performance, i decided to install Cyanogenmod 11 on it.
Installation was not without problems. At first i flashed Clockworkmod Recovery 6.0.2.9. The phone bricked into a bootloop with a yellow triangle on it. Flashing the Cyanogenmod 11 resulted an error of "Status 7". So i searched for the latest Clockworkmod Recovery, which was at 6.0.4.5. After flashing the 6.0.4.5, Cyanogenmod 11 installed successfully. Performance was really smooth. No lags, no jitter, and everything worked like a charm.
The problem started when i re-installed my applications. Suddenly i got a message of "insufficient storage". This has never happened before. Note, that i previously had large games on my phone like Real Racing 3 and Bard's Tale. This time, i haven't even installed those large games. So i looked at my Storage, and found out that i only had 141mb of free space. But the weird thing is, my reported Apps was only 353mb, from 1.97GB internal storage. So there was over 1GB of storage just vanished.
I browsed for a solution to this problem, and landed on this thread. After reading reply from fabiosirigu, i decided to brave myself, and deleted the content of the lost+found folder (but not the folder itself). I accessed the folder with the built-in File Manager from Cyanogenmod, and set it to "Root Access Mode", and select all folder in the folder, and deleted it. The deletion took quite a few minutes, which felt like ages. Just sat on my bed, crossed my fingers, hoped that nothing will go wrong.
After the deletion, i rebooted my phone. the cyanogenmod logo appeared, and the system booted as usual. I just exhaled a massive sigh of relieve. I went straight to the internal storage, and now it is showing the correct report, 1.67GB of free space.
Thank you for your reply fabiosirigu. Really solved my problem.
lost+found genesis
Let somebody correct me if I'am wrong.
lost+found directory is standard for some unix/linux filesystems. All ext(s) 2, 3 and 4 contains it by default.
The operating system collects unidentified, broken files and its parts inside of l+f dir.
No one of these junks is used by running system.
So - you can look in l+f for some lost, missing files. If you don't miss for any (who knows it better?) then you don't need l+f content.