[APP][ROOT] FolderMount - Link folders from internal SD to external to free space

[egingell]

Why "SuperSU by Chainfire is a must"? I run CM13 on SGS4, I have Root access enabled and I can grant SU permissions to the app without SuperSU. But FM doesn't work in that case anyway. Why don't you make it possible for FM to work on MM without SuperSU? There are lots of problems when installing SuperSU on CM13. Many other apps with root requirements work on CM13 without SuperSU.

My guess would be "namespace separation".

Sent from: SGS5 - LP 5.1.1 / SGS4 - LP 5.0.1

 

[madmack]

Up to this point everything is normal. The problem is that FolderMount changes vital system settings (I think especially the vold.fstab). On some devices this can produce fatal errors. Perhaps @madmack can tell us which settings are going to be changed. So we are able to recover them to the original state using a Terminal Emulator?! I needed to restore a TWRP-backup of the system partition many times because of the problems I encountered. Perhaps you also have a backup of your system partition to restore?

In all patches that FM performs, a popup appears asking for the permission. The actual message of this popup indicates which files will be patched. If that didn't happen for you, please let me know. I explicitly state the binaries or ASCII files that FM will attempt to patch due to this reason.

Why "SuperSU by Chainfire is a must"? I run CM13 on SGS4, I have Root access enabled and I can grant SU permissions to the app without SuperSU. But FM doesn't work in that case anyway. Why don't you make it possible for FM to work on MM without SuperSU? There are lots of problems when installing SuperSU on CM13. Many other apps with root requirements work on CM13 without SuperSU.

SELinux policies. Having root access isn't sufficient anymore to do whatever you want. The mount commands particularly are sensitive to these policies and SuperSU has a special flag to work around this problem., default SU doesn't. Set your SELinux to permissive and things should work.

 

[madmack]

So the "old" version 2.8.2 didn't do this lookup from your website? Because it runs without any problems.

You are right. Try this apk and let me know if it crashes or not.

 

[ndrancs]

You are right. Try this apk and let me know if it crashes or not.

Thanks for updated the FM

 

[Danilo-Sanchez]

SELinux policies. Having root access isn't sufficient anymore to do whatever you want. The mount commands particularly are sensitive to these policies and SuperSU has a special flag to work around this problem., default SU doesn't. Set your SELinux to permissive and things should work.

How can I install SuperSU on CM13? Just flash the latest beta?

 

[fipsy]

In all patches that FM performs, a popup appears asking for the permission. The actual message of this popup indicates which files will be patched. If that didn't happen for you, please let me know. I explicitly state the binaries or ASCII files that FM will attempt to patch due to this reason.

Oooops! FM never asked me for anything! Nevertheless it worked. At least for some time until the device was frozen. If it didn't ask for anything, didn't it also change anything? If so, why did I have those freezes even after uninstalling FM? I'd like to see this at least clarified before testing your new apk.

Second: I do not have installed SuperSU anymore since CM11 also provides this feature. Maybe this is a problem? I never encountered any issues concerning su rights with other apps so far. My SElinux has always been permissive as "getenforce" tells.

 

[sn0w89]

You are right. Try this apk and let me know if it crashes or not.

Hi, my phone is SGS4 i9505 running on CM13 from 20160319, I just installed two of your last beta of FM, v2.9.1b and v2.9.2b, over 2.9b but they does not mounting folders, I try a clean install FM without restoring from back up, same result, dont monunt, do reboot after each try, but it not help, then I install 2.9b restor from backup and work and mounting perfect. What can I do for make it work, or, perhaps, it no sense now upgrade to v2.9.2b and use 2.9b?
p.s. sorry for my english
Thank you for useful program

 

[Andycar]

Not just in theory. But there maybe a workaround: If you configure WhatsApp not to download media automatically and you always wait when booting, until FolderMount has bound your WhatsApp folder from external SDCard, you probably will have no losses. Only voice messages are still affected because you cannot prevent them from being downloaded automatically.

There are no any losses, actually. In such situation I usually force stop or greenify WhatsApp, manually unbind the pair, move my "early-received" media files from the folders of internal card to WhatsApp media folders on external card, and then bind the pair in FM again.
Cheers[emoji1]
@madmack, on my Note 4 N910G running CM13, none of the last two betas binds the pairs, whereas 2.9b works nicely[emoji1]
I have external SdCard (64Gb) formatted as exFat and it's vital to me, because I keep large nandroid backup files on it...

 

