Error: Unable to bind folder
Hi I am able to link apps using app2sd. However, apps default data folder is not automatically linked, eg whatsapp image folder. I tried the folder mount to sdext2 folder or sd card. Both failed saying unable to bind. I am also not able to find any log file. Is there anything that I can do to link my internal folder to external card or the sdext2 (ext4) folder?
What are the source and destination folders used in the pair?
Check the error report for any logs (It's an option in Apps2SD)Sorry, don't really get what you mean by what they are used. I was trying out before doing on actual data. So I just created a new folder "test":
And tried to bind to sdext2:
I googled somewhere that say maybe folder permission issue. So I tried binding in the same internal folder:
This also doesn't work.
My phone is rooted. OS is kitkat 4.4.4. Is this version an issue?
Check the error report for any logs (It's an option in Apps2SD)
Managed to find the error report and learn how to read it. It's a directory issue and corrected it. It's working now, but linking to sdext2 folder had given me a shock, the whole of the internal storage becomes unavailable after that. Don't know why, but the system reports access denied to internal storage.
Had now link everything to external sd card to play safe. But correctly the folder mount interface becomes very very slow. Not too sure why. Hopefully everything will be fine. Had started linking actual data file now.
Use Apps2SD backup restore tool for app backup and use Broken app cleaner to delete leftover files which would resolve most of the play store errorsI had trouble updating apps backed up and restored or just moved to my micro SD card using Titanium Backup. I've even bought the full version after reading it's the definitive app backup tool on Android, but now I'm a little disappointed. After wiping and reflashing my phone several times over the last few days, I ended up ignoring the backup and just reinstalling the apps from the Google Play library, spending the time reconfiguring everything again.
Anyway, did anybody have the problems with App2SD breaking app auto update on Google Play? I was getting the dreaded 963 error.
ran into a major issue with Apps2sd. I'd been using it Pro updated on a newer phone ok, been recently using the Tasker intent to mount all folders after booting as the auto folder mount still seemed intermittent the last version I tried. On this phone I hadn't been using a second partition for linking.
Just a couple of days ago I had to send that new phone away for repairs and returned to using my old phone. Everything seemed ok until I updated the old version 13.3 to 14.3 and did the same folder mount after boot using Tasker (unsure if that's part of the fault just something I did). Then my second partition would never mount and after a quick search and FAQ check I followed the instructions of repartitioning and fixing 2nd partition permissions. After finishing the long backup, partition and restore, the same issue exists where 2nd partition won't mount, so I reverted to v13.3 and it mounts ok again. Is there some known issue in the later versions I should avoid? I can probably narrow down the issue now I know I can just change the app version to test rather than taking forever trying to fix the partition. Only just figured this out... need to relink all those apps and configs again...
I didn't record it down but it seemed to be the normal mount error. A quick search and I see it looks like this "mount: mounting /dev/block/vold/public:179_66 on data/sdext2 failed: invalid argument"What is the error in v14.3?