When installing, there is written:
Yes... new Shadow storage policy by google coz this mess..OK. Let's see...
fbind is working with LOS-18.1/Magisk-22 flawlessly. It mounts cleanly to /data/media[/0].
But the mounted folder(s) is/are not accessible via /storage/emulated[/0].
Even "/storage/emulated" is not accessible by root.
And fbind cannot mount to /storage/emulated[/0] anymore.
I expect this is due to Android-11's new secure storage policy.
Does someone has an idea to trick that out???
This is due to Googles "scoped storage policy" (forced in Android11).
Update to this problem:Quick question, and forgive me I havent had time to read all 90 pages to this thread. Wanted to see if quick fix / known issue workaround to this:
When I try to use latest fbind from github, using something as simple as "target" results in my entire SD card being mounted in the internal specified folder. Same when I use from_to ... is there known cause / easy workaound for this?
If not, I can provide more details in a later reply. Here is an example of the result:
$internal/somefolder/subfolder -> $rootOfSDCardContents
$internal/somefolder/subfolder -> $rootOfSDCardContents/somefolder/subfolder
part -o umask=0 /dev/block/mmcblk1p2--L,MyLoNgPaSsWoRd /mnt/sdcrypt extsd_path /mnt/sdcrypt target DCIM target Audio target TitaniumBackup