[Q] Issue with using Link2SD to bind external data - Galaxy Tab S Q&A, Help & Troubleshooting

I have run into an issue with using Link2SD to bind external data. On the SD card, I have two partitions. The first partition is using FAT and the second is EXT4. If I link the external data (bind) to the first partition, everything appears to work correctly. However, if link it to the second partition, the app is able to access the data but is not able to write to it. For example, the Amazone Kindle app is not able to download any new books if linked to the second partition, but it can if linked to the first partition. Is this be design or am I missing something?

@Title101
I had the same issue as you. I would suggest removing the second partition and allowing the entire SD card to use FAT fs. Since I made those changes, everything works fine. You should also take into consideration which directories you are moving, some applications don't do well when their data directory is redirected.

Related

Android on Kaiser: The difference between SD/NAND/EXT2?

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.

Possible FIX for persistent low space and sd/emmc mounting issues.

Ok I have been seeing so many posts latley about low space issues and sd and emmc not mounting, but I never had the issue till today. However After some digging I managed to fix my problem without having to wipe my phone or revert to stock. I believe everyones issues may be linked to their ext2/3/4 partitions. I use link2sd and after a reboot I noticed my linked apps were not loaded, so I opened link2sd and it said there were no apps linked. So I decided to reboot and when it reloaded all my linked apps were back but all of a sudden in the notification bar i see the low space icon. So I decide to unlink all of my apps and uninstall link2sd, and do a dalvik and cache partition wipe along with a fix permissions. Apon reboot I still recieve the low space warning, so I decide to go back to recovery and format the sd-ext, only it errors and quits without formating. So i reboot and get the low space warning again along with my sdcard and emmc not mounting or readable. So heres what I did.
I powered off my phone removed the sdcard and placed it in my pc. I tried to save the files on my sd but windows could not read it either. So i used "G-Parted" (google it - awesome program) to remove both the fat32 and ext3 partitions on my sdcard and then create new ones. I placed the sdcard back in my phone booted up and all issues are fixed, no low space warning and my sd and emmc were back to normal.
A lot of people kind of forget about the ext partitions when trying to solve issues. I believe a corrupted sd ext may be the root of everyones low space and mounting problems. Even if it seems as if its working correctly there still may be a bad block messing everything up. A lot of people dont realize that formating your sd with windows does not format or remove your ext partition.
I may be wrong but it fixed both of my issues and i hope it fixes everyone elses too. Hey its worth a shot right.
It may be definitely worth a shot. I haven't been able to mount emmc since just before I used Link2SD to create an ext3 partition (it happened with a kernel update while I was still on Nils' Business Gingersense 2.1/3.0 mix.)
I *haven't* been getting low memory messages, however, in part because I make extensive use of NotEnoughSpace's ability to move stuff out of \data\data.
However, now when I mount to PC, the PC sees the emmc as a drive letter but can't populate it. I had followed the instructions on xda here but, while that does give me amazing functionality, it doesn't restore the emmc mount (nor would I expect it to).
I'd be reluctant to wipe my sd card, but the fact is I have always had a "spare" sd card which I use synctoy to keep current with my "phone" sd card. The only difference is that the "spare" doesn't have the ext3 partition, and, interestingly, even when I boot up with that card instead of the one with the ext3 partition, I still can't get emmc to mount to PC.
Would be interested in any other ideas.

[Q] Apps to SD help please

I've been trying to learn up on apps to sd from reading several forums, and can't seem to find the right answers.
I've been rooting and ROMing for months now, but never had a need to push phones to SD. Now i think it's time, but have a few questions.
There's a Move to SD Card option under manager applications from the CM menu. How does that differ from the option to push apps to SD in titanium?
What's the story with ext3, ext4, and sd-ext partitions?
Do i need one of those, and if so which one?
I've noticed that when trying to put apps on sd using hte application settings, that i sometimes can't find the widget associated to an app. Is that normal?
Thnks for your help.
mangle
It's probably the same function. I haven't used Ti much though. I'm still a newbie with that app. The app itself has to support being put on the SD card in the manifest file for the app in order for you to be able to move it.
thanks for the reply. I guess i'm trying to figure out what the benefit of having an SDcard partition is when it comes to off loading apps to the SD card. There have been plenty of views on the thread. I'm sure someone out there has the knowledge.
The benefit is that it puts the bulk of the app on the the SD card to save space on your internal storage since those are usually smaller size than the SD card. It'll still save some data and prefs on internal storage but the apk for the app will be on the card. This is very useful for apps that are large like games which can sometimes be over 20MB.
You can read some of the developer docs here for more info on app2sd.
http://developer.android.com/guide/appendix/install-location.html
Best way I have found to move apps to sd is to partition your sdcard with ext3 (ext4 if your kernel supports it) and then use the link2sd app from the market to move your apps, their lib files, and their dalvik-cache files to the sd-ext. Saves a ton of space on the /data and /data/data partitions.
Also if your running gingerbread you should check out jermaine151's ext4_no_data_limit mods. They take the tiny /data/data partition (usualy the cause of low space errors) and move it to the larger /data partition, eliminating the low space issue. It also converts the ext3 /data and /cache partitions to the faster ext4 file system, speeding up apps.

[GUIDE] Repartitioning SD Card for link2sd for DUMMIES.

