privacyguy123
privacyguy123
> Inconsistent Mount cannot be fixed Do elaborate
Confirmed fine on KSU
A Shamiko dev once helped me fix it with ```ro.zygote.disable_gl_preload=1``` Perhaps same issue with your module if you are mass umounting things
You've blown my mind wide open with this latest explanation - good work. You've helped explain a lot of weirdness I've been trying to work out on my side
[mountinfonew.txt](https://github.com/snake-4/Zygisk-Assistant/files/15212586/mountinfonew.txt)
> Both detections are caused by ZygiskNext. It's not a bug. I was hoping for more information as to why, if we are exhaustively hiding everything possible?
Some conversations had relating to this, not taking any credit ... but perhaps you can use this to help hide this particular detection: ``` I don't know the secret yet...
I am far noobier when it comes to this stuff, but I am able to reproduce having this extra jit-cache entry with Zygisk installed on multiple phones. 🤔
"2800000 ==MagiskManagerDetected" Credit goes to ApkUnpacker. Finding this proves useless though, because we don't have Magisk and I personally have all root/Sus apps hidden from this thing. Sharing incase it...
> > Thanks for the information. One thing I've noticed is that with both ZygiskNext and Zygisk, there's always an extra read-write `jit-cache` mapping even after all modules are `dlclose`....