I just noticed that SD cards formatted in NTFS via USB work on the Shield tab (Lollipop). So, would it also work in the SD card 1 (slot)?
You need to mount the sdcard in ntfs mannually with third app.
Sent fro SomeFon
No. It also works in the SD slot.
What device? He he.
Sent fro SomeFon
Shield.
I am searching an android device installed upon ntfs, due to several hardware concerns that ext2/3/4 causes in emmc or ssd disks, i experienced bootloop, only because an ext2 error on my sdext2 partition, i took out the sdcard, and the phone booted normally.
Ext any kind, i believe exfat is brother of ext, Nevermore i pretend use.
After i learned that kingston taiwan's original notebooks ssd disks, are usinf ntfs, and i still never seen any notebook with standard linux installed, think with me: may be why?
Hm.
Now, i modded the link2sd scripts to start sdext2 in a ntfs partition, 2Giga is the minimum for good ntfs usage, and what i am experiencing, is not comparable with any device that i had, is crazyly fast, stable, and no errors.
Sent fro SomeFon
See this:
Ntfs breaks cached ads.jar in various apps.
Anyone heard somewhere , the gogle will change the adwares method?
Ha, may it because why?
See the pictures:
Youtube, running on sdext2-ntfs
And the File explorer showing the youtube cache folder,
The ntfs security, detected remote code in cache.
Called by ads.jar 1 & 2
The ntfs security, stopped these jars, and renamed to .fusehidden... that you see on the picture.
So?
What more the damn ext1/2/3/4 Done for away desteoying devices via malicious cached dexes and jars codes?
Sent from SomeFon
Related
I have a Samsung galaxy tab 7" currently running the latest version of the overcome rom (but i'm not married to it if others here have better recommendations), and for whatever reason, whenever i try to format my newly purchased 32gb sd card that i've placed inside, it wants to format it in fat32, which is one of the worst filesystems for data integrity ever devised (no journaling or data protection features of any kind). I have attempted to use my fat32 formatted sd card for a few ebooks that i've got, but when i move them from one folder to another, and then reboot, I get a lost+found directory full of corrupt, errant data and an empty folder where i attempted to move my stuff... this is, of course, unacceptable.
first off, why is fat32 used for the sd card in the first place when the system clearly uses rfs by default (upgraded to ext4 by my overcome installation), and anyone who is technologically inclined knows the pretty extreme limitations of fat32 (4gb single file data limit, no file protection mechanisms)?
and secondly, how do I fix this problem? the tab doesn't seem to accept my sd card when i format it in ext4 using my ubuntu desktop and an sd card reader, nor does gingerbread seem to have any advanced mount controls at all (including strangely the lack of mount support for cifs/smb, which i think is crazy as well but probably well out of the scope of this particular post).
tldr: external storage support on gingerbread is archaic and broken, how do i fix it for regular use?
Pinging this thread for IMPORTANCE
I very much hate FAT32, yet am forced to keep using it in my external SD card on phone in the same way. I would love to see all devs add full ROM support for reformatting and mounting external SD cards with full suite of OS supported file systems. How is it OS supports EXT4 yet I am still bound to FAT32 on SD card !!!!????
This is very important to me, and should be to you all too. we need file system journaling and large file support!
Wouldn't hurt to build in advanced visual presentation for formatting/converting any partition on phone from/to all supported types with ability to setup swap partitions. I know I ask for a lot.
------Running--------
SPH-D710, Starburst ROM v2.0, EK02 modem, custom startup screen/sounds
---------------------
cpgeek said:
I have a Samsung galaxy tab 7" currently running the latest version of the overcome rom (but i'm not married to it if others here have better recommendations), and for whatever reason, whenever i try to format my newly purchased 32gb sd card that i've placed inside, it wants to format it in fat32, which is one of the worst filesystems for data integrity ever devised (no journaling or data protection features of any kind). I have attempted to use my fat32 formatted sd card for a few ebooks that i've got, but when i move them from one folder to another, and then reboot, I get a lost+found directory full of corrupt, errant data and an empty folder where i attempted to move my stuff... this is, of course, unacceptable.
first off, why is fat32 used for the sd card in the first place when the system clearly uses rfs by default (upgraded to ext4 by my overcome installation), and anyone who is technologically inclined knows the pretty extreme limitations of fat32 (4gb single file data limit, no file protection mechanisms)?
and secondly, how do I fix this problem? the tab doesn't seem to accept my sd card when i format it in ext4 using my ubuntu desktop and an sd card reader, nor does gingerbread seem to have any advanced mount controls at all (including strangely the lack of mount support for cifs/smb, which i think is crazy as well but probably well out of the scope of this particular post).
tldr: external storage support on gingerbread is archaic and broken, how do i fix it for regular use?
Click to expand...
Click to collapse
I tried formatting to ext4 and the phone did not recognize the card. Just wondered if anyone else had sucessfully tried any other filesystems?
Right now 64GB microsd's seem to be the best deal and name brand versions can be found as cheap as $20-25 where 128gb cards will still cost you $70+ and usually involve rebates at the lower end prices.
Exfat and fat32. I have mine formatted to fat32.
Sent from my Alcatel OneTouch Idol 3 using Tapatalk
Applications that can write to SD card can only write to a SD card format to FAT 32. The system file manager can write to Exfat, but that's it.
Still not all apps will have permissions. I can't get Utorrent to save to the ext sd for anything
Sent from my 6045I using XDA Free mobile app
jvs60 said:
Still not all apps will have permissions. I can't get Utorrent to save to the ext sd for anything
Sent from my 6045I using XDA Free mobile app
Click to expand...
Click to collapse
Syncthing is the same way...you should still be able to use the kitkat workaround though which is to save your files to a folder under the android\data\<appname> folder on the sdcard since each app has access to it's own data area.
I never knew about this workaround. So i create the folders on my ext sd card?
Sent from my 6045I using XDA Free mobile app
jvs60 said:
I never knew about this workaround. So i create the folders on my ext sd card?
Sent from my 6045I using XDA Free mobile app
Click to expand...
Click to collapse
Try this: http://www.instructables.com/id/How-to-bypass-Android-44-KitKat-external-SD-write-/
damn... i'll try that
how come the sdcard can't be used for anything
camera 360 can't use it to save, there's no option to choose applications installation on sdcard ect.
had to use link2sd to move almost all my apps without error
seriously now...
keyra74 said:
damn... i'll try that
how come the sdcard can't be used for anything
camera 360 can't use it to save, there's no option to choose applications installation on sdcard ect.
had to use link2sd to move almost all my apps without error
seriously now...
Click to expand...
Click to collapse
It can be used if you are rooted...requires adding a line to platform.xml. If you find the thread about what camera software to use I posted some instructions on how to fix it where 3rd party's can use the external sd...or you can google on "platform.xml android external sd".
http://forum.xda-developers.com/showpost.php?p=62100041&postcount=37
famewolf said:
It can be used if you are rooted...requires adding a line to platform.xml. If you find the thread about what camera software to use I posted some instructions on how to fix it where 3rd party's can use the external sd...or you can google on "platform.xml android external sd".
http://forum.xda-developers.com/showpost.php?p=62100041&postcount=37
Click to expand...
Click to collapse
thx i used the goold old sdfix app. it's normally for kitkat and we have to use some trick like that on lollipop bad alcatel bad
keyra74 said:
thx i used the goold old sdfix app. it's normally for kitkat and we have to use some trick like that on lollipop bad alcatel bad
Click to expand...
Click to collapse
Blame google, not Alcatel. The external sd card issue is due to Lollipop..
That app makes the same change...you can uninstall it after it modifies the file. Simpler for me to just edit the file and push the change.
I'm on exfat on a 64gb. Works fine.
The 200gb I had in my g3 worked just fine.
Just realized the card cost more than this phone...
scatoclysm said:
I'm on exfat on a 64gb. Works fine.
Click to expand...
Click to collapse
+1
My 32 gb HDSC card came formatted with FAT32. I preferred ExFAT, so I reformatted the card using Disk Utility on my Mac. The Icon 3 didn't recognize it until I reformatted back to FAT32. Maybe I should have tried formatting it on a Windows machine. I may try a 64 GB HDXC card that probably comes formatted with ExFAT.
maigre said:
My 32 gb HDSC card came formatted with FAT32. I preferred ExFAT, so I reformatted the card using Disk Utility on my Mac. The Icon 3 didn't recognize it until I reformatted back to FAT32. Maybe I should have tried formatting it on a Windows machine. I may try a 64 GB HDXC card that probably comes formatted with ExFAT.
Click to expand...
Click to collapse
Really not much of a benefit to exfat over fat32...especially if you set cluster size when formatting. I also read about some folks having permission issues writing to the exfat till they reformatted. The samsung 128GB I put in my idol3 worked like a champ.
NooB....Thank Google lollypop for sdcard problems. U can write to sdcard with some apps not all if the code is written for this.
It seems TWRP doesn't recognise exfat partitions if the sdcard doesn't contain a partition table (GPT works, I haven't tried old-style msdos partition table).
This could be partly explained by the fact that, without a partition table, the external sdcard is called /dev/block/mmcblk1 instead of /dev/block/mmcblk1p1
To put it another way, if you want your sd card to be both readable when the phone is normally booted AND when it's booted into TWRP, you have to make a GPT table on the sdcard, and create an exfat partition inside.
=> In windows, it just fell into place after messing around with it for a bit. Your mileage will vary, depending on if you had an msdos partition table, a pre-existing GPT partition table (easiest) or no partition table at all. I gave up trying to figure it out.
=> Under TWRP adb shell, using the image containing gdisk, I did it this way (data-destructive operation !) :
- Use gdisk to create a new GPT table on /dev/block/mmcblk1 (or /dev/sdX outside from adb shell)
- Also with gdisk, create a new partition (types 8300 or 0700 should do) on the device targeted previously
- Then, exit gdisk and use "mkfs.exfat -n extsd /dev/block/mmcblk1p1" (or /dev/sdX1 if you didn't do it from TWRP adb shell) to reformat the partition created previously to exfat format.
However => do NOT use mkfs.exfat command on the /dev/block/mmcblk1 device (or /dev/sdX), else you'll have to redo step 1 again
Also, under adb shell, make sure you don't accidentally wipe /dev/block/mmcblk0 device, else you'll brick your phone !
I hope this helps a few people
DarkZell666 said:
It seems TWRP doesn't recognise exfat partitions if the sdcard doesn't contain a partition table (GPT works, I haven't tried old-style msdos partition table).
This could be partly explained by the fact that, without a partition table, the external sdcard is called /dev/block/mmcblk1 instead of /dev/block/mmcblk1p1
To put it another way, if you want your sd card to be both readable when the phone is normally booted AND when it's booted into TWRP, you have to make a GPT table on the sdcard, and create an exfat partition inside.
=> In windows, it just fell into place after messing around with it for a bit. Your mileage will vary, depending on if you had an msdos partition table, a pre-existing GPT partition table (easiest) or no partition table at all. I gave up trying to figure it out.
=> Under TWRP adb shell, using the image containing gdisk, I did it this way (data-destructive operation !) :
- Use gdisk to create a new GPT table on /dev/block/mmcblk1 (or /dev/sdX outside from adb shell)
- Also with gdisk, create a new partition (types 8300 or 0700 should do) on the device targeted previously
- Then, exit gdisk and use "mkfs.exfat -n extsd /dev/block/mmcblk1p1" (or /dev/sdX1 if you didn't do it from TWRP adb shell) to reformat the partition created previously to exfat format.
However => do NOT use mkfs.exfat command on the /dev/block/mmcblk1 device (or /dev/sdX), else you'll have to redo step 1 again
Also, under adb shell, make sure you don't accidentally wipe /dev/block/mmcblk0 device, else you'll brick your phone !
I hope this helps a few people
Click to expand...
Click to collapse
Or just keep it formatted as fat32 and skip the above which was my choice.
Just my two cents - why would you want to format SD to ext4? Journaling filesystems don't work very well with flash drives, cells die much quicker.
Hey guys,
I was hoping someone with some experience with Android M could help. After installing the OTA update and upgrading to Marshmallow, it seems that the OS makes you format microSD cards as either portable or internal storage. The issue that I'm running into is that after formatting the memory card as portable storage, the system formats it as Fat32 so I can no longer transfer large MKV files to play in Kodi. Prior to installing the 6.0 OTA, I had no issues transferring the files to my microSD card.
As a workaround, I tried using my USB OTG drive to play the videos but I can't get Kodi to recognize the drive as a source for my video files. Does anyone have any suggestions on how to get around these new memory card complications that Android 6.0 has introduced?
I would greatly appreciate some help on this as this was one of the main reasons I purchased this tablet so that I could use it as a temporary HTPC when I'm traveling. Thanks in advance!
Have you tried removing the SD CARD and formatting on a PC?
Seems that Marshmallow's not all it's cracked up to be.
Don't have marshmallow, but have you tried reformatting the SD card on your PC using exFat or NTFS instead?
I don't know if marshmallow will prompt you to reformat again when you put the card back in the Shield though...
Sent from my SHIELD Tablet using XDA Free mobile app
You didn't mention what size of card, but if it is larger than 32gigs you will need to put the sd card in a computer and format as NTFS. Android doesn't support exfat, only fat32 and NTFS. Try that and let us know what happens!
hbar98 said:
You didn't mention what size of card, but if it is larger than 32gigs you will need to put the sd card in a computer and format as NTFS. Android doesn't support exfat, only fat32 and NTFS. Try that and let us know what happens!
Click to expand...
Click to collapse
Funny...running a 64GB SDCard formatted exFat right now on my original ST8 (Lollipop)...and also a 16GB SDCard formatted exFat on my old Samsung S4 (also Lollipop).
Sent from my SHIELD Tablet using XDA Free mobile app
Try to restart tablet? The best is using es Explorer to transfer files. Fat32 do not accepted file over 4gb. Try format back exfat
Sent from my SHIELD Tablet K1 using Tapatalk
An Droid said:
Funny...running a 64GB SDCard formatted exFat right now on my original ST8 (Lollipop)...and also a 16GB SDCard formatted exFat on my old Samsung S4 (also Lollipop).
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
(sarcasm)
Oh, wow! Your personal experience with two different phones made by two different manufacturers running an old system that was never designed for what Marshmallow does obviously contradicts and demolishes what I said.
(/sarcasm)
ExFat support can be added to android kernels, if the manufacturer decides to do so. Samsung, a maker of sd cards ranging from 4gigs to 200+gigs, has an interest in making sure that their devices work with their cards that also work in a variety of consumer computers. ExFat support can also be added in customer kernels, should the maintainer decided to do so (in fact, many kernels that I see for modern devices that also support an external sd cards proudly show that they support ExFat).
Android AOSP, without any mods or other built in support, does not support ExFat well, if at all. It may or may not work. The fact that nVidia has written that any cards over 32gig must be formatted to NTFS tells me that they have not chosen to build in ExFat support into their devices. Should someone desire to flash a different rom or custom kernel that support ExFat, that is their business. But since the OP didn't list what size of card they used, or if they were using any mods or a different kernel, I had to go with the most basic support.
hbar98 said:
(sarcasm)
Oh, wow! Your personal experience with two different phones made by two different manufacturers running an old system that was never designed for what Marshmallow does obviously contradicts and demolishes what I said.
(/sarcasm)
Android AOSP, without any mods or other built in support, does not support ExFat well, if at all. It may or may not work. The fact that nVidia has written that any cards over 32gig must be formatted to NTFS tells me that they have not chosen to build in ExFat support into their devices. Should someone desire to flash a different rom or custom kernel that support ExFat, that is their business. But since the OP didn't list what size of card they used, or if they were using any mods or a different kernel, I had to go with the most basic support.
Click to expand...
Click to collapse
ST8 = Shield Tablet 8" (original vs. K1 model).
Point is, this goes against your open ended and incorrect "Android doesn't support exfat, only fat32 and NTFS" statement.
Supporting exFAT in Android makes sense as it's the recommended file system by the SDCard association for SDCards larger than 32GB.
NTFS is in the same boat - it's also not officially supported by all Android implementations.
Marshmallow formats SDCards to Ext4 (and encrypts) when configured as internal storage. When configured as portable both exFAT and NTFS (and Fat16/32) may all be an option - OP can try both if using the portable option.
Sent from my SGH-I337M using XDA Free mobile app
Similar problem with lg g2 on marshmallow
Hi,
Having a related problem with kodi on my phone.
On lollipop, kodi found my 16gb Fat32 otg USB drive as a source, but won't show up now I'm on marshmallow. I can still play video through mx player, fx explorer media viewer, and os video player. I searched around storage and mount folders, but can find no access to the external drive browsing the file system unless I'm using the native file browser.
Marshmallow detects partition very different with Lollipop. on Marshmallow your device can use sdcard with 128 GB like internal
its mean sdcard needed change partition format to another type (not FAT, NTFS or exFAT) the matter here then you plug that sdcard to windows, windows wont detect your sdcard but you can see it through another program like MiniTool Partition Wizard.
The problem with marshmallow and this partition used to drop out connect with your sdcard. only one way to fix it reboot your device. also, sometime they cant turn wifi on then you just needed to reboot again to let your device working normally.
We needed to wait for a new patch.
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.