yashsingh1/xdaforums huggingface dataset:
[Magisk] Zer0x00:
Tried it -> does not work :/

Edit: Tried also Magisk 16.4 -> same error

Seems like never ROM Revisions of Samsung has this issue.

I'm unable to downgrade to an older stock kernel because samsung blocks ("sw rev check fail device ...")
[Magisk] neromanello:
Does it get into root mode when you enter 'su' ?

What is telling the Magisk log about it & fbind?
[Magisk] neromanello:
Did you try to apply the patch to the boot.img of your new Android? Maybe you have to do it. It's done through ODIN.

First select in Magisk: .img.tar not only .img and select the boot.img from your android room AP .tar file.

Then ODIN to flash the patch.img.tar generated file.

You have a lot of places to found a tutorial doing this...

Take care to backup all your system first!.
[Magisk] Zer0x00:
Yes, it gets to root mode.

Can't experiment because that phone is my daily driver now.
[Magisk] neromanello:
OK. What about Magisk log?, Could you attach it to us?.

If files are 0 KB, you can try checking out the Magisk manager where it shows you its log.
[Magisk] Praetoriani:
First of all, thx VR25 for this awsome module :good:

But now to my problem. I am trying to mount my second Partition but I always fail with it.

This is what i wrote to my config-file:

part /dev/block/mmcblk1p2 /data/SDext2 ext3

But somehow it always ends with Errors. This is what the Log-File sais:

+ date

+ echo -e 'Wed Oct 24 17:03:04 GMT 2018\n'

Wed Oct 24 17:03:04 GMT 2018

+ grep -Ev '^#|^part ' /data/media/fbind/config.txt

+ grep -iq fsck

+ echo -e '\n'

+ apply_config

+ echo 'STORAGE INFORMATION'

STORAGE INFORMATION

+ grep -E '^/mnt/media_rw/4A8E-3950_path|^/data/media/0_path |^part |^LOOP ' /data/media/fbind/config.txt

+ . /data/media/fbind/.tmp

+ part /dev/block/mmcblk1p2 /data/SDext2 ext3

+ '[' -z ext3 ]

+ sed 's/.*\///; s/--L//'

+ echo /dev/block/mmcblk1p2

+ PARTITION=mmcblk1p2

+ echo /dev/block/mmcblk1p2

+ sed s/--L//

+ PPath=/dev/block/mmcblk1p2

+ is_mounted /data/SDext2

+ mountpoint -q /data/SDext2

+ wait

+ grep -Eq /mnt/media_rw/

+ echo '/dev/block/mmcblk1p2 /data/SDext2'

+ echo '/dev/block/mmcblk1p2 /data/SDext2'

+ grep -Eq '/data/media/[1-9]|/storage/emulated/[1-9]'

+ mkdir -p -m 777 /data/SDext2

+ wait_until_true '[' -b /dev/block/mmcblk1p2 ]

+ Count=0

+ '[' 0 -ge 90 ]

+ Count++

/sbin/.core/img/fbind/service.sh: /data/media/fbind/.tmp:line 24: Count++: not found

+ '[' -n '[' ]

+ '[' -b /dev/block/mmcblk1p2 ]

+ break

+ '[' -n '[' ]

+ '[' -b /dev/block/mmcblk1p2 ]

+ grep -q '\-\-L'

+ echo /dev/block/mmcblk1p2

+ '[' -n ]

+ mount -t ext3 -o noatime,rw /dev/block/mmcblk1p2/data/SDext2

mount: mounting /dev/block/mmcblk1p2 on /data/SDext2 failed:Invalid argument

+ is_mounted /data/SDext2

+ mountpoint -q /data/SDext2

+ echo '(!) Failed to mount mmcblk1p2'

(!) Failed to mount mmcblk1p2

+ rmdir /data/SDext2

+ return 1

+ false

Just to make things complete: I am running Android Nougat 7.1.1 on a rooted (Magisk) Stock ROM

Would be great if someone could help me with this issue
[Magisk] VR25:
[MENTION=5116670]Praetoriani[/MENTION] et al, hold on... this week won't end without at least one fbind update!

A new version may be up as early as tomorrow (GMT+1).

---

EDIT

Perhaps the water can start boiling right now.

[MENTION=5116670]Praetoriani[/MENTION], try this...

1. Run <su -c sed -i 's/Count++/Count=$((Count + 1))/g' /sbin/.core/img/fbind/core.sh>.

