This is a cross post of a thread in the Q & A section because I think it is more appropriate here. Please forgive me if you disagree.
I have encountered a problem using SDXC cards in the Galaxy S III. It appears, to me, to be a bug in the exFAT drivers which are only used in the 64 GB SDXC card, 32GB cards and less are formatted as FAT32.
Please see thread http://forum.xda-developers.com/showthread.php?t=1805743 for further information.
ChitownWingMan said:
This is a cross post of a thread in the Q & A section because I think it is more appropriate here. Please forgive me if you disagree.
I have encountered a problem using SDXC cards in the Galaxy S III. It appears, to me, to be a bug in the exFAT drivers which are only used in the 64 GB SDXC card, 32GB cards and less are formatted as FAT32.
Please see thread http://forum.xda-developers.com/showthread.php?t=1805743 for further information.
Click to expand...
Click to collapse
I heard you might need to format the card as FAT32
Zephyron said:
I heard you might need to format the card as FAT32
Click to expand...
Click to collapse
You can't use FAT32 on a 64GB card. The phone formats 32GB or smaller as FAT32 and the 64GB at exFAT.
Some platforms support FAT32 on greater than 32GB cards/drives but it is not very compatible.
Thanks for your help
ChitownWingMan said:
You can't use FAT32 on a 64GB card. The phone formats 32GB or smaller as FAT32 and the 64GB at exFAT.
Some platforms support FAT32 on greater than 32GB cards/drives but it is not very compatible.
Click to expand...
Click to collapse
Don't confuse FAT32 and FAT16. FAT32 supports up to 2 TB, though I believe Windows makes it difficult to format anything larger than 32 GB.
tamasrepus said:
Don't confuse FAT32 and FAT16. FAT32 supports up to 2 TB, though I believe Windows makes it difficult to format anything larger than 32 GB.
Click to expand...
Click to collapse
You are correct the theoretical maximum size of FAT32 is 2TB. However, since Microsoft in their infinite wisdom decided only to support FAT32 up to 32GB (most likely to force people to use NTFS) support for FAT32 above 32GB is spotty and unreliable.
This being said if you format a 32GB card or smaller in the Galaxy S III, it will be formatted FAT32. If you format a 64GB (or greater I presume) in the Galaxy S III, it will be formatted exFAT.
ChitownWingMan said:
You are correct the theoretical maximum size of FAT32 is 2TB. However, since Microsoft in their infinite wisdom decided only to support FAT32 up to 32GB (most likely to force people to use NTFS) support for FAT32 above 32GB is spotty and unreliable.
This being said if you format a 32GB card or smaller in the Galaxy S III, it will be formatted FAT32. If you format a 64GB (or greater I presume) in the Galaxy S III, it will be formatted exFAT.
Click to expand...
Click to collapse
exFat format will not read correctly on SGSIII. I just had this issue with my 64 GB SD card. I formatted it in FAT32 and all was fine. I did use a Mac with disk utility to do the formatting though. Windows 7 was trying to force exFAT to format.
ChitownWingMan said:
You are correct the theoretical maximum size of FAT32 is 2TB. However, since Microsoft in their infinite wisdom decided only to support FAT32 up to 32GB (most likely to force people to use NTFS) support for FAT32 above 32GB is spotty and unreliable.
Click to expand...
Click to collapse
Windows Vista and above don't let you format volumes larger than 32 GB as FAT32. It's an artificial limitation on their part.
Other than that, FAT32 has been around a long time, and works fine with 32+ GB volumes. It's not great but doesn't really become spotty and unreliable till you go beyond 100 GB or so.
I'd get a Linux LiveCD and format your SD card FAT32 with that.
Partition Wizard Home Edition (win) is free and will format all your fat32 needs http://www.partitionwizard.com/free-partition-manager.html
hauniii said:
exFat format will not read correctly on SGSIII. I just had this issue with my 64 GB SD card. I formatted it in FAT32 and all was fine. I did use a Mac with disk utility to do the formatting though. Windows 7 was trying to force exFAT to format.
Click to expand...
Click to collapse
Thank you for confirming my research. I am currently in communication with Samsung, T-Mobile and SanDisk. With any luck with potential sales in the millions they will fix it. The man at Samsung commented "We sell that card on our website we had better get it working"
Further Update
ChitownWingMan said:
Thank you for confirming my research. I am currently in communication with Samsung, T-Mobile and SanDisk. With any luck with potential sales in the millions they will fix it. The man at Samsung commented "We sell that card on our website we had better get it working"
Click to expand...
Click to collapse
I spoke with someone at Sandisk and they have heard of the problem and are researching it. T-Mobile and Samsung are also "investigating" it.
I formatted my 64GB card FAT32 and I am using it like that for now.
One problem with using FAT32 is that there is a directory size limit of 65,535 bytes total for the directory itself (not the files in the directory). I have a Titanium Backup directory with almost 12,000 files in it, all with long names. That easily exceeds the 64K directory size limit and this directory is "full" and trying to write to it generates errors.
If you have a directory with 5,000 files with an average file name length of 12 characters (rather short in this day and age) that makes the directory 60,000 bytes. If the average file name length is 13 characters the directory size will be 65,000 bytes and if the average file name length is 14 bytes the directory size is now 70,000 bytes and this exceeds the maximum directory size.
If you keep your file names to the old DOS 8.3 (11 characters) format then a directory can handle approx. 5,957 files. The actual number is less because there are other bytes in each entry used by the system (permissions, file size, starting segment, etc.).
For programs like Titanium Backup this can become a problem. Titanium backup uses long file names (longer than 20 characters) that include the date in them. I always backup my entire phone downloaded apps & data, system apps & data and system data. This is about 470 different items being backed up. Titanium Backup uses 2 and sometimes 3 files for each item backed up. I also maintain a 7 day backup history. This creates a total of 8,225 (approx) files, if each has a file name length of 20 characters that would be a directory size of 164,500 bytes.
This far exceeds what FAT32 can handle. And this is a somewhat reasonable scenario.
So, let's put pressure on T-Mobile and Samsung to get the exFAT problem fixed.
Related
I've tested two sandisk class 4 SD cards.
If I format it to fat32 and partition the space(to use link2SD), my phone refuses to use the SD card and says it's not there. I use minitools for partition and the official SD card maker software for formating. I did everything by the book and tried multiple options(different labels, ntfs, ext2, etc.)
A fresh, unallocated space card works perfectly fine however.
My phone is rooted and unlocked bootloader running softMIUI rom with a modfied power saving blend kernel.
Please help! This is confusing the hell out of me.
Was looking at your post and I decided to grab a few of my MicroSD card 1gb, 2gb, 4gb, 8gb and 16gb....
I formated all of them on windows .... right click format, all default settings... Fat32. These are MicroSD cards that have had information on them... they all run fin on my arc. All different brands.
This leads me to believe that there's possibly either something wrong with the MsD card or the reader on the phone.
fluxgfx said:
Was looking at your post and I decided to grab a few of my MicroSD card 1gb, 2gb, 4gb, 8gb and 16gb....
I formated all of them on windows .... right click format, all default settings... Fat32. These are MicroSD cards that have had information on them... they all run fin on my arc. All different brands.
This leads me to believe that there's possibly either something wrong with the MsD card or the reader on the phone.
Click to expand...
Click to collapse
Solved it
Did this:
Changed the partition id to this:
"0*06 fat16,greater than 32 mb"
and made the second partition fat32 as well.
Removed the 100mb linux swap file partition I created....not sure if that was necessary.
I just received this in the mail and I was wondering where do I start in terms of formating format and allocation size? Also, how would I check its true capacity and transfer rates?
put it in the phone & let it format for you, it formats exFAT but I was using a 64GB card. Not sure if it does FAT32 if using a 32gb or smaller sd card. If you need FAT32 then use linux or Windoze to format it & I always "default" for allocation size.
that is my question too. thanks
I have a Sandisk Ultra SDXC 64GB Class 10 UHS-1 Micro SD card in my T999 T-Mobile Galaxy S III phone.
The card has become "damaged" (Samsung's term). 4 times now. Please note that the card works fine on my Window 7 PC. This last time I formatted the card in the phone, put the card in the PC, copied a bunch of files to it (about 3GB) and then put the card back into the phone. And the phone said that the card might be damaged. I was sure to unmount the card before removing it.
I called T-Mobile tech support and they know nothing about it.
I called Sandisk and they said "There are known problems with Samsung Phones and Tablets and Sandisk Class 10 cards. Samsung is aware of this and working on it. Would you like us to replace your Class 10 UHS-1 card with a Class 6 card?"
I called Samsung tech support and they know nothing about it and are not setup to tell their engineers about issues. The only way to report an issue to engineering is via email.
Let's make a loud stink about this so Samsung/T-Mobile will fix it.
Follow up on original post:
I went out and purchased the recommended Sandisk 64 GB SDXC Class 6 memory card and the problems are exactly the same as with the Class 10 card.
The problem seems to appear when there is more that 4GB (I'm not sure if it is exactly the 4GB barrier or not) on the card the Galaxy S III has a problem mounting the card. Note that once the card has gone greater than 4 GB even deleting files to reduce it below 4 GB does not allow the card to be mounted.
On the class ten card I was able to successfully run the fsck -t exfat command on the card that Android would not mount. fsck returned no errors or problems found.
My testing is rather limited but I can say: The T-Mobile Galaxy S III (T999) does not work correctly with SanDisk Ultra 64 GB SDXC memory cards (class 6 or Class 10)
Please, let's spread this around so that maybe Samsung, T-Mobile and SanDisk will learn how to work together and solve the problem for the sake of their customers.
I put the new card in the phone and formatted it in the phone.
I don't quite understand how you got 2 crap microsd card, I'm using a Samsung ultra 32gb class 10 just fine, never had one problem mounting it never seen one error message. Sorry
Sent from my SGH-T999 using xda premium
achmedclaus said:
I don't quite understand how you got 2 crap microsd card, I'm using a Samsung ultra 32gb class 10 just fine, never had one problem mounting it never seen one error message. Sorry
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I think it is a software problem with the 64 GB Micro SDXC Card.
I have a Sandisk Ultra SDXC 64GB Class 10 UHS-1 in my Galaxy SIII and have never had an issue. I had problems formatting the card in my PC, So i just threw it in the phone and formatted it there. It was formatted and I have loaded about 25gb of music, 5gb of pictures through Cheetah Sync without issue.
picachux said:
I have a Sandisk Ultra SDXC 64GB Class 10 UHS-1 in my Galaxy SIII and have never had an issue. I had problems formatting the card in my PC, So i just threw it in the phone and formatted it there. It was formatted and I have loaded about 25gb of music, 5gb of pictures through Cheetah Sync without issue.
Click to expand...
Click to collapse
Have you rebooted your phone or unmounted and remounted the card? That is when the problems occur.
I believe that there is a bug in the code the Samsung uses to check the card prior to mounting. They are doing more than just a simple
fsck -t exfat.
I tried a 32 GB SDHC Samsung Class 10 card with the exact same data that was on the 64GB SDXC card without any problems. It is my belief that there is a bug in exFAT code in the Galaxy S III.
Thanks for your comments.
I have only unmounted the card twice to kickstart the media scan after loading some music and I reboot my phone every 2 days or so.
ChitownWingMan said:
Have you rebooted your phone or unmounted and remounted the card? That is when the problems occur.
Click to expand...
Click to collapse
I've reboot my phone all the time—I don't have any problems. I don't mount/unmount very often, but just tried it now and everything appears to be fine.
My card is a 64 GB class 5 SanDisk, formatted FAT32 (done on a Linux machine).
tamasrepus said:
I've reboot my phone all the time—I don't have any problems. I don't mount/unmount very often, but just tried it now and everything appears to be fine.
My card is a 64 GB class 5 SanDisk, formatted FAT32 (done on a Linux machine).
Click to expand...
Click to collapse
I believe the bug is in the exFAT drivers in the S III.
I formatted the card in the S III under the mistaken assumption that the phone would know best.
The theoretical maximum size of FAT32 is 2TB. However, since Microsoft in their infinite wisdom decided only to support FAT32 up to 32GB (most likely to force people to use NTFS) support for FAT32 above 32GB is spotty and unreliable.
This being said if you format a 32GB card or smaller in the Galaxy S III, it will be formatted FAT32. If you format a 64GB (or greater I presume) in the Galaxy S III, it will be formatted exFAT.
I will try formatting the card as a 64GB FAT32 partition. However, this will mess up my using a USB 3.0 card reader (at 5Gb/S transfer rate) to write to the card. Writing to the card via WiFi is interminably slow by comparison.
Sounds like windows is damaging the exFAT partition when you plug it in to your computer to transfer stuff. I've never done that because I just use Cheetah Sync to sync my iTunes(25gb) folder to my sdxc card and to sync my pictures/videos from the sdxc to my pc.
ChitownWingMan said:
I believe the bug is in the exFAT drivers in the S III.
Click to expand...
Click to collapse
Seems that way to me too. exFAT is not in Linux upstream, so I imagine Samsung just bought a binary driver from someone. Who knows the quality.
I will try formatting the card as a 64GB FAT32 partition. However, this will mess up my using a USB 3.0 card reader (at 5Gb/S transfer rate) to write to the card. Writing to the card via WiFi is interminably slow by comparison.
Click to expand...
Click to collapse
What does the card reader have to do with it? I've a USB 3.0 card reader, and my 64 GB FAT32-formatted fine.
As I recommended in the other thread, use a Linux Live CD to format your SD card.
tamasrepus said:
Seems that way to me too. exFAT is not in Linux upstream, so I imagine Samsung just bought a binary driver from someone. Who knows the quality.
What does the card reader have to do with it? I've a USB 3.0 card reader, and my 64 GB FAT32-formatted fine.
As I recommended in the other thread, use a Linux Live CD to format your SD card.
Click to expand...
Click to collapse
or use Partition Wizard Home Edition (free)(windows) for large fat32 format jobs works perfectly and the price is right http://www.partitionwizard.com/free-partition-manager.html
picachux said:
Sounds like windows is damaging the exFAT partition when you plug it in to your computer to transfer stuff. I've never done that because I just use Cheetah Sync to sync my iTunes(25gb) folder to my sdxc card and to sync my pictures/videos from the sdxc to my pc.
Click to expand...
Click to collapse
Because I thought the same thing one of the tests that I performed was to never remove the card from the phone. I did all of my copying to and from the card via File Expert Web Sharing. One day I ran the phone battery down and the phone rebooted. When it came back up it was unable to verify the card. However, fsck -t exfat found no problems with the card.
One interesting point, I was using Cheetah Sync (a great program) last night to copy a TitaniumBackup directory to the phone and it failed. Here is a copy of the email I sent to the developer:
The destination directory contains 11,841 files totaling 2.93GB and Cheetah needs to download 1917 files and is failing on the 1st file with the error "Sync Error - I/O error downloading files.".
Note: Cheetah Sync had already copied almost 7,000 files. It originally failed during a copy of almost 9,000 files. I restarted
the sync and that is why it failed on 1 of 1,917 files.
I am using a T-Mobile Galaxy S III (Model SGH-T999) with 32 GB internal memory and a 32 GB external SD Card (Samsung Class 10).
The source directory is c:\phone\card_backup\TitaniumBackup and the destination directory is /mnt/extSdCard/TitaniumBackup.
I am able to manually create a file in that directory using a file explorer.
tamasrepus said:
Seems that way to me too. exFAT is not in Linux upstream, so I imagine Samsung just bought a binary driver from someone. Who knows the quality.
What does the card reader have to do with it? I've a USB 3.0 card reader, and my 64 GB FAT32-formatted fine.
As I recommended in the other thread, use a Linux Live CD to format your SD card.
Click to expand...
Click to collapse
The card reader is not the issue just the mechanism to allow me to copy files quickly from/to the card.
How Windows will handle a FAT32 partition greater than 32GB is my concern. In the past I have always used NTFS for drives/cards greater than 32GB because FAT32 has a 4GB - 1 file size limit and I have many video files that are larger then that.
MiniTool Partition Wizard and Easeus Partition Master can both also make a 64GB FAT32 partition.
Thanks...
Update
There is an update to this thread here:
http://forum.xda-developers.com/showpost.php?p=29904990&postcount=10
I have a SanDisk 64gb card which is formatted Fat32.
I've been running it without issue for a few months.
45gb is being used.
I wanted to transfer the files to my pc, and have a few questions/comments:
- after transferring my files I want to format to exFAT
- will my files that were on my Fat32 card be able to be transferred to my exFAT card, as there are a couple of Nandroid, ROM downloads, pics, etc. that I want to transfer back.
- after transferring files to my pc, I was going to place the card back into my S4 and format card from the device. From what I've read, the device will format the card to exFAT. Would this be correct?
There are a couple of reasons I'd like to format the card:
- I want to transfer files to pc, and have some more space on the card, and figured I'd format to exFAT so as not to have file size limitations, although I've yet to dl any 4gb files.
- I'm taking a preemptive strike to avoid possible card issues which may arise in the future. I thought transferring many of the 45gb of files on the card, and re-formatting the card may assist with this, or is this not necessarily true?
If formatting the card and emptying files doesn't reduce the possibility of borking the card in the future, I want to transfer files anyway, in addition to having the card in exFAT unless there is a downside to this format.
Tia......
I recommend keeping it at Fat32. The phone won't read ExFat.
Sent from Spaceball One.
Biker1 said:
I have a SanDisk 64gb card which is formatted Fat32.
I've been running it without issue for a few months.
45gb is being used.
I wanted to transfer the files to my pc, and have a few questions/comments:
- after transferring my files I want to format to exFAT
- will my files that were on my Fat32 card be able to be transferred to my exFAT card, as there are a couple of Nandroid, ROM downloads, pics, etc. that I want to transfer back.
- after transferring files to my pc, I was going to place the card back into my S4 and format card from the device. From what I've read, the device will format the card to exFAT. Would this be correct?
There are a couple of reasons I'd like to format the card:
- I want to transfer files to pc, and have some more space on the card, and figured I'd format to exFAT so as not to have file size limitations, although I've yet to dl any 4gb files.
- I'm taking a preemptive strike to avoid possible card issues which may arise in the future. I thought transferring many of the 45gb of files on the card, and re-formatting the card may assist with this, or is this not necessarily true?
If formatting the card and emptying files doesn't reduce the possibility of borking the card in the future, I want to transfer files anyway, in addition to having the card in exFAT unless there is a downside to this format.
Tia......
Click to expand...
Click to collapse
Shouldn't be a problems with what you're wanting to do.
-Copy sd card contents to PC
-Reformat and copy content back
-Make sure the recovery you're using can read exFAT (both TWRP and Philz CWM can read exFAT)
-Also be sure the kernel support exFAT or your phone might not boot up.
-There's pros and cons to each format but for regular user like myself it's not something I really worry about
blackknightavalon said:
I recommend keeping it at Fat32. The phone won't read ExFat.
Sent from Spaceball One.
Click to expand...
Click to collapse
The phone out of the box should read exFAT. It's when using different kernels that does not support exFAT it will not read.
baseballfanz said:
Should be a problems with what you're wanting to do.
-Copy sd card contents to PC
-Reformat and copy content back
-Make sure the recovery you're using can read exFAT (both TWRP and Philz CWM can read exFAT)
-Also be sure the kernel support exFAT or your phone might not boot up.
-There's pros and cons to each format but for regular user like myself it's not something I really worry about
The phone out of the box should read exFAT. It's when using different kernels that does not support exFAT it will not read.
Click to expand...
Click to collapse
Last night, I:
- copied 45gb data from card to pc - 50 minutes
- I've read about the kernels and the format to be used
- decided to keep card @ Fat32 : "If it Ain't Broke, Don't Fix It" applies here
- I haven't deleted files yet, or formatted
I formatted the card once before using my pc and www.easeus.com
I found this also:
http://forum.xda-developers.com/showthread.php?t=1773735&page=2
But most likely will use the easeus method, which is also in that thread.
I'll take another look, but does formatting the card using the S4 format to exFAT or Fat32?
I thought it was exFAT, buy info or mis info is all over the place.
I've not used the on phone format feature yet.
To go from exFat to FAT32 I use Minitool partition
http://download.cnet.com/MiniTool-Partition-Wizard-Home-Edition/3000-2094_4-10962200.html
To go from FAT32 to exFat I just used the Windows PC formatting feature.
baseballfanz said:
I've not used the on phone format feature yet.
To go from exFat to FAT32 I use Minitool partition
http://download.cnet.com/MiniTool-Partition-Wizard-Home-Edition/3000-2094_4-10962200.html
To go from FAT32 to exFat I just used the Windows PC formatting feature.
Click to expand...
Click to collapse
I'm on Fat32 already.
Is re-formatting an exercise in futility?
I was thinking to re-format because:
- after months of making Nandroids without issue, I had trouble recently Booting after backing up to extSdCard. I'd freeze on Samsung splash after multiple backup attempts.
I backed up to internal and booted fine. I dont know if this was coincidence, but figured I'd format for good measure. Otherwise, the extSdCard is running without issue.
Not sure there even is an issue.
I actually had a successful Nandroid to extSdCard card afterwards.
Just thinking out loud.
I'll probably just empty the card of some gb, and not format.
Biker1 said:
I'm on Fat32 already.
Is re-formatting an exercise in futility?
I was thinking to re-format because:
- after months of making Nandroids without issue, I had trouble recently Booting after backing up to extSdCard. I'd freeze on Samsung splash after multiple backup attempts.
I backed up to internal and booted fine. I dont know if this was coincidence, but figured I'd format for good measure. Otherwise, the extSdCard is running without issue.
Not sure there even is an issue.
I actually had a successful Nandroid to extSdCard card afterwards.
Just thinking out loud.
I'll probably just empty the card of some gb, and not format.
Click to expand...
Click to collapse
Formatting is a breeze. I've gone from exFAT to FAT32 and vice versa without a problems. Both was achieved in minutes, only time consuming is copying contents to and from sd card.
I was also having troubles with TWRP not booting past Samsung splash screen and I was on exFAT at the time.
Like you have mentioned I only got that problems since flashing with Aroma and never before that.
I've since switch over to Philz CWM and everything is OK (except nandroid backup take ages:laugh
blackknightavalon said:
I recommend keeping it at Fat32. The phone won't read ExFat.
Sent from Spaceball One.
Click to expand...
Click to collapse
I'm sorry but this is an incorrect statement. Samsung has supported exFat on 64GB cards only on both the Galaxy S3 and S4. Their initial implementation was buggy but they did work the kinks out.
Here are the disadvantages to using FAT32 on 64GB cards:
Fat32 only supports files up to 4GB - 1 (technically 4,294,967,295 bytes) in length. A high definition video today takes up to 4GB per hour of video (even more sometimes). This limits the size of movies you can store.
The maximum size of a directory (actual number of bytes of the directory itself, not number of files) is limited to 65,5355 bytes. Considering that each directory entry takes up 32 bytes that limits the number of files in a single directory to 2047 entries if long file names are not used. With files names longer than 8 characters that number gets reduced significantly. That is a problem for apps like Titanium backup that use lots of files or if you have a lot of MP3s.
I have been using exFat on my 64GTB SDXC memory cards on both my S3 and my s4 without any problems after Samsung fixed the initial bugs.
You should not encounter any problems copying files from your FAT32 card to your PC and then copying them back to an exFat card. I have done that several times.
@ChitownWingMan
Some good info there re capacities and such.
Earlier I decided to keep the format at Fat32, and didn't re format
If it ain't broke, don't fix it, as they say.
I also understand that exFat is Kernel sensitive, so I'd be limited to wha I can flash
Owe ya a Thanks. My daily 8 limit ran out
Biker1 said:
@ChitownWingMan
Some good info there re capacities and such.
Earlier I decided to keep the format at Fat32, and didn't re format
If it ain't broke, don't fix it, as they say.
I also understand that exFat is Kernel sensitive, so I'd be limited to wha I can flash
Owe ya a Thanks. My daily 8 limit ran out
Click to expand...
Click to collapse
Your welcome. I was one of the first people to report the exFat bug in the original release of the S3 and I worked with Sandisk and Samsung to identify it as a bug.
I actually tried to run NTFS for a while but I couldn't find a decent implementation for Android and EXT2, EXT3 or EXT4 have little or no support on Windows.
ChitownWingMan said:
I'm sorry but this is an incorrect statement. Samsung has supported exFat on 64GB cards only on both the Galaxy S3 and S4. Their initial implementation was buggy but they did work the kinks out.
Here are the disadvantages to using FAT32 on 64GB cards:
Fat32 only supports files up to 4GB - 1 (technically 4,294,967,295 bytes) in length. A high definition video today takes up to 4GB per hour of video (even more sometimes). This limits the size of movies you can store.
The maximum size of a directory (actual number of bytes of the directory itself, not number of files) is limited to 65,5355 bytes. Considering that each directory entry takes up 32 bytes that limits the number of files in a single directory to 2047 entries if long file names are not used. With files names longer than 8 characters that number gets reduced significantly. That is a problem for apps like Titanium backup that use lots of files or if you have a lot of MP3s.
I have been using exFat on my 64GTB SDXC memory cards on both my S3 and my s4 without any problems after Samsung fixed the initial bugs.
You should not encounter any problems copying files from your FAT32 card to your PC and then copying them back to an exFat card. I have done that several times.
Click to expand...
Click to collapse
Ahh, this again. Since Ubuntu doesn't read exFat, you'll understand my reluctance to reformat.
blackknightavalon said:
Ahh, this again. Since Ubuntu doesn't read exFat, you'll understand my reluctance to reformat.
Click to expand...
Click to collapse
I just googled "ubuntu exfat" and came up with more than a dozen websites with instructions on how to install and use exfat on Ubuntu.
Good luck...
I have done exactly what the OP mentioned - with 32 GB SD card. I copied all files to my computer, formatted the SD card from its original FAT-32 to exFAT, using an SD-card adapter. With quick format that only takes 2 seconds. Then copied all files back to the card, stuck it in my Galaxy S4 (Build VRUEMJ7, if that's important). And it works fine - all the files are readable on the phone - music, video, .doc, .xls, .ppt. , mp3 , No problems.
TWRP recovery has support for ExFAT since v2.4.0.0.
hey all,
i have a generic 64GB class 10 micro SD card and am trying to use it with HTC Desire HD running CM7 last nightly version. sd card came in exFAT format, which apparently only few phones support. I have reformatted it to FAT32, but learned that max size for it is 32GB. however it still mounted and appeared.
my problem is when using camera to record video, about 30 secs in i get message saying 'please insert sd card before using camera'. this dismounts the sd. thats the guaranteed way of testing. also sometimes when downloading big files from market, it also dismounts. seems any major writing to card does that. otherwise it seems to work properly. is there any way of fixing this?
so far i have tried:
using phone and computer
-reformat to FAT32
using MiniTool Partition Wizard Home Edition
- making 2 partitions FAT32, 32GB each
- making 1 big FAT32 partition, 1 small ex4
- making 1 big FAT32, 1 smaller ex4, 1 smaller swap partition, then using link2SD to build mount script.
any help would be helpful
thanks
dovy said:
hey all,
i have a generic 64GB class 10 micro SD card and am trying to use it with HTC Desire HD running CM7 last nightly version. sd card came in exFAT format, which apparently only few phones support. I have reformatted it to FAT32, but learned that max size for it is 32GB. however it still mounted and appeared.
my problem is when using camera to record video, about 30 secs in i get message saying 'please insert sd card before using camera'. this dismounts the sd. thats the guaranteed way of testing. also sometimes when downloading big files from market, it also dismounts. seems any major writing to card does that. otherwise it seems to work properly. is there any way of fixing this?
so far i have tried:
using phone and computer
-reformat to FAT32
using MiniTool Partition Wizard Home Edition
- making 2 partitions FAT32, 32GB each
- making 1 big FAT32 partition, 1 small ex4
- making 1 big FAT32, 1 smaller ex4, 1 smaller swap partition, then using link2SD to build mount script.
any help would be helpful
thanks
Click to expand...
Click to collapse
As far as i remember, Our device supports Max 32GB, above that should work as a card reader but won't give you functionality like you suppose to expect from 16 or 32GB of micro-sd card.
Advice to change MicroSD to some what 16/32 GB and even if that doesn't work then try changing rom itself.