Related
This patch allows mounting of NTFS volumes through vold (i.e the disk is automatically mounted when pluged into the device).
Mountpoint is:
/mnt/sdcard/usb<disk-number>-disk0
Known issues:
- NTFS volumes are mounted read-only, this has been explicitly added to the vold to prevent data loss or filesystem corruption until we know that the patch is stable.
Tested on FolioMod v1.3c
Installation:
copy zip file to your sdcard, rename to update.zip and flash using recovery.
vold-update-0.2.zip - this is the patch for vold containing ntfs support
vold-rollback.zip - rollback to default FolioMod 1.3 vold
source-0.2.zip - source code for updated vold
v0.1
- Initial release
- Ntfs support, multiple disks working
v0.1.1
- make sure that the mount point directory exists, create if necessary
v0.2
- multiple partitions are working
- fixed asec handling as discussed
- mount point directories are removed, when unmounting disk (if empty)
I know vold also handles sdcard + multiple usb stick is that part still included?
and the strange vold.fstab with wildcards? otherwise it will be hard to use for a toshiba rom, i think.
Yes this should all be still included, until now I had no issues with my sdcard.
What the patch does is try to mount everythin with FAT like before, if that fails, it tries NTFS.
The vold.fstab is still included, only change is what partitions should be mounted, this was 'all' before and has been changed to 'auto' (as the 'all' seems to be a toshiba addition)
Still need to figure out how to use this, hope to get a new disk on Monday, so I can test that.
weeds2000 said:
The vold.fstab is still included, only change is what partitions should be mounted, this was 'all' before and has been changed to 'auto' (as the 'all' seems to be a toshiba addition)
Click to expand...
Click to collapse
Could that also help recognizing some strange formatted SD cards? E.g. I have a digicam (Panasonic) that modifies the FAT32 somehow that the folio tells me the card is defective (but still works perfectly fine in Windows or the Digicam)?
I doubt it, as nothing has changed for sdcard.
But as this vold is compiled with additional debug output you may as well trry to use it. Maybe the output will give some more information on what is going wrong.
But I guess this is because your cam actually uses the "secure" part in your Secure Digital Memory Card. See http://en.wikipedia.org/wiki/Secure_Digital#DRM_features for more info on that.
Very interesting! Thank you !!
Tested with FolioTNT 4.0a and 2 usb sticks (16 and 8 gigs) and working perfectly on both
Great job
Is write supported already or is only for read?
Can large files be read?!?! (i mean no laggy?)
Thanks
Great job, thank you very much Mr. Weeds!
OK partition support is somehow working now, but not really a solution I like to release.
Looks like vold was not intended to handle that.
The main reason for this post is, that the handling of /mnt/asec and /mnt/asec_secure is somewhat bad (again vold was not intended to even handle multiple external storage devices at the same time)
Just to make sure anyone know what that is: Apps2SD stores the packages in that folder.
At the moment vold will create (and mount) an asec container for every storage device attached to the folio. So if I insall an app (or move it manually) with SDCard inserted it will use the asec dir of the SDCard. If I install an app without SDCard it will use the asset directory of the internal storage.
The problem is it seems I cannot change on the fly between those two directories. If I unmount SDCard /mnt/asec does not contain the package if put there. So I need to take out the SDCard and reboot the device.
Fixing this behaviour would be quite simple. The question rather is where to put it?
Internal storage or SDCard?
The same question goes for what should be the default SDCard (i.e. the one mounted under /sdcard, the one where apps download their resources). Internal Storage or external SDCard.
The one thing I can think of is creating a selection setting within the settings app where I can select which device should be mounted as primary SDCard.
If that is switched the systrem may copy contens from asec to the new device.
So the layout of /mnt may look like that
/mnt/sdcard (linked to /sdcard) - the primary sdcard device as selected by the user (defaults to internal storage)
/mnt/sdcard2 - well, the other one (either internal or sdcard depending on what the first device is)
/mnt/usb-storage/usb<disk-number>-disk<partition-number> - hdd's mounted over USB
Just waiting for anyone to come up wither other/better ideas...
weeds2000 said:
Fixing this behaviour would be quite simple. The question rather is where to put it?
Internal storage or SDCard?
The same question goes for what should be the default SDCard (i.e. the one mounted under /sdcard, the one where apps download their resources). Internal Storage or external SDCard.
Just waiting for anyone to come up wither other/better ideas...
Click to expand...
Click to collapse
proper behaviour would be internal storage for apps.. as its not nice that the apps you install disappear if you remove the sdcard or usbsticks.
i noticed this problem early on..but no one mentioned it as a problem.
do you see why the .android_secure mountpoint does not happen?
i think somehow this relate to the problem of downloading paid apps.
If this is OK for everyone, then this would be a much simpler approach, so /sdcard and /mnt/sdcard always point to internal storage.
If someone needs more storage (i.e. for downloaded resources) we may simply create a tool wich does some linking (e.g. link /sdcard/gameloft to /sdcard2/gameloft)
The mount point for asec_secure exists as well, 2 times with the same issues as asec. I don't know if this is related to paid apps. According to the logs I get a 403 response from the google servers.
Is there any specific reason, why SDCard is put under /sdcard/sdvcard-disk0?
I'd like to move that to /mnt/sdcard where usb-storage will go as well.
Using that approach it might be unessesary to unmount the external storage when a USB-connection is made.
weeds2000 said:
Is there any specific reason, why SDCard is put under /sdcard/sdvcard-disk0?
I'd like to move that to /mnt/sdcard where usb-storage will go as well.
Using that approach it might be unessesary to unmount the external storage when a USB-connection is made.
Click to expand...
Click to collapse
normally its a good reason.. the Toshiba filemanager looks at a location where all users got access..
no regular user would look into a /mnt/sdcard2 unless the toshiba pointed to the location.
so /mnt/sdcard offers both internal storage + sdcard + usbstick here which i think works well and all users easily find it as its within the sdcard default location.
i dont think that logic should change..
updated to 0.2 write support is still disabled.
As I always used NTFS-3G I cannot tell if the driver implementation is reliable and complete. However I think it is, as my knowledge from incomplete write support is 3 or 4 years old...
From weeds2000:
"This patch allows mounting of NTFS volumes through vold (i.e the disk is automatically mounted when pluged into the device)...."
------------------
This patch was tested by me on FolioMod v1.3c.
It readed well one HD NTFS, and recognized all of SD cards that were not recognized before.
Many thanks.
weeds2000 said:
updated to 0.2 write support is still disabled.
As I always used NTFS-3G I cannot tell if the driver implementation is reliable and complete. However I think it is, as my knowledge from incomplete write support is 3 or 4 years old...
Click to expand...
Click to collapse
do you consider this ok to be included in a new update?
I of course let you approve if its ok for regular use..
denver-tempor said:
From weeds2000:
"This patch allows mounting of NTFS volumes through vold (i.e the disk is automatically mounted when pluged into the device)...."
------------------
This patch was tested by me on FolioMod v1.3c.
It readed well one HD NTFS, and recognized all of SD cards that were not recognized before.
Many thanks.
Click to expand...
Click to collapse
You have NTFS formatted SD Cards? Or FAT cards which weren't recognized before?
Nemo0815 said:
You have NTFS formatted SD Cards? Or FAT cards which weren't recognized before?
Click to expand...
Click to collapse
I have some SD cards (several trades and capacities) FAT formatted that weren't recognised before applying this patch. Now, they are.
Also, I tested a 2.5 USB HD, NTFS, and it was readed without problems.
weeds2000 said:
As I always used NTFS-3G I cannot tell if the driver implementation is reliable and complete. However I think it is, as my knowledge from incomplete write support is 3 or 4 years old...
Click to expand...
Click to collapse
OK, so I was wrong, this is from the kernel documentation on NTFS Write support.
This enables the partial, but safe, write support in the NTFS driver.
The only supported operation is overwriting existing files, without
changing the file length. No file or directory creation, deletion or
renaming is possible. Note only non-resident files can be written to
so you may find that some very small files (<500 bytes or so) cannot
be written to.
While we cannot guarantee that it will not damage any data, we have
so far not received a single report where the driver would have
damaged someones data so we assume it is perfectly safe to use.
Click to expand...
Click to collapse
So it looks like ntfs-3g is the way to go, this will take some time however.
@dexter
I played around with various disks today, watched a movie, etc... Seems like everything is OK, so I would consider 0.2 be a candidate for regular use.
I will include this in the next update..
You seem to have many downloads, but not really any complaints
that should tell us something.
Hello folks,
I am trying to move my google music cache to the external 32GB SD card so that it won't fill up my internal storage but somehow I fail.
Here is what I did so far:
format sdcard as ext2
manually mount sdcard since it won't automatically when ext:
Code:
mkdir /Removable/MicroSD
mount -r -w -t ext2 /dev/block/vold/179\:9 /Removable/MicroSD
mkdir /Removable/MicroSD/GoogleMusicData
Then move all data from /sdcard/Android/data/com.google.android.music/cache to /Removable/MicroSD/GoogleMusicData/cache
I did this with root explorer since I'm not too much of a terminal h4xx0r.
Delete the folder /sdcard/Android/data/com.google.android.music/
Link the new Folder on external MicroSD Card to the original location via this terminal command:
Code:
ln -s /Removable/MicroSD/GoogleMusicData /data/media/Android/data/com.google.android.music
Since /sdcard is already a link like the one I am setting up here, it is not possible to link to this linked location (/sdcard/Android/data/com.google.android.music).
Instead I had to link to the origninal destination of /sdcard which is /data/media.
Now the microSD card is accessible for root explorer. It shows read and write access.
But google music won't find it. It says that it doesn't have enough space to stream music so I figure that it somehow doesn't have access to the sd card.
What could be the issue here?
Also instead of 28GB free memory root explorer shows me only 364,44MB free memory. the command "df" in terminal however confirms 28GB of free memory.
I thought that a reboot might do it. But it doesn't. Instead it gets rid of all the hacking I've done in terminal. So I guess I would have to place a script in /etc/init.d for the link to be set everytime I reboot, right?
Help please?
We don't know how gmusic checks that, but I would suggest checking the perms on the mount, perhaps even mounting somewhere else.
Never done it and don't have the resources but I'm sure with root, making /mnt/sdcard a real microsd is possible.
Sent from my Transformer Prime TF201 using Tapatalk
Maybe this thread will help ?
Thanks for your response!
What do you mean by "checking the perms on the mount"?
I don't want to mount my microsd to /sdcard since then I would have 16 gigs of unused space on my internal memory.
I would rather just link this music folder to my external card and maybe some others later (e.g. DCIM and so on).
I have also tried the mount -o bind command instead of ln but that didn't do the job either. the folder com.google.android.music then only appeared under /data/media/Android/data/ but not under /sdcard/Android/data/ which I totally don't understand how that can happen.
I have root of course.
Does anybody maybe have a script by hand of a similar undertaking so that I can look into that and try to understand how this whole mounting and binding thing works?
Hey guys, I'm sure this is a fairly common problem that us "Blaze" users are having issues with but I haven't figured out a way around it. As we all know, Blaze only came with about 1.5g of "Internal SD" memory while the "External SD" memory could be expended. This becomes a problem as the "Internal SD" is the default storage for apps, especially when you are trying to download a game that is more than 1.5g. I've looked into "Directory Bind" app but that's only really to move the app files from internal into external, AFTER it has been downloaded and install on the phone and point to its new location. Ive heard about Internal/External reverse mount tweaks, but haven't found one specifically for our phone. Does anyone know if there is a way around this? So what I'm basically asking is this: Can we use the External SD as the default storage for apps and games? And have the apps/games installed to the external SD location?
Sent from my SGH-T769 using xda app-developers app
+1 on this, would love to see something
I have the same question if you find something let me know.
Sent from my SGH-T769 using xda premium
Desertstorm00 said:
Hey guys, I'm sure this is a fairly common problem that us "Blaze" users are having issues with but I haven't figured out a way around it. As we all know, Blaze only came with about 1.5g of "Internal SD" memory while the "External SD" memory could be expended. This becomes a problem as the "Internal SD" is the default storage for apps, especially when you are trying to download a game that is more than 1.5g. I've looked into "Directory Bind" app but that's only really to move the app files from internal into external, AFTER it has been downloaded and install on the phone and point to its new location. Ive heard about Internal/External reverse mount tweaks, but haven't found one specifically for our phone. Does anyone know if there is a way around this? So what I'm basically asking is this: Can we use the External SD as the default storage for apps and games? And have the apps/games installed to the external SD location?
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
as a matter of fact, I have found a way to switch the internal/external sd mount points. You need to go into /etc/ using Script Manager and edit the vold.fstab file. Inside, you will find this:
Originally Posted by crazydrummer95 View Post
okay so heres what it looks like:
# internal sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
asec = disable
discard = enable
format_option = -r 2272
}
dev_mount sdcard /mnt/sdcard 28 /devices/platform/msm_sdcc.1/mmc_host/mmc0/mmc0
#external sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun1/file
asec = enable
}
dev_mount sdcard /mnt/sdcard/external_sd auto /devices/platform/msm_sdcc.3/mmc_host/mmc2/mmc2
#otg sdcard
{
ums_path = /dev/zero
asec = disable
}
usb_mount sdcard2 /mnt/sdcard/usbStorage auto /devices/platform/msm_hsusb_host.0
#end line
you need to change the lines :
dev_mount sdcard /mnt/sdcard 28 /devices/platform/msm_sdcc.1/mmc_host/mmc0/mmc0
dev_mount sdcard /mnt/sdcard/external_sd auto /devices/platform/msm_sdcc.3/mmc_host/mmc2/mmc2
and make it look like this:
dev_mount sdcard /mnt/sdcard/external_sd 28 /devices/platform/msm_sdcc.1/mmc_host/mmc0/mmc0
dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.3/mmc_host/mmc2/mmc2
Thanks! I will give it a try.
Sent from my SGH-T769 using xda app-developers app
Desertstorm00 said:
Thanks! I will give it a try.
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
Just for future reference, Make sure you do a little research about the question you are asking. There is a thread exactly like this one in the dev section.
crazydrummer95 said:
Just for future reference, Make sure you do a little research about the question you are asking. There is a thread exactly like this one in the dev section.
Click to expand...
Click to collapse
Oh. Right. You started it.
Sent from my SGH-T769 using xda app-developers app
crazydrummer95 said:
as a matter of fact, I have found a way to switch the internal/external sd mount points. You need to go into /etc/ using Script Manager and edit the vold.fstab file. Inside, you will find this:
Originally Posted by crazydrummer95 View Post
okay so heres what it looks like:
# internal sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
asec = disable
discard = enable
format_option = -r 2272
}
dev_mount sdcard /mnt/sdcard 28 /devices/platform/msm_sdcc.1/mmc_host/mmc0/mmc0
#external sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun1/file
asec = enable
}
dev_mount sdcard /mnt/sdcard/external_sd auto /devices/platform/msm_sdcc.3/mmc_host/mmc2/mmc2
#otg sdcard
{
ums_path = /dev/zero
asec = disable
}
usb_mount sdcard2 /mnt/sdcard/usbStorage auto /devices/platform/msm_hsusb_host.0
#end line
you need to change the lines :
dev_mount sdcard /mnt/sdcard 28 /devices/platform/msm_sdcc.1/mmc_host/mmc0/mmc0
dev_mount sdcard /mnt/sdcard/external_sd auto /devices/platform/msm_sdcc.3/mmc_host/mmc2/mmc2
and make it look like this:
dev_mount sdcard /mnt/sdcard/external_sd 28 /devices/platform/msm_sdcc.1/mmc_host/mmc0/mmc0
dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.3/mmc_host/mmc2/mmc2
Click to expand...
Click to collapse
I tried to do this in script manager and it said i was opening a read only file. Tried to open directly, wouldn't let me save. Tried to open a local copy and script manager force closed. Then tried Root Explorer. Still wouldn't let me save. Even tried copying vold.fstab to my sd card, editing it, deleting the copy inside /etc and pasting the edited version, operation failed.
am i missing something?
jparnell8839 said:
I tried to do this in script manager and it said i was opening a read only file. Tried to open directly, wouldn't let me save. Tried to open a local copy and script manager force closed. Then tried Root Explorer. Still wouldn't let me save. Even tried copying vold.fstab to my sd card, editing it, deleting the copy inside /etc and pasting the edited version, operation failed.
am i missing something?
Click to expand...
Click to collapse
did you mount the directory as r/w, in root explorer its a gray button at the top
masterofthedamned said:
did you mount the directory as r/w, in root explorer its a gray button at the top
Click to expand...
Click to collapse
I meant root browser. But, I even downloaded Droid Explorer to run it on my computer, no go. Eventually, Root Explorer did allow me to edit but upon reboot, the process android.process.media kept force closing.
Does this vold thing work?
jparnell8839 said:
I meant root browser. But, I even downloaded Droid Explorer to run it on my computer, no go. Eventually, Root Explorer did allow me to edit but upon reboot, the process android.process.media kept force closing.
Click to expand...
Click to collapse
Download Script Manager from the Play Store
I'm going to implement this into my next build of pa...
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
For those running some iteration of the stock Touchwiz-skinned ICS rom (whether custom or just stock rooted), you can always try flashing this (md5 829584F66F2F13419639A0F77AEC2033) in whatever non-stock recovery you happen to be using. This replaces the vold.fstab with one merwinski tweaked (so the internal/external sd swap stuff happens), and includes a script I put together that moves some relevant files from one to the other for you (in other words - anything you selected to move to SD via Settings > Applications should still be there and usable after flashing this). All usual disclaimers apply (i.e. I'm not responsible for breaking blah blah etc.), but if for whatever reason you want to go back to how it was before you can flash this (md5 A38CD198B5DB73209441D4A6250D33C4) and that will undo everything (including the file moving) that was done with the first one.
Hope this helps folks, and just because it bears repeating - THIS HAS ONLY BEEN TESTED ON STOCK ROMS, NOT ANY OF THE AOSP/CM BASED ONES! IT WILL VERY LIKELY NOT WORK ON THOSE!
thomas.raines said:
I'm going to implement this into my next build of pa...
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Patiently waiting!!!
paranoidandroidpoweredBLAZE!!
I thought it worked...
Alright, So i'm running CWM and I used your VOLDSwap. Now, It worked from the look. my phone storage is 3gb now and my SD is 1.2gb. so when I look at all my storages at the same time, I see my phone storage (1.2gb) my USB storage, which is now my SD card. It was 1.2 gb now its 3.8 gb. and my SD card which is now my USB storage at 1.2gb.
here is my problem, in theory I should be able to install to the "USB directory" because that is now my actual SD card, however; when I do this, i still bypasses my USB storage (my actual SD card) and still installs it to my actual USB storage (1.2gb and also being recognized right now as my SD card) so what can I do to fix this? I love that my USB storage says 3.8 gb, but it's pointless if it still uses my Sudo USB storage of 1.2 gb? is there anyway to rewrite the install directory. because It still installs to my phone but instead of going to the USB storage like it used to, because my USB and SD are swapped now, it instead heads to my USB which is labled as my SD... it's like.. no matter what I do I can't get it to install to my higher gb storage location.. any help would be beyond appreciated.
hollow2318 said:
Alright, So i'm running CWM and I used your VOLDSwap. Now, It worked from the look. my phone storage is 3gb now and my SD is 1.2gb. so when I look at all my storages at the same time, I see my phone storage (1.2gb) my USB storage, which is now my SD card. It was 1.2 gb now its 3.8 gb. and my SD card which is now my USB storage at 1.2gb.
here is my problem, in theory I should be able to install to the "USB directory" because that is now my actual SD card, however; when I do this, i still bypasses my USB storage (my actual SD card) and still installs it to my actual USB storage (1.2gb and also being recognized right now as my SD card) so what can I do to fix this? I love that my USB storage says 3.8 gb, but it's pointless if it still uses my Sudo USB storage of 1.2 gb? is there anyway to rewrite the install directory. because It still installs to my phone but instead of going to the USB storage like it used to, because my USB and SD are swapped now, it instead heads to my USB which is labled as my SD... it's like.. no matter what I do I can't get it to install to my higher gb storage location.. any help would be beyond appreciated.
Click to expand...
Click to collapse
I've had the same problem someone I forget who posted this vold change(don't feel like reading hundreds of posts to find who but thanks lol) and has worked wonders for me with no issues so far. Switch it out and make sure permissions are set correctly.
http://db.tt/byVnF6Cc
Here the outcome
## Vold 2.0 Generic fstab
## - San Mehat ([email protected])
##
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
## storage_struct - ex) series, "/mnt/sdcard/extStorages" / parallel
######################
# internal sdcard
dev_mount sdcard /storage/sdcard1 28 /devices/platform/msm_sdcc.1/mmc_host/mmc0/mmc0
# external sdcard
dev_mount external_sd /storage/sdcard0 auto /devices/platform/msm_sdcc.3/mmc_host/mmc2/mmc2
#otg sdcard
dev_mount sda /mnt/usbdisk auto /devices/platform/msm_hsusb_host.0
Sent from my AOKP Blaze
set right RW-RW-RW and change strings
dev_mount sdcard /mnt/sdcard 28 /devices/platform/msm_sdcc.1/mmc_host/mmc0/mmc0
dev_mount sdcard /mnt/sdcard/external_sd auto /devices/platform/msm_sdcc.3/mmc_host/mmc2/mmc2
to:
dev_mount sdcard /mnt/sdcard/external_sd 28 /devices/platform/msm_sdcc.1/mmc_host/mmc0/mmc0
dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.3/mmc_host/mmc2/mmc2
main my question: if now unroot device will it work?
On root device i have big trouble to connect GSM NETWORK
I'm having mount issues with my TF700. Its unlocked and rooted, installed busybox. Stock ROM and Stock Recovery. It mounts the internal OK, mounts microSD OK, mounts SD OK. But if I plug in my external Bluray reader (with DVD inserted) It mounts USBDisk001, but is linked to my SD card which is already mounted! So now I have 2 mount links to my SDcard! I've rebooted and tried other things, but couldnt get it to work properly. So I removed the SD card. Plug in the Bluray drive and it does nothing (as expected). I open a terminal, become superuser, and mkdir /Removable/Bluray, then mount -t iso9660 /dev/block/sr0 /Removable/Bluray. It claims to have mounted Read-Only (as it should), but I enter the folder and ITS EMPTY! Whats wrong here?! I type blkid and it shows the disc Label. So it IS reading the disc. I try to unmount the disc and try again. umount /Removable/Bluray . It claims Invalid Argument as if nothing is mounted! WTF?!
Any help would be greatly appreciated. FYI, Same disc on linux and windows Machine shows files fine on same external drive.
Edit: Oh, and installing busybox didn't overwrite the original mount files. I used smart install from stericson's installer and mount is still symlinked to the original /system/bin/toolbox .
Sent from my ASUS Transformer Pad TF700T using xda premium
I wanted to convert my external sdcard to ext4 so I can create a symbolic link. Mainly because one of the apps I use won't see the sdcard (devs tell me it's because the tf700 isn't using mass storage drives apparently) and I thought this might solve the problem if I could put a link on the internal card that pointed to the external. I'm aware that symbolic links cannot work with FAT32 partitions but will between ext4/3/2 partitions.
I formatted the card with minitool partition and the TF700 wouldn't mount it. It shows up in settings > storage as a MicroSD with a Mount option but this simply does nothing. Having trawled through some thread someone provided this script to mount an ext4 card.
Code:
mkdir /Removable/MicroSD
mount -o noatime,nodiratime -t ext4 /dev/block/mmcblk1p1 /Removable/MicroSD
chmod -R 777 /Removable/MicroSD
Which should be done at each boot. This seemed to work as I got to the card and was able to manually copy something to it but it seems to be flakey and unreliable. eg. a picture copied to it would fail to load. I managed to get it to after a while (not sure what I did). Then I tried an .apk file and it wouldn't install, giving an error. I also used Rom toolbox to specify Apps2SD destination to the external but trying to install anything will give "not enough space" error.
So I am stumped.
As I am rooted but NOT unlocked I can't install a rom which might be the solution but I'd like to know if what I'm trying to do is possible without that.
I find it odd that the TF700 can't deal with an ext4 partition since it can happily deal with them on the internal. I'm confused so any clear explanation of the situation would be welcome.
louiscar said:
and I thought this might solve the problem if I could put a link on the internal card that pointed to the external. I'm aware that symbolic links cannot work with FAT32 partitions but will between ext4/3/2 partitions.
Click to expand...
Click to collapse
The internal "sdcard" is not an ext4 partition, it's a FUSE filesystem that emulates some properties of FAT (no case sensitivity, no permissions) on top of ext4. It also does not support symlinks.
louiscar said:
I formatted the card with minitool partition and the TF700 wouldn't mount it.
Click to expand...
Click to collapse
Many users of the Data2SD mod had problems with Minitool - use gparted to create ext4 partitions.
louiscar said:
This seemed to work as I got to the card and was able to manually copy something to it but it seems to be flakey and unreliable. eg. a picture copied to it would fail to load. I managed to get it to after a while (not sure what I did).
Click to expand...
Click to collapse
Are you on the latest 10.4.4.25 firmware? Because that fixed something with microSD cards, and it's the only kernel so far that reliably works with my Sandisk "Mobile Ultra" microSD card, even with ext4.
_that said:
The internal "sdcard" is not an ext4 partition, it's a FUSE filesystem that emulates some properties of FAT (no case sensitivity, no permissions) on top of ext4. It also does not support symlinks.
Click to expand...
Click to collapse
Ok although I don't understand the Fuse fs (still trying to get to grips with basic unix stuff), I did think that symlinks were used internally.
_that said:
Many users of the Data2SD mod had problems with Minitool - use gparted to create ext4 partitions.
Click to expand...
Click to collapse
Ok I'll give that a go.
_that said:
Are you on the latest 10.4.4.25 firmware? Because that fixed something with microSD cards, and it's the only kernel so far that reliably works with my Sandisk "Mobile Ultra" microSD card, even with ext4.
Click to expand...
Click to collapse
Yes, I've just done the OTA to .25 a few days ago.
So basically what you are saying is that there's no reason why an external MicroSD formatted as Ext4 shouldn't work with the TF700?
Many thanks for the quick reply. I'm going to get gparted and give this a go.