When i tried to download 6gb movie today the torrent application said that android doesn't support files larger than 4gb at the moment.
I believe this was the case with the fat32 file system, but i'm with galaxy nexus with 16GB build in memory, so i find it hard to believe it's still with the archaic fat32? Actually what's it's file system and if the reason is somewhere else can it be fixed?
Fking1 said:
When i tried to download 6gb movie today the torrent application said that android doesn't support files larger than 4gb at the moment.
I believe this was the case with the fat32 file system, but i'm with galaxy nexus with 16GB build in memory, so i find it hard to believe it's still with the archaic fat32? Actually what's it's file system and if the reason is somewhere else can it be fixed?
Click to expand...
Click to collapse
Im just guessing here but the files are saved to your memory card. So if thats FAT32 then yeah 4GB would be your limit, you should check that first I guess
It depends entirely on the file system used on the SD card. Most SD cards are formatted Fat32, which has a file size limit of 4GB. However, on Galaxy Nexus, I believe the "SD card" is using ext3, which has a file size limitation 16GB (when using 1KB blocks). I can say with absolutely certainty that I have copied over files as large as 9GB to my Galaxy Nexus successfully.
The file system is ext4, the 'sdcard' is virtual - it's a directory on the main partition, not a seperate partition (that's why UMS isn't supported).
AFAIK no flavour of linux or unix uses fat32.
Dunno why your system won't let you go over 4Gb, it may be an error in your torrent app, or maybe its setup assumes all sdcards are fat32 and isn't actually checking...
Yeah that seems to be the most logical reason, thank you guys for the input.
Why did that thread stop there? I need to know which torrent client you are using lol. If it's the torrent client then try other ones right? Why are you currently using?
Also, i heard that changing the kernel might be the solution to the problem if it really isn't the torrent client. I wish i could elaborate more but i unfortunately don't understand what it does per say
Related
I'm trying to copy .rar files to my phone over 4gigs and instead of using a dvd I'd like to put it on either my SD card or my phone storage. I have a 16 gig SD card with over 12 gigs free. I know I can convert it from fat32 with win7 so I'm not worried about that. I just need to know if he phone will support ntfs. I've searched online and can't seem to find a definitive answer... any help would be greatly appreciated!!
I apologize if this is in the wrong category I wasn't sure where to post this.
Sent from my ADR6300 using XDA App
Ysosrslawl said:
I'm trying to copy .rar files to my phone over 4gigs and instead of using a dvd I'd like to put it on either my SD card or my phone storage. I have a 16 gig SD card with over 12 gigs free. I know I can convert it from fat32 with win7 so I'm not worried about that. I just need to know if he phone will support ntfs. I've searched online and can't seem to find a definitive answer... any help would be greatly appreciated!!
I apologize if this is in the wrong category I wasn't sure where to post this.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
These phones don't support ntfs filesystems yet. Why would you want to use ntfs on a primarily storage drive anyways?
I like to transport sometimes large files via my cell phone. Or in the event that another storage device isn't working I can use this quickly and temporarily.
Sent from my ADR6300 using XDA App
NTFS isnt really any faster than fat32, its more of a security encryption issue and its not like fat32 doesnt support large file transfers. Plus i dont know of any device that doesnt recognize fat32.
Partitioning could be an option right? One partition in FAT32 for the phone and one in NTFS for file transfers.
Sent from my ADR6300 using XDA App
Since your transfering .rars I'm assuming your already use to using WinRar or a similar archiving tool, would it be out of the question to use it to split the file into pieces small enough to be compatible with a Fat32 formatted card?
Ok since i have hdmi out on my galaxy nexus i tried downloading some 720p movies to it. The download for the 3 and 6gb ones didn't even started (aTorrent), the only one i managed to download and save was under 1gb.
Are there some limitations of the file system or other problem with big files?
Fking1 said:
Ok since i have hdmi out on my galaxy nexus i tried downloading some 720p movies to it. The download for the 3 and 6gb ones didn't even started (aTorrent), the only one i managed to download and save was under 1gb.
Are there some limitations of the file system or other problem with big files?
Click to expand...
Click to collapse
I may be wrong, I believe the phone has an ext3 disk format, which means the max file size is 16GB. If it's ext4, then you could fill the entire user partition with one file and be (theoretically) fine.
I suggest you sideload the file from a PC rather than directly OTA. Either your torrent app can't handle something this big, or something is timing out.
I dont know about downloading, but i have sideloaded a 4gb movie on it, plays fine.
ATnTdude said:
I may be wrong, I believe the phone has an ext3 disk format, which means the max file size is 16GB. If it's ext4, then you could fill the entire user partition with one file and be (theoretically) fine.
Click to expand...
Click to collapse
As I understand it it's ext 4, but since the free space on a brand new phone is 11.3Gb that's probably irrelevant.
So I got a great deal on a class 10 32GB Samsung card, it came pre-formatted to fat32, however I had the wild idea that android supported NTFS based on something I read in the past so I formatted it to NTFS on a windows system and copied some files over (some being over 5GB each)...plugged in my card and turned on my phone and I get a message saying my card is blank or the wrong file format...guess it doesn't support NTFS
I know if I use the phones built in format utility it will format to fat32 which I don't really want because of the filesize limitation, I'd like to be able to copy 8-10GB files every so often so I can use my phone as a little shuttle drive in between places...
But I also want the ability for windows to be able to read my sd card if I change my phone into USB mode so I think that excludes the ext3, ext4 format which I think android will read...
Any ideas?
Won't happen search and you will find threads on this before
You will also find a Q&A section that this belongs in
Sent from my SPH-D710 using Tapatalk
There's an app in the market that will mount any file formatted sdcard in the device I but I haven't used it out remember the name but you can check it and yes this belongs in Q&A but The way you format is fat 32
Touched by an Epic 4G w/Cm9 & Fueled by the NY Giants 2012
Got that Newegg deal as well! Can't wait for it to arrive. Interested in the answer as well as I hope to put some high quality movies there.
Sent from my badass Samsung Galaxy Tab 10.1.
So I found an ntfs app in the market that'll mount ntfs at startup but I gotta root for it work. Guess I now have a reason to root
Oh but it says it was made for the galaxy tab...but it opens fine on my s ii
Sent from my SPH-D710 using the XDA mobile application powered by Tapatalk
btw where is the Q&A section i should be looking for? xda has gotten so huge i'm lost at least i can find the e4gt forum
maybe i should change the title of my thread to what filesystems can i format my sd card to that my phone will read?
if you use windows, fat32 is the way to go so then you can connect the phone to computer and still can access the files
t0mmyr said:
btw where is the Q&A section i should be looking for? xda has gotten so huge i'm lost at least i can find the e4gt forum
maybe i should change the title of my thread to what filesystems can i format my sd card to that my phone will read?
Click to expand...
Click to collapse
There is a Q&A section right under general in the epic touch
Sent from my SPH-D710 using Tapatalk
charles98 said:
if you use windows, fat32 is the way to go so then you can connect the phone to computer and still can access the files
Click to expand...
Click to collapse
The reason the op doesn't want fat32 is because he has single files that exceeds 4 GB that he wants to transfer, so fat32 would not work for him.
im0rtalz said:
The reason the op doesn't want fat32 is because he has single files that exceeds 4 GB that he wants to transfer, so fat32 would not work for him.
Click to expand...
Click to collapse
maybe drive mount in market but lots of bad reviews....May work don't know
Sent from my SPH-D710 using Tapatalk
Windows also recognized NTFS by the way.
out of curiosity, does anyone know if any custom roms support ntfs sd cards nativey?
t0mmyr said:
out of curiosity, does anyone know if any custom roms support ntfs sd cards nativey?
Click to expand...
Click to collapse
None because Android does not.....
Sent from my SPH-D710 using Tapatalk
format it ext3/4 and then install an ftp server app on your phone.
There is an app that works fine
I have exactly the same problem. I want to have the sdcard in NTFS so then I do not have the 4GB limitation of FAT32. The is possible to have .mkv files on your phone or tablet.
In the case of my table the N8010, I have formatted the sd card on Windows with NTFS. Then installed the "paragon" app from market which works very good. It recognized the sd card in NTFS and mount perfectly. But it seems that when your card is overloaded with thounsands of files and some big 6GB file, then comes the problem. Android JB everytime that comes out of sleep, it will check for errors the sd card. Everytime! Then, I get the message "sd card checking for errors" and never gets back. The sd card is not recognized anymore until I reboot the device.
I think that the paragon app is not perfect and might have bugs, but
Is there any way to disable the "sd card check for error" functionality? Have read some threads about it, to delete some file from system, but that method produces inconsistencies with other apps.
By the way, I have tried to format on ExFat, and had the same problem. When the card is almost full it will never end up checking for errors. I finally broke the sd card when I formated it with ExFat and 64k allocation size. It was not regoznized neither by windows and android afterwards
thanks
cla20000 said:
By the way, I have tried to format on ExFat, and had the same problem. When the card is almost full it will never end up checking for errors. I finally broke the sd card when I formated it with ExFat and 64k allocation size. It was not regoznized neither by windows and android afterwards
thanks
Click to expand...
Click to collapse
I don't think you broke it unless you fried the flash chips. You can try using the disk manager in windows and try to see if it sees it. Or just learn how to use Linux command line tools and fix it that way. I recovered 80% of my pictures off of a dead SD card using dd and a file recovery utility. I don't recall which one. That 16GB SD card now works just fine as a 12GB card. I don't trust it for any more than shuttling between systems though.
Also, I've never had good luck with exFAT. I much prefer the EXT filesystems, but they aren't natively supported in windows or most cameras. Maybe try NTFS without journaling (If that's even possible)
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
exfat is proprietary windows and needs licenses. android won't support it.
ntfs is a journaling file system and will impact performance if you can get android to read it.
ext2/3 is the best solution. there are utilities you can install so windows can read it.
calisro said:
exfat is proprietary windows and needs licenses. android won't support it.
ntfs is a journaling file system and will impact performance if you can get android to read it.
ext2/3 is the best solution. there are utilities you can install so windows can read it.
Click to expand...
Click to collapse
Ext2Fsd is excellent for Windows 7, I don't know what I'd do without it.
sent from my ET4G on Paranoid Android using XDA Premium HD in hybrid mode
I flashed the
[ROM] AOKP(Jellybean & ICS) Task & Ktoonsez Run a Train(8/13)(TGFY ONLINE!!! also tried [ROM][OFFICIAL] CyanogenMod 10 Preview Builds for SGH-I747 (08/10)
Today. I have a 64gb sdxc card and it's reading "Damaged card". Is this a common fix and does it have any fix?
Hope my sd card didn't get damaged...
Thanks,
Satya
You need to format it in FAT32 with EaseUS or something else...
I had the same thing happen (exfat 64G card corrupted by the attempted mount under AOKP/CM10) - really irritating. Someone claimed the card would still mount under Recovery and they could pull the contents using adb, but I had no luck with this and had to reformat (but fortunately I could reconstruct the contents). fat32 is limited to 4G file size so I stuck with exfat under a Sammy-based rom (Wanam), at least until exfat support is sorted out under CM10.
plaut said:
I had the same thing happen (exfat 64G card corrupted by the attempted mount under AOKP/CM10) - really irritating. Someone claimed the card would still mount under Recovery and they could pull the contents using adb, but I had no luck with this and had to reformat (but fortunately I could reconstruct the contents). fat32 is limited to 4G file size so I stuck with exfat under a Sammy-based rom (Wanam), at least until exfat support is sorted out under CM10.
Click to expand...
Click to collapse
FAT32 is NOT limited to 4g in size, which is why EaseUS is recommended...
BNaughty said:
FAT32 is NOT limited to 4g in size, which is why EaseUS is recommended...
Click to expand...
Click to collapse
Unless you're talking about a particular extension of FAT32 (e.g., FAT+), the maximum size of a single file is 4GB - 1 byte. The entire volume can be much larger, of course (up to 16 TB with 4096 byte sectors).
plaut said:
Unless you're talking about a particular extension of FAT32 (e.g., FAT+), the maximum size of a single file is 4GB - 1 byte. The entire volume can be much larger, of course (up to 16 TB with 4096 byte sectors).
Click to expand...
Click to collapse
Then I misread what you said, i apologize... you're right 4g file size...
I can't figure out how to get around the 4GB file size restriction on the Pixel 3. I never had any problems using an exFAT file system on external hard drives/USB drives on previous phones.
It seems that if I attempt to use exFAT or NTFS file systems on my drives, the Pixel will not recognize it, format it back to FAT32, and I'm back at square one.
I've tried to wirelessly transfer files from PC to phone through Portal, using the external drive as the storage device, but that didn't work either.
double0psycho said:
I can't figure out how to get around the 4GB file size restriction on the Pixel 3. I never had any problems using an exFAT file system on external hard drives/USB drives on previous phones.
It seems that if I attempt to use exFAT or NTFS file systems on my drives, the Pixel will not recognize it, format it back to FAT32, and I'm back at square one.
I've tried to wirelessly transfer files from PC to phone through Portal, using the external drive as the storage device, but that didn't work either.
Click to expand...
Click to collapse
??? I have a 128 gb USB c thumb drive formatted fat32. It's working fine on my pixel 3.
Sent from my [device_name] using XDA-Developers Legacy app
I can get FAT32 to work. But FAT32 limits file sizes to less than 4GB. I'm trying to have larger movie files on a USB drive to watch on a long trip. Can't put them on a FAT32 formatted drive because they're way too large. And Pixel doesn't support exFAT or NTFS.
I'm trying to find a way around this, unless I really just have to resort to splitting all of the files into smaller segments. Was hoping not to have to do that though.
double0psycho said:
I can get FAT32 to work. But FAT32 limits file sizes to less than 4GB. I'm trying to have larger movie files on a USB drive to watch on a long trip. Can't put them on a FAT32 formatted drive because they're way too small. And Pixel doesn't support exFAT or NTFS.
I'm trying to find a way around this, unless I really just have to resort to splitting all of the files into smaller segments. Was hoping not to have to do that though.
Click to expand...
Click to collapse
Windows artificially limits fat32 to 32 gb so if that's all you need it should format it fine. If you need more there are 3rd party apps or you can do it in a windows power shell running as administrator. In a power shell use format /FS:FAT32 X:. Where X: is the drive letter of the device you're formatting.
Edit, you know what. I miss understood your question. I was thinking partition size not file size. Sorry about that.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Windows artificially limits fat32 to 32 gb so if that's all you need it should format it fine. If you need more there are 3rd party apps or you can do it in a windows power shell running as administrator. In a power shell use format /FS:FAT32 X:. Where X: is the drive letter of the device you're formatting.
Edit, you know what. I miss understood your question. I was thinking partition size not file size. Sorry about that.
Click to expand...
Click to collapse
Yeah, realized I said small when I meant the file sizes are too large. Either way, I'm hoping to find a way to get my pixel to be able to "see" some 8GB or larger files on an external storage device. I've used a couple apps that said they allow read/write NTFS and exFAT file systems, but none have really worked.
I'm just passing through, I don't own a pixel. But normally you need a kernel that supports either ntfs or exfat or both. I saw there are 2 kernels in the development section. Have you tried those?
double0psycho said:
I can't figure out how to get around the 4GB file size restriction on the Pixel 3. I never had any problems using an exFAT file system on external hard drives/USB drives on previous phones.
It seems that if I attempt to use exFAT or NTFS file systems on my drives, the Pixel will not recognize it, format it back to FAT32, and I'm back at square one.
I've tried to wirelessly transfer files from PC to phone through Portal, using the external drive as the storage device, but that didn't work either.
Click to expand...
Click to collapse
FAT32 and exFAT are not the same type of filesystem.
double0psycho said:
I can get FAT32 to work. But FAT32 limits file sizes to less than 4GB. I'm trying to have larger movie files on a USB drive to watch on a long trip. Can't put them on a FAT32 formatted drive because they're way too large. And Pixel doesn't support exFAT or NTFS.
I'm trying to find a way around this, unless I really just have to resort to splitting all of the files into smaller segments. Was hoping not to have to do that though.
Click to expand...
Click to collapse
FAT32 is working as it should be.
jd1639 said:
Windows artificially limits fat32 to 32 gb so if that's all you need it should format it fine. If you need more there are 3rd party apps or you can do it in a windows power shell running as administrator. In a power shell use format /FS:FAT32 X:. Where X: is the drive letter of the device you're formatting.
Edit, you know what. I miss understood your question. I was thinking partition size not file size. Sorry about that.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
It is not an "artificial" limit. This is how FAT32 was designed to work.
double0psycho said:
Yeah, realized I said small when I meant the file sizes are too large. Either way, I'm hoping to find a way to get my pixel to be able to "see" some 8GB or larger files on an external storage device. I've used a couple apps that said they allow read/write NTFS and exFAT file systems, but none have really worked.
Click to expand...
Click to collapse
Those apps never work without root. Even with root, they're still finicky.
[Cruzer] said:
I'm just passing through, I don't own a pixel. But normally you need a kernel that supports either ntfs or exfat or both. I saw there are 2 kernels in the development section. Have you tried those?
Click to expand...
Click to collapse
As stated here, a custom kernel with exFAT support is your best option.
Please read up on filesystems here.
Sent from my Pixel 3 XL using Tapatalk
bxlegend said:
FAT32 and exFAT are not the same type of filesystem.
It is not an "artificial" limit. This is how FAT32 was designed to work.
k
Click to expand...
Click to collapse
I agree to a point. It was designed to work that way since Microsoft is pushing NTFS for larger partitions. You can certainly have FAT32 partitions larger than 32 gb.
jd1639 said:
I agree to a point. It was designed to work that way since Microsoft is pushing NTFS for larger partitions. You can certainly have FAT32 partitions larger than 32 gb.
Click to expand...
Click to collapse
Let's be careful here because you're confusing file size with partition size. Microsoft is not "pushing" one filesystem over another. The FAT32 filesystem had too many limits for servers which is why Microsoft introduced NTFS. As consumer needs grew, NTFS was made the default for Windows filesystem. The same applies to removable flash storage. To get consumers and manufacturers away from FAT32, Microsoft created exFAT. Microsoft, Apple, and Google are all competitors and they all have default supported filesystems. Microsoft and Apple user proprietary filesystems while Google sticks with open source since it's patent free. Which is why Pixel phones do not support Microsoft and Apple filesystems by default.
Sent from my Pixel 3 XL using Tapatalk
double0psycho said:
I can't figure out how to get around the 4GB file size restriction on the Pixel 3. I never had any problems using an exFAT file system on external hard drives/USB drives on previous phones.
It seems that if I attempt to use exFAT or NTFS file systems on my drives, the Pixel will not recognize it, format it back to FAT32, and I'm back at square one.
I've tried to wirelessly transfer files from PC to phone through Portal, using the external drive as the storage device, but that didn't work either.
Click to expand...
Click to collapse
There are a couple of apps that allow accessing exFAT and NTFS file systems via OTG. Here's one I've used:
https://mixplorer.en.uptodown.com/android
It also allows accessing the files directly, so a slow copy to the phone isn't required for say playing a movie.