[Chaleman]

I have a samsung galaxy Grand prime Phone...i installed foldermount app and after running the app it offered to fix a faulty module which i accepted and rebooted but after that i closed the app and went to my files/sd card and saw it was not showing any file
...now i cant move any file to my internal sd card...i still can download apps from playstore but nothing else...even the gallery shows"device memory low,delete some files"..i cant even open gallery...the settings/storage shows total space 4gb..system memory 5gb...applications 189 mb..memory card showing 0. 0 as total...
I tried uninstalling foldermound..
Untooting and factory reset ...nothing helped..plz help...

EXACTLY the same thing happend to me on my Samsung Galaxy S7 930F... After rebooting Foldermount I could write anything to the External SD Card nor move apps to the SD using the traditional android way. I factory reset AND restores from a previous TWRP Backup and still had the same problem, even with different sd cards that I just formatted... so I had to Factory Restore using Kies and start from scratch....

Could this have been prevented or fixed? I love FM, but this needs to be addressed.... Thanks!!!!

Chale

edit: this happened whilst using Foldermount 2.9.1b found a few pages back...

 

[quicktrick]

SELinux policies. Having root access isn't sufficient anymore to do whatever you want. The mount commands particularly are sensitive to these policies and SuperSU has a special flag to work around this problem., default SU doesn't. Set your SELinux to permissive and things should work.

Then how can I configure SELinux policies using root access to allow FM to work properly without SuperSU and without disabling SELinux itself? I've just read something about SELinux and I know it can be configured in the way that allows certain processes to have certain permissions. I'm not an advanced Linux user and it's a little hard for me to work it out by myself.

 

[daniello8]

How is CM13 support coming along? Any ambitions?

 

[fipsy]

Then how can I configure SELinux policies using root access to allow FM to work properly without SuperSU and without disabling SELinux itself?

http://forum.xda-developers.com/showthread.php?t=2524485
Maybe this helps.

 

[MrHomebrew]

EXACTLY the same thing happend to me on my Samsung Galaxy S7 930F... After rebooting Foldermount I could write anything to the External SD Card nor move apps to the SD using the traditional android way. I factory reset AND restores from a previous TWRP Backup and still had the same problem, even with different sd cards that I just formatted... so I had to Factory Restore using Kies and start from scratch....

Could this have been prevented or fixed? I love FM, but this needs to be addressed.... Thanks!!!!

Chale

edit: this happened whilst using Foldermount 2.9.1b found a few pages back...

https://youtu.be/XtsbWHgmzbs

---------- Post added at 07:24 PM ---------- Previous post was at 07:18 PM ----------

EXACTLY the same thing happend to me on my Samsung Galaxy S7 930F... After rebooting Foldermount I could write anything to the External SD Card nor move apps to the SD using the traditional android way. I factory reset AND restores from a previous TWRP Backup and still had the same problem, even with different sd cards that I just formatted... so I had to Factory Restore using Kies and start from scratch....

Could this have been prevented or fixed? I love FM, but this needs to be addressed.... Thanks!!!!

Chale

edit: this happened whilst using Foldermount 2.9.1b found a few pages back...

You should be able to transfer data from your pc to internal phone storage the just use especially file Explorer to transfer the same data to the SD card. I am referring to say pictures or music kind of thing.

Also if you have a USB media stick that you can put your sd card into you can transfer files from your pc to the SD card skipping the process of having to copy to internal, then manually to external.

Again I am referring to being able to access your sd card more effectively so you can manually transfer photos and stuff back and forth between pc and sd card.

I blame samsung for all this added headache and removing adaptable storage.

And just to say I noticed FolderMount transfers all data to sd card as a posed to the adb adaptable storage method fix for the Galaxy s7 edge that others have been using. Which was also slow for Multitasking.

FolderMount by far is the way to go no question about it.

I appreciate all the hard work and dedication from the developer.

https://youtu.be/I2p9VBsfoOQ

 

[Chaleman]

https://youtu.be/XtsbWHgmzbs

---------- Post added at 07:24 PM ---------- Previous post was at 07:18 PM ----------



You should be able to transfer data from your pc to internal phone storage the just use especially file Explorer to transfer the same data to the SD card. I am referring to say pictures or music kind of thing.

Also if you have a USB media stick that you can put your sd card into you can transfer files from your pc to the SD card skipping the process of having to copy to internal, then manually to external.