2. Reboot.
[Magisk] neromanello:
Sorry, can you explain what is this command for? (Just a global explanation... What does it is used for?. (su -c sed)

Thanks!
[Magisk] Praetoriani:
@neromanello

In general:

su is used to get root access

sed is used to replace some text with some other text

And next time, be so good and do not post several times in a row with the same question ;).

Please write everything in one post (you can also quote several people within one post)

@VR25

THX for your input. Will try it :D

EDIT

@VR25

Tried it, but it still doesn't work :( .

Again the logfile:

+ date

+ echo -e 'Thu Oct 25 17:56:30 GMT 2018\n'

Thu Oct 25 17:56:30 GMT 2018

+ grep -Ev '^#|^part ' /data/media/fbind/config.txt

+ grep -iq fsck

+ echo -e '\n'

+ apply_config

+ echo 'STORAGE INFORMATION'

STORAGE INFORMATION

+ grep -E '^/mnt/media_rw/4A8E-3950_path |^/data/media/0_path |^part |^LOOP ' /data/media/fbind/config.txt

+ . /data/media/fbind/.tmp

+ part /dev/block/mmcblk1p2 /data/SDext2 ext3

+ '[' -z ext3 ]

+ sed 's/.*\///; s/--L//'

+ echo /dev/block/mmcblk1p2

+ PARTITION=mmcblk1p2

+ echo /dev/block/mmcblk1p2

+ sed s/--L//

+ PPath=/dev/block/mmcblk1p2

+ is_mounted /data/SDext2

+ mountpoint -q /data/SDext2

+ wait

+ echo '/dev/block/mmcblk1p2 /data/SDext2'

+ grep -Eq '/data/media/[1-9]|/storage/emulated/[1-9]'

+ echo '/dev/block/mmcblk1p2 /data/SDext2'

+ grep -Eq /mnt/media_rw/

+ mkdir -p -m 777 /data/SDext2

+ wait_until_true '[' -b /dev/block/mmcblk1p2 ]

+ Count=0

+ '[' 0 -ge 90 ]

+ Count=1

+ '[' -n '[' ]

+ '[' -b /dev/block/mmcblk1p2 ]

+ break

+ '[' -n '[' ]

+ '[' -b /dev/block/mmcblk1p2 ]

+ grep -q '\-\-L'

+ echo /dev/block/mmcblk1p2

+ '[' -n ]

+ mount -t ext3 -o noatime,rw /dev/block/mmcblk1p2 /data/SDext2

mount: mounting /dev/block/mmcblk1p2 on /data/SDext2 failed: Invalid argument

+ is_mounted /data/SDext2

+ mountpoint -q /data/SDext2

+ echo '(!) Failed to mount mmcblk1p2'

(!) Failed to mount mmcblk1p2

+ rmdir /data/SDext2

+ return 1

+ false
[Magisk] VR25:
[MENTION=5116670]Praetoriani[/MENTION], what happens when you try to mount it manually?

su
mkdir -p /data/SDext2
mount -t ext3 -o noatime,rw /dev/block/mmcblk1p2 /data/SDext2
[Magisk] Praetoriani:
This is what the console returns if I try to mount it manually:

mount: '/dev/block/mmcblk1p2' -> '/data/SDext2' : Invalid Argument

I attached two images, just to show you that the partition is there. It's the 2nd partition (ext3 formatted) on my external sd
[Magisk] Praetoriani:
@VR25

After several attempts, I could finally mount the partition manually :D

When I looked inside the /data-directory I recognized that all foldernames were in small letters.

So I renamed the SDext2-Folder to sdext2. Not sure if this makes a big difference.

Next I opened up a terminal and entered the following command:

mount /dev/block/mmcblk1p2 /data/sdext2

And ... it worked ;)

However, the partition is mounted as ext2

(although in fact it is an ext3-formatted partition)

:eek:

I attached two pics for you to proof that it worked

:victory:

The big question now is, how can I get this done with your module?

Or ... in other words:

Is there a way you can implement this in your module, so that it can be done with your module too?

EDIT

@VR25

let me tell ya two more things:

1) I'm such an idiot. I always thought that my partition is ext3-formatted.

But that's false. The partition is definitely ext2-formatted.

:eek: :silly:

2) Due to 1) I therefore changed the original line inside the config-file from

part /dev/block/mmcblk1p2 /data/SDext2 ext3

to

part /dev/block/mmcblk1p2 /data/sdext2 ext2

and now it works like a charm.

The partition now gets mounted on every boot.