Alright, this is a guide for those people who need to increase/decrease their size of ext2/3/4 partition or even change SD card as I did from 2 GB Samsung to 4 GB Kingston Class 4.
This has been tested on windows 8.
Windows only recognizes the first partition of any removable device, this is where the problem lies while changing SD card or while making the amendments to your Ext partition. You apps will all be LOST if you format without care. Don't get hyper, this is quick and easy guide.
Things you will need.
1.Minitool Partition wizard home edition (probably the same which you used to create the partition)
2.Ext2 Volume manager.
3.Ext2IFS for windows.
USB mount is strictly not advisable, use a card reader. If you don't have any then use a mobile which is not an android, Nokia as for example.
1. Switch your mobile off, remove SD card. Insert it into card reader and then to USB port.
2.Windows will show you your FAT/FAT32 partition.
3.Backup your FAT/FAT32 partition. This is because you are gonna delete this partition.
4.After backing up open Minitool Partition wizard, delete your FAT/FAT32 partition. Be sure to delete this only, DO NOT DELETE EXT2/3/4. Apply those changes.
5.Go to Ext2 Volume manager and select the removable SD card. Double click on Linux partition. Then click on mount points and done.
6.Go to My computer and you will find your Ext2/3/4 partition as a removable drive. Backup this, be sure to copy all the files. Do not leave any file.
7.Now delete this partition from Minitool Partition wizard, your full card is empty now.
8.Create a new parition as primary and Ext2/3/4. Drag this to the far right. Be sure that all the unallocated space is before this Ext partition. Not even a single MB should be after this partition. Apply changes. Select the size of partition according to your convenience.
9.Copy all those EXT backup files to this Ext partition. Windows will show this partition now. If it does not, go to Ext2 Volume manager and do the steps you did before.
10.Now that you have created an Ext partition of your desirable size. Go to Minitool Partition wizard and create a primary FAT/FAT32 partition in the unallocated space. Apply changes.
11.Copy those backup files on this new partition of fat file system which you copied. Now the Ext partition will not be shown in windows.
12.You are done! Insert SD into your phone and power it on. The first boot will take a little longer than normal.
13.Go to link2sd and check the storage, you will be having all the apps + your partition size is increased/decreased now.
If you have any problems tell me.
To all those who want to create a pictorial guide, DO IT BUT INCLUDE A LINK TO MY ORIGINAL GUIDE.
Close to 100 views still nothing here. :/
Sent from my GT-S5360 using XDA
Master_Key said:
Close to 100 views still nothing here. :/
Sent from my GT-S5360 using XDA
Click to expand...
Click to collapse
I believe that increasing means getting bigger ext partition without the need to re-partition the card. If I were you I would create a guide in RESIZING EXT PARTITIONS, else rename your guide to "how to repartition a SD Card"
Sent from my GT-S5360 using xda premium
Sorry, changed it.
Well that day I had laptop and since then I am using mobile so forgot to check the caption.
Sorry again
Sent from my GT-S5360 using XDA
Problem
I followed all of your steps to the letter to repartition and increase the size of my link2sd partition and after rebooting my phone, I'm getting nothing but error messages and "force close" left and right. I'm not sure at all what had gone wrong. :/ I backed up every single file from both partitions, but everything appears to be borked.
UPDATE: it's apparently not mounting the second partition; that's at least what it seems to be telling me as I'm going through some of the stuff on link2sd
ElusiveZatchmo said:
I followed all of your steps to the letter to repartition and increase the size of my link2sd partition and after rebooting my phone, I'm getting nothing but error messages and "force close" left and right. I'm not sure at all what had gone wrong. :/ I backed up every single file from both partitions, but everything appears to be borked.
UPDATE: it's apparently not mounting the second partition; that's at least what it seems to be telling me as I'm going through some of the stuff on link2sd
Click to expand...
Click to collapse
Can you tell me in more detail what did you do?
Also what kind of SD card are you using and other details.
increase 2nd partition of SD card without losing data
My SD card's 2nd partition is FAT32 and I'd like to increase it's size. How do I do it without losing my apps installed on there?
I tried connecting it to card reader and using miniTools to increase the size but it only allows NTFS partition to increase without losing data.
increase size of partition 2
Hi, just a quick question, can I increase the size of partition 2 without formatting or losing files and data?

[Q] Troubles with Link2SD

Hello guys,
I've got a problem.
I've been following the following guide "http://www.link2sd.info/description" in order to create a partition with Minitool Partition Wizard and link/swap all my apps on my SD card.
So I've got two partitions on my SD card now:
- The first one, "kingston (F)" - 14 Go FAT32 which is where I store all my data.
- The second one, with no name, 780 Mo FAT32 which is used by Link2SD to link and install my apps.
So far, everythings fine, Link2SD is working as it should be.
My only problem is: the second partition (the one used by Link2SD) does not show in windows 7 explorer. It is not visible on my computer and I cannot access to the data on this partition. Which is a shame as I want to backup all these data, just in case. And I want to upgrade my SD card to 32 Go so I need to copy and move all this data from my current SD card to the new one.
Curiously, the partition on my SD card shows in Minitool Partition Wizard, it also shows in "ES File Explorer" on my phone, and it is also visible via Windows Disk Management program (but I cannot explore or access to it: it just shows as 780 Mo used separately, with no name, no letter).
Do you know what the problem is? Maybe I did something wrong when creating the partition?
Your help or suggestions would be very appreciated.
You didn't do anything wrong, it just doesn't work that way. Windows 7 doesn't know how to mount the 2nd partition, because Android doesn't tell it to mount as a drive. It's like you're asking why you can't mount the /data or /system partitions on Windows 7

Categories

Resources