I have seen this mentioned but no solution. (It's been causing mild headaches for lots of things from storing camera pics to flashing ROMs)
Is there a way to get the Transformer to use the SDCARD as the actual default storage point?
It's a severe pain that everything defaults to the internal storage that it thinks is external then I have to move everything to the external SDCARD after that.
It would be a moot point but I have a 32GB SDCARD that sits empty while my internal storage fills up. I store a lot of music and movie files for editorial, etc and the Transformer is great for that. . .except for the dumb mount points of the sdcard.
You could make a soft link in /sdcard/ that points to /Removable/MicroSD/ but your sdcard has to be formatted NTFS to support it. I would assume the mount points for removable media are located in /etc/fstab
This drives me a tad crazy as well. That and the naming convention. Should be under /media/ or /mnt/ but "/Removable/MicroSD/" is a ginormous pain when you're using to unix/linux media mounting conventions or navigating under the shells
Oh well.
Sent from my Transformer TF101 using XDA Premium App
This was done for other devices such as the Notion Ink Adam so I know it's possible.
sent from a device using an app
uncorq said:
This drives me a tad crazy as well. That and the naming convention. Should be under /media/ or /mnt/ but "/Removable/MicroSD/" is a ginormous pain when you're using to unix/linux media mounting conventions or navigating under the shells
Oh well.
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
I'll agree with that, but its something I can over look. I'm assuming you would has to change this line in /etc/vold.fstab
Code:
dev_mount microsd /Removable/MicroSD auto /devices/platform/sdhci-tegra.2/mmc_host/mmc1
just have to get the docks sdcard to mount into the devices internal memory "sdcard" in the same manner the microsd does, should be fairly easy to do, just have to poke around a bit to see how microsd is being mounted
I try link 2 sd and data root 2 sd on the market, but the apps would not recognize the microsd. So there no way of linking to the sd by apps.
Sent from my Transformer TF101 using Tapatalk
I try link 2 sd and data root 2 sd on the market, but the apps would not recognize the microsd. So there no way of linking to the sd by apps.
Click to expand...
Click to collapse
Exactly. I would consider this a fairly obvious flaw to Asus that they change the accepted behavior being used everywhere else. Overall happy with the device but this is causing a headache since it's the only android device I have that operates this way it's not something I can just "get used to" as the odd man out. Why include external storage (a major reason for this over the Galaxy Tab 10.1 for me) and then make it a pain to use?
I'm assuming you would has to change this line in /etc/vold.fstab
Click to expand...
Click to collapse
Will see if that helps but wondering if this would cause a conflict elsewhere.
I'm making this too complicated in my head.
Simply: The internal and external mount points should be swapped.
Anything I want on the internal storage I can move, but that's fewer and further between than the sdcard. Maybe some music or whatnot.
This would solve other problems like ROM managements, etc.
one more thing... if it's just photos you are wanting to move, you could
"ln -s /sdcard/DCIM /Removable/SD/DCIM"
all new photos taken will end up on SD I might have that backwards? type ln in terminal with no arguments, and it will tell you what you need
do this for any folders you want on SD, then androids core stuff that apps need, and you don't need elsewhere still stays internal
I get "operation not permitted" for some reason. I have root permissions. Sudo, etc.
bitter1 said:
I get "operation not permitted" for some reason. I have root permissions. Sudo, etc.
Click to expand...
Click to collapse
FAT32 doesn't support symlinks.
Try this instead.
Regards,
Dave
Oh yeah, duh. Will give the other a shot.
I have to stick to FAT32 because I occasionally have to use OSX to shuffle things around.
dan-htc-touch said:
one more thing... if it's just photos you are wanting to move, you could "ln -s /sdcard/DCIM /Removable/SD/DCIM"
Click to expand...
Click to collapse
You also need to be root or prefix that with sudo
foxmeister said:
FAT32 doesn't support symlinks.
Try this instead.
Regards,
Dave
Click to expand...
Click to collapse
cd /mnt/sdcard
mkdir fssd
mount -o bind /Removable/SD /mnt/sdcard/fssd
yeap that works.. Thanks..
If your running Prime (Or something that supports init.d scripts), you could add that command to one of the files in /system/etc/init.d/ to make it automatically run at boot
Tortel1210 said:
If your running Prime (Or something that supports init.d scripts), you could add that command to one of the files in /system/etc/init.d/ to make it automatically run at boot
Click to expand...
Click to collapse
I just did that to 07 and no joy
After reboot no effect. I'll play some more later.
which command did you add? you only need to add the last one.
brando56894 said:
which command did you add? you only need to add the last one.
Click to expand...
Click to collapse
sure. only that one.
maybe the MicroSD (yeah changed it) is not mounted yet when the script runs?! or does the script run at all?!
off to bed now. tomorrow is another hot day.
I think you need to prefix it with /system/xbin. Heres the command I used in my init scripts:
Code:
/system/xbin/mount -o bind /Removable/MicroSD/DCIM/ /sdcard/DCIM/
That code will make pictures save on the micro sd card instead of internal memory.
Also, make sure the folder in the internal memory where you want it to bind to the external storage is empty.
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 apparently I have to use my computer or root explorer to write to my SD card since the 3.2 update. Does anyone know how this might be fixed to allow general file managers or applications to take advantage of?
same here....
f'ing moto fail here....this is NOT sd support to me
i have been using file manager HD and it will copy files to & from the sd card and delete from the sd card. it just wont "move" to the sd card.
EDIT- was using root explorer...not the other one.
Did you do anything special since upgrading to #Version three point two? I use the same program and it won't move, copy, or delete.
jase33 said:
i have been using file manager HD and it will copy files to & from the sd card and delete from the sd card. it just wont "move" to the sd card.
Click to expand...
Click to collapse
I can copy from the SD card but not paste to using the same software...this mean its read only
To be clear, I updated using update.zip and now running tiamat kernel, but I'm sure it was read only before I flashed the new kernel
I updated to 3.2 with ota and manually rooted. using stock kernel. write to sd works fine. maybe the method you updated from or the kernel you use is causing an issue.
sdcard
heh i find it amusing:
Real SDCard = /mnt/external1
Same ole crap SDCard = /mnt/sdcard, /sdcard, /data/media, and i bet more if i care to look harder.
jase33 said:
I updated to 3.2 with ota and manually rooted. using stock kernel. write to sd works fine. maybe the method you updated from or the kernel you use is causing an issue.
Click to expand...
Click to collapse
Are u talking about the Sdcard folder or the external1 folder?
I updated via update.zip method
Edit: Attached screenshot of my external1 permission
jase33 said:
i have been using file manager HD and it will copy files to & from the sd card and delete from the sd card. it just wont "move" to the sd card.
Click to expand...
Click to collapse
Moving from one source to another isn't possible. It's a linux/android thing. So that's nothing to worry about.
Remount /mnt/external1 as read/write
Here's what I've done to make /mnt/external1 read/write accessible:
adb shell or any other terminal emulator to get to a shell on the xoom
su to get to the # prompt
umount /mnt/external1
mount -t vfat -o fmask=0000,dmask=0000,rw /dev/block/platform/sdhci-tegra.2/mmcblk0p1 /mnt/external1
That remounts the sdcard without using vold, which is enforcing a mask on the perms.
Now to get this to happen at boot...
Stealyourface said:
Moving from one source to another isn't possible. It's a linux/android thing. So that's nothing to worry about.
Click to expand...
Click to collapse
Yeah I know.....I was just responding simply
Sent from my HD2
Stealyourface said:
Moving from one source to another isn't possible. It's a linux/android thing. So that's nothing to worry about.
Click to expand...
Click to collapse
I move files all the time in Linux, via both command line and file manager. I don't know where you are getting this "Linux/Android can't move files" from.
Given up and revert back to Tiamat 1.1
I reflashed stock and upgraded to 3.1 then 3.2 only to learn that the SD card was not writable within the xoom. I have full confidence that one of the devs will release a mod for 3.2 to get us all the features that we are accustomed to. Until then I've flashed back to Tiamat 1.1.
ekarelis said:
Here's what I've done to make /mnt/external1 read/write accessible:
adb shell or any other terminal emulator to get to a shell on the xoom
su to get to the # prompt
umount /mnt/external1
mount -t vfat -o fmask=0000,dmask=0000,rw /dev/block/platform/sdhci-tegra.2/mmcblk0p1 /mnt/external1
That remounts the sdcard without using vold, which is enforcing a mask on the perms.
Now to get this to happen at boot...
Click to expand...
Click to collapse
This is exactly right. It appears vold is now placing special perms above standard media_rw perms. So, apps without this level of permission can not write to external storage. We will address this in the upcoming Tiamat Rom release.
looking forward to 3.2 cusrom rom
Thanks brd. Very much looking forward to the tiamat 3.2 based rom.
mambomta said:
I move files all the time in Linux, via both command line and file manager. I don't know where you are getting this "Linux/Android can't move files" from.
Click to expand...
Click to collapse
Move a file from your xoom (if you even have one) from internal storage to external. It either won't let you, or it'll get corrupted in the process.
Stealyourface said:
Move a file from your xoom (if you even have one) from internal storage to external. It either won't let you, or it'll get corrupted in the process.
Click to expand...
Click to collapse
My Xoom should arrive tomorrow. If the Xoom is not allowing a move, it is a bug, not a limitation in Linux.
Hi.
As so many apps still don't support card locations other than /mnt/sdcard, I manually run as root the following to mount /Removable/MicroSD off /mnt/sdcard
mount -o bind /Removable/MicroSD /mnt/sdcard/MicroSD
This works great. Non /Removable aware apps then pick up files on the Transformers sdcard slot.
However, I'd like to automate this. Anyone know how I would do this? I guess a tweak to the android equivalent fstab file?
Thanks!
I have been looking for a solution for this, and found an older thread here on XDA with several methods.
I used root explorer to modify the mount point in /etc/vold.fstab
Just change the mount point from /Removable/MicroSD to /mnt/sdcard/MicroSD and reboot.
This seems to work great so far, but I have only been using this for a couple of hours. Don't forsee any problems though.
Sent from my Transformer TF101 using Tapatalk
kbrabble said:
I have been looking for a solution for this, and found an older thread here on XDA with several methods.
I used root explorer to modify the mount point in /etc/vold.fstab
Just change the mount point from /Removable/MicroSD to /mnt/sdcard/MicroSD and reboot.
This seems to work great so far, but I have only been using this for a couple of hours. Don't forsee any problems though.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Thanks for that. I'll give it a go!
Hmm, this seems to cause a force close when you eject the card. It then also fails to mount the first 2-3 times when you plug the card back in.
I guess some Asus service is relying on the card being at /Removable
There must be a way to autorun a mount -bind somehow?
Have you also tried hooking up to your computer, as I know on some devices changing the mount points to nested like that would screw up the process for mounting to the computer properly.
I haven't experienced any force closes, or any problems mounting the card when reinstalled. As far as mounting on the computer, I have not tried. I agree that a -bind would be the best way, but haven't found a way to do this at boot yet.
Sent from my Transformer TF101 using Tapatalk
Is there a way I can make the MicroSD just an extension of the internal storage? It would be nice to store apps on it as well. Is this possible?
Apps2SD lets you put apps on, and ICS lets you use it pretty much the same way as the internal. So no need really.
If you really wanted to it would involve symlinking partitions, but I'm not entirely sure as to the process
Oh that's great because I remember honeycomb didn't allow that. When an app is on sd will its files reside on sd? For example DoggCatcher stores its files on internal and I would really like to have those files on my MicroSD. Would a symbolic link work to do this?
Edit: tried app2sd but it couldn't find SD card because of how TF names internal as SD.
Trying out Link2SD because it seems promising. I think it creates symbolic links.
Not symbolic links
Symlinking, the ls command, think of it as a linux-shortcut command perse.
I find that Titanium backup works very well, but it needs root.
How do you do it in Titanium? I can't figure out how. Thanks for the help so far
Edit: Also if for example Doggcatcher's files are on internal and it won't let me specify where I want to store them how would I move them to MicroSD?
Really sorry, I was getting TI backup mixed with something else.. X.x
https://play.google.com/store/apps/...wOSwiY29tLndvbmd4bWluZy5hbmRyb2lkLmFwcDJzZCJd
Try this--
and this with root-- https://play.google.com/store/apps/details?id=com.leinardi.setinstalllocation&feature=also_installed (works well, my ROM has built in support for this though, most big apps (games) can be moved with the native ics feature. hunt through settings.
Thanks for the help! Is the TF internal filesystem Fat32 by default?
Thing O Doom said:
Not symbolic links
Symlinking, the ls command, think of it as a linux-shortcut command perse.
I find that Titanium backup works very well, but it needs root.
Click to expand...
Click to collapse
No offense intended, but I'm not sure I understand what you are saying. Symlink is just a short name for a symbolic link, as far as I could find (from Wikipedia):
In computing, a symbolic link (also symlink or soft link) is a special type of file that contains a reference to another file or directory in the form of an absolute or relative path and that affects pathname resolution.
Click to expand...
Click to collapse
And the "ls" command (without any other parameters) just lists the files in the current directory in Linux and Unix type OSs.
---------- Post added at 12:52 AM ---------- Previous post was at 12:50 AM ----------
taC nayN said:
Thanks for the help! Is the TF internal filesystem Fat32 by default?
Click to expand...
Click to collapse
The internal is ext4, I believe, a Linux filesystem type.
I'm trying this to create soft link so I can have DoggCatcher files on MicroSD instead of Internal but when I tried
ln -sf /removable/MicroSD/DoggCatcher /sdcard/Doggcatcher
it says No such file or directory. What am I doing wrong? My MicroSD is exFAT.
Sorry, I'm getting so mixed up today. *blarg* Thank you for pointing that out. Id even know what I was thinking. -sleep time-
myandroiid.blogspot.com/p/how-to-use-your-sdcard-as-internal.html
HERE IS COMPLETE GUIDE ITS AWESOME
Sent from my HTC Salsa C510e using xda premium
taC nayN said:
I'm trying this to create soft link so I can have DoggCatcher files on MicroSD instead of Internal but when I tried
ln -sf /removable/MicroSD/DoggCatcher /sdcard/Doggcatcher
it says No such file or directory. What am I doing wrong? My MicroSD is exFAT.
Click to expand...
Click to collapse
If it is the same as mine, then it should be "ln -sf /Removable/MicroSD/DoggCatcher /sdcard/DoggCatcher". Note the capital R in removable. Now, if DoggCatcher is a directory name then you may need to add a "/" at the end of one or both of your target and source. Not sure if the 'f' option works with busybox, you may need just 'ln -s'. Also, the normal command structure is " ln -s(f) source-file link-name ". Make sure you have the parts in the intended order.
Allright I got everything *mostly* figured out now. I don't necessarily want to make MicroSD primary because they are the same size so I just want to extend it. I figured out how to move DoggCatcher via the app (I'm an idiot)
I still would like to know how to create soft links between SD and internal though because it keeps failing.
sidneyk said:
If it is the same as mine, then it should be "ln -sf /Removable/MicroSD/DoggCatcher /sdcard/DoggCatcher". Note the capital R in removable. Now, if DoggCatcher is a directory name then you may need to add a "/" at the end of one or both of your target and source. Not sure if the 'f' option works with busybox, you may need just 'ln -s'. Also, the normal command structure is " ln -s(f) source-file link-name ". Make sure you have the parts in the intended order.
Click to expand...
Click to collapse
Thank you so much! That was the problem. Greatly appreciated.
I just installed a new ROM and the SDCARD and SDCard-ext are in the wrong location. They are listed under the root director ( / ) and /storage instead of under /mnt/sdcard
Does it work? You could create a symlink. If that fixed it, put it in a script on bootup.
post-mortem said:
Does it work? You could create a symlink. If that fixed it, put it in a script on bootup.
Click to expand...
Click to collapse
Does it work is a relative question. (wasn't meant to sound wise-a$$). I can access them, but apps do not see them at all. They are looking for the cards in /mnt therefor not finding them.
I changed them in /system/etc/vold.fstab but now it won't boot. The not booting is not an issue, I can fix that, but I don't know how to fix these incorrect paths/
No one else who's using this ROM is having these problems? I say either reflash, create symlinks, or choose another ROM.
post-mortem said:
No one else who's using this ROM is having these problems? I say either reflash, create symlinks, or choose another ROM.
Click to expand...
Click to collapse
Not sure if anyone else is running it. Haven't been able to find a thread on here for it. How do you do symlinks?
mikemikemikexxx said:
Not sure if anyone else is running it. Haven't been able to find a thread on here for it. How do you do symlinks?
Click to expand...
Click to collapse
ln -s target shortcut
See a bit more here.
Make a script in your /system/etc/init.d directory, so these links will be created on every boot.
post-mortem said:
ln -s target shortcut
See a bit more here.
Make a script in your /system/etc/init.d directory, so these links will be created on every boot.
Click to expand...
Click to collapse
From what I have read you cannot use them on FAT.
Why does editing this file not work? I fail to see how Android could do anything other than read the file, provided permissions are the same.
mikemikemikexxx said:
From what I have read you cannot use them on FAT.
Why does editing this file not work? I fail to see how Android could do anything other than read the file, provided permissions are the same.
Click to expand...
Click to collapse
The internal memory is not FAT; typically, only the 1st partition on the SD card is FAT, everything else should be EXT. So, executing ln -s /storage /sd-ext should work (or wherever it's currently being mounted).
post-mortem said:
The internal memory is not FAT; typically, only the 1st partition on the SD card is FAT, everything else should be EXT. So, executing ln -s /storage /sd-ext should work (or wherever it's currently being mounted).
Click to expand...
Click to collapse
I meant the card but ln is not working.
One more thing I am going to try is an ADB pull and push. If that doesn't work I really need some community support.
bump to the front.
Are my questions that complex or that dumb that I get so few replays? /bump
Sent from my XT875 using xda app-developers app
Is there a good reason that you don't want to use another ROM?
Mainly speed and compatibility. I need the offline commands only available in JB. Stock ROM is dead slow and is only ICS. Other custom ROMs were also on the slow side and/or battery hogs.
Sent from my XT875 using xda app-developers app
So, is this right?
FAT partition is currently being mounted as /storage
EXT partition is currently being mounted as /mnt/sdcard
post-mortem said:
So, is this right?
FAT partition is currently being mounted as /storage
EXT partition is currently being mounted as /mnt/sdcard
Click to expand...
Click to collapse
Well the way my phone is laid out is
System (I assume too large so they split it in two which resulted in the below SD-Card)
SD-Card
SD-Card EXT (The actual SD Card) - FAT32
I assume the System and SD-Card are standard Android partition format.
Do you use a file manager on the phone, such as ES File Explorer? Are you familiar with using adb?
Edit: Basically, I'm trying to figure out the exact path of the mounted partitions, and where they're supposed to be mounted.
post-mortem said:
Do you use a file manager on the phone, such as ES File Explorer? Are you familiar with using adb?
Edit: Basically, I'm trying to figure out the exact path of the mounted partitions, and where they're supposed to be mounted.
Click to expand...
Click to collapse
They are 100% supposed to be mounted under: /mnt/sdcard and /mnt/sdcard-ext
Right now they are mounting to: /storage/sdcard and /storage/sdcard-ext
There is also an entry in under root ( /sdcard and /sdcard-ext --- For these two I am booting into stock ROM to see if they are suppose to be directly in root as well, will post up when I know)
Check the scripts in your init.d to see if one of them is mounting the sd partitions under /storage.
I suppose you could also try booting without the sd card in place, and see if those /storage directories still exist. Not sure how much that will tell you, though.
post-mortem said:
Check the scripts in your init.d to see if one of them is mounting the sd partitions under /storage.
I suppose you could also try booting without the sd card in place, and see if those /storage directories still exist. Not sure how much that will tell you, though.
Click to expand...
Click to collapse
The init.d for sure says to load sdcards to /storage . (on this particular ROM only)
I will try without the sdcard as you suggested and let you know. Battery died on me, phone won't boot even when plugged in until at least 10%.
Which script is mounting the sd card to /storage? Is it part of the ROM, or is it something which the dev included in this ROM? I ask in case the ROM expects the sd card to be mounted there.
Regardless, try changing the script to link to /sdcard.