Related
Can anyone tell me where the music is stored on my device whenever I select a file to be available offline in Google Music?
Sent from my SAMSUNG-SGH-I997 using XDA App
Good question. I searched my internal and external SD, but didn't see it...
In for answer
/sdcard/external_sd/Android/data/com.google.android.music/cache/music/
So I'm assuming that sd_card/external_sd/ is my 2gb external card. Is that correct? If so I wonder why it saves to the external sd. I haven't bought a bigger card yet. I can't find a way to change where the files are saved.
Sent from my SAMSUNG-SGH-I997 using XDA App
Kmo78 said:
So I'm assuming that sd_card/external_sd/ is my 2gb external card. Is that correct? If so I wonder why it saves to the external sd. I haven't bought a bigger card yet. I can't find a way to change where the files are saved.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
Doesn't look like there is a way to change the cache location. Time to get a bigger SD card!
I decided to do a little experimenting with this. I removed my sd card and when I turned my phone on google music began downloading the 15 songs I had selected to be available offline. I went to the /sdcard/external_sd/ directory and the files were there without an external card installed. So is this path just a shortcut to the external card? It's kinda weird. I'd prefer to have the songs saved to the phone. Hopefully google will give us an option in an updated version of the application.
Sent from my SAMSUNG-SGH-I997 using XDA App
I was kind of surprised by this thread as I have the opposite problem, my music is synced to sdcard/data, instead of external_SD where I want it.
Guessing since you posted this you don't know how you got it synced to external?
Mixy said:
I was kind of surprised by this thread as I have the opposite problem, my music is synced to sdcard/data, instead of external_SD where I want it.
Guessing since you posted this you don't know how you got it synced to external?
Click to expand...
Click to collapse
Same thing here!
I'm having the same problem here on my transformer. Maybe someone wants to look at what I've been trying so far and join in solving this: http://forum.xda-developers.com/showthread.php?t=1476972
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.
FuzzyMeep Two said:
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.
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.
Click to expand...
Click to collapse
This method doesn't work on my Evo 4G LTE. Still shows the internal SD available space on "Make available offline" Does it matter if I'm using a 64GB card?
@GMtom1 are you sure that you got whatever your sd card is labed as right? I haven't tried this method yet, but that seems to be the biggest point of failure for us evo lte users that are bringing our cards from other devices
******
gmtom1 said:
This method doesn't work on my Evo 4G LTE. Still shows the internal SD available space on "Make available offline" Does it matter if I'm using a 64GB card?
Click to expand...
Click to collapse
I have been having problems too... After i re-flashed my device, it has not been just working the way it did before, the script wouldn't work, so i believe that me installing Busybox or BASH, or something like that well before i made the script, was allowing the script to work properly. But, in the mean time, find "Directory Bind" it works perfectly...
p.s make sure you clear any music of of your internal sdcard, or it will still exist, but be inaccessible.
gmtom1 said:
This method doesn't work on my Evo 4G LTE. Still shows the internal SD available space on "Make available offline" Does it matter if I'm using a 64GB card?
Click to expand...
Click to collapse
Same..I tried it, made sure busybox was installed and still didn't work on my Evo 4G LTE
Anyone gotten to work on (Verizon) Galaxy S3?
I just tried to do this via your method and using the DirectoryBind utility, and both versions don't seem to like the path of my external SD Card (extSdCard).
Screenshots attached.
My script was:
Code:
mount -o bind extSdCard/music sdcard/Android/data/com.data.google.android.music
also tried with
Code:
mount -o bind /mnt/extSdCard/music sdcard/Android/data/com.data.google.android.music
FWIW the directory extSdCard exists
sti3 said:
I just tried to do this via your method and using the DirectoryBind utility, and both versions don't seem to like the path of my external SD Card (extSdCard).
Screenshots attached.
My script was:
Code:
mount -o bind extSdCard/music sdcard/Android/data/com.data.google.android.music
also tried with
Code:
mount -o bind /mnt/extSdCard/music sdcard/Android/data/com.data.google.android.music
FWIW the directory extSdCard exists
Click to expand...
Click to collapse
was getting the same errors as you are until I added the mnt/ in both paths.
mount -o bind mnt/sdcard/external_sd/gmusic mnt/sdcard/Android/data/com.google.Android.muisic
and I am good to go, 30GB of storage just waiting to be filled with music.
esox23 said:
was getting the same errors as you are until I added the mnt/ in both paths.
mount -o bind mnt/sdcard/external_sd/gmusic mnt/sdcard/Android/data/com.google.Android.muisic
and I am good to go, 30GB of storage just waiting to be filled with music.
Click to expand...
Click to collapse
I apologize for the gravedig, but I've been struggling significantly getting this to work on my Galaxy S3.
As a previous poster above said, because my external SD card is mounted at /mnt/extSdCard there are problems.
My command is:
Code:
mount -o bind /mnt/extSdCard/MusicCache /mnt/sdcard/Android/data/com.google.android.music
and it doesn't work at all...
Any idea why?
So I was on CleanROM 5.6 and wanted to give 10.1 a shot. I made a backup and downloaded it to my computer via the ROMManager tool. I ran into 2 issues with 10.1 and decided I'd try again later, so I wanted to flash back to my CleanROM backup that I'd just made. Whether via ROMManager or going straight into recovery the process says it can't open the path to the file. I say the path, as this has occurred with the zip image on internal memory and when I've tried on the SD card.
Soooo, now I'm pretty stuck. Thoughts? I felt like it must have related to the new 4.2 file structure but again, this was an issue whether my zip was on internal memory or the card.
Thanks,
BH
The exact process is:
installing [path]
finding update package.
opending update package.
e: cant open [path] (bad)
installation aborted
CWM says it's leaving a log file but I am not seeing it.
Sounds like your filesystem is like this: "/sdcard/0" and if it is, then do the following:
use Root Explorer or a similar program and navigate to /sdcard/0/ press Menu should give you an option for Multi-Select, select all the folders/files in the /0/ directory, hit menu or down on the bottom choose Move (again depends on the browser) back up one level to the main /sdcard/ directory, and hit Paste. It will tell you there is files with the same information (because the ROM rebuilt the file structure) choose Merge, and let it do its thing. Depending on how many files you have, it may take a little while, just be patient.
Click to expand...
Click to collapse
taken verbatim from here:
http://rootzwiki.com/topic/37316-protip-42-and-recoveries/
I'm going to give it a shot now. I wouldn't have thought this would be an issue restoring since the zip was accessible and I even tried flashing from internal mem, but perhaps it's not as much as issue of reading the file as knowing where to extract the data? We'll see.
All in all, if I could just get 10.1 to stop giving me market errors (920) I'd probably just stick with that at the moment. Alas, have tried all of the interweb's solutions for that too.
Will update, thanks.
So I don't have a /0/ dir on the card, but I do have a /1/. Tried moving the contents of /1/ but it failed. May try another file explorer app (this was via CMs). Interestingly, I was able to flash a ClearnROM install zip, which is 4.1.1 based. Why would that work but the constructed backups wouldn't?
update: I can flash anything else regardless of location, and I am using the latest recovery. def seems like something specific to zip backups made/downloaded via the newest means in ROM Manager
monorailmedic said:
So I don't have a /0/ dir on the card, but I do have a /1/. Tried moving the contents of /1/ but it failed. May try another file explorer app (this was via CMs). Interestingly, I was able to flash a ClearnROM install zip, which is 4.1.1 based. Why would that work but the constructed backups wouldn't?
update: I can flash anything else regardless of location, and I am using the latest recovery. def seems like something specific to zip backups made/downloaded via the newest means in ROM Manager
Click to expand...
Click to collapse
Well if the rom zip is on /sdcard or /extsdcard then it will flash fine. If your backups are on /sdcard/1/ then that's literally the same as /0/. Recovery is looking for your Nandroid backup on /sdcard but it's not there, it's actually been unnecessarily moved to /sdcard/1/ if I'm understanding you correctly. You will not be able to restore a nandroid until you get those files moved back to the proper file path.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Well if the rom zip is on /sdcard or /extsdcard then it will flash fine. If your backups are on /sdcard/1/ then that's literally the same as /0/. Recovery is looking for your Nandroid backup on /sdcard but it's not there, it's actually been unnecessarily moved to /sdcard/1/ if I'm understanding you correctly. You will not be able to restore a nandroid until you get those files moved back to the proper file path.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I have a similar problem with my file system after flashing from 4.2 back to 4.1 that has me confused.
I flashed to a TW rom after being on CM10.1, and I was using the most recent TWRP when I originally flashed CM10.1. I had the usual problem that everybody seems to have being that the "0" folder was located on my card. I copied the fold over to my normal sdcard folder (unfortunately I used root browser instead of root explorer, which made this much more painful as it does not have the "merge" ability. Root Explorer - accept no substitutes)
After doing the merge though, I have 2 problems.
#1 - My external SDcard is now listed under "storage."
#2 - There is an Sdcard there called "sdcard0 as well as a "extSdCard" in this storage folder with all the same information as the original "0" folder that was on the internal sdcard. Also a bunch of folders named UsbDriveA, UsbDriveB, etc.
Why did this happen? And how should I set up my folders so that it behaves properly? In other words, what does a normal file system look like?
SlimSnoopOS said:
...Recovery is looking for your Nandroid backup on /sdcard but it's not there, it's actually been unnecessarily moved to /sdcard/1/ if I'm understanding you correctly. You will not be able to restore a nandroid until you get those files moved back to the proper file path...
Click to expand...
Click to collapse
So this is where I am confused, does the zip not contain all of the appropriate backup data within itself, and it is looking elsewhere (in the wrong path) for backup data? This seems odd based on the whole idea as well as the size of the file. If this is not the case, when why is whatever scripting is included in the backup looking for an absolute and not a relative path to the data? It should always be relative to the location of the zip file itself.
I really want to try and understand this.
PeterGunz said:
I have a similar problem with my file system after flashing from 4.2 back to 4.1 that has me confused.
I flashed to a TW rom after being on CM10.1, and I was using the most recent TWRP when I originally flashed CM10.1. I had the usual problem that everybody seems to have being that the "0" folder was located on my card. I copied the fold over to my normal sdcard folder (unfortunately I used root browser instead of root explorer, which made this much more painful as it does not have the "merge" ability. Root Explorer - accept no substitutes)
After doing the merge though, I have 2 problems.
#1 - My external SDcard is now listed under "storage."
#2 - There is an Sdcard there called "sdcard0 as well as a "extSdCard" in this storage folder with all the same information as the original "0" folder that was on the internal sdcard. Also a bunch of folders named UsbDriveA, UsbDriveB, etc.
Why did this happen? And how should I set up my folders so that it behaves properly? In other words, what does a normal file system look like?
Click to expand...
Click to collapse
See my attached photo for what your file system should look like. I'm using ES File Explorer and that's my file system.
What do you mean your external SDcard is listed under Settings/Storage? Both of mine are listed, internal storage is first then my external sd card is second. Care to screenshot what you mean?
monorailmedic said:
So this is where I am confused, does the zip not contain all of the appropriate backup data within itself, and it is looking elsewhere (in the wrong path) for backup data? This seems odd based on the whole idea as well as the size of the file. If this is not the case, when why is whatever scripting is included in the backup looking for an absolute and not a relative path to the data? It should always be relative to the location of the zip file itself.
I really want to try and understand this.
Click to expand...
Click to collapse
If you're using CWM, it saves your backups for internal sd card in: /sdcard/CWM/backup and blobs. For your external sd card, it's saved /extsdcard/CWM/backups and blobs. If you flashed any AOSP 4.2 rom, it moves EVERYTHING from your /sdcard/ path to /sdcard/0. See the difference? Example, your music should be in this path /sdcard/Music but instead it's been moved to /sdcard/0/Music on AOSP 4.2. I get what you're saying how it should be looking for where the zip is BUT the multi-user support completely disrupts our entire thinking of how our file system should be because one user could be "rooted" whereas the other user would be completely stock depending on who signed in. It's too early to expect this to just work since Google introduced this in 4.2. It's a take it or leave it thing.
Sent from my SCH-I535 using xda app-developers app
For a standard backup that makes total sense. My confusion is how this happens with a zip, when all of the backup data is confined to that one archive file (or at least should be).
monorailmedic said:
For a standard backup that makes total sense. My confusion is how this happens with a zip, when all of the backup data is confined to that one archive file (or at least should be).
Click to expand...
Click to collapse
When you made a backup with Rom Manager, it saved to /sdcard, since flashing 4.2, everything on /sdcard moved to /sdcard/1/... Rom Manager and any app honestly would have issues when the file location has changed suddenly and without its express permission. It's not the fault of Rom Manager that it can't find the file to restore your backup. Having an updated TWRP or CWM is supposed to help prevent the /sdcard contents from being merged to /sdcard/0, its not supposed to continue looking for the "new" file destination.
SlimSnoopOS said:
See my attached photo for what your file system should look like. I'm using ES File Explorer and that's my file system.
What do you mean your external SDcard is listed under Settings/Storage? Both of mine are listed, internal storage is first then my external sd card is second. Care to screenshot what you mean?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Sorry, I can see what I said was confusing.
On the root of my device, among the usual folders, there is one named "sdcard" and another named "storage."
In the "sdcard" folder, all of the folders were empty; however, there is a folder named "0" which contained all of my sdcard contents from my internal sdcard.
In the "storage" folder from the root of my file system, it resembles what you have in your screenshot, except there are no asec and obb folders. In the sdcard folder is a replica of the 0 folder. It contains everything that was in my original internal sdcard. The extsdcard contains everything normally found on my external sd card.
When download something with the stock browser, it defaults to the sdcard folder on the root of file system.
I've attached some screenshots. Let me know what you think and thank you for the help.
PeterGunz said:
Sorry, I can see what I said was confusing.
On the root of my device, among the usual folders, there is one named "sdcard" and another named "storage."
In the "sdcard" folder, all of the folders were empty; however, there is a folder named "0" which contained all of my sdcard contents from my internal sdcard.
In the "storage" folder from the root of my file system, it resembles what you have in your screenshot, except there are no asec and obb folders. In the sdcard folder is a replica of the 0 folder. It contains everything that was in my original internal sdcard. The extsdcard contains everything normally found on my external sd card.
When download something with the stock browser, it defaults to the sdcard folder on the root of file system.
I've attached some screenshots. Let me know what you think and thank you for the help.
Click to expand...
Click to collapse
Oh! This is actually funny, we've been looking at the same thing from two different viewpoints. I see what you mean, /Storage and /sdcard are perfectly normal when you see them on the absolute root file system: "/". I always go to /mnt, that's where I have my file explorer default to open when I launch the app. Sdcard0 = sdcard, and various apps will use the names interchangeably. I have exactly the same paths /sdcard and /Storage, and I do see /Storage/sdcard0 and /Storage/extsdcard along with the same empty USB Drive folders. This is just how the "/" directory is split up. There isn't a duplication of files taking up more space than necessary, it's just showing you another path to get to those files. To reiterate, on "/" you can get to your sdcard contents in at least three paths: /mnt, /sdcard, and also /Storage/sdcard0
All that matters is the /sdcard/0 aka /Storage/sdcard0/0 is GONE. Which, in your original post you said no longer exists correct?
Sent from my SCH-I535 using xda app-developers app
I am still not understanding how there is a problem with executing a zip file that contains all the backup data. It doesn't matter where I move this zip file, as it seems it should be all inclusive of the backup data. Why does it matter the path of this file? What is the script looking for during restoration? Shouldn't it be looking within the archive?
I'm sorry, I feel like a tool, but again, I'm obviously missing some very basic part of what is happening when the file is accessed. As it is all inclusive, why is recovery looking for content anywhere outside of the archive?
monorailmedic said:
I am still not understanding how there is a problem with executing a zip file that contains all the backup data. It doesn't matter where I move this zip file, as it seems it should be all inclusive of the backup data. Why does it matter the path of this file? What is the script looking for during restoration? Shouldn't it be looking within the archive?
I'm sorry, I feel like a tool, but again, I'm obviously missing some very basic part of what is happening when the file is accessed. As it is all inclusive, why is recovery looking for content anywhere outside of the archive?
Click to expand...
Click to collapse
Backups cannot be flashed like other ZIP files. They need to be restored using the restore function of your recovery. The problem is that the CWM restore function is looking for its backups where it puts them (not surprisingly). Android 4.2 moved them to another location and you need to move them back.
SlimSnoopOS said:
Oh! This is actually funny, we've been looking at the same thing from two different viewpoints. I see what you mean, /Storage and /sdcard are perfectly normal when you see them on the absolute root file system: "/". I always go to /mnt, that's where I have my file explorer default to open when I launch the app. Sdcard0 = sdcard, and various apps will use the names interchangeably. I have exactly the same paths /sdcard and /Storage, and I do see /Storage/sdcard0 and /Storage/extsdcard along with the same empty USB Drive folders. This is just how the "/" directory is split up. There isn't a duplication of files taking up more space than necessary, it's just showing you another path to get to those files. To reiterate, on "/" you can get to your sdcard contents in at least three paths: /mnt, /sdcard, and also /Storage/sdcard0
All that matters is the /sdcard/0 aka /Storage/sdcard0/0 is GONE. Which, in your original post you said no longer exists correct?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Correct!
You helped me solve my problem. I was so confused for awhile there.
What should I rename my sdcard after copying everything over from "0"?
I just flashed back to 4.2.1 (AOLP) and I cannot find the contents of my internal sdcard anywhere. In fact, when I check storage on the system settings it only shows that I have a little over 12gbs total space on the internal sdcard. The 8gb I have on TW on the internal sdcard are not recognized by the rom. Any thoughts?
Is there a safe, proven method for moving apps out of internal storage and into an external SD on the Galaxy Tab 2 10.1 GT-P5113, or more generally for Android 4.2? I've seen a few scripts that look a bit dangerous. The closest I've gotten so far is the FolderMount app, but even on a rooted tab, this app only seems to have access to the `/storage/emulated/0/` internal path, and all the apps I install are going into `/data/app/`.
deesto-xda said:
Is there a safe, proven method for moving apps out of internal storage and into an external SD on the Galaxy Tab 2 10.1 GT-P5113, or more generally for Android 4.2? I've seen a few scripts that look a bit dangerous. The closest I've gotten so far is the FolderMount app, but even on a rooted tab, this app only seems to have access to the `/storage/emulated/0/` internal path, and all the apps I install are going into `/data/app/`.
Click to expand...
Click to collapse
You can use FolderMount to access the root file system. I have /data/media/ bound with it as we speak.:laugh:
When you are on the screen to select the Source directory tap the menu button in the top right corner, select "/ Path" from the menu, and say OK to the warning. You should be able to select any folder on your device now.
Caldair said:
You can use FolderMount to access the root file system. I have /data/media/ bound with it as we speak.:laugh:
When you are on the screen to select the Source directory tap the menu button in the top right corner, select "/ Path" from the menu, and say OK to the warning. You should be able to select any folder on your device now.
Click to expand...
Click to collapse
Doh! Thanks! Yep, that works! But then I got the prompt: "source isn't empty. want me to move the contents?" (paraphrase), I answered "yes", and ended with "Unfortunately, FolderMount has stopped." Does the dir have to be empty before you can do this? Or do you have to move apps one at a time, with a unique mount pair for each? I was trying to "move" /data/app/ dir itself to SD; maybe that's a bad idea.
deesto-xda said:
Doh! Thanks! Yep, that works! But then I got the prompt: "source isn't empty. want me to move the contents?" (paraphrase), I answered "yes", and ended with "Unfortunately, FolderMount has stopped." Does the dir have to be empty before you can do this? Or do you have to move apps one at a time, with a unique mount pair for each? I was trying to "move" /data/app/ dir itself to SD; maybe that's a bad idea.
Click to expand...
Click to collapse
Oh yeah! Sorry I should have said I moved everything to the destination manually, then i mounted the folder in FolderMount and do not let it move anything for you! Though to be completely honest I don't think I would recommend mounting /data/app/. I don't think foldermount mounts the directory early enough at boot for that to work. Many of the large files that applications use are stored on the emulated sd card, in /sdcard/Android/data/ & .../obb/. Moving these will free up a lot of space probably. But like I have, mounting /data/media/ will let you move all of the contents of what used to be your "real" internal sd to some folder on your external sd. Android settings/storage sees me with INTERNAL STORAGE:Total Space: 4.59GB, Available: 3.68GB, Apps (app data & media content): 4.19GB, Music,Downloads,Pictures,etc.:~12GB! In system tuner my internal storage, /storage/emulated/0/ shows 23GB used, 36GB free with my 64GB card.
After moving everything that was in /data/media/ to my external it is easy to format my internal sd partition in recovery to clear away the now redundant files, and free up that space for the rest of my data.
After trying just another rom (revolt) my internal memory relocated to path /mnt/shell/emulated/0 (previously it was in path /mnt/sdcar). This thing make me sick, is this way how i can return back path to my internal memory ?
oh, 2admins: can you rename post to "returning back path to internal memory"
All 4.2 roms will do that.(has something to do with multi user support added in 4.2) Your only option is to copy everything back to the original location.
Using on CM11, should work for any android build above 4.#.#
If you are having trouble mounting folders like I did like SuperMount, FolderMount didn't work for me
Even if they work, they require payment for most important features
Get BusyBox (Most custom ROMs already have it, like CM)
I used busybox mount because regular mount didn't work
Get the SManager app
Move the contents of obb folder to somewhere in external SD, (Or you can move the entire obb folder and create an empty obb folder in sdcard/Android)
Create new script from SManager (or any other text editor and save it with .sh extension) and type the mount command in it
Lets say I moved the folders inside obb to storage/sdcard1/obbfolders, then command is:
busybox mount -o bind /storage/sdcard1/obbfolders/ storage/sdcard0/Android/obb
Save the file (in SManager you press back after typing and it asks if you want to save)
Click on the file you created and check the Su and Boot boxes and Save
Script should be good to go, click Run
I use FX File Explorer to verify it (obbfolders should be shown on the main page)
Reason I created this thread, I searched this for a quite good amount of time and couldn't find anything
All "mount folder android", "mount bind android" searches either come up dead or show me an app that doesn't work for me
needo2 said:
Using on CM11, should work for any android build above 4.#.#
If you are having trouble mounting folders like I did like SuperMount, FolderMount didn't work for me
Even if they work, they require payment for most important features
Get BusyBox (Most custom ROMs already have it, like CM)
I used busybox mount because regular mount didn't work
Get the SManager app
Move the contents of obb folder to somewhere in external SD, (Or you can move the entire obb folder and create an empty obb folder in sdcard/Android)
Create new script from SManager (or any other text editor and save it with .sh extension) and type the mount command in it
Lets say I moved the folders inside obb to storage/sdcard1/obbfolders, then command is:
busybox mount -o bind /storage/sdcard1/obbfolders/ storage/sdcard0/Android/obb
Save the file (in SManager you press back after typing and it asks if you want to save)
Click on the file you created and check the Su and Boot boxes and Save
Script should be good to go, click Run
I use FX File Explorer to verify it (obbfolders should be shown on the main page)
Reason I created this thread, I searched this for a quite good amount of time and couldn't find anything
All "mount folder android", "mount bind android" searches either come up dead or show me an app that doesn't work for me
Click to expand...
Click to collapse
Trying to follow your guide....can't get it to work ?
1: Moved the entire OBB folder to my SD
2: Installed busybox, started it, software says it is installed, there's a button to install again....don't know what else it does ? If I click install, well, it installs again
3: Created the new script, saved it, ran it. It seems OK
4: When I open FX File explorer, I don't know what I'm looking for, I don't see anything going on, no operations running ?
...I didn't want to delete the original OBB directory since I don't have confirmation of this working ?
Thanks for your help
almost there...
Hi there
Had the same problem and found your thread after quite some surfing. Following your instructions, all seemed to work fine, just had to inject an "su" before the busybox mount command, then the whole external_sd (/storage/sdcard1/) was mounted to an existing (empty) folder on the internal sd (/storage/emulated/legacy/External_SD)... at least that's how it looks in SManager. When checking the target folder via file explorer, it still looks empty.
My setup:
- Samsung S4 mini on Cyanogenmod 10.2
- phone is not fully rooted, but root is granted to SManager and Busybox
- external sd card has permissions "d---rwxr-x" and is owned by "system" whereas the internal storage has permissions "drwxrwxr-x" and is owned by "root"
do I face a permission issue?
If yes, how to solve that (tried to change permissions of the External_SD folder recursively using chmod -R under root... but didn't suceed)
If not, any ideas...???
Thanks for any hint!
cheers
I'm using Lucky Patcher to bind oob folder, you should try.
@needo2: Is it required to mount the folder? This could cause problems on rejecting sd card. Maybe it does work replaceing the source directory with a simple link ("ln -s") to sd?