(the following is all with stock rom, rooted, no otg helper apps involved. 16gb TF card in a usb multi-sd-reader-thing.)
first of all, I finally had the good sense to notice that vold.fstab lists all the external usb mounts (UsbDriveA, UsbDriveB, etc.) and specifies that they ONLY support exfat. which, given that my fat32 sticks worked ok, I suppose implies that exfat is a superset of fat.
so, ok, some experiments:
- single fat32 partition - ok. automounts.
- single exfat partition - ok. automounts.
- single ntfs partition - fail. "blank card." also, no built-in ntfs .ko or ntfs3g/fuse, so cannot mount from CLI. but fdisk recognizes partition as hpfs/ntfs.
- single ext2/ext3/ext4 partition - fail. "blank card." but
$ su
# mkdir /sdcard/foo
# mount /dev/block/sdb1 /sdcard/foo
works fine. i.e. messing around with supported filesystems in one's vold.fstab, would likely fix this.
- 2 fat32 partitions - partial. first partition automounts, second partition does not.
at this point I got bored so did not try e.g. mixing fat32 ntfs and extfs partitions together.
it seems we are supposed to be satisfied with single partition fat devices, exfat apparently superseding vfat, fat32 still supported. I did not test fat16 but I'm guessing that'll probably work as well.
which is probably most of the target market, and to be honest that isn't exactly unreasonable. and at least we do have the helper apps that pick up the slack when needed.
I do wonder how CM deals with this - although my thought it is really more a function of the specific kernel and/or if you have some kind of fuse support installed. (and again, having a less-ignorant vold.fstab configuration)
so your saying i can pair my ps3 controller?
We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.