:victory:

Sorry for all the throuble I made.

:o

Big thanks for your time you invested to help me out.
[Magisk] Savek:
Problem with Pie

Hi!

Have been using fbind for quite a while with LineageOS 15.1 - now switched to 16.

Installed Magisk 17.3 and fbind 2018.8.10-1 via TWRP.

Fixed the Count++ via sed.

So no error messages any more; just that my folder contents are visible under "/data/media/0" - but not under "/storage/emulated/0" as they used to.

This apparently messes up WhatsApp as it doesn't find any data and re-generates a new setup under "/storage/emulated/0/WhatsApp" instead of using the existing data.

OnePlus:/ # ls -la /storage/3938-3234/.fbind/WhatsApp/

total 896

drwxrwx--x 7 root sdcard_rw 131072 2018-05-18 21:36 .

drwxrwx--x 4 root sdcard_rw 131072 2018-10-26 00:54 ..

drwxrwx--x 2 root sdcard_rw 131072 2018-10-25 18:59 .Shared

drwxrwx--x 2 root sdcard_rw 131072 2018-10-25 03:34 .trash

drwxrwx--x 2 root sdcard_rw 131072 2018-05-18 21:36 Backups

drwxrwx--x 2 root sdcard_rw 131072 2018-10-25 02:01 Databases

drwxrwx--x 12 root sdcard_rw 131072 2018-05-18 13:46 Media

OnePlus:/ # ls -la /data/media/0/WhatsApp/

total 772

drwxrwx--- 7 media_rw media_rw 131072 2018-05-18 21:36 .

drwxrwx--- 15 media_rw media_rw 4096 2018-10-26 01:06 ..

drwxrwx--- 2 media_rw media_rw 131072 2018-10-25 18:59 .Shared

drwxrwx--- 2 media_rw media_rw 131072 2018-10-25 03:34 .trash

drwxrwx--- 2 media_rw media_rw 131072 2018-05-18 21:36 Backups

drwxrwx--- 2 media_rw media_rw 131072 2018-10-25 02:01 Databases

drwxrwx--- 12 media_rw media_rw 131072 2018-05-18 13:46 Media

OnePlus:/ # ls -la /storage/emulated/0/WhatsApp/

total 8

drwxrwx--x 2 root sdcard_rw 4096 2018-10-26 00:52 .

drwxrwx--x 15 root sdcard_rw 4096 2018-10-26 01:06 ..

OnePlus:/ # cat /data/media/fbind/config.txt

from_to "WhatsApp" ".fbind/WhatsApp"

from_to "Threema" ".fbind/Threema"

Logs attached.
[Magisk] VR25:
[MENTION=5116670]Praetoriani[/MENTION], after the manual testing, I was going to ask you about the filesystem. So, no worries! :p

[MENTION=876473]Savek[/MENTION], and that's the report I wanted to see the most!

Other Pie and Oreo users, where are you hiding at? :rolleyes:

Lets gather additional data first, if you don't mind having SdcardFS support.

1) What's the output of getprop | grep -Ei 'fuse|sdcardfs|esdfs'?

2) Upload the file generated by su -c mount >/sdcard/mounts.txt.
[Magisk] Savek:
1: OnePlus:/ # getprop | grep -Ei 'fuse|sdcardfs|esdfs'

[persist.esdfs_sdcard]: [false]

[persist.fuse_sdcard]: [true]

[persist.sys.sdcardfs]: [force_off]

[ro.sys.sdcardfs]: [0]

ro.sys.sdcardfs was set to "0" by me during testing - not sure about the initial value though.

2: attached.

One more thing: When I try to mount manually to "/storage/<sdcard>/WhatsApp", the phone reboots:

OnePlus:/ # mount | grep WhatsApp

/dev/block/mmcblk0p28 on /data/media/0/WhatsApp type ext4 (rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered)

OnePlus:/ # umount /data/media/0/WhatsApp

OnePlus:/ # mount /dev/block/mmcblk0p28 /storage/emulated/0/WhatsApp

---> freeze, reboot

Same thing happens during startup, when I add the intsd_path to the config.txt.
[Magisk] neromanello:
Mounting Script at init

Hi [MENTION=5228676]VR25[/MENTION] or another caritative soul. Please help, as the module does not work rightly during boot, I'm needing to put a script delayed at the init of the system. Of course after Magisk and FBIND. The only thing I need to run (as you know) is:

su -c 'fbind -mb'

