Check your modules first which is the cause of the mount gap…
as much as possible turn off all autohidding toggles and use manual method by adding the suspicious mount paths to custom try_umount or custom sus_mount
if you could compile your kernel, you may update it to the latest susfs… there’s a backport for latest susfs in non-gki:
https://github.com/sidex15/android_kernel_lge_sm8150/tree/OpenELA-4.14.y-susfs
for this one use native detector to check the suspicious mounts… also you need to disable umount mode in the zygisk-next… or if I could guide you further. send the logs by sending the logs zip file using send logs in the danger zone…
There's no suspicious mounts detected it's just mount gap detection with peer id 44 no other info. Maybe it's a false +ve in the app . Also I can't send logs it says failed to prepare logs :undefined. I tried rezygisk but no change. I have turned off all auto hiding also turned off cmd line and hide ksu loops. Only level 4 custom rom hiding is on.
> There's no suspicious mounts detected it's just mount gap detection with peer id 44 no other info. Maybe it's a false +ve in the app . Also I can't send logs it says failed to prepare logs :undefined. I tried rezygisk but no change. I have turned off all auto hiding also turned off cmd line and hide ksu loops. Only level 4 custom rom hiding is on.
Do you have any modules that have mounts? could you show me the full module list?
Sorry for the late response... if you test if there's a mount gap without modules, I think it's probably either using Overlayfs or Magic mount on that KSUN (I assume you're using an old version < KSUN 2.0). try to switch either of those to see if mount gaps are gone...
> Sorry i too was busy (exams). I tested using overlayfs but mount gap persist. Does that mean it's a ROM issue ? Can mnt/androidwritable/ cause this?
are you using a custom rom?