Related
In short:
Is there a thread somewhere stating the pro's and con's of running Android from different types of "media" (SD, NAND, EXT2)?
If there is, please provide a link, I can't seem to find anything that isn't an unanswered question or small comments.
If there isn't, let this be a starting point for those looking for the answer to this question.
Longer:
I've seen this question pop up once and again but it might be that the topic is totally exhausted and people have stopped commenting on it. I can't seem to find an answer though; What are the pro's and con's of using NAND, EXT2, FAT32 or any combination of it?
I see a couple of installation alternatives and some I have been able to conclude myself but others not.
* Running from SD-card using HaRET
This option is the slowest in terms of Android performance. It has the added value of easily getting back to Windows Mobile by rebooting the phone, gaining easy access to the SD card and manipulation options.
* Running the system AND data on NAND
This option has in my view the fastest Android experience. Access to files on the SD card is a bit more cumbersome (there is the SD card split widget APK available but I have yet to see it working) and access to files for manipulation I can't comment on (haven't gotten to that yet).
* Running the system from NAND and data on EXT2
The performance seems almost as fast as the system+data on NAND. I have no idea about the added value of running anything from an EXT2-partition in the SD card but I'm guessing it will be slower. I have no idea if file access for manipulation is easier or not compared to the other options.
* Running the system AND data from EXT2
I have not tried this yet and cannot comment on it. Something tells me it will be slower than NAND because of SD card overhead.
* Running the system from EXT2 and data on NAND
I have not tried this yet and cannot comment on it.
Now, I've missed out on several of the installation options but I'll edit this post as soon as I get to investigating it further.
Any comments/experience/knowledge in this is greatly appreciated, as it can make things clearer as to what options to choose.
Well these are very good question and wanted to start a thread on this matter as well. I also could not find a strait answer anywhere.
I also want to know if there is an advantage using ext2 over fat32.
So, people out there having knowledge about this matter please share it.
Ext2 and Fat32 are both types of filesystem used on various different types of media, including SD card, Hard drives etc.
EXT2 is (one) of the native linux filesystems, and is fully supported in kernel, and is usually faster and more stable in that OS
FAT32 is the 32bit version of the old MSdos filesystem, used up to Windows 98, and still supported by windows machines, but slower and less stable than the native NTFS filesystem used by XP and above.
Nand is actually the type of flash ROM used by our devices, and not a filesystem as such, and running Android in Nand refers to where the information is stored, rather than the filesystem used to store it.
It's equally valid to say that we run WM in Nand also.
I think that in the case of Android EXT2 should be faster and more stable than fat32 since it's designed for Linux, and works better in that OS.
Zenity ik would like to thank you very much as this answers mij questions.
And i think this would many others aswell.
Don't forget - if you format your MicroSD to just EXT2 then you will make it very awkward to transfer files to/from the card on a Microsoft Windows based system.
This may, or may not be a problem for you.
Ultimately, the current ideal situation (IMHO) is to run your OS from NAND, and to store your data (music / movies / documents) on a FAT32 format MicroSD - as this enables you to swap the MicroSD card without turning off the device, and provides best cross-platform usability of the MicroSD for the purposes of transferring data to/from it.
Thank you all!
Thank you all for commenting! I will add your comments to the Android-wiki I'm building as this question could come back repeatedly from newcomers (and old ones who forgot )!
boli99 said:
Don't forget - if you format your MicroSD to just EXT2 then you will make it very awkward to transfer files to/from the card on a Microsoft Windows based system.
This may, or may not be a problem for you.
Ultimately, the current ideal situation (IMHO) is to run your OS from NAND, and to store your data (music / movies / documents) on a FAT32 format MicroSD - as this enables you to swap the MicroSD card without turning off the device, and provides best cross-platform usability of the MicroSD for the purposes of transferring data to/from it.
Click to expand...
Click to collapse
There is a program for allowing the mounting of EXT2 file systems on windows, however they are not signed. This is more problematic in Windows that are 64bit. The program is called 'ext2fsd' and you can get it from source forge. EXT2 is a better file system, and does not have the 4GB file size limit, and does not fragment (although on a SD card, this should not be an issue). EXT2 also has file permissions that Linux understands. Fat32 has no Access control file permissions.
I have just recently got polymod's eclair running with both system and data on ext2 partitions.
my question is...
I am just wondering what the boot order is...
and where(if possible) can it be changed?
system.img in the andboot folder VS system on partition.
I know it can be set in the installer. but lets say I had installed system on ext2 partition. and then later placed a system.img in the andboot folder.
can I swap between the two?
OK...
I figured it out myself,
You can use the installer to select boot options (Not just options to install)
so I have a system and data on partitons. (currently using)
and I also have a second build installed to .img files in the andboot folder. (for failsafe backup)
if I want to swap from one into the other
I enter installer and change the settings for the system and data to
their respective locations and then just QUIT.
I also still have a donut build in the android folder. as well as still running winmo.
quad boot system on my phone...LOL
Now thats a neat use of the installer, I think this find deserves it's own thread in fact, I'm certain others will find it useful
Tanks !
binlabin said:
* Running the system from NAND and data on EXT2
The performance seems almost as fast as the system+data on NAND. I have no idea about the added value of running anything from an EXT2-partition in the SD card but I'm guessing it will be slower. I have no idea if file access for manipulation is easier or not compared to the other options.
Click to expand...
Click to collapse
I've done some tries with this doing the partitioning from within android and then formatting the FAT32 partition from Windows 7 but the FAT32 partition doesn't work very well afterward. Really slow and sometimes crashes the explorer. Propably something to do with my SD-card. May try doing the partitioning and formatting from Linux to see if it works better.
Seems to me the main advantage of this option is to increase the size of available data storage which i suspect can become a limitation sooner or later in a pure NAND install.
EDIT: Now I've done it and gone NAND-System + EXT2-Data... Partitioned the SD-card from Ubuntu with gparted. Resized the FAT32 partition and created 3 primary EXT2 partitions. only the second (partition 3) should be used though with the setup I am using. It's charging right now so I haven't tried it out much yet but I will later on. However I noticed that I now have 171Mb free phone storage instead of 30-something that I had before (same apps installed).
EDIT2: Ran gparted again and shrinked the unused partition (partition 2) and expanded the data partition (partition 3) so I now have 369Mb free "Internal phone storage". Haven't noticed any speed differences between this and when I had data on NAND.
nand
By then one question:
If im install android in the NAND is more fast ready? But this process erase WM6?
Because now android work good in my HTC TYNT II but the camera and bluetooth not work and have one or two performance problems and for this dont like delete WM6 of my phone, and for this im use Android from my SD.
But look the NAND option because have a problems with the time live of my battery only lasts 5hours with android and SD.
Thanks for your help and cooperation
excellent thread which answers some questions that I had. Thanks to everyone who contributed. The only question remaining though and I have posted this elsewhere without getting an answer:
I partitioned a 2 gb sdcard with ~1.6gb Fat32 and the rest as a single Ext2. I selected system on nand and data on ext2 in the installer. After installation, it does show alot more memory for data as compared to data on nand, BUT I also have a data.img in andboot which is in the Fat32 partition, with a size around 250mb. The question is, is the data in that file or on ext2? If I backup data from installer, it creates a databackup.img in andboot with the same size as data.img. Seems to me the ext2 partition is just taking up space and not being used. Can anyone more knowledgeable shed some light on this? Thanks.
Not quite sure what is going on there, seems very counter-intuitive, I would have assumed that system on Nand, data on EXT2 would have installed the data partition to EXT2 on SD. This would seem not to be the case in this instance.
There are a few experiments you could try, if you are brave enough, since you may cause problems by trying any of these suggestions, which could mean a reinstall, I leave it to your judgement how to proceed
Ok firstly I assume you have a card reader, since you managed to partition and format the SD card in the first place. Remove the SD card, insert in card reader, delete the andboot folder, or the contents of the folder, ( may be wise to have a spare SD with either a winmo or android install handy at this point, just in case things go horribly wrong ).
Now with the cleaned SD, put it in the phone and boot, it should boot fine, IF the data is truly on the EXT2 partition.
That at least will answer one question, namely, where the heck is my data?
If this works fine, then I'd just put it down to some inner weirdness of android on non-native devices, if it fails then I'm wondering if your EXT2 partition may have problems, forcing the phone to dump it on the first available good partition, namely the FAT32 one.
Oh and if it does fail, you will have to reinstall, since your data will be toast.
Finally, good luck, I await with interest
As I recall, the install has the FAT32/Ext2 options incorrectly swapped. It has been this way for a while.
zenity said:
Not quite sure what is going on there, seems very counter-intuitive, I would have assumed that system on Nand, data on EXT2 would have installed the data partition to EXT2 on SD. This would seem not to be the case in this instance.
There are a few experiments you could try, if you are brave enough, since you may cause problems by trying any of these suggestions, which could mean a reinstall, I leave it to your judgement how to proceed
Ok firstly I assume you have a card reader, since you managed to partition and format the SD card in the first place. Remove the SD card, insert in card reader, delete the andboot folder, or the contents of the folder, ( may be wise to have a spare SD with either a winmo or android install handy at this point, just in case things go horribly wrong ).
Now with the cleaned SD, put it in the phone and boot, it should boot fine, IF the data is truly on the EXT2 partition.
That at least will answer one question, namely, where the heck is my data?
If this works fine, then I'd just put it down to some inner weirdness of android on non-native devices, if it fails then I'm wondering if your EXT2 partition may have problems, forcing the phone to dump it on the first available good partition, namely the FAT32 one.
Oh and if it does fail, you will have to reinstall, since your data will be toast.
Finally, good luck, I await with interest
Click to expand...
Click to collapse
Great idea, I'll try this on the weekend. I wont delete data though, I'll just rename andboot and backup data for good measure, because I want to be able to go back to the data by renaming it back if it doesn't work. I was also thinking if there is any way to get to the ext2 partition and read it... I'm on xp so I cant do it on my pc, and on the phone, I've looked around in astro n other file managers but cant see anything. But if the case is as golfnz34me points out, then I should just backup the data, and change the option to Fat32 in install and restore data. That should do the trick.
golfnz34me said:
As I recall, the install has the FAT32/Ext2 options incorrectly swapped. It has been this way for a while.
Click to expand...
Click to collapse
Thanks, will check this out. If its true, then great, more speed for my /data! I wonder how I missed this, been going through these forums regularly...
Ok I checked it out, and golfnz34me is correct it seems.
But now I found a new problem. I backed up data, and in the installer, set the data to SDCard, and tried to restore data. It gives various errors like
Code:
cannot determine filesystem size
failed
failed to format
...some other lines...
losetup: /dev/block/loop2: no such device or address
I created the partition with Paragon partition manager, and after getting this error I rechecked in PPM. I reformated the partition, but still get the error. In PPM the partition drive letter isnt assigned. Or, the partition isnt the active partition. Can one of those be the problem? The volume name is Ext2. Im not very experienced in partitioning etc, apart from normal ntfs partition for new hds in windows, so I didnt play with any options. I dont have a linux system either. Any got any ideas? Any help would be appreciated alot!
Not sure about using partition managers other than gparted, afaik most people are using the Gparted live cd if they don't have a linux install handy.
The errors all point to some sort of problem with the EXT2 partition, or it's formatting.
Also EXT2 partitions do not have drive letters, nor do they have to be active partitions.
Apps and data on SD card.
I cant seem to figure out how to make all the apps and other stuff install to the SD card. Do I have to partition the card into two partitions? or is there a way to install the system to Nand and make all the apps and data go to the SD card? Ive tried setting it to System on nand and data on SD partition but it says no partitions to install to or something.
I keep getting a message about storage space running low.
I have installed Apps2SD so all my apps that can be moved have been moved.
My contacts folder seems large at 18Mb
QuickOffice is 5Mb but I never use it.
Am I missiing something here?
Is there a way to free up memory easily?
If you have an a2sd+ script (most custom roms have), the apk files of your apps will be moved to the ext2/3/4 partition on the sd card, but there still remains the dalvik cache on the /data partition which uses up memory. There are scripts to move this dalvik cache to the sd card as well, but they require you have a class 4 or faster card. The best thing to do is search the thread of your rom, since it's probably been asked about it there.
If you're using google's a2sd (because you're not using a custom rom with such a script), not all apps can be moved to the sd card, since the developer has to specifically state the app can be moved, and for some reason, a lot of people don't do that. You can download a program called SDMove or App2sd from the market which will tell you which apps can be moved (and give you an option to move them), but there isn't very much you can do about getting more space. That is, if you don't want to get a new rom or install a a2sd+ script.
Cheers for the feedback.
Iam not sure if LeeDroid has the APPS2SD in the rom, I have Rom Manager and I THINK i now have ext2 and swap file but yet to confirm that with the new sd card as I am unable to copy the files from the old to the new, (thats another story)
So are you saying that APPS2SD on the ROM is better than APPS2SD from the market? I liked the market one so much I actually paid for to pro version.
Some of the apps will not move which is annoying, esp if what you say is that its all down to the lazy developers.
Can I reduce the phone book size? Text Messages etc to alleviate this issue?
I have no qualms in installing a new ROM if that will give me more space.
As many Desire users, I had the same issue.
Oxygen ROM is the best thing that had happened to Desire.
First do S-OFF, put Bravo Oxygen HBOOT patch (see alpharev.nl for more info), and then flash Oxygen ROM. And you will never have to worry about space again. I don't even move my apps to SD anymore, since there is no need.
Porcupine00 said:
As many Desire users, I had the same issue.
Oxygen ROM is the best thing that had happened to Desire.
First do S-OFF, put Bravo Oxygen HBOOT patch (see alpharev.nl for more info), and then flash Oxygen ROM. And you will never have to worry about space again. I don't even move my apps to SD anymore, since there is no need.
Click to expand...
Click to collapse
I said that around in other posts and other members were moaning at me because "not everyone can do that". Anyway, yes flashing a hboot will give you more data to work with (depending on which template you get).
Using A2SD(+) is a workaround if you don't want to S-Off you Desire. However, A2SD(+) still uses /data partition unless you get a Data2SD script or at least a script to move the Dalvik cache. I think a lot of people fail to realise this.
Flashing Hboots? Sounds like Gary Glitters footwear!
What is S-OFF?
So is A2SD (+), different from A2SD?
Does this require a degree in Linux like so many of the other things?
If your contacts app is too large ...
http://androidforums.com/htc-desire/127440-internal-memory-again.html
for me, data2sd was the only solution to consider when it comes to internal memory issues
uktotty said:
Flashing Hboots? Sounds like Gary Glitters footwear!
What is S-OFF?
So is A2SD (+), different from A2SD?
Does this require a degree in Linux like so many of the other things?
Click to expand...
Click to collapse
Firstly, HBOOT is the partition table in your phone. By default it has 147 MB for the /data partition (that's where your apps go) and 250 MB for the /system (where your ROM is installed).
Secondly, HTC implemented a security flag in our phones that protect this HBOOT from being changed and denies writing to /system when using the phone.
Now, this security flag can be disabled (S-OFF = security off), which will allow you to change the layout of your partition table. What @Porcupine00 was saying is a lot of people do the procedure to S-OFF their devices, flash the Oxygen HBOOT (which gives 300+ MB of /data storage), because Oxygen ROM is very small (about 90 MB) and doesn't need that much space in /system, so this space is made available in /data. However, messing with partitions is quite dangerous and you should read all the guides carefully before trying, because it can really brick your device. Must I add is voids you warranty?!
Now, to clear up the confusion about a2sd. There is the a2sd system implemented by Google and available in FroYo and higher which can only move the apps meant to be moved. There is the app on the market which is called App 2 SD which shows the apps installed on your phone that can use this system. And there are a2sd+ scripts which move all apps to the ext partition on your sd card.
Data2SD is another kind of script for moving apps to ext partition, along with their other data, but it requires a fast sd card (I think a class-6 or higher is recommended, whereas my stock Desire sd card is a class-2).
I advice you read through the Desire Android Development forum and find out about all these methods and make sure you know what you are doing before flashing.
Good luck!
thank you sir, very informative and non patronising
I still need to work out how to get the date from my old 4gb to my new 16Gb card as everyhing I have tried has failed, then I can get some larger partitions and the ext's
What is the problem you are having? When I rooted my phone, I swapped my 4-GB with an 8-GB one and the only thing I did is just copy all the contents from the former to the latter. I had no issues with apps, media files whatsoever.
However, I only had a FAT partition back then, so if you are talking about moving the apk's on the ext partition, you'll need to use a Linux operating system (because Windows doesn't read ext, and also doesn't mount anything else than the first partition on an external drive, which happenes to be the FAT one in our case). There are live cd's from several linux distributions that are available for free download, which you can use to copy the content from your ext partition to your pc, then back to the new card.
The problem is as follows.
Titanium back up all apps and data to 4gb card
Copy contents to windows desktop, folder properties 3.6gb
Change card to 16gb in phone, connect etc
Copy contents of 3.6gb file to new card
800mb on new card.
It seems to be copying FOLDERS but not the contents of those folders.
I am using standard USB mount
I have tried Droid Explorer
I also have ABD installed and stuff but it confuses me!
I have also got various versions of linux and a VM but not tried any of that as 20 years of windows experience probably wont help me
Only thing missing is a card reader currently so doing all of this via usb cable with card in phone
Maybe it has something to do with your Windows system? Could you try on another computer? Also, have you tried reformatting the new card before copying the files?
good point, dont have any other pcs to try here and works laptop is pgp encrypted.
I have used partionmanager to format the car, partition the card etc and it shows healthy partitions.
Just cant seem to copy and paste the files!
OK so I copy 3.6 gb from android to desktop, do the reverse and droid explorer says
"Copying 439Mb"
Can you try to open up your card using Windows Explorer and look at what size it shows? I'm thinking it's not actually the '439 MB' that's wrong, but the '3.6 GB'. I remember my Sense nandroid backup had about 400 MB as well, and also, how could you possibly fit 3.6 GB of apps in a Desire's 147-MB /data partition?
After you copy, try looking at some random files and cross-check the size it says on the phone (use Astro or some other fille manager), then chech the size on the card shown on your PC, and the size of the copied file. Maybe there is no copying error at all, but just a size-showing one, so maybe you've nothing to worry about
Sorry not the data partion the MicroSD Card
I am moving from a 4gb card which will hold around 4gb to a 16gb card which will allow me ext, swap parttions etc
Sorry, my bad, I meant 'Titanium Backup' and not 'nandroid backup'. I was saying the Titanium backup alone is fine if it's about 400 MB. So you can't copy your files like music, wallpapers and stuff? I wonder where the problem is
Trying something now, which is bot into recovery mode and mount the USB, copy to the new card via that method, no error messages yet
Guys
Thanks for the feedback
We have a result!!
Copy files from old CD Card to PC (3.6Gb)
Change cards in phone
reboot into recovery and mount usb
Copy files back (3.6Gb)
Woo Hoo
Phone runs quicker now, will see what we can do about internal memory after new rom
http://forum.xda-developers.com/attachment.php?attachmentid=2823490&stc=1&d=1404033113Hi, I'm hearkenoath and I have to bear with a Galaxy Fame GT-6810L ;P Not complaining so much recently though.
I partitioned mi 32 GB SD class 4 Card Adata (if the brand helps) using Mini Tool Partition Wizard Home Edition like sayhellotwoheaven posted http://forum.xda-developers.com/showthread.php?t=2126363 I followed his steps and numbers. Even though I knoe that partitions should be only 20% of the total space.
And I know, I know: maybe our kernel doesn't support EXT4. I'm using Corsifame ROM from this forum but the perfomance was pushing me to smash my device against the wall. So I was interested in swapping virtual memory AND I KNOW, VM has a reduced number of R/W cycles and potentially can fry my SD/internal storage.
I used this helpful thread http://forum.xda-developers.com/showpost.php?p=50143050&postcount=101&nocache=1&z=8882311745546758 and set it up to full ZRAM usage and Swap partition (since the other options don't worked for me)
The result was superb, so much better that before or with the 32 GB card not partitioned but the space ended in 9.99 GB only readable trough the phone and with the Kies installed.
My problem is this: the SD card cant mount, obviuosly I can't flash zips from CWM (only using /sdcard0) or backup and that stuff. I tried umount /storage/extSdCard/ and mount/ from CWM. Also can't cd to that directory (but I feel like never can't)
What can I do?
My root was with VRoot if helps. I appreciate all input.
P.S. I followed this tutorial and got Backtrack 5 running in our humble device. I always thought that my device would freeze This are the screenshots and here are the links if you wanna try it.I wonder if Ubuntu can run as well, but it needs 2.5 GB of space (hope that not in internal) View attachment 2823462 http://apk-hacks.blogspot.mx/2012/06/backtrack-5-en-android-tutorial.html?m=1
http://forum.xda-developers.com/attachment.php?attachmentid=2823490&stc=1&d=1404033113
http://forum.xda-developers.com/attachment.php?attachmentid=2823496&stc=1&d=1404033485
I've spent several years lurking on XDA and have always been able to find answers without having to ask questions. I guess my time is up because I'm hitting a wall finally. And I apologize in advance if this is the wrong place to put the question - its just that I have the Galaxy Tab Pro 8.4 and I haven't found any conversations that were generic enough to try and fix the issues I've got. So without further adieu:
Stats: Galaxy Tab Pro 8.4 - ROOTED, with CyanogenMod 12 installed. TWRM as my recovery. 64GB SD card partitioned into 40gigs of FAT32 for general storage, 20gigs of ext2 for use with Linux Deploy, and about a Gig leftover for swap if such a thing is even possible,
The 40 gig partition of the memory stick is auto-mounted by the OS and is totally usable.
The 20 gig partition I cannot get to mount on any folder even when creating an empty folder myself and trying to mount it by hand.
What I want to do is use Linux Deploy to create a Linux system in the 20gig partition of the card but no matter what options I've tried I can't seem to make it work. The Linux Deploy status indicates that it can see /dev/block/mmcblk1p2 which is the Linux partition but when I set that as the target for install I get an error indicating it cant mount the partition - the message says to hit 'stop' and try again, when I do that I get the following:
Making file system (ext4) .. ext2fs_check_if_mount: can't check if filesystem is mounted due to missing mtab file while trying to determine whether /dev/block/mmcblk1p2 is mounted. /dev/block/mmcblk1p2: Device or resource busy while setting up the superblock
fail
<<< end: install
I'm not sure what to do about this. If it were a plain Linux box I'd just go to the fstab and add the partition directly but I don't see where anything like that is on android.
Has anyone had experience with this? I'd really appreciate the help.
Thanks in advance for any info you can give
-rmagnuson
Initially Titanium Backup's "move to SD" feature looked like a great way to use tools I was already familiar with to make the most of limited internal storage. While searching for answers on how to set up what TB needed, it became clear that pretty much any similar app or solution - e.g. Mounts2SD - would need this partition mounted to function properly.
Problem is I can't seem to get it to work, despite trying EVERYthing that all of xda forums and Google can tell me. And there's a lot of info on this topic.
This is the mount command in Terminal emulator:
Code:
su
busybox mount -t ext4 /dev/block/mmcblk1p2 /sd-ext
(where I've confirmed that /dev/block/mmcblk1p2 is the partition I want to mount, ext4 is replaced by correct filesystem, and /sd-ext exists and is the desired mount point.)
It seems to go fine... I don't get any errors or feedback. But TB doesn't detect the partition even after adding an "app" folder using "mkdir" command.
Here's way more info than necessary about my situation in case it might help...
Device is SM-113, KK 4.4.4. Rooted, stock everything, selectively debloated using Titanium Backup Pro
Recovery is TWRP 3.0.0
Busybox by Stericson from Google Play
This is what I've done, in all possible combinations:
— Have used 3 separate SD cards: 32GB fresh out of the package (largest size officially supported by this tab) and 2 used 64GB (no documentation but it mounted and works fine for regular storage!)
— Used TWRP, AParted (from Play store) and Minitool (on Windows) to create the partitions
— 2nd partition formatted as ext2 & ext4 (read somewhere that ext3 wasn't a good idea...)
— Size of the 2nd partition ranging from less than 10% of SD card size up to 10GB
— Mounting to /sd-ext, /system/sd, and /data/sd (per TB's knowledgebase, linked above )
I've also attempted using a few apps from Google PIay as recommended by various threads on the subject from this forum (don't even remember which but I can look them up if necessary). I've since wiped and restored a nandroid backup so that none of these can potentially get in the way.
This IS working on my (also stock, MM 6.0.1) Galaxy S5 (G900W8) with one of the cards that didnt work on this tab - a 4GB ext4 partition on a 64GB SD card. After TB recognized it I set up init.d support and it happily mounts on every boot.
So it looks like it's something to do with this device, which sadly has extremely limited space that makes me want to cry. Therefore, I hope someone else with the 113 can lend a hand.
If necessary, I'm totally willing to flash stock, re-root, and set everything up again in order to make this work!
Not too sure. I use Aparted and Link2SD on a couple of my older toys...lol. I use ext 3 too. I have a 210, I'll play with it and see if I can figure it out.
Thanks @RealWelder! Don't know if that'll help as it's a different device, but let me know what, if anything, you figure out.
Personally, I'm going to give it another shot using the 'Mounts2SD' app (even though I'd wanted to do this WITHOUT any new apps... oh well, if it works at least I'll have plenty of space!)
I got it to work! *happy dance* Absolutely NO idea exactly what did it, but there was a lot of fiddling with permissions, and rebooting, and painfully typing "mount -t ext4 etc. etc." into terminal, and making adjustments to init.d scripts until finally ... TB recognized it.
Thank you XDA forum!
Sent from my Samsung SM-T113 using XDA Labs