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?
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
Hello,
There is anyone with sdcard with 32GB classe 10 formated on ntsf working?
Thanks
Sent from my GT-I9100 using Tapatalk
Or any sdcard on ntfs filesystems working?
Sent from my GT-I9100 using Tapatalk
Has to be fat32 android doesn't use NTFS format as far as I'm aware.
Sent from my Htc Hd2 using XDA Premium HD app
Ok. Thanks
Sent from my GT-I9100 using Tapatalk
Yes and No -- NTFS
Yep, I'm having the same trouble with my 64GB NTFS sd card with this G-Pad. On the other hand, I can assure you that NTFS formatted cards will work with Android. I've been using my 64-GB NTFS sdCard in my Sasmung Tab 3 8" for the last 4 months with no problem (CM11 4.4.2 the entire time). The card became corrupted a couple months back and I chose to reformat in NTFS and it hasn't had a single problem until I just bought his G Pad. I can reformat it - I just need to find out which way is the best.
b3aucb said:
Yep, I'm having the same trouble with my 64GB NTFS sd card with this G-Pad. On the other hand, I can assure you that NTFS formatted cards will work with Android. I've been using my 64-GB NTFS sdCard in my Sasmung Tab 3 8" for the last 4 months with no problem (CM11 4.4.2 the entire time). The card became corrupted a couple months back and I chose to reformat in NTFS and it hasn't had a single problem until I just bought his G Pad. I can reformat it - I just need to find out which way is the best.
Click to expand...
Click to collapse
Like you said, you used CM, which has root and drivers to read NTFS cards. In G Pad, you have three options: install CM, root G Pad or format in exfat.
NTFS - exFAT
I have the same problem NTFS or exFAT do not work: (I have slimkat Rom 4.4.2 but unfortunately, one form of which we are going sou Fat16 Fat32: (
Edit : helped change the kernal?
NTFS is not enabled in the kernel for the GPad gpe, and so probably not in the other versions either. There is limited support by default in the kernels for NTFS, allowing only read, and not write access, and limited file sizes as well. Therefore no point in enabled it for our device without adding code to the kernel.
The 64 gig Sandisk card has issues with exfat. Google to find out why, or search in these threads to learn more. Fat32 works fine on every card and should be your go-to default partition type.
There are kernels associated with different Roms or devices which support NTFS.
Ditched NTFS for exFAT
boy_pt said:
Like you said, you used CM, which has root and drivers to read NTFS cards. In G Pad, you have three options: install CM, root G Pad or format in exfat.
Click to expand...
Click to collapse
Ahh. I gotcha. I temporarily dumped 40GB of SD contents onto my PC, reformatted the card as exFAT, and the stock G Pad picked up my 64GB Samsung SD perfectly. Thanks.
OK my problem is I have the tab 3 10.1 with a 64gb micro SD card in it and the only way to root is to put a smaller SD card in because for some reason it can't read the 64gb micro SD card and when I want to make a backup in cwm it says it can't mount the 64gb micro SD card but if I use anything smaller everything works fine so my question is, is there a work around or some way to Make my tab 3 mount the micro SD because I'd like to install other roms and stuff but I'm not going to I till I can make a backup first. Also with the 64gb card in my tab 3 everything else works like watching videos stored on the SD or music on the SD, anyways any help with this issue would be much appreciated.
Sent from my GT-P5210 using xda app-developers app
you MIGHT have better luck if you format the SD card in some other file system. Other than that I'm not sure
You could buy an 8 gig one and swap it too
DopeShow said:
OK my problem is I have the tab 3 10.1 with a 64gb micro SD card in it and the only way to root is to put a smaller SD card in because for some reason it can't read the 64gb micro SD card and when I want to make a backup in cwm it says it can't mount the 64gb micro SD card but if I use anything smaller everything works fine so my question is, is there a work around or some way to Make my tab 3 mount the micro SD because I'd like to install other roms and stuff but I'm not going to I till I can make a backup first. Also with the 64gb card in my tab 3 everything else works like watching videos stored on the SD or music on the SD, anyways any help with this issue would be much appreciated.
Sent from my GT-P5210 using xda app-developers app
Click to expand...
Click to collapse
Have you tried both recoveries? CWM and TWRP if neither work you may have to format to fat32.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Yes I've tried every recovery out there and with cwm it does this count down from 10 that says connecting then after it gets to 1 it says aborted because it cannot mount the micro SD and yes its formated to fat32 and I've tried exfat and every other format nothing works, and in my first post when I said I couldn't root from the micro SD I mean by going into cwm and loading zip file from there it does the same thing and says it can't connect, that's why everytime I root my device this way I have to borrow a 32gb micro SD and everything works fine
Sent from my GT-P5210 using xda app-developers app
Same problem with my 64g card. MY 16g works great. Cant seem to get the 64g formatted in either my phone or the Tab3. I can sometimes get the Tab3 to recognize the card and it will show the files on the memory card but once I go into recovery there is nothing there.
My 64gb card is recognized while the device is in regular running mode like I can go into settings and then storage and see the card there and how much space is used and free the Only time the card doesn't work right is when I'm in recovery mode because for some reason in recovery mode the system says it can't mount it and that is my whole problem, I need a way to fix it so my 64gb card can be mounted and used while in recovery mode.
Sent from my GT-P5210 using xda app-developers app
It's either a recovery issue or a driver/kernel/bootloader issue, a case that the Tab 3 10.1 development is far from being active.
It looks like it can't allocate space that exceeds 32GiB.
Also wrong thread.
Trying formating your SD card on the computer to fat32 or extfat .
Sent from my GT-I9505 using XDA Premium 4 mobile app
I've already done that and the card works fine example in the device it only stops working in cwm recovery saying it can't be mounted
Sent from my GT-P5210 using XDA Premium ANDROID Developer's App
Thread cleaned of off topic posting and unnecessary non-related junk.
(yes, we can do this)
Any more silly ridiculous junk posted, and this thread will be closed permanently.
If the OP wants to keep this in open forums, we cannot prevent this and welcome the debate, as it seems fitting.
Cheers
MD
My thoughts...
Running the tab in normal mode allows the 64gb card to be read. However, if you start in CWM or TWRP recovery, you are no longer in the "normal" mode and the tab does not recognize the 64gb card. In recovery mode, it is possible that the memory allocations are limited where as in normal mode, 64gb is OK.
In this case, for rooting, maybe you should load the root file on internal memory and not the memory card. I use 4gb cards and neither CWM or TWRP could work with them. I think the issue is in the recovery programs and not the Tab, save for memory limitations set by the base firmware.
Again, JMHO and I may be way out in left field here.
TWRP after 2.4 supports exfat. What version are you using? Many people have posted that TWRP 2.7.0.0 has hosed sd support and people have posted earlier versions like 2.6.*.* and now 2.7.0.1 work fine. I'm guessing you've were trying a broken version.
Your phone is a computer running the linux operating system. Hardware works by way of software called drivers that allow the system to communicate with various devices like drives and radios. The drivers in linux are built into the kernel which is the heart of the system or they are loaded as modules. When building a kernel you can add or subtract any number of various drivers you may or may not need into the system. The stock Samsung kernel has the various file system (fat32, exfat, ext3, etc) drivers built into it and that's why your sd card is recognized and works fine within the Samsung custom Android operating system you're running. TWRP and other recovery systems are bare bones operating systems that you load in order to perform maintenance functions like loading firmware or running backups. When the devs for TWRP compiled their kernel (processed all the changes to their new kernel and made it ready to operate) for version 2.7.0.0 they screwed up by either leaving out support for cards of a certain size, file systems of a certain size, support for certain filesystems or used experimental buggy drivers. This is why your card doesnt work in recovery.
You should try a different version of the recovery you desire. You might also want to try formatting the sdcard as another filesystem like ext4. The CWM thread for your tablet forum.xda-developers.com/showthread.php?t=2432467 says that 64gb support is very buggy and that CWM is not being worked on anymore for your device. Some people say it works for them though. Page 1 of the TWRP thread for your device (which is final on version 2.7 which may mean his last build killed 64gb support) mentions earlier versions working with 64gb cards. You may want to ask people posting early in the thread if they have an early version they could upload for you.
If you own a mac or linux system or burn a linux cd( ubuntu live cd) you could format your 64gb microsd as ext3 or ext4 and it should have no issue unless it's a problem with the capacity of the microsd in which case you could try to create one partition on the microsd card of say 25gb. That could work if partition size and not disk capacity is the problem.
Those seem to be your options along with just buying a 32gb, 16gb, 8gb, 4gb, 2gb card to root with. Memory is getting cheaper and images to flash ROMs and recoveries are generally small. You could probably buy one in your local drug store for $5. If money isn't tight, there's your easiest solution. You could borrow a smaller card from someone too if money is tight. They are pretty common in phones going back 6 years now. If you want to learn more about your phone and get hands on experience try another method above.
Good luck. Hope you get it going.
GorillaPimp said:
TWRP after 2.4 supports exfat. What version are you using? Many people have posted that TWRP 2.7.0.0 has hosed sd support and people have posted earlier versions like 2.6.*.* and now 2.7.0.1 work fine. I'm guessing you've were trying a broken version.
Your phone is a computer running the linux operating system. Hardware works by way of software called drivers that allow the system to communicate with various devices like drives and radios. The drivers in linux are built into the kernel which is the heart of the system or they are loaded as modules. When building a kernel you can add or subtract any number of various drivers you may or may not need into the system. The stock Samsung kernel has the various file system (fat32, exfat, ext3, etc) drivers built into it and that's why your sd card is recognized and works fine within the Samsung custom Android operating system you're running. TWRP and other recovery systems are bare bones operating systems that you load in order to perform maintenance functions like loading firmware or running backups. When the devs for TWRP compiled their kernel (processed all the changes to their new kernel and made it ready to operate) for version 2.7.0.0 they screwed up by either leaving out support for cards of a certain size, file systems of a certain size, support for certain filesystems or used experimental buggy drivers. This is why your card doesnt work in recovery.
You should try a different version of the recovery you desire. You might also want to try formatting the sdcard as another filesystem like ext4. The CWM thread for your tablet forum.xda-developers.com/showthread.php?t=2432467 says that 64gb support is very buggy and that CWM is not being worked on anymore for your device. Some people say it works for them though. Page 1 of the TWRP thread for your device (which is final on version 2.7 which may mean his last build killed 64gb support) mentions earlier versions working with 64gb cards. You may want to ask people posting early in the thread if they have an early version they could upload for you.
If you own a mac or linux system or burn a linux cd( ubuntu live cd) you could format your 64gb microsd as ext3 or ext4 and it should have no issue unless it's a problem with the capacity of the microsd in which case you could try to create one partition on the microsd card of say 25gb. That could work if partition size and not disk capacity is the problem.
Those seem to be your options along with just buying a 32gb, 16gb, 8gb, 4gb, 2gb card to root with. Memory is getting cheaper and images to flash ROMs and recoveries are generally small. You could probably buy one in your local drug store for $5. If money isn't tight, there's your easiest solution. You could borrow a smaller card from someone too if money is tight. They are pretty common in phones going back 6 years now. If you want to learn more about your phone and get hands on experience try another method above.
Good luck. Hope you get it going.
Click to expand...
Click to collapse
yes ive tried multiple recovery's and they all do the same thing and cannot read the 64gb micro sd and yes I have my sd formatted to fat32 and I am on windows on my laptop but I can format the micro sd to ext3 or 4 but my question is, if I do that and its formatted to ext3 will I still be able to access my tablets drive space through my laptop like I can now with it being on fat32, because if I cant then that would be pointless for me to do because then I wouldn't be able to add and take things off my sd while its in my tablet., also I said in my first post that this problem doesn't happen using a smaller micro sd like 32 or smaller it only happens with the 64gb, so it has to do with the size some how
GorillaPimp said:
TWRP after 2.4 supports exfat. What version are you using? Many people have posted that TWRP 2.7.0.0 has hosed sd support and people have posted earlier versions like 2.6.*.* and now 2.7.0.1 work fine. I'm guessing you've were trying a broken version.
Your phone is a computer running the linux operating system. Hardware works by way of software called drivers that allow the system to communicate with various devices like drives and radios. The drivers in linux are built into the kernel which is the heart of the system or they are loaded as modules. When building a kernel you can add or subtract any number of various drivers you may or may not need into the system. The stock Samsung kernel has the various file system (fat32, exfat, ext3, etc) drivers built into it and that's why your sd card is recognized and works fine within the Samsung custom Android operating system you're running. TWRP and other recovery systems are bare bones operating systems that you load in order to perform maintenance functions like loading firmware or running backups. When the devs for TWRP compiled their kernel (processed all the changes to their new kernel and made it ready to operate) for version 2.7.0.0 they screwed up by either leaving out support for cards of a certain size, file systems of a certain size, support for certain filesystems or used experimental buggy drivers. This is why your card doesnt work in recovery.
You should try a different version of the recovery you desire. You might also want to try formatting the sdcard as another filesystem like ext4. The CWM thread for your tablet forum.xda-developers.com/showthread.php?t=2432467 says that 64gb support is very buggy and that CWM is not being worked on anymore for your device. Some people say it works for them though. Page 1 of the TWRP thread for your device (which is final on version 2.7 which may mean his last build killed 64gb support) mentions earlier versions working with 64gb cards. You may want to ask people posting early in the thread if they have an early version they could upload for you.
If you own a mac or linux system or burn a linux cd( ubuntu live cd) you could format your 64gb microsd as ext3 or ext4 and it should have no issue unless it's a problem with the capacity of the microsd in which case you could try to create one partition on the microsd card of say 25gb. That could work if partition size and not disk capacity is the problem.
Those seem to be your options along with just buying a 32gb, 16gb, 8gb, 4gb, 2gb card to root with. Memory is getting cheaper and images to flash ROMs and recoveries are generally small. You could probably buy one in your local drug store for $5. If money isn't tight, there's your easiest solution. You could borrow a smaller card from someone too if money is tight. They are pretty common in phones going back 6 years now. If you want to learn more about your phone and get hands on experience try another method above.
Good luck. Hope you get it going.
Click to expand...
Click to collapse
also IDK if you know this but there isn't many recovery's out there for the galaxy tab 3 10.1 the only one I use is bindroid_cwm_p5210_santos10wifi and even with this recovery it has a slight lag to it when using it.
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.