Again I am referring to being able to access your sd card more effectively so you can manually transfer photos and stuff back and forth between pc and sd card.

I blame samsung for all this added headache and removing adaptable storage.

And just to say I noticed FolderMount transfers all data to sd card as a posed to the adb adaptable storage method fix for the Galaxy s7 edge that others have been using. Which was also slow for Multitasking.

FolderMount by far is the way to go no question about it.

I appreciate all the hard work and dedication from the developer.

https://youtu.be/I2p9VBsfoOQ

Thanks for the video... it worked for me the first time I tried, but then it stopped working and also if I tried to use the "android inbuilt" transfer to sd (change storage location in the phone's settings) I got back a message saying "not enough storage space" in the external sd card, whereas clearly there was heaps of space. What I'm trying to say is that I "think" that the mod foldermount creates on the S7 somehow corrupts the Android's inbuilt system of apps 2 sd transfer...

Chale

edit: foldermount rules them all! i need this to work!! please!!

 

[alershka]

Just wanted a bit of clarification on the requirements for running on Marshmallow.

1) SELinux set to permissive
2) SuperSU standard install (not systemless)

I'm currently running systemless SuperSU without xbin_bind so I can use Android pay. Changing to permissive will probably break android pay but if I don't need to go back to normal root it will save me a step.

I am running stock 6.0 with systemless root on a Moto X Pure. I have to not been able to get the latest beta to work but then again I have not tried forcing permissive yet.

Sent from my XT1575 using Tapatalk

 

[MrHomebrew]

Just wanted a bit of clarification on the requirements for running on Marshmallow.

1) SELinux set to permissive
2) SuperSU standard install (not systemless)

I'm currently running systemless SuperSU without xbin_bind so I can use Android pay. Changing to permissive will probably break android pay but if I don't need to go back to normal root it will save me a step.

I am running stock 6.0 with systemless root on a Moto X Pure. I have to not been able to get the latest beta to work but then again I have not tried forcing permissive yet.

Sent from my XT1575 using Tapatalk

I am se enforcing on the s7 edge with no su systemless and all is up and running for me.

I know we have different phone just saying.

 

[Chaleman]

I am se enforcing on the s7 edge with su systemless and all is up and running for me.

I know we have different phone just saying.

Sorry for my ignorance.. how do I get su systemless? I have my s7 exynos rooted by flashing SuperSU after flashing twrp.... I'm not clear what this is...

Thanks!

 

[haplox]

Hello,

I have been reading a lot of post in the thread, and I still cant understand how the app works, or maybe I am doing something wrong. I bind the whatsapp folder in the internal sd to ext sd, but when I receive new files (images, videos, etc), whatsapp save the files in both sd cards (internal and external).

So, if this is the normal way the app works, I do not understand it, or maybe it is not binding both folders. Apart, every time I reboot the mobile and open FM it is deactivate. Then it says that is mounting all the binds and that the result is OK, but the slider remains deactivated

My phone Samnsung Galaxy Young (GT-S6310N)
Stock 4.1.2 ROM rooted with SuperSU 2.69 installed in /System

Please a help. Thanks

 

[MrHomebrew]

Sorry for my ignorance.. how do I get su systemless? I have my s7 exynos rooted by flashing SuperSU after flashing twrp.... I'm not clear what this is...

Thanks!

You do not need systemless, I do not have it like that. Mine is none systemless I apologize for the confusion.

 

[SpasilliumNexus]

Just wanted a bit of clarification on the requirements for running on Marshmallow.

1) SELinux set to permissive
2) SuperSU standard install (not systemless)

I'm currently running systemless SuperSU without xbin_bind so I can use Android pay. Changing to permissive will probably break android pay but if I don't need to go back to normal root it will save me a step.

I am running stock 6.0 with systemless root on a Moto X Pure. I have to not been able to get the latest beta to work but then again I have not tried forcing permissive yet.

Sent from my XT1575 using Tapatalk

I'm using a Pure with the same systemless setup for Android Pay on stock 6.0 too. You need to open build.prop with a text editor (I use Solid Explorer), search for "esdfs" and change true to false. Reboot and FM will work on both enforcing and permissive (I use enforcing).

See my post here a few weeks back about it: http://forum.xda-developers.com/showpost.php?p=65624939&postcount=3784

Sent from my XT1575 using Tapatalk