bg4m3r
Android Expert
FAT32? Use just FAT.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
spocko
Well-Known Member
Why? He has a 64 GB card. FAT has a max partition size of 4 GB, so that would be a significant limitation. I can't think of any reason to use FAT instead of FAT32.
bg4m3r
Android Expert
So it seems windows is making me go stupid since it calls all forms of FAT FAT. I was thinking of FAT32. My bad.
Last edited:
DaKillaWilla
Well-Known Member
I've had problems with other apps that supposedly convert updated system apps. I would get a lot of force closes. Link2sd worked good at converting them. It saved me close to 1gb of space. Not bad...
bg4m3r
Android Expert
Most apps that do that only move the apk, or misplace the lib files. That's what causes the force closes.
gmturner
Lurker
If it supported loop-mounted sparse ext4, we could have had our cake and ate it too. But I guess I can see how the matrix of potential problems could start to multiply once link2sd creates dependencies on >4GB files (no fat32 support), loop-mount, ext4 support in kernel, end-user not accidentally filling partition with zero's via incorrect dd usage, userland support for hot resize, etc...
Unfortunately, since link2sd seems to want to maintain it's own brain-dead-looking init script, even if I one gets it to work, some future link2sd could easily find a way to get confused by it, with potentially disastrous results.
Any precedent out there for replacing symlinks with, i.e., aufs or overlayfs, or just bind mounts, as a means of getting android's storage onto non-default block devices?
It's often hard for me to satisfy myself that android will treat symlinks identically to regular files, hence, I always find myself wondering whether it's link2sd's fault, whenever I manage to break my phone
Unfortunately, since link2sd seems to want to maintain it's own brain-dead-looking init script, even if I one gets it to work, some future link2sd could easily find a way to get confused by it, with potentially disastrous results.
Any precedent out there for replacing symlinks with, i.e., aufs or overlayfs, or just bind mounts, as a means of getting android's storage onto non-default block devices?
It's often hard for me to satisfy myself that android will treat symlinks identically to regular files, hence, I always find myself wondering whether it's link2sd's fault, whenever I manage to break my phone
every time i try to link internal data for a app or link the obb (you know the big files the whole reason i want this to work 
) i come up with the error Failure Link2sd package invalid im using current version of link2sd plus a sandisk 32gb micro sd card my second partition is ext4 stock 4.4.2 with lg stuff, rooted
) i come up with the error Failure Link2sd package invalid im using current version of link2sd plus a sandisk 32gb micro sd card my second partition is ext4 stock 4.4.2 with lg stuff, rooted
bg4m3r
Android Expert
Have you tried reinstalling link2sd? You don't have to use a second partition to bind OBB files. They can be bound to the first partition.every time i try to link internal data for a app or link the obb (you know the big files the whole reason i want this to work
How did you format your card? Does link2sd have root access? Maybe try recreating the mount script.
ShapeShifter499
Android Enthusiast
I have this same exact issue. If I use link2sd to "move apps to sd" it fails but using the stock system baked in "move to sd" in settings it works fine. Any ideas why? I was hopping to make this automatic so all apps get moved by default to the sd card.
bg4m3r
Android Expert
This is a bug in the app. I thought it had been fixed, but I just tried it and it failed for me too. You could still try setting the automatic setting in the options and see if it works that way. It might just be an issue with doing it manually.