And to have an icon in my home screen that runs this. and another icon to run the -u command. I think these ones could be '.sh' files, but as I don't know scripting I don't know if it's as easy to run root commands. I've read that NO. So please try to help me doing this.

It's the only thing I need as when my cellphone reboots it starts OK but unmonted .

Could you help me or oriented in same way?. Maybe this could bring a solution for another ones... in the meanwhile...

Thanks!
[Magisk] VR25:
There's an app called SManager (script manager) which lets you do all that easily.

You need a script with <su -c fbind -mb> and another with <su -c fbind -u>. However, since the app will be granted root access anyway, <su -c> can be omitted. SManager allows you to run scripts on boot and even create shortcuts/widgets to run these at anytime.

Now, moving on, I reproduced the issue you reported. The culprit is Magisk, not fbind. The problem is, Magisk is failing to execute fbind's boot script (service.sh). It's as if the script didn't exist.

If you run the script manually, it works as expected. If you copy it to /sbin/.core/img/.core/service.d/ and set 755 permissions, guess what? It also works. You have to change modPath in the script to /sbin/.core/img/fbind, though.

I'm on Magisk 17.3. Will downgrade and see how things go.

By the way, I've finished working on a new version days ago. Just couldn't publish it due to this issue.
[Magisk] neromanello:
Hi!, thanks for the answer!!, I can see you have a muddle laying around here, so thanks to attend us...

I'm going to check that during the day.

And OK, could be this due to an issue regarding the early execution of the module (or similar) that maybe postponing it could solve? Is there an easy wat to check that?. OR Maybe your solution of service.d is such... ???

Regarding changing modPath, I've been running Termux, just writing 'su' and then using 'fbind' commands normally (the path was the /data for Termux dir). Do you mean that I need first to change the path inside Termux to this: '/sbin/.core/img/fbind' ???. And only after this executing the 'fbind' commands?, or what did you mean?. (To change it inside service.sh AT the new directory '/sbin/.core/img/.core/service.d/' )????

PD: Ah ok, SManager, I've read about it in this thread, so, ok I will try to make the scripts with it.

Thanks!!!
[Magisk] VR25:
No, that's not the problem. The script is not executed at all. All other modules' service.sh run as expected. Either Magisk is pretending the file isn't there or the file is being hidden from it. Very strange behavior... downgrading to Magisk 17.2 didn't help.

I meant changing that variable's value in service.sh (editing the file).
[Magisk] neromanello:
OooK, the variable as default is:

modPath=${0%/*}

Just trying with:

modPath=/sbin/.core/img/fbind

Inside '/sbin/.core/img/.core/service.d/' folder with 755 permissions.

I'll give you my feedback.

EDIT: [MENTION=5228676]VR25[/MENTION]

The next time I've booted, the only strange thing was that I have a new SD card notification to transfer media as the first time boot. Then, all the things seems to be at the same way (not having mounted the dirs.).

Magisk log is saying nothing about service.sh.

Here it's my 'terminal.log' file, maybe it is usefull for you for something. As other log files are empty...

And another thing: Here it's an screenshot of my permissions on my SD Card. As you use in the script something like "/mnt/media_rw", maybe it's related...
[Magisk] VR25:
**2018.10.28-beta (201810280)**

- Automatic partition filesystem detection

- Doubled SDcard wait timeout

- Enforce the <global> mount namespace by running <mount> under <su -Mc>.

- Remove modified props from /data/property/ and don't create these again.

- SDcardFS support for Android 8.0+ (experimental)

- Updated building and debugging tools

- Updated documentation

- Use <var=$((var + 1))> instead of <var++>.

- Use the largest SDcard partition as fallback for bind-mounts.

---

Notes

- Other major changes have been made, besides the ones listed above.

- SDcardFS support is a work in progress. It all started when [MENTION=5765352]TechnoSparks[/MENTION] decided to take a closer look at it. Read the details here. That blog post is updated regularly. So, keep checking SDcardFS news there!

- The default working mode for Oreo+ relies on SDcardFS. If fbind finds that unsuitable/immature, it automatically switches to the legacy (FUSE) mode. The phone reboots (cleanly) to apply changes. So, don't worry if that happens to you the first time after installing this version (shortly after boot). Users can force FUSE or SDcardFS modes by moving system.prop.FUSE or system.prop.SDcardFS to system.prop. All 3 files reside in </sbin/.core/img/fbind/>.

- If auto-bind doesn't work, run su -c mv /sbin/.core/img/fbind/service.sh /sbin/.core/img/.core/service.d/.

---

Bugs

- Obviously, this is not a fully baked cake. Expect some ants coming out of it.
[Magisk] VR25:
And here's a stable release...

**2018.10.29 (201810290)**

- Automatic partition filesystem detection

- Doubled SDcard wait timeout

- Enforce the <global> mount namespace by running <mount> under <su -Mc>.

- Generate basic logs as opposed to verbose.

- Magisk 15.0-17.3 support

- Remove modified props from /data/property/ and don't create these again.

- Removed <setenforce x> and other rather useless features.

- Save tmp files to </dev/fbind/>.

- Updated building and debugging tools

- Updated documentation

- Use <var=$((var + 1))> instead of <var++>.

- Use the largest SDcard partition as fallback for bind-mounts.

---

Find me on Telegram -- https://t.me/vr25xda/.
[Magisk] appman1234:
I would like to report that the latest version does not mount the folders after reboot, and need to mount them manually myself. Not happen to previous versions 2018.8.15 or older.

Both Redmi Note 4X and Mi Pad 4 have the same situation.

Thanks for this awesome module!
[Magisk] VR25:
Thanks for reporting.

What's your system setup? I'm on LOS 14.1, harpia, Magisk 17.3 and auto-mount is working.

If </data/media/fbind/logs/service.sh.log> exists, please, upload it. Thanks.
[Magisk] appman1234:
The log folder does not exist. Need any command to enable it?

I'm on miui.eu 8.10.25 rom, Magisk 17.3.

I manually save the info displayed by fbind -i command and attached herewith.

Thanks!
[Magisk] VR25:
There's no switch. It's supposed to be generated automatically.

Does </sbin/.core/img/.core/service.d/fbind.sh> exist? If so, are folders bound when you run it manually as per the steps below?

su
PATH=/sbin/.core/busybox:$PATH
sh /sbin/.core/img/.core/service.d/fbind.sh
[Magisk] appman1234:
Yes, </sbin/.core/img/.core/service.d/fbind.sh> exists.

My folders are bound when I ran it manually as per your steps. Also, the "logs" folder and service.sh.log file are created (attached) as well.

However, I found that my folders are not bound and service.sh.log is not updated after reboot the phone manually.

Thanks!

Edit:

It seems that Magisk does not run any service.d service scripts. The below is the excerpt of Magisk log:

...

466 512 I Magisk : hide_list: [com.nianticlabs.pokemongo]

466 791 I Magisk : ** late_start service mode running

466 791 I Magisk : * Running service.d service scripts

466 791 I Magisk : * Running module service scripts

466 791 I Magisk : swaptorpedo: exec [service.sh]

...

Thanks!
[Magisk] VR25:
This situation just got funnier! :rolleyes:

In my case service.d scripts are executed, but module's service.sh aren't!

That's why I moved service.sh to ...service.d/fbind.sh in the first place.

The questions still remains, if the script has no issues (i.e., it does it's job when ran manually), why isn't it executed by Magisk?

Now, are folders bound automatically on the next boot after moving </sbin/.core/img/.core/service.d/fbind.sh> to </sbin/.core/img/fbind/service.sh>?
[Magisk] appman1234:
Finally it WORKS by the following trial and error:

1) </sbin/.core/img/fbind/service.sh> with permission 0644 or 0755 - WORKING!

2) </sbin/.core/img/.core/service.d/fbind.sh> with permission 0644 - NOT WORKING!

3) </sbin/.core/img/.core/service.d/fbind.sh> with permission changed to 0755 - WORKING! (It seems that the permission of the file is not properly set.)

Hope this helps :)
[Magisk] VR25:
And I just released an update. Thanks.

**2018.10.30 (201810300)**

- Boot script is now in two different locations, but it'll run only once. Hopefully this rogue behavior ensures auto-bind works every time.

- Corrected wrong version numbers in module.prop.

- Fixed <fbind.sh permissions not changing due to MOUNTPOINT0 variable being local to install_module()>.

- Minor cosmetic changes

- Use </sbin/su -Mc mount -o rw,gid=9997,noatime> as <mount> alias.
[Magisk] TrippyEngine:
Hi, I tried the latest version of your module, but after creating the config.txt and going to the terminal to type su and then fbind -mb, there is an error that the operation is not permitted, so it left source intact. Do you have any suggestions?
[Magisk] VR25:
Please post...

1) </data/media/fbind/logs/> (after a reboot)

2) Your config.txt

3) A screenshot of the error

You didn't edit config.txt on Windows Notepad, did you?
[Magisk] The_Walking_Playground:
Hi [MENTION=5228676]VR25[/MENTION],

Thank you for this module. I'm having the same issue with the latest version of the module as I had with the 8-10-2018-1 version: the folders are bind mounted to data/media/{user} but cannot be accessed at storage/emulated/{user}. If I adjust the intsd_path to storage/emulated/0, it still doesn't work. There's nothing in the log that indicates a failure since I can see the proper folders in data/media.

My device is the HTC U11, running Slim9 Alpha (Pie). Please let me know what logs or terminal output I can provide to help troubleshoot this issue.

TWP

P.S. Screenshot isn't working for me as I'm bind mounting the Pictures folder, but I'm told there isn't sufficient storage. So maybe there's an access or SELinux issue with Pie?

P.P.S. Un-bind-mounted the folder so I can upload screenshots of what data/media looks like versus my internal storage, where the bind mounts appear as inaccessible folders. Also uploading log file and config.txt. Please let me know how to proceed, as I'm available to test today.

P.P.P.S. Interestingly, the "target" command doesn't seem to result in a non-accessible folder - it just doesn't bind mount at all. But I also noticed that on some reboots, I can access the internal storage "Download" folder. Could it be a timing issue, in addition to an access issue?
[Magisk] VR25:
Hmm, that's very interesting!

The quick explanation is that Pie may not come with FUSE support, unlike previous Android versions. So, perhaps it's only shipping with SDcardFS.

In order to work properly, fbind has to disable SdcardFS and another virtual file system named ESDFS (similar to SdcardFS and usually found on Motorola phones). Doing so, FUSE is the only alternative left. If it's absent, then SDcardFS can't be disabled.

Bind-mounting folders under SDcardFS is a work in progress. There's a beta version for users to play with. Unfortunately, no one has shown interest in testing it yet. My current system has legacy SDcardFS, which works differently. Otherwise, progress on this would be blazing fast.

Now, would you mind doing me a favor?

Upload /proc/mounts as mounts.txt

1) With fbind enabled

2) With fbind disabled

Thanks
[Magisk] The_Walking_Playground:
Hi,

Thanks for your response! I saw the Beta version, but there was a stable release post right after it, so I (incorrectly) assumed the stable release included those changes. That could also be why no one else has tested it. Attached is the output that you requested. I'll try the Beta version right now. Thanks!

TWP

EDIT: [MENTION=5228676]VR25[/MENTION] Is the Beta version in the OP that's labeled 8.28 supposed to be the one that supports sdcardfs? If so, it's labeled incorrectly, which could also be the reason no one has tried it ;).

EDIT 2: I just booted up the sdcardfs version, and my device immediately rebooted after I logged in. I assume that means fbind is unable to use sdcardfs on my device?

EDIT 3: Added logs folder from Beta version. Hope that helps! I'll keep the Beta version installed for now.
[Magisk] VR25:
Uh-oh, I forgot to rename that zip! :silly: It should be 10.28. Thanks for point that out. :p

Yes, your SDcardFS version behaves just like mine! Fbind reboots your device once because it has to enable FUSE and switch its working mode to legacy.

With it still installed and enabled, what's the output of <getprop | grep -Ei 'esdfs|sdcardfs|fuse'>? Thanks.

P.S., [MENTION=8756890]The_Walking_Playground[/MENTION], which device is this?
[Magisk] The_Walking_Playground:
Hi,

Here's the relevant output of the command:

shell@ocn:/ $ getprop | grep -Ei 'esdfs|sdcardfs|fuse'
[persist.esdfs_sdcard]: [false]
[persist.fuse_sdcard]: [true]
[persist.sys.sdcardfs]: [force_off]
[ro.sys.sdcardfs]: [false]
shell@ocn:/ $

TWP
[Magisk] VR25:
[MENTION=8756890]The_Walking_Playground[/MENTION], so, I forgot your device...

I really need to bring my sleep game back up! :rolleyes:

Anyway...

Unfortunately, unless you downgrade to Oreo-, you can't use FUSE. Therefore, fbind won't work properly.

We're in the same situation when it comes to sdcardfs. Other than that, I'm still on Nougat (LOS 14.1).

You have to wait until [MENTION=5765352]TechnoSparks[/MENTION] and I come up with new algorithms.

We'll be performing additional tests soon and a new beta will surface, eventually. Thanks for your collaboration!