Related
This patch allows mounting of NTFS volumes through vold (i.e the disk is automatically mounted when pluged into the device).
Mountpoint is:
/mnt/sdcard/usb<disk-number>-disk0
Known issues:
- NTFS volumes are mounted read-only, this has been explicitly added to the vold to prevent data loss or filesystem corruption until we know that the patch is stable.
Tested on FolioMod v1.3c
Installation:
copy zip file to your sdcard, rename to update.zip and flash using recovery.
vold-update-0.2.zip - this is the patch for vold containing ntfs support
vold-rollback.zip - rollback to default FolioMod 1.3 vold
source-0.2.zip - source code for updated vold
v0.1
- Initial release
- Ntfs support, multiple disks working
v0.1.1
- make sure that the mount point directory exists, create if necessary
v0.2
- multiple partitions are working
- fixed asec handling as discussed
- mount point directories are removed, when unmounting disk (if empty)
I know vold also handles sdcard + multiple usb stick is that part still included?
and the strange vold.fstab with wildcards? otherwise it will be hard to use for a toshiba rom, i think.
Yes this should all be still included, until now I had no issues with my sdcard.
What the patch does is try to mount everythin with FAT like before, if that fails, it tries NTFS.
The vold.fstab is still included, only change is what partitions should be mounted, this was 'all' before and has been changed to 'auto' (as the 'all' seems to be a toshiba addition)
Still need to figure out how to use this, hope to get a new disk on Monday, so I can test that.
weeds2000 said:
The vold.fstab is still included, only change is what partitions should be mounted, this was 'all' before and has been changed to 'auto' (as the 'all' seems to be a toshiba addition)
Click to expand...
Click to collapse
Could that also help recognizing some strange formatted SD cards? E.g. I have a digicam (Panasonic) that modifies the FAT32 somehow that the folio tells me the card is defective (but still works perfectly fine in Windows or the Digicam)?
I doubt it, as nothing has changed for sdcard.
But as this vold is compiled with additional debug output you may as well trry to use it. Maybe the output will give some more information on what is going wrong.
But I guess this is because your cam actually uses the "secure" part in your Secure Digital Memory Card. See http://en.wikipedia.org/wiki/Secure_Digital#DRM_features for more info on that.
Very interesting! Thank you !!
Tested with FolioTNT 4.0a and 2 usb sticks (16 and 8 gigs) and working perfectly on both
Great job
Is write supported already or is only for read?
Can large files be read?!?! (i mean no laggy?)
Thanks
Great job, thank you very much Mr. Weeds!
OK partition support is somehow working now, but not really a solution I like to release.
Looks like vold was not intended to handle that.
The main reason for this post is, that the handling of /mnt/asec and /mnt/asec_secure is somewhat bad (again vold was not intended to even handle multiple external storage devices at the same time)
Just to make sure anyone know what that is: Apps2SD stores the packages in that folder.
At the moment vold will create (and mount) an asec container for every storage device attached to the folio. So if I insall an app (or move it manually) with SDCard inserted it will use the asec dir of the SDCard. If I install an app without SDCard it will use the asset directory of the internal storage.
The problem is it seems I cannot change on the fly between those two directories. If I unmount SDCard /mnt/asec does not contain the package if put there. So I need to take out the SDCard and reboot the device.
Fixing this behaviour would be quite simple. The question rather is where to put it?
Internal storage or SDCard?
The same question goes for what should be the default SDCard (i.e. the one mounted under /sdcard, the one where apps download their resources). Internal Storage or external SDCard.
The one thing I can think of is creating a selection setting within the settings app where I can select which device should be mounted as primary SDCard.
If that is switched the systrem may copy contens from asec to the new device.
So the layout of /mnt may look like that
/mnt/sdcard (linked to /sdcard) - the primary sdcard device as selected by the user (defaults to internal storage)
/mnt/sdcard2 - well, the other one (either internal or sdcard depending on what the first device is)
/mnt/usb-storage/usb<disk-number>-disk<partition-number> - hdd's mounted over USB
Just waiting for anyone to come up wither other/better ideas...
weeds2000 said:
Fixing this behaviour would be quite simple. The question rather is where to put it?
Internal storage or SDCard?
The same question goes for what should be the default SDCard (i.e. the one mounted under /sdcard, the one where apps download their resources). Internal Storage or external SDCard.
Just waiting for anyone to come up wither other/better ideas...
Click to expand...
Click to collapse
proper behaviour would be internal storage for apps.. as its not nice that the apps you install disappear if you remove the sdcard or usbsticks.
i noticed this problem early on..but no one mentioned it as a problem.
do you see why the .android_secure mountpoint does not happen?
i think somehow this relate to the problem of downloading paid apps.
If this is OK for everyone, then this would be a much simpler approach, so /sdcard and /mnt/sdcard always point to internal storage.
If someone needs more storage (i.e. for downloaded resources) we may simply create a tool wich does some linking (e.g. link /sdcard/gameloft to /sdcard2/gameloft)
The mount point for asec_secure exists as well, 2 times with the same issues as asec. I don't know if this is related to paid apps. According to the logs I get a 403 response from the google servers.
Is there any specific reason, why SDCard is put under /sdcard/sdvcard-disk0?
I'd like to move that to /mnt/sdcard where usb-storage will go as well.
Using that approach it might be unessesary to unmount the external storage when a USB-connection is made.
weeds2000 said:
Is there any specific reason, why SDCard is put under /sdcard/sdvcard-disk0?
I'd like to move that to /mnt/sdcard where usb-storage will go as well.
Using that approach it might be unessesary to unmount the external storage when a USB-connection is made.
Click to expand...
Click to collapse
normally its a good reason.. the Toshiba filemanager looks at a location where all users got access..
no regular user would look into a /mnt/sdcard2 unless the toshiba pointed to the location.
so /mnt/sdcard offers both internal storage + sdcard + usbstick here which i think works well and all users easily find it as its within the sdcard default location.
i dont think that logic should change..
updated to 0.2 write support is still disabled.
As I always used NTFS-3G I cannot tell if the driver implementation is reliable and complete. However I think it is, as my knowledge from incomplete write support is 3 or 4 years old...
From weeds2000:
"This patch allows mounting of NTFS volumes through vold (i.e the disk is automatically mounted when pluged into the device)...."
------------------
This patch was tested by me on FolioMod v1.3c.
It readed well one HD NTFS, and recognized all of SD cards that were not recognized before.
Many thanks.
weeds2000 said:
updated to 0.2 write support is still disabled.
As I always used NTFS-3G I cannot tell if the driver implementation is reliable and complete. However I think it is, as my knowledge from incomplete write support is 3 or 4 years old...
Click to expand...
Click to collapse
do you consider this ok to be included in a new update?
I of course let you approve if its ok for regular use..
denver-tempor said:
From weeds2000:
"This patch allows mounting of NTFS volumes through vold (i.e the disk is automatically mounted when pluged into the device)...."
------------------
This patch was tested by me on FolioMod v1.3c.
It readed well one HD NTFS, and recognized all of SD cards that were not recognized before.
Many thanks.
Click to expand...
Click to collapse
You have NTFS formatted SD Cards? Or FAT cards which weren't recognized before?
Nemo0815 said:
You have NTFS formatted SD Cards? Or FAT cards which weren't recognized before?
Click to expand...
Click to collapse
I have some SD cards (several trades and capacities) FAT formatted that weren't recognised before applying this patch. Now, they are.
Also, I tested a 2.5 USB HD, NTFS, and it was readed without problems.
weeds2000 said:
As I always used NTFS-3G I cannot tell if the driver implementation is reliable and complete. However I think it is, as my knowledge from incomplete write support is 3 or 4 years old...
Click to expand...
Click to collapse
OK, so I was wrong, this is from the kernel documentation on NTFS Write support.
This enables the partial, but safe, write support in the NTFS driver.
The only supported operation is overwriting existing files, without
changing the file length. No file or directory creation, deletion or
renaming is possible. Note only non-resident files can be written to
so you may find that some very small files (<500 bytes or so) cannot
be written to.
While we cannot guarantee that it will not damage any data, we have
so far not received a single report where the driver would have
damaged someones data so we assume it is perfectly safe to use.
Click to expand...
Click to collapse
So it looks like ntfs-3g is the way to go, this will take some time however.
@dexter
I played around with various disks today, watched a movie, etc... Seems like everything is OK, so I would consider 0.2 be a candidate for regular use.
I will include this in the next update..
You seem to have many downloads, but not really any complaints
that should tell us something.
Or more to the point, does anyone think they will fix the way the TF memory/partitions are based with the ICS "AiO" Android 4 revision?
While its not an operational annoyance for me (IE most everything works fine), I HATE the fact that the internal memory is mounted as the sdcard instead of as internal memory (like any other device I have used)
I hate that out of 16GB I only have 11.xGB to use (especially when my ROM size before install is only 180Mb extracted... Stock is like 400Mb+) and cant use something like Firerats (at least not that I have found with searching, and yes I know firerats is basically just a repartition tool for MTD not eMMC or anything else) to repartition it to reclaim the wasted space...
From what I understood (and i could be wrong here), its only setup with the Internal memory as an SD instead of... internal memory... is because of Honeycomb, and that the layout is similar to other devices in that its a single memory chip for the internal/system/sd like any other NON Honeycomb device only the internal memory is... well internal memory...
So my question is that can anyone in the know on this subject help me out here...
AFAIK we get one chip for storage. Most stuff expects /sdcard so it makes sense for HC/ICS to be putting our /data/media on /mnt/sdcard with the FUSE thing.
And I can't see any really good reason to change what the norm is on TF101.
Sent from my Transformer TF101 using Tapatalk
I think you'll find that on Froyo/Gingerbread phones with internal memory as well as an SD slot, internal memory has always been mounted as /sdcard/ or /mnt/sdcard/ - the external card is mounted as a subfolder under that. This is for the user's convenience. Can you imagine how it would work to mount the internal memory if there was no external card present otherwise?
I seriously doubt ICS itself will solve the niggling problem of external SD mounting on our TF101s, but Asus may well change the layout so it's under /sdcard/xxxx/ to help matters.
Spidey01 said:
AFAIK we get one chip for storage. Most stuff expects /sdcard so it makes sense for HC/ICS to be putting our /data/media on /mnt/sdcard with the FUSE thing.
And I can't see any really good reason to change what the norm is on TF101.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
I could understand ASUS placing the internal storage as /sdcard since most stuff does expect/save to /sdcard automatically. Being that the tablet has an advertised 16GB of memory, ASUS probably believed that your every day average Joe wouldn't go out and buy an sd card.
Sent from my DROIDX using XDA App
unfnknblvbl said:
I think you'll find that on Froyo/Gingerbread phones with internal memory as well as an SD slot, internal memory has always been mounted as /sdcard/ or /mnt/sdcard/ - the external card is mounted as a subfolder under that. This is for the user's convenience. Can you imagine how it would work to mount the internal memory if there was no external card present otherwise?
I seriously doubt ICS itself will solve the niggling problem of external SD mounting on our TF101s, but Asus may well change the layout so it's under /sdcard/xxxx/ to help matters.
Click to expand...
Click to collapse
I guess I was a bit vague, I dont actually want it as extra storage or partition, I just want it all as /data instead of /sdcard... all the phone I have and have used (which I admit arent the latest, the newest I have used was an 8GB phone I cant remember the model of) so far didnt actually use /sdcard they just used /data... I have an SD card specificly for being an SD card... I hate having to either remap or manually use a file manager to get my TB files or anything else that uses the fake /sdcard instead of my actual SD card... id prefer all /data bleh...
Hammerfest said:
I guess I was a bit vague, I dont actually want it as extra storage or partition, I just want it all as /data instead of /sdcard... all the phone I have and have used (which I admit arent the latest, the newest I have used was an 8GB phone I cant remember the model of) so far didnt actually use /sdcard they just used /data... I have an SD card specificly for being an SD card... I hate having to either remap or manually use a file manager to get my TB files or anything else that uses the fake /sdcard instead of my actual SD card... id prefer all /data bleh...
Click to expand...
Click to collapse
it IS all on /data. /sdcard or /mnt/sdcard is a FUSE mounted filesystem from /data/media. All space accessible on /sdcard is also accessible on /data.
EDIT:
All my android phones do not do what you claim either, the internal mem is mounted as /mnt/emmc and /data is a 2GB partition on the emmc
lilstevie said:
it IS all on /data. /sdcard or /mnt/sdcard is a FUSE mounted filesystem from /data/media. All space accessible on /sdcard is also accessible on /data.
EDIT:
All my android phones do not do what you claim either, the internal mem is mounted as /mnt/emmc and /data is a 2GB partition on the emmc
Click to expand...
Click to collapse
ok, lets put it this way, nothing is mounted under /sdcard when i look at my phones without my SD card in them... get me now? when I go to phone data I have 7~Gb free listed for apps and such, there is no SD card listed, I dont know how to put it any other way, there is NOTHING in the removable or sdcard directory (the removable doesnt even exist on my phones) until I put one of my MicroSD cards in...
ergo, data is a 2gb partition you say, cool! I want to eliminate the fake sdcard partition then and combine it all into /data! I want the programs that store data on to the /sdcard to ACTUALLY GO TO MY DAMN SDCARD...
what phone do you have that has 7GB of /data/ ?
Hammerfest said:
ok, lets put it this way, nothing is mounted under /sdcard when i look at my phones without my SD card in them... get me now? when I go to phone data I have 7~Gb free listed for apps and such, there is no SD card listed, I dont know how to put it any other way, there is NOTHING in the removable or sdcard directory (the removable doesnt even exist on my phones) until I put one of my MicroSD cards in...
ergo, data is a 2gb partition you say, cool! I want to eliminate the fake sdcard partition then and combine it all into /data! I want the programs that store data on to the /sdcard to ACTUALLY GO TO MY DAMN SDCARD...
Click to expand...
Click to collapse
I said my phones had a 2gb data partition. what I said about the transformer is:
lilstevie said:
it IS all on /data. /sdcard or /mnt/sdcard is a FUSE mounted filesystem from /data/media. All space accessible on /sdcard is also accessible on /data.
Click to expand...
Click to collapse
get it, /sdcard is DIRECTLY linked to /data/media, you lose no space what-so-ever to the /sdcard link.
further more show me a phone that has all the space in /data that is listed as having 16/32GB mem, it is pretty standard, my sgs was /mnt/sdcard, until I flashed CM7 when it was changed to /mnt/emmc, still not seen what you say where a device has all its space as /data
im not saying its not standard, im just saying (as is the original request on my post) that I dont want it mounted as SDCARD because I want my damn programs and sdcard data to do to... you guessed it, my ACTUAL SD CARD...
when I make backups with Titanium Backup, I want them to go to the MicoSD card I have inserted like they would with any other phone/device without having to **** with anything else, same with game/app extra data that uses SD card storage...
I played with an SGS2 today and while i didnt get to play with terminal, I ran TB and the backup went to the MicroSD card inserted and not the internal memory... unlike what the TF does...
infazzdar said:
I could understand ASUS placing the internal storage as /sdcard since most stuff does expect/save to /sdcard automatically. Being that the tablet has an advertised 16GB of memory, ASUS probably believed that your every day average Joe wouldn't go out and buy an sd card.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
And that buy now after years of PC's with X GB hard drives that they would be used to losing some to the OS and recovery partiton. Especially since Windows and major Linux distro's have gotten excessively FAT.
Sent from my Transformer TF101 using Tapatalk
A lot of the newer tegra phones are set up this way.
Sent from my CushZero using Tapatalk
Hammerfest said:
im not saying its not standard, im just saying (as is the original request on my post) that I dont want it mounted as SDCARD because I want my damn programs and sdcard data to do to... you guessed it, my ACTUAL SD CARD...
when I make backups with Titanium Backup, I want them to go to the MicoSD card I have inserted like they would with any other phone/device without having to **** with anything else, same with game/app extra data that uses SD card storage...
I played with an SGS2 today and while i didnt get to play with terminal, I ran TB and the backup went to the MicroSD card inserted and not the internal memory... unlike what the TF does...
Click to expand...
Click to collapse
hate to break it to you but the SGS2 has a smaller /data partition, then the rest is mounted as /mnt/sdcard.
you do know that TiBU does allow you to select where you save your backup to right?
And for programs that don't (/mnt/sdcard/kindle for example), you can symlink the folder(s) they want to /Removable/MicroSD/(kindle) quite easily.
Sent from my Transformer TF101 using Tapatalk
I agree, its really annoying. A good example is dolphin browser. When I go to back up the settings and bookmarks "to SD" I have to hunt and peck in a file manager to find the stupid file and move it to my actual SD card. I am not at all a fan of the simulated SD card.
Superjoe said:
I agree, its really annoying. A good example is dolphin browser. When I go to back up the settings and bookmarks "to SD" I have to hunt and peck in a file manager to find the stupid file and move it to my actual SD card. I am not at all a fan of the simulated SD card.
Click to expand...
Click to collapse
yep, it annoys the everliving piss outta me, and while programs like TiB can "select" the location, and you can make "simlinks" for specific apps, I dont want to have to go through the hassle, I want to know that any program I use, when it requires the MicroSD, or normally saves to the MicroSD, to save to my &^*^&*%^%& MicroSD...
its as simple as that...
Guys, chill out, it's just a forum on the Internet.
Best alternative to dealing with the design: make a patch se or custom that screws with /init*.rc files accordingly. Main problem (give or take figuring out how to do it) would probably be how the system would react when no MicroSD card is mounted.
Sent from my Transformer TF101 using Tapatalk
lilstevie knows more about the partition structure of Android devices, and the Transformer in particular, than all of those in this thread put together. If you're not willing to take and/or accept that he has answered your questions multiple times and in multiple different ways, I can't help you and this thread is not going to go anywhere.
I am closing this thread.
I'm not a developer by any stretch of the imagination, but this Linux cell phone has ignited my inner geek, and I must bend it to my will.
My basic question is, with the current state of development, how much is it possible to move from the internal storage of an LG Optimus Fuel phone (L34C/KitKat) and onto the external SD card?
I blow stuff up a lot because I'm an inveterate tinkerer, too adventurous for my own good/skill level. I'm an Android noob, but an old hand at Linux, which means I think I know a lot more about what I'm doing with KitKat than I actually do. But at least I do have a fetish for backups, which is all that makes my misadventures endurable.
So I did a Nandroid backup on my L34C after modding it only enough to support the TWRP backup. But the phone's internal storage is puny, and TWRP manager will only write to the internal SD, so I could only install about 300MB more in apps before there no longer was enough space for another Nandroid backup. Which means I've either got to tone down my tweaking (figure the odds!) or find another way to do Nandroids.
Yes, I could do an initial Nandroid, followed by Titanium backups, but where's the fun in that? Same with doing online Nandroid backups. No self-respecting geek every would let someone else be in charge of maintaining his backups (IMHO). And bonus points if I can relieve internal SD overcrowding by installing/moving apps and whatnot to the external storage.
So I'm thinking this is going to require linking, but the OE FAT32 partition on the external SD card won't support it. The OE 4GB SD card was too small to be slicing up, so I bought a 16GB cat4 SD card, formatted half in FAT32 and half in Ext3, but I could never get the Ext3 partition to mount. I wasn't able to find anything definitive, but I did come across information (of unknown validity) that the L34C's lack of init.d support was the reason it wouldn't mount.
So is this true? If I install a kernel with init.d support in my L34C, will I then be able to mount additional partition(s) on the external SD card?
As for the specifics of the partitioning, I found one mention in another forum in a post dated almost three years ago stating partitions on an Android external SD card had to be no more than 2GB in size, and preferably only 1GB. Is this true? Does it still pertain to KitKat? And what is/was the cause of this partition size limitation?
If the 2GB limit is true, what about creating and mounting multiple 2GB partitions? Say, one exclusively for writing the Nandroid backup to, and a second for moving files out of internal storage?
And what of my overall objective? In the current state of development, is writing Nandroid backups to the external SD card of an L34C (or even better, to the USB) known to be possible? Or im-possible?
If not, and presuming I can manage to get an Ext-formatted partition on the external SD card to mount, which of the many <something>2SD apps should I look to to move as much material as possible off of the internals storage?
I did try installing Link2SD, even though there wasn't an external partition available that supported linking. When I tried to move an app with it, one that Link2SD itself had labeled 'movable,' it failed with:
!Failure
App2SD is not supported by your device. Because your device has a primary external storage which is emulated from the internal storage. You can link the app in order to move its files to the SD card.
Click to expand...
Click to collapse
Dunno why it's blaming Apps2SD unless Link2 is built around Apps2.
But the advice was no help because I can't link to a partition that won't mount. And for all I know, the fact that the L34C uses emulated storage might be a show-stopper.
I've asked these same questions at other Android forums, but got no answers. I initially didn't want to even join XDA because you guys are too far above my pay grade. But I don't think I have any other choice, not if I ever want to get to the bottom of this.
Thank you for taking the time to red my long-winded post.
Hi there,
What you may wish to do is transfer them to your pc for safe keeping and not have to worry about it. You could also try inserting your sd card into your PC and manually transferring the nandroids from your pc to your sd card afterwards.
Also regards to the sd card write protection issue, I could not find anything relevant for your device in particular but you can ask your question here and someone may be able to help you.
Good luck
I have recently got a Shield Tablet and I have attempted to add a 128GB to the internal storage but every time I go through the adoption process to bring it into internal, it formats it and results in it being corrupted? The sdcard is brand new.
Tablet is on Marshmallow.
HeroXx said:
I have recently got a Shield Tablet and I have attempted to add a 128GB to the internal storage but every time I go through the adoption process to bring it into internal, it formats it and results in it being corrupted? The sdcard is brand new.
Tablet is on Marshmallow.
Click to expand...
Click to collapse
I am having the same issue with the Shield tablet and a 128g sd card. I can use as portable, but trying to adopt as internal storage always returns the "damaged" partition after formatting and starting the moving process. I have tried formatting as ext4 in a PC first as recommended by others to no avail. If anyone is able to get this working please post your fix.
Found the below "Notes" on Nvidia's site. Looks like you'll have to format NTFS on your PC. Some PCs will not allow you that option out of the box, but you can easily change Windows' built-in formatter's options to allow it to format NTFS. The settings are somewhat hidden. To enable it, open up Device Manager and find your micro-SD card, go to the Properties -> Policies tab and then choose "Optimize for performance". Once you've done this, you'll see the NTFS option in the format dialog. Just make sure you "Eject" the card properly, as it seems it's more easily corrupted if not ejected properly.
NOTES:
The ability to move data to SD card is variable for select*apps*and games. Onlyapps*that developers have opted in as moveable to external storage can be moved.
The SHIELD tablet K1 only supports writing to FAT32 and NTFS formatted cards.
64*GB*(or higher) microSD cards – Android does not support the exFAT file system out-of-the-box. Because the standard FAT32 file system does NOT support partitions greater than 32*GB*by default, 64*GB*cards come pre-formatted as exFAT. If you want to use a 64*GB*microSD with the SHIELD tablet K1, it has to be converted to a file system format that is supported by stock Android, which in this case is NTFS. This can be done using a PC.
Android KitKat significantly changes the way applications are allowed to use SD cards. If you use SD Card to store data, please read here for further details."
Hey, I have a similar problem but wanted some opinions.
Received my new K1 and updated to MM and everything is cool. Installed PNY 64GB (10 class) and chose the integrated storage option. The K1 sees the storage and I'm able to move apps to it. My problem is that new apps cannot download due to no storage. The message "whatever app cannot be downloaded. Install a SD CARD......something, something" (sorry, I'm at work).
Will formatting my sd card to FAT32 or NTFS fix this or is there something else wrong? I haven't seen any messages or errors regarding corruption and the sd card is working.
Thanks for any helpful suggestions!
When my 64Gb card was formatted exFat as it came stock, i had the same issue. I'm on LP. I had an almost empty card inserted, other than some mp3 files, and kept getting the message that my storage was full and that i need to delete some apps. I've since formatted it NTFS but i have not checked to see if items are being sent to the external SD. Don't have my tablet with me right now to check, but i wanted to reply to you that you were not alone in seeing the out of room message.
Sent from my LG-E980 using XDA Free mobile app
I had my PNY 64GB formatted with exFAT and it worked ok. I've switched to adopted storage and that worked too. But I saw other glitches with internal storage, such as MTP not seeing all files/folders even after reboot. I think "adopted storage" is buggy in general currently. It's also quite slow. Not impressed.
I prefer the Move to SD of Lollipop and Kitkat.
Do we already have a fix/workaround for this? I have a K1 (with the latest OTA 1.2) and 64GV Samsung Evo, formatting the sd card as adoptive storage still says corrupted. I already tried formatting it as Fat32/NTFS but to no avail.
I also couldn't get adopted storage to work.
The best fix for me is not using adopted storage
Instead I use an app called FolderMount which simply creates a symbolic link (is this the correcton term?) on the device's internal storage for whatever folder/file you like. It integrates moving data and managing it as well making the process as easy as it gets though you can of course do the same thing manually as it's using linux operations to do these things.
After you make the symbolic link when apps look for the data in the usual place on internal storage they "see" it but the data is actually whereever the symbolic link points to ie. on your external SD card.
Not found any real workaround for this it makes the tablet a bit of a dud
Sent from my SHIELD Tablet K1 using XDA-Developers mobile app
diji1 said:
I also couldn't get adopted storage to work.
The best fix for me is not using adopted storage
Instead I use an app called FolderMount which simply creates a symbolic link (is this the correcton term?) on the device's internal storage for whatever folder/file you like. It integrates moving data and managing it as well making the process as easy as it gets though you can of course do the same thing manually as it's using linux operations to do these things.
After you make the symbolic link when apps look for the data in the usual place on internal storage they "see" it but the data is actually whereever the symbolic link points to ie. on your external SD card.
Click to expand...
Click to collapse
I've read about the FolderMount app before but I thought that it works only for lollipop. I'll give this a try. Thanks!
NinjaCoool said:
I've read about the FolderMount app before but I thought that it works only for lollipop. I'll give this a try. Thanks!
Click to expand...
Click to collapse
Caveats: I actually haven't tried it on Marshmallow since I went back to LP however I cannot see any reason that FolderMount will not work as it's using underlying Linux operations to do all the work. But YMMV.
I like this approach since you can move any folder from internal storage to microSD which makes it very flexible. For example you could move:
/Download
/Images/DCIM
/Android/obb
/Android/data
/where you store recorded videos/
and never worry about internal storage again (until you run out of microSD of course lel)
Or whatever you wanted.
diji1 said:
Caveats: I actually haven't tried it on Marshmallow since I went back to LP however I cannot see any reason that FolderMount will not work as it's using underlying Linux operations to do all the work. But YMMV.
Click to expand...
Click to collapse
FolderMount from the Play Store is not working on MM due to security changes.
There is a beta version that fixes it for some devices. Best to read the official thread here: http://forum.xda-developers.com/showthread.php?t=2192122
Sent from my SGH-I337M using XDA Free mobile app
There's a problem with cards 64GB and up. I managed to format as internal storage a 32GB one, had no succes with 64 and 128 ones
I couldn't get portable storage to work on the stock MM RoW LTE rom. It works perfectly fine on all the custom roms I've tried (Bliss, Temasek, RR, etc) but none of those have LTE so for me it's either or if I want to use a MM rom. Otherwise, I'd have to use a LP rom for both to work...
I've hit this issue using the RR rom with my 128gb SD. But then if I keep the card in portable mode, I have those permission issues with my emulators. Has anyone got any suggestions or recommendations?
I've so far tried xInternalSD, SDFix and FolderMount with no success and I don't want to do that solution where I have to adjust the permission xml of all my apps. Its micromanagement I don't want.
I just have to use fat32 to get my 128gb card to work.
gqukyo said:
I just have to use fat32 to get my 128gb card to work.
Click to expand...
Click to collapse
To work as adopted storage or portable storage? Because mine is working in portable mode, just has write to SD permissions issues for any apps not updated to deal with MM's new OTT security requirements on External SD's (which is most apps to be honest).
Adopted storage, I only tried it once but didn't like it so using portable.
gqukyo said:
Adopted storage, I only tried it once but didn't like it so using portable.
Click to expand...
Click to collapse
Being Fat32 initially shouldn't have made a difference, because the card is reformatted to ext4 when its made into adopted storage and the tablet just seems incapable of reading an ext4 encrypted SD Card, so it comes up as corrupted.
What brand and model is your 128gb micro sd? And was it the stock rom you did it on? I'm using a Sandisk Ultra myself, and this definately does not work.
It's been awhile so I don't recall all the things I've tried nor the roms. All I know is I got it to it to work once. Think I have a SanDisk something. Just wasn't worth it in the end to me. If you're trying to get it to work, doesn't hurt to try. Stranger things have worked to fix issues in android.
Considering Android is based on Linux, albeit with an ancient kernel, does it support XFS file system? I'm guessing it formats the microSD card as any of the extended file systems (2, 3 or 4) but if it does support XFS, I'd prefer to format it as that FS.
Xfs on android (ported for sdcard)
Update: I've attached clockworkmod with support for xfs(or any other file system the kernel supports) all i did is put my kernel and modify /etc/recovery.fstab ). just untar it ,go to bootloader menu and do fastboot flash recovery...
forum.xda-developers.com
I saw that topic but it's 10 years old. I was hoping for more recent answers.
Why ? For what purpose exactly ? If you want better performance use an A2 microsd card. If you want a better filesystem try exfat , the xfs you can try to format it on Linux and see if the Android will work with it, however I don't recommend that, could introduce risk.
Check out ssdfs if you are into dev stuff however without GPT-5 I can't foresee much interesting happening in filesystems and storage handling due to complexity.
Network_Pro said:
Why ? For what purpose exactly ? If you want better performance use an A2 microsd card. If you want a better filesystem try exfat , the xfs you can try to format it on Linux and see if the Android will work with it, however I don't recommend that, could introduce risk.
Check out ssdfs if you are into dev stuff however without GPT-5 I can't foresee much interesting happening in filesystems and storage handling due to complexity.
Click to expand...
Click to collapse
For faster uploading of files. Ever since I formatted my storages to XFS they move/copy files between each other with the maximum speed their manufacturer says they can do. When they were ext4, copying 50 GB from one device to another was like on Windows - start fast then drop to a ridiculously slow speed, like 20 MB/sec, for instance. And I'm getting the same slow performance RN with the microSD card formatted by Android 12. I wanna upload 400 GB to the SD card but with the current file system I'll never have the 150 MB/sec the card's manufacturer says it can reach for writing. Which means I'll be uploading these 400 GB a whole year. I barely managed to upload my music which is 85 GB and it took me 3 hours to do that.
IDK how to format the microSD card on Linux. I don't even know if that's possible, bc GParted doesn't detect the phone as a device at all - even when it's mounted.
Ah here we are again trying to overcome corporations limitations they imposed on us by their retardation.
Well well well. Whos decision was it to Not use XFS in the first place? Give me a name... Someone from Google who was responsible for Android? Someone from the Phone Device manufacturer? The sd association for not informing developers about a correct filesystem? The makers of ext4 probably sponsored by Redhat ?
They are all GUILTY if you ask me. GUILTY !!!
They should give us our money back for all their crappy products !!!
We should start a class action law suit against all of them, for all of their bull**** limitations, separately for their retardation, and separately for their LIES in their advertising.
How do you know XFS is faster if you can not format the sdcard on Linux?
To format a sdcard on Linux - you connect Only the sdcard. After it's formatted - insert the sdcard in the phone and see if the phone can work with it, or not.
1.)SD cards are usually formatted with exfat.
2.)You will have to build your own kernel with explicit XFS support to enable XFS support.
Now I don't remember, but you can multipartition SD card
Keep the first partition as exfat, the second partition as XFS or ext4 or btrfs.
and loop mount it in a directory.
It's a convoluted process and not sure if it is worth the